CalcuForge
Developer & Tech

Base64 / URL / JWT Encoder & Decoder

Switch between Base64, URL encoding, and JWT modes to encode, decode, and inspect tokens — entirely in your browser.

Input
Encoded (Base64)
Q2FsY3VGb3JnZSB0b29scyBydW4gZW50aXJlbHkgaW4geW91ciBicm93c2VyLg==
Decoded (from Base64)
Not valid Base64 — check for missing padding ("=") or characters outside A–Z, a–z, 0–9, +, /.
Reference

What each mode does

header.payload.signature
Base64Two-way encode/decode of any text to and from the Base64 alphabet
URLPercent-encode/decode characters unsafe in URLs
JWTSplits the token on '.' and Base64URL-decodes the header and payload as JSON
Worked example

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.

ClaimMeaning
subSubject — usually the user or account ID
iatIssued-at timestamp
expExpiration timestamp
FAQ

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.

Related tools