ASCII Table
The full ASCII table with decimal, hex, octal, binary and HTML entities.
Build and sign a JWT with HS256, HS384 or HS512 for testing.
Use a throwaway secret for test tokens. A secret typed into any web page should be treated as exposed.
The JWT Generator builds a token from standard and custom claims and signs it with HS256, HS384 or HS512, with helpers for iat and exp so you are not doing epoch arithmetic by hand.
Testing anything that consumes JWTs means having a supply of them, with the claims you need and an expiry that has not passed. This builds one: set the payload, choose an algorithm, provide the secret, and get a signed token.
The registered claims have helpers because they are the fiddly part. iat is filled with the current time, exp is set by picking a duration rather than doing epoch arithmetic, and sub, iss and aud have their own fields alongside whatever custom claims you add. Signing uses HMAC — HS256, HS384 or HS512 — which is what a symmetric secret supports; RS256 needs a private key and is deliberately out of scope for a browser tool.
Pick a duration and exp is calculated for you, with iat filled from the current time.
Dedicated fields for sub, iss and aud, plus a JSON box for anything else the token needs to carry.
The generated token is decoded back and shown, so you can confirm the claims came out the way you intended.
Signatures come from the browser’s own crypto, so the tokens verify correctly in any library.
RS256 needs a private key, and the page declines to accept one rather than encouraging the habit.
Fill the standard fields and add any custom claims as JSON.
Pick a duration and exp is calculated for you.
The shared signing key. Use a throwaway one for test tokens.
The signed JWT is ready to paste into an Authorization header.
HS256 unless something requires otherwise. The larger HMAC variants are rarely needed, and the real security comes from the secret being long and random rather than from the digest size.
At least as long as the digest — 32 bytes for HS256. A short or guessable secret makes the signature worthless, because an attacker can simply brute-force it offline against any token they hold.
No. That needs an RSA private key, and pasting one into a web page is a bad habit even when the page is honest about being local. Use your own tooling for asymmetric signing.
The tokens are correctly signed, so they work. But a secret typed into any web tool should be treated as exposed — generate production tokens on your own infrastructure.
What people who use the JWT Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the JWT Generator. It takes half a minute and no account.
Write the first reviewThe full ASCII table with decimal, hex, octal, binary and HTML entities.
Check any number against the Luhn checksum and see the working.
Estimate how long a password would survive, and see exactly what weakens it.
Generate complete fake user profiles for seeding and design work.
Check XML is well-formed and find the exact tag that breaks it.
Convert between signed and unsigned, with the negation steps shown.
Convert YAML config into JSON and see exactly how each value was typed.
Generate Go structs with json tags from a sample payload.