JSONPath Extractor

1. Paste JSON into JSON input, drop a .json file, or choose browse files.
2. Check the document tree after valid JSON is parsed. An invalid document reports its line and column.
3. Click a rendered key or value, or type into JSONPath expression. The quick-insert buttons add common path pieces at the cursor.
4. Set Result limit when needed. Results update as the expression changes.
5. Use Copy paths, Copy values (JSON), or an export control for the current matches.

How to query JSON with JSONPath

Start at $, the document root. Dot notation walks through named properties, while bracket notation handles names such as in stock. Wildcards select every property or array item, recursive descent searches below the current level, and negative indices select from the end.

{"store":{"book":[{"title":"Dune"}]}}
$.store.book[*].title
$.store.book[0].title = "Dune"

Array slices use start:end:step. Unions select several indices or property names, such as $.store.book[0,2]. Each result row keeps the concrete path, JSON type, and value preview together.

How JSONPath filters select values

Use a filter inside [?(...)]. The @ symbol refers to the item being tested, and $ refers to the document root. Comparisons accept numbers, strings, booleans, and null. Use &&, ||, !, and parentheses to combine conditions.

For example, $.store.book[?(@.price < 20)] keeps entries whose price is below 20. A bare path such as [?(@.discount)] keeps values where that property exists and is neither null nor false. Nested filters, function calls, and regular-expression operators are unsupported.

What the JSONPath result limit changes

Result limit starts at 500 and accepts up to 5000. If a query finds more, the summary shows the displayed count and total count. The document tree renders the first 500 entries of each object or array. Entries left out of the tree remain queryable when you type their path.

An invalid JSONPath expression clears the current results and shows an error below the query field. An expression that creates more than 300,000 intermediate nodes also fails and asks for a narrower path.

Export JSONPath matches

Export JSON creates an array of { path, type, value } objects. Export JSONL writes one match object per line. Export TXT writes tab-separated paths and values. Export CSV uses object keys as columns when every match is an object; otherwise it uses index, path, type, value.

JSONPath Extractor selects and exports matches. It does not mutate, flatten, reformat, validate, or compare the source JSON. Parsing, tree rendering, and query evaluation happen in the browser. The page makes no request containing the JSON you paste or upload.

Where JSONPath queries come up

A developer can inspect a nested API response, click a title in the tree, then export matching records as JSONL for a fixture or script.

An analyst can filter an array with @.price < 20, export object matches as CSV, and open the columns in a spreadsheet.

A support engineer can copy concrete paths from a configuration document into a ticket while keeping the source JSON in the browser.

JSONPath Extractor or JSON-LD Extractor?

JSONPath Extractor belongs to JSON Extract Tools and suits a JSON document you want to query by path. Choose JSON-LD Extractor when the source is HTML and you need each JSON-LD block parsed independently in source order.

Frequently asked questions