RSA Key Generator

Choose 2048 or 4096 bits.

Use this tool

Result

The result appears in this panel after you run the tool.

About this tool

Keys are created with Web Crypto in this browser.

The private key is shown for you to copy. It is not chained and it is not sent to analytics.

How to use it

  1. Open this page and provide the input it asks for.
  2. Set the options that are visible, then use Generate keys.
  3. Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.

Limitations

RSA-OAEP keys as SPKI and PKCS8 PEM

The parameters Web Crypto is given

The bit length must be 2048 or 4096. Anything else throws. The key pair is generated as RSA-OAEP with public exponent 65537 and hash SHA-256, with usage encrypt and decrypt. The public key is exported as SPKI and the private key as PKCS8. Each export is base64-wrapped as PEM, with a BEGIN and END line and line breaks every 64 characters. PEM is an encoding of the key bytes so you can copy them. It is not a cipher around the key. The base64 is reversible by anyone who sees the PEM.

The page generates keys. It does not encrypt a message, and it does not sign one. OAEP with SHA-256 is the algorithm these keys are for. They are not labeled as RS256 signing keys, and they are not PKCS#1 v1.5 encryption keys. A consumer that expects a different padding will reject them even though the modulus length looks familiar. SSH wire format and certificate requests are not produced.

The private key is on the screen

Both PEM blocks are shown so you can copy them. The private key is not placed in the chained artifact, and analytics never receives the PEM. That still means the key exists in the page in this browser. Copy it into a place you control, then treat the screen as sensitive. A screenshot or a shared machine is a real exposure. The generator does not set a passphrase on the PKCS8 export. The PEM is unencrypted. If you needed a passphrase-wrapped key file, this export is not that file.

What to generate instead when RSA is the wrong shape

A fresh UUID does not encrypt. An HMAC key is a symmetric secret you type or generate as bytes, not a modulus. AES on this site is a password and AES-GCM, not this key pair. Use these PEM blocks when a system asked for an RSA-OAEP key of 2048 or 4096 bits with SHA-256. Use something else when the system asked for a signature algorithm, a curve, or a symmetric key. Generating the wrong type and hoping the PEM header is enough will fail at the import, not here. This page only checks the bit length and then shows the armor.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.