Query JSON with JSONPath
online, free & instant

Query any JSON structure in seconds

No install. No account. No nonsense.

Related JSON tools

Common questions answered

What are JSON query languages?

JSON query languages provide structured ways to search, filter, and transform JSON data using declarative expressions. Unlike imperative code that loops through arrays, a query language lets you describe what you want and handles traversal automatically. Popular options include JSONPath, JMESPath, and jq — each with different syntax and capabilities.

This tool supports JSONPath for interactive querying. Type a query to extract nested values, filter arrays by conditions, or select specific fields. Query languages are particularly valuable when exploring unfamiliar JSON: instead of mentally parsing a 500-line response, you write a query to extract exactly the fields you need.

// Data
{"users":[
  {"name":"Alice","role":"admin"},
  {"name":"Bob","role":"user"},
  {"name":"Charlie","role":"admin"}
]}

// Query: $.users[?(@.role=="admin")].name

["Alice", "Charlie"]

// 2 matches found

Get the most out of this tool

• Start with $ (root) and add segments progressively — $.users, then $.users[0], then $.users[0].name — to explore data.
• Use filter expressions to find records matching criteria without writing loops or temporary variables.
• JSONPath is the most widely supported query language for JSON — learning it once applies across many tools and libraries.

Comparing JSON query languages — JSONPath, JMESPath, and jq

The JSON ecosystem has produced three primary query languages, each with different design goals and capabilities. JSONPath, inspired by XPath for XML, is the oldest and most widely embedded in tools and frameworks. JMESPath offers a formally specified, cross-platform consistent query language adopted as the standard by the AWS CLI and other cloud tools. jq is the most powerful — a full expression language for transformation and aggregation, not just querying. Understanding when to use each language is as important as understanding their syntax.

JSONPath (RFC 9535) uses $ as the root identifier and provides intuitive dot-notation ($.store.book[0].title) and bracket-notation access. Its .. recursive descent operator searches at any depth without specifying the exact path — $..price finds all price fields anywhere in the document. Filter expressions use ?(@.field == value) syntax. JSONPath is well-suited for path-based value extraction and is the query language of choice for tools like Postman, k6, AWS Step Functions, and JSON Schema's $ref resolution.

JMESPath (jmespath.org) was designed for strict specification compliance and consistent behavior across implementations. It lacks recursive descent but offers pipe operators for chaining: people[?active] | [0].name filters and then takes the first result's name. JMESPath's multi-select syntax creates new structures: people[*].{name: name, age: age} produces a new array of objects with only the specified fields. Its built-in functions — sort_by(), min_by(), max_by(), join() — enable common transformations without a full programming language.

jq's filter language is the most expressive but also the most complex to learn. It treats JSON as a stream of values and applies transformations to each value. The pipe operator | chains operations; the comma operator , produces multiple outputs; reduce accumulates results. jq programs can define functions, use variables ($x`), apply conditional logic (if-then-else), and handle errors with try-catch. For automation pipelines that require real data transformation rather than simple extraction, jq is the appropriate tool.