AES-256-GCM
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
Preparing your comprehensive developer toolkit
Practical Guide
Encrypt and decrypt text locally with authenticated AES-256-GCM. Legacy CryptoJS mode supports existing ciphertext.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption. Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption. Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption. Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption. Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
AES-256-GCM uses 600,000 PBKDF2-SHA256 iterations, a fresh random salt and IV, and authenticated encryption. Save the full JSON result for decryption.
Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
Legacy CryptoJS mode reads and writes salted OpenSSL Base64 with CBC. It has no authentication and is intended for existing ciphertext only.
Open the tool to try these features.