- What is Base64 and why is JSON often Base64-encoded?
- Base64 is a binary-to-text encoding that represents arbitrary bytes using only 64 printable ASCII characters (A-Z, a-z, 0-9, +, /). JSON gets Base64-encoded when it has to travel through a text-only channel that does not tolerate the original characters: JWT payload, URL fragment, environment variable, HTTP basic auth header, email attachment.
- What is the difference between Base64 and Base64URL?
- Base64URL replaces + with -, / with _, and drops the trailing = padding. It is what JWTs and most URL-safe encodings use. This tool auto-detects both formats on decode and lets you pick the variant on encode.
- My JWT decoded but the result is gibberish — why?
- A JWT has three parts separated by dots. The middle part is the Base64URL-encoded payload — that is what you want to decode. The first part is the header and the third is the signature (binary, will not decode to readable JSON). Paste just the middle segment.
- How big a payload can I decode?
- Practically unlimited. Both encode and decode run in linear time and constant memory per byte. Multi-megabyte payloads decode in milliseconds.
- Is the decoded JSON validated?
- After Base64 decoding the tool runs JSON.parse on the result. If it parses, the formatted output is shown. If it does not (the Base64 contained something other than JSON), the raw decoded text is shown with a notice.
- Is my data private?
- Yes. Both Base64 transcoding and JSON parsing happen locally in your browser. No network calls during conversion — you can decode JWTs from production without leaking anything.