JSON Path Finder Online: How to Query JSON with JSONPath Expressions

Paste your JSON into FindUtils' free JSON Path Finder, type a JSONPath expression like $.users[0].name, and see the matched values instantly — no installation, no signup, no data uploaded to servers. The tool evaluates your expression in real time, shows the extracted results as formatted JSON, and displays every resolved path so you can copy them with a single click.

JSONPath is a query language for JSON, often described as "XPath for JSON." It lets you navigate complex nested structures, filter arrays by conditions, and extract exactly the data you need using a concise expression syntax. This guide covers everything from basic dot notation to advanced filter expressions, with practical examples you can test directly in the playground.

What Is JSONPath and Why Does It Matter?

JSONPath is a standardized query language (formalized as RFC 9535 in February 2024) that lets you select and extract specific values from JSON documents. Every expression starts from the root ($) and uses a combination of dot notation, bracket notation, wildcards, and filters to navigate to target data.

Here's why developers use JSONPath daily:

• API response parsing — Extract 3 fields from a 200-line API response without writing a single line of JavaScript
• Configuration management — Query deeply nested config files to find specific settings
• Test automation — Validate specific values in JSON responses using JSONPath assertions
• Data pipelines — Extract and route data based on JSONPath selectors in tools like AWS Step Functions, Postman, and JMeter
• Log analysis — Pull specific fields from structured JSON logs

JSONPath is supported natively by Postman, JMeter, Jayway (Java), AWS Step Functions, Kubernetes, and dozens of other tools. Learning the syntax once lets you use it everywhere.

How to Use the JSON Path Finder (Step by Step)

Step 1: Open the Tool and Load JSON Data

Navigate to FindUtils' JSON Path Finder. You'll see a query bar at the top and two panels below: JSON Input on the left and Result on the right. Paste your JSON data into the input panel, or click the Load Sample button to start with example data containing users, metadata, and nested objects.

You can also drag and drop a .json file directly into the input panel. The tool accepts any valid JSON — objects, arrays, strings, or numbers.

Step 2: Write a JSONPath Expression

Type your JSONPath expression in the query bar. The default expression is $, which returns the entire document. Build from there:

• $.users — Access the "users" array
• $.users[0] — Get the first user
• $.users[*].name — Get all user names
• $.users[?(@.age>25)] — Filter users older than 25

Results update in real time as you type. The match count and execution time are displayed next to the query bar.

Step 3: Explore Built-In Examples

Click the Examples button to browse 19 categorized JSONPath queries:

• Basics — Root access, property access, array indexing, nested navigation
• Wildcards & Slicing — All elements, field extraction, array slices
• Recursive Descent — Finding fields at any depth with ..
• Filters — Boolean, numeric, and string comparisons

Click any example to load it into the query bar instantly.

Step 4: Copy Matched Paths

When your expression returns results, the resolved paths appear as clickable chips above the output (e.g., $.users[0].name, $.users[1].name). Click any path to copy it to your clipboard. This is the core "path finder" functionality — discover the exact path to any value in your JSON.

Step 5: Export Results

Use the Copy button to copy the entire result to your clipboard, or click Download JSON to save the output as a file. Press Enter after writing an expression to save it to your query history for quick re-use.

JSONPath Syntax: The Complete Reference

Basic Navigation

Dot notation works for simple property names. Bracket notation handles special characters like hyphens, spaces, or dots in property names.

Wildcards and Slicing

Wildcards are essential for extracting the same field from every object in an array — one of the most common JSONPath operations.

Recursive Descent

Recursive descent (..) is JSONPath's most powerful navigation feature. It searches the entire document tree and returns every match, regardless of how deeply nested it is. Use it when you know the field name but not its exact location.

Filter Expressions

Filters let you select array elements that match a condition. The @ symbol refers to the current element being evaluated.

Supported operators: ==, !=, >, <, >=, <=. The right-hand value can be a number, string (in double quotes), boolean (true/false), or null.

Practical JSONPath Examples

Extracting Data from an API Response

Suppose you receive this JSON from a REST API:

{
  "data": {
    "users": [
      {"id": 1, "name": "Alice", "email": "[email protected]", "role": "admin"},
      {"id": 2, "name": "Bob", "email": "[email protected]", "role": "user"},
      {"id": 3, "name": "Charlie", "email": "[email protected]", "role": "user"}
    ],
    "pagination": {"page": 1, "total": 42}
  }
}

Common queries you'd run in the JSON Path Finder:

$.data.users[*].name          → ["Alice", "Bob", "Charlie"]
$.data.users[0].email         → "[email protected]"
$.data.users[?(@.role=="admin")]  → [{"id":1, "name":"Alice", ...}]
$.data.pagination.total       → 42
$..email                      → ["[email protected]", "[email protected]", "[email protected]"]

Navigating Nested Configuration Files

JSON config files for applications, Kubernetes manifests, and infrastructure-as-code templates often have deep nesting:

$.database.connections.primary.host    → "db-prod.example.com"
$.services[*].port                     → [8080, 3000, 5432]
$.services[?(@.port==8080)].name       → ["api-gateway"]
$..timeout                             → [30, 60, 120]

Filtering E-Commerce Product Data

$.products[?(@.price<=50)]             → Products under $50
$.products[?(@.inStock==true)]         → Available products only
$.products[*].category                 → All category names
$..reviews                             → All reviews from any product

Extracting Test Results from CI/CD Pipelines

Build tools and test runners output JSON results. JSONPath makes it easy to extract specific metrics:

$.testSuites[*].name                   → All suite names
$.testSuites[?(@.failures>0)]          → Suites with failures
$..duration                            → All durations
$.summary.totalTests                   → Total test count

JSONPath vs jq: When to Use Which

Both JSONPath and jq query JSON data, but they solve fundamentally different problems. JSONPath selects data; jq transforms it.

Recommendation: Use JSONPath when you need to locate and extract specific values — especially in tools that already support it (Postman, JMeter, AWS). Use jq (try FindUtils' JQ Playground) when you need to transform, aggregate, or reshape data.

Free Online JSON Path Finder Tools Compared (2026)

FindUtils' JSON Path Finder is optimized for learning and daily use: 19 built-in examples, a quick-reference panel, query history, and clickable path chips make it the most feature-rich free option for developers who want to test JSONPath expressions quickly. For strict RFC 9535 compliance, jsonpath.com and jsonpath-evaluator.com are good alternatives.

Common JSONPath Mistakes and How to Fix Them

Mistake 1: Forgetting the Root Symbol ($)

Wrong: .users[0].name (missing $) Right: $.users[0].name

Every JSONPath expression must start with $ to indicate the root of the document.

Mistake 2: Using Dot Notation for Special Characters

Wrong: $.content-type (hyphen breaks dot notation) Right: $['content-type']

Property names containing hyphens, dots, spaces, or other special characters require bracket notation with quotes.

Mistake 3: Confusing Wildcards with Recursive Descent

$[*] and $.. are different:

• $.users[*].name — Gets names from the users array only
• $..name — Gets ALL "name" fields at every level of the document

Use [*] when you know the exact array location. Use .. when you need to search the entire tree.

Mistake 4: Expecting Transformed Output

JSONPath extracts data — it cannot transform it. If you need to rename fields, merge arrays, or calculate aggregates, use jq instead. FindUtils' JQ Playground handles these transformations.

Mistake 5: Missing Quotes in String Filters

Wrong: $.users[?(@.role==admin)] (unquoted string) Right: $.users[?(@.role=="admin")]

String values in filter expressions must be wrapped in double quotes. Numbers and booleans (true, false, null) do not need quotes.

JSONPath in the Real World

JSONPath isn't just a learning exercise — it's embedded in tools developers use daily:

• Postman — Uses JSONPath in test assertions: pm.expect(jsonData.users[0].name).to.equal("Alice")
• JMeter — JSON Extractor post-processor uses JSONPath to extract values from API responses
• AWS Step Functions — Uses JSONPath for input/output processing in state machines
• Kubernetes — kubectl get pods -o jsonpath='{.items[*].metadata.name}'
• Jayway JsonPath (Java) — The most popular JSONPath library, used in Spring Framework
• Rest Assured (Java) — API test framework with built-in JSONPath assertion support

Learning JSONPath syntax in a playground means you can apply it immediately across all these tools.

Tools Used in This Guide

• JSON Path Finder — Test JSONPath expressions in your browser with real-time results, 19 examples, and clickable path chips
• JQ Playground — Test jq expressions for data transformation, aggregation, and reshaping
• JSON Formatter — Pretty-print and validate JSON before querying it with JSONPath
• JSON Visualizer — Visualize JSON structure as an interactive tree to understand nested data before writing expressions
• JSON Diff — Compare two JSON documents to verify extraction results

FAQ

Q1: What is JSONPath and what is it used for? A: JSONPath is a query language for JSON documents, standardized as RFC 9535 in 2024. It lets you navigate JSON structures and extract specific values using expressions like $.users[0].name. Developers use it in API testing (Postman, JMeter), infrastructure management (Kubernetes, AWS Step Functions), and data extraction pipelines.

Q2: Is the FindUtils JSON Path Finder free to use? A: Yes. FindUtils' JSON Path Finder is completely free with no signup, no ads, and no usage limits. All processing happens in your browser — your JSON data is never sent to any server.

Q3: What is the difference between JSONPath and jq? A: JSONPath is a query language for extracting values from JSON (like SQL SELECT). jq is a full programming language that can extract, transform, aggregate, and construct new JSON. Use JSONPath for simple data extraction; use jq when you need to reshape or calculate data. Try the FindUtils JQ Playground for jq.

Q4: How do I find the path to a specific value in JSON? A: Paste your JSON into the FindUtils JSON Path Finder and start with $ to see the full document. Use the Examples button to explore common query patterns. When your expression returns results, the resolved paths appear as clickable chips above the output — click to copy any path instantly.

Q5: What's the best free JSONPath tester online in 2026? A: FindUtils offers one of the most feature-rich free JSONPath testers available. It includes 19 built-in examples, an embedded syntax reference, query history, drag-and-drop file upload, and clickable path chips — all with client-side processing for maximum privacy. For strict RFC 9535 compliance testing, jsonpath.com is also a solid choice.

Q6: Is it safe to paste sensitive JSON into an online tool? A: On FindUtils, yes. All processing happens in your browser using JavaScript — your JSON data is never transmitted to any server. There's no backend, no logging, and no data storage. Verify by checking your browser's network tab while using the tool.

Q7: What JSONPath features does the FindUtils tool support? A: The tool supports dot notation ($.field), bracket notation ($['key']), array indexing ($[0], $[-1]), array slicing ($[0:3]), wildcards ($[*]), recursive descent ($..field), and filter expressions with comparison operators (==, !=, >, <, >=, <=). This covers the vast majority of real-world JSONPath use cases.

Q8: How do I filter JSON arrays with JSONPath? A: Use filter expressions with the @ symbol: $.users[?(@.age>25)] returns users older than 25, $.items[?(@.active==true)] returns active items, and $.products[?(@.price<=100)] returns products priced at 100 or less. Test filters instantly in the JSON Path Finder.

Next Steps

• The Complete Guide to Online JSON Tools — Explore the full suite of JSON tools for formatting, validation, comparison, and conversion
• JQ Playground Guide: Test & Run jq Expressions Online — Learn jq for data transformation when JSONPath's extraction-only approach isn't enough
• How to Compare Two JSON Files Online — Compare JSON documents after extracting data with JSONPath
• JSON Schema Validation Explained — Validate the structure of JSON data you're querying