Base64 / URL / JWT Encoder & Decoder
Switch between Base64, URL encoding, and JWT modes to encode, decode, and inspect tokens — entirely in your browser.
What each mode does
Decoding a JWT payload
A JWT like eyJhbGc...signature is three Base64URL segments joined by dots. Decoding the middle (payload) segment as JSON typically reveals claims such as "sub" (subject/user ID), "iat" (issued at), and "exp" (expiration) — exactly what the widget above shows for the sample token, including whether it has already expired.
| Claim | Meaning |
|---|---|
| sub | Subject — usually the user or account ID |
| iat | Issued-at timestamp |
| exp | Expiration timestamp |
Common questions
Every calculation runs entirely in your browser using standard JavaScript — nothing you paste is sent to a server or logged anywhere. That said, a JWT payload is not encrypted, only encoded, so anyone who has the token can already read its contents; be mindful of where you paste real tokens regardless of which tool you use.