What is the difference between JSONPath and dot notation?

JSONPath uses $ as the root and bracket notation for arrays (e.g., $.store.books[0].title), while dot notation uses plain dots with numeric indices for arrays (e.g., store.books.0.title). JSONPath is more expressive and supports wildcards and filters.

What is the maximum JSON size this tool supports?

The tool can handle JSON files up to several megabytes depending on your browser's memory. For very large files, the tree view may take a moment to render, but formatting and validation work quickly on any size.

Can I format and validate JSON with this tool?

Yes. The tool includes JSON formatting (pretty-print with 2 or 4 space indentation), minification (compress to single line), and validation that shows the exact line and position of any syntax errors.

100% Free — No Account Required

Free JSON Path Finder

Explore nested JSON visually. Click any key or value to instantly get its JSONPath expression and dot notation. Format, validate, minify, and search your JSON data — all in your browser.

Indent:

JSON Input Valid JSON Invalid JSON

Keys: Depth: Size:

JSONPath:

Dot Notation:

Total Keys

Max Depth

Arrays

Objects

How JSONPath Works

JSONPath is a query language for JSON, similar to XPath for XML. Learn the syntax to navigate any JSON structure.

Expression	Description	Example
`$`	Root object/element	$
`.key`	Child operator — access a property	$.store.name
`[n]`	Array subscript — access by index	$.items[0]
`[*]`	Wildcard — all elements in array/object	$.items[*].name
`..key`	Deep scan — search all descendants	$..price
`['key']`	Bracket notation — for special characters in keys	$['first-name']
`[start:end]`	Array slice — subset of array	$.items[0:3]

When to Use a JSON Path Finder

Whether you're debugging APIs, building integrations, or exploring data, finding the right path saves hours.

API Debugging

Paste API responses to quickly find the exact path to any field you need to extract in your code.

Data Extraction

Navigate complex JSON datasets to find paths for data pipelines, ETL processes, and transformations.

Config Exploration

Explore large configuration files (package.json, tsconfig, etc.) to find and reference settings paths.

Testing & QA

Validate API response structures and generate assertions using precise JSON paths for your test suites.

JSON Best Practices

Follow these tips to keep your JSON clean, readable, and easy to work with.

Use Consistent Keys

Stick to one naming convention — camelCase or snake_case — throughout your JSON structure.

Keep It Flat

Avoid deeply nested structures when possible. Flat JSON is easier to query, parse, and maintain.

Validate Early

Always validate JSON before processing. A missing comma or extra bracket can cause silent failures.

Use Meaningful Names

Choose descriptive key names like "orderTotal" instead of "ot" for self-documenting data structures.

Avoid Trailing Commas

Unlike JavaScript, JSON does not allow trailing commas after the last element in an array or object.

No Comments in JSON

Standard JSON does not support comments. Use JSONC or JSON5 if you need inline documentation.

JSON Path Finder FAQ

Common questions about JSON paths, formatting, and this tool

JSONPath is a query language for JSON data, similar to XPath for XML. It was introduced by Stefan Goessner in 2007 and provides a way to reference specific elements within a JSON structure using expressions like $.store.books[0].title. It's widely used in API testing tools like Postman, programming languages, and data processing pipelines.

Paste your JSON into this tool and use the interactive tree view. Expand objects and arrays by clicking the arrow icons, then click on any key or value to instantly see its full JSONPath and dot notation in the path bar below. You can also use the Search tab to find specific keys or values across the entire structure.

JSONPath starts with $ as the root and uses bracket notation for arrays (e.g., $.store.books[0].title). Dot notation uses plain dots and treats array indices as regular keys (e.g., store.books.0.title). JSONPath is more expressive and supports wildcards ([*]), deep scans (..), and filters, while dot notation is simpler and commonly used in JavaScript.

No. This tool runs entirely in your browser using JavaScript. Your JSON data never leaves your computer and is not transmitted to any server. Everything — parsing, formatting, validation, tree rendering, and path finding — happens locally. This makes it safe to use with sensitive or proprietary data.

The tool can handle JSON files up to several megabytes, depending on your browser's memory. For typical API responses and configuration files (under 1MB), everything works instantly. For very large files, the tree view may take a moment to render, but formatting and validation remain fast. If you're working with extremely large files (10MB+), consider using a desktop tool or splitting the data.

Yes! Click the Format button to pretty-print your JSON with proper indentation (2 or 4 spaces). Use Minify to compress it to a single line. The Validate button checks your JSON syntax and shows the exact position of any errors, making it easy to fix malformed data.

Switch to the Search tab on the right panel and type any key name or value you're looking for. The tool will search through the entire JSON structure and list all matching paths. Click any result to select it and see its full JSONPath and dot notation.

This tool supports standard JSON (RFC 8259). Objects, arrays, strings, numbers, booleans, and null values are all supported. Note that JSON5 extensions (comments, trailing commas, single quotes) are not supported — the JSON must be valid per the standard specification.

Track Your Marketing Data with Confidence

PixelFly provides server-side tracking that ensures your conversion data is accurately captured, even when ad blockers are active.

Start Free Trial Explore More Tools

No credit card required. 14-day free trial.