Runs locally in your browser. Nothing you enter is uploaded to our servers.
Tips for AES demos
Educational only — do not encrypt production data here.
AES needs a strong random key and a unique nonce/IV per message.
GCM provides authenticity; “raw” modes without auth are risky.
Never reuse the same nonce with the same key.
Prefer Web Crypto / vetted libraries over hand-rolled crypto.
AES as a browser demo
Processing stays in your browser — your input is not uploaded to our servers.
AES is a symmetric block cipher: the same secret encrypts and decrypts. This page shows the round-trip with a key you type.
A demo is not a protocol. Real use needs a random IV/nonce, authenticated encryption (GCM), and key storage you did not invent tonight.
Try the AES demo
Enter a sample and a demo key
Do not use a production key or customer data.
Encrypt, then decrypt
Confirm the plaintext returns. If it does not, the key or encoding does not match.
Stop there
Copying ciphertext into a real product without GCM and key management is how data gets lost.
AES demo FAQ
Is AES broken?
AES itself is standard. Demos fail when people reuse IVs, skip authentication, or hard-code keys.
Where should I store the key?
Not in this page and not in a git repo. Use a KMS or OS keystore in real apps.
Does ciphertext go to a server?
No. The demo is local.