YAMLPath & JMESPath Tester
About YAMLPath / JMESPath Tester
YAMLPath / JMESPath Tester parses YAML 1.2 once and runs expressive selections over the resolved data, with JSON or YAML result rendering.
How it works
Two query languages
JMESPath supports filters, projections, pipes and functions. YAMLPath mode uses familiar JSONPath syntax over YAML data, including child, wildcard, recursive and filter selectors.
YAML-native input
Anchors and aliases are resolved under a safety limit and multi-document streams become a top-level array. No manual JSON conversion is required.
Flexible result format
Return query results as pretty JSON for application code or YAML for configuration workflows. Missing JMESPath results are represented explicitly as null.
Frequently asked questions
Is YAMLPath a formal standard?
No single YAMLPath standard exists. This mode deliberately uses JSONPath syntax over the resolved YAML value and is labeled accordingly.
Does JMESPath modify the source?
No. Expressions transform the in-memory result only; the YAML input remains unchanged.
Can I query a YAML document stream?
Yes. Multiple documents are exposed as an array, so expressions can select across document indexes.
Sources & last verified
The behaviour of this tool and the claims on this page were checked against the specifications below on . Everything runs in your browser, so the output you see is exactly what the engine produced.
Found a wrong result or an outdated claim? Report an error and it will be re-verified.