Where Does KeePassXC-Browser Store Settings and Keys?
KeePassXC-Browser keeps its own settings in extension storage while passwords stay in your KeePassXC database file.
Last updated
KeePassXC-Browser splits storage three ways. Extension settings and site associations sit in per-profile extension storage. The browser link runs through a native messaging proxy. Passwords stay in the KeePassXC database file wherever you keep it.
Migrations trip on the middle layer. A fresh proxy install needs re-authorization inside KeePassXC before filling works again. Move the .kdbx first, reconnect second, import settings last.
Where KeePassXC-Browser stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile)
Settings and associations per profile. Re-authorize the browser connection in KeePassXC after moving. Passwords remain in your .kdbx wherever it lives.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile)
Same extension model on Mac. Native host runs through the KeePassXC install. Reconnect and confirm the association code on first fill.
~/.config/google-chrome/Default/Extensions (per profile)
Chromium profiles under ~/.config and Firefox under ~/.mozilla. Proxy ships with the KeePassXC package. Database file moves separately by design.
Frequently asked questions
How do I move KeePassXC-Browser to a new computer?
Reconnect it to the database on the new machine and re-authorize the browser connection. Extension settings import from the options export. The .kdbx file itself moves by your own sync method.
Does the extension store my passwords?
No. The extension holds settings and the connection association only. Passwords live in the .kdbx database that KeePassXC opens. Back up that file; the extension data is secondary.
Notice an outdated path? Let us know.