JWKS Generator
Generate key pairs (RS256, PS256, ES256, ES384 or EdDSA), manage kid values, and create JWKS (JSON Web Key Sets)
containing public keys only. You can also sign JWTs using the generated private key, inspect the payload, and copy keys, JWKS, or tokens with a single click.
Keys are created locally and never uploaded anywhere.
The JWKS contains only the public key.
Thumbprint (RFC 7638): -
The signature uses the generated private key and the selected algorithm.
Verify a JWT
Check a token against a JWKS: signature, expiry, kid. Everything runs in your browser.
Convert key formats (PEM ⇄ JWK)
Turn a PEM public key, private key (PKCS#8) or X.509 certificate into a JWK, or a JWK / JWKS into PEM. RSA, EC (P-256, P-384, P-521) and Ed25519 are detected automatically. Everything runs in your browser; keys are never sent anywhere.
GuideHow to use & features
- Optionally enter a kid, then click “Generate 2048-bit RSA keys” to create the key pair and JWKS.
- Copy the public key as a JWKS (JSON Web Key Set) and keep the private key in PKCS#8 PEM format.
- Edit the payload JSON and click “Create JWT” to generate an RS256-signed token.
SamplesSample input & output
Publish an RSA key
Algorithm: RS256 Key ID: demo-key
{
"keys": [
{
"kty": "RSA",
"kid": "demo-key",
"alg": "RS256",
"use": "sig",
"n": "u0fKsY6LQyqQy1vny7H2X7bqY7HWe8soT0x6XPrmT5w",
"e": "AQAB"
}
]
}FAQFAQ
What is generated?
An RSA key pair (2048 bits) for RS256. The private key (PKCS#8 PEM), public key (SPKI PEM), the public key as a JWK and a JWKS in `{"keys": [...]}` form all appear at once.What should I put in `kid`?
If left empty, a random UUID is used. When the `kid` in a JWT header matches the `kid` in the JWKS, the verifier can pick the right key.Where should I publish the JWKS?
A public-key JWKS is usually served at a URL such as `/.well-known/jwks.json`, and verifiers fetch keys from it. Never publish the private key.Can it sign a JWT?
Yes. Enter a payload and it creates an RS256 JWT with the generated private key and `kid`. If you have not written `iat`, the current time is added.Are the generated keys saved?
No. They disappear when you reload the page, so copy the keys you intend to use and store them yourself.Are my keys sent anywhere?
No. Key generation and signing both happen in your browser.How do I make a JWKS from a PEM public key I already have?
Paste the PEM that starts with BEGIN PUBLIC KEY into the "Convert key formats" card of the JWKS Generator, tick "Set kid to the thumbprint", and convert. Put the resulting JWK inside {"keys": [ … ]} and you have a JWKS. If you paste a private key (BEGIN PRIVATE KEY) the secret values appear too, so do not use that output for publishing.
Use casesCommon use cases
Preparing a signing key and JWKS for dev and test environments
Quickly set up a local or staging environment where you issue JWTs like your own auth server and verify them with a JWKS.Testing JWT verification code
Create your own key pair and JWTs and check that the verifying code correctly judges a valid signature, a wrong signature and a different `kid`.Checking the JWKS format
See on a real example how `kid`, `use`, `alg` and so on are attached to a public-key JWK.Building an OIDC mock
Put the public-key JWKS on a mock server and hand over tokens signed with the private key to try the integration.
NotesNotes & limitations
These are keys for development and testing
A private key shown on screen can remain in history or the clipboard. Do not create production keys here; create them in a managed environment such as an HSM or KMS.Only RSA 2048-bit (RS256)
ES256, EdDSA, RS512 and other RSA sizes are not supported.The JWKS holds only the one generated key
It cannot build a JWKS with several keys or the old-and-new keys of a rotation. If you need that, generate several times and combine them into the `keys` array by hand.Keys are not saved
Reloading or pressing generate again discards the previous key. If you want to verify a signed JWT later, keep the key with it.
AboutAbout this tool
JWKS & RSA Key Pair Generator
Instantly generate JSON Web Key Sets (JWKS) and RSA key pairs (public/private keys) directly within your browser.
This security tool is invaluable when mocking authentication servers adhering to OIDC (OpenID Connect) and OAuth 2.0. It saves you the hassle of running manual OpenSSL commands locally, allowing you to quickly set up token signing verification for your test endpoints.
Articles for this tool
What is JWKS (JSON Web Key Set)?
How JWKS works: each JSON field, its use in JWT signature verification, and key rotation. Generate an RSA key pair and see JWKS and PEM formats in your browser.
JWT Security Deep Dive: Attack Vectors, JWKS, and Production Best Practices
A guide to JWT security: the alg:none attack, algorithm confusion, key management with JWKS, token revocation strategies, and a production security checklist.
