JWT Claims Viewer
The JWT Claims Viewer decodes the token payload and presents every claim — registered and custom — in a structured, tree-style layout that is easy to scan, even for nested objects and arrays.
What This Tool Does
Claims are the statements a token makes: who issued it, who it is for, when it expires and any application-specific data. This tool decodes the payload and renders each claim with its value, expanding nested structures so complex tokens stay readable. Registered claims are shown alongside custom ones with their raw values intact.
How to Use
- Paste your JWT into the input field.
- Browse the tree of claims in the output panel.
- Expand mentally through nested objects and arrays rendered with indentation.
- Copy or download the claim listing for your notes.
Key Features
- Tree-style rendering of all payload claims
- Handles nested objects and arrays gracefully
- Registered and custom claims shown together
- Readable formatting for long or complex values
- Copy and download actions
- Local-only processing — no uploads or storage
Common Use Cases
- Reviewing which claims your identity provider emits
- Checking role, scope or permission claims during authorization debugging
- Comparing claim sets between environments or tenants
- Exploring unfamiliar tokens from third-party APIs
- Documenting a token contract for your team
Registered vs. Custom Claims
Registered claims (iss, sub, aud, exp, nbf, iat, jti) have standardized meanings defined by RFC 7519. Custom claims are defined by your application — prefer collision-resistant names, because all claims share one flat namespace.
Remember that claims are visible to anyone holding the token. Keep payloads small and free of sensitive data.
Frequently Asked Questions
What is a JWT claim?
A claim is a name/value pair in the payload — a statement about the subject (for example sub: "user-123") or metadata such as expiration time.
Which claims are standard?
RFC 7519 registers iss, sub, aud, exp, nbf, iat and jti. Everything else is a custom or private claim defined by the issuing application.
Can the viewer show nested claims?
Yes. Objects and arrays inside the payload are rendered as an indented tree so their structure stays visible.
Are claims encrypted?
No. Claims are Base64URL-encoded, not encrypted — anyone with the token can read them. Never place secrets in claims.
Does viewing claims verify the token?
No. The viewer only decodes and formats. Verify the signature separately before trusting any claim.
Is my token uploaded?
No. Everything is decoded and rendered locally in your browser.
Related JWT Tools
- JWT Decoder — Decode JWT tokens to view header and payload
- JWT Payload Formatter — Pretty print JWT payload with proper indentation
- JWT Inspector — Comprehensive analysis of JWT token structure and claims
- JWT Audience Validator — Validate JWT audience claim against expected value