Free JWT Generator (HS256)
Build a signed HS256 JSON Web Token for testing · edit the payload, set a secret, and copy the token. Everything runs locally via Web Crypto.
100% client-side · nothing you enter is ever sent to a server or stored.
Preview · sign in with a free account to run it
Token = base64url(header) · base64url(payload) · HMAC-SHA256 signature, joined with dots · signed entirely in your browser.
How to use it
- Edit the header and payload JSON. The sample payload has a sub, an iat set to now and an exp one hour later.
- Enter the HMAC secret your test server verifies with.
- Copy the signed HS256 token and use it in a request.
Example
Input
Header {"alg":"HS256","typ":"JWT"}
Payload {"sub":"user_123","role":"admin","iat":1795046400}
Secret demo-secretResult
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyXzEyMyIsInJvbGUiOiJhZG1pbiIsImlhdCI6MTc5NTA0NjQwMH0.mKEnDA9FEn5H_AdH1Y0trKovhdiHytNnlHI2z8fHp38
Claims worth setting
- sub
- Who the token is about, usually the user ID.
- exp
- When it expires, in Unix seconds. Always set one, so a leaked test token doesn't work for ever.
- iat
- When it was issued, in Unix seconds.
- aud and iss
- Who the token is for and who issued it. Servers should check both.
- Invalid JSON
- The tool won't sign until the header and payload are valid JSON objects. Check quotes and commas.
Go deeper
Page updated
Frequently asked questions
Is it safe to paste a real secret here?
The signing runs entirely in your browser · nothing is transmitted. Still, treat any secret that has touched a third-party page as compromised in principle: for production keys, rotate rather than reuse.
What claims should a JWT include?
At minimum: exp (expiry · keep it short, minutes not months), iat (issued at), and sub (the subject). Add iss and aud so tokens can't be replayed across services. Never put passwords or PII in claims · JWTs are readable by anyone who holds them.
Can I create tokens for my production Supabase project?
Technically yes, if you have its JWT secret, which is exactly why that secret must never leave your server. Use a separate test project for experiments.
How do I check the token I made?
Paste it into the JWT Debugger to decode it, check the claims, and verify the signature with the same secret.
Want the full picture?
This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.
Run a full security scanRelated tools
HMAC Generator
Compute an HMAC signature from a message and secret key · SHA-256/384/512, hex or Base64 output, all in your browser via Web Crypto.
PKCE Generator
Generate a spec-compliant PKCE pair · a random code_verifier and its SHA-256 code_challenge · for testing OAuth 2.0 authorization-code flows.
Basic Auth Generator
Turn a username and password into a ready Authorization: Basic header · encoded locally, never transmitted.