Developer guide

How to use JWT Decoder online, free

Decode JWT tokens free in your browser and inspect header and payload claims safely. No signup, no install — paste a token and see its contents instantly.

A JWT Decoder takes a JSON Web Token — the three-part string separated by dots that you see in Authorization headers — and decodes its header and payload into readable JSON, so you can see exactly what a token claims: who it was issued to, when it expires, what roles it carries, and which issuer created it. JWTs are the standard way many APIs represent a logged-in session, and inspecting one is often the fastest way to understand an authentication problem.

This tool is for developers debugging login flows, API testers checking token contents, and support engineers verifying expiry times or missing claims. When an API returns an unauthorized error, the token payload often explains why: it may have expired, carry the wrong audience, or lack the role the endpoint requires.

An important limit: this decoder reads and displays a token; it does not verify its signature. A decoded payload proves only what the token claims, not that the token is genuine or unexpired in the eyes of your server. Signature verification requires the signing key and belongs in your backend, never in a browser tool.

Try JWT Decoder →

Free, no signup — opens the tool directly.

How to use JWT Decoder

  1. 1Open the JWT Decoder and paste the complete token, including all three dot-separated parts.
  2. 2Check that you copied the whole token without extra spaces or line breaks.
  3. 3Run the decoder to split the token and decode its header and payload into readable JSON.
  4. 4Read the header to see the signing algorithm and token type the issuer used.
  5. 5Read the payload claims, paying attention to subject, expiry, issued-at, issuer, and audience values.
  6. 6Compare the expiry claim with the current time if you are investigating an unauthorized error.
  7. 7Use what you learned to adjust your login flow, token request, or backend verification — remembering that decoding alone does not prove a token is valid.

Why use JWT Decoder

  • Reveals token contents instantly, so authentication problems become visible instead of mysterious.
  • Shows expiry and claim values that explain most unauthorized errors at a glance.
  • Helps you confirm that a login flow is issuing tokens with the expected audience and roles.
  • Runs locally in the browser, so tokens are inspected without sending them to a third party.

Privacy & how it works

The JWT Decoder runs entirely in your browser. Your token is decoded on your own device and is never uploaded to a server. Treat tokens as sensitive anyway: a token grants access like a password, so avoid pasting production tokens into any tool you do not trust.

Frequently asked questions

What are the three parts of a JWT?

A header describing the token type and signing algorithm, a payload carrying claims such as subject and expiry, and a signature that lets the issuer verify the token. The decoder displays the header and payload; it does not verify the signature.

Does decoding a JWT prove it is valid?

No. Decoding only shows what the token claims. A token can be decoded even if its signature is forged or it has expired. Only the server, using the signing key, can verify that a token is genuine and acceptable.

Why did my API reject a token that decodes fine?

Common reasons are an expired token, a wrong audience or issuer, a missing required role, or a signature the server cannot verify. The decoded payload usually points at the first three; signature problems need backend investigation.

Is it safe to paste a JWT into a decoder?

This decoder runs locally and never uploads your token, which is the safest arrangement. Still, prefer test tokens over production ones whenever you can, since anyone holding a token can use it until it expires.

Related guides