JWT Decoder

Paste a JSON Web Token to read its header, its payload and what the standard claims mean, including when it was issued and when it expires. The token is decoded entirely in your browser and is never uploaded. This tool only decodes: it does not verify the signature, so a decoded token is not proof that the token is genuine.

Processed locally in your browser. Your data is not uploaded to our servers.

Your token stays in this page: it is never uploaded or sent to analytics. โ€œBearer โ€ and surrounding quotes are ignored.

Result

This tool decodes only. It does NOT verify the signature, so it cannot tell you whether the token is genuine, untampered or trusted. Never trust the claims of a token you have not verified on a server with the right key.

Examples

A JWT is three Base64URL segments joined by dots. For example, the first two segments of a simple token decode to:

SegmentDecoded content
Header: how the token is signed{"alg":"HS256","typ":"JWT"}
Payload: the claims{"sub":"1234567890","iat":1516239022}
Signature: bytes that prove the first two parts, if checked with the keySflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

Formula & Methodology

Decoding is reversible and needs no key:

  1. Split the token at the two dots into header, payload and signature.
  2. Decode the header and the payload from Base64URL to bytes, read the bytes as UTF-8 text and parse the text as JSON.
  3. Convert the numeric time claims (exp, nbf, iat) from seconds since 1 January 1970 UTC to dates and compare them with your device clock.
  4. Show the signature segment as it is. It is never checked.
header.payload.signature

Notes and limitations

  • Signatures are never verified. Verifying one needs the secret or public key and must happen on your server, never in a web page you do not control.
  • Expiry and validity status uses your device clock, which may be wrong. Servers normally allow a few seconds of clock skew.
  • Encrypted tokens (JWE, five segments) cannot be decoded without their key, and only the compact serialization is supported, not JSON serialization.
  • A decoded payload is readable by anyone who has the token. Do not put secrets in a JWT payload.
  • The tool does not look up keys, check issuers or call any network service.

How to Use

  1. Paste the token into the box. A leading โ€œBearer โ€ or quotes are removed for you.
  2. Read the status and the validity message. Remember that the signature is never verified.
  3. Check the header for the algorithm and the payload for the claims. The table explains each standard claim and shows dates in UTC and in your time zone.
  4. Review the warnings, such as an unsecured algorithm or a missing expiry.
  5. Copy the header or the payload as formatted JSON if you need them.

Frequently Asked Questions

Does this tool verify a JWT?

No. It only decodes the token. Verifying the signature needs the secret or public key, and it must be done on your server. A token can be decoded even when it is forged or expired, so decoding says nothing about whether you should trust it.

Is it safe to paste my token here?

The token is decoded by code in your browser and is not sent to ToolQuarter, analytics or any other service. Even so, a live token is a credential: avoid pasting production tokens on shared or untrusted computers, and prefer expired or test tokens when you can.

What do exp, nbf and iat mean?

They are times written as seconds since 1 January 1970 UTC. iat is when the token was issued, nbf is the earliest moment it may be used and exp is the moment on or after which it must be rejected. The table shows each one as a date and as a time relative to now.

Why does the status say expired when my server accepts the token?

This tool compares exp with your deviceโ€™s clock, which can be ahead or behind. Servers may also allow a short leeway for clock differences. Check that your device time is correct.

Why can I read the payload without a key?

The header and payload of a signed JWT are only encoded, not encrypted. The signature protects against changes, not against reading. If the content must stay secret, the token needs to be encrypted (JWE) or the data kept on the server.

Last updated: