Decode JWTs!

Paste a JWT to see its header and payload neatly!
JWT
Result
 

Decode JWTs!

Online JWT (JSON Web Token) decoder tool that instantly decodes token headers and payloads in your browser. Inspect expiration times (exp), issuers (iss), subjects (sub), and custom claims in real time without writing scripts or using command-line utilities.

All decoding is performed 100% client-side directly within your browser. No token data is ever transmitted to remote servers, making it completely safe for debugging private staging and internal authorization headers.

How to use

  1. Paste your dot-separated JWT string (e.g. eyJhbGciOi...) into the top input field.
  2. The decoded **Header** and **Payload** are immediately formatted and rendered as structured JSON.
  3. Standard timestamps such as exp (expiration) and iat (issued at) are automatically converted into human-readable local date and time.
  4. Use the copy button to transfer the formatted JSON payload directly into your test suites or debugging logs.

Supported features

  • Client-Side Privacy: Tokens never leave your browser or touch external networks, ensuring secure inspection of sensitive dev tokens.
  • Epoch Timestamp Resolution: Automatically parses exp, nbf, and iat claims into localized dates to verify validity at a glance.
  • JSON Pretty-Printing: Cleans compact payload strings into indented, easy-to-read JSON structures.
  • Malformed Token Detection: Flags padding issues, invalid Base64URL characters, and syntax errors instantly.

Use cases

Debugging 401 Unauthorized API Responses

Quickly verify whether the exp timestamp inside an Authorization: Bearer <token> header has expired before digging into backend auth logic.

OAuth 2.0 / OpenID Connect ID Token Verification

Inspect identity tokens issued by providers like Google, Auth0, or Keycloak to confirm scope grants, user roles, and email claims.

Microservice Architecture Token Auditing

Ensure tokens passed across API gateways maintain valid signing algorithms (alg: RS256, HS256) and expected tenant identifiers.

Notes and limitations

  • Decoding vs. Signature Verification: This tool decodes the content of the token. To verify cryptographic authenticity, you must validate the signature against your private secret or public JWKS key.
  • Avoid Storing Sensitive Secrets in Payloads: JWT payloads are encoded, not encrypted. Never store confidential data like passwords or credit card numbers inside JWT claims.

FAQ

Can anyone read the payload of a JWT without the secret key?

Yes. The header and payload of standard JWTs are merely Base64URL-encoded, not encrypted. The secret key is only required to verify that the token has not been tampered with.

Is it safe to paste confidential development tokens into this decoder?

Yes. json.kr processes tokens entirely in-memory using client-side JavaScript. Tokens are never transmitted to any backend server or third-party tracking services.

What happens when the exp timestamp is exceeded?

The exp claim specifies the exact second when the token becomes invalid. Once current time exceeds exp, compliant servers will reject requests with an authentication error like TokenExpiredError.