Text Encryption Tool

Sometimes you need to send a sentence that shouldn’t be readable by whoever runs your email server or chat platform. This tool encrypts any text with AES-256 using a password you choose, then emits a compact base64url token you can send over any channel. The recipient pastes it back here with the same password and sees the original message. Everything happens in your browser through the Web Crypto API, so your text and password never reach our server.

How the encryption flows

  1. 1

    Type the message

    Plain text, one line or many. Unicode, emoji and line breaks are preserved.

  2. 2

    Choose a password

    Anything 12+ characters with mixed types. You'll need to share this with the recipient out-of-band.

  3. 3

    Encrypt

    The tool derives an AES-256 key from the password using PBKDF2 and encrypts with AES-GCM for authenticated encryption.

  4. 4

    Send the ciphertext

    Copy the base64 blob into email, chat or a ticket: it's opaque to anyone without the password.

  5. 5

    Decrypt on the other side

    Recipient pastes the blob, types the password, hits decrypt.

The cryptography stack

  • AES-256 in GCM mode, provides confidentiality and authentication in one pass. If the ciphertext is tampered with, decryption fails rather than silently producing garbage.
  • PBKDF2-SHA-256, 310,000 iterations, derives a key from your password so brute-forcing is expensive even with a weak password.
  • Random 12-byte IV and 16-byte salt, fresh for every encryption; packaged with the ciphertext in the output token so the recipient can reproduce the key.

What it protects against

Threat Protected?
Email provider reading the body Yes
Chat server storing the text Yes
Network eavesdropping Yes
Recipient’s device being unlocked No
Keylogger on either endpoint No
Password reuse across services No

Choosing a password

  • At least 16 characters of mixed types, or a passphrase of 5+ unrelated words.
  • Don’t reuse a password you use anywhere else.
  • Share out-of-band: if you send the password in the same chat where you send the ciphertext, the encryption bought you nothing.

Not a replacement for Signal or PGP

This tool is convenient for ad-hoc protection, a one-off credential shared over email, a sensitive note left in a shared doc. For long-term encrypted conversations, use a messenger with forward secrecy (Signal) or PGP with key management. Password-based encryption has no forward secrecy: if the password leaks, every past message encrypted with it becomes readable.

Frequently Asked Questions

Yes, it’s the same primitive used in TLS 1.3, SSH and countless government standards. With a strong password, 310,000 PBKDF2 iterations and a random IV, breaking the ciphertext is computationally infeasible.

The message is permanently unrecoverable. There’s no backdoor or recovery mechanism, that’s the point. Store the password in a manager if it matters.

No. A fresh random IV means the ciphertext differs every time, even for identical plaintext and password. This is correct cryptographic behaviour.

No. Encryption and decryption run entirely in your browser via the Web Crypto API. Your plaintext never leaves your machine.

Related Tools

Tool available in other languages