The wrong password fails loudly, not silently

Decryption requires the exact password used to encrypt. A typo or wrong password triggers an immediate error: "Decryption failed. Wrong password or corrupted file." The error deliberately does not distinguish between a wrong password and a corrupted file. This ambiguity is intentional — it prevents an attacker from using error messages to probe whether their password guess is close to correct.

Encrypted text must be base64

The tool encrypts into a binary format (7BB1 magic bytes + 16-byte salt + 12-byte IV + AES-256-GCM ciphertext + 16-byte auth tag) and encodes it as base64 so it survives copy/paste, email, SMS, and Slack without corruption. You paste the base64 back in, and decryption reverses the process by extracting the salt and IV and recomputing the key.

This tool only decrypts its own output

The 7BB1 format is proprietary to this tool. Encrypted text from other tools — even if they use AES-256-GCM — will be rejected because the magic bytes do not match. Cross-tool interoperability is not in scope. You must encrypt and decrypt with the same tool.

The password cannot be recovered

There is no password recovery, reset, or bypass. If you lose the password, the ciphertext becomes permanently inaccessible. The tool never stores, logs, or transmits the password — it stays in your browser and is used only to derive an encryption key via PBKDF2 with 200,000 iterations of SHA-256. That cost per attempt makes brute-force attacks expensive and recovery impractical.

For encrypted files rather than pasted text, see the File Decrypter, which uses the same format. For archives, see Remove ZIP Password.