Where Does Gradience Write Its Themes?
Gradience writes its theming into ~/.config/gtk-4.0 and gtk-3.0; deleting those folders reverts everything.
Last updated
Gradience does not keep a theme engine running; it generates CSS into ~/.config/gtk-4.0 (Libadwaita/GTK4) and ~/.config/gtk-3.0 (with adw-gtk3). Presets are just recipes for those outputs, applied through the app or gradience-cli.
That file based design makes reverting trivial and debugging easy. If theming vanishes after reboot, the CSS folders were reset or the Flatpak overrides never persisted, not the preset library.
Where Gradience stores this, by platform
~/.config/gtk-4.0/
Generated gtk.css and assets per toolkit. Flatpak users must grant filesystem overrides or sandboxed apps never see the files. Revert by deleting both folders.
Frequently asked questions
How do I undo Gradience theming completely?
Delete ~/.config/gtk-4.0 and ~/.config/gtk-3.0 (or use Preferences, Theming, Reset per toolkit). That removes every trace Gradience applied, presets untouched.
GTK4 apps themed but GTK3 apps ignored. What is missing?
Install the adw-gtk3 theme plus its Flatpak package, then grant overrides (flatpak override --filesystem=xdg-config/gtk-3.0 or via Flatseal). GTK3 apps cannot see the CSS otherwise.
Notice an outdated path? Let us know.