JSON Validator & Formatter
Validate JSON and format it with readable indentation.
Read the guideRun the tool
The calculation runs in your browser. This tool does not send your input to JVR Software.
More information
Back to the toolWhat it is and when to use it
JSON Validator & Formatter checks whether a document follows JSON syntax and presents it with indentation so people can review it. Use it on an API response before debugging a field, on exported data before comparing records, or on a configuration file before submitting it to a program that expects JSON.
How it works
JSON represents objects, arrays, strings, numbers, booleans and null. The formatter validates syntax, then places structural punctuation on readable lines. Spaces inside a string are data and must be preserved. Formatting does not check that required business fields are present or that their values are valid for a particular API.
How to use it
- Paste the raw response or file content without Markdown code fences.
- Select Run tool and look at the indentation to identify object and array boundaries.
- If an error is reported, check for trailing commas, single quotes, comments and unescaped double quotes, then run it again.
Worked example
Paste {"users":[{"name":"Ava","active":true}],"count":1}. The formatted result puts the users array and its one object on separate indented lines. The count stays a number and active stays a boolean.
Reading the result
An indented result is useful for humans reviewing structure. Compare type as well as value. "1" is a string and 1 is a number. If a service rejects valid JSON, consult its schema and inspect field names, required values and supported types.
To diagnose an API rejection, start at the nearest enclosing object or array. Check whether the value was omitted, set to null, or sent with a different type. Those are three different payloads. This formatter preserves number spellings, string escapes and member order even when a downstream language might interpret them differently.
Common mistakes and limits
Formatting does not redact secrets, sort keys, check duplicate-member policy or guarantee compatibility with consumers that have different number precision. Duplicate keys are ambiguous between applications. For identifiers that must retain leading zeroes, use strings in the source data.
