Filter nested JSONPath items
Choose the JSON document source, write an outer-item existence query, and verify match paths and complete exported values.
Run JSONPath query
Filter nested JSON with a fixed RFC 9535 profile and export complete matched values with original locations.
| Delivery | Check |
|---|---|
| Matched values | The selected level, original value text and result order |
| Matched locations | Every path, including intentional repeated selections |
| No matches | A complete empty array, distinct from a refused request |
| Query report | The query and source identity used for this run |
Choose supported inputs deliberately
The current limits, controls and supported profile are listed in the tool reference on this page. A syntactically valid input can still be refused for profile, source-path work or complete-output capacity.
The selected file is read only after you click Run. Reading, checks and processing share one 10-second task period.
Each role uses its selected mode only. Empty or invalid active files never fall back to pasted text.
Recover and save
Correct query grammar or reduce output/parse work. Do not substitute a non-singular wildcard query into a comparison; use an existence filter for the nested array.
Keep complete evidence
This is a bounded preview. Full diagnostics, matches and source data remain in the complete copy and downloads.
Match order and repeated selections are preserved. Matched values retain original number tokens and internal whitespace.
Copy the entire value array and download the report to keep every matched path and source hash.
- Confirm that matches are outer records when that is the intended delivery.
- Inspect every path and retain the order and multiplicity of repeated selections.
- Save the full value array and query report; the short preview is only for navigation.
Recover without switching sources silently
Correct query grammar or reduce output/parse work. Do not substitute a non-singular wildcard query into a comparison; use an existence filter for the nested array. After cancellation, rerun the unchanged active sources in a fresh request. Refused inputs and timed-out requests do not yield partial artifacts.
Cancelled or timed-out work produces no complete artifact. The next run uses the same active roles unless you deliberately edit or change them.
References
- Nested JSONPath selection question and author feedback
The complete document is retained. The original non-singular comparison is refused; this separate nested-existence query returns the complete first outer record, unlike the answer’s inner-identifier selection.
- RFC 9535 JSONPath
Background specification; this fixed profile excludes functions and uses exact safe integral numeric values.
Tools in this category
Expand a tool to see its steps, options and supported formats, then open its workspace.
Query local JSON with JSONPathFilter nested JSON with a fixed RFC 9535 profile and export complete matched values with original locations.
Filter nested JSON with a fixed RFC 9535 profile and export complete matched values with original locations.
Steps
- Provide the local JSON and the query separately.
- Choose the active source mode for each role. File selection shows metadata only; click Run to read and process.
- For a nested identifiers array, filter the outer item using an existence test on its nested filter.
- Inspect all matched locations, then copy or download the complete value array and query report.
Capabilities and limits
- One JSON document up to 1 MiB, 50,000 value nodes and depth 64. Query up to 4,096 UTF-8 bytes, 128 root segments and 32 cumulative parser calls. Cumulative retained source JSON Pointer paths allow 8 MiB; object/array reads, membership and key/descriptor visits allow 100,000 operations, including eager nested-filter lists.
- Supports members, indices, slices, wildcards, descendants, nested existence filters and basic logical/comparison operators. Function calls and JavaScript expressions are refused. All numeric document and query literals must have exact safe integral values.
- At most 10,000 matches; duplicate selections stay duplicated and ordered. query-report.json and matches.json together allow 8 MiB. No-match produces an empty array.
- Matched valueJSON retains its original JSON spelling and whitespace. Paths include RFC normalized locations and JSON Pointer. The user’s original query is retained without reformatting.
- The document role uses either its pasted value or exactly one selected UTF-8 file; clear the selected file to paste. An empty or invalid active file never falls back to hidden pasted text. A filename label allows 512 UTF-8 bytes.
- One leading BOM is removed and recorded, including pasted input. Invalid UTF-8, decoded duplicate JSON keys and unpaired Unicode surrogates are refused. Inputs stay in this browser.
- A fixed 10-second whole-task deadline or cancellation returns no partial export. Rerun after correcting the input; a fresh Worker starts each job.
- The query is a separate text control. Functions including count/length/match/search/value, JavaScript expressions and non-singular comparisons are refused; this is not full RFC 9535 conformance. The original query is not replaced by a normalized expression.
- File contents are read only after Run, within the same fixed 10-second period as engine loading, checks and processing. Cancelling or exceeding any limit publishes no partial copy or download. Only the current tab holds the inputs in bounded memory.
- The screen uses a bounded preview. Copy preserves the complete ordered value array; query-report.json preserves every matched location and the source identity. No content upload or remote reference fetch.