Where Does Thorium Reader Store Books?
Where Thorium Reader keeps imported books, settings, and cache on each OS, and how the Store install differs.
Last updated
Thorium Reader copies every imported ebook into its own app data folder, so deleting the original file never harms the library. Publications sit in a publications subfolder beside the config, parser cache, and Chromium data. The exact root moves per OS and per installer.
Windows has the twist: the GitHub installer uses Roaming while the Store build redirects under Local Packages. Linux follows XDG config home. Thorium 3.5 added an extra storage directory for new imports, which finally lets large libraries live off the system disk.
Where Thorium Reader stores this, by platform
%APPDATA%\EDRLab.ThoriumReader\publications
Holds publications plus config, parser cache, and Chromium data. The Store build instead nests the same tree under Local\Packages with its Store ID. Newer versions support an additional storage folder for future imports off the system disk.
~/Library/Application Support/EDRLab.ThoriumReader/publications
Same publications layout as Windows under Application Support. Move books between machines by copying this folder and reopening them. Symlink relocation works but risks database pruning on broken paths.
~/.config/EDRLab.ThoriumReader/publications
Follows XDG config home, defaulting under ~/.config. Self-built instances may use a publications-dev folder instead. The additional storage setting from 3.5 applies here exactly as elsewhere.
Frequently asked questions
how do I move my Thorium library
Copy the publications folder to the new machine at the matching OS path, then open the books in the fresh install. That moves the files; reading positions travel separately. The whole app data folder can move too, but mind the Chromium cache bulk.
can I store Thorium books on another drive
Open Settings and configure an additional storage directory, and future imports land there while old books stay put. Advanced users can relocate existing files by hand with symlinks, at the risk of database pruning if paths break. The app never moves old files by itself.
books missing after a Store install
Look under the Local Packages path with the Store ID instead of Roaming. The GitHub installer uses the plain Roaming path. Both hold the same publications layout inside, so check both before assuming books are gone.
Notice an outdated path? Let us know.