Skip to content
JWT Decoder
Encoded Token

Debug only — not server-side auth. Secret stays in this tab and is not saved.

Signature not checked.

160 chars HS256 algorithm

This tab only decodes the token. The signature is not checked unless you paste an HMAC secret. That check is debug-only — it is not server-side authentication. Nothing is uploaded.

algHS256
Issued: 1/18/2018, 1:30:22 AM
  • sub — Subject — the user or entity1234567890
Header
{
  "alg": "HS256",
  "typ": "JWT"
}
Payload
{
  "sub": "1234567890",
  "name": "Ada Lovelace",
  "iat": 1516239022
}
Signature
OgYXxzx6Zijvpg3tKbxvN-sGdqvtP9EjWRFcaMEEGqc

JWT Decoder

Decode JWTs locally — inspect claims and optionally check HS256 HMAC — free, private and running entirely in your browser

Read the header and payload of a JSON Web Token, including the issued-at and expiry timestamps rendered as readable dates. Decoding happens in your browser, so a token from a live session is not transmitted anywhere.

Guide, examples, and FAQ

About JWT Decoder

What it does

The decoder splits the token, Base64URL-decodes the header and payload, and displays both as formatted JSON alongside the standard claims. You can optionally check HS256/HS384/HS512 with a secret in this tab — that is debug-only, not server-side authentication. RSA/ECDSA are not verified here.

Who it is for

For backend developers debugging authorisation, QA engineers checking why a request returns 401, and support staff confirming when a token expired.

When to use it

Use it when a request is rejected and you need to see the claims the server received, or to confirm whether a token has simply expired.

Key features

  • Encoded Token

    Paste header.payload.signature (2 or 3 segments). Status shows N chars and the alg chip when decode succeeds.

  • Header, Payload, Signature

    Pretty JSON for Header and Payload with Copy JSON. Signature is shown as Base64URL text or (none).

  • Claims banner

    When iat, nbf, or exp are present, shows Issued / Not before / Expires as local times with relative text.

  • HMAC secret (optional)

    Password field with show/hide. Checks HS256, HS384, and HS512 only. Status lines include Signature not checked., Valid HMAC — debug only, not server-side auth., and Invalid HMAC — secret or token does not match.

How to use JWT Decoder

  1. 1Paste a JWT into Encoded Token (a signed sample loads by default).
  2. 2Read Header, Payload, and Signature on the right.
  3. 3Check the Issued / Not before / Expires banner when those claims exist.
  4. 4Optionally enter an HMAC secret for HS256 / HS384 / HS512 — debug only.
  5. 5Copy Header or Payload JSON, or Clear to empty the token and secret.

Example

Before

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkFkYSBMb3ZlbGFjZSIsImlhdCI6MTUxNjIzOTAyMn0.OgYXxzx6Zijvpg3tKbxvN-sGdqvtP9EjWRFcaMEEGqc

After

Header: {"alg":"HS256","typ":"JWT"}. Payload: {"sub":"1234567890","name":"Ada Lovelace","iat":1516239022}. Signature: OgYXxzx6Zijvpg3tKbxvN-sGdqvtP9EjWRFcaMEEGqc. Status: HS256 algorithm.

Sample is HS256-signed with secret toolsera-demo-hs256. Paste that secret to see Valid HMAC — debug only, not server-side auth. Decode alone does not verify the signature.

Common problems and fixes

  • The token will not decode

    A JWT has three dot-separated parts. Truncated copies from logs are the usual cause.

  • Expiry looks wrong

    The exp claim is in seconds since the Unix epoch, in UTC. Compare it against UTC, not local time.

Benefits

  • Save time

    What used to take a script or a desktop app now takes seconds — decode jwts locally the moment the page loads.

  • Stay private

    Nothing is uploaded. JWT Decoder runs client-side, which keeps confidential jwts locally on your own machine.

  • Get accurate output

    Deterministic processing and clear error reporting mean the result you see is the result you ship.

  • Work anywhere

    Once the page has loaded, JWT Decoder runs in the browser on desktop or mobile. Reloading the page needs a connection.

Common use cases

  • Backend developers

    Inspect and clean up jwts locally returned by an API before wiring it into a service.

  • Frontend developers

    Prepare fixtures and mock jwts locally for components without leaving the browser.

  • QA engineers

    Reproduce a defect by checking the exact jwts locally a failing request produced.

  • Data analysts

    Reshape exported jwts locally into a structure a spreadsheet or notebook can read.

  • DevOps engineers

    Sanity-check configuration jwts locally before rolling a change out to production.

  • Students

    Learn how jwts locally is structured with immediate, visual feedback while experimenting.

Tips & best practices

  • Keep a small sample of your jwts locally handy — testing the options on a short input is faster than reworking a large one.
  • Use the copy and download actions instead of selecting text manually; they preserve formatting exactly.
  • Bookmark JWT Decoder so the workspace is one keystroke away during your next session.
  • Format jwts locally before diffing or committing it — consistent formatting keeps reviews focused on real changes.
  • Use JWT Decoder alongside your editor: paste, transform, copy back, and skip writing a throwaway script.

Common mistakes to avoid

  • Pasting partial jwts locally and assuming the result is wrong — always include the full input.
  • Ignoring the status messages in the workspace; they explain exactly what went wrong and where.
  • Uploading sensitive jwts locally to random online services — JWT Decoder never needs to, because it runs on your device.
  • Copying jwts locally out of a terminal with wrapped lines, which silently corrupts the input.
  • Trusting a transformed result without re-validating it once more before shipping.

Frequently asked questions

Does decode verify the signature?

No. Without a secret the status stays Signature not checked. You can paste an HMAC secret for HS256, HS384, or HS512 only — that check is debug-only, not server-side authentication.

Are RS256 or ES256 verified here?

No. Non-HS algorithms show: HMAC check is only for HS256, HS384, and HS512.

What if alg is none?

A warning appears: Header alg is none — this JWT is unsecured. HMAC verification is not applied. The HMAC line also shows: Unsecured token (alg none) — HMAC is not applied.

What error do short or broken tokens show?

JWT must contain 2 or 3 dot-separated segments, or Failed to decode: followed by the browser parse error.

Is my data uploaded or stored?

Nothing is uploaded. Processing runs in your browser. Your input is kept only while this tab stays open and is cleared when you reload or close the tab. The HMAC secret is not saved.

Conclusion

JWT Decoder gives you a fast, private and dependable way to decode jwts locally — inspect claims and optionally check hs256 hmac without installing anything. Because every calculation and conversion happens in your browser, you get instant results while your jwts locally stays on your machine. Try it above, then explore the rest of TheToolSera's developer tools to complete the next step in your workflow.

Ready to try JWT Decoder?

Scroll back up to start now, or continue with another free developer tool.

Guides and glossary

Learn and reference material connected to JWT Decoder.