Rebuild Database Indexes

Rebuild checks existing search data and index consistency. Its scope differs by strategy: completion does not mean every missing feature has been extracted. Refresh mainly syncs file changes.

Steps

1. In the workspace’s Files tab, open the three-dot menu beside Database and choose Repair Database.
2. Choose the database area or feature data that needs repair.
3. For Image Database, check the strategies shown below; they follow the Add Files strategy configuration.
4. Start the task and watch progress.
5. After completion, try the related search again.

Only one database type is repaired per run. Repeat for another type if needed.

Which Database Should You Choose?

• Image database: use it for image search related capabilities, including global, global subject, color, and local strategies.
• Pose database: use it when pose search data needs to be regenerated.
• Semantic database: use it when text-prompt search is unavailable or abnormal.
• Face database: use it when face search or face albums need to be regenerated.

The dialog does not provide a separate file database or duplicate database. Normal file additions, removals, renames, and replacements belong to Refresh Database. If duplicate search reports missing hashes, use its Go to Repair Database action or refresh after enabling the duplicate setting.

Choosing Image Strategies

• Global: rebuild normal reverse image search.
• Global subject: useful when a clear subject is the part you want to compare.
• Global color: rebuild color-aware search data.
• Local keypoints: align the search index with already saved keypoint data. This does not first-extract keypoints for existing photos or re-extract them with new parameters.

Difference from Refresh

Refresh checks what changed in folders and updates records. Rebuild checks existing data and indexes. To add missing keypoints, enable Local · Keypoints under Settings → Add Files while retaining other needed parsing options, then right-click a small set of files and choose Reparse File. After successful completion, open database details to refresh statistics and reopen Image Search. Reprocessing may affect existing collection associations and other image records; back up an important database before proceeding beyond a small trial.

Common Cases

• If a search strategy shows no results, check its parsed data and scope first. Local-keypoint repair can finish immediately when there is nothing to align, even if no keypoints have ever been extracted.
• If face albums are incomplete, rebuild face data.
• If database.db itself is damaged and cannot be opened, this index repair is different from Tools → Repair Database File. Use the damaged-file guide only when corruption is confirmed.

Wait for background tasks to finish and refresh statistics before treating a count mismatch as an error. Multiple-subject parsing can produce more subject records than photos; that alone does not indicate corruption.