What's inside a JWT?
A JWT is three Base64URL pieces joined by dots: header.payload.signature.
- Header: how the token is signed, e.g.
{"alg":"HS256","typ":"JWT"}. - Payload: the claims, like the user (
sub), issuer (iss) and expiry (exp). - Signature: proves the token wasn't changed. Checking it needs the secret or public key.
Decoding is not verifying. Anyone can read a JWT's payload, so never put secrets in it, and always verify the signature on your server. To test with your own test secret or public key, paste it on the Signature card.
How to use it
- Paste a token into the Token box. A
Bearerprefix from anAuthorizationheader is fine. The header, payload and signature light up in their own colors, the same as the dots on the cards. - Read the Header card: every field it knows is explained (how the token was signed, which key, what type).
- To check the signature, paste the secret or the public key into the box on the Signature card: it says whether the signature matches. Test secrets only.
- Read the Payload card: the claims are listed with readable dates, and the badge tells you whether the token has expired.
- Copy the header or payload as formatted JSON with the Copy buttons.
Example
This token was signed with HS256 and the demo secret nifty-dev-tools-demo (the Example button uses the same
secret). In the input, the header, payload and signature each have their own color, the same as the dot on their card:
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6ImRlbW8tMjAyNiJ9.eyJpc3MiOiJodHRwczovL2F1dGguZXhhbXBsZS5jb20iLCJzdWIiOiJ1c2VyXzhmM2EyYyIsIm5hbWUiOiJBZGEgTG92ZWxhY2UiLCJyb2xlIjoiYWRtaW4iLCJpYXQiOjE3OTUwNDY0MDAsImV4cCI6MTc5NTA1MDAwMH0.6J7SfkIOwHNqeAjWxt02jXB7GcEWyB0NrPuuyuPNX9c
The header says it's a JWT signed with HMAC SHA-256 (alg HS256) by the key demo-2026 (kid). The payload:
{
"iss": "https://auth.example.com",
"sub": "user_8f3a2c",
"name": "Ada Lovelace",
"role": "admin",
"iat": 1795046400,
"exp": 1795050000
}
iat 1795046400 is 19 November 2026, 00:00:00 UTC, and exp is one hour later, 01:00:00 UTC.
The header, explained
| Field | Meaning |
|---|---|
alg | How it was signed: HS256 with a shared secret, RS256 or ES256 with a key pair, none not at all |
typ | The kind of token, usually JWT |
kid | Which of the issuer's keys signed it |
The Header card explains every field it finds, in plain words.
Common claims
| Claim | Meaning |
|---|---|
iss | Issuer: who created the token |
sub | Subject: usually the user ID |
aud | Audience: who the token is meant for |
exp | Expiration time (Unix seconds) |
nbf | Not valid before (Unix seconds) |
iat | Issued at (Unix seconds) |
jti | Unique token ID |
FAQ
Can you verify the signature?
Yes. Paste the secret (for HS256, HS384, HS512) or the public key (for RS, PS, ES and EdDSA tokens, as a PEM
-----BEGIN PUBLIC KEY----- or a JWK; a JWK Set works too, picked by the token's kid) into the box on the
Signature card. It's checked in your browser with its built-in crypto, and we never upload or store the secret or
key. Still, use test secrets only: check tokens from production on your server. The Example token verifies
with the demo secret nifty-dev-tools-demo.
Why does it say “encrypted token”?
Tokens with five parts are encrypted JWTs (JWE). Their payload can't be read without the decryption key.
Is it safe to paste a real token here?
The token is decoded in your browser, and we never upload, log or store it. Still, treat live tokens like passwords and prefer expired or test tokens when you can.