JWT Decoder

Decode a JWT to read its header, claims and expiry, privately in your browser.

This tool only decodes the token. It does not verify the signature, so a decoded token is not proof that it is genuine. Decoding runs in your browser and the token is never uploaded. Still, avoid pasting live production tokens into any website.

JWT decoder: read the header and payload of a token

Paste a JSON Web Token to see its header, its payload claims and whether it has expired. Timestamps such as iat, nbf and exp are converted into readable dates. It is useful for debugging login and API authorization problems.

What is inside a JWT

A JWT has three Base64URL parts separated by dots: a header (algorithm and type), a payload (claims such as the user, issuer and expiry) and a signature. The header and payload are only encoded, not encrypted, so anyone holding the token can read them.

Decoding is not verifying

Reading a token's contents does not prove it is authentic. To trust a JWT, a server must verify its signature with the correct key and check its claims. This tool does not do that.

Security tips

  • Never put secrets or passwords in a JWT payload, because it is readable.
  • Keep token lifetimes short and check the exp claim.
  • Avoid pasting live production tokens into online tools; use a test token where you can.

Veelgestelde vragen

Can a JWT be decoded without the secret?

Yes. The header and payload are just Base64URL-encoded JSON. The secret is only needed to verify the signature.

Is it safe to paste my token here?

Decoding happens in your browser and nothing is sent to a server, but treat any live token as sensitive and prefer test tokens.

What do iat, nbf and exp mean?

iat is when the token was issued, nbf is the time before which it must not be accepted, and exp is when it expires. All are Unix timestamps.

Why does it say the token is not a JWT?

A JWT must have exactly three parts separated by dots. Opaque tokens and API keys usually do not follow this format.

Meer in Converters & Utilities