JWT Decoder
Decode JSON Web Tokens (JWT) instantly with this free client-side JWT decoder. View the header, payload, signature, and token claims securely in your browser.
Loading tool…
What is a JWT?
A JSON Web Token is a compact, URL-safe credential defined in RFC 7519. It has three parts separated by dots: a header saying which algorithm signed it, a payload of claims such as the subject, issuer, audience, and expiry, and a signature. The first two parts are Base64URL-encoded JSON — encoded, not encrypted. Anyone holding the token can read everything inside it.
That last point is the one that catches people out. The signature does not hide the contents; it proves the token has not been altered and was issued by someone holding the signing key. Decoding a JWT therefore requires no secret at all, while verifying one requires the key. Put nothing in a JWT payload that you would not be comfortable showing to the bearer, because they can read it in a second.
Why we built this tool
Debugging authentication means reading tokens: checking whether exp has passed, whether the roles claim contains what the gateway expects, whether the audience matches, or why one service accepts a token another rejects.
Those are live session tokens. Pasting one into a website means transmitting a working credential to a third party — if it has not expired, whoever receives it can use it. That is the single strongest argument for a client-side tool, and it is why ours decodes purely in your browser: the split, the Base64URL decode, and the JSON parse all happen in your tab, with no network request. The token is never sent anywhere. Even so, treat any token you have pasted anywhere as worth rotating.
Tips and common mistakes
- Decoding proves nothing about validity — only the signing key can verify a token.
- Times in
exp,iat, andnbfare Unix seconds, not milliseconds; a thousandfold error makes a token look valid until the year 56000. - Clock skew between servers is a frequent cause of a token being rejected as expired or not-yet-valid.
- Rotate any token you have pasted anywhere, and never share a live one in a ticket or chat.
Open JWT Decoder with a link
Assistants and scripts can open JWT Decoder with its input already in the link, after the #, which never leaves your device:
#text=— the text to work on
Example: https://mygadgets.ink/tools/jwt-decoder/#text=... · also compressed gz fields and ?url=. How tool links work
Quick start: using JWT Decoder
- Paste the token into the input above — the whole string, including both dots.
- Read the decoded header to see the signing algorithm.
- Read the payload claims, starting with
exp,iat,iss, andaud. - Compare those against what the rejecting service expects.
- Remember that decoding is not verification; only the signing key can prove the token is genuine.
For raw encoding work, see Base64 Encoder/Decoder, and Timestamp Converter turns the numeric exp claim into a readable date.
The three parts of a JWT
A JWT has three Base64URL-encoded sections joined by dots:
- Header — the token type and the signing algorithm used.
- Payload — the claims: user ID, roles, issue time, expiry, and any custom data.
- Signature — a cryptographic check that proves the token has not been tampered with.
The dots separate them. Decoding reads the header and payload; the signature is verified with a secret key, not read.
The security truth: encoded, not encrypted
This trips up newcomers constantly. A JWT payload is not secret. Base64 is encoding, not encryption — anyone who has the token can decode and read every claim in it. The consequences:
- Never put sensitive data in a JWT payload. No passwords, no secrets, no private personal data. Assume the client can read it, because they can.
- The signature provides integrity, not secrecy. It proves the token was not altered, but does nothing to hide the contents.
- Trust comes from verifying the signature server-side with the secret key — not from the payload looking valid.
Reading the important claims
exp— expiry, as a Unix timestamp. Convert it with Timestamp Converter to see the real date and check whether the token is stale.iat— when it was issued.sub— the subject, usually the user ID.- Custom claims — roles, permissions, tenant, and so on.
Common uses
- Debug an auth flow by inspecting what the token actually contains.
- Check why a token is rejected — often it has simply expired.
- Confirm the claims your backend is issuing.