About this tool
A JSON Web Token carries login or access information as three parts joined by dots. The header and payload are only Base64URL-encoded text, which this tool decodes so you can read them. It also turns exp, iat and nbf time fields into readable dates and warns you when a token has already expired.
It is useful when you are debugging an API, checking which claims a token holds, or finding out when it stops working.
How to use it
- Paste your token. A leading Bearer prefix is removed for you.
- Read the decoded header and payload below.
- Check the dates section to see when the token was issued and when it expires.
Good to know
- Decoding does not prove that a token is genuine. This tool does not verify the signature.
- A JWT payload is readable by anyone who has the token, so never put secrets in it.
- Treat real tokens like passwords. This page decodes them locally and does not send them anywhere, but avoid pasting production tokens into tools you do not trust.
Key features
- Instant result with copy or download.
- Validation with clear messages for bad input.
Limitations
- Results are only as good as the input; check them before you rely on them.
Privacy and security
Runs in your browser; the file is not sent to any server.
Frequently asked questions
Is it safe to paste my JWT here?
The token is decoded in your browser and is not sent to us. Still, treat live tokens as secrets and prefer test tokens when you can.
Does this verify the signature?
No. Verifying needs the secret or public key and should be done in your server code.
What do exp, iat and nbf mean?
exp is when the token expires, iat is when it was issued and nbf is the time before which it must not be accepted. They are Unix timestamps in seconds.
Why does it say the token could not be decoded?
The text is probably cut short or has extra characters. Paste the whole token, from the first character to the last.
More tools you may need
Related guides
Last reviewed: 2026-11-22. Found a mistake? Tell us. See our tool accuracy policy.