JWT Decoder Guide: Read Claims, Check Times and Understand Unverified Results
Admin ·
Decode JWT opens the readable header and payload of a three-part compact token in your browser. Paste a public example or synthetic test token, choose Decode token and inspect formatted JSON, the claimed algorithm, signature presence and numeric time fields. Copy payload copies the displayed payload when you deliberately choose it.
Reading a token tells you what its text says. This workspace does not verify signatures, decrypt five-part tokens or decide whether an application should trust the claims. Time labels use the device clock, and editing the input retains the previous result until another decode. These boundaries matter when troubleshooting authentication.
Start with a public example and decode explicitly
The workspace starts empty. Decode token is unavailable while the input is empty or whitespace-only. Try an example fills the supplied public sample and decodes it, showing its HS256 header, John Doe payload and iat value. That sample is demonstration data, not an account credential you should deploy.
For your own controlled fixture, paste the full compact token and choose Decode token. Read the warning above the results, then inspect Header and Payload. Both output fields are read-only and left-to-right, including on right-to-left pages. There is no automatic decode on each input edit.
- Use the supplied public sample or construct synthetic data without private claims.
- Paste the token, choose Decode token and confirm that the displayed payload matches your intended input.
- Use the result to investigate structure and timing; perform authentication checks in the application that accepts the token.
Three parts describe this decoder’s input shape
This decoder expects header.payload.signature with exactly two dots. It trims outer whitespace and removes one initial case-insensitive Bearer prefix followed by whitespace. It does not parse a complete Authorization: header line or remove arbitrary labels, quotes or internal spaces. Keep the encoded token intact.
Header and payload must each decode to a JSON object. The third segment can be empty. Five-part compact input receives an unsupported-form message; having five parts alone does not prove the string is a valid encrypted token. JWT standards include both JWS and JWE representations, while this workspace implements a narrower readable three-part inspection path.
IETF RFC 7519: JWT claims, NumericDate and unsecured formsIETF RFC 7515: JWS serialization, Base64URL and validationIETF RFC 7516: five-component JWE compact serialization
Base64URL, UTF-8 and JSON are separate checks
Header and payload accept the unpadded Base64URL alphabet: letters, digits, - and _. A trailing = or other character is rejected, as is an encoded length whose remainder on division by 4 is 1. The decoded bytes must be valid UTF-8, and their text must be valid JSON. Successful encoding checks still do not authenticate the token.
Each decoded JSON value must be an object, rather than an array, null, string or number. A generic JWS may carry other payload types; this page does not support all such forms. Fatal UTF-8 decoding checks the bytes. It is not a promise that every JSON string escape is a Unicode scalar value: an ASCII JSON escape such as \ud800 can still parse and remain visible as an escape.
IETF RFC 7515: JWS serialization, Base64URL and validationMDN: TextDecoder.decode and fatal decoding errorsMDN: JSON.parse and numeric precision
Algorithm and signature presence are untrusted facts
Algorithm displays the string in header alg; a missing, empty or non-string value shows Not stated. A displayed HS256, RS256 or none is the token’s own assertion. This decoder supplies no key input, algorithm allowlist, issuer-to-key relationship, cryptographic verification or critical-header policy enforcement.
Present, not checked means only that the third segment is nonempty and uses the permitted alphabet. That segment is not decoded, length-validated or checked against a key and signing input. Even a one-character segment can be reported as present. None means an empty third segment, not that an application should accept an unsecured token.
IETF RFC 7515: JWS serialization, Base64URL and validationIETF RFC 8725: JWT algorithm, issuer and audience checks
Empty signatures and encrypted forms need context
RFC 7519 describes an unsecured JWT using alg set to none and an empty signature. This decoder accepts an empty third segment independently of the claimed algorithm. It does not check that the combination is standards-conforming or appropriate for a particular application. A readable result therefore cannot establish an acceptable token type.
JWE compact serialization has five components. This workspace rejects that input shape and has no decryption key or decryption operation. It also does not handle JWS JSON serialization, detached payload workflows or nested-token validation. It always Base64URL-decodes the payload; the b64:false JWS extension is outside that path, and JWT profiles prohibit that extension.
IETF RFC 7519: JWT claims, NumericDate and unsecured formsIETF RFC 7516: five-component JWE compact serializationIETF RFC 7797: unencoded JWS payload option and JWT restrictions
Formatted JSON is a reading view
The formatter adds indentation while keeping number literals and duplicate field names in the displayed text. For example, 1e3 remains 1e3 instead of being rewritten as 1000. This is useful when examining source notation, but the formatted JSON is not the original encoded signing input and should not replace that input in a verification workflow.
Facts come from JavaScript JSON parsing, which converts numbers to Number values and selects the last occurrence of a duplicate name. A payload containing "exp": 0 followed by "exp": 1e100 shows both fields, but its time diagnostic uses the latter parsed value. Large numbers can lose precision in parsed facts even when the visible literal remains exact. Formatter warnings are not displayed in this workspace.
IETF RFC 7519: JWT claims, NumericDate and unsecured formsIETF RFC 7515: JWS serialization, Base64URL and validationMDN: JSON.parse and numeric precision
Time rows use finite numeric seconds
JWT NumericDate values use seconds since the Unix epoch; fractions are permitted by the definition. This tool collects finite numeric iat, nbf and exp, in that order, and multiplies them by 1000 for date display. A numeric string such as "1516239022" does not produce a time row. Neither does a value parsed as non-finite, although its original text remains in the payload.
Do not paste a millisecond timestamp into a claim that your application expects in seconds. A value around 1516239022000 seconds describes a very different date from 1516239022 seconds. The decoder does not infer a different unit from the number’s length, rewrite the claim or check application-specific requirements.
| Claim | Standard topic | This workspace’s display |
|---|---|---|
iat | Issued at | Local date for a finite number; no age-policy badge. |
nbf | Not before | Local date; Not valid yet while its value exceeds the device clock. |
exp | Expiration | Local date; Expired at or before the device clock, otherwise Not expired yet. |
IETF RFC 7519: JWT claims, NumericDate and unsecured formsMDN: JSON.parse and numeric precision
Local dates and clock badges have practical limits
Displayed dates use the page’s language and the browser’s time zone. They can differ between devices for the same numeric claim. Expired and Not valid yet compare with the current device clock, without a clock-skew allowance, signature verification or issuer/audience policy. There is no continuously updating countdown; rendering again may reevaluate the labels.
A finite number can still exceed the browser’s supported Date range, including when seconds multiplied by 1000 overflow. The tool keeps the formatted payload readable and shows Time value is outside the supported date range for that row, without a time badge. A date-formatting diagnostic describes a display boundary, not a trusted decision about token validity.
IETF RFC 7519: JWT claims, NumericDate and unsecured formsMDN: JavaScript Date representation and supported rangeMDN: Intl.DateTimeFormat locale and default time zone
Use decoding as one diagnostic step
A token can be readable yet forged, modified, intended for another audience, issued by an unexpected party or rejected by application policy. Claims such as iss, aud and sub appear in the payload but are not checked here. The workspace also does not fetch keys named by headers or validate a typ value.
A receiving application needs the checks appropriate to its token profile, including an allowed algorithm, cryptographic validation with a trusted key and relevant issuer, audience and timing rules. Compare those actual application results with the decoded text. Do not turn a successful parse, a claimed algorithm or Not expired yet into an authorization decision.
IETF RFC 7519: JWT claims, NumericDate and unsecured formsIETF RFC 8725: JWT algorithm, issuer and audience checks
Edited input and displayed output can differ
Editing Token clears notices but keeps the old decoded result or error until you choose Decode token again. If you paste a second token and immediately choose Copy payload, you copy the previous displayed payload. Compare the visible result with the input you intended to decode before copying or drawing conclusions.
Decode runs asynchronously while loading the formatter. When multiple Decode actions overlap, only the latest action may deliver its result or error. An enabled Clear also invalidates pending deliveries, so a previous decode cannot restore a cleared payload. This delivery guard does not stop all computation or securely erase memory, and merely editing the input is not a new Decode action.
Clear empties the workspace when available
Clear removes the input, displayed result and error, and shows Token cleared. It is enabled when the input is nonempty or a result exists. If you receive an error and then manually empty the input, the retained error alone does not enable Clear. Try an example or enter a new nonempty fixture and decode it to replace that error.
Reloading starts with an empty workspace. Neither Clear nor reload erases text you previously copied to the system clipboard or into another application. Removing visible state is not secure browser-memory erasure, credential revocation or deletion of copies elsewhere.
Local decoding and deliberate copying have different boundaries
The decoding operation reads the token in the browser without a token-containing request or a persistent token vault. Normal page hosting, analytics and code loading are separate from that operation. The historical phrase JWT decoder online describes an available browser page; it does not mean that this decoder uploads the token to a validation service.
A real token can carry credentials and private claims even after expiration. Readable Base64URL is encoding, not encryption, and an expiry field does not delete the payload. Prefer the public sample or synthetic fixtures for demonstrations and shared troubleshooting. Avoid putting private tokens into screenshots, issue reports or copied examples.
IETF RFC 7519: JWT claims, NumericDate and unsecured formsIETF RFC 8725: JWT algorithm, issuer and audience checks
Copy payload copies the formatted visible payload
Copy payload writes the entire displayed formatted payload to the system clipboard and shows Payload copied on success. It does not copy the original compact token or header. The destination application receives a separate copy; review where you paste it and which claims it contains.
If the Clipboard API write fails, the workspace shows Clipboard unavailable. Select the payload to copy it. You can select the read-only output manually. This page provides no download, token export, saved history or automatic transfer to another tool. A copy notice does not verify any signature or remove existing clipboard data later.
Input size and JSON nesting are separate limits
The Token field limits user input to 100000 UTF-16 code units. This is a workspace control limit, not a JWT standard maximum, network-header allowance or guarantee that every receiving service accepts such a token. Base64URL token text is usually ASCII, but pasted surrounding text is still governed by the field’s units.
The JSON formatter supports nesting up to 256. More deeply nested header or payload JSON can parse yet fail formatting with the depth error. This tool does not offer file upload, streaming, batch decoding or a configurable depth limit. Shorten a synthetic fixture or use a workflow designed for the needed input rather than treating every failure as a bad signature.
Troubleshoot the layer identified by the error
Count the parts first, then inspect the reported header, payload or signature error. Base64URL, UTF-8, JSON grammar and JSON-object shape failures describe different stages. A successful parse clears the old error; a failed Decode removes the old result and shows the current error.
Application rejection is a separate problem from a decoder error. Keep the original token intact in the application’s controlled environment and use its validation logs and policy to investigate. This page cannot tell you whether a key, audience, issuer, revocation rule or authorization policy is correct.
| Symptom | Check | Next step |
|---|---|---|
| Wrong number of parts | Compact shape and pasted wrappers | Use a full three-part fixture; five-part compact JWE is unsupported. |
| Base64URL or UTF-8 error | Reported encoded segment | Check unpadded alphabet, intact bytes and unintended whitespace. |
| JSON/object/depth error | Decoded content and nesting | Use JSON objects for both readable segments within the formatter limit. |
| Readable token rejected by application | Actual verifier and application policy | Inspect trusted-key, algorithm, issuer, audience and relevant timing checks there. |
IETF RFC 7515: JWS serialization, Base64URL and validationIETF RFC 8725: JWT algorithm, issuer and audience checksMDN: TextDecoder.decode and fatal decoding errors
Choose related tools for a specific inspection task
Base64 encoder and decoder can help investigate an individual segment when the correct alphabet and byte interpretation are selected. The JWT workspace already performs its own Base64URL and UTF-8 checks. Decoding a segment elsewhere does not validate its signature or establish whether the whole token is acceptable.
JSON formatter helps examine a public or synthetic JSON object independently, while Timestamp converter helps compare units and date representations. Those are separate workflows; this page does not automatically hand off a token or claims. Keep private credentials out of shared examples and verify authentication in the receiving application.
Common questions
Does this verify a JWT signature?
No. It reads the header and payload, reports a claimed algorithm and notes whether the third segment is nonempty. There is no key input, cryptographic verification or application acceptance decision.
Does Present, not checked mean a valid signature exists?
It means only that nonempty third-segment text uses the permitted alphabet. The segment is not decoded or checked for cryptographic validity, length or consistency with the claimed algorithm.
Can I decode a token with no signature?
An empty third segment is accepted when the header and payload pass the readable-object checks. RFC 7519’s unsecured form uses alg set to none, but this decoder does not enforce that combination or decide whether an application may accept it.
Why is a five-part token rejected?
Five-part compact input matches the JWE form, which this workspace does not support. It provides no decryption operation or key input; part count alone does not establish that the input is valid encrypted data.
Can I paste a Bearer token?
Yes, one initial case-insensitive Bearer prefix followed by whitespace is removed after trimming outer whitespace. A complete Authorization: line or additional wrapper text is not parsed as an HTTP header.
Are exp, nbf and iat seconds or milliseconds?
JWT NumericDate values are seconds since the Unix epoch, with fractions permitted. This tool uses finite numbers and multiplies them by 1000 for browser date display; it does not infer units or convert numeric strings into time rows.
Why does a numeric-looking time claim have no row?
A quoted number is a string, and a number parsed as non-finite is omitted from time facts. The original payload text remains visible. Finite numbers outside the supported Date range get a diagnostic row without a time badge.
Does Not expired yet mean the token is accepted?
No. The label compares the parsed value with the current device clock. There is no automatic countdown, signature verification, clock-skew policy, issuer/audience validation or authorization decision.
Why do duplicate claims appear but only one time is used?
The reading view retains duplicate fields. JavaScript JSON parsing keeps the last occurrence for the facts, so the displayed time uses that value. A receiving application must apply its own accepted parsing and token-validation rules.
Why does edited input still show an older result or error?
Editing is separate from Decode token. It keeps the previous result or error until another Decode action. Copy payload acts on the displayed result, which may differ from newly edited input.
What happens if I Clear while decoding?
An enabled Clear empties the workspace and invalidates pending decode deliveries. Earlier results or errors cannot return through that decode path. This does not cancel every computation, erase the clipboard or securely wipe browser memory.
Is an expired token safe to share?
Expiration does not encrypt or delete private claims, and the token may still be sensitive. Use the supplied public sample or synthetic data for demonstrations and shared bug reports.
What does Copy payload copy?
It copies the whole formatted visible payload, without the header or original compact token. Clipboard writes can fail; the workspace then offers manual selection. Clear does not erase copies outside the workspace.
How large or deeply nested can input be?
User input is limited to 100000 UTF-16 code units, and JSON formatting supports nesting up to 256. These are workspace limits, not universal JWT, HTTP or receiving-application limits. There is no batch or file-upload interface.
Sources and further reading
- IETF RFC 7519: JWT claims, NumericDate and unsecured forms
- IETF RFC 7515: JWS serialization, Base64URL and validation
- IETF RFC 7516: five-component JWE compact serialization
- IETF RFC 8725: JWT algorithm, issuer and audience checks
- IETF RFC 7797: unencoded JWS payload option and JWT restrictions
- MDN: TextDecoder.decode and fatal decoding errors
- MDN: JSON.parse and numeric precision
- MDN: JavaScript Date representation and supported range
- MDN: Intl.DateTimeFormat locale and default time zone
- MDN: Clipboard.writeText and write failures
- MDN: maxlength and UTF-16 code-unit input limits