How is this different from the JSON Formatter?

The Formatter focuses on pretty-printing and validation. The workspace adds an interactive tree, JSONPath queries, schema inference and YAML/CSV conversion around the same input, so you can complete a whole task without switching tools.

Which JSONPath features are supported?

Root $, child .key and ['key'], array indices including negatives, [start:end:step] slices, wildcards .* and [*], and recursive descent ..key. Filter expressions ?() and script expressions are not supported and raise an error.

Why does CSV export reject my JSON?

CSV is a flat table, so export needs an array of objects (one object per row). A single object or an array of scalars has no row structure; reshape it into an array of objects first.

Can I trust the generated schema?

It is inferred from one sample, so it captures that sample's shape. Fields missing from some records become optional, and mixed array element types become anyOf. Treat it as a starting point to review, not a final contract.

JSON Developer Workspace — Guide

A professional JSON workspace — format and validate, explore an interactive tree, query with JSONPath, infer JSON Schema, and convert to YAML or CSV, all in your browser.

What it is and when to use it

Most JSON work is not a single operation but a chain: you receive a payload, format it to read it, inspect the structure to understand it, extract the few fields you actually need, and then hand the result to another system in YAML or CSV. Doing that across separate tools means pasting the same document repeatedly and losing context at every hop. This workspace keeps one input and lets you move between formatting, a structural tree, JSONPath queries, schema inference and conversion against that same document. The design borrows the idea behind professional data tools — that understanding structure and querying it matter more than pretty-printing alone — while keeping everything in your browser. JSONPath here is a deliberately bounded subset: it covers navigation, wildcards, slices and recursive descent, which handle the overwhelming majority of real extraction tasks, and it fails loudly on unsupported syntax so you never mistake a syntax error for an empty result. Schema inference walks the sample and merges array element types, taking the intersection of object keys for required fields, so a field present in only some records is correctly marked optional.

A single workspace for the whole JSON task: format and validate, explore the structure as a collapsible tree, query values with JSONPath, infer a JSON Schema from a sample, and convert to YAML or CSV — without bouncing between five separate tools.

How to use it

Paste or type your JSON into the input box; syntax errors are reported with the parser message.
Use the Format tab to pretty-print at your chosen indent and optionally sort keys.
Switch to Tree to expand and collapse the structure, or Query to pull values with a JSONPath like $.store.book[*].title.
Use Schema to infer a draft-07 schema from the sample, or Transform to export YAML or CSV.

A worked example

Fill in sample JSON

{"store":{"book":[{"title":"Sayings of the Century","price":8.95},{"title":"Moby Dick","price":8.99}],"bicycle":{"color":"red","price":19.95}}}

Copy this into the tool, or open JSON Developer Workspace

Things that trip people up

The Query tab supports $, .key, ['key'], [n] (negative indices count from the end), [start:end:step] slices, .* and [*] wildcards, and ..key recursive descent. Filter expressions like ?(@.price) are not supported and raise a clear error rather than silently returning nothing.
CSV export requires an array of objects; the header is the union of keys across rows. Non-array input is rejected with an explanation instead of producing a malformed file.
The inferred schema describes the shape of your sample, not a guaranteed contract — review required fields and types before relying on it.

Questions people ask

How is this different from the JSON Formatter?: The Formatter focuses on pretty-printing and validation. The workspace adds an interactive tree, JSONPath queries, schema inference and YAML/CSV conversion around the same input, so you can complete a whole task without switching tools.
Which JSONPath features are supported?: Root $, child .key and ['key'], array indices including negatives, [start:end:step] slices, wildcards .* and [*], and recursive descent ..key. Filter expressions ?() and script expressions are not supported and raise an error.
Why does CSV export reject my JSON?: CSV is a flat table, so export needs an array of objects (one object per row). A single object or an array of scalars has no row structure; reshape it into an array of objects first.
Can I trust the generated schema?: It is inferred from one sample, so it captures that sample's shape. Fields missing from some records become optional, and mixed array element types become anyOf. Treat it as a starting point to review, not a final contract.

Next steps

Open the JSON Developer Workspace tool

Spotted something wrong on this page? Tell us via Contact Us