How to AES Encrypt Text
AES Encryption
When to Use AES Encryption
Encrypt sensitive text for local testing, debug application crypto flows, or verify that your key and IV produce expected ciphertext before integrating AES in production code. Useful for reproducing encrypted config values during development.
How It Works
This tool uses AES-GCM via the Web Crypto API. Provide a 128- or 256-bit AES key (hex or base64) and optionally a 12-byte IV. If IV is blank, a random IV is generated and shown in the output alongside the ciphertext. All processing runs locally in your browser.
Security Considerations
- Use cryptographically random keys and IVs — never reuse an IV with the same key
- Never encrypt production secrets in browser tools on untrusted machines
- Prefer established libraries and key management systems for production encryption
Frequently asked questions
Is my key sent anywhere?
No. Encryption runs entirely in your browser. Clear the key field after use on shared machines.
Which AES mode is used?
AES-GCM with a 12-byte IV. Use the same key, IV, and mode when decrypting.
Does this use PKCS7 padding?
No. AES-GCM is a stream-style authenticated mode — it does not use PKCS7 or zero padding. Block padding (PKCS7) applies to modes like AES-CBC, which this tool does not implement.