Header and Payload
See the decoded header and payload as formatted JSON, ready to copy.
Decode a JSON Web Token to read its header, payload and claims. See when it was issued, when it expires and which algorithm it uses — instantly and privately in your browser.
This tool decodes tokens only. It does not verify signatures, and your token never leaves your device.
This tool only decodes the token. It does not verify the signature, so a decoded token is not proof that it is genuine — always verify tokens on your server.
A JSON Web Token (JWT) is a compact, URL-safe string used to pass information between systems — most often to prove who a user is after they sign in. It has three parts separated by dots: a header, a payload of claims, and a signature.
The header and payload are just Base64URL-encoded JSON, so anyone can read them. A decoder turns them back into readable JSON so you can inspect what a token contains.
See the decoded header and payload as formatted JSON, ready to copy.
exp, iat and nbf claims are shown as real dates, in UTC and your local time, with how long ago or from now.
Instantly see whether the token is valid, expired or not valid yet.
Get warnings for unsigned tokens (alg: none), empty signatures and tokens with no expiry.
Issuer, subject, audience and other standard claims are labelled in plain language.
Decoding happens locally. Your token is never sent to a server.
Paste the JWT, with or without the "Bearer " prefix.
The header, payload and signature appear immediately.
Look at the expiry status, dates and any warnings.
Copy the header or payload JSON for your notes or tests.
Quick answers about using the MoSanKit JWT Decoder.
No. It only decodes the token. A decoded token is not proof that it is genuine — always verify signatures on your server with the correct key.
The decoding runs entirely in your browser and the token is never uploaded. Even so, avoid pasting live production tokens into any website you do not control — use a test token where you can.
JWT payloads are encoded, not encrypted. Never put secrets such as passwords in a JWT payload.
exp is when the token expires, iat is when it was issued and nbf is the time before which it must not be accepted. All three are Unix timestamps in seconds.
It means the token is unsigned. A server must never accept such a token for authentication.
No. Encrypted tokens have five parts and cannot be read without the decryption key.
Explore more free developer tools from MoSanKit.