DigUp reads files locally across macOS, Windows, and Linux. If indexing pauses, an installer shows an unrecognized prompt, or specific files do not show up in results, checking system permissions and supported file types can help identify what happened.
Installation and System Prompts
On Windows, the beta installer is not signed yet, so Windows may say it does not recognize the app. If that prompt appears, select “More info” and then choose “Run anyway”. Review DigUp Windows Installer Warning During Setup for the installation steps.
On a Mac, opening a video at its moment in QuickTime Player triggers an operating system prompt asking once whether DigUp may control it. For details on this permission dialog, see QuickTime Permission Prompt in DigUp.
Indexing and Excluded Files
DigUp only reads files inside the folders you explicitly pick. It never downloads files that only live in cloud storage, such as iCloud on a Mac or OneDrive on Windows. Details on cloud file exclusions are documented at Indexing iCloud and OneDrive Files in DigUp.
If indexing seems delayed or certain files are absent, check DigUp Indexing Slow or Files Skipped. DigUp does not skip long PDFs entirely; it indexes the first 30 pages right away and reads the rest later, indexing up to 5,000 pages a file. Note that macOS version 0.6.1 resolved issues where folder names with accents or non-Latin characters could stall indexing, as well as problems where frequently changing folders restarted scans. Windows and Linux builds remain in beta (0.7.0-beta.1).
Language Queries and Search Matches
While DigUp evaluates queries across more than 100 languages as outlined in DigUp Cross-Language Search, exact-word matching functions differently from conceptual meaning. Text inside screenshots is only indexed on a Mac, and languages written without spaces are not split into distinct words for exact matching.