Developer Workflows

Format, Minify, and Base64-Encode JSON Privately

Pretty-print a messy payload, minify it for the request, Base64 it if you must - all in the browser, no upload.

By OneDevToolkit Team Published September 16, 2026 Updated September 24, 2026 7 min read
Developer workstation with dual monitors used for formatting and transforming JSON payloads

Half the “just format this JSON” sites will happily accept a body full of emails, tokens, or staging secrets. You don’t need that risk for a pretty-print.

Here’s the tiny local recipe I reach for instead.

Three steps, no upload

  1. JSON Formatter - catch broken braces early and make nested objects readable.
  2. JSON Minifier - strip whitespace when you need a compact request body.
  3. Base64 Encoder - for headers, data URIs, or whatever wrapper the API insists on.

Do this daily? Save the chain in Recipe Studio. Same idea, longer form: JSON → API recipe.

Easy ways to shoot yourself in the foot

Minifying garbage JSON just hides the error - format first. Don’t Base64 something that’s already Base64. And before you paste a “sample” into Slack for a teammate, strip live bearer tokens. Future-you will thank you.

More of the same neighborhood: Code tools, JSON converters, and JSON/API workflows.

Base64 in APIs: When It Helps and When It Hurts Developer Workflows · 6 min OpenAPI to Postman Without Cloud Converters Developer Workflows · 6 min Inspect HAR Files Without Uploading Them Anywhere Developer Workflows · 6 min

← All posts Browse tools