What this tool does
AES-256-GCM is today's mainstream symmetric cipher: one key both reads and verifies the data — flip a single byte of ciphertext and decryption fails outright instead of silently producing garbage. GCM is the default of TLS 1.3, and it is what this tool uses underneath.
The workflow is simple: pick a password, paste text, encrypt — you get a self-contained Base64 cipher; anyone with the same password can decrypt it here (or in any compatible implementation). Salt, IV and auth tag travel inside the cipher — no extra parameters needed. Everything runs locally.
How to use
- Pick a strong password The password is the only key — lose it and the cipher is unrecoverable. Encryption and decryption must use the exact same password (a trailing space counts).
- Encrypt and store the cipher The Base64 output is all you need: send it in a message or store it in notes. Every encryption uses a fresh random salt & IV — encrypting the same text twice gives different output, which is expected.
- Paste the cipher to decrypt Switch to "Decrypt", paste the cipher, enter the same password. The "send to decrypt" button moves the result back into the input for a quick round-trip check.
FAQ
Can it be decrypted without the password?
No. AES-256 with 210k derivation rounds makes brute force impractical. Store your password somewhere safe.
Different output each time — is that a bug?
No. Salt and IV are random per encryption — required for security; decryption only cares about content, not what the cipher looks like.
Can other tools or languages decrypt this?
Yes, if the format is honored: after Base64 decode, skip the 6-byte magic, take 16-byte salt and 12-byte IV; the rest is GCM ciphertext (with 16-byte tag); key = PBKDF2-SHA256(password, salt, 210000 iterations, 256-bit).
Does it encrypt files?
This tool is text-only (≤2MB). Binary file encryption is a separate scenario, not offered yet.
"Wrong password" but I am sure it is correct?
This error also covers tampered ciphertext. First confirm the cipher is intact (no lost characters when copying), then check the password for invisible differences (spaces, full-width chars).
Is this end-to-end encryption?
This is password-based encryption: security depends on password strength and how you transmit it. True E2E (like Signal) adds key exchange and forward secrecy — send the password over a different channel.
Limits
Text only, up to 2MB per run; no binary files, no unauthenticated AES-CBC/CTR modes.
The cipher format is self-contained but private (FTAE1 prefix) — interoperating with other tools requires the unpacking steps in FAQ #3.
Does not protect the operating environment (keyloggers, screen peeking); password strength caps the security.