KeeWebX — KeePass that runs
in your browser.

KeeWebX is a modern, web-only KeePass client. Open your .kdbx file in any browser — or double-click an HTML file and run it offline. No server, no signup, no install.

Try the demo → Self-host no signup, no installer, no server
KeeWebX showing a vault with colorful tag chips
The included demo vault — open it in one click, no signup.

Why KeeWebX

Runs from a .html file

No server, no Docker, no Node. Extract the release zip, double-click index.html, unlock your database. Browser extension autofill works on file://.

Passkey quick unlock

Unlock with Touch ID, Face ID, Windows Hello, or a YubiKey. WebAuthn PRF derives the master key — no password typing, same security.

KDBX4, TypeScript, 20 deps

ChaCha20 + Argon2id, no legacy crypto. Strict TypeScript. A single monorepo you can audit in an afternoon.

How it compares

KeeWebXBitwarden1PasswordKeePassXC
File formatKDBX4 (own it)ProprietaryProprietaryKDBX4 (own it)
Runs in browserYesExtension onlyExtension onlyNo, desktop only
Server requiredNo (your file, your storage)Yes (their vault or self-host)Yes (their servers)No
SubscriptionFree, MITFree tier + paidRequiredFree, GPL
Passkey unlockYes (WebAuthn PRF)LimitedYesNo
Phone browserYesApp onlyApp onlyNo
Works on file://YesNoNoN/A (native)

Self-host KeeWebX in 10 seconds

Option A — pure local

Download the release, extract, double-click index.html. That's it. All encryption runs in your browser via WebCrypto.

Option B — any static host

python3 -m http.server 8080
# or
bunx serve .

Works on GitHub Pages, S3, Netlify, nginx, Caddy, and anything else that serves a folder of files.

Full self-host guide →

FAQ

Where does my password file go?

Nowhere you don't put it. KeeWebX runs entirely in your browser. By default the file you open stays on your disk; the page loads it locally and decrypts it with WebCrypto. Open the network tab in your browser and watch — there's no upload happening.

Is KeeWebX reading my passwords?

It can't. KeeWebX is the same source as the GitHub release — you can read it, build it yourself, or download the zip and run it offline by double-clicking index.html. There's no server in the unlock path; the master key never leaves the page.

How is KeeWebX different from KeeWeb?

KeeWeb hasn't shipped since 2021. KeeWebX is a fresh fork rewritten in TypeScript (strict mode, ~20 deps vs ~80), KDBX4-only (ChaCha20 + Argon2id, no legacy crypto), one monorepo instead of three, and adds passkey quick unlock, colorful tag chips, and a hi-res site icon picker. Same KDBX file works in both.

What's the catch with KeeWebX?

Web-only by design. There is no Electron desktop app and there will not be one. If you need a native client, KeePassXC is excellent. If you live in the browser anyway and want passkey unlock and a real KDBX4 file you can move between machines, KeeWebX is for you.

How do I move my vault between devices?

Today: WebDAV (Nextcloud, Synology, anything that speaks WebDAV) or sync the .kdbx file yourself via Dropbox / iCloud / Drive. Coming soon: BYOK OAuth adapters and end-to-end-encrypted passkey-authenticated sync — your master password never leaves the browser, the server only sees ciphertext.

Why should I trust KeeWebX, a fork?

Don't trust — verify. KeeWebX is MIT-licensed, the build is reproducible, and the SHA in the deployed bundle matches the GitHub commit. Read the source, build it from a clean checkout, or just run it from a static file with no network access.