Free · No sign-up · Private

JWT Decoder

Decode a JSON Web Token and inspect its header and payload.

Quick answer

Paste a JWT and the decoder splits it at the dots, Base64URL-decodes the header and payload, and shows them as formatted JSON. If the payload has an exp claim, the expiry date is shown in UTC. The signature is not verified, since that needs the secret or public key.

JWT DecoderRuns in your browser

A JWT must have at least 2 dot-separated parts.

Step by step

How to use the JWT Decoder

01

Paste a JWT.

02

See the decoded header and payload as JSON.

Worked examples

Common JWT claims

ClaimMeaning
issIssuer
subSubject (usually the user ID)
audAudience
expExpiry time (Unix seconds)
iatIssued at
nbfNot valid before

Good to know

Structure of a JWT

A JWT has three Base64URL parts joined by dots: header.payload.signature. The header names the signing algorithm, the payload holds the claims, and the signature proves the first two were not changed.

Keep tokens secret

A valid token works like a password until it expires. This decoder runs locally, but avoid pasting live production tokens into tools you do not trust.

Reading the expiry time

The exp claim is a Unix timestamp in seconds. The decoder converts it to a UTC date so you can see whether a token has expired, which is the most common reason an API suddenly returns 401 Unauthorized. The Unix timestamp converter turns iat and nbf values into dates the same way.

FAQ

Frequently asked questions

Does the decoder check the signature?

No. Decoding only reads the token; verification needs the signing key.

Is a JWT encrypted?

Usually not. Standard signed JWTs can be read by anyone; only JWE tokens are encrypted.