Developer

JSON Formatting, Validation, and Comparison Are Different Tasks

Learn JSON’s basic structure and when to format, validate, inspect, or compare two documents.

YF
Yes FreeTool editorial team
Technical content team
Published
8 min read
Table of contents

What JSON represents

JSON is a text syntax for values: objects, arrays, strings, numbers, booleans, and null. An object maps string keys to values; an array stores values in order.

{
  "name": "Moin",
  "role": "Developer",
  "active": true,
  "skills": ["TypeScript", "SQL"]
}

Here, name and role contain strings, active is a boolean, and skills is an ordered array. JSON has no comments, dates, functions, or undefined value in its standard grammar.

Validation answers “can this be parsed?”

Syntax validation checks rules such as double-quoted keys, matched braces, legal escapes, and the absence of trailing commas. This is invalid JSON:

{ "name": "Moin", }

Removing the trailing comma makes it syntactically valid. That still does not prove the data is correct for an application. Schema validation is a separate layer that might require name to be present or active to be boolean.

Formatting and viewing change presentation

Minified and indented JSON can represent the same parsed value. Formatting inserts whitespace and line breaks for readability; it does not repair ambiguous data or verify a business schema. A tree viewer adds navigation so nested arrays and objects are easier to inspect.

The JSON Viewer parses input and shows either formatted text or a tree. Because parsing is required, it also identifies syntax errors, but it is not a JSON Schema validator.

Comparison asks what changed

The JSON Compare tool parses two documents and recursively reports added, removed, and changed paths. Object key order and whitespace disappear during parsing, so they are not differences. Arrays are compared by numeric index, not by a record ID or as unordered sets.

A worked comparison

Original: {"status":"pending","count":2}
Updated:  {"status":"ready","count":2,"cached":true}

The parsed comparison reports $.status as changed and $.cached as added. It does not report count. If an item is inserted at the beginning of an array, later indexes shift and may create several differences even when those objects have IDs.

Use formatting for readability, parsing for syntax, schema validation for application rules, and comparison for revisions. If JSON is transported in an encoded field, read why Base64 is not encryption.

Continue reading

Related articles