Skip to content
Kordu Tools Kordu Tools

AES Encrypt

Runs in browser

Encrypt text with AES-256-GCM, AES-CBC, AES-CTR, or AES-ECB in your browser. PBKDF2 key derivation, random IV, zero uploads.

Last updated 02 Apr 2026

Paste your text, enter a password, and click Encrypt. Supports AES-256-GCM (recommended), AES-CBC, AES-CTR, and AES-ECB. Key derived via PBKDF2 with a random salt. All processing is client-side via WebCrypto — nothing leaves your browser.

AES-256-GCM — recommended. Authenticated encryption with a 256-bit key.

Looking for AES Decrypt?

Save the encrypted output and your password — without both, data cannot be recovered.
Loading rating…

How to use

  1. 1

    Choose your AES algorithm

    Select from the algorithm dropdown. AES-256-GCM is recommended — it provides authenticated encryption that detects tampered ciphertext during decryption.

  2. 2

    Enter your password

    Type a passphrase in the Password field. This is used with PBKDF2 to derive a strong AES key. Use a long, unique password for best security.

  3. 3

    Paste your plaintext

    Enter the text you want to encrypt in the input panel.

  4. 4

    Click Encrypt

    Click the Encrypt button. The Base64-encoded ciphertext appears in the output panel — it includes the salt, IV, and encrypted data in one self-contained string.

  5. 5

    Save the ciphertext and password

    Copy the ciphertext and store it with your password. Use the AES Decrypt tool with the same algorithm and password to recover the plaintext later.

Frequently asked questions

What is AES encryption?
AES (Advanced Encryption Standard) is a symmetric block cipher standardized by NIST in 2001. It uses the same key for both encryption and decryption and is the most widely deployed encryption algorithm in the world — used in TLS, VPNs, file encryption, disk encryption, and messaging apps.
Which AES mode should I use?
Use AES-256-GCM whenever possible. It provides authenticated encryption — decryption fails if the ciphertext has been tampered with. AES-CBC is a solid fallback for compatibility. Avoid AES-ECB: it has no IV, so identical plaintext blocks produce identical ciphertext, leaking patterns.
Is this tool safe to use for sensitive data?
Yes — all encryption runs in your browser using the WebCrypto API. No data is uploaded. The implementation uses PBKDF2 key derivation with a random salt and a unique random IV per encryption, meeting modern security standards.
Are inputs sent to a server?
No. There are zero network requests. Your password, plaintext, and ciphertext never leave your device. AES encryption is performed entirely by the browser's native WebCrypto API.
How is the key derived from my password?
Your passphrase is run through PBKDF2 with SHA-256, 100,000 iterations, and a random 16-byte salt. This makes brute-force attacks significantly harder. The salt is embedded in the ciphertext output so the same passphrase can always regenerate the exact key.
What happens if I lose my password?
There is no recovery mechanism. AES symmetric encryption is only as secure as your password. If you lose the password, the ciphertext cannot be decrypted. Store your password in a password manager.
What does the Base64 output contain?
The Base64 string encodes: a 16-byte random salt (for PBKDF2), a 12-byte (GCM) or 16-byte (CBC/CTR) random IV, and the ciphertext. This self-contained format means you only need the ciphertext and password to decrypt — no need to store the salt or IV separately.
What is the difference between AES-256-GCM and AES-256-CBC?
AES-256-GCM provides authenticated encryption: it detects if the ciphertext was modified after encryption, preventing padding oracle and bit-flipping attacks. AES-256-CBC only encrypts — it does not verify integrity. Use GCM for new implementations.
Can I decrypt the output with OpenSSL?
The output format is custom (salt + IV + ciphertext, Base64-encoded). It is not directly compatible with openssl enc, which uses a different key derivation scheme. Use the matching AES Decrypt tool on this site.

Encrypt any text with AES (Advanced Encryption Standard) directly in your

browser using the WebCrypto API. No data is uploaded or transmitted.

**Supported modes:**

- **AES-256-GCM** (recommended) — authenticated encryption that detects

tampering automatically during decryption

- **AES-192-GCM / AES-128-GCM** — GCM with smaller key sizes

- **AES-256-CBC / AES-128-CBC** — widely compatible block cipher mode

- **AES-256-CTR / AES-128-CTR** — stream cipher mode, no padding required

- **AES-128-ECB / AES-256-ECB** — no IV; avoid in production (identical

plaintext blocks produce identical ciphertext)

**How it works:** Your passphrase is stretched into a strong AES key using

PBKDF2 (SHA-256, 100,000 iterations) with a random 16-byte salt. A random

IV/nonce is generated for every encryption. The salt and IV are prepended

to the ciphertext before Base64 encoding — the output is completely

self-contained; only the ciphertext and your password are needed to decrypt.

**Privacy:** All cryptographic operations use the browser's WebCrypto API.

Your key and plaintext never leave your device.

Related tools

AES Decrypt

Decrypt AES ciphertext in your browser. Supports GCM, CBC, CTR, and ECB modes with 128/192/256-bit keys. Password never transmitted.

RSA Encrypt

Encrypt text with RSA-OAEP using a public key in your browser. Generate RSA-2048 or RSA-4096 key pairs. Max ~190 bytes plaintext. Nothing uploaded.

SHA-256 Hash Generator

Generate SHA-256 hashes from text instantly. WebCrypto hardware-accelerated, real-time output. Used in Bitcoin, TLS, and digital signatures. Zero uploads.

Base64 Encoder

Encode text or binary files to Base64 or Base64URL. Supports MIME line wrapping, data URIs, and files up to 50 MB. Fully browser-based.

Password Generator

Generate cryptographically secure passwords with custom length (8–128), character sets, entropy display, and exclude-ambiguous option. Runs in your browser.

Learn more

API Authentication Methods Compared: OAuth, JWT, API Keys

Compare API authentication methods with real HTTP examples. OAuth 2.0, JWT, API keys, and session tokens explained. 78% of breaches involve weak auth.