Interactive Utility · Client-Side Only

JSON Web Token (JWT) Decoder

⚠️ This tool decodes — it does not verify signatures. A JWT's header and payload are only base64url-encoded, not encrypted, so anyone can read them without the signing key. That's all this tool does. It cannot confirm a token is authentic or unmodified — only a server holding the correct signing secret or public key can do that. Never paste a production signing key or secret into any online tool, including this one.

Claim Summary

Why this tool doesn't verify signatures

Verifying a JWT's signature requires the same secret (HMAC algorithms like HS256) or public key (RSA/ECDSA algorithms like RS256, ES256) that the issuing server used to sign it. A tool that invited you to paste that secret into a browser field to "verify" a token would be teaching a habit — pasting signing secrets into random web tools — that eventually leads to a real production secret ending up somewhere it shouldn't. Decoding is safe to do anywhere, on any token, because the payload was never confidential in the first place. Verification is a server-side concern and belongs in your backend's JWT library, not in a browser tool.

What do the standard claims (exp, iat, nbf, sub) mean?

iat (issued at) and exp (expiry) are Unix timestamps marking when the token was created and when it stops being valid. nbf (not before) marks a time before which the token should be rejected even though it's already signed. sub (subject) typically identifies the user or entity the token represents. None of these are enforced by the token itself — enforcing them is the receiving server's job.

What does it mean if the algorithm is "none"?

"alg": "none" is a valid but dangerous JWT header value meaning the token is intentionally unsigned. A server that doesn't explicitly reject none tokens can be tricked into accepting a token an attacker forged by hand. If you see this in a token you didn't generate yourself for testing, treat it as a signal to check your server's JWT library configuration, not as normal behavior.

Why does a valid-looking token sometimes fail to decode here?

A JWT must have exactly three base64url segments separated by periods. Truncated tokens (common when copying from a terminal that wraps or clips text), tokens with extra surrounding whitespace, or a payload that isn't valid JSON once decoded are the most common causes of a decode failure here.