How to Format and Validate JSON Without Exposing Private Data

JSON is easy for software to generate and surprisingly easy for a person to break. One missing quote, trailing comma or unescaped line break can stop a configuration file or API request from parsing.

A formatter makes structure visible. A validator answers a different question: whether the text follows JSON syntax. Neither can tell you whether the values are correct for a particular API.

Pretty-print, validate and minify

These actions serve different stages:

• Pretty-print adds indentation and line breaks so nesting is readable.
• Validate parses the text and reports whether the syntax is valid.
• Minify removes unnecessary whitespace for compact storage or transmission.

Vootkit's JSON Formatter uses the browser's JSON parser. Pretty-print produces two-space indentation, Minify removes formatting whitespace, and Validate reports a parsing error without sending the text to Vootkit.

Protect secrets before pasting

JSON often contains material that should not enter a third-party server: API keys, bearer tokens, email addresses, customer records, internal URLs and authentication cookies.

Even when a formatter promises deletion, uploading production payloads expands the number of systems that handle them. Use a local browser tool or sanitize a copy first. Replace secrets with obvious placeholders while preserving the same data type and structure.

For example, replace a real token with "REDACTED_TOKEN", not with an unquoted word that creates a new syntax error.

Format JSON step by step

1. Make a copy of the payload.
2. Remove or replace secrets and personal information when possible.
3. Open JSON Formatter.
4. Paste the JSON.
5. Select Validate to check syntax.
6. Select Pretty-print to inspect the structure.
7. Correct the source, not merely the formatted output.
8. Use Minify only when a compact representation is required.

Copy the result and test it in the system that defines the expected schema. Valid JSON can still contain a misspelled property, wrong data type or unsupported value.

Common JSON errors

Trailing commas

JSON does not allow a comma after the final item in an object or array.

{"name":"Ada","active":true}

The comma after true would make that object invalid if another property does not follow.

Single quotes

JSON strings and property names require double quotes. JavaScript may accept single-quoted strings in source code; JSON does not.

Unquoted property names

{name:"Ada"} resembles a JavaScript object literal but is not valid JSON. Use {"name":"Ada"}.

Unescaped characters

A literal line break inside a quoted string is invalid. Encode it as \n. A double quote inside a string must be escaped as \".

Comments

Standard JSON has no comment syntax. Remove // and /* ... */ comments or use a format that explicitly supports them.

Numbers and special values

JSON supports ordinary decimal numbers, but not NaN, Infinity or undefined. Use null only when that meaning is appropriate for the receiving system.

Syntax is not schema

This object is valid JSON:

{"email":42,"items":"many"}

It may still be invalid for an API expecting email to be a string and items to be an array. Validation by JSON.parse confirms grammar, not business rules.

Use the API documentation, a JSON Schema validator or tests in the consuming application. JSON ↔ CSV is useful when the structure is tabular enough to flatten sensibly, and CSV Viewer & Sorter can then check the resulting rows and columns.

Compare a working and broken payload

When a request suddenly fails, format both the last working payload and the new one, then use Text Diff on sanitized copies. Differences in types and nesting become easier to see when property order and whitespace are consistent.

Do not publish real secrets in bug reports, screenshots or public repositories. Rotating a leaked key is safer than merely deleting the post because copies may already exist.

Common questions

Does formatting change the data?

Pretty-printing changes whitespace outside strings, not parsed values. Minifying does the reverse. Property order is usually preserved by the implementation but should not be treated as semantic in JSON objects.

Why does valid JSON still fail my API?

The API may require a particular schema, authentication, content type or value. Syntax validation is only the first layer.

Can JSON contain dates?

JSON has no date type. Dates are commonly represented as strings, and the required format belongs to the receiving system.

Is local formatting completely risk-free?

It avoids uploading the payload to Vootkit. You still need to protect the device, clipboard, browser extensions, screenshots and any place where you paste the result.

A safer debugging habit

Sanitize first, validate syntax, pretty-print for inspection, verify the schema and rotate any credential that may have been exposed. Readable JSON speeds debugging; disciplined handling prevents the debugging process from becoming the security incident.