Free · No signup · Runs locally

Decode a JWT without sending it anywhere.

Inspect a JSON Web Token’s header and payload locally. Signature verification is not performed.

  • Processed in your browser
  • No uploads
  • No account or email
  • Free to use
Developer Tools

JWT decoder

Paste a token to view its decoded header and payload.

Decoding does not verify the signature. Do not trust a token until it has been verified by your server.

The token stays in your browser and is not sent to a server.

Runs in your browser. Nothing is uploaded.

Why use this tool

Inspect claims locally

A quick way to see what a token contains during development and debugging.

Header and payload

View both decoded JSON sections at once.

Local decoding

The token is never sent to a server.

Copy either part

Copy the header or payload as formatted JSON.

Clear security warning

The tool explains that decoding is not verification.

Use cases

Inspecting a token safely

Decoding shows what a token claims. It does not prove that the token is authentic.

Checking expiry

Read the exp and iat claims to see when a token was issued and when it ends.

Debugging authorization

Inspect the issuer, audience, scopes, and custom claims used by your API.

Reviewing a test token

Confirm that a locally generated token contains the payload you expected.

Example

Three segments, two readable parts

The header and payload are Base64URL-encoded JSON. The signature is not decoded.

Token
eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjMiLCJleHAiOjE3MDAwMDAwMDB9.signature
Payload
{
  "sub": "123",
  "exp": 1700000000
}
How it works

JWT Decoder: three quick steps

No upload step, no account, and no detour through a server.

  1. Paste a token

    Add a JWT from your clipboard.

  2. Decode it

    The header and payload are decoded locally.

  3. Inspect the claims

    Review the JSON without trusting the token yet.

JWT Decoder runs on your device

This tool runs entirely in your browser. Nothing you enter is sent to a server, and there is no upload step. Your input stays in this tab unless you explicitly download it.

No uploads. No account. No tracking scripts.

  • Runs in your browser
  • No uploads
  • No account or email
  • No tracking scripts
  • No usage limits
  • Open standards
FAQ

JWT Decoder questions, answered

Is my token uploaded?

No. The token is decoded in your browser and is not sent to a server.

Does it verify the signature?

No. This tool only decodes the header and payload. It does not verify the token or contact the issuer.

Why is verification not included?

Verification requires the correct key, issuer, audience, and algorithm policy. That belongs in your server or authorization layer, not in a browser inspector.

Does it check expiry?

No. It only displays the claims. Check the exp and nbf claims in your own authorization logic.

Does this tool verify the signature?

No. It only decodes the header and payload. Signature verification requires the issuer’s key and should happen on your server or with a dedicated verification library.