KeePassXC-Browser
An open-source extension that fills in logins from your KeePassXC desktop app.
Before you install: this extension does nothing on its own. You must have the KeePassXC desktop app installed and running, with browser integration turned on.
Why it's a strong pick
Your passwords stay in a KeePassXC database on your own computer, and this extension lets Chrome use them. It is open source under GPL v3, and its code is public on GitHub. It uses Manifest V3, Chrome's current extension format. Its latest release came in September 2026. It is free, and it talks to the local app, not to a cloud service.
What it does
KeePassXC-Browser connects your browser to the KeePassXC desktop password manager through native messaging. When you open a login page, it can fill in your details from your KeePassXC database. The KeePassXC Team makes it. There are versions for Firefox, Chrome and Chromium, and Edge.
Key features
- Autofill. Fill logins on websites from your KeePassXC database.
- Context menu. Use the right-click menu to fill fields.
- Password generator. Create a new password from the browser.
- HTTP Basic Auth. It handles sites that ask for a browser login box.
- Default password manager. An optional permission lets it take over that role.
- Passkey scripts. The manifest includes passkeys scripts.
Who it's for
It suits people who keep passwords in a local KeePassXC database and want browser autofill. If you want a hosted password service that syncs on its own, look at the other picks in our password managers guide.
What permissions does KeePassXC-Browser ask for?
Its manifest asks for activeTab, clipboardWrite, contextMenus, cookies, nativeMessaging, notifications, offscreen, storage, tabs, webNavigation, webRequest and webRequestAuthProvider. Privacy is optional. It also asks for access to all sites and needs Chrome 124 or newer. The README says nativeMessaging is for communication with KeePassXC, and storage keeps settings locally, never synced.
What do I need before it works?
You need the KeePassXC desktop app, version 2.3.0 or later, installed and running. Browser integration must be switched on in KeePassXC. The extension then connects to the app. If KeePassXC is closed or locked away, the extension has nothing to fill.
What about privacy?
The README says the extension's settings are always stored locally and never synced. It has no other privacy statement that we could read. We could not read the developer's privacy policy when we checked; read it before installing. Your passwords live in your KeePassXC database, not in the extension.
Why does it need so many permissions?
The README explains several. NativeMessaging is for talking to KeePassXC. Cookies is for Public Suffix List access. WebRequest is for HTTP Basic Auth. These are the developer's own explanations, so read the full table in the README if you want the rest.
FAQ
Is it free? Yes.
Does it work in other browsers? There are Firefox, Chrome and Chromium, and Edge versions.
Does it store my passwords? Your passwords stay in your KeePassXC database. The README says the extension's settings are stored locally and never synced.
Good to know
Keep KeePassXC open while you browse, or autofill will stop. Back up your database file on its own, since there is no cloud copy unless you make one. Check that browser integration is enabled for Chrome in KeePassXC before you blame the extension.
Other password managers to compare
KeePassXC-Browser is one of our picks in the password managers guide. See Bitwarden and 1Password and Passbolt and authenticator.sh 2FA and Psono in the same guide.
This is a third-party extension, not built or maintained by Xplorekit. We link to the official Chrome Web Store listing — install and permissions are entirely between you and the extension's own publisher.