DevFormat Studio
Home / JWT Token Decoder

JWT Token Decoder

Decode JSON Web Tokens locally to inspect the header, payload and expiry times. Runs locally in your browser — nothing is uploaded.


What Is a JSON Web Token and Why Do Developers Decode It?

A JSON Web Token, or JWT, is a compact, URL-safe string used to carry claims between two parties. It is the most common format for access tokens in modern authentication systems, including OAuth 2.0 and OpenID Connect. A JWT consists of three parts separated by dots: a header describing the signing algorithm, a payload containing claims such as the user ID, roles and timestamps, and a signature that proves the token was issued by a trusted party.

Both the header and the payload are simply Base64URL-encoded JSON, which means anyone holding a token can read its contents. Developers decode tokens to debug login problems, confirm that the right scopes were granted, check which identity provider issued the token, and find out why a request returns 401 Unauthorized. The most frequent cause is an expired token, and that is why the decoder translates the exp, iat and nbf claims into readable dates.

How to Decode a JWT

Step-by-step instructions

  1. Copy a token from your application, browser developer tools or API client. A leading Bearer prefix is removed automatically.
  2. Paste it into the input box. Decoding runs as soon as the token has three parts, or you can press Decode. Use Load Sample Data to see a demo token.
  3. Review the header to see the algorithm (alg) and token type, then the payload to inspect every claim.
  4. Check the time panel. It shows issued-at, not-before and expiry in UTC and your local time zone, together with a badge such as "Expired 2 hours ago".
  5. Copy or download the decoded JSON for use in bug reports.

Important: decoding is not verifying

This tool reads a token but does not check its signature, because verification requires the secret or public key and should happen on your server. Never trust claims from an unverified token to make security decisions. Treat the decoder as an inspection aid only.

Privacy and Security Benefits

A live JWT is effectively a password: anyone who obtains it can act as the user until it expires. Pasting production tokens into an online decoder that uploads them to a server is a real risk. DevFormat Studio decodes tokens with JavaScript in your browser, makes no network request containing your input and keeps no history. For extra caution, you can use expired or test tokens, or disconnect from the network before pasting.

Frequently Asked Questions

Can this tool verify a token's signature?

No. It only decodes the readable parts. Signature verification must be done by your backend with the proper key.

Why can I read the payload without a secret?

JWTs are signed, not encrypted. The payload is merely encoded, so avoid placing sensitive data inside it.

What do exp, iat and nbf mean?

They are Unix timestamps: exp is when the token expires, iat when it was issued, and nbf the earliest time it is valid.

Is it safe to paste my token here?

The token is processed only in your browser and is never transmitted. Still, avoid sharing live production tokens with anyone.