Universal

JWT decoderEN

Inspect JSON claims and NumericDate timestamps while treating every decoded value as untrusted data.

Decoded does not mean verified. Treat all content as untrusted.

Processing stays in this tab.

Ready.

How to use it

Use this decoder to inspect a compact JWS/JWT during development or troubleshooting before proper verification.

  1. Paste the complete three-part token, including its signature segment.
  2. Decode to inspect formatted header and payload JSON plus recognised time claims.
  3. Verify the token separately with the correct algorithm, key, issuer, audience, and claim policy.

Worked example

Input
eyJhbGciOiJub25lIn0.eyJzdWIiOiJyaWd1bGEifQ.signature
Output
Header: {"alg":"none"}
Payload: {"sub":"rigula"}

Readable data is not trusted data; this page performs no signature or claim validation.

Method and definitions

  • The first two RFC 7515 compact segments are strict Base64url-decoded as UTF-8 JSON objects.
  • Finite integer iat, nbf, and exp NumericDate claims are additionally shown as UTC ISO timestamps.

Limits and edge cases

  • Signature, issuer, audience, expiry, not-before, nonce, and application-policy checks are not performed.
  • Encrypted five-part JWE tokens and non-object JSON segments are rejected.

Privacy

All input and output stays in this tab. Rigula does not upload, store, or include it in a share URL.