Skip to content
Kural

JWT decoder

Read JWT header and payload, expiry dates and verify HMAC signatures.

A JSON Web Token is three Base64url parts joined by dots: a header with the algorithm, a payload with claims (user id, roles, expiry) and a signature. The decoder shows the first two as formatted JSON and turns exp, iat and nbf into readable dates. Most of the time that is enough to see why an API answers 401.

How to use

  1. Paste the token. A leading Bearer from an Authorization header is removed automatically.
  2. Check the status badge: not expired, expired or not valid yet.
  3. Read the header and payload; copy either as JSON.
  4. For HS256/384/512 tokens, enter the secret to verify the signature (the example token uses kural-secret).

Frequently asked questions

Can a JWT be decoded without the secret?

Yes. The header and payload are only encoded, not encrypted, so anyone holding the token can read them. The secret is needed only to check that the token has not been modified.

What do exp, iat and nbf mean?

exp is the expiry time, iat is when the token was issued and nbf means “not before”. All are Unix timestamps in seconds.

Why does my token fail to decode?

It may be truncated, contain spaces or line breaks, or be an encrypted JWE (five parts instead of three).

Is my token sent anywhere?

No, decoding and the signature check happen on your device.