b2KIT

Encryption Key Generator

Generate random AES-128, AES-256, and RSA key pairs using the Web Crypto API for development and testing.

Tested tool guide Tested browser tools Checked August 16, 2026

What Encryption Key Generator does and how it behaves

Select AES-128, AES-256, or RSA to generate new cryptographic key material with the browser's Web Crypto API. AES generation produces one symmetric key, while RSA generation produces a mathematically linked public and private key pair. Generation happens locally in the browser, and this tool does not upload the keys. The important distinction is that these results are random, not derived from a password or other repeatable input. Running the same option twice should therefore produce different key material.

How the result is produced

1

AES key generation

The AES-128 option creates a 128-bit symmetric key, and AES-256 creates a 256-bit symmetric key. One secret key is used on both sides of an AES operation. The tool requests fresh key material from Web Crypto each time; it does not turn entered text into a key. AES key generation alone does not supply an encryption mode, initialization vector, nonce, or authentication tag.

2

RSA pair generation

The RSA option creates two related components rather than a single shared secret. The public key can be given to a party that needs its public role, while the private key must remain confidential. The exact operation permitted by an RSA key depends on its algorithm parameters. A key intended for encryption is not automatically suitable for signatures, even though both may be described as RSA keys.

Good uses

  • Create a temporary AES-128 or AES-256 key for checking whether an encryption and decryption test accepts the expected key length.
  • Generate a disposable RSA public/private pair for testing key import, key export, or a public-key round trip without reusing operational credentials.
  • Obtain representative symmetric and asymmetric key material while designing configuration fields, validation rules, fixtures, or documentation for software that handles both AES and RSA.

Limits and checks

  • There is no deterministic example output to reproduce. Each generation uses fresh randomness, so save the generated material if a later test must use that exact key.
  • A generated key is only one part of a cryptographic operation. AES still requires choices such as mode and nonce handling, while RSA requires compatible algorithm parameters and an appropriate encryption or signature scheme.
  • Key length does not identify the representation expected by another program. Confirm whether the destination expects raw bytes, JWK, SPKI, PKCS #8, or another supported form before treating displayed key material as directly interchangeable.

Common questions

Can I regenerate the same key by selecting the same option again?

No. AES-128, AES-256, and RSA selections describe the kind of key to generate, not a seed or recipe for reproducing one. A later generation creates different key material. If a test must be repeatable, preserve the original generated key in a suitable test-secret location and import that saved value for subsequent runs.

Should I use a key from this generator in production?

Not automatically. Web Crypto is designed for cryptographic operations, but production suitability also depends on the page environment, algorithm parameters, key representation, access controls, storage, rotation, backup, and exposure through the clipboard or browser extensions. This generator is described for development and testing. Use an approved production key-management process when your system or organization requires one.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools