JWT Sign & Verify (RS256, PS256, ES256 and more)
Create and check JSON Web Tokens signed with public-key algorithms (RS256/384/512, PS256/384/512, ES256/384/512).
Use the tool
Why this tool exists
Choose generate, sign or verify. Generating creates a key pair and prints PKCS#8 and SPKI PEM plus the public JWK. Signing takes a JSON payload and a PKCS#8 private key (PEM or JWK) and returns the compact token; ECDSA signatures use the raw r||s form the JWS spec requires. Verifying checks the signature with a public key and shows the payload.
The algorithm is chosen by you, never by the token header (a basic defence against algorithm-confusion attacks); verification checks the signature only, so real code must also check exp, nbf, iss and aud. Output was cross-checked with the jsonwebtoken library in both directions.
The file is read in your browser and is not uploaded anywhere.
How to use it
- Pick an algorithm and generate a key pair.
- Switch to sign, paste the payload and the private key.
- Copy the token, or switch to verify and paste a token with the public key.
- Never paste production private keys into a page you do not control.
Frequently asked questions
Which algorithm should I use?
ES256 is compact and fast; RS256 is the most widely supported; PS256 is RSA with a modern padding scheme.
My key says BEGIN RSA PRIVATE KEY.
That is the older PKCS#1 form. Convert it: openssl pkcs8 -topk8 -nocrypt -in key.pem -out pkcs8.pem.
Does it check expiry?
No. Verify the claims in your application code.
Is my data sent anywhere?
The file is read in your browser and is not uploaded anywhere.