Where Does Recoll Store Its Index and Config?
Where Recoll keeps its index configuration, the Xapian search database, and GUI preferences on each OS..
Last updated
Recoll organizes search around a configuration directory holding recoll.conf plus a xapiandb index subfolder. Unix systems default under home while Windows uses LocalAppData. GUI preferences live apart in Qt standard storage.
Environment variables and flags relocate the whole tree for multi-index setups. The index itself dwarfs config in size, so dbdir splits it onto roomier disks. Back up config for rules and the index for speed; either rebuilds from the other plus time. GUI prefs travel separately.
Where Recoll stores this, by platform
~/.recoll
Default tree with recoll.conf and xapiandb index inside. GUI prefs live separately in Qt storage. Relocate with RECOLL_CONFDIR or -c flag. Split bulky index data out with dbdir when home fills.
%LOCALAPPDATA%\Recoll
Same config plus index layout under LocalAppData. GUI preferences follow Qt conventions beside it. Multiple indexes each get their own folder through env or flags.
~/.recoll
Mirrors the Unix default tree on Mac. The GUI preferences path follows Qt on macOS too. Treat the index as disposable cache and the conf as the precious part.
Frequently asked questions
how do I move a Recoll index
Copy the config directory with indexing stopped to move both settings and index. The xapiandb subfolder holds the searchable data; recoll.conf holds the rules. Point RECOLL_CONFDIR at the copy on the new machine when paths differ.
index too big for home, what now
Set dbdir in recoll.conf to park the bulky Xapian data on a bigger disk while config stays home. Indexing speed and disk hunger both live there. GUI preferences stay separate in the Qt config location.
how do I run multiple indexes
Point RECOLL_CONFDIR or the -c flag at a fresh folder per collection. Each gets its own conf and xapiandb. The default tree indexes home; extras cover mounts, archives, or mail spools.
Notice an outdated path? Let us know.