Where Does Gpick Store Config and Palettes?
Gpick keeps settings in its .config folder on Linux with custom converters as user_init.lua. Palettes save to user-chosen files.
Last updated
Gpick documents its folder better than its files. The config directory under XDG config is confirmed with custom converters as user_init.lua inside. Settings persist through a dynamic system in the same tree.
Palettes refuse a fixed home entirely, saving wherever chosen across half a dozen formats. No canonical settings filename is verified, which this post states instead of filling. Copy the folder whole and record palette spots separately.
Where Gpick stores this, by platform
~/.config/gpick
Settings tree with custom converters as user_init.lua. No single canonical settings filename verified, so the directory is the quotable unit. Palettes save to user-chosen files in many formats.
Frequently asked questions
How do I back up Gpick settings?
Copy ~/.config/gpick whole with the app closed. Settings live in that tree through its dynamic variable system while user_init.lua carries custom converters. Palettes travel separately from their saved locations.
Where are my Gpick palettes?
Anywhere chosen at save time. Native palettes plus GIMP, ASE and CSS formats all write to user-picked files with no fixed home. Resource defaults ship under system share with data-home overrides.
What is the main Gpick settings file?
It could not be verified. No single canonical settings filename is documented inside the config folder, so this post quotes the directory plus the converter file. Folder copies dodge the gap.
Notice an outdated path? Let us know.