AES Text Encryptor
Lock text with a password using AES-256-GCM — decrypt it back anytime
✦ Passwords are not keys — stretching makes them so
AES needs a 256-bit key, but humans remember passwords, not keys. Key stretching (PBKDF2 here) turns your password into a proper key through 100,000 rounds of hashing — guessing then costs attackers 100,000x per try. GCM mode adds authentication, so any tampering is detected instead of silently decrypted.
What this tool does
- 🔏 Encrypts any text with a password to portable base64
- 🔓 Decrypts it back with the same password
- 🎲 Fresh random salt + IV every time — same text encrypts differently twice
- ⚠️ Wrong passwords fail with a clear error, never with garbage
When to use it
- Sending a secret through chat or email
- Storing a private note where others might look
- Learning how authenticated encryption behaves
Privacy: everything runs in WebCrypto locally — passwords, plaintext and keys never leave your browser.
Last updated · 2026-09-01
How encryption works
PBKDF2-SHA-256 (100k iterations, 16-byte random salt) derives a 256-bit key from your password; AES-GCM with a 12-byte random IV encrypts, and salt+IV+ciphertext are concatenated as base64. Decryption splits the same layout and lets GCM authentication reject wrong passwords.
Why encrypt here?
Real authenticated encryption
AES-256-GCM with PBKDF2-SHA-256 at 100,000 iterations — the boring, reviewed construction professionals use, not a homebrew XOR.
One portable string
Salt, IV and ciphertext travel in a single base64 blob, so the output pastes cleanly into any chat, mail or document and decrypts anywhere.
Loud failures, never silent garbage
A wrong password or a single flipped character fails with a clear error thanks to GCM authentication — you always know where you stand.
Frequently asked questions
What exactly protects my message?⌄
AES-256 in GCM mode (authenticated encryption) with a key stretched from your password via PBKDF2-SHA-256, 100,000 iterations, plus a fresh random salt and IV per message. Tampered ciphertext fails loudly instead of decrypting to garbage.
Can you decrypt it without my password?⌄
No — and neither can we: the password never leaves your browser, and there is no copy of anything anywhere. Lose the password and the message is unrecoverable, by design.
Is the output safe to paste into chat or email?⌄
Yes. Ciphertext is plain base64 text (salt + IV + data in one string), so it survives chat apps, email and notes without corruption.
Frequently asked questions
What exactly protects my message?
AES-256 in GCM mode (authenticated encryption) with a key stretched from your password via PBKDF2-SHA-256, 100,000 iterations, plus a fresh random salt and IV per message. Tampered ciphertext fails loudly instead of decrypting to garbage.
Can you decrypt it without my password?
No — and neither can we: the password never leaves your browser, and there is no copy of anything anywhere. Lose the password and the message is unrecoverable, by design.
Is the output safe to paste into chat or email?
Yes. Ciphertext is plain base64 text (salt + IV + data in one string), so it survives chat apps, email and notes without corruption.