RSA Key Pair Generator
Generate an RSA key pair in the browser with selectable modulus size, hash, and signing or RSA-OAEP purpose, then export standard key representations.
Generated key pair
What is RSA Key Pair Generator?
Generate an RSA key pair in the browser with selectable modulus size, hash, and signing or RSA-OAEP purpose, then export standard key representations. Modulus size 2048, 3072, or 4096 bits; SHA-256, SHA-384, or SHA-512; signing or RSA-OAEP; optional OpenSSH comment. Private PKCS#8 PEM, public SPKI PEM, OpenSSH public key, JWK, and a SHA-256 fingerprint, with download actions.
Open the tool
What the tool does
- Input: Modulus size 2048, 3072, or 4096 bits; SHA-256, SHA-384, or SHA-512; signing or RSA-OAEP; optional OpenSSH comment.
- Controls and processing: Generation uses the Web Crypto API; export views must identify private versus public material unambiguously.
- Output: Private PKCS#8 PEM, public SPKI PEM, OpenSSH public key, JWK, and a SHA-256 fingerprint, with download actions.
How to use it
- Provide the input. Modulus size 2048, 3072, or 4096 bits; SHA-256, SHA-384, or SHA-512; signing or RSA-OAEP; optional OpenSSH comment.
- Review the settings. Generation uses the Web Crypto API; export views must identify private versus public material unambiguously.
- Generate, inspect, and export. Private PKCS#8 PEM, public SPKI PEM, OpenSSH public key, JWK, and a SHA-256 fingerprint, with download actions.
Key features
- Input: Modulus size 2048, 3072, or 4096 bits; SHA-256, SHA-384, or SHA-512; signing or RSA-OAEP; optional OpenSSH comment.
- Controls and processing: Generation uses the Web Crypto API; export views must identify private versus public material unambiguously.
- Output: Private PKCS#8 PEM, public SPKI PEM, OpenSSH public key, JWK, and a SHA-256 fingerprint, with download actions.
Useful workflows
- Generate an RSA key pair in the browser with selectable modulus size, hash, and signing or RSA-OAEP purpose, then export standard key representations.
- Use it when you need this deliverable or diagnostic result: Private PKCS#8 PEM, public SPKI PEM, OpenSSH public key, JWK, and a SHA-256 fingerprint, with download actions.
- Place it before the next verified workflow step: protecting the private key, testing interoperability, and obtaining a certificate where required.
Limits and safety notes
- Generation time depends on device and key size, so do not promise a fixed 5–15 seconds. A key pair is not a certificate; SPKI alone does not create mTLS, and OpenSSH compatibility depends on server policy.
Troubleshooting
- Use a non-production sample and provide every required version- or algorithm-specific field; generate or inspect one item before bulk output.
- Validate the result with an official or trusted implementation before use, and never place live secrets, passwords, tokens, or private keys in logs or URLs.
- Generation time depends on device and key size, so do not promise a fixed 5–15 seconds. A key pair is not a certificate; SPKI alone does not create mTLS, and OpenSSH compatibility depends on server policy.
Frequently asked questions
What is RSA Key Pair Generator?
Generate an RSA key pair in the browser with selectable modulus size, hash, and signing or RSA-OAEP purpose, then export standard key representations.
How do I use RSA Key Pair Generator?
Provide the expected input, review the page settings, then verify the result before copying or downloading it. Expected output: Private PKCS#8 PEM, public SPKI PEM, OpenSSH public key, JWK, and a SHA-256 fingerprint, with download actions.
What input does it accept?
Modulus size 2048, 3072, or 4096 bits; SHA-256, SHA-384, or SHA-512; signing or RSA-OAEP; optional OpenSSH comment.
What output does it produce?
Private PKCS#8 PEM, public SPKI PEM, OpenSSH public key, JWK, and a SHA-256 fingerprint, with download actions.
What are the limits?
Generation time depends on device and key size, so do not promise a fixed 5–15 seconds. A key pair is not a certificate; SPKI alone does not create mTLS, and OpenSSH compatibility depends on server policy.
Related AppKiro tools
Start with a verified input
Use a non-production sample first. Confirm the output with a trusted implementation and keep secrets, tokens, passwords, and private keys out of URLs and logs.
Open the tool