○ RUNS IN YOUR BROWSER

JWT Decoder

Paste a JSON Web Token to read its header and payload as formatted JSON, see when it was issued and when it expires, and check an HMAC signature with your secret. Decoding happens in your browser, so the token is never sent anywhere.

CHECK THE SIGNATURE

The secret is checked in your browser and never sent anywhere.

DECODED

Issuer (iss)
https://auth.example.com
Subject (sub)
user_8412
Audience (aud)
tool-kit.space
Issued at (iat)
Thu, 1 Jan 2026, 00:00:00 UTC
Not before (nbf)
Thu, 1 Jan 2026, 00:00:00 UTC
Expires (exp)
Fri, 1 Jan 2100, 00:00:00 UTC

HEADER

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

PAYLOAD

{
  "sub": "user_8412",
  "name": "Ada Lovelace",
  "iss": "https://auth.example.com",
  "aud": "tool-kit.space",
  "iat": 1767225600,
  "nbf": 1767225600,
  "exp": 4102444800
}
● Decoded HS2567 claims Decoded in your browser · the token is never sent anywhere

What's in a JWT

A JSON Web Token is three base64url-encoded parts joined by dots. The header says how the token is signed, for example {"alg":"HS256","typ":"JWT"}. The payload holds the claims: who the token is about (sub), who issued it (iss), who it's for (aud) and when it's valid. The signature is computed over the first two parts, so any change to them breaks it.

Valid now, expired or not valid yet

The badge compares the exp and nbf claims with your device's clock. A token without exp never expires on its own, which is a risk if it leaks; most APIs issue tokens that last minutes or hours and refresh them.

Verifying the signature

For HMAC tokens, the signature is a hash of the header and payload made with a shared secret. When the secret you type produces the same hash, the token is genuine and unchanged. If it doesn't match, either the secret is wrong or someone edited the token.

How to decode a JWT

  1. 1

    Paste the token

    Paste a JWT into the token box, with or without the word Bearer in front. The header and payload show up as formatted JSON straight away.

  2. 2

    Read the claims

    Issuer, subject and audience are labelled, and the iat, nbf and exp times are shown as dates in your time zone with a badge that says whether the token is valid now or expired.

  3. 3

    Check the signature

    For HS256, HS384 and HS512 tokens, type the secret to see whether it signed this token. Pick Base64 when your secret is stored that way.

Frequently asked questions

Is it safe to paste a real token here?

The token is decoded with JavaScript on your device and never sent to a server, and the secret you type for the signature check stays in your browser too. Still, treat a live token like a password, and prefer test tokens when you can.

Can anyone read what's inside a JWT?

Yes. The header and payload are only base64url-encoded, not encrypted, so anyone who has the token can read them. The signature only proves the token wasn't changed. Never put passwords or other secrets in a JWT payload.

Why can't I check an RS256 or ES256 signature?

Those tokens are signed with a private key and checked with the issuer's public key, usually published as a JWKS. This tool checks HS256, HS384 and HS512, which use one shared secret.

What do exp, nbf and iat mean?

They're times in seconds since 1970. iat is when the token was issued, nbf is the moment before which it must not be accepted, and exp is when it expires. A server should refuse the token outside that window.

Why does it say my token has five parts?

A token with five parts is an encrypted JWT (JWE). Unlike a signed JWT, its payload is encrypted and can only be read with the key it was encrypted for.

On this page
Pages
Home
All tools
Suggest a tool
About
Privacy