crypto::compare

International cryptographic algorithm reference across 12 categories.

C = Classical, PQ = Post-QuantumVisual Guide
Symmetric Encryption
The padlock on your data. One key locks it, same key unlocks it.
What it does
Every time you open a website, send a message, or save an encrypted file, symmetric encryption is doing the actual work. It takes your data and a secret key and scrambles the data so thoroughly that without the key, a supercomputer running until the heat death of the universe couldn't unscramble it. The "symmetric" part means both sides use the same key — which is blazing fast but creates a chicken-and-egg problem: how do you safely share that key in the first place? That's where KEM and key exchange come in.
Where you see it in the real world
When your browser shows a padlock icon, symmetric encryption (AES or ChaCha20) is encrypting every byte between you and the server. When you encrypt a hard drive with BitLocker or FileVault, that's AES. When WireGuard VPN tunnels your traffic, that's ChaCha20. When a government stamps a document TOP SECRET and encrypts it, that's AES-256. Every single HTTPS connection, every encrypted chat message, every secure file transfer — symmetric encryption is the workhorse doing the heavy lifting at the center of all of it.
Why it matters
This is the foundation everything else builds on. Key exchange negotiates a key, signatures verify who you're talking to, but symmetric encryption is what actually protects the data. Get this wrong and nothing else matters.
Your projects using this
AES-256-GCM for payload encryption
Sealed in the WordPRIVATE
AES-256-GCM with per-member key wrapping
AES-256-GCM encrypted QR file transfer
AES-256-GCMNIST StandardRecommended default
AES·🇧🇪 Belgium

General-purpose authenticated encryption. TLS 1.3, disk encryption, government classified data.

2 sources· Reviewed 2026-03-16
ARIA-256Korean Standard KS X 1213Acceptable (constrained)
ARIA·🇰🇷 South Korea

Korean government and financial systems.

2 sources· Reviewed 2026-03-16
Camellia-256CRYPTREC / ISO / IETFAcceptable (constrained)
Camellia·🇯🇵 Japan

Japanese government, TLS suites, NESSIE-approved applications.

2 sources· Reviewed 2026-03-16
ChaCha20-Poly1305IETF RFC 8439Recommended default
ChaCha·🇺🇸 United States

Authenticated encryption without AES hardware. Mobile, TLS 1.3 fallback, WireGuard.

1 source· Reviewed 2026-03-16
KuznyechikGOST R 34.12-2015Acceptable (constrained)
GOST·🇷🇺 Russia

Russian government and military systems.

2 sources· Reviewed 2026-03-16
SM4GB/T 32907 / ISO 18033-3Acceptable (constrained)
SM4·🇨🇳 China

Chinese government, banking, wireless LAN (WAPI).

2 sources· Reviewed 2026-03-16
XChaCha20-Poly1305IETF Draft / libsodiumRecommended default
ChaCha·🇺🇸 United States

File/at-rest encryption needing random nonces safely. libsodium default.

2 sources· Reviewed 2026-03-16
7 algorithms shown