JWT decoder
Read header, payload and expiry
No database: AIMRAN doesn't store your files, text or results
What is JWT decoder?
A JWT (JSON Web Token) is a token many applications use to identify a user after logging in. It looks like an unreadable string, but it actually contains JSON data that this tool displays clearly.
Paste the token and you'll see its header, its contents and whether it has expired. If you know the secret key, you can also check that the signature is authentic.
How to use it
- Paste the JWT into the “Token” field, with or without the Bearer prefix.
- Review the header, the payload and the expiration status.
- Check under “Dates” when it was issued, when it becomes valid and when it expires.
- To verify the signature, enter the HMAC secret and indicate whether it's Base64.
Advantages
- Turns iat, nbf and exp into readable dates with relative time.
- Warns if the token has expired, isn't valid yet or isn't signed.
- HMAC signature verification (HS256, HS384 and HS512).
- Free, with no sign-up.
Use cases
- See which claims and permissions your API's login token carries while debugging a 401 error.
- Check whether a Bearer token copied from the browser dev tools has expired and when it runs out.
- Verify with the secret key that an HS256 token issued by your backend is correctly signed.
- Spot unsigned tokens with alg "none" before accepting them in an integration.
Technical details
The token is split into its three parts (RFC 7519), and the header and payload are decoded from Base64URL and parsed as JSON; the Bearer prefix is removed automatically. Five-part JWE tokens are detected and flagged as encrypted. The iat, nbf, exp and auth_time claims (Unix seconds) are shown as dates and compared with the current time to indicate whether the token is valid, expired or not yet valid. A warning is shown if alg is “none”. The HMAC signature is verified with the Web Crypto API (crypto.subtle.verify) over “header.payload” with SHA-256, SHA-384 or SHA-512 depending on the algorithm; the key can be entered as text or Base64. Asymmetric algorithms (RS, ES, PS) are decoded but not verified.
Frequently asked questions
What is a JWT?
A compact token with three dot-separated parts: header, payload (data) and signature. It's used for authentication and authorization in APIs and web applications.
How do I know if a JWT has expired?
Look at the exp claim in the payload. The tool converts it to a date and tells you whether the token is still valid or how long ago it expired.
Is decoding a JWT the same as verifying it?
No. Anyone can read the contents of a JWT. Verifying it means checking the signature with the key to make sure it hasn't been modified.
Can I verify RS256 tokens?
The tool decodes any JWT, but only verifies HMAC signatures: HS256, HS384 and HS512.
Is it safe to store sensitive data in a JWT?
Not in a regular signed JWT (JWS), because its payload is only Base64URL-encoded and can be read. JWE is used to hide data.
Blog guides
- What a JWT is, what is inside it and why decoding it is not validating it
- What Base64 is, when to use it and how to encode in JavaScript, Node and the terminal
Related tools
- Base64, URL and HTML · Encode and decode in all three formats
- Hash generator · MD5 and SHA for text or files
- Unix timestamp · Convert to a date and back
- JSON · Format, validate and minify
- URL parser · Parts, parameters and rebuilding
- UUID generator · Unique identifiers instantly