Resources
The written material behind the tools — what JSON actually requires, why a conversion loses something, and what a specific parser error means. Every page ends where the work starts, at the tool that does the job.
Guides
All 13 guides →What is JSON?JSON is a text format for structured data. It has six value types, one page of grammar, and a handful of rules that trip people up constantly.How to format JSONFormatting re-prints a document with consistent indentation. The choices that matter are the indent width, whether to sort keys, and what happens to very large numbers.How to validate JSONThere are two different questions hiding behind "is this JSON valid": does it parse, and does it match the shape it is supposed to have.Common JSON syntax errorsNearly every failed parse is one of a dozen mistakes. Here is each one, what the parser says about it, and the fix.JSON vs YAMLYAML is a superset of JSON, which makes conversion in one direction lossless and in the other direction a decision about what to discard.JSON vs XMLThe two formats model different things. Converting between them is not a translation; it is a series of decisions, and every converter has to make them.JSON vs CSVCSV holds rows of text. JSON holds a typed tree. Every conversion between them either flattens something or invents something.How to convert JSON to CSVThe conversion itself takes a second. Getting a file that opens correctly and still means what the JSON meant takes four decisions.How to open a JSON fileA .json file is plain text. Anything that opens a text file will open it — the question is what makes it readable.How to compare two JSON filesA line-by-line diff of two JSON documents reports differences that are not differences. A structural diff compares values.How to handle large JSON filesThe limit is rarely the file size. It is what loading it into memory as objects, and rendering it as DOM nodes, actually costs.JSON data types explainedSix types, and about a dozen edge cases that cause almost all real-world bugs.JSON escape charactersEight escape sequences plus \uXXXX. Everything else after a backslash is a syntax error.
Examples
All 3 example sets →JSONPath examplesOne sample document, and the expressions people actually need against it, each with the result it produces.JSON Schema examplesSchemas that do something, from a five-line object check up to conditionals and reusable definitions.JSON API response examplesThe response shapes you meet in practice, and what each convention costs the client that consumes it.
The tools themselves
72 tools across four categories, plus the unified workspace.
JSON WorkspaceOne editor for format, validate, repair, query, diff and convert.JSON ToolsFormat, validate, repair, diff and explore a JSON document.ConvertersMove data between JSON, CSV, XML, YAML, SQL and more.Code GeneratorsTurn a JSON sample into typed models for 13 languages.Developer ToolsEncoding, hashing, time, colour, regex and formatters.All 72 toolsThe complete list, filterable by name, format or keyword.