About this tool
Paste a JSON Web Token (JWT) to see its header and payload as readable JSON, the signing algorithm, and the issued-at, not-before and expiry times converted to dates — with a clear note whether the token is valid, expired or not yet valid. A “Bearer ” prefix is removed automatically. Decoding happens entirely in your browser.
How to use it
- Paste the token — from an Authorization header, a cookie or your app's storage.
- Read the status: valid, expired, not yet valid or no expiry.
- Check the claims in the payload and copy the header or payload as JSON.
Good to know
- A JWT has three base64url parts separated by dots: header, payload and signature. The colours under the input show each part.
- exp, iat and nbf are Unix timestamps in seconds; they are shown as dates in your time zone with a relative time.
- The signature is not verified. Checking it needs the secret or public key, which should stay on your server and never be pasted into a website.
- Anyone can decode a JWT — the payload is not encrypted — so never put passwords or private data in one.
What is inside a JWT
The header names the signing algorithm (such as HS256 or RS256). The payload holds claims: sub (the user), iss (who issued it), aud (who it is for), iat (issued at), nbf (not before) and exp (expiry), plus any custom data such as a role. The signature proves the first two parts weren't changed — but only to someone who holds the key.
Debugging with the decoder
“401 Unauthorized” with a token that looks fine? Check exp first — an expired token is the most common cause. Then check aud and iss match what your API expects, and that the role or scope claim your code checks is really there. Remember the time claims are in seconds, not milliseconds.
Security reminders
Decoding isn't verifying: never trust a payload in your backend without checking the signature with a proper JWT library. Don't store secrets in the payload, keep access tokens short-lived, and never paste production signing keys into online tools.
Frequently asked questions
How do I decode a JWT?
Paste it into the box. The header and payload are base64url-decoded and shown as formatted JSON, with the expiry and issue times turned into readable dates.
Does this verify the token?
No. It only decodes it. To trust a token, verify its signature on your server with the secret or public key — a decoded payload can be changed by anyone.
Why does my token show as expired?
Its exp claim is earlier than your device's current time. Access tokens are often short-lived (minutes to hours); your app should use a refresh token or sign in again.
Is it safe to paste a token here?
The token stays in your browser and isn't sent anywhere. Still, a valid token works like a password until it expires, so avoid sharing live production tokens.