Passwords and 2FA codes. Encrypted before they leave.
A password manager that encrypts records in your browser before they are sent. Edit any field — the right side shows what our server would receive at that moment.
Characters without a key. Your password or recovery file unlocks the key — we don't have it.
Every feature, from both sides
On the left, what you get. On the right, what stays with us — including the service data the service can see.
Passwords
Generate, show and hide, copy in one click. If the connection drops, an unsaved record can be restored.
Record name, site, login and password live inside the encrypted record.
2FA codes
Paste a secret or an otpauth:// link into the record. Copy the current code with a button; PasswordX shows how many seconds it has left.
The 2FA secret is encrypted. The code itself is computed in your browser.
An email address per site
Connect an email alias to a record and read its mail in PasswordX — confirmation codes land there too.
The alias address is visible: mail is routed by it. Mail arrives over ordinary SMTP and is visible to the service on receipt, before encryption.
Multiple vaults
Personal, family, work. Search across loaded records.
Internal identifiers and sizes are visible. Vault and record names are not.
Read-only sharing
Open one record or vault to another person — together with mail of the aliases linked to those records. See who has access and revoke it.
Who has access is visible. The record key is encrypted for the recipient.
Recovery file
Saved during first setup. Restores access to the account and vault if you forget your password.
The file stays with you. We have no back door: without the password and the file we can't restore access.
Notes
Backup codes, PINs, answers to security questions.
Encrypted just like passwords.
Lock
On demand and after 15 minutes of inactivity, with a warning a minute before. Values leave the screen and can't be copied until you sign in again.
Nothing changes for the service: the contents are already encrypted.
2FA codes next to the password
A built-in authenticator. The secret from the site lives in the same record. When the site asks for a code, copy it with a button — PasswordX shows how many seconds it has left.
The secret as ciphertext. The code, never.
The code is computed in your browser from the secret and the current time, per RFC 6238. It never reaches the server.
Record names are labelled here for clarity. The service doesn't have them.
What we honestly can't do
Security starts with knowing the limits.
FAQ
Algorithms and threats in detail: How security works.
Can PasswordX read my passwords?
No. Records are encrypted in your browser. Your password or recovery file unlocks the key, and a recipient you share with gets the key to the chosen record or vault only. The server stores ciphertext and the service data needed for sync and sharing.
What does the PasswordX server see?
Record contents — names, sites, logins, passwords, 2FA secrets and notes — are encrypted. The service sees internal identifiers, sizes, granted access and alias addresses. Mail to an alias arrives as ordinary email and is visible on receipt, before it is encrypted.
PasswordX is a website. How can the server not see my passwords?
Encryption runs right in your browser, on the PasswordX page. A record becomes ciphertext before it is sent to the server. The server doesn't have the vault key.
What happens if I forget my PasswordX password?
You restore access with the recovery file you save during first setup. If both the password and the file are lost, we can't restore access either: there is no back door.
Where does PasswordX work?
In the browser at passwordx.io, with nothing to install.
Who will see a record I share?
Only the recipient you choose, and only to read: they can't edit or delete the record. Along with it they see available mail of the alias linked to it. Your other records, main inbox and other aliases stay closed to them.
Can I revoke access I have shared?
Yes. Revoking closes that particular access. Other rights you granted — for example to a vault containing the record — remain, and copies the recipient has already seen or saved stay with them. So after revoking, change the password on the site and set a new 2FA secret.
Is it safe to keep 2FA codes next to the password?
For most accounts, yes, if your PasswordX password is long and unique: the 2FA secret is encrypted just like the password. For the most important accounts, such as your main email, you can keep the second factor separately, on a hardware key. More
What encryption does PasswordX use?
The open OpenPGP version 6 standard: Ed25519 and X25519 keys, AES-256-GCM symmetric encryption and Argon2 to protect the key with your password. It uses the OpenPGP.js library and no home-made cryptographic primitives.
From the blog
All articlesStop memorising passwords
Signing up takes a couple of minutes. Save the recovery file at the end and your vault is ready.
This is how we would see that sentence if it were a record in your vault.