Your token
Paste a token to decode it.
How to
Read a token in three steps
- Paste the token Copy it from your app, an Authorization header or your logs. Whitespace and a Bearer prefix are ignored.
- Read the parts The header says how the token was signed. The payload holds the claims, such as who it is for and when it expires.
- Check the warnings The tool flags expired tokens, tokens not yet valid, no expiry, unsigned tokens and an empty signature.
Handling tokens safely
- A JWT payload is only encoded, not encrypted. Anyone who holds the token can read it, so keep secrets out of it.
- Decoding is not verifying. Only a server with the right key can tell whether the signature is genuine.
- Treat live tokens like passwords: do not paste them into sites you do not trust. This page never sends them, but a test token is still safer.
- Servers must reject tokens whose algorithm is "none" and should check the algorithm they expect, not the one the token claims.
FAQ
JWT decoder questions
Is my token sent to a server?
No. The token is decoded by code running in your browser. It is not sent, stored, shared in a link or placed in the address.
Does this verify the signature?
No. Verifying needs the secret or public key and should happen on your server. A token that decodes here may still be forged.
What do exp, iat and nbf mean?
exp is when the token expires, iat when it was issued and nbf the time before which it must not be accepted. All are seconds since 1 January 1970 UTC.
Why does it warn about alg "none"?
A token with algorithm none has no signature, so anyone can write one. Servers that accept it can be tricked into trusting forged identities.
Can it read an encrypted JWT?
No. Tokens with five parts are encrypted (JWE) and need the decryption key. This tool only reads signed tokens, which have three parts.