Tool · last scan Nov 2026
DocFetcher Problems & Issues
Free open-source desktop search that finds text inside your documents on Windows, macOS and Linux
VERDICT TRY WITH CAUTION
64/100
Try with caution
- signals
- 12
- sources
- 30
- known errors
- 10
// answer first
Should you use DocFetcher?
Try with cautionDocFetcher 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.
Top problems
- DocFetcher crashes with 'program died' while indexing
- Runs out of memory on large document collections
- DocFetcher not finding words that are in the file
Good for
- Researchers and students with large PDF libraries
- Lawyers and consultants handling sensitive files
- Linux and macOS users
Avoid if you are
- People who want instant filename search
- Users with scanned paper archives
Common alternatives:
AnyTXT Searcher, Recoll,
Agent Ransack
score breakdown
- Pricing
- 92Pricing score 92 of 100
- Usability
- 55Usability score 55 of 100
- Performance
- 62Performance score 62 of 100
- Support
- 35Support score 35 of 100
- Reliability
- 55Reliability score 55 of 100
- Onboarding
- 50Onboarding score 50 of 100
- Security
- 80Security score 80 of 100
- Integrations
- 55Integrations score 55 of 100
// score breakdown, 0-100
- Pricing
- 92Pricing score 92 of 100
- Usability
- 55Usability score 55 of 100
- Performance
- 62Performance score 62 of 100
- Support
- 35Support score 35 of 100
- Reliability
- 55Reliability score 55 of 100
- Onboarding
- 50Onboarding score 50 of 100
- Security
- 80Security score 80 of 100
- Integrations
- 55Integrations score 55 of 100
how these scores were set
Free, private and fast once the index is built, but large indexes crash without memory tweaks, setup is fiddly, new features go to the paid Pro edition and support is a forum plus an old bug tracker.
Overview
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.
- company
- DocFetcher Development Team
- founded
- 2007
- website
- docfetcher.sourceforge.io
DocFetcher Not Working? Common Errors & Fixes
10 entries// step-by-step fixes for the errors users hit most
- E-01DocFetcher Crashes With 'Program Died' ErrorDocFetcher 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.
- E-02DocFetcher Out of Memory: How to Increase the Memory LimitDocFetcher 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.
- E-03DocFetcher Won't Start or OpenIf 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.
- E-04DocFetcher Not Finding Text in FilesDocFetcher 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.
- E-05DocFetcher Not Searching Scanned PDFsDocFetcher 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.
- E-06DocFetcher 'Folder Hierarchy Is Too Deep' ErrorThis 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.
- E-07DocFetcher High CPU UsageHigh 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.
- E-08DocFetcher Index Not UpdatingThe 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.
- E-09Outlook Won't Start After DocFetcher IndexingOn 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.
- E-10DocFetcher 'Requires a Java Runtime' ErrorOlder 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.
Try it: a launcher with snippets and clipboard history
A hands-on sandbox of how DocFetcher-style tools work, including where users run into trouble. Simplified illustration, not the real DocFetcher app. Nothing is saved.
SANDBOX · docfetcher LIVE, NOTHING SAVED
Our team built this sandbox from scratch. Want a real DocFetcher-style tool built around how you work?
Get a quote// We build software. Any software.
Have an idea for an app? We'll build it.
We're a small team of developers who build custom software fast. Not just tools like DocFetcher: web and mobile apps, games, desktop software, AI tools, internal tools: whatever you have in mind. 50+ custom products built for clients so far, and we run our own products too: booking platforms, games, learning apps. See our work
- Web apps & SaaS
- Mobile apps (iOS & Android)
- Games
- Desktop software
- AI tools & automations
- Internal tools & dashboards
- Client portals & booking
- Your own version of any tool
- ✓ Free 15-min call to scope it
- ✓ Price agreed up front
- ✓ Your data, your code
Signals & Issues
12 signals · sorted by impact// patterns extracted from real user feedback, not raw reviews
DocFetcher crashes with 'program died' while indexing✓ verified
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.
reported 7xnegativevia Other (3)scaling breaks
impact7/10
Runs out of memory on large document collections✓ verified
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.
reported 7xnegativevia Other (3)scaling breaks
impact7/10Why is DocFetcher indexing so slow?✓ verified
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.
reported 6xnegativevia Other (3)expectation mismatch
impact5/10High CPU usage from folder watching and the daemon✓ verified
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.
reported 4xnegativevia Other (2)workflow failure
impact4/10
DocFetcher not finding words that are in the file✓ verified
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.
reported 6xnegativevia Other (3)workflow failure
impact6/10Scanned PDFs and images are not searchable✓ verified
DocFetcher reads the text layer only. Image-only PDFs show an empty preview and never match, so they need OCR in another tool first.
reported 5xnegativevia Other (2)workflow failure
impact5/10Plain-text previews and limited interface✓ verified
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.
reported 4xnegativevia Other (2)expectation mismatch
impact3/10Not a filename finder like Everything✓ verified
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.
reported 4xnegativevia Other (2)user type mismatch
impact3/10
Fiddly setup: config files instead of settings✓ verified
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.
reported 6xnegativevia Other (3)expectation mismatch
impact5/10Older versions need a separate Java install✓ verified
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.
reported 4xnegativevia Other (3)migration pain
impact4/10
Free version gets fixes, not features✓ verified
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.
reported 5xnegativevia Other (3)support breakdown
impact5/10
Outlook won't start after indexing PST mail
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.
reported 3xnegativevia Otherworkflow failure
impact6/10
What Users Love
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 Plans
- ✓Full-text index and search
- ✓Windows, macOS, Linux
- ✓Portable version
- ✓Python scripting API
Limitations: No new features, plain-text previews, no folder-name search, memory limit set by editing launcher files, no OCR, forum-only support
- ✓All Pro features
- ✓No time limit
Limitations: Shows only 5 results per search
- ✓Perpetual license for 1.x
- ✓Bugfixes and support until one year after 2.0
- ✓Bundled Java runtime
- ✓Folder search
Limitations: 64-bit only, Windows 7 SP1+, macOS 11+, Linux GTK 3
- ✓Two of Windows, macOS, Linux
- ✓Perpetual license for 1.x
- ✓Windows, macOS and Linux
- ✓Perpetual license for 1.x
Features
Search
- Full-text content search
Lucene index of chosen folders
- Filename search
filename: prefix; folder names not indexed in free version
Formats
- Outlook PST indexing
- Archive search (zip, 7z, rar, tar)
- OCR for scanned PDFs
Run OCR elsewhere first
Deployment
- Portable version
- Web interface / multi-user
Only in paid DocFetcher Server
Indexing
- Folder watching / background daemon
Daemon only flags changes; updates run on next start
Integrations
- Python scripting API
Since 1.1.20
Who Should Use This?
Good Fit
Researchers and students with large PDF libraries
Free, fast content search across thousands of text-based PDFs and documents.
Lawyers and consultants handling sensitive files
Everything stays offline, and PST plus Office formats are covered.
Linux and macOS users
One of few free cross-platform content search tools; runs on all three systems.
Neutral
Teams needing shared search
Possible with shared portable indexes, but it is a hack; a web interface needs paid DocFetcher Server.
Non-technical users
Works out of the box for small sets, but memory and error fixes mean editing config files.
Admins indexing 100 GB+ or network shares
Works if you raise memory and index subfolders separately; expect long first indexes and occasional rebuilds.
Avoid
People who want instant filename search
Everything or WizFile find files by name instantly without building content indexes.
Users with scanned paper archives
No OCR, so image-only PDFs are invisible to search.
Regret Patterns
Common buyer's remorse scenarios reported by users.
Users point it at an entire drive, wait hours, and the index dies on one bad file or memory limit, forcing a full rebuild.
People expecting it to find text in scanned contracts or receipts discover it has no OCR.
Users requesting improvements learn the free edition is in maintenance mode and new work goes into the paid Pro.
Memory, deep folders, language and index location all require hand-editing launcher files, which non-technical users give up on.
Users wanting fast filename search find DocFetcher heavy and slow for that job and switch back.
When It Breaks Down
Scenarios where this product tends to fail users.
Default memory runs out and the index can crash; the FAQ advises max memory, queuing subfolders separately and rebuilding after any crash.
Indexing stops with 'Folder hierarchy is too deep' until the Java stack size (-Xss) is raised in the launcher.
Folder watching keeps re-triggering, pushing CPU high; turning off watching for that index fixes it.
The daemon can stop Outlook from starting until its executable is renamed.
Search still works but files no longer open or preview until the original drive letter is restored.
Tokenization splits on symbols and whole words, so partial strings and IDs are missed without wildcards or the source-code analyzer.
Alternatives Users Switch To
Recoll
8x mentionedFree 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.
AnyTXT Searcher
7x mentionedFree 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.
Agent Ransack
6x mentionedFree Windows content search with no index to build or break; trade-off: every search scans live, so big folders are slower.
Everything
6x mentionedInstant filename search on Windows with tiny resource use; trade-off: content search is slow and unindexed, so it complements rather than replaces DocFetcher.
UltraSearch
4x mentionedFast Windows search that reads the NTFS file table for names and can also search content; trade-off: Windows only, content search is not indexed.
Frequently Asked Questions
See how DocFetcher compares in our Best Launcher Software rankings, or calculate costs with our Budget Calculator.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usWork at DocFetcher or spotted something outdated? Suggest a correction — we verify every change against public sources. See our methodology.