Guides
These are written for the parts of JSON where the answer is not obvious and the common advice is wrong or out of date. Number precision, flattening conventions, JSONPath dialects, what actually breaks at ten megabytes.
Everything measured here was measured, and the measurements say on what. Where something could not be verified, the page says that rather than guessing, because a site whose argument is correctness does not get to be sloppy about its own claims.
-
Why your JSON IDs keep changing value
JSON numbers are unbounded. IEEE 754 doubles are not. Everything else follows from that.
JSON Validator -
The ten JSON mistakes that actually break payloads
Ranked by frequency, not by how interesting they are, with the exact error message each one produces.
JSON Repair -
What actually breaks when JSON files get big
Every size threshold in JSON tooling comes from one specific limit, and the limit people warn you about is usually the wrong one.
JSON Beautifier -
NDJSON and JSON Lines: one record per line
A giant JSON array cannot be streamed, appended to, or partially recovered. One JSON value per line fixes all three.
NDJSON to JSON -
JSON, YAML or TOML: which to reach for
These three formats differ less in what they can express than in how they fail, and the failures are what you will spend your time on.
JSON to YAML -
JSON Schema: the parts that decide whether validation works
Most broken JSON Schema setups do not throw. They return valid on data that is wrong.
JSON Schema Generator -
JSONPath, the version that is actually specified
JSONPath was a blog post for seventeen years. RFC 9535 finally says what it means.
JSONPath Tester -
Flattening nested JSON to CSV without losing data
Every JSON to CSV converter makes a dozen undocumented decisions for you. These are the decisions.
JSON to CSV -
JSON has no comments, and that was on purpose
Comments were cut from JSON to protect interoperability, and that decision has cost every configuration file since.
JSON Repair -
JSON has no date type, so pick one and write it down
JSON has six types and none of them is a date, so every codebase invents one. Only one of the four common answers is safe.
JSON Validator -
JSON API response shapes that survive five years
Almost every painful API migration traces back to a shape decision made in an afternoon and frozen by the first integration.
JSON Schema Generator