Evaluate JSONPath locally

Use a focused practical subset for common browsing/debugging jobs. Results include a readable JSONPath and an RFC 6901 JSON Pointer for exact locations.

JSON document

{"store":{"book":[{"title":"A","price":8.95},{"title":"B","price":12.5}],"open":true}}

JSONPath expression

—Matches

—Root

—Depth

—Input bytes

Supported: $, child properties, quoted bracket properties, array indexes, wildcards, and recursive descent. Not supported: filters, slices, unions, functions, or script expressions.

#	JSONPath	JSON Pointer	Value

Local developer workflow

This v10.72 layer keeps high-frequency developer jobs browser-local and connects focused tools without replacing their established engines. JSON, Base64, URL, UUID and JWT content is processed in the browser; YAML may use the existing optional parser library when available, with its documented local fallback.

Trust and standards boundaries

Formatting is not schema validation, Base64 is not encryption, URL normalization is not a privacy guarantee, UUID metadata is not provenance, and decoded JWT claims are not trusted until cryptographic and application-specific validation succeeds. RS256 tools accept explicit PEM key formats and do not fetch issuer keys or make authorization decisions.

How to use this JSONPath Tester

Evaluate a practical JSONPath subset locally with matched values, readable paths, RFC 6901 pointers, result limits, and explicit unsupported syntax.

Enter, paste, upload, or choose the inputs shown in the tool above.
Adjust the available options for the result you need.
Review the output before copying, downloading, or using it elsewhere.

What this tool does

Test child, index, wildcard, and recursive-descent JSONPath expressions against pasted JSON without uploading the document.

Practical tips and limits

Validate syntax before using transformed data in production, and keep a source copy when sorting or minifying large payloads.