Explorer
Tree explorer will appear here once JSON is loaded
Inspector
Select a node to inspect it
Tree explorer will appear here once JSON is loaded
Select a node to inspect it
Paste JSON and Jsontify lints it against strict RFC 8259 JSON - the actual specification, not the more forgiving dialect that some parsers and languages tolerate. Trailing commas, single-quoted strings, unquoted object keys, // and /* */ comments, and NaN/Infinity are all flagged, even though plenty of hand-written config files and LLM output contain exactly these.
Each lint failure reports the precise line and column, plus a plain-English reason ('Trailing comma before }', 'Object keys must use double quotes') instead of a bare parser exception, so fixing it by hand takes seconds rather than a manual character-by-character hunt.
This kind of strict linting matters most right before JSON goes somewhere that will not tolerate the loose dialect - a strict API consumer, a schema validator, a CI pipeline step - where a trailing comma that "worked fine" in a JavaScript file will hard-fail.
If you'd rather have working JSON than a strict lint report, the Repair tool on the same page runs a dedicated pass that automatically fixes the common lint failures - trailing commas, missing quotes, stray comments - in a single undoable step, entirely in your browser.