DexTools

JWT Parser

Decode a JWT header, payload and claims in your browser, with expiry checks and no signature claims.

Nothing leaves your browser Dex Dev

Decoded in this tab. The signature is not verified.

Decoded
Paste a JWT above to see its header, payload and claims.
Waiting for a token.
Save to DriveInsert into Office

Saving needs a Dex account. The tool never does.

How it works

  • Paste a token. The header and payload are Base64url-decoded and pretty printed, and the registered claims are pulled out with readable dates.
  • Expiry is checked against the clock in your browser and stated in the status strip, so an expired token is obvious rather than something you work out from a Unix timestamp.
  • The signature segment is shown but never verified. Verifying needs the issuer key, and a browser tool that claimed to verify would be lying to you.
  • The token stays in the tab. That matters: a JWT is a bearer credential, and pasting one into a server-side decoder hands over your session.

Examples

Why is my request 401?

Paste the token you are sending. If the status strip says it expired, the client is not refreshing it. If the audience does not match the API, the token was issued for a different service.

Checking what a token carries

The registered claims table shows subject, issuer and scope without decoding the JSON by hand, which is usually enough to see whether the right role made it into the token.

Frequently asked questions

Does this verify the signature?

No, and it says so on the page. Verification requires the issuer public key or shared secret; decoding only reads the claims. Never trust claims from a token your server has not validated.

Is it safe to paste a real token here?

The token is decoded in your browser and never transmitted, which is the property that makes this safer than the many JWT sites that post the token to a server. It is still a credential: avoid pasting production tokens into shared or recorded screens.

Why does it say the token is expired?

The exp claim is a Unix timestamp in seconds. The page compares it with your clock, so a device with the wrong time will disagree with the server about expiry.

What is the difference between nbf and iat?

iat is when the token was issued. nbf is the earliest time it may be used. A token with a future nbf is rejected even though it has been issued.