Base64 to JSON
Decode Base64 or base64url back into readable, validated, and pretty-printed JSON.
Validate and encode JSON as Base64 or base64url instantly. Free, private, and 100% in your browser.
Base64 is the standard way to embed JSON in places that only accept plain characters: HTTP headers, query strings, environment variables, config values, and tokens. This encoder validates your JSON first and then produces standard Base64 or URL-safe base64url.
Your JSON is checked before encoding, so you never encode a broken payload by accident.
Accented letters, non-Latin scripts, and emoji are encoded correctly, unlike the browser's built-in btoa().
Encode exactly as typed, minified to save space, or pretty-printed.
Switch to the URL-safe alphabet (- and _ without padding) used by JWTs and URLs.
Optionally wrap the output at 76 characters for email and PEM-style formats.
Encoding runs entirely in your browser. Your data is never uploaded.
{"user":"ada","role":"admin","exp":1767225600}eyJ1c2VyIjoiYWRhIiwicm9sZSI6ImFkbWluIiwiZXhwIjoxNzY3MjI1NjAwfQ==eyJ1c2VyIjoiYWRhIiwicm9sZSI6ImFkbWluIiwiZXhwIjoxNzY3MjI1NjAwfQBase64 turns any text into a safe set of characters that survives HTTP headers, URLs, environment variables, cookies, and systems that do not handle quotes or line breaks well. JWT payloads, Kubernetes Secrets, and data URIs all use Base64-encoded JSON.
Standard Base64 uses + and / and pads with =. base64url replaces + with - and / with _ and usually drops the padding, so the result can be used in URLs and file names without escaping. JWTs use base64url.
No. Base64 is an encoding, not encryption. Anyone can decode it, so never use it to protect passwords or secrets.
Yes. The JSON is first encoded as UTF-8 and then as Base64, which is the standard approach. The browser's btoa() function fails on these characters; this tool does not.
No. Encoding runs entirely in your browser. Your JSON never leaves your device.
Decode Base64 or base64url back into readable, validated, and pretty-printed JSON.
Convert JSON to well-formed XML with custom root and item names, attributes, and indentation.
Turn JSON arrays into CSV for Excel or Google Sheets, with nested object flattening and custom delimiters.
Convert JSON to clean, readable YAML for Kubernetes, Docker Compose, CI pipelines, and config files.