JSONfmt provides JSON formatting, validation and inspection tools for general informational and development purposes. Here’s what that means in practice.

A validator, not a guarantee

“Valid JSON” means the text conforms to RFC 8259’s grammar — nothing more. It does not mean the data is correct, safe, complete, or shaped the way your application expects. A document can be perfect JSON and still contain wrong numbers, an expired token, or a role field your API rejects. Structural expectations are a separate layer — see what JSON Schema is — and data correctness is a separate layer above that.

Parsers differ at the edges

We check syntax against the strict JSON grammar and cross-check with your browser’s JSON.parse. Edge cases exist where implementations legitimately differ: duplicate object keys (legal, last-wins — but some systems disagree), numbers beyond IEEE-754 precision, and depths beyond parser recursion limits. When a payload matters, test it in the parser that will actually consume it.

Formatting changes bytes, not meaning

Minifying removes insignificant whitespace; sorting keys changes object member order. Both produce equivalent JSON for any spec-compliant consumer — but they change the byte sequence, so checksums, signatures (JWT, webhook HMACs) and byte-exact diffs will differ after formatting. Re-sign payloads after transforming them, never before.

Advertising

The site may display third-party advertising (for example Google AdSense) to cover hosting costs. Advertisers don’t influence what the tool reports — an ad is a rectangle on the page, not an opinion about your JSON.

Liability

To the maximum extent permitted by law, JSONfmt and its maintainers are not liable for losses arising from use of this site or reliance on its output — including corrupted configs, rejected API calls, and payloads formatted at 2 a.m. that looked fine at the time. When the JSON matters, validate it at the boundary where it’s consumed.