Security & Privacy
Text Encryption (AES-256)
Encrypt and decrypt messages with a password using AES-256-GCM — right in your browser. Share the scrambled text safely; only someone with the password can read it.
How to use
- 1Type your message and a strong password, then press Encrypt.
- 2Send the encrypted text. Share the password separately (e.g. by phone). The recipient pastes it here with the password and presses Decrypt.
How it's calculated
The password is stretched with PBKDF2-SHA-256 (600,000 iterations) into a 256-bit key; the text is encrypted with AES-GCM, which also detects tampering. A random salt and IV are included in the output.
Frequently asked questions
Is my text sent to a server?
No — encryption and decryption happen entirely in your browser using the Web Crypto API.
How strong is it?
AES-256-GCM is the same standard used by banks and governments. Your security depends on the password — use a long, unique passphrase.
What if I forget the password?
The text can't be recovered — there's no backdoor. Keep the password somewhere safe.
Why the output looks much longer than your message
The Base64 text you copy isn't just your encrypted message — it's a small container: a 4-byte format marker, a 16-byte random salt, a 12-byte random IV, and then your message encrypted with AES-GCM, which appends a 16-byte authentication tag. A two-character message like "Hi" turns into 50 raw bytes before encoding (4 + 16 + 12 + 2 + 16), which comes out to 68 characters of Base64 — so even a one-word secret produces a long string. That overhead is fixed per message (not per character), so it matters a lot for a two-word message and barely at all for a paragraph.
Why encryption succeeds but decryption can fail loudly
AES-GCM is an authenticated cipher — decrypting with the wrong password, or decrypting text that's been altered by even one character (a dropped space from a messy copy-paste, for instance), doesn't produce garbled output. It fails outright with an explicit error, because the authentication tag can't verify. That's deliberate: you should never end up trusting a decrypted message that was silently corrupted or tampered with, so this tool treats "might be wrong" and "definitely wrong" the same way — as a hard failure.
Why the password has to travel separately
Encrypting a message and then sending the ciphertext and the password through the same channel (the same email, the same chat thread) defeats the purpose — anyone who intercepts one gets the other. The tool's own guidance — send the password by phone call or a separate app — exists because the security model assumes an attacker might see the encrypted text in transit (email is not private), but shouldn't also have the password. A weak or reused password undermines everything else: PBKDF2's 600,000 iterations slow down brute-forcing, but they don't make a short, guessable password strong.
A bad paste, the wrong tool, and a wrong password fail differently
What you copy starts with the letters TSE1, then a random salt, then a random starting value, then the encrypted message and a check that the text was not altered. On decrypt, spaces and line breaks in the paste are ignored. Text that is not in that encoding at all fails with That isn't valid encrypted text (Base64 expected). A block that is too short, or that does not start with TSE1, fails with This isn't data encrypted with this tool. A block that looks right but has the wrong password, or a single changed character, fails with Wrong password, or the data was changed. Encrypting keeps a trailing space as part of the message. Decrypting trims the paste before it tries to read it.
A short password warns you, and Encrypt still runs
On Encrypt, a password with at least one character and fewer than 12 shows the hint Use at least 12 characters — a few random words works well. The button stays clickable. What actually disables it is an empty message or an empty password. Encrypting the same message with the same password twice produces two different blocks, because a fresh salt and a fresh starting value are chosen every time. Either block decrypts with that password, since those extra pieces travel inside what you copy. Switch from Encrypt to Decrypt while a result is on screen and that result moves into the input, so you can check a message you just encrypted without pasting it yourself.
Related tools
- File Encryption (Password-Protect Any File)
Encrypt any file with a password before sharing or storing it — AES-256-GCM in your browser. Decrypt it here later to get the original file back, name and all.
- Phishing Email Checker
Paste a suspicious email or text message to spot common phishing red flags — urgency, credential requests, gift-card payments, look-alike links and more.
- Password Strength Checker
Check how strong a password really is — entropy, estimated crack time and the weak patterns attackers look for. Checked privately in your browser.
- Password Policy Generator
Generate a clear, modern company password policy based on NIST SP 800-63B — length, MFA, breached-password screening, lockouts and password managers.
- Edit PDF (Add Text, White-Out, Shapes)
Add text, white-out boxes, highlights, rectangles and form fields to PDF pages — click to place, drag to move — then download.
- Protect PDF
Lock a PDF with a password using AES-256 encryption. The password and file never leave your browser.