Format JSON

The usual stumbling blocks

The comma behind the last entry. Allowed in JavaScript, prohibited in JSON. The most common error ever, and the message points to the Next Line - there is the closing bracket, on which it stands out.

Simple quotation marks. JSON knows only double, even with the keys. {'a': 1} is invalid; {"a": 1} is right.

Comments. JSON has none. // Begins, breaks off every parser.

Arrange keys

The switch sorts alphabetically, recursively across all levels. Useful when comparing two files that should contain the same thing: If the keys are ordered, a line comparison shows only the real differences instead of the order.

Structured data for your website generates Schematic generator .

Where JSON appears on a website

Most visible in the structured data: The block application/ld+json In the head of a page, search engines describe what it's all about -- a company, a product, a questionnaire. Google No longer reads the whole block; the rich results stay out without the page looking different.

In addition: answers from programming interfaces, translation files, manifest.json For web apps and the configuration files of almost every tool, the same applies everywhere – the file works completely or not at all.

Why this is in the browser

JSON often contains exactly what you don't load onto external servers: access data from a configuration, customer data from an interface response, internal addresses. This tool doesn't send anything to a server - the formatting happens in your browser, and what you insert does not leave the computer. With many online formatters who don't say that, the question is where the inserted data ends up.