JWT Decoder
Inspect any JSON Web Token's header and payload — decoded locally, never sent anywhere.
Header
Payload
What is a JWT decoder?
A JWT decoder reads a JSON Web Token and shows you the two readable parts inside it: the header, which describes the token type and signing algorithm, and the payload, which carries claims such as the user ID, issuer and expiry time. JWTs are the standard way APIs pass authentication and session information, so decoding a token is a routine debugging step for developers. Our free tool decodes any JWT in your browser — paste the token, click a button, and the header and payload appear instantly with the expiry highlighted.
How JWT Decoder works
- Paste the full JWT — the three Base64URL segments separated by dots — into the input box.
- Click Decode.
- The header and payload appear in their own panels as readable JSON. A separate line summarises the token's expiry from its
expclaim, when one is present. If the token is malformed, an error message tells you so.
Everything happens locally in the browser. The signature segment is read but never verified — decoding only shows you the token's contents; it does not prove the token is genuine.
Key features
- Header decoding: shows the algorithm (
alg) and token type (typ) as formatted JSON. - Payload decoding: shows every claim — subject, issuer, roles, scopes and anything else the issuer embedded.
- Expiry summary: surfaces the
expclaim so you can see at a glance whether a token is still valid. - Error reporting: malformed tokens produce a clear error instead of confusing output.
- Fully private: tokens are decoded in the browser and never sent to our servers.
Common uses
- Debugging logins: inspect the token your app received to confirm the right user and roles were issued.
- Checking expiry: read the
expclaim to see exactly when a token stops being accepted. - Verifying claims: confirm scopes, permissions and issuer values before wiring up authorization logic.
- Comparing environments: decode tokens from development and production to spot configuration differences.
- Learning JWTs: see how the header, payload and signature fit together in a real token.
Is it safe to use?
Yes, with one important caveat. Decoding happens entirely in your browser, so the token never leaves your device. But a JWT payload is only Base64URL-encoded, not encrypted — anyone holding the token can read its claims, so treat tokens as secrets. And remember this tool decodes but does not verify the signature: a readable token is not proof it is authentic. Always validate signatures on your own server.
Tips
- Decoding is not verifying. A payload tells you what a token claims, not that the claims are trustworthy — signature checks belong server-side.
- Check the
algvalue. The header names the signing algorithm; make sure it matches what your server expects. - Watch the expiry. Most authentication bugs trace back to an
expclaim that has already passed — check it first. - Paste the whole token. A JWT needs all three dot-separated parts; pasting only the middle segment will fail to decode.
Frequently asked questions
What does a JWT decoder do?
A JWT decoder splits the token into its three dot-separated parts, Base64URL-decodes the header and payload, and shows them as readable JSON. Our tool also summarises the expiry claim, so you can inspect a token's contents and lifetime in seconds.
Can I decode a JWT token online without sending it anywhere?
Yes. This tool decodes tokens entirely in your browser using JavaScript. The token you paste is never uploaded, logged or shared — nothing leaves your device. No account, key or sign-up is required — decoding starts the moment the page loads.
Does decoding a JWT verify its signature?
No. Decoding only reads the header and payload; it never checks the signature. A token that decodes cleanly can still be forged or tampered with. Signature verification must happen on your server using the issuer's secret or public key. Never trust claims from a token your server has not verified.
Why does my token fail to decode?
A valid JWT needs all three dot-separated parts with correct Base64URL encoding. Truncated tokens copied from logs, missing segments, or characters outside the Base64URL alphabet will fail. Re-copy the full token and make sure no whitespace or line breaks slipped in.
Is the payload of a JWT encrypted?
No. The payload is only Base64URL-encoded, which anyone can reverse in seconds — it is an encoding, not encryption. Never put passwords, keys or other secrets in token claims, because anyone holding the token can read them. Use a JWE when claims must stay private.
What is the exp claim?
The exp claim is a timestamp, in seconds since the Unix epoch, after which the token must no longer be accepted. Our tool surfaces this expiry so you can tell at a glance whether a token is still valid or has already lapsed.
Working with structured data too? Try our JSON Formatter to pretty-print copied payloads, or our Regex Tester to validate token formats in your code.