How strong is this encryption?
AES-256 with GCM is a strong, widely used standard. The strength of your result depends on the passphrase. Use a long random passphrase or a password manager entry, not a short word.
Encrypt a message with AES-256-GCM using a passphrase, or decrypt Base64 ciphertext. The work happens in your browser.
Runs in your browser — nothing is uploaded
AES is the standard symmetric cipher used to protect data at rest and in transit. GCM mode adds an authentication tag, so tampering with the ciphertext is detected and decryption fails rather than producing garbage.
This tool derives the key from your passphrase with PBKDF2-SHA256 and 310,000 iterations, which slows down guessing attacks. The output contains a random salt and IV, so the same message encrypts differently each time. Keep the passphrase somewhere safe, because the data cannot be recovered without it.
AES-256 with GCM is a strong, widely used standard. The strength of your result depends on the passphrase. Use a long random passphrase or a password manager entry, not a short word.
Ciphertext should look random. The Base64 output packs a 16-byte salt, a 12-byte IV and the encrypted data with its authentication tag.
Nothing can recover the data. There is no back door, so store the passphrase in a password manager or another secure place before you encrypt anything important.
The ciphertext was probably copied incompletely, or extra characters were added. GCM rejects any change, so check that you copied the full Base64 string.
This tool handles text. For files, use a dedicated encryption tool or your operating system's encrypted archive feature. Share the passphrase through a separate channel.
No. The Web Crypto API performs the operations in your browser, and neither the passphrase nor the message is uploaded.