JWT Generator & Verifier - Sign JWTs Online
Sign JWTs locally in your browser with HS256/HS384/HS512, customize the header and payload, set expiry, and verify signatures and time claims. Secrets never leave your device.
Sign JWT
Verify & Decode
Signing and verification use Web Crypto locally. Secrets and tokens are never sent to a server.
About This Tool
The JWT generator puts signing and verification on one page: fill in the header and payload, choose an expiry, and sign with HS256, HS384 or HS512. A second panel verifies the signature and checks time claims.
Signing uses the browser's Web Crypto API, so secrets and tokens stay in local memory. It is useful for creating a test token during API integration or diagnosing an authentication failure.
HS256, HS384 and HS512 are supported.
Verification checks the signature, exp and nbf, and decodes both segments for inspection.
Key Features
Three HMAC algorithms
HS256, HS384 and HS512 cover common server-side signing setups.
Editable header and payload
Edit JSON directly; iat and exp are added automatically and syntax is validated.
Full verification
Check the signature and detect expired or not-yet-valid tokens.
Fully local
Secrets never leave the browser and no token data is uploaded.
When to Use It
API integration
Generate a test token with roles and an expiry for protected endpoints.
Diagnose 401 errors
Check the signature, expiry and claims to find the cause quickly.
Teach JWT
Break down the three segments and show how claims map to the signature.
How to Use It
- 1Choose an algorithm and enter a secret.
- 2Edit the header and payload, then set an expiry.
- 3Generate and copy the token.
- 4Paste a token and secret into the right panel to verify.
Frequently Asked Questions
Is RS256 supported?
No. The tool intentionally supports HMAC only to avoid handling private keys in the browser.
Is the secret stored?
No. It exists only in page memory and disappears on refresh or close.
Can I use the token in production?
It is fine for testing. Production secrets should stay on the server, not in a browser workflow.
