Where Does PicView Store Settings?
PicView prefers AppData for settings when installed, and its own Config folder in portable mode. How to tell.
Last updated
PicView checks two places for config. Installed copies use AppData. Portable extracts use a Config folder next to the exe when AppData has nothing and the app dir is writable. The AppData copy wins when both exist, so edits to the other copy appear to vanish. Check AppData first before assuming portable mode is live.
That dual logic causes confusion when edits seem to vanish. You changed one copy while the app reads the other. Check AppData first. If it exists, that is the live file regardless of portable intent. Close PicView before copying UserSettings and keybindings between folders. The gallery cache rebuilds on its own, while unknown keys fall back to defaults after a version change.
Where PicView stores this, by platform
%APPDATA%\Ruben2776\PicView\Config\UserSettings.json
Live settings when present: UserSettings.json plus keybindings.json. Takes priority over portable Config. Delete it to switch a copy to portable mode.
Frequently asked questions
How do I force PicView into portable mode?
Delete the AppData copy at Ruben2776 PicView Config. The next launch falls back to the app dir Config if that folder is writable. Keep only one copy to avoid editing the wrong file.
How do I back up PicView settings?
Copy UserSettings.json and keybindings.json between the Config folders with PicView closed. Gallery cache rebuilds itself. Version mismatches reset unknown keys to defaults.
Notice an outdated path? Let us know.