Where Does Tenacity Store Settings and Macros?
Where Tenacity keeps tenacity.cfg, plugins, and macros on Windows, Linux, and portable installs.
Last updated
Tenacity keeps its whole profile in one folder: %APPDATA%\Tenacity on Windows, ~/.config/tenacity on Linux (plus a Flatpak variant and a Portable Settings option). Preferences, macros, and plugin data all live inside as tenacity.cfg and siblings.
The folder is self contained by design, which makes migration a straight copy. The one rule is to never mix Audacity registry files into it: only the main cfg ports over safely, and even that is officially unsupported. When plugins misbehave, deleting the registry file forces a clean rescan.
Where Tenacity stores this, by platform
%APPDATA%\Tenacity
tenacity.cfg for preferences plus pluginregistry.cfg, macros, and recent files. Create a Portable Settings folder beside the exe to relocate everything for a carry along install. Close the app before copying.
~/.config/tenacity
Same files for AppImage and system packages. Flatpak builds use ~/.var/app/org.tenacityaudio.Tenacity/config instead, so check the sandbox path first. Honors $XDG_CONFIG_HOME when set.
Frequently asked questions
how do i migrate tenacity settings to a new pc
Copy the whole Tenacity settings folder to the same path on the new machine with the app closed (%APPDATA%\Tenacity on Windows). Macros, plugin registry, and preferences travel together. Point a fresh portable install at a copied Portable Settings folder for the same effect.
can i import audacity settings into tenacity
Copy audacity.cfg from the Audacity folder into the Tenacity folder renamed as tenacity.cfg. Copy nothing else: plugin registry files from Audacity break Tenacity plugins. Macros need manual recreation regardless.
where are tenacity plugins registered
In the same settings folder (pluginregistry.cfg and pluginsettings.cfg). Delete pluginregistry.cfg with Tenacity closed to force a rescan; it rebuilds on next launch. The Help > About > Build Information page prints the live folder when in doubt.
Notice an outdated path? Let us know.