List every path in a YAML document with its line number and resolved type, read a value out by path, and see which keys came in through a merge.
Waiting for YAML
Every path in the document, with the line it is written on.
The paths appear here
Every path with its line, its resolved type and a preview of its value.
A key marked merged came in through a <<: merge key, so it is real to a parser but is not written on the line shown — the line is where the merge happened, not where the key is defined. Types are the ones a YAML 1.2 parser resolves; a 1.1 parser would read some of them differently, and the formatter flags those.
YAML Path Explorer runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
A Kubernetes manifest or a CI workflow is deep enough that an error message naming `spec.template.spec.containers[0].resources.limits` tells you what is wrong and not where to go and fix it. Having the path and the line together means you can jump straight there.
Merge keys are marked, and that matters more than it sounds. A `<<:` merge brings keys in from an anchor, and those keys are real to a parser but are not written anywhere near the place they appear. An explorer showing them identically to written keys would send you looking at a line that does not contain them.
The types shown are the resolved ones, which is where YAML's ambiguities become visible: `8080` is a number, `"8080"` is a string, and `yes` is a string under 1.2 and a boolean under 1.1. Reading a configuration file as paths-and-types is often the quickest way to notice that a value is not the type the program expects.
Only the first document is listed when a file contains several separated by `---`, which is how most single-document readers behave — and a Kubernetes manifest with several resources in one file is the usual case, so the count is shown.
It came in through a `<<:` merge key from an anchor elsewhere in the file. It is real to a parser but is not written on the line shown — the line is where the merge happened, not where the key is defined.
Dotted keys with bracketed indices: `spec.containers[0].image`. It is the form Kubernetes and most CI tools use in their error messages, which is the point.
Because a path is relative to a document, and most readers of a multi-document file handle one at a time. The count of documents is shown so you know there are others.
Because unquoted digits are a number in YAML. Whether that matters depends on the consumer — Compose wants port mappings quoted for a different reason, and a Kubernetes containerPort genuinely is an integer.
No. It is parsed in your browser, which matters for a manifest containing internal hostnames or a workflow naming your secrets.