JSON Query and Explorer Tools

7 tools · free · nothing uploaded

Four query languages disagree about almost everything except the dollar sign, so each has its own page rather than a shared box with a dialect dropdown. If you do not yet know what you are looking for, start with the tree viewer and copy the path out.

Start here

jq playground Real jq, compiled to WebAssembly — the same filters your shell pipeline runs. JSONPath tester RFC 9535 alongside the legacy Goessner and Jayway dialects, which disagree more than you think. Tree viewer Collapse a large document down to the shape, then copy the path to any node. JMESPath tester The dialect the AWS CLI, Ansible and the Azure CLI use for --query. List all paths Every leaf in the document with its type and value, as a flat list you can grep. JSON Pointer Resolve an RFC 6901 pointer, or list every pointer a document contains.

Everything else in Query / Explore

Graph view — Force-directed / tree render, exports SVG.

Why these run in your browser

There is no server-side processing here and no upload step: the page loads, and from then on the parsing, converting and rendering happen in this tab using your machine's CPU. That has three consequences worth knowing about. Your data stays on your machine, which matters when the JSON is a production payload with real customer records in it. There is no file-size limit imposed by us, only by how much memory your browser will give the tab. And once the page has loaded, it keeps working with the network off.

The trade is that very large documents are bounded by browser memory rather than by a beefy server — somewhere past 50 MB a textarea gets sluggish, and dropping the file in is better than pasting it. The privacy page spells out what is and is not collected.