Encrypt and decrypt text
Encrypt a message with a password to pass it on safely, or — for developers — encrypt and decrypt with a raw key by algorithm to check what another system produces. Everything happens in your browser.
With a password
AES-256-GCM, with the key derived from your password by PBKDF2-SHA256 over 600,000 iterations and a random salt. The output carries the salt and IV, so only the password is needed to decrypt.
With a key (developers)
Never reuse a nonce with the same key: for GCM and ChaCha20 that breaks the encryption.
Se ejecuta por completo en tu navegador: no se envía nada a ningún sitio
Choosing an algorithm
- AES-GCM and ChaCha20-Poly1305 are authenticated: they detect tampering and a wrong key. Prefer them.
- XChaCha20-Poly1305 takes a 24-byte nonce, safe to choose at random for any number of messages.
- AES-CBC and AES-CTR encrypt without authenticating; use them only to interoperate with systems that require them, and add a MAC.
How safe is the password mode?
As safe as the password. AES-256-GCM and PBKDF2 are standard and implemented by your browser; a short or common password can still be guessed. Use a long passphrase and share it separately.
Why is there no ECB mode?
ECB encrypts identical blocks to identical output, which leaks patterns in the data. It should not be used, so it is not offered.
Is anything sent to a server?
No. Encryption and decryption run in your browser, and nothing is stored.