어떤 JSONPath 구문이 지원됩니까?

도구는 다음을 지원합니다: $(루트), .key(자식), ..key(재귀 내림), [*](와일드카드), [0] / [-1](배열 인덱스), [1,2](유니온), ==, !=, >, =, <= 연산자가 있는 [?(@.field op value)] 필터 표현식.

속성 값으로 배열을 어떻게 필터링합니까?

필터 표현식을 사용하세요: $.items[?(@.price < 10)]은 가격이 10 미만인 모든 항목을 반환합니다. 필터를 연결하고 임의의 비교 연산자를 사용할 수 있습니다.

깊게 중첩된 구조를 쿼리할 수 있습니까?

예, 재귀 내림 연산자를 사용하세요: $..name은 문서의 모든 깊이에서 모든 'name' 필드를 찾습니다.

내 JSON이 서버로 전송되나요?

아니요. 파싱은 전적으로 브라우저에서 이루어지며, 데이터가 페이지를 벗어나지 않습니다.

JSONPath 쿼리 도구

이 도구에 대해

JSON 문서를 붙여 넣고 JSONPath 쿼리를 실행하여 필요한 데이터를 정확히 추출하세요. 루트($), 자식(.key), 재귀 내림(..key), 와일드카드([*]), 배열 인덱스, 유니온, [?(@.age > 18)]와 같은 필터 표현식을 지원합니다. 결과는 빠른 재실행을 위한 쿼리 히스토리와 함께 강조 표시된 JSON으로 표시됩니다.

사용 방법

1 1단계: 왼쪽 입력 패널에 JSON 데이터를 붙여 넣거나 입력하세요.
2 2단계: 쿼리 필드에 JSONPath 표현식을 입력하세요(예: $.store.book[*].author).
3 3단계: '쿼리 실행'을 클릭하거나 Ctrl+Enter를 눌러 실행하세요.
4 4단계: 강조 표시된 JSON으로 일치 결과를 확인하세요. '결과 복사'를 클릭하여 클립보드에 복사하세요.

What JSONPath is for

JSONPath is a query language for JSON, the way XPath is a query language for XML. Instead of writing loops to dig through nested objects and arrays, you write one compact expression that describes where the data you want lives, and the engine walks the structure and returns every matching value. This tool runs JSONPath expressions against JSON you paste, entirely in your browser, and shows the matched values with syntax highlighting and a match count. It's distinct from a JSON formatter or validator: those check and pretty-print the whole document, whereas JSONPath extracts specific pieces from it.

The syntax, piece by piece

Every expression begins with $, the root of the document. From there you chain steps:

Syntax	Meaning	Example
`.key` or `['key']`	Child by name	`$.store.bicycle`
`[n]`	Array element by index	`$.store.book[2]`
`[-1]`	Index from the end	`$.store.book[-1]`
`[]` or `.`	Every element/value (wildcard)	`$.store.book[*].author`
`..`	Recursive descent — search at any depth	`$..price`
`[a,b]`	Union — several indices or keys at once	`$.store.book[0,2]`
`[?(...)]`	Filter — keep elements matching a condition	`$.store.book[?(@.price < 10)]`

Inside a filter, @ refers to the current element being tested. This engine supports existence checks (?(@.isbn) keeps items that have an isbn field) and comparisons with ==, !=, >, <, >=, and <= against a number, a quoted string, or true/false/null.

A worked example

Using the bookstore JSON the tool loads by default — a store with an array of four book objects and a bicycle — here is how a few queries resolve:

$.store.book[*].author walks every book and pulls its author, returning all four author names.
$..price uses recursive descent to find every price anywhere in the tree — the four book prices and the bicycle's, five matches in total. The leading $.store is unnecessary because .. already searches everywhere.
$.store.book[?(@.price < 10)] filters the book array to just those under $10 — the two cheapest books — returning the whole object for each match, not only the price.
$.store.book[?(@.category == 'fiction')] keeps the three fiction titles; note the single quotes around the string value.
$.store.book[?(@.isbn)] is an existence filter: it returns only the books that carry an isbn field, ignoring the two that don't.

The results panel shows the count (e.g. "5 matches") and pretty-prints the matched values; a single match is returned as the value itself, multiple matches as an array.

Filter vs. wildcard: a common confusion

A wildcard [*] returns every element; a filter [?(...)] returns only elements that pass a test. People often reach for a filter when they mean a wildcard, or forget that a filter only operates on an array — in this engine, applying [?(...)] to a plain object yields nothing. So query the array, then filter: $.store.book[?(@.price >= 10)] works, but pointing a filter at a single object does not.

Practical tips

Use .. when you don't know the depth. If a field is buried at varying levels, $..fieldName finds them all without spelling out the path.
Quote string comparisons. Write @.status == 'active', not @.status == active — an unquoted bare word won't match.
Test incrementally. Start with $.store, confirm it returns the object, then add one step at a time. The match count tells you immediately when a step narrows to zero.
Click a sample query to load both the expression and the example JSON, then edit from there — the fastest way to learn the syntax by experiment.
Remember $ matches one value, not a list. Returning multiple values requires a wildcard, union, recursive descent, or filter somewhere in the path.

Where JSONPath is genuinely useful

It shines for pulling a few fields out of large API responses, writing assertions in API tests ("the response has at least one order with status shipped"), configuring data pipelines and log processors, and exploring an unfamiliar JSON payload without writing throwaway code. Many tools — from jq-style processors to test frameworks and no-code platforms — accept JSONPath-style expressions, so the syntax transfers widely.

Everything runs locally

The JSON you paste and every query you run are processed entirely in your browser by a JavaScript engine; nothing is uploaded. That means you can safely test queries against sensitive or proprietary JSON, and the tool keeps working with your network disconnected. (Note this is a focused JSONPath implementation covering the operators above; very advanced extensions like array slices and script expressions aren't part of it.)