JSON packed into a single Base64 line — safe for variables, headers and URLs.
Reverse: Base64 to JSONDrop your file here
or choose one from your computer
up to 50 MB
Files never leave your device — everything runs in your browser
Some places accept only plain text without quotes, braces or line breaks: environment variables, HTTP headers, Kubernetes secrets, URL parameters, CI settings. The usual answer is to encode the JSON as Base64. The converter first removes all whitespace from the JSON, encodes it as UTF-8 so any language and emoji survive, and then writes Base64.
The standard alphabet uses + and / with = padding. Switch on URL-safe to get - and _ without padding — the variant used in URLs and JWT tokens. The data URL option adds data:application/json;base64, in front, so the result can be used directly as a link or a src attribute.
Large integers are encoded exactly as written, without rounding. To check the result or decode a value you received, use Base64 to JSON.
Nothing is uploaded: everything runs inside your browser, so API responses, configs, contact lists and datasets stay on your device.
A file, pasted text or the Sample; errors are reported before encoding.
Standard or URL-safe alphabet, plain Base64 or a data URL.
Copy the Base64 string or download it as a text file.