What it does
The JWT Decoder parses a JSON Web Token into its three constituent parts: the header, payload, and signature. The Header (Algorithm & Type) area shows token metadata such as the signing algorithm and type, while Payload (Claims) presents the decoded claims in a readable JSON structure. The signature is also made available for inspection, allowing you to see the token’s encoded third segment.
All processing happens locally in the browser using plain browser APIs. The tool calls no backend endpoints and sends no token data anywhere, making it suitable for inspecting tokens that contain sensitive information. It has one operating mode: paste or type a token, run the decoding operation, and review the result. It does not update the output automatically as you type, so you must explicitly run the decoder after changing the token. The tool also includes sample content so you can explore the interface without supplying a token first.
When to use it
- Inspecting an unfamiliar access token: Decode a token to review its algorithm, type, issuer, subject, audience, expiration, and other claims without exposing it to a remote decoding service.
- Checking expiration-related claims: Look for fields such as exp, iat, or nbf in the decoded payload before troubleshooting an authentication failure.
- Confirming the token structure: Verify that the pasted value contains the expected header, payload, and signature segments and that the header and payload contain valid JSON.
- Reviewing authorization context: Examine claims related to roles, scopes, permissions, tenant identifiers, or client identifiers when diagnosing an unexpected authorization decision.
- Debugging a malformed token: Use the decoder’s error messages to distinguish an invalid three-part JWT structure from a token whose claims cannot be parsed as JSON.
- Testing a locally developed token: Decode a JWT generated by a development system or test fixture and compare its visible header and claims with your expectations.
- Learning how JWT payloads are represented: Use the built-in example to see how common token metadata and claims appear after decoding, subject to the limits of decoding rather than cryptographic verification.
How to use it
- Locate the JWT Token input. The interface labels this area JWT Token. Paste a compact JWT or type one directly into the field.
- Use the sample token if needed. If you do not have a token available, load the built-in example through the interface’s sample-data action. The action is available, but its text label is not stated in the interface labels.
- Run the decoder. Press the interface’s decode control after entering or replacing the token. The tool does not process changes automatically while you type.
- Review the header. Inspect Header (Algorithm & Type) for values such as alg and typ. The header describes how the token is represented; it does not by itself prove that a signature is valid.
- Review the payload. Inspect Payload (Claims) to see the decoded JSON claims. Pay particular attention to identity, scope, time, issuer, and audience fields relevant to your use case.
- Inspect the signature segment. Check the signature shown by the tool as part of the complete token structure. The decoder does not perform cryptographic signature verification with a trusted secret or public key.
- Copy the output if necessary. Use the tool’s copy action to place the relevant decoded result on the clipboard. The interface labels do not state the copy action’s wording, and the tool does not offer a download option.
Worked example
Consider a compact JWT whose decoded header is:
{ "alg": "HS256", "typ": "JWT" }
Its decoded payload contains these claims:
{ "sub": "user_123", "iss": "https://issuer.example", "aud": "orders-api", "iat": 1735689600, "exp": 1767225600, "roles": ["reader", "editor"] }
After pasting the compact token and running the decoder, the Header (Algorithm & Type) area shows alg as HS256 and typ as JWT. The Payload (Claims) area shows the subject user_123, issuer https://issuer.example, audience orders-api, and the two listed roles. The integer timestamps remain numeric JSON values, while the roles are presented as a JSON array.
This example lets you inspect what the token claims. It does not establish that the token was issued by the named issuer, was intended for your application, remains within its validity window, or has a valid signature. Those questions require separate trust and validation decisions. In particular, a payload can be decoded without being trusted: any party able to construct a token can also choose the payload content unless a valid signature is checked against the appropriate key.
The tool accepts only text representing a JWT. It does not accept a file, provide drag-and-drop, or download the decoded output. No numeric input limit is published for the token length.
Limitations and edge cases
- Decoding is not cryptographic verification. A successful decode shows that readable portions can be interpreted; it does not prove that the signature is authentic, that the issuer is trusted, or that the token has not expired.
- Expected claims are not automatically evaluated. The tool does not state that it enforces expiration, not-before, issuer, audience, or required-claim rules. You must interpret those claims against your application’s requirements.
- Only the standard three-part JWT structure is accepted. A valid JWT must have a header, payload, and signature separated by dots. A token with a missing or extra segment produces the error “Invalid JWT format. A JWT should have 3 parts separated by dots (header.payload.signature)”.
- Claims must contain parseable JSON. Even when the token has three parts, content that cannot be interpreted as JSON causes “Failed to parse JWT claims as JSON.”
- There is no live decoding. You must run the decoder after editing the token. If the displayed result appears stale, confirm that the decode action was run after the most recent change.
- No state is retained between visits. The tool does not use local storage, so it does not preserve a pasted token, decoded result, or preferences for a later session.
- Text input is the only input route. The tool has no file input and no drag-and-drop support. Use a different workflow if your source is stored in a file and you need to transfer its contents into the JWT Token field.
- No output download is available. When you need an artifact, use the clipboard and paste the copied result into another application.
Troubleshooting
- Problem: The tool reports “Invalid JWT format. A JWT should have 3 parts separated by dots (header.payload.signature)”.
Fix: Check that the pasted value contains exactly three dot-separated segments. Remove introductory text such as “Bearer,” surrounding quotation marks, or accidental spaces that are not part of the token. - Problem: The tool reports “Failed to parse JWT claims as JSON”.
Fix: Confirm that the token was generated as a JWT and that its payload segment represents a JSON object. The decoder can show the structure but cannot recover claims from a malformed payload. - Problem: The tool reports “Failed to decode JWT. The token may be malformed.”
Fix: Re-copy the token and ensure it was not shortened, reflowed, or combined with other text. Then run the decoder again. - Problem: The result does not reflect a recent edit.
Fix: Run the decode action again. The output does not update automatically while you type. - Problem: The decoded token contains unexpected or misleading claims.
Fix: Remember that decoding exposes claims but does not validate them. Check the token against the expected issuer, audience, time claims, and signature using a verification library or other dedicated validation tool. - Problem: You need to retain the output as a file.
Fix: Copy the result and paste it into an application that can save it. The decoder itself has no download function.
Frequently asked questions
Does the JWT Decoder send my token to a server?
No. Processing occurs entirely in the browser, and no backend endpoints are called. The token is not uploaded.
Does the tool verify a JWT signature?
No. It decodes and displays the header, payload, and signature information, but it does not validate the signature with a secret, public key, or trusted key set. Use a cryptographic JWT verification library when authenticity is required.
Can I open a token from a file?
No. The tool works only with text that you paste or type into the JWT Token field. It has no file input or drag-and-drop support.
Can I download the decoded result?
No. The tool can copy a result to the clipboard, but it does not provide a download action. Paste the copied text into another application if you need to save it.
What token length does it support?
The tool does not publish a numeric limit for token length. Browser and memory constraints may still affect unusually large inputs, but no specific threshold is stated.
Does it update while I type?
No. You must run the decoder after entering or changing the token.
Does it remember tokens between visits?
No. The tool does not use local storage and does not preserve state between sessions.
Should I use this tool for complete authentication validation?
No. It is appropriate for inspecting token structure and claims. Use a dedicated verification and validation tool when you need to check a signature, trusted issuer, audience, expiration, not-before time, or other application-specific requirements.