Where Does Authenticator Store TOTP Codes?
Where GNOME Authenticator keeps codes on Linux, keyring backed storage. Exact folders are covered below.
Last updated
Authenticator is GNOME TOTP with local storage. Your codes live in app data plus keyring entries. There is no account cloud to sign into.
That local design keeps secrets contained. New machines start empty. For keeps, export backup codes after adding accounts. Exact file names shift with releases. Keep exports encrypted, since they unlock every linked service. Copying raw folders alone leaves codes locked behind the old keyring. Check the in app storage readout when sizes look wrong on different releases.
Where Authenticator TOTP stores this, by platform
~/.local/share/authenticator (codes, keyring backed)
Codes live locally with keyring backing and no cloud account. Export backups before wiping. Raw folder copies alone leave codes locked.
Frequently asked questions
How do I move Authenticator codes to a new machine?
Export backup codes from settings first, then import on the new machine. Tokens live in the app data plus keyring entries. Reinstalls wipe local codes without an import file. Verify counts before wiping, since missing entries mean missed exports.
Does Authenticator sync online?
No. Authenticator keeps TOTP secrets in local storage backed by the keyring. There is no cloud account to sign into. Treat manual exports as the only backup path. Screenshot QR setup codes too where services allow re enrollment.
Notice an outdated path? Let us know.