What is the difference between Base64 and Base64URL output?
Standard Base64 uses +, /, and optional = padding. Base64URL replaces + and / with - and _ and removes padding so the result is safer inside URLs and tokens.
Encode valid JSON into standard Base64 or URL-safe Base64URL with UTF-8-safe processing, minify or pretty controls, a compact audit strip, and local-only browser execution.
Standard Base64 uses +, /, and optional = padding. Base64URL replaces + and / with - and _ and removes padding so the result is safer inside URLs and tokens.
This tool is intentionally JSON-first. It blocks invalid input so you do not accidentally encode broken payloads and then debug the wrong thing later.
Preserve mode keeps the original validated JSON text exactly as entered, including whitespace. Minified and Pretty modes first normalize the JSON text before encoding it.
Yes. The encoder converts the JSON text to UTF-8 bytes before producing Base64, which avoids the Unicode problems that come from passing arbitrary strings straight into btoa().
No. All validation, serialization, and Base64 encoding happen locally in your browser. No data is uploaded or stored.