AES Key & IV Generator

Copy interoperable raw key and IV bytes as hexadecimal or Base64 using cryptographically secure browser randomness.

AES key length

Key (hex)

Key (Base64)

IV (hex)

IV (Base64)

All cryptographic operations run locally in your browser. Keep private keys secret and use production key-management practices for real systems.

Batch AES key + IV inventory

Generate several Web Crypto AES keys at once and hand off exact bytes in hex/Base64URL with fresh 96-bit IVs.

128 / 192 / 256

Batch count

Key size

#	Key (hex)	Key (Base64URL)	IV (hex)

Generated material is local. IVs are fresh random values, but production key custody and nonce policy still belong in a real key-management design.

Practical guide and verification

Key size and representation

AES uses 128-, 192-, or 256-bit keys. Hex and Base64 are only text encodings of the same bytes; choosing a longer-looking representation does not change the underlying key strength.

Randomness matters

A cryptographic key should come from a cryptographically secure random source, not a memorable phrase, timestamp, ordinary pseudo-random function, or user ID.

Storage

Generating a strong key is only the first step. Store it separately from encrypted data, restrict access, plan rotation and backup, and never commit production keys to source control.

Browser-local cryptographic utilities

preserves the established Web Crypto workflows while connecting token, key, KDF, encryption/signature, fingerprint and verification jobs. Inputs stay in your browser unless the page clearly states that a network request is required.

Protocol boundary

Correct primitive output does not certify a complete protocol, key-management system, parameter choice, endpoint, or production deployment. Match the source system exactly and use established application/security libraries for production authentication and storage.