Where Does UniGetUI Store Settings and Data?
UniGetUI keeps settings and caches in %LOCALAPPDATA%\UniGetUI. Package backups export separately to files you choose.
Last updated
UniGetUI stores its own state under %LOCALAPPDATA%\UniGetUI: settings, caches, operation history, and scheduler data. Installed and nominally portable builds share that location; only explicit portable mode relocates data next to the executable. A GitHub issue trail exists precisely because users expected otherwise.
Package lists are separate artifacts. Backups export to local files you place anywhere (with optional timestamping and retention), or sync to a secret GitHub Gist for one-sign-in restores. That separation is deliberate: settings describe how UniGetUI behaves, backups describe what to install. Copy both for a full move, since each alone restores half the setup.
Where UniGetUI stores this, by platform
%LOCALAPPDATA%\UniGetUI
Settings, caches, history, scheduler state. Portable zips still land here unless portable mode is on. Package-list backups export separately to user-chosen files or a secret Gist.
Frequently asked questions
how do i migrate unigetui to a new pc
Export a package backup from the app (optionally timestamped, optionally synced to a secret Gist) and save %LOCALAPPDATA%\UniGetUI for settings. New machine: install UniGetUI, import the backup, and let it pull from Winget, Scoop, Chocolatey, and the rest.
is unigetui portable really portable
Portable means no installer, not no footprint. Zip builds still write settings to the user profile unless portable mode is enabled to keep data beside the executable. Check which mode you run before assuming the folder is self-contained.
Notice an outdated path? Let us know.