# DocFetcher Problems & Issues 2026 - Crashes, Memory & No Results

Source: https://www.tryorbye.com/products/docfetcher
Last analyzed: 2026-11-19
Try or Bye score: 64/100

## Verdict: Try with caution

DocFetcher works for some teams, but users report recurring problems (score 64/100). Most reported issues: DocFetcher crashes with 'program died' while indexing; Runs out of memory on large document collections; DocFetcher not finding words that are in the file. Not a good fit for: People who want instant filename search; Users with scanned paper archives. Users most often switch to AnyTXT Searcher, Recoll, Agent Ransack.

## What it is

DocFetcher is a free, open-source (Eclipse Public License) desktop search app that indexes folders you choose and then searches the text inside PDFs, Office files, Outlook PST, EPUB, HTML, archives and more in milliseconds. It runs on Windows, macOS and Linux, has a portable version you can carry on a USB drive or cloud folder, and since version 1.1.26 bundles its own Java runtime. New features now go into the paid DocFetcher Pro; the free version gets maintenance releases (1.1.27 in January 2026). It suits researchers, lawyers, admins and anyone with a big pile of local documents who wants private, offline full-text search.

## Common errors & fixes

### DocFetcher 'Folder Hierarchy Is Too Deep' Error

This error means Java ran out of stack space walking deeply nested folders. Raise -Xss2m to -Xss4m in the launcher script and always start DocFetcher from that script.

1. **Windows** — Move misc\DocFetcher.bat up into the DocFetcher folder Edit the last line and change -Xss2m to -Xss4m Always launch DocFetcher through DocFetcher.bat
2. **Linux and macOS** — Open DocFetcher.sh in a text editor Change -Xss2m to -Xss4m and save Start DocFetcher from the script
3. **Rebuild the index** — Right-click the failed index and choose Rebuild Index

Full guide: https://www.tryorbye.com/products/docfetcher/issues/folder-hierarchy-too-deep

### DocFetcher High CPU Usage

High CPU usually comes from folder watching reacting to a program that keeps changing files, or on Linux from the daemon when .indexes.txt is missing. Rebuild that index with watching off, or create the empty file.

1. **Turn off folder watching for busy folders** — Right-click the affected index and choose Rebuild Index In the indexing dialog untick 'Watch folders for file changes' Update that index manually when needed
2. **Fix the Linux daemon at 100% CPU** — Open your indexes folder, e.g. ~/.docfetcher If there is no file named .indexes.txt, create an empty one: touch ~/.docfetcher/.indexes.txt Restart the daemon or log out and back in
3. **Exclude churning subfolders** — In the indexing dialog add a regex exclusion such as .*/\.svn/.* with Match Against set to Absolute path Rebuild the index

Full guide: https://www.tryorbye.com/products/docfetcher/issues/high-cpu-usage

### DocFetcher Index Not Updating

The DocFetcher daemon only flags changed folders; the actual update runs the next time DocFetcher starts. Open DocFetcher, update indexes manually, or schedule DocFetcher --update-indexes.

1. **Update manually** — Right-click the index in the Search Scope pane Choose Update Index; this is much faster than the first build
2. **Schedule updates from the command line** — Run DocFetcher with --update-indexes, e.g. from Task Scheduler or cron On Windows use DocFetcher.bat (moved up from misc) instead of DocFetcher.exe if you want to see console output
3. **Keep watching on** — Rebuild the index with 'Watch folders for file changes' ticked Leave DocFetcher running, or make sure the daemon starts at login
4. **Restore the original drive letter** — For external drives, assign the same letter in Disk Management as when the index was created Opening and previewing work again once the letter matches

Full guide: https://www.tryorbye.com/products/docfetcher/issues/index-not-updating

### DocFetcher Not Finding Text in Files

DocFetcher matches whole words, so partial words, part numbers and scanned PDFs often return nothing. Use wildcards, check the file type is indexed, and update or rebuild the index.

1. **Use wildcards and phrases** — Add * for partial words: docfetch* Use ? for a single character: docf?tcher Put exact sequences in quotes: "invoice 2024"
2. **Switch the analyzer for codes and IDs** — Open the indexing dialog for the folder Under Advanced Settings choose the Analyzer option suited to source code Rebuild the index
3. **Index unsupported or extensionless files** — Add unknown extensions to the plain text list in the indexing dialog For files without an extension, add a pattern rule with regex [^\.]* , Match Against Filename and Action Detect mime type For files with the wrong extension, add a rule like .*\.doc with Detect mime type
4. **Check for scanned PDFs** — Open the PDF and try to select text If you can't, run it through OCR software, save it and update the index
5. **Update the index and check scope** — Right-click the index in Search Scope and choose Update Index Make sure the folder's checkbox is ticked in the Search Scope pane

Full guide: https://www.tryorbye.com/products/docfetcher/issues/not-finding-text

### DocFetcher Out of Memory: How to Increase the Memory Limit

DocFetcher runs on Java with a fixed heap limit set by -Xmx in its launcher. Raise it (for example to -Xmx4g on an 8 GB PC) and big indexes stop hanging and crashing.

1. **Windows installed version** — Move misc\DocFetcher.bat up one level into the DocFetcher program folder Open it in a text editor and change -Xmx on the last line, e.g. -Xmx4g Always launch DocFetcher by double-clicking DocFetcher.bat
2. **Linux and macOS** — Open DocFetcher.sh (on macOS inside the .app bundle under Contents/MacOS) in a text editor Change the -Xmx value, e.g. -Xmx4g Start DocFetcher from that script
3. **PortableApps version** — Open App\AppInfo\Launcher\DocFetcherPortable.ini In the CommandLineArguments= line change -Xmx, e.g. -Xmx4g
4. **Linux snap** — Run docfetcher from a terminal The startup message names the config file where the memory setting lives; edit it and restart
5. **Reduce memory pressure** — Index subfolders separately with the + button in the indexing dialog Keep at least 1 GB of free disk space for index files Rebuild any index that crashed while memory was too low

Full guide: https://www.tryorbye.com/products/docfetcher/issues/out-of-memory

### Outlook Won't Start After DocFetcher Indexing

On Windows the DocFetcher daemon can block Outlook after you index Outlook PST mail. Rename docfetcher-daemon-windows.exe, reboot, and update your indexes manually from then on.

1. **Disable the daemon** — Close DocFetcher Open the DocFetcher program folder Rename docfetcher-daemon-windows.exe (e.g. to docfetcher-daemon-windows.exe.off) Reboot Windows and start Outlook
2. **Update mail indexes manually** — With the daemon off, open DocFetcher and right-click the mail index Choose Update Index when you want new mail included
3. **Index a copy instead** — Point DocFetcher at an exported or copied PST rather than the live Outlook data file

Full guide: https://www.tryorbye.com/products/docfetcher/issues/outlook-wont-start

### DocFetcher Crashes With 'Program Died' Error

DocFetcher crashes during indexing are usually a parser choking on one bad file or the Java memory limit being hit. Update to 1.1.27, raise the memory limit, index subfolders separately and rebuild the broken index.

1. **Update to the latest version** — Download DocFetcher 1.1.27 from docfetcher.sourceforge.io/download For portable installs, copy your old conf and indexes folders into the new DocFetcher folder
2. **Raise the memory limit** — Close DocFetcher Edit the -Xmx value in the launcher (see the memory guide), for example -Xmx4g Do not set it above your physical RAM
3. **Rebuild the crashed index** — Right-click the index in the Search Scope pane Choose Rebuild Index; a partial index from a crash may be broken even after you fix the cause
4. **Index subfolders one at a time** — In the indexing dialog, use the + button at the top right to queue subfolders One failing folder then no longer kills the whole run
5. **Re-save or exclude problem files** — Note the file named in the error or last processed Re-save old Office files in a newer format, for example with LibreOffice Or exclude it with a regex rule in the indexing dialog's pattern table

Full guide: https://www.tryorbye.com/products/docfetcher/issues/program-died-crash

### DocFetcher 'Requires a Java Runtime' Error

Older DocFetcher builds (1.1.25 and earlier) and the PortableApps version need a separate Java. Install 1.1.26 or newer, which bundles Java, or fix the CommonFiles\Java folder for the portable build.

1. **Upgrade to 1.1.26 or newer** — Download the latest release from docfetcher.sourceforge.io/download It bundles its own Java runtime, so no separate install is needed Copy conf and indexes from an old portable install to keep your data
2. **Fix the PortableApps layout** — Put the CommonFiles folder beside DocFetcherPortable, not inside it Make sure CommonFiles contains a folder named Java, even when using jPortable 64
3. **Older versions only: install the right Java** — Install a 64-bit Java runtime On Apple Silicon Macs, older DocFetcher needed the x64 Java runtime, not ARM64

Full guide: https://www.tryorbye.com/products/docfetcher/issues/requires-java-runtime

### DocFetcher Not Searching Scanned PDFs

DocFetcher has no OCR and only reads a PDF's text layer, so scanned PDFs show an empty preview and never match. OCR them first, then update the index.

1. **Confirm it is a scan** — Open the PDF in a viewer Try to select a sentence; if nothing highlights, it is image-only
2. **Add a text layer with OCR** — Run the PDFs through OCR software that saves a searchable PDF Replace the originals in the indexed folder
3. **Re-index the folder** — Right-click the index in Search Scope and choose Update Index Search again; the preview should now show text

Full guide: https://www.tryorbye.com/products/docfetcher/issues/scanned-pdf-not-searchable

### DocFetcher Won't Start or Open

If DocFetcher does nothing when launched, disable the startup manual and HTML preview in settings-conf.txt, then try the script launcher to see the error. Old versions also fail without a matching 64-bit Java.

1. **Turn off the startup manual and HTML preview** — Close DocFetcher Open settings-conf.txt in the conf folder: C:\Users\<you>\AppData\Roaming\DocFetcher\conf (Windows), ~/.docfetcher/conf (Linux/macOS) or <app folder>\conf (portable) Add the lines ShowManualOnStartup = false and PreferHtmlPreview = false Optionally add HotkeyEnabled = false, then start DocFetcher
2. **Launch from the script to see the error** — Windows: move misc\DocFetcher.bat into the DocFetcher folder and run it from a command prompt Linux: chmod +x DocFetcher.sh and run ./DocFetcher.sh in a terminal macOS: cd into DocFetcher.app/Contents/MacOS in Terminal and run the executable there
3. **Update to 1.1.26 or newer** — Install the latest release, which bundles its own Java runtime Note it is 64-bit only: Windows 7 SP1+, macOS 11+, Linux with GTK 3
4. **Update graphics drivers** — If startup fails right after a GPU driver update, install a newer or older driver version

Full guide: https://www.tryorbye.com/products/docfetcher/issues/wont-start

## Common problems

- **DocFetcher crashes with 'program died' while indexing** (reliability): The bug tracker is full of 'program died' and Java exception reports, many triggered while parsing odd Office, PDF or image files. The FAQ says most indexing errors come from third-party parsers (Apache POI, PDFBox) and that a crashed index should be rebuilt.
- **Runs out of memory on large document collections** (performance): Large indexes hang or crash until the Java memory limit (-Xmx) is raised by editing a launcher file. Users on AlternativeTo describe needing bigger heap settings or disabling previews to keep it stable.
- **DocFetcher not finding words that are in the file** (usability): Searches match whole tokens, so part of a word or long number strings often return nothing unless you use wildcards. Scanned PDFs without a text layer, unsupported extensions and stale indexes also cause missed hits.
- **Why is DocFetcher indexing so slow?** (performance): The first index has to open and extract text from every file, which users say can take hours or even days on big collections. There is no progress bar because counting files in advance would slow it down further.
- **Fiddly setup: config files instead of settings** (onboarding): Raising memory, fixing deep-folder errors, changing language or index location all mean editing .bat, .sh, .ini or .txt files by hand. Reviewers say getting it working well takes trial and error.
- **Free version gets fixes, not features** (support): The FAQ says feature requests are not planned for DocFetcher and development continues in the paid DocFetcher Pro. The SourceForge bug tracker has hundreds of open tickets, and a long-time user called it unmaintained.
- **Scanned PDFs and images are not searchable** (usability): DocFetcher reads the text layer only. Image-only PDFs show an empty preview and never match, so they need OCR in another tool first.
- **Outlook won't start after indexing PST mail** (integrations): The FAQ documents a Windows conflict where the DocFetcher daemon holds Outlook data files so Outlook refuses to open. The fix is renaming the daemon executable and updating indexes manually.
- **High CPU usage from folder watching and the daemon** (performance): When another program keeps changing files in an indexed folder, folder watching keeps DocFetcher busy. On Linux the daemon can sit at 100% CPU if the .indexes.txt file is missing.
- **Older versions need a separate Java install** (onboarding): Up to 1.1.25 you had to install Java yourself (64-bit, and x64 Java even on Apple Silicon Macs). From 1.1.26 a runtime is bundled, but old portable setups still throw 'requires a Java Runtime' errors.
- **Plain-text previews and limited interface** (usability): Previews are text only (HTML aside), there is no hit-count column, and folder names are not searchable in the free version. Users describe the GUI as limited compared with newer tools.
- **Not a filename finder like Everything** (usability): People expecting instant filename search find DocFetcher slow and heavy. It only searches folders you index, which is the point of a content search tool but surprises users coming from Everything.

## What users like

- **Free and open source for any use**: DocFetcher is free under the Eclipse Public License, with no ads, accounts or usage limits.
- **Fully offline and private**: Indexes stay on your disk and nothing goes to the cloud, which reviewers value when employers restrict cloud tools.
- **Searches return in milliseconds once indexed**: Text is extracted once into a Lucene index, so queries are near instant and index updates are much faster than the first build.
- **Reads many formats, including PST and archives**: Office, PDF, Outlook PST, EPUB, HTML, RTF, CHM, Visio, SVG plus zip, 7z, rar and tar archives are searched out of the box.
- **Portable version you can carry anywhere**: The portable build keeps indexes beside the app, so you can move a fully indexed repository between drives, PCs or a cloud folder.
- **Powerful query syntax**: Supports wildcards, phrases, boolean operators, proximity search and filename: queries, plus a Python scripting API from 1.1.20.

## Pricing

- **DocFetcher (free)**: $0.00 (free) — hidden costs: None, but new features only go into the paid Pro edition
- **DocFetcher Pro demo**: $0.00 (free)
- **DocFetcher Pro 1.x (one platform)**: $40.00 (one_time) — hidden costs: New features not included; the next major version is a new purchase. Organizations need one copy per computer
- **DocFetcher Pro 1.x (two-platform bundle)**: $60.00 (one_time) — hidden costs: Same major-version rule as single licence
- **DocFetcher Pro 1.x (all three platforms)**: $90.00 (one_time) — hidden costs: Same major-version rule as single licence

## Who should and shouldn't use it

- **Researchers and students with large PDF libraries** — Good fit: Free, fast content search across thousands of text-based PDFs and documents.
- **Lawyers and consultants handling sensitive files** — Good fit: Everything stays offline, and PST plus Office formats are covered.
- **Linux and macOS users** — Good fit: One of few free cross-platform content search tools; runs on all three systems.
- **People who want instant filename search** — Avoid: Everything or WizFile find files by name instantly without building content indexes.
- **Teams needing shared search** — Depends: Possible with shared portable indexes, but it is a hack; a web interface needs paid DocFetcher Server.
- **Users with scanned paper archives** — Avoid: No OCR, so image-only PDFs are invisible to search.
- **Non-technical users** — Depends: Works out of the box for small sets, but memory and error fixes mean editing config files.
- **Admins indexing 100 GB+ or network shares** — Depends: Works if you raise memory and index subfolders separately; expect long first indexes and occasional rebuilds.

## Alternatives

- **AnyTXT Searcher** (https://www.tryorbye.com/products/anytxt): Free Windows full-text search that indexes automatically with a lighter feel; trade-off: closed source, Windows only, and one independent test found it missed many hits.
- **Recoll**: Free open-source full-text search on Xapian with richer indexing and filtering options, often named the top DocFetcher alternative; trade-off: dated UI and heavy first index.
- **Agent Ransack** (https://www.tryorbye.com/products/agent-ransack): Free Windows content search with no index to build or break; trade-off: every search scans live, so big folders are slower.
- **UltraSearch** (https://www.tryorbye.com/products/ultrasearch): Fast Windows search that reads the NTFS file table for names and can also search content; trade-off: Windows only, content search is not indexed.
- **Everything** (https://www.tryorbye.com/products/everything): Instant filename search on Windows with tiny resource use; trade-off: content search is slow and unindexed, so it complements rather than replaces DocFetcher.

## FAQ

### Is DocFetcher free?

Yes. DocFetcher is free and open source under the Eclipse Public License, for personal and commercial use. The separate DocFetcher Pro is paid (from €40 one-time per platform) and gets the new features.

### Is DocFetcher worth it?

For free, private full-text search across PDFs, Office files and Outlook mail, yes. Expect a slow first index and some config-file tweaking for big collections. If you only need filename search, use Everything instead.

### Is DocFetcher safe?

It is open source, runs offline and keeps its index on your own disk. Download it only from the official docfetcher.sourceforge.io site or the DocFetcher Pro site to avoid repackaged installers.

### Does DocFetcher need Java?

Not anymore. Since version 1.1.26 DocFetcher bundles its own Java runtime. Version 1.1.25 and older needed a separately installed 64-bit Java.

### Why is DocFetcher not finding my text?

Usually the word is part of a longer token (use wildcards like docfetch*), the PDF is a scan with no text layer, the file type is not indexed, or the index is out of date. Update or rebuild the index and check the file types in the indexing dialog.

### Can DocFetcher search scanned PDFs?

No. It reads the text layer only and has no OCR. Run scanned PDFs through OCR software first, then re-index the folder.

### How do I increase DocFetcher memory?

Edit the -Xmx value in the launcher: misc/DocFetcher.bat (Windows), DocFetcher.sh (Linux/macOS) or App\AppInfo\Launcher\DocFetcherPortable.ini (PortableApps), for example -Xmx4g. Do not exceed your physical RAM.

### Where does DocFetcher store its index?

Windows: C:\Users\<you>\AppData\Roaming\DocFetcher. Linux: ~/.docfetcher. macOS: /Users/<you>/.docfetcher. Portable: the indexes folder next to the app. Change it in misc/paths.txt.

### What is the difference between DocFetcher and DocFetcher Pro?

Pro is the paid, actively developed edition with a bundled runtime, folder search, a checkbox for extensionless files, improved PDF and Mobi extraction and signed macOS builds since 1.22. The free version gets maintenance releases only.

### How much does DocFetcher Pro cost?

€40 one-time for one platform, €60 for two and €90 for Windows, macOS and Linux. The licence covers version 1.x with fixes until one year after 2.0 ships; new features and the next major version are not included. A free demo shows 5 results per search.

### Does DocFetcher work on Mac and Linux?

Yes. Version 1.1.27 supports 64-bit Windows 7 SP1+, macOS 11+ and 64-bit Linux with GTK 3, with a snap package on Linux.

### Does DocFetcher search network drives?

Yes, you can index network folders, but first indexes over the network are slow and memory heavy. Unplugged or remapped drives can still be searched, but files only open again under the original drive letter.

### What are the best DocFetcher alternatives?

Recoll (free, open source, more indexing options), AnyTXT Searcher (free, Windows), Agent Ransack (no index needed) and Everything for filename search. DocFetcher Pro is the paid upgrade path.

---
Try or Bye aggregates problem patterns from user reviews, forums, and app stores. Methodology: https://www.tryorbye.com/methodology