DevKit

JWT Decoder

Read a JSON Web Token without sending it anywhere, and verify HMAC signatures right here.

Free No sign-up Runs in your browser
Token
Header
Payload
—Algorithm
—Expires
—Issued
—Status
Verify an HMAC signature (optional)

Paste the shared secret used to sign this token. Verification happens locally with the Web Crypto API.

Never paste production tokens into a site you do not control. This page is client-side only, but a token is still a credential.

The three parts of a JWT

A JSON Web Token is a string of three Base64URL segments joined by dots: header.payload.signature. The header names the signing algorithm (alg) and token type; the payload holds claims — registered ones like sub, exp, iat, aud, plus whatever your application adds; the signature lets the issuer prove the first two parts were not altered.

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9 . eyJzdWIiOiIxMjM0NTY3ODkwIn0 . dBjftJeZ4CVP-mB92K27uhbUJU1p1r_wW1gFWFOEjXk
header                                  payload                              signature

Decoding is not validation

Anyone holding a token can read the header and payload — they are Base64URL, not encrypted. The signature only proves integrity, and only if you actually check it. A server that decodes a token and trusts sub without verifying the signature is trivially impersonated. Verifying, in turn, must reject the none algorithm and must not let the token's own header choose between HMAC and RSA keys (the classic algorithm-confusion attack).

Reading the exp claim

exp, iat and nbf are Unix timestamps in seconds, not milliseconds. A token whose exp looks like 1516239022 expires in January 2018 — long past. Compare exp against the current time with a small clock skew allowance (30–60 seconds) so tokens are not rejected right at the boundary.

What this tool can verify

HMAC signatures (HS256, HS384, HS512) can be checked with the shared secret, and that check runs locally in your browser using the Web Crypto API. RS*, ES* and PS* tokens are signed with a private key and verified with a public key — there is no secret to paste, so this page only decodes them. For those, verify on the server or with a dedicated tool that accepts a JWKS URL.

Treat tokens as passwords. They are bearer credentials: whoever has one can act as that user until it expires. Avoid pasting production tokens into any web page, including this one.

Frequently asked questions

Is it safe to decode a JWT here?
The token is never transmitted — parsing happens in JavaScript on your machine and nothing is logged. Still, a JWT is a credential, so prefer test tokens and revoke anything you accidentally expose.
Why can't I verify an RS256 token?
RS256 is asymmetric: signing uses a private key, verification a public key. There is no shared secret to type in. Fetch the issuer's JWKS endpoint and verify there, or use a tool that accepts a public key.
My token has five segments instead of three.
That is a JWE (encrypted JWT), which uses five parts and cannot be read without the decryption key. This tool handles signed (JWS) tokens only.
Does a valid signature mean the user is logged in?
No. A valid signature means the token was issued by whoever holds the key and has not been modified. You still have to check expiry, audience, issuer and whether the session was revoked.

Related tools