How to Use JWT Decoder Online
Paste your JWT token
Drop any `header.payload.signature` bearer token locally.
Inspect decoded JSON
Read pretty-printed Header, Payload claims, and Expiry status.
Copy claims
Copy decoded JSON blocks for bug reports or tests.
Inspect JWT Headers, Claims & Token Expiration With Zero Network Risk
Pasting a live bearer JWT from Auth0, Firebase, Cognito, or an internal microservice into a server-backed debugger can expose active user sessions. UtilZon JWT Decoder parses all three Base64URL segments (`header.payload.signature`) strictly in local JavaScript and converts Unix `exp` and `iat` claims into human-readable dates immediately.
Anatomy of a JSON Web Token (Header, Payload & Signature)
Every JWT consists of three dot-separated Base64URL strings: the Header (`alg`, `typ`, `kid`), the Payload containing standard registered claims (`sub`, `iss`, `aud`, `iat`, `exp`) plus custom roles/scopes, and the cryptographic Signature verified by the backend using its secret or JWKS public key.
Standard Registered JWT Claims (RFC 7519)
| Claim | Meaning | Purpose |
|---|---|---|
| sub / iss / aud | Subject / Issuer / Audience | Identifies user, auth provider & target API |
| iat / nbf / exp | Issued / Not Before / Expires | Unix epoch timestamps controlling validity window |
| kid / alg | Key ID / Algorithm (RS256, HS256) | Header fields selecting signature verification key |
Common Use Cases
- Checking why an API returned `401 Unauthorized` (expired `exp` or wrong `aud` claim).
- Inspecting custom RBAC roles, scopes, and tenant IDs inside OAuth access tokens.
- Verifying `kid` headers during JWKS key rotation debugging.
- Decoding ID tokens privately during local frontend/backend development.
Expert Pro Tips
- Never store passwords or sensitive PII inside a JWT payload—anyone holding the token can Base64URL-decode it.
- Always verify JWT signatures on your backend server; client-side decoding only inspects claims.
- Use Hash & Timestamp to convert any other Unix epoch fields inside your token payload.
Recommended Next Workflow Tools
Why Use UtilZon JWT Decoder?
- 100% Client-Side Processing — files never leave your device
- No signups, watermarks, or daily file caps
- Works seamlessly on Windows, macOS, Linux, Android, and iOS
- Instant zero-latency execution via native browser APIs
Frequently Asked Questions About JWT Decoder
Is it safe to paste my real production JWT into UtilZon?▾
Yes. Decoding runs 100% in local JavaScript inside your browser—no token is ever sent across the network.
Does decoding a JWT verify its cryptographic signature?▾
Client-side decoding inspects the Base64URL header and payload; cryptographic signature verification should always be performed on your server with your secret or JWKS.
Why does it show my token as Expired?▾
It compares the JWT's `exp` Unix timestamp directly against your device's current UTC clock.
Can it decode JWE (5-part encrypted JWTs)?▾
Encrypted JWE payloads require a decryption key; standard 3-part JWS tokens decode completely.
How helpful was JWT Decoder?