Encrypt and Decrypt Text With a Password

It uses AES-GCM with a 256-bit key. The key is derived from your password with PBKDF2 (SHA-256, 100,000 iterations) and a random salt, and each message uses a fresh random IV. The output packs the salt, IV and ciphertext together as base64.

AES-GCM and PBKDF2 are standard, well-reviewed building blocks, and GCM also detects tampering. The real weak link is your password: short or common passwords can be guessed. Use a long, unique passphrase for anything sensitive.

There is no recovery and no backdoor. The password is the only way to derive the key, so if you forget it the text cannot be decrypted by you or anyone else. Store the password somewhere safe before you rely on it.

No. Encryption and decryption run locally with the browser Web Crypto API, so the plaintext, the password and the result stay on your device. Nothing is sent to a server or saved.

A new random salt and IV are generated every time, so the output changes on each run even with the same text and password. This is expected and is what keeps the encryption safe; both outputs still decrypt to the same text.

Decryption fails for the wrong password or if the data was altered, and the tool reports a corrupted or wrong-password error. Only the exact password used to encrypt will recover the original text.