Account

What new tool do you want?

Developer Tools

JWT Decoder

Decode a JSON Web Token to read its header and payload, check expiry times, and verify HS256/384/512 signatures with your secret.

How to use

  1. 1Paste the token (three parts separated by dots).
  2. 2Read the decoded header and claims; add the secret to verify an HMAC signature.

Frequently asked questions

Is it safe to paste a JWT here?

Decoding happens entirely in your browser. Still, treat live tokens like passwords and avoid pasting production tokens into any website.

Does decoding mean the token is valid?

No. Anyone can decode a JWT. Only verifying the signature with the right key proves it wasn't forged or modified.

Why can't RS256 tokens be verified here?

RS256 and ES256 use public-key signatures. This tool verifies shared-secret (HS) tokens; public-key verification is planned.

Worked example: JWT Decoder

The sample token in the placeholder decodes to a header of {"alg":"HS256","typ":"JWT"} and a payload of {"sub":"1234567890","name":"John Doe","iat":1516239022}. The tool converts that iat (issued-at) Unix timestamp to a readable date for you — 1516239022 seconds since the epoch is 2018-01-18 01:30:22 UTC — since JWT timestamps are always raw seconds-since-epoch integers, not a human-readable format, and reading one by eye is error-prone. This particular token has no exp (expiry) claim at all, so the tool correctly reports "No expiry" rather than guessing one.

Why decoding and verifying are two completely different guarantees

A JWT's header and payload are just Base64url-encoded JSON — no secret or key is needed to read them, which is exactly why you should never put sensitive data in a JWT payload expecting it to be hidden; anyone who gets the token can decode it instantly, this tool or any other. Verifying the signature is the separate step that actually matters for trust: it proves the token was issued by someone who holds the signing secret and that the header/payload haven't been altered since. A token can decode perfectly and display a completely fabricated "admin": true claim — decoding alone proves nothing about authenticity.

Why only HS256/384/512 can be verified here, not RS256

HS256, HS384 and HS512 are symmetric — the same secret both signs and verifies the token, so this tool just needs the shared secret you type in to recompute the HMAC and compare it against the token's signature. RS256 and ES256 are asymmetric — a private key signs, and a separate public key verifies — which is a fundamentally different cryptographic operation (RSA or elliptic-curve signature verification rather than HMAC) that this tool doesn't implement yet. If you're inspecting a token signed with RS256, you can still read its header and payload here; you just can't confirm the signature's validity with this specific tool.

A Bearer prefix is stripped before the three parts are checked

The box opens with a sample token already in it. Before anything is split, a leading Bearer and the space after it are removed, in any mix of capitals. The remainder must be exactly three pieces separated by dots. Anything else stops with the message that a JWT has three parts: header, payload, and signature. If the header or the payload is not valid base64url JSON, I get a different message and no decoded fields. The secret box is optional and starts empty. Leaving it empty still decodes the token. It does not invent a verification result from a blank secret.

Related tools

More: Developer Tools