JSONPath / JMESPath Tester
Paste JSON and test JSONPath ($..) or local JMESPath path expressions (orders[*].id). Use "Open in JSON
Formatter" to continue your workflow.
- Paste JSON and run JSONPath queries.
- Extract nested fields and debug paths.
- Great for API payload inspection.
- Share results: Generate a secure link to share your current input and results with teammates — nothing is uploaded to any server.
Input JSON
Matched results
Tree Explorer
Generated Paths
Examples & Recipes
Filter Builder
Filter syntax portability varies. JSONPath filters are [?(@.field == 'value')]; JMESPath uses [?field=='value'] with backticks for numeric/boolean literals.
Empty-result Debugger
Code Snippets
Snippets reflect the current expression and mode. Install the relevant package (jsonpath-plus, jmespath, jsonpath-ng) before running.
Recent Expressions
Dialect & Compatibility
Platform Notes
- Standard JSONPath is now defined by RFC 9535, but many tools still use older or custom variants.
- This page uses local jsonpath-plus-style behavior for JSONPath. Expressions may need adjustment in kubectl.
- JMESPath is common in AWS CLI-style queries. JSONPath expressions do not work in JMESPath-only tools.
- Use JSON Pointer when you need an exact location for JSON Patch operations.
JSONPath vs JMESPath Comparison
| Simple field extraction | Either JSONPath or JMESPath |
|---|---|
| Recursive search | JSONPath |
| Reshaping/selecting fields | JMESPath when supported |
| AWS CLI-style queries | JMESPath |
| JSON Pointer/path extraction | JSONPath result metadata |
| Kubernetes/kubectl examples | JSONPath, with kubectl compatibility caveats |