LinuxmacOSWindows

Where Does Kid3 Store Settings?

Kid3 keeps tagger settings in kid3rc plus app state nearby, with registry and plist equivalents on Windows and Mac.

Last updated

Kid3 stores settings per platform convention: kid3rc in the XDG config home on Linux with state in the data home, registry keys on Windows, a plist on macOS. A config env var overrides the path everywhere, and portable mode pins an INI beside the app.

Custom import formats and filename-to-tag schemes live in that same config, which makes it the file worth versioning. Tagged music files themselves stay wherever your library lives.

Where Kid3 stores this, by platform

Linux
~/.config/kid3rc

kid3rc with formats and schemes; state in ~/.local/share/kid3/kid3staterc. Override with KID3_CONFIG_FILE; portable mode uses kid3.ini beside the app.

macOS
~/Library/Preferences (Kid3 plist)

Same role via plist preferences. Portable-style INI overrides work the same when a fixed path suits scripts better.

Windows
Registry: HKEY_CURRENT_USER\Software\Kid3

Settings live in the registry rather than a file. Export the Kid3 key to migrate; portable mode with kid3.ini avoids the registry entirely.

Frequently asked questions

How do I migrate Kid3 settings?

Copy kid3rc (and kid3staterc for window state) to the same config paths on the new machine. Import formats and filename schemes travel inside.

How do I reset Kid3 to defaults?

Delete kid3rc with Kid3 closed to restore defaults. Custom import formats live in that file, so export any keepers first.

Notice an outdated path? Let us know.