Header and payload
View both decoded JSON sections at once.
Inspect a JSON Web Token’s header and payload locally. Signature verification is not performed.
Paste a token to view its decoded header and payload.
Decoding does not verify the signature. Do not trust a token until it has been verified by your server.
The token stays in your browser and is not sent to a server.
Runs in your browser. Nothing is uploaded.
A quick way to see what a token contains during development and debugging.
View both decoded JSON sections at once.
The token is never sent to a server.
Copy the header or payload as formatted JSON.
The tool explains that decoding is not verification.
Decoding shows what a token claims. It does not prove that the token is authentic.
Read the exp and iat claims to see when a token was issued and when it ends.
Inspect the issuer, audience, scopes, and custom claims used by your API.
Confirm that a locally generated token contains the payload you expected.
The header and payload are Base64URL-encoded JSON. The signature is not decoded.
eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjMiLCJleHAiOjE3MDAwMDAwMDB9.signature
{
"sub": "123",
"exp": 1700000000
}
No upload step, no account, and no detour through a server.
Add a JWT from your clipboard.
The header and payload are decoded locally.
Review the JSON without trusting the token yet.
This tool runs entirely in your browser. Nothing you enter is sent to a server, and there is no upload step. Your input stays in this tab unless you explicitly download it.
No uploads. No account. No tracking scripts.
No. The token is decoded in your browser and is not sent to a server.
No. This tool only decodes the header and payload. It does not verify the token or contact the issuer.
Verification requires the correct key, issuer, audience, and algorithm policy. That belongs in your server or authorization layer, not in a browser inspector.
No. It only displays the claims. Check the exp and nbf claims in your own authorization logic.
No. It only decodes the header and payload. Signature verification requires the issuer’s key and should happen on your server or with a dedicated verification library.