Real AES-256-GCM encryption & decryption, 100% in your browser
Uses the browser's native crypto.subtle Web Crypto API for authenticated, industry-standard encryption.
Your passphrase is stretched into a 256-bit key with a random salt and 100,000 SHA-256 iterations.
Each encryption uses a fresh random salt and IV, so identical input never produces identical output.
Salt, IV, and ciphertext are packed into one copyable Base64 string — easy to share or store.
A wrong passphrase or corrupted data fails cleanly with a readable error, never garbled output.
All encryption and decryption happens locally in your browser — nothing is ever sent to a server.
This tool lets you encrypt sensitive text — notes, credentials, messages — using real AES-256-GCM encryption, entirely on your own device. There is no server component: your plaintext, passphrase, and ciphertext never leave your browser tab.
Your passphrase is never used directly as an encryption key. Instead, it is combined with a random 16-byte salt and run through PBKDF2 with 100,000 iterations of SHA-256 to derive a 256-bit AES key. A random 12-byte IV (initialization vector) is generated for every encryption. The salt, IV, and resulting ciphertext (which includes GCM's built-in authentication tag) are concatenated and Base64-encoded into a single string you can copy, store, or send.
This tool has no server, no account system, and no stored copy of your passphrase or plaintext. The decryption key only exists momentarily in your browser's memory, derived fresh from the passphrase you type each time. If you lose the passphrase, there is mathematically no way to reverse AES-256-GCM without it — that is precisely what makes the encryption strong. Always store your passphrase somewhere safe, such as a password manager.
AES-256-GCM, an authenticated encryption cipher, via the browser's native Web Crypto API (crypto.subtle). Your passphrase is turned into a 256-bit key using PBKDF2 with a random salt and 100,000 iterations of SHA-256, so the same passphrase never produces the same key twice.
No. All key derivation, encryption, and decryption happen locally in your browser using crypto.subtle. Nothing you type is transmitted, logged, or stored anywhere.
The encrypted text cannot be recovered. This tool has no backdoor, no password reset, and no master key — the passphrase is the only way to derive the decryption key. Losing it means the data is permanently unrecoverable, so store your passphrase somewhere safe.
AES-GCM includes a built-in authentication tag, so decryption with an incorrect passphrase or corrupted ciphertext fails outright rather than silently returning garbled text. The tool catches this and shows a clear "Incorrect passphrase or corrupted data" message.
Each encryption generates a fresh random salt and a fresh random IV (initialization vector), which are prepended to the ciphertext and needed for decryption. This randomness means encrypting the same text twice produces different output, which is a deliberate security property that prevents pattern analysis.