Generator
Generate RSA public and private key pairs locally in your browser, choose a realistic usage profile, and export PEM output for signing, encryption, testing, or infrastructure setup.
Common key profiles
Current competitors are strongest when they make real usage profiles obvious. Start from a signing or encryption preset, then adjust the modulus length if you need to.
2048-bit keys are the normal baseline today. 4096-bit keys add cost but may fit longer-lived or more conservative security policies.
Pick signing when you need JWT or signature flows. Pick OAEP when the pair is meant for RSA-based encryption and decryption work.
Format
PEM export
Public key
SPKI
Private key
PKCS#8
Key safety note
Tools like 8gwifi and JSEncrypt make generation easy, but the private key still needs careful handling. Download it only when you are ready to store it securely.
Usage note
Signing and encryption are different workflows. Use PKCS#1 signing for JWT or signatures, and OAEP when the pair is meant for RSA encryption/decryption.
Private key
Treat this as secret material. Store it securely and keep it out of client-side or public distribution paths.
Public key
Use this for verification, distribution, or encryption targets depending on the selected key profile.
How to Use This RSA Key Generator
Use this tool when you need a clean, browser-based way to create an RSA keypair for signing, verification, encryption tests, or local security workflows.
Pick the key size
Use 2048-bit RSA for most everyday signing and compatibility needs, or move to 4096-bit when you want a larger security margin.
Choose the intended algorithm mode
Match the output to your workflow, whether you are generating keys for JWT signing, application encryption tests, or local infrastructure setup.
Generate the keypair in the browser
The tool creates the public and private keys locally and exports them in PEM format so they are easy to move into apps and services.
Store and use the keys safely
Keep the private key in a secure vault or environment-specific secret store and only distribute the public key where verification or encryption is needed.
When This Tool Is Most Useful
RSA is still a practical tool for identity, signing, and interoperability work. This generator is most helpful when you need fresh local key material without reaching for OpenSSL commands or external web generators.
JWT and auth signing
Generate asymmetric signing keys for RS256-based token flows where the signer holds the private key and downstream services verify with the public key.
Encryption and decryption testing
Prototype public-key encryption flows during development when you need to validate how a service encrypts data for a specific private key holder.
Infrastructure and SSH-style setup
Prepare local key material for infrastructure experiments, access control demos, certificate-related workflows, or environment bootstrapping.
Developer docs and example payloads
Use safe generated keypairs in internal documentation, training guides, or proof-of-concept code without exposing any real production secret.
FAQs
Does RSA key generation happen locally?
Yes. The tool uses browser cryptography APIs so the public and private keys are generated on your device instead of being sent to a remote service.Which key size should I choose?
For most development and production web scenarios, 2048-bit RSA is the baseline. Use 4096-bit if you specifically want longer keys and can accept the larger size and slower operations.What is the difference between the private and public key?
The private key must stay secret and is used for signing or decrypting. The public key can be shared and is used for verification or encryption depending on the workflow.Can I use these keys for JWT signing?
Yes. PEM-formatted RSA keypairs are commonly used for RS256 token signing and verification flows in development and production systems.