JWT Decoder (No Verification)
Paste a JWT to see its header and claims in readable JSON, including when it was issued and when it expires. It only decodes; it does not check the signature. Tokens stay in your browser.
- No watermark or limits
- Client-side only
- Shows exp, iat and nbf
- Does not verify signature
- Runs on your device. Files are never uploaded.
- Free and unlimited. No sign-up, no watermark.
JWT payload decoder (no verification) in three steps
No account, no email, no waiting for an upload.
- STEP 01
Paste the token
A 'Bearer ' prefix, quotes and line breaks are removed for you.
- STEP 02
Decode
The header and payload are base64url-decoded and parsed as JSON.
- STEP 03
Read the result
See the algorithm and claims, plus times in UTC with a relative note such as 'expires in 2 hours'.
What JWT payload decoder (no verification) does, and what it doesn't
We'd rather tell you up front than surprise you after the download.
What you get
- Header and payload in clear JSONPretty-printed, with all claims shown, including custom ones.
- Readable timesiat, nbf, exp and auth_time are shown as ISO dates in UTC, with how long ago or how far ahead they are.
- Expiry at a glanceThe summary line says whether the token has expired or when it will.
- Payload as a fileDownload the payload alone as a .json file to use elsewhere.
- Sensible checksA token with the wrong number of parts or invalid Base64URL gets a clear message. Encrypted tokens (JWE) are identified.
Good to know
- No signature verificationA decoded token is not a trusted token. Anyone can create a JWT with any claims. Verify signatures in your server code with the right key.
- Encrypted tokens cannot be readA five-part JWE needs its key to decrypt, which this tool does not do.
- Times are as claimedExpiry compares against your device's clock. If it is wrong, so is the status.
Your data never leave your device
The tool runs inside your browser instead of on our servers, so there is nothing to upload, store or delete afterwards.
Typical online tool upload
Your file travels over the internet, sits on someone else's computer for a while, and you wait for the upload and the download.
Mediaextractr no upload
The tool loads into your browser once, then works on your file locally. Nothing is sent, so nothing can leak.
When people use JWT payload decoder (no verification)
Debug login problems
Check the audience, issuer, scopes and expiry of a token that is being rejected.
Inspect third-party tokens
See which claims an identity provider includes.
Learn how JWTs work
See that the payload is readable by anyone.
Check token lifetime
Verify that a token's exp and iat match your configuration.
Mediaextractr vs typical upload tools
| MediaextractrPrivate | Typical upload tools | |
|---|---|---|
| Your file is uploaded | Never | Yes |
| Sign-up needed | No | Often, after a few files |
| Daily file limit | None | Often 1–2 free files |
| Watermark | Never | Sometimes |
| Wait for upload & download | No | Yes |
| Speed on very large files | Depends on your device | Depends on their servers |
What is inside a JWT
A JSON Web Token has three parts separated by dots: a header, a payload and a signature. The first two are JSON written in Base64URL, so anyone can read them. The signature proves the token was made by someone holding the key.
That is why you should never put secrets in a JWT payload. Decoding needs no key.
Handling real tokens carefully
Tokens are credentials, so treat them with care. This page decodes in your browser, but you should still follow good habits:
- Use expired or test tokens when you can.
- Do not share live tokens in tickets or chats.
- Check exp, iss and aud, then verify the signature on your server.
- Standard claims: sub (subject), iss (issuer), aud (audience), exp, nbf and iat.
- For the raw pieces, use Base64 decode; format the payload with the JSON formatter; convert timestamps with the Unix timestamp converter.
Reading the claims
The exp claim is the moment after which the token should be rejected, iat is when it was issued, and nbf is the earliest time it is valid. All three are Unix seconds. A large gap between iat and exp tells you the token lifetime. If exp is missing, the token never expires, which is worth questioning.
Questions, answered
How do I decode a JWT?
Paste the token. The header and payload appear as JSON, with times converted to UTC.
Is it safe to paste a live token here?
Decoding happens in your browser tab and the token is not sent to any server. Still, treat live tokens as passwords: prefer expired or test tokens when you can.
Does it verify the signature?
No. It decodes only. Verification needs the secret or public key and should happen on your server.
Why can't it read my token?
It may be encrypted (JWE) or not a JWT. A JWT has three dot-separated parts.
How is expiry calculated?
By comparing the exp claim with your device's current time.
Will it decode tokens on my phone?
It does, on current phone and tablet browsers. Paste the token, including a Bearer prefix if present.