Written by Sam Taylor — Full-Stack Developer. More about me →I once sent a minified JSON file to a client for review. They replied: "This is gibberish — can you send the actual data?" I had sent the right data, just in the wrong format. Here's when to beautify and when to minify.
Beautified JSON uses indentation (typically 2 spaces) and line breaks to make the structure visually obvious. A 100KB minified file becomes ~500KB when beautified. Use beautified JSON when: reviewing API responses during development, debugging data issues, sharing data with non-technical stakeholders, committing configuration files to git, or creating API documentation examples.
Minified JSON removes all unnecessary whitespace, producing the smallest possible file at the cost of readability. Use minified JSON when: sending data over the network (API responses), storing large datasets, embedding JSON in HTML or JavaScript, or reducing bandwidth costs at scale. The size difference is significant: beautified JSON with 2-space indentation is typically 3-5x larger than the same data minified.
Most JSON formatters do both. Formly's JSON tool has Format (beautify) and Minify buttons side by side — paste once, toggle between views. Format adds 2-space indentation. Minify strips everything to a single line. Both run in your browser with zero data upload.
Written by Sam Taylor — Full-Stack Developer. More about me →