Passwords that never leave your browser
Seven ways to build one — from random characters to phrases you can actually remember — and a vault to keep them in, encrypted with a passphrase only you know.
No account. No server. Nothing to sign in to.
Generate a password or read how it works
Seven ways to make one
Random characters when you want them, and words when you have to type the thing by hand or read it off a screen to someone. Simple, Advanced, Words, Passphrase, Wireless, Mad Lib and Numbers — each with its own controls, and each showing the strength of what it just made, in bits.
The number is the claim, so it is the thing most carefully checked. Options that add nothing say so: the leet toggle is a fixed public mapping and buys 0 bits, eight of the ten capitalisation modes are deterministic and buy 0 bits. A generator that flattered its own output would be worse than none.
A vault, if you want one
A generator on its own is a moment-tool: you take a password and leave, and the clipboard timer erases the only copy thirty seconds later. The vault keeps what you make, sealed with AES-256-GCM under a key derived from your passphrase. It is a single encrypted envelope — no index, no plaintext list of what you have, and nothing searchable outside the ciphertext.
It locks itself when you stop using it. It can hand you a recovery key — sixteen words, shown once — so that forgetting a passphrase is survivable. And there is still nothing to sign in to.
Your cloud, not ours
The vault can live as one encrypted file in a folder you already sync — Dropbox, OneDrive, iCloud Drive. Your own software carries it between your machines, using an account you already have with a company you already chose. We are not in the middle of that and could not be: there is no server here to put there. Your provider stores ciphertext it cannot read.
The limit, in the same breath: that makes two machines safe in sequence, not in the same instant. A save re-reads the folder and merges before writing, so an edit made elsewhere is not overwritten — but nothing here can see across your sync client’s own conflict handling. It needs the File System Access API, which today means Chromium on desktop; everywhere else the vault stays in browser storage and everything else works.
What it costs you
Nothing to buy and nothing to sign up for. The costs are the other kind, and they are the direct consequence of having no account:
- Nobody here can let you back in. There is no password reset, because there is no account to reset. Lose the passphrase and the recovery key and the vault is gone for good.
- Browser storage is not permanent. Clearing site data, an eviction, or a lost device all destroy a vault that was never exported. Export it somewhere.
- Syncing through a folder is desktop Chromium only, and deliberately not offered on phones — the permission does not survive a page refresh there.
Read it yourself
Every claim on this page is either checked by a test or written down somewhere with its limit attached. The code is on GitHub, unbundled and unminified: what a server sends you is what is committed there. The documentation explains how the vault is encrypted, the about page explains why it is built this way, and the legal page is the full privacy statement.