TontonTools

JWT Decoder

Decode a JSON Web Token's header and payload instantly and privately.

100% Free No signup Privacy-friendly Web Development
Updated Sep 2026

Decoding only — the signature is not verified. Never paste production secrets.

Share X / Twitter Facebook LinkedIn WhatsApp

How to use JWT Decoder

  1. Paste your JWT (the long xxxxx.yyyyy.zzzzz string) into the box.
  2. View the decoded header and payload shown as formatted JSON.
  3. Check the standard claims — expiry and issued-at are shown as readable dates.
  4. Inspect or debug as needed. Remember the signature is not verified here.

What is JWT Decoder?

A JSON Web Token (JWT) is a compact, URL-safe token made of three Base64URL parts separated by dots: a header (algorithm and type), a payload (the claims/data), and a signature (which verifies integrity). The header and payload are encoded, not encrypted, so anyone can read them.

Common payload claims include iss (issuer), sub (subject), aud (audience), iat (issued at) and exp (expiry). Decoding reveals these; verifying the signature — which requires the secret or public key — is what proves the token is authentic.

About the JWT Decoder

The JWT Decoder instantly decodes a JSON Web Token into its readable header and payload, and breaks out the standard claims — issuer, subject, audience, issued-at and expiry — with human-readable dates. Paste a token to see exactly what it contains while debugging authentication.

JWTs are the backbone of modern auth: APIs, single sign-on and session tokens all use them. When a request is rejected or a session expires unexpectedly, decoding the token is the fastest way to see the claims and check the expiry. This tool makes that a one-paste operation.

Decoding happens entirely in your browser, so tokens are never sent to a server. Note that this tool decodes tokens for inspection — it does not verify the signature, so never trust a token's contents without server-side verification.

Frequently Asked Questions

No. It decodes the header and payload for inspection only. Signature verification requires the secret or public key and must be done server-side.
No. Decoding is done entirely in your browser, so your token never leaves your device. Still, avoid pasting production tokens you don't control.
The header and payload are Base64URL-encoded, not encrypted. Encoding provides format compatibility, not secrecy — never store sensitive data in a JWT payload.
“exp” is the expiry time and “iat” is when the token was issued, both as Unix timestamps. The decoder converts them to readable dates.

Learn more

JWT Explained: How JSON Web Tokens Work

JWTs power modern authentication, but they are widely misunderstood. Here is how they work, what is inside one, and the key security caveat.

Read the guide

We use cookies for analytics and to keep the tools free via ads. See our Privacy Policy.