Developer Tools

How to Read JWT Claims Without Mistaking Them for Proof

Decode JWT headers and claims, interpret expiry times and diagnose format errors, while separating readable payloads from signature and claim verification.

By the Criza Labs team · Updated · 6 min read

Key takeaways

  • Decoding reads token contents; it does not verify the signature or make the claims trustworthy.
  • Expiry labels compare a supplied exp value with the device clock and do not establish server acceptance.
  • Use synthetic examples and never paste production secrets, live production tokens or signing keys.

A JWT decoder reads a token’s encoded header and claims so you can inspect fields such as subject, role and expiry. Use it for development and troubleshooting with synthetic examples, while keeping a firm distinction between seeing a claim and proving that a trusted issuer created a token your application should accept.

Before you start

Use a made-up token or a deliberately sanitised development sample. Never paste production secrets, live production tokens, signing keys or real customer credentials into this workflow. A token that appears expired may still contain personal or internal information, so expiration alone does not make it a suitable example to share.

Know which format you expect. This tool reads the header and payload of the three-part compact signed-token form and identifies a five-part input as an encrypted-token form it cannot read. JWTs can be represented using signing or encryption structures; the distinction is described in RFC 7519, checked 16 November 2026.

Inputs stay in your browser; CrizaTools does not upload the token for decoding. Local processing does not turn the tool into a verifier, nor protect text you later copy into a ticket or screenshot. Keep the sample artificial, and use your application’s trusted verification implementation to make authentication and authorisation decisions.

Step by step with CrizaTools

  1. Open the JWT decoder and replace the made-up initial example in JSON Web Token with a synthetic sample. You can include or omit the leading Bearer prefix; the tool removes that prefix for decoding.
  2. Read the format status. Three dot-separated parts are expected for the readable compact form here. Five parts trigger the encrypted-token message; another part count produces a format error.
  3. Inspect Header and Payload, which are shown as formatted JSON. Each section can report its own Base64URL-or-JSON error, so one successfully decoded section does not prove the other section is well formed.
  4. Read Algorithm and the signature label as descriptions of the supplied text. Signature present, not verified means the third segment is nonempty, not that a cryptographic check succeeded.
  5. Review numeric Issued at (iat), Not valid before (nbf) and Expires (exp) entries when present. Dates are displayed in the device’s time zone, and the relative expiry label uses the device clock.
  6. Use Copy header or Copy payload if you need that decoded JSON in a local development note. Review the copied content before sharing it. There is no Verify button, key field, token-signing action or automatic call to your application server.

Two worked examples

Example 1: reading a one-hour sample interval. Paste this entirely artificial token; its final segment is deliberately not a valid signature:

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJkZW1vXzciLCJyb2xlIjoicmVhZGVyIiwiaWF0IjoxNzk0Nzg3MjAwLCJleHAiOjE3OTQ3OTA4MDB9.bm90LWEtc2lnbmF0dXJl

The exact decoded header is {"alg":"HS256","typ":"JWT"}. The payload is:

{
  "sub": "demo_7",
  "role": "reader",
  "iat": 1794787200,
  "exp": 1794790800
}

The difference is 1794790800 − 1794787200 = 3600 seconds, or exactly one hour. The times are 16 November 2026, 00:00 UTC and 01:00 UTC. On a device configured for India Standard Time, they correspond to 05:30 and 06:30 that morning; the browser’s precise date formatting may differ.

The relative expired-or-time-left sentence depends on when you inspect the sample. Algorithm HS256 and Signature present, not verified are descriptive outputs, not evidence that this deliberately invalid token should be accepted.

Example 2: a changed role without trustworthy proof. Paste this second artificial token:

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJkZW1vXzciLCJyb2xlIjoiYWRtaW4ifQ.bm90LWEtc2lnbmF0dXJl

The header is unchanged. The exact payload is {"sub":"demo_7","role":"admin"}. The status includes No expiry (exp) claim, Algorithm HS256 and Signature present, not verified, and there are no numeric time-claim rows.

Changing readable text to say admin does not grant administrative authority. The decoder can display it because decoding is possible without checking a valid signature. A trusted application must decide whether its cryptographic and claim-validation requirements are satisfied; neither an attractive JSON display nor the absence of exp establishes permission.

Limits and what to watch for

The tool splits the input, decodes its first two segments and parses them as JSON. It does not verify any signature, fetch issuer keys, enforce an allowed algorithm, validate an audience or compare a not-before claim with an acceptance policy. Even a malformed nonempty third segment can produce Signature present, not verified.

Treat header and payload fields as untrusted input until the actual relying application validates them. RFC 8725 discusses algorithm verification and audience and issuer validation as part of JWT security practice; checked 16 November 2026 in the official best-current-practice document. Do not infer a verification policy from whatever algorithm name a supplied token happens to claim.

Numeric date claims use seconds from the Unix epoch, rather than JavaScript’s usual millisecond timestamp. A 13-digit millisecond value can therefore produce an unexpected future date when interpreted as seconds. The display renders numeric time claims only; a quoted numeric string does not receive the same date conversion. See RFC 7519’s NumericDate definition, checked 16 November 2026.

The wording Valid for another… is only an exp-based countdown. It does not establish overall validity, and a missing expiry is not a promise of unlimited acceptance. Device clock accuracy, the application’s validation policy and checks beyond exp all matter, so use the application’s own verification result when diagnosing a rejected request.

There is no file input, download action or published fixed input-size ceiling in this component. Work with short, controlled samples rather than very large pastes. The interface cannot decrypt a JWE, inspect every nested-token workflow or tell you whether a token has been revoked in your application’s own state.

Common mistakes

  • Pasting a live production token: build a synthetic example instead and keep production secrets out of the workflow.
  • Treating a decoded role as permission: verify through the trusted application before relying on claims.
  • Reading Signature present as Signature verified: the decoder only checks that the third segment is nonempty.
  • Using milliseconds for NumericDate: supply seconds when constructing an artificial standards-based claim.
  • Treating the expiry label as an acceptance test: compare it with the application’s full verification result.
  • Copying all claims into a support ticket: share only sanitised fields needed to explain the development issue.

Questions and answers

Does decoding a JWT verify its signature?

No, decoding reads the encoded content without proving who created it. CrizaTools has no verification key input or signature-validation action, so its readable output must not be used as proof of authenticity.

Is it safe to paste a production JWT into the decoder?

Use synthetic samples and never paste production secrets or live production tokens. Although CrizaTools decodes locally, credentials and personal claims should remain in the production systems and controlled workflows that need them.

Why does the decoder say valid when my API rejects the token?

The displayed wording refers only to the supplied exp value compared with the device clock. Your API may reject the token for a signature, issuer, audience, not-before or other application-policy reason that this decoder does not check.

Why does a JWT expiry date look far in the future?

A sample may contain milliseconds where seconds were intended, or simply have an incorrect claim value. Inspect the original numeric exp and its intended unit before changing the application or assuming the date display establishes validity.

Can I decode an encrypted five-part JWT here?

This tool recognises the five-part form and reports that it cannot read its encrypted contents without a key. It does not provide decryption or key-entry functionality; use your authorised application’s appropriate JWE workflow instead.

Sources

Read synthetic claims with the JWT decoder, then inspect copied JSON with the JSON formatter while keeping verification in your trusted application.

Free tools for this

PDF & image

JWT Decoder

Decode a JSON Web Token in your browser to read its header and claims, with issued and expiry times in your time zone.

PDF & image

JSON Formatter

Format, validate and minify JSON in your browser. Shows the line and column of any error, sorts keys and copies or downloads the result.

PDF & image

Base64 Encode & Decode

Encode text to Base64 or decode Base64 back to text, with full UTF-8 for emoji and Indian scripts and a URL-safe option.

More guides

Free desktop app from Criza Labs

Bill every day? Get CrizaVoise free

GST invoices, thermal receipts, stock and payments in one offline app for Windows, Linux and macOS. No subscription, no sign-up, no ads, and your data stays on your computer.

  • 58 mm and 80 mm thermal printing
  • UPI QR on every invoice, WhatsApp sharing
  • Open source (Apache 2.0), English, Hindi, Gujarati and more
The CrizaVoise dashboard with quick bill and new invoice buttons, stock alerts and sample figures