JWT Debugger

Decode JWT payloads locally (signature not verified)

Signature not verified

This decoder reads payload claims only. It does not verify the JWT signature. A decoded payload tells you what the token claims, not whether it's authentic — never trust without server-side signature verification.

JWT Token

Samples

Header

—

Payload

—

How to use

Paste a JWT — the three dot-separated segments (header, payload, signature) are split automatically.
The Base64URL header and payload are decoded into readable JSON.
Registered claims such as exp, iat, and nbf are rendered as human-readable dates next to their raw epoch values.
Decoding happens entirely in your browser; the signature is not verified and the token never leaves your machine.

Examples

Paste a token like eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjMiLCJleHAiOjE3MDAwMDAwMDB9.abc and the payload reveals sub: 123 and exp: 1700000000, shown as a readable UTC date.
If the exp claim is in the past, the tool flags the token as expired so you can spot stale credentials at a glance.

Verify outputs before using in production. No warranty — see Terms.