Generate an RSA key pair right in your browser. Choose 2048, 3072 or 4096 bits and the intended use, and get the public and private keys as PEM, the public key as JWK and as an OpenSSH line with its SHA256 fingerprint — ready to download. Nothing is stored or uploaded.
| Size | Security strength | Use until |
|---|---|---|
| 2048 | 112 bits | 2030 |
| 3072 | 128 bits | Beyond 2030 |
| 4096 | ~150 bits | Beyond 2030 |
3072 bits for use beyond 2030; 2048 is the minimum.
Web Crypto uses the OS's secure random generator and keys never leave the page. For production secrets many teams still prefer generating on the server.
PKCS#8 PEM, readable by OpenSSL, Node, Java, Python and Go.
Yes, though Ed25519 keys from ssh-keygen are preferred for SSH today.
No. Close the tab and they're gone.
Keys are generated by the browser's Web Crypto generateKey with public exponent 65537 and a cryptographically secure random source, for RSASSA-PKCS1-v1_5 (RS256), RSA-PSS (PS256) or RSA-OAEP. The key material is the same whichever you pick; the choice only sets the algorithm label on the JWK. The public key is exported as SPKI and the private key as PKCS#8 DER, Base64-encoded in 64-character lines inside -----BEGIN PUBLIC KEY----- and -----BEGIN PRIVATE KEY----- armour. The OpenSSH public key is built per RFC 4253: the string 'ssh-rsa', then the exponent and modulus as mpints, each with a leading zero byte when its top bit is set. Its fingerprint is the unpadded Base64 SHA-256 of that blob, matching ssh-keygen -lf. Keys live only in the page's memory and are never stored or sent.