Developer tool

JWT Decoder

JWT decoder: read the header and payload of a JSON Web Token as clear JSON in your browser. It does not verify the signature, so a token may still be forged.

Your file never leaves your device.

Decode only. This tool does not verify token signatures.

Runs locally in your browser

Your text is not uploaded.

Simple steps

How it works

  1. 01

    Paste a JWT with three dot-separated segments.

  2. 02

    Decode the header and payload locally.

  3. 03

    Review the claims and copy the readable JSON.

The three parts of a JWT

A JSON Web Token is three Base64URL strings joined by dots: a header, a payload and a signature. The header names the signing algorithm, such as HS256 or RS256. The payload holds claims such as sub (the subject, usually a user ID), iss (who issued the token), aud (who it is for) and exp (when it expires).

The tool decodes the header and payload into readable JSON. The signature is a cryptographic check over the first two parts; it is neither decoded nor verified here.

Reading the times in a token

exp, iat (issued at) and nbf (not before) are Unix timestamps in seconds. "exp": 1700000000 means the token expired at 2023-11-14T22:13:20Z. Paste any of these numbers into the Unix Timestamp Converter to read them as dates.

Decoding is not verifying

Anyone can create a token with any payload; only a valid signature shows who issued it. In your own applications, never trust a decoded payload without verifying the signature with the correct key, and reject tokens whose header says "alg": "none".

The payload is encoded, not encrypted, so anyone who has a token can read it. Keep passwords and other secrets out of JWT claims.

Good to know

Frequently asked questions

Does this tool verify a JWT signature?

No. It only decodes the header and payload; a valid-looking token may still be forged or expired.

Can I paste a production token?

Avoid pasting secrets into tools unless your security policy allows it. This page processes locally, but decoded text remains visible on screen.

What parts are decoded?

The first two JWT segments are decoded as Base64URL JSON. The signature is not checked.

What if the token is malformed?

The decoder reports missing segments, invalid Base64URL, or invalid JSON.

Is the token sent to a server?

No. Decoding occurs locally and makes no network request.