Paste JSON and it is laid out again with two spaces, four spaces or tabs. When it parses you also get how many keys the top-level object holds, or how many items the top-level array holds. When it does not parse you get the parser’s own message. The work is done by this page, so a response with a token in it is not sent anywhere.
This page loads no libraries at all. The work is done by the browser itself. Your file is read on your own machine and never sent anywhere. Open your browser’s network tab and watch while you use it.
The message from the browser’s own JSON parser, with Invalid JSON in front of it. Most browsers include the position where parsing stopped, though the wording differs between them. That position is where parsing gave up rather than where the mistake is: a bracket left open early is reported further down, at the first thing that could not follow it.
No. It reads strict JSON, so the comments and trailing commas that many configuration files tolerate come back as errors. They have to come out before the text will format.
No. This page has a text box and nothing else. There is no file picker and nothing to drop a file onto. The whole document has to fit in the box and in the memory the browser gives the tab.
The text is parsed and written out again, so more than the spacing can move. A repeated key keeps only its last value. Numbers come back in JavaScript’s form: 1.0 as 1, 1e3 as 1000, and past about seventeen digits the tail turns to zeros. String contents survive, but their escapes are rewritten, so A comes back as A.
Everything here is free and works the same way, in your browser.
A new DeskKit tool lands every week or two. Leave an address to hear about it. Nothing else is ever sent, and one click removes you.