Base64 to JSON Converter

Somewhere in almost every developer’s inbox is a ticket that reads: “the system sent me this string, what is it?” followed by a wall of characters ending in equals signs. It is base64 — and what it holds, nine times out of ten, is JSON. The string could be a JWT payload segment, a data URI from a marketing email, a cookie value, or metadata a cloud provider attached to a resource. Decoding it by hand means pulling out an old script, dealing with whitespace that breaks the parse, remembering that + and / mean something different in URL-safe contexts, and then still ending up with a wall of unformatted JSON.

Base64 to JSON Converter removes every one of those friction points. Paste the raw string — with or without whitespace, with or without a data: URL prefix, standard or URL-safe alphabet — and get back clean, pretty-printed JSON with the correct UTF-8 handling for Unicode content. If the decoded text turns out not to be JSON, you still get the text with a clear warning instead of a dead end. Live conversion, byte-accurate decoding, copy and download, all in the browser.

• Whitespace-tolerant: Newlines, tabs and spaces inside the base64 are stripped automatically — paste values as they arrived in an email.
• Data URI aware: data:application/json;base64, prefixes are detected and removed when the option is on.
• URL-safe support: - and _ characters from base64url (JWT, query strings) are mapped back to + and / automatically.
• Correct UTF-8 decode: Emoji and international characters return byte-for-byte identical to the original JSON.
• Pretty-printed output: Indentation of 2 or 4 spaces, or compact single-line output, chosen before decoding.
• Honest errors: Invalid base64 is flagged, and non-JSON decoded content is shown as text with a warning rather than hidden.
• Copy and download: One-click clipboard copy or save the decoded JSON as a file.
• Fully private: All decoding happens client-side — nothing is uploaded.

1. Paste the base64 string into the input pane. It may contain line breaks, spaces, a data: prefix, or even quotes copied from a log — those are handled.
2. Check the two options. Data URI stripping is on by default; URL-safe mapping should be on for JWT tokens, off for standard base64. The live output will usually make it obvious which one is needed.
3. Choose the output indentation — 2 spaces for readability, 4 for wide monitors, compact for round-tripping.
4. Read the result. Valid JSON is pretty-printed with a confirmation. Non-JSON content is shown with a warning instead of an error.
5. Copy or download the decoded JSON for use elsewhere.

Example 1 — Inspecting a JWT payload. A token arrives as eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyIjoiYWRtaW4iLCJyb2xlIjoib3duZXIiLCJleHAiOjE4MDAwMDAwMDB9.abc123. Paste the middle segment into this tool with URL-safe mode on: the claims come back as formatted JSON in seconds — no terminal one-liner required.

Example 2 — Email data URIs. A support email embeds a configuration as data:application/json;base64,ewogICJ0aGVtZSI6... Paste the entire value with the prefix included; the prefix is stripped and the config is decoded into readable JSON.

Example 3 — Cloud metadata. An EC2 instance user-data script stores application settings as a base64 blob. Decode it here to audit what the instance actually launched with, then edit and re-encode with the companion JSON to Base64 tool.

Example 4 — Debugging an API gateway. A gateway logs the request body as a single base64-encoded line, wrapped across several lines in the log file. Paste the wrapped value — whitespace is stripped, and the original payload is back in view.

• Decode without friction: No terminal, no scripts, no manual cleanup of whitespace or prefixes.
• JWT and token debugging in seconds: URL-safe mode plus UTF-8 decoding reads modern token payloads exactly.
• See the truth, not an error: Non-JSON content is still shown, so a confusing payload never becomes a dead end.
• Byte-accurate Unicode: What was encoded comes back exactly — no mojibake from a naive Latin-1 decode.
• Private by default: Payloads stay in your browser, which matters when the base64 contains real customer data.