JWT Decoder
Paste a JSON Web Token to inspect its header and payload.
This tool only decodes the token — it does not verify the signature.
Related Tools
// more about this tool
Why use this tool
A JWT has three Base64Url-encoded segments separated by dots: a header, a payload, and a signature. This tool decodes the header and payload back into readable JSON so you can inspect the claims (expiry, subject, custom fields) directly, without writing a script just to peek inside a token your app just received.
Does this tool verify the signature? No — and it's worth stating plainly: it cannot, since verification requires the secret or public key the token was signed with, which never leaves your auth server. Anyone can decode a JWT and read its contents, including an attacker holding a token they didn't legitimately receive. Decoding tells you what a token claims; it says nothing about whether those claims are trustworthy. Verification always has to happen server-side, against the actual signing key, before you trust anything in the payload.
How it works
- Paste the full JWT string (header.payload.signature) into the textarea.
- The header and payload decode automatically, with no button to click.
- Check the Algorithm, Expires, and Valid/Expired summary bar below the two JSON panels.
- Copy either decoded JSON block independently if you need to paste it elsewhere.
Example
Decoded payload of a typical token
{
"sub": "user_123",
"name": "Bilal Fali",
"iat": 1760000000,
"exp": 1760003600
}FAQ
Does this tool verify the signature?
No. It only decodes the header and payload back into readable JSON — it never checks whether the signature is valid, because that requires the signing key, which this tool never has access to.
Can someone steal my token by pasting it here?
Nothing you paste leaves your browser — decoding happens entirely client-side. That said, treat any token-handling tool, including this one, the way you'd treat any clipboard paste of a secret: avoid pasting production tokens into tools you don't control as a general habit.
Why does exp look like a strange number instead of a date?
The exp (and iat) claims are Unix timestamps — seconds since January 1, 1970 — not human-readable dates. This tool converts exp into a readable date and an Expired/Valid badge automatically so you don't have to do that math yourself.
What's the difference between the header and the payload?
The header describes how the token is signed (typically the alg and typ claims); the payload carries the actual claims about the subject — who it's for, when it expires, and any custom data your auth system attached.
Why does the Algorithm shown sometimes say HS256 or RS256?
That value comes straight from the header's alg claim and names the signing algorithm the issuer used — HS256 is a shared-secret HMAC scheme, RS256 is RSA public/private key signing. Knowing which one your backend expects is often the first thing to check when signature verification fails server-side.