Token
paste or type · or drop a .txt file
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
Header
algHS256
typJWT
Payload
subsubject1234567890
nameJohn Doe
iatissued atJan 18, 2018, 1:30 AM
Signature

SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

Signature is not verified. The secret key is never required or sent anywhere.

What is a JWT and what does decoding reveal?

A JSON Web Token (JWT) is a compact, URL-safe token with three Base64URL-encoded parts: a header (algorithm and type), a payload (claims about the user or session), and a signature.

Decoding the header and payload requires no secret: it's public data. The signature proves integrity but can only be verified with the original key, which stays on your server.

Claims, expiry, and common debugging scenarios

The most common debugging need is checking whether a token is expired — the decoder shows exp as a human-readable date alongside the raw timestamp. Custom claims added by your auth service also appear in full.

subSubject — the user or session ID
issIssuer
expExpiration timestamp
iatIssued at
nbfNot before

Security: what you can and cannot do here

This tool decodes (base64-decodes) the header and payload. It does not verify the signature — that requires the secret or public key, which you should never paste into a third-party tool.

Decoding is safe: there is no secret involved, and because all processing happens in your browser, the token never reaches any server. Use this tool to inspect claims, not to validate tokens in production.