How to use JSONPath & JMESPath Query Workbench
Query JSON using JMESPath or a non-evaluating JSONPath implementation with explicit supported syntax.
What to provide
Choose JMESPath or JSONPath. JSONPath supports root, child names, array indices, wildcards, recursive names, slices, and unions—never script expressions or evaluated filters.
Paste the JSON document that the query should inspect.
- Paste, type, or drag and drop a supported text file into the input area.
- Place the second value in the adjacent panel. Sensitive fields are masked by default.
- Choose the options that match your intended result.
- Select “Run tool” or press Ctrl/Command + Enter, then copy, download, or move the result back into the first input for another pass.
Use “Swap inputs” to reverse the comparison without copying either value.
What the result means
The inert JSON result and result cardinality.
Privacy and safety
This utility is loaded as browser code and processes your input only in this tab. OmniCastConverter has no upload endpoint and never stores your content, filenames, tokens, or secrets. Generated markup and code are shown as inert text and are never executed.
Limitations
- JSONPath filters and scripts are deliberately unsupported because they require expression evaluation. JMESPath functions operate on data only and cannot access browser globals.
Try the included example
Select “Load example” at any time to restore this tested sample.
people[?active].name{"people":[{"name":"Ada","active":true},{"name":"Lin","active":false},{"name":"Grace","active":true}]}