Convert JSON to Base64

Encode a JSON object, array, or value as a Base64 string. Converts JSON into a safe ASCII representation for embedding in URLs, headers, environment variables, and other contexts where special characters aren't allowed.

Input (JSON)

Options

Base64 Chunks

Print base64 in chunks of a certain size. Each chunk gets printed on a new line.

Print base64 as-is without chunks. The entire output gets printed on one line.

Data URL

Create a data URL with the "data:application/json;base64" MIME type.

Output (Base64)

What It Does

How It Works

Convert JSON to Base64 changes data from Json into Base64. That is more than a cosmetic rewrite. Field layout, quoting, nesting, and even type representation can shift because the destination format has different rules and limits.

Conversion tools are constrained by the destination format. If the source can express nesting, comments, repeated keys, or mixed data types more richly than the target, the output may need to flatten or reinterpret part of the structure.

All processing happens in your browser, so your input stays on your device during the transformation.

Common Use Cases

Encode JSON configuration for environment variables
Prepare JSON payloads for URL query parameters
Create Base64-encoded data for API testing
Encode JSON for embedding in XML CDATA or HTML attributes
Prepare structured data for message queue payloads

How to Use

Paste or type your JSON into the input.
Click Encode to convert it to Base64.
Choose standard or URL-safe Base64 encoding.
Copy the Base64 string for use in your target system.
Optionally minify the JSON before encoding to reduce size.

Features

Standard Base64 and URL-safe Base64 output
Validates JSON before encoding
Optional minification before encoding (smaller output)
Shows the encoded string length
Handles any valid JSON structure

Examples

Below is a representative input and output so you can see the transformation clearly.

Input

{"name":"Ada","score":9}

Output

eyJuYW1lIjoiQWRhIiwic2NvcmUiOjl9

Edge Cases

Very large inputs can still stress the browser, especially when the tool is working across many JSON values. Split huge jobs into smaller batches if the page becomes sluggish.
Source values that look similar can map differently in the target format when data types are inferred, flattened, or serialized.
If the output looks wrong, compare the exact input and option values first, because Convert JSON to Base64 should be repeatable with the same settings.

Troubleshooting

Unexpected output often means the input is being split or interpreted at the wrong unit. For Convert JSON to Base64, that unit is usually JSON values.
If a previous run looked different, check for hidden whitespace, changed separators, or a setting that was toggled accidentally.
If nothing changes, confirm that the input actually contains the pattern or structure this tool operates on.
If the page feels slow, reduce the input size and test a smaller sample first.

Tips

Minify your JSON before encoding to reduce the Base64 string length by 20-40%. Whitespace and indentation add unnecessary bytes.

Why Encode JSON as Base64

JSON contains characters that are problematic in many contexts. Braces, brackets, quotes, and colons break URL parsing, XML embedding, and shell variable assignment. Base64 encoding converts JSON into a safe alphabet (A-Z, a-z, 0-9, +, /) that works everywhere. The trade-off is a ~33% size increase.

Standard vs URL-Safe

Standard Base64 uses + and / characters, which have special meaning in URLs. URL-safe Base64 replaces these with - and _, making the encoded string safe for query parameters, URL fragments, and filenames. Use URL-safe when the Base64 will appear in a URL; standard is fine for headers, environment variables, and database fields.

Size Considerations

Base64 encoding increases data size by approximately 33% (every 3 bytes become 4 characters). For a 1KB JSON document, the Base64 output is about 1.33KB. Minifying JSON before encoding removes whitespace, reducing the input size and therefore the encoded output. A pretty-printed 2KB JSON might minify to 800 bytes, encoding to just over 1KB.

Frequently Asked Questions

Does it validate the JSON first?

Yes. Invalid JSON produces an error. Only valid JSON is encoded.

What's the difference between standard and URL-safe Base64?

Standard uses + and /. URL-safe uses - and _ instead, which are safe in URLs without percent-encoding.

Does encoding preserve formatting?

The exact input (including whitespace) is encoded. Minify first if you want compact encoding.

How much larger is the Base64 output?

About 33% larger than the input. 750 bytes of JSON becomes roughly 1000 characters of Base64.

Can I encode JSON arrays?

Yes. Any valid JSON — objects, arrays, strings, numbers, booleans, null — can be encoded.

How do I decode it back?

Use Convert Base64 to JSON to reverse the encoding and restore the original JSON.