If you work with web APIs, configuration files or modern JavaScript apps, you handle JSON every day. JSON stands for JavaScript Object Notation, and it has become the default format for exchanging data between systems because it is small, readable and supported by every programming language. The trouble starts when a response arrives as one long line, or when a file refuses to load because of a tiny syntax mistake. This guide explains what valid JSON looks like and how to format, validate and repair it in a few clicks.
What does JSON look like?
JSON is built from just two structures. An object is a set of name and value pairs wrapped in curly braces. An array is an ordered list of values wrapped in square brackets. Values can be strings, numbers, true, false, null, or other objects and arrays. A small example describes a user with a name, an age and a list of skills, and every property name and every string is written in double quotes.
Because the structure can nest many levels deep, indentation is what makes it readable. Machines do not need the spaces, so APIs usually send JSON with all whitespace removed. That compact form is called minified JSON, and reading it by eye is painful.
Step 1: Beautify the data
Open the JSON Formatter, paste your data into the input box and click Format. The tool re-indents the document so every level of nesting is visible. You can pick two spaces, four spaces or tabs, depending on your team's style. For large responses, switch to the tree view and collapse the branches you do not care about. This is the quickest way to find a single field inside a huge payload.
Step 2: Validate the syntax
Formatting only works when the JSON is valid. If it is not, a good validator tells you where the parser gave up. The most common problems are easy to recognise once you know them:
- Trailing commas. A comma after the last item of an object or array is allowed in JavaScript but not in JSON.
- Single quotes. JSON strings and property names must use double quotes. Single quotes are invalid.
- Unquoted property names. Writing name: "Ali" instead of "name": "Ali" is a very common copy and paste mistake from JavaScript code.
- Comments. JSON does not support comments. Remove anything that starts with // or /* before parsing.
- Missing brackets. Every opening brace or bracket needs a matching closing one. The error position usually points just after the real problem.
- Invalid values. Values such as undefined, NaN and Infinity are not valid JSON. Use null or a string instead.
When the validator reports a line and column, look at the character just before that position first. A missing comma or an extra quote there is the cause in most cases.
Step 3: Minify when you ship
After you have fixed and reviewed the data, you may want the smallest possible version, for example to embed it in a request body or an environment variable. Minifying removes spaces and line breaks without changing the content. For large documents this can reduce the size noticeably, although compression such as gzip on your server gives an even bigger saving.
Step 4: Compare and sort
JSON objects are unordered, so two documents can hold the same data but list properties in a different order. Sorting the keys alphabetically before comparing makes real differences stand out. It is a handy trick when you review configuration changes or compare responses from two environments.
Privacy matters
API responses often contain tokens, emails or internal identifiers. Before pasting data into any online tool, check where it is processed. Our formatter runs completely in your browser, so the text is never sent to a server. If you are working with highly sensitive data, you can also use your editor's built-in formatter or the command line, for example by piping data through a local JSON tool.
Quick checklist
- Use double quotes for all strings and property names.
- Never leave a trailing comma.
- Do not add comments to JSON files.
- Format while you debug, minify when you ship.
- Keep sensitive data in tools that run locally.
With these habits, JSON errors become a two-minute job instead of an afternoon of frustration. Try it now with the free JSON Formatter & Validator.