Text Encryptor
Encrypt a message with a password using AES-256 in your browser, and decrypt it anywhere with the same password. 100% free, no signup. Everything runs in your browser.
Loading the tool…
Sending a password, an API key or a door code by chat is something everyone does and nobody is comfortable with, because the message sits in a server log, a backup and a search index for years after the moment it was needed. I built this so the thing that sits there is ciphertext. You type the message and a password, the browser encrypts it with AES-256-GCM using a key derived from that password, and you get one string that is safe to paste anywhere. The recipient pastes it back here with the password and gets the message. The password travels by some other route, which is the one rule that makes the whole thing work.
Every byte of this happens inside the tab using the browser's built in Web Crypto, the same code that secures the padlock in the address bar. There is no server, no account and no record, which is checkable: load the page, go offline, and it still encrypts. The output carries its own salt and nonce, so you do not need to keep anything except the password, and because GCM authenticates what it encrypts, a wrong password or a tampered message fails cleanly instead of producing plausible garbage. For checking whether the password you chose is already on a breach list, the password breach checker sits next to this one.
How to use
- Choose Encrypt. Type or paste the message. Anything goes: a sentence, a key, a paragraph, a configuration block.
- Enter a password. Length matters more than symbols; a sentence you can remember is stronger than eight characters with punctuation.
- Press Encrypt and copy the result. One string, safe to paste into a chat, an email, a ticket or a text file.
- Send the encrypted string by one route and the password by another. A phone call for the password is fine.
- To read a message, choose Decrypt, paste the string, enter the password and press Decrypt.
- If decryption fails, the password is wrong or the string was altered in transit. Check that the whole string was copied.
Why use our text encryptor?
The real algorithm, not a toy. AES-256 in GCM mode, with the key derived by PBKDF2-SHA256 at 600,000 iterations, the figure OWASP currently recommends. All of it runs through the browser's SubtleCrypto interface rather than a JavaScript reimplementation, which means the primitives are the ones the browser vendors maintain and audit. The iteration count is the part that makes a password attack expensive: each guess costs the attacker the same second it costs you.
Nothing leaves the device, and that is the design rather than a promise. There is no endpoint to send anything to. The page works with the network disconnected. For a password or a private key, that is the only acceptable arrangement, and it is the reason to use this over an online encryption service that shows you a padlock icon and keeps your plaintext in a request log.
One string carries everything except the password. The salt and the nonce are packed into the output alongside the ciphertext, so the recipient needs nothing from you but the password. Encrypt the same message twice and you get two different strings, because the salt and nonce are fresh each time, which is how it should be and how most homemade schemes are not.
Tampering is detected, not silently decoded. GCM produces an authentication tag over the ciphertext. Change one character of the string and decryption refuses rather than returning corrupted text that might look right at a glance. The same mechanism is why a wrong password fails rather than producing garbage, and why the tool cannot tell you which of the two happened.
Honest about the limits. This protects the content of a message against anyone who gets the ciphertext. It does not hide the fact that an encrypted message exists, it does not protect against a weak or reused password, and it cannot help if the device you type on is compromised. Encrypting a secret and then emailing the password in the same thread defeats the entire exercise. The password generator is the right source for the password itself.
Who is this tool for?
Handing over credentials. A client needs the admin login, a contractor needs the API key, a colleague needs the Wi-Fi password. Encrypt it here, paste the result in the chat, read the password to them over the phone. The chat log now contains nothing useful to whoever reads it in three years.
Notes you want in a cloud file but not readable in it. A recovery phrase, a list of account details, a medical note. Encrypt the text, save the string in whatever notes app you already use, and the sync service is storing ciphertext. The create ZIP tool is a reasonable way to bundle several such strings for a backup.
A message that should expire with the password. Tell someone the password in person, encrypt the follow-up, and the written record is useless once either of you forgets it. For some conversations that is a feature.
Checking what a vendor means by encrypted. When a service says it encrypts your data, this page is a quick reference for what that should look like from the user's side: a key derived from something only you have, ciphertext that fails loudly when tampered with, and no copy of the plaintext anywhere but your own screen.
Frequently asked questions
AES-256-GCM with a key derived by PBKDF2-SHA256 at 600,000 iterations, using the browser's built in cryptography. Against anyone who has only the encrypted string, the security is the security of your password: a long, unique passphrase makes guessing impractical, and a short reused one does not. The password breach checker will tell you if the password you chose is already on a list.
No. Encryption and decryption run entirely in the browser through the Web Crypto API, and there is no endpoint involved. You can load the page, disconnect from the internet, and it still works. For anything sensitive, that arrangement is the whole reason to use it.
No. There is no master key, no recovery route and no copy of the password anywhere. The impossibility of recovery is what makes the encryption worth anything, and it cuts both ways. For something you cannot afford to lose, keep the password in a password manager.
A fresh random salt and nonce are generated for every encryption and packed into the output. Identical messages therefore produce unrelated ciphertext, which prevents anyone spotting that two strings contain the same content. The recipient does not need to know the salt; it travels inside the string.
Older ZIP encryption is weak and widely broken; modern AES ZIPs are fine but need a tool that supports them at both ends. This produces plain text that pastes anywhere, including places that reject attachments, and the algorithm is the one browsers use for the web itself.
Not directly; this tool is for text. A small file can be turned into text with the image to Base64 tool or any Base64 encoder and then encrypted here, though the string gets large. For whole files, a dedicated file encryption tool is the better fit.
It needs the same format, which is this page. The format is simple and documented in the page source: one version byte, a 16-byte salt, a 12-byte nonce and the AES-GCM ciphertext, Base64 encoded. Anyone with that description and standard crypto libraries can decrypt it without this site.

