ENES

AES Encrypt & Decrypt

Encrypt and decrypt text using AES-GCM in your browser. Automatic PBKDF2 key derivation, random IVs, and Base64 cipher envelopes.

Runs in your browser · Free, no sign-up · Nothing is stored

About this tool

Sensitive notes and configuration values should not be stored or shared as plain text. This browser-based AES encryption and decryption tool uses the Web Crypto API to encrypt text and create a portable ciphertext envelope containing the parameters required for decryption. AES-GCM is the recommended default because it provides both confidentiality and integrity verification, while AES-CBC should be used only for compatibility with systems that provide a separate authentication mechanism. This utility is intended for testing and controlled workflows and does not replace HTTPS, secure key exchange, or an approved secret-management system.

How to use it

What Is AES Encryption and Decryption?

AES is a symmetric block cipher standardized by the National Institute of Standards and Technology. Symmetric encryption uses the same cryptographic key for encryption and decryption. In this tool, that AES key is derived from a passphrase using PBKDF2-HMAC-SHA-256 with 600,000 iterations and a fresh random salt generated for each encryption. The salt, iteration count, algorithm, key length, and initialization vector are stored in the ciphertext envelope so the same key can be derived during decryption. Increasing the PBKDF2 work factor makes offline guesses more expensive, but it cannot make a weak or reused passphrase safe.

AES-GCM is the recommended mode for new encryption because it provides authenticated encryption: it protects confidentiality while detecting unauthorized changes to the ciphertext and authentication tag. AES-CBC provides confidentiality only, has no built-in integrity protection, and should be used solely for compatibility with systems that supply a separate, correctly implemented authentication mechanism. Each encryption generates a fresh random IV (12 bytes for GCM, 16 bytes for CBC) that is stored in the envelope; a fresh IV is generated for every encryption so it is not reused with the same derived key. Salts and IVs do not need to be secret, but the passphrase must be protected separately.

How to use it

  1. On the Encrypt Plaintext tab, choose a key length. All new encryptions use AES-GCM.
  2. Enter your text and a strong, unique passphrase, then click the Encrypt button.
  3. Copy and preserve the complete envelope. "Copy Envelope" gives a compact base64 string and "Copy JSON" gives readable metadata; both contain the same parameters. Do not remove the salt, IV, algorithm, iteration count, or ciphertext.
  4. To decrypt, open the Decrypt Ciphertext tab and paste the full envelope. The tool reads the algorithm and key length from the envelope automatically — you only need to supply the matching passphrase.

Why use this over alternatives

This utility performs key derivation, encryption, and decryption locally through the browser's Web Crypto API. It is intended for testing, learning, and controlled text-encryption workflows. For production secrets or regulated data, use an approved encryption and key-management solution reviewed by a qualified security professional.

Questions

Are my passphrase and plaintext sent to a server?
Encryption, decryption, and key derivation are performed in your browser using the Web Crypto API. However, browser-based processing does not protect against malicious extensions, compromised devices, clipboard history, third-party scripts, or an untrusted copy of the webpage.
Can a forgotten passphrase be recovered?
The tool does not provide passphrase recovery and does not retain a copy of your passphrase. Decryption requires deriving the correct key from the original passphrase and the parameters stored in the envelope. A sufficiently weak passphrase may still be vulnerable to offline guessing, so use a long, unique passphrase and store it securely.
Is AES-256 automatically more secure for passphrase-based encryption?
AES-128 and AES-256 both use standardized key sizes. In a passphrase-based tool, practical security often depends more on passphrase unpredictability, key-derivation settings, correct IV handling, authenticated encryption, and implementation quality than on selecting 128-bit or 256-bit AES alone.
Does encrypting text replace HTTPS or secure file transfer?
No. Application-level encryption does not replace HTTPS, authenticated communication, secure key exchange, access controls, or trusted secret-management systems. If the ciphertext and its passphrase travel through the same compromised channel, encryption may provide little practical protection.

Related tools

All security tools