Runs locally in your browser. Nothing you enter is uploaded to our servers.
Tips for generating JWTs
Generated tokens are for demos and local testing only.
Never use demo secrets in production.
Keep payloads minimal — JWTs are often readable without encryption.
Set sensible exp and avoid huge lifetimes.
Sign and verify with the same algorithm and key material on the server.
Mint a test JWT, not a production issuer
Processing stays in your browser — your input is not uploaded to our servers.
This builds a signed JWT from claims and a key you supply so you can hit a local API that expects a bearer token.
Tokens created here are as sensitive as the key. Do not point them at a production audience.
Generate a test JWT
Fill claims and a test key
Set `sub`, `exp`, and `aud` to what your stub API checks.
Sign
Copy the three-part token into Authorization: Bearer …
Throw it away after the test
Rotate the test secret if it ever leaked into logs or a ticket.
JWT generate FAQ
Will this token work on a public IdP?
Only if that IdP uses the same key — which it should not. Use this against your own test verifier.
Is the key uploaded?
No. Signing is local.
Which algorithm?
Match the verifier. HS256 with a shared secret is common in demos; asymmetric algs need a real key pair.