Where Does gThumb Store Catalogs and Settings?
Where gThumb keeps its config, cache, and catalog folders on Linux, and how settings transfer via dconf.
Last updated
gThumb splits state three ways on Linux: config files, thumbnail cache, and catalog data under their XDG homes, with preferences additionally in dconf. Flatpak builds nest the same trio under their sandbox ID. Clearing cache alone fixes most thumbnail weirdness.
Catalogs deserve backup priority since they hold organization work. Settings transfer through dconf dump commands rather than file copies. Treat cache as disposable, catalogs as precious, and config as reproducible. That priority never misleads.
Where gThumb stores this, by platform
~/.config/gthumb
Config home for settings files with catalogs and data under local share. Preferences also live in dconf paths for dump and load transfers. Flatpak nests everything under its sandbox ID. Clear cache alone for thumbnail repairs.
Frequently asked questions
how do I move gThumb to a new machine
Dump dconf settings for the gThumb paths and copy config, catalog, and data folders with the app closed. Thumbnails rebuild from cache clearing when stale. Flatpak trees move as one sandbox folder instead.
thumbnails blank or stale, how to fix
Close the app and clear only the cache directory to force fresh thumbnails. Settings and catalogs survive a cache wipe untouched. Blank thumbs after upgrades usually yield to this exact step.
how do I transfer preferences only
Use dconf dump and load round-trips for the gThumb schema paths. File copies move catalogs and data; dconf moves preferences. Both halves matter for a faithful migration.
Notice an outdated path? Let us know.