JSON Web Token (JWT) is an open standard (RFC 7519) for securely exchanging information between parties as a JSON object. A JWT consists of 3 parts separated by dots:
eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjM0NTY3ODkwIn0.abc123
JWT Decoder helps you decode a JWT token to view its header and payload content — it does not verify the signature.
exp (expired?), shows iat as date and timeeyJ...) into the textareaexp badge — it turns red if the token is expired| Claim | Meaning | Example |
|---|---|---|
sub |
Subject (user ID) | “1234567890” |
name |
User’s name | “John Doe” |
iat |
Issued At (creation time) | 1716000000 |
exp |
Expiration (expiration time) | 1716086400 |
iss |
Issuer (issuing party) | “auth.example.com” |
aud |
Audience (intended recipient) | “my-app” |
Metoolzy’s JWT Decoder runs 100% client-side — the token is not sent anywhere. However, avoid pasting production tokens containing real user data into any online tool.
Verifying a signature requires a secret key or public key — which shouldn’t be shared on an online tool. Decoding the payload is sufficient for debugging purposes.
Yes. The JWT header and payload are just Base64URL encoded — any decoder will produce the same result.
See more: Base64 Encode/Decode · Hash Generator · JSON Formatter