Short answer
- Formatting changes layout for readability or compactness.
- Formatting is not the same as proving business logic, query results, security, or application correctness.
- Use a diff when you want to compare formatted output with the original text.
JSON formatting
JSON formatting pretty-prints or minifies JSON text. Because JSON syntax is strict, parsing can catch malformed JSON syntax before formatting succeeds.
A JSON formatter does not prove that the data matches an application contract or business rule.
SQL formatting
SQL formatting reflows clauses, indentation, and keyword casing so a query is easier to read.
SQL dialects differ. A formatter should be treated as a readability aid unless a database engine or dialect-aware parser verifies the query.
Formatting vs validation
- JSON parse errors can identify invalid JSON syntax.
- SQL formatting does not guarantee dialect-specific correctness.
- Neither formatter proves that the data or query is safe for a particular application.
Minifying
Minifying JSON removes extra whitespace when a compact payload is useful.
Minifying SQL is usually for compact transfer or generated queries, not for human review.
Comparing before and after
After formatting or minifying, compare the original and output if you need to inspect exactly what changed.
Local processing note
The current Tidy Utils formatting and diff tools process pasted text in the browser.
FAQ
Is formatting the same as validation?
No. Formatting changes layout. Validation checks whether input satisfies a syntax, schema, dialect, or application rule.
Does a JSON formatter validate JSON?
A JSON formatter that parses JSON can catch malformed JSON syntax, but it does not validate application-specific meaning.
Does a SQL formatter validate SQL?
A SQL formatter can improve readability, but it does not guarantee that a query works in a specific database dialect.
Can I compare formatted output to the original?
Yes. Use a text diff after formatting or minifying to inspect the changed text.