Skip to content

Data tool

JWT Decoder

Paste a JSON Web Token to read its header, payload and claims, see when it expires, and check the signature.

Decoded in your browser. The token and the key are never uploaded or saved.

A token copied with "Bearer" in front, or inside quotes, works too.

JWT Decoder by YegappanFree tool. Open the full page for the guide.

How to use the JWT Decoder

  1. Paste the token. A copied Authorization header, or a token with Bearer in front, works as it is.
  2. Read the header and the payload as JSON. The claims table shows each date in your local time and says what each claim means.
  3. To check the signature, enter the secret for an HS256 token or the public key for an RS256 or ES256 token, then choose Check signature.

What a JWT decoder shows you

A JWT decoder splits a JSON Web Token into its header, payload and signature and shows the first two as readable JSON. Use it to decode a JWT token online, read its claims, see when it expires, and run a JWT signature verification with the secret or the public key.

The header and the payload are Base64URL-encoded JSON, so decoding them needs no key. A JWT is signed, not encrypted: anyone who holds the token can read what is inside. The signature only proves that the first two parts have not been changed since they were signed.

Dates in a JWT are Unix timestamps in seconds. The exp, nbf and iat claims are shown in your local time and in UTC, with a plain answer on whether the token has expired.

This decoder works locally. The token, the secret and the public key stay in the page, nothing is saved, and pasting sends no request. A JWT works as a login until it expires, so treat a live production token like a password wherever you paste it.

The signature check supports HS256, HS384 and HS512 with a shared secret, and RS256, PS256 and ES256 (with their 384 and 512 variants) with a public key in PEM or JWK form. EdDSA tokens can be checked in browsers that support Ed25519.

Common questions

How do I decode a JWT token online?

Paste the token into the box. The header and the payload are decoded straight away and shown as formatted JSON, with every claim listed underneath.

Is it safe to paste a JWT here?

The token is decoded in your browser and is not sent or saved. Even so, a token that has not expired works like a password, so use test tokens where you can and avoid pasting live production tokens into any website.

Can a JWT be decoded without the secret?

Yes. The header and payload are only encoded, not encrypted, so anyone can read them. The secret or key is needed only to create the signature or to check it.

How do I know if a JWT has expired?

Look at the exp claim. It is a Unix timestamp in seconds. The decoder converts it to your local time and tells you whether that moment has passed.

What is the difference between decoding and verifying a JWT?

Decoding only reads the contents. Verifying recalculates the signature with the secret or the public key, which proves the token came from the holder of that key and has not been altered. A server must always verify.

Why does the signature not match?

The usual causes are a wrong secret, a Base64-encoded secret entered as plain text, a public key from a different key pair, or a token that was edited after it was signed.

Can this decode an encrypted token (JWE)?

It reads the header of a five-part JWE token. The content itself is encrypted and cannot be read without the decryption key.

Guides for the JWT Decoder

Related tools