Skip to content
QuicklyTools

JWT Decoder

Decode JSON Web Tokens to read header and payload claims, with human-readable dates and an expiry check.

Runs in your browser
Loading tool…

About the JWT Decoder

Inspect JWTs from OAuth, OpenID Connect and API authentication. The header and payload are decoded and pretty-printed; registered claims such as exp, iat and nbf are converted to readable dates, and you see at a glance whether the token has expired.

Tokens are decoded locally — never paste production tokens into tools that send them to a server.

How to use it

  1. Paste the token (with or without “Bearer ”).
  2. Read the header, payload and claims.
  3. Check the expiry status.

Good to know

  • Decoding does not verify the signature. Anyone can create a token with any payload; only signature verification with the correct key proves authenticity.
  • Encrypted tokens (JWE, five parts) cannot be decoded without the key.

Frequently asked questions

Is the payload of a JWT secret?

No. A signed JWT is only Base64URL-encoded, so never put secrets in it.

Why is my token “not valid Base64URL”?

It may be truncated, contain extra characters, or be an opaque (non-JWT) token.

More developer tools →