Skip to content

JWT decoder

Paste a JSON Web Token to read its header and claims. It is decoded in your browser and never sent anywhere.

Signed with HS256.

Signature not verified
Algorithm
HS256
Lifetime No exp claim
—
Claims
3
Standard claims with readable dates
Subject (sub)
1234567890
Issued at (iat)
Thu, 18 Jan 2018 01:30:22 UTC

How it works

What's inside a JWT

A JSON Web Token has three parts separated by dots:

  • Header: which algorithm signed the token, such as HS256 or RS256.
  • Payload: the claims: who the token is about, who issued it, when it expires, and any custom data.
  • Signature: proof that the header and payload haven't been changed, made with a secret or private key.

The header and payload are just JSON encoded with URL-safe Base64, which is why this page can read them without any key. The signature is what makes a JWT trustworthy, and checking it is your server's job.

Common JWT mistakes

  • Trusting the payload without verifying the signature on the server.
  • Accepting the none algorithm, which means no signature at all.
  • Long or missing expiry times: a leaked token stays usable until it expires.
  • Storing personal data in the payload, which anyone holding the token can read.

The guide to JWT security best practices shows how each of these has broken real systems, and the verify settings that prevent them.

Frequently asked questions

Is it safe to paste my token here?

DevBenchr decodes the token in your browser and never sends it anywhere. Still, treat real tokens like passwords: they can give access to accounts. Prefer tokens from test environments, and never paste production tokens into tools that send them to a server.

Does the decoder check the signature?

No. Checking the signature needs the secret or public key, which shouldn't be pasted into a website. Decoding shows what a token claims; only your server, with the key, can confirm the claims are genuine.

Are JWTs encrypted?

Usually not. A standard JWT is only signed: anyone who has it can read the contents, as this page shows. Don't put secrets or sensitive personal data in a JWT payload unless it is encrypted (a JWE).

What do exp, iat and nbf mean?

They are timestamps in seconds since 1 January 1970 (UTC). exp is when the token expires, iat when it was issued, and nbf the moment before which it must not be accepted. DevBenchr turns them into dates.