Where does my password go?

Into your browser's cryptography engine and nowhere else. This page has no backend that could receive it — the encryption happens in JavaScript on your own device, which is why the tool keeps working with the network switched off entirely.

Can you recover my text if I forget the password?

No, and that is not a policy we could change. The key exists only for as long as the tab is doing the work, and it is derived from your password each time. Nobody here ever holds a copy of either.

Why is the encrypted result so much longer than my text?

Forty-one bytes of header travel with it — a format marker, the iteration count, the sixteen-byte salt and the twelve-byte initialisation vector — plus a sixteen-byte authentication tag at the end. That overhead is fixed, so it looks enormous on a short message and negligible on a long one.

Is this compatible with OpenSSL or another encryption tool?

No. The cipher is standard, but the container around it is specific to this site, so the output opens with the matching decrypt tool here and not with `openssl enc`. If you need an interchange format, encrypt a file with GPG instead.

Should I use this instead of an end-to-end encrypted messenger?

Use the messenger where you have one. This is for the cases where you do not — a document, a ticketing system, a shared spreadsheet, anywhere the medium is fixed and untrustworthy and you still need to put something in it.

Encrypt Text

AES-256-GCM with a password, entirely in this tab.

Everything runs inside your browser. Your files never leave your device.

Input

Result

The result appears here as you type.

Ask about Encrypt Text

Questions about what this tool does, which option to pick, or what it can and cannot handle.

The question you type here is sent to an AI provider to be answered — your files and whatever you put in the tool above are not, and the assistant cannot see them. Answers are generated and can be wrong. The tool itself is not guessing: it runs deterministic code on your device.

About the Encrypt Text

Sometimes a paragraph needs to travel through a channel you do not trust. A note in a shared document, a password sent to a colleague over chat, recovery details pasted into a ticket that will outlive the problem. Encrypting the text first means the channel carries something unreadable, and only the person with the password gets the words back.

This tool uses AES-256 in GCM mode, which is the same construction that protects HTTPS traffic, run through your browser's built-in WebCrypto implementation. The key is not your password — it is derived from your password by PBKDF2, which repeats a hash function hundreds of thousands of times specifically to make guessing slow. Six hundred thousand rounds is the current OWASP floor, and it is the default here. On a laptop that costs about a second. To someone running a dictionary attack against you, it costs a second per guess, which is the entire point.

GCM is an authenticated cipher, which is the part people usually skip. It does not merely conceal the text; it detects any change to it. If a single byte of the result is altered in transit, decryption fails rather than returning subtly wrong words. That means you can tell the difference between "this arrived intact" and "something happened to this", which a plain cipher cannot tell you.

Everything the result needs to be opened again — the random salt, the initialisation vector, the iteration count and the hash used — is packed into the output alongside the ciphertext. Keep the whole block and it will still open in a year, whatever the defaults on this page have become by then. Lose the password and nothing opens it, including us. There is no recovery path, because there is no account, no key escrow and nowhere a copy could have been kept.

How to use it

1Type or paste the text you want to protect into the input box.
2Enter a password in the options. Long and unusual beats short and clever — a passphrase of four unrelated words is stronger than a mangled dictionary word.
3Leave the PBKDF2 rounds at 600,000 unless you have a reason to change them. Raising the number slows an attacker and this page by the same proportion.
4Copy the encrypted block that appears. Send all of it, including the line breaks, or paste it somewhere it will not be reflowed.
5Store the password separately from the ciphertext, in a password manager. Sending both down the same channel defeats the exercise.

Questions

Where does my password go?: Into your browser's cryptography engine and nowhere else. This page has no backend that could receive it — the encryption happens in JavaScript on your own device, which is why the tool keeps working with the network switched off entirely.
Can you recover my text if I forget the password?: No, and that is not a policy we could change. The key exists only for as long as the tab is doing the work, and it is derived from your password each time. Nobody here ever holds a copy of either.
Why is the encrypted result so much longer than my text?: Forty-one bytes of header travel with it — a format marker, the iteration count, the sixteen-byte salt and the twelve-byte initialisation vector — plus a sixteen-byte authentication tag at the end. That overhead is fixed, so it looks enormous on a short message and negligible on a long one.
Is this compatible with OpenSSL or another encryption tool?: No. The cipher is standard, but the container around it is specific to this site, so the output opens with the matching decrypt tool here and not with `openssl enc`. If you need an interchange format, encrypt a file with GPG instead.
Should I use this instead of an end-to-end encrypted messenger?: Use the messenger where you have one. This is for the cases where you do not — a document, a ticketing system, a shared spreadsheet, anywhere the medium is fixed and untrustworthy and you still need to put something in it.