DigUp Guide Unofficial
EN

DigUp Indexing Slow or Files Skipped

DigUp indexing can take significant time during its initial pass and deliberately ignores cloud-only files, system items, and excluded formats.

Current versions: 0.6.1 for Mac, 0.7.0-beta.1 (beta) for Windows and Linux; checked against DigUp's GitHub releases on October 15, 2026.

First-Pass Indexing Speeds

On a Mac, several hundred files typically take a few minutes, while a large Downloads folder can take an hour. On Windows and Linux, DigUp uses the graphics card when a setup check finds it faster, or the processor otherwise. When running on a processor alone, a picture takes a few seconds (about five seconds on a 2017 laptop’s Core i5), so a large photo library can take hours. After the first pass finishes, DigUp only reads new files, which become searchable a few seconds after saving.

Files That DigUp Skips by Design

DigUp deliberately excludes several categories of files from regular indexing:

  • Cloud-only files that do not live locally on your drive (such as online-only files on iCloud or OneDrive). See cloud-only files troubleshooting for details.
  • Keys, certificates, password files, and hidden directories such as .ssh.
  • Applications, caches, and folders that look like datasets.
  • Source code files in ordinary folders. Inside a repository containing .git or package.json, DigUp indexes only screenshots unless you configure code search.
  • On Windows and Linux, old Word .doc files, RAW photos, and SVG images are skipped, and text inside screenshots is not read.

Mac Indexing Settings and Updates

On macOS, version 0.6.1 introduced scheduled indexing in Settings → Folders. If configured, indexing pauses until the set hours (1:00 to 7:00 by default), while search remains available throughout the day. Version 0.6.1 also resolved an issue where folders with rapid changes restarted scans repeatedly, and added handling to skip runaway files automatically instead of stopping.

Step by step

  1. Check indexing status

    Open the menu bar icon on macOS or the system tray icon on Windows and Linux to see if indexing is currently active or paused.

  2. Review indexing schedule

    If using a Mac, check Settings → Folders to verify whether indexing is restricted to specific hours such as 1:00 to 7:00.

  3. Verify file locations

    Check that missing files reside locally on your disk rather than in cloud-only storage, and ensure they are not inside hidden folders or datasets.

  4. Check code search configuration

    If source files are missing, open Settings → Code to confirm that the folder is selected for code indexing and search using the code: prefix.

  5. Update the application

    If scanning stalls repeatedly on macOS, check that you are running version 0.6.1 or later to ensure bug fixes for scan restarts and runaway files are present.

Questions

Why does DigUp take hours to index photos?

On Windows and Linux systems running without graphics card acceleration, processing each image on a processor takes a few seconds, which adds up across large libraries.

Why is my source code missing from search results?

DigUp skips code during ordinary indexing. To index functions and repositories, turn on code search in Settings and select specific project folders.

Can I pause indexing while using my computer?

Yes. You can pause indexing from the menu bar icon on a Mac or the tray icon on Windows and Linux, or set restricted indexing hours on macOS in Settings → Folders.