DigUp reads only the folders you choose and skips certain files and folders on purpose, so check the documented rules below first if you see “0 files indexed”, “0 of 0”, or empty search results. The Mac 0.6.1 update fixed two bugs that caused zero-file counts, while several user reports on Mac and Windows remain open as of 2026-10-16.
Documented reasons for 0 files or no results
| What you see | Documented reason | Where to check |
|---|---|---|
| A chosen folder is a code project | Inside a code project (a folder with .git, package.json and the like), ordinary search reads only screenshots. Searching source files requires turning on code search in Settings → Code or during setup, and starting your query with code:. |
Code search guide |
| Files only live in the cloud | DigUp never downloads files that only live in the cloud, such as iCloud on a Mac or OneDrive on Windows. | Cloud files guide |
| Specific files are missing | DigUp only reads supported pictures, PDFs, documents, audio, and video. On Windows and Linux, old Word .doc files, RAW photos, and SVG pictures are skipped. |
Supported file types |
| Folders or files are skipped by design | DigUp never reads keys, certificates, password files, hidden folders like .ssh, apps, caches, or folders that look like datasets. It also skips any folders or file types you excluded in Settings. |
Settings |
| The first pass is still running | The first indexing pass takes a few minutes for a few hundred files on a Mac, or can take hours for a large photo library on Windows and Linux on a processor alone. | Menu bar on a Mac, or the tray on Windows and Linux (Indexing speed guide) |
| The model download stopped | DigUp needs the 865 MB model before it can index and search your files. | Model download guide |
Fixes in Mac 0.6.1
If you use an Apple Silicon Mac, check that you are running DigUp 0.6.1, which fixed two indexing issues:
- Code folders used to show “0 of 0”. They now show their files right away, and Settings notes that they are read after your other folders (issue #21).
- Choosing a folder with accents, Korean, or Japanese in its name (such as Google Drive’s “내 드라이브”) no longer stops indexing for every folder (issue #14).
Open user reports (as of 2026-10-16)
Users have reported other cases where DigUp shows zero indexed files. As of 2026-10-16, the cause of these reports is not confirmed by the developer and there is no released fix in the checked threads:
- On Mac (0.6.x) and in comments from Windows 0.7.0-beta.1 users, folders are listed in Settings but the status stays at “0 files indexed” or “0 files out of 0”, even after restarting (issue #67).
- On 64-bit Windows 11 with 0.7.0-beta.1, indexing finishes with no error, but the folder shows “0 files indexed” and searches for file names, content, or pictures return nothing (issue #97).
- On a Mac, a 40 GB photo library in
~/Picturesshows “nothing to index here yet” or “zero of zero indexed” (issue #43). - On Windows 11 with 0.7.0-beta.1, users report that a file larger than 2 GB in a chosen folder stops indexing for that folder and subsequent folders (issue #87; see Windows and Linux beta known issues).
If you run into one of these symptoms, you can add details to the matching issue or open a new report on DigUp’s GitHub Issues page.
Search matching limits
If files are indexed but a query returns no match, check how your search is phrased. Exact words such as invoice numbers, error codes, and names are matched as written in file names and document text. On Windows and Linux, text inside screenshots is not read yet. In languages written without spaces, such as Chinese, Japanese, and Thai, text is not split into words for exact matching, though searching by meaning works (Search tips). On a Mac, 0.6.1 also fixed a bug where a word that appears only as the start of a longer word disappeared after you stopped typing (issue #40).