Share Copied!
Blog Nov 13, 2026 7 min read

JWT Decoder: Read a Token and Know What It Cannot Prove

Illustration of a token split into three parts under a magnifier

To decode a JWT, open FileReadyNow's JWT Decoder, paste your token into the token field, click Decode Token, and read the Header, Payload, Signature and Claims tabs. The page says it runs in your browser with no network requests. It also says it does not validate the signature, which matters more than any other fact on this page.

FileReadyNow built this tool, so read this as a walkthrough from the maker, not an outside review. The facts about the tool come from its live page, and the facts about tokens come from the JWT specification (RFC 7519) and the JWT best practices document (RFC 8725). I use a made-up token as the example, so nothing here is a real credential.

What is inside a JWT?

A JSON Web Token, or JWT, is a string of three parts separated by dots. The specification says each part is base64url encoded. The tool page says it splits the token at the dots and decodes the header and payload into formatted JSON.

PartWhat it holdsWhat decoding shows you
HeaderThe token type and the signing algorithm, such as HS256Readable JSON
PayloadThe claims: who the token is about, who issued it, when it expiresReadable JSON
SignatureA value made with a secret or private key, used to check the token has not been alteredOnly the encoded string. The page says it cannot be verified without the key

One limit of that picture: the specification also allows encrypted JWTs, which have five parts instead of three. You cannot read an encrypted token's contents by decoding it. The tool page describes the three-part kind.

How do I decode a JWT step by step?

  1. Copy a token from your app, your browser's DevTools or an API response.
  2. Open the JWT Decoder and paste it into the Paste Your JWT Token field. The page also has Load Sample and Clear buttons.
  3. Click Decode Token.
  4. Open the Claims tab for plain-language explanations of the standard claims, and use the Copy button on any tab to take the JSON with you.

A worked example with a made-up token

Here is a harmless token I made up for this post. Its signature is not real, because it is only the words "not-a-real-signature" encoded, so no key could ever verify it.

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyLTEwNDIiLCJuYW1lIjoiVGVzdCBVc2VyIiwiaWF0IjoxNzY3MjI1NjAwLCJleHAiOjE3NjcyMjkyMDB9.bm90LWEtcmVhbC1zaWduYXR1cmU

PartDecoded
Header{{"alg":"HS256","typ":"JWT"}}
Payload{{"sub":"user-1042","name":"Test User","iat":1767225600,"exp":1767229200}}

The two numbers are Unix timestamps, meaning seconds since 1 January 1970 UTC. The specification defines them that way. Converting them by my own arithmetic, iat is 1 January 2026 at 00:00 UTC and exp is 1 January 2026 at 01:00 UTC. The difference is 3,600 seconds, so this token was valid for one hour. As that time has passed, a decoder should show it as expired. I have not run this exact token through the tool, so try it yourself and compare.

What do the standard claims mean?

The specification defines six registered claims, and all of them are optional. The tool page says its Claims tab explains iss, sub, aud, exp and iat. The sixth, nbf, is defined in the specification, but the page does not mention it.

ClaimMeaningNotes
issIssuer: who created the token
subSubject: who or what the token is about
audAudience: who the token is meant forIf present, the specification says a party not listed must reject the token
expExpiration timeA token must not be accepted on or after this time
nbfNot before: earliest time it may be acceptedDefined in the specification, not mentioned on the tool page
iatIssued at: when the token was created

Why does decoding not verify a token?

Anyone can decode a token, because base64url is an encoding, not a lock. What makes a token trustworthy is the signature check, which needs the secret or public key. The tool page says it does not validate the signature. It also says verification belongs on a server and that keys should never be entered into a browser-based tool. There is no key field on the page.

The specification is clear that the receiving application has to do the checking. If any validation step fails, the token must be rejected. The best practices document adds that libraries should let you restrict which algorithms are accepted, and that the none algorithm should be used only when the token is protected some other way. So treat the expiry status as a read of the exp claim only. A decoded, unexpired token that nobody has verified is still just text.

Is it safe to paste a token into a decoder?

The tool page says everything runs in your browser and nothing is sent to a server. That is the page's own statement, and you can test it. Open your browser's DevTools, switch to the Network tab, and decode a made-up token like the one above. You should not see a request that carries it.

The page says nothing about whether it stores or logs tokens. Its privacy text talks about files, which does not fit a token tool. So my advice is to keep to test or expired tokens where you can, because a live token works like a password until it expires. Also remember that the payload is readable by anyone who holds the token, so do not put private data in it.

What can this tool not do?

It does not verify signatures and has no algorithm list or key field. It does not create tokens, and it does not tell you whether a token is genuine or whether your server will accept it. The page states no token size limit. Once decoded, you can tidy the JSON with the JSON Beautifier. If you want to protect a message with a passphrase, the Text Encrypt and Decrypt tool is a separate tool for that, and it is not a way to make a JWT secure.

Frequently asked questions

How do I decode a JWT?

Copy the token, open the JWT Decoder, paste it into the token field and click Decode Token. The page then shows the header, payload and signature in separate tabs, plus a Claims tab that explains the standard claims. Decoding only reads the token. It does not prove that the token is genuine.

Does decoding a JWT verify it?

No. Decoding only displays what the token contains. Verifying means checking the signature against the right key, and the tool page says it does not validate the signature. If your application accepts the token, that check must happen on your server, with your key, before you trust any claim.

Is the payload of a JWT encrypted?

Usually not. A signed JWT is protected against tampering, but its header and payload are only base64url encoded, so anyone holding the token can read them. The JWT specification says private data must be protected by encrypting the token or by using an encrypted connection such as TLS.

What does the exp claim mean?

The exp claim is the expiration time, written as a number of seconds since 1 January 1970 UTC. The specification says a token must not be accepted on or after that time. The decoder converts it to a readable date, but that tells you only what the token claims, not whether it is genuine.

Is it safe to paste a token into an online decoder?

The page says everything runs in your browser and nothing is sent to a server, and you can check that in the Network tab of your browser's DevTools. A live token still works like a password until it expires, so I would use test or expired tokens when you can.

Where should I go next?

Ready to try it? Open the JWT Decoder, paste the made-up token from this post, and check that its dates match the arithmetic above.

Sources: IETF RFC 7519, JSON Web Token (structure, registered claims, expiry, signed versus encrypted tokens, accessed November 16, 2026); IETF RFC 8725, JSON Web Token Best Current Practices (algorithm checks and the none algorithm, accessed November 16, 2026).

Last updated: November 16, 2026.

Tags: jwt decoder decode jwt jwt decoder online jwt token decoder decode jwt token jwt payload jwt exp claim json web token decoder
Share
Navin Adhikari

Written by

Navin Adhikari

Leading full-stack development for FileReadyNow.


Mostly in-browser 79 of 106 tools run entirely in your browser. Each tool page says which.
Uploads auto-deleted Files sent to server-side tools are deleted automatically, most within 15 minutes.
SSL encrypted transfer Everything sent to our servers uses HTTPS / TLS encryption.
Never sold or shared We don't sell, share, or manually open your files, or use them for training.
How we handle files See which tools upload and how long files are kept.
Full security details →