JWT tool

JWT Decoder & Parser

A JWT decoder that is also a JWT parser. Paste a token, a Bearer header, or a log line, then read claims in this tab. Nothing is uploaded.

Like the tool? Find a bug?Share with us

Decoder / Parser

Paste a JWT, a Bearer header, or a log line. Header and payload decode in this tab. The token is not sent anywhere, and the signature is not verified.

Supported files: .jwt, .txt, .json
0 / 50,000
Header JSON will appear here.
Payload JSON will appear here.
A Buffer helper will appear here.

Guide

How this JWT decoder works

01

Three URL-safe parts

A signed JWT is header.payload.signature, each Base64URL. This decoder JSON-parses the first two parts. Encrypted JWE tokens have five parts and are rejected instead of guessed.

02

Claims are just JSON

Registered claims such as iss, sub, aud, exp, nbf, and iat show as a table. Times are UTC. Decode is not verify — a valid-looking payload can still be forged.

03

Next.js uses base64url

The Next.js snippet uses Buffer.from(part, "base64url") in a Node server runtime. It still does not check HMAC or RSA. Keep verification in your auth library, not in this tab.

Use it

What to paste

A raw JWT, Bearer eyJ…, Authorization: Bearer, a cookie such as access_token=, or a log line that contains the token. Input is capped at 50,000 characters. Treat production tokens as secrets even though this page never sends them.

FAQ

Questions

Does this upload my JWT?

No. Decoding and copy run in the browser. There is no account and no API call. The token never leaves this device.

Decode or verify?

This is a decoder and parser. It reads header and payload. It does not check the signature, so it cannot tell a real token from a forged one. Use your issuer’s keys for verification.

Why is my token expired?

exp is a Unix timestamp. If it is in the past, the token is expired for clients that honor it. nbf in the future means it is not valid yet.

Is there a size limit?

Paste is capped at 50,000 characters so a huge dump cannot freeze the tab.