FAQ

What platforms does File Hunter run on?

File Hunter runs on macOS, Linux, and Windows (WSL recommended). It is a Python web application — any system that runs Python 3.10+ and has a browser can use it. It runs well on Raspberry Pi and other ARM devices.

How many files can it handle?

File Hunter has been tested with production catalogs containing over ten million files. The UI uses lazy tree loading, paged file lists, and an in-memory stats cache to stay responsive at scale. SQLite in WAL mode handles concurrent reads and writes efficiently.

Can I browse files when the drive is disconnected?

Yes. The full catalog — file names, paths, sizes, hashes, tags, descriptions, and folder structure — persists in the local SQLite database. When a drive is disconnected, its locations go offline but remain fully browsable and searchable. Only operations requiring physical file access (preview, download, move, delete) are blocked until the drive is reconnected.

What is the difference between free and Pro?

The free version includes everything you need for local file management: multi-location catalog, offline browsing, duplicate detection, consolidation, merge, storage treemap, search, upload, scheduled scans, themes, auth, and more. It is MIT-licensed and will stay free forever.

File Hunter Pro adds remote agent support: install agents on other machines to catalog their files into your central instance. Features include content streaming, remote scanning, cross-machine deduplication, and live agent status. Pro is a one-time purchase with lifetime updates.

How does the agent system work?

A lightweight Python agent runs on a remote machine and connects to your File Hunter server over WebSocket. The agent exposes its configured directories as locations in your catalog. The server triggers scans, and the agent hashes files locally and sends results back. Content (images, video, documents) is streamed on demand through the server with range request support.

Is my data safe?

File Hunter runs entirely on your own hardware. No data leaves your machine or network. The catalog is a local SQLite file. There are no cloud services, no telemetry, no analytics. Consolidation never silently deletes files — it creates .moved stubs and .sources audit files so you can always trace where files went.

Can I run it on a headless server?

Yes, that is one of the primary use cases. File Hunter is a web application — it runs on the server and you access it from any browser on any device on the network. There is no desktop GUI, no Electron, no X11 required.

What happens if a scan is interrupted?

If the server stops during a scan, the progress up to that point is preserved in the database. Restart the server and rescan — it picks up incrementally, skipping files that were already hashed.

Can multiple users access it at the same time?

Yes. Multiple browser sessions can be open simultaneously. All mutations (scans, uploads, deletes, moves) are broadcast via WebSocket to every connected client in real time.

How do I back up my catalog?

Copy the file_hunter.db file. It is a standard SQLite database. For a consistent backup while the server is running, use SQLite’s .backup command or simply copy the file (WAL mode ensures read consistency).

How do I reset everything?

Delete file_hunter.db and restart the server. This removes all catalog data, users, and settings. Your actual files on disk are never affected. If you used --demo, also delete the testdata/ directory.