JWT Decoder — Inspect Header, Payload & Signature

Decode a JWT to see exactly what it contains: the algorithm in the header, every claim in the payload, and whether the token has expired. Tokens are decoded locally — your access tokens never leave your browser.

What is a JSON Web Token?

A JWT (RFC 7519) is a compact, URL-safe string used to pass claims between two parties — most often between a login/identity service and an API. It has three dot-separated parts: a header describing the signing algorithm, a payload containing the claims (user id, roles, expiry…), and a signature that lets the receiver verify the token was issued by a trusted party and not modified.

The header and payload are just Base64URL-encoded JSON. That means anyone who has the token can read its contents — JWTs are signed, not encrypted. Never put secrets such as passwords or card numbers in a JWT payload.

Standard claims you will see

iss (issuer) identifies who created the token; sub (subject) is usually the user id; aud (audience) names the API the token is meant for; exp, nbf and iat are Unix timestamps for expiry, not-before and issued-at; and jti is a unique token id used for revocation. Applications add their own custom claims such as email, roles or tenant_id.

This decoder converts the exp claim to a readable date and flags whether the token is currently expired, which is the single most common cause of mysterious 401 Unauthorized responses. The iat and nbf claims are shown as raw Unix numbers, so convert them with the Epoch Time Converter when you need the date.

Decoding is not verifying

Decoding only reads the token. Verifying means checking the signature against the issuer's secret (HMAC) or public key (RSA/ECDSA). This tool is for inspection and debugging; your backend must always verify signatures before trusting any claim. If you need to create a signed test token, use the companion JWT Builder.

How to use it

  1. Copy the token from your Authorization: Bearer … header, cookie or local storage.
  2. Paste it into the token field. The header and payload appear as formatted JSON immediately.
  3. Check the expiry indicator and the aud/iss values against what your API expects.

Anatomy of a token

A typical HS256 token looks like this (line breaks added for readability):

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.
eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkFkYSBMb3ZlbGFjZSIsImlhdCI6MTUxNjIzOTAyMn0.
SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

The first segment decodes to {"alg":"HS256","typ":"JWT"}, the second to {"sub":"1234567890","name":"Ada Lovelace","iat":1516239022}, and the third is the HMAC-SHA256 signature over the first two segments.

Common use cases

Pitfalls when pasting a token

Paste only the token itself. If you copy the whole header value, Bearer eyJ…, the first segment contains a space and decoding fails with an error, because the tool splits on dots and expects exactly three parts. Remove the word Bearer and any quotes first.

The expiry badge only looks at the exp claim and compares it with your computer's clock, so a wrong system clock gives a wrong answer. The iat and nbf claims are shown as raw Unix numbers; convert them with the Epoch Time Converter. For example 1516239022 is 2018-01-18T01:30:22Z.

Frequently asked questions

Is it safe to paste a production token here?

The token is decoded entirely in your browser and is not transmitted anywhere. That said, a live access token grants access to whatever it was issued for, so treat it like a password and avoid sharing screenshots of it.

Why can't this tool tell me if the signature is valid?

Verifying a signature requires the issuer's secret key or public key. This tool does not ask for keys; it focuses on inspecting the contents. Signature verification belongs on your server.

What does "alg: none" mean?

It means the token claims to be unsigned. Well-configured servers reject such tokens. If you see it in production traffic, investigate immediately.

My token has five parts instead of three — why?

That is a JWE (encrypted JWT), not a JWS. Its payload is encrypted and cannot be read without the decryption key.

Does the decoder convert iat and nbf to dates?

No. Only exp gets a readable date and an expired or valid badge. iat and nbf are displayed as Unix timestamps, which you can convert with the Epoch Time Converter.

Related tools

Explore all developer tools →