Skip to content

JWT Decoder

This JWT decoder reads a token's header and claims, shows when it expires and checks HMAC signatures, all on this page.

Encoded token

The secret never leaves this page.

Decoded

Header

{
  "alg": "HS256",
  "typ": "JWT"
}

Payload

{
  "sub": "user_8421",
  "name": "Ada Lovelace",
  "email": "ada@example.com",
  "roles": [
    "editor",
    "billing"
  ],
  "iat": 1762300800,
  "exp": 1793836800,
  "iss": "https://auth.example.com"
}

Claims

Expires exp2026-11-05 00:00:00Zin under a minute
Issued iat2025-11-05 00:00:00Z1 year ago
Issuer isshttps://auth.example.com
Subject subuser_8421
Decoded locallyRuns in your browser

Load from a URL

Your browser fetches it directly, so the server must allow cross-origin requests (CORS).

How to decode a JWT

  1. Paste the token. A leading Bearer is ignored, so an Authorization header value works as is.
  2. Header and Payload appear as JSON. Claims shows exp, iat and nbf as UTC dates with how long ago or how soon, plus issuer, subject, audience and token ID.
  3. For an HS256, HS384 or HS512 token, enter the shared secret under Verify HS256 / HS384 / HS512 signature and press Verify.

Example

Signed with HS256 and the secret kitchen-table-42:

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczovL2xvZ2luLmV4YW1wbGUub3JnIiwic3ViIjoic3ZjLXJlcG9ydHMiLCJhdWQiOiJyZXBvcnRzLWFwaSIsInNjb3BlIjoicmVwb3J0czpyZWFkIiwiaWF0IjoxNzkwODQxNjAwLCJleHAiOjE3OTA4NDUyMDB9.5Wcs1uZjdO41tDjsl5b7M1CKVW23Yc6Un_p3ygZ26co

Payload:

{
  "iss": "https://login.example.org",
  "sub": "svc-reports",
  "aud": "reports-api",
  "scope": "reports:read",
  "iat": 1790841600,
  "exp": 1790845200
}

Claims shows iat as 2026-10-01 08:00:00Z and exp as 2026-10-01 09:00:00Z, marked expired: a one-hour token. With the secret, Verify says Signature verified.; any other secret gets Invalid signature for this secret.

Decoded locally

A JWT is a bearer credential: whoever holds an unexpired token can use it. Decoding needs only Base64URL and JSON parsing, so this page does it in JavaScript and checks HMAC signatures with the browser’s Web Crypto API. The token and secret are never sent or saved, a reload clears them, and once loaded the page keeps working offline.

What the JWT decoder does not do

  • RS256, ES256 and other public-key algorithms need the issuer’s public key, which this tool does not take; Verify says Only HS256, HS384 and HS512 can be checked with a secret.
  • Decoding is not verification. Anyone can write a token with any payload; only a valid signature proves who issued it.
  • Encrypted tokens (JWE) have five parts. Their payload cannot be read without the key, and the tool says so.

A single segment also decodes in Base64 to JSON. Compare two payloads in JSON diff, or browse a long one in the JSON formatter.

Questions

Is it safe to paste a production token?

It stays in this tab, but treat it like a password: anyone who sees your screen or clipboard can use it until it expires. Share your screen with an expired or test token.

Why does it say expired when my server still accepts the token?

Expiry is compared with your computer clock. Servers often allow some clock skew, such as leeway in PyJWT or clockTolerance in the Node.js jsonwebtoken package.

Why does my secret not verify?

The secret is used as UTF-8 text, so a secret stored Base64-encoded on the server gives different bytes and fails. Also check that the token was not cut short when copied.

Can it create or sign tokens?

No. It decodes and verifies only.

Related tools

Esc