YAML Parser

Parse YAML and inspect the resulting data.

Tree view
The tree appears here. Paste JSON or click Sample.

YAML Parser Online – See the Parsed Data Tree

The YAML parser loads a YAML document the same way a program would and shows the result as an interactive, collapsible tree. It answers the question that matters most when YAML behaves unexpectedly: what data does this file really contain? Indentation, implicit typing, and anchors make it easy to write YAML that looks right but parses into something else — the tree makes those surprises visible.

How to use it

Paste YAML into the editor, open a .yaml file, or press Sample. The tree appears instantly. Expand and collapse nodes, copy a value, or check the type badge of each entry: strings, numbers, booleans, nulls, mappings (objects), and sequences (arrays) are all shown distinctly. If the text cannot be parsed, the error message points to the line and column.

Things the tree reveals

  • Implicit types – port: 8080 is a number, version: "1.10" is a string, but version: 1.10 becomes the number 1.1. Seeing the parsed type helps avoid classic version-number bugs.
  • Indentation mistakes – a list item indented one level too deep ends up inside the previous item instead of beside it.
  • Null values – an empty value after a colon, ~, or null all become null.
  • Anchors and aliases – shared blocks referenced with *alias are expanded in place. YAML 1.1 merge keys (<<: *defaults) are applied as well, so the tree shows exactly what tools like Docker Compose see after merging.
  • Dates – timestamps like 2026-09-30 are kept as text so the value is shown exactly as written.

Multi-document files

Kubernetes bundles and Helm output often contain many resources separated by ---. The parser reads all of them and returns an array, one element per document.

Private and fast

Parsing is done locally in your browser with a standards-compliant YAML library. Your configuration is never uploaded.

To check syntax and reformat a file, use the YAML Validator. To get the parsed data as text, convert it with YAML to JSON or YAML to XML. For JSON input, the JSON Viewer offers the same tree.

Frequently Asked Questions

The parser uses the YAML 1.2 core schema. That means yes/no/on/off stay strings (only true and false are booleans), and numbers with leading zeros are not read as octal — the behaviour most modern tools such as Kubernetes expect.

Aliases (*name) are resolved to the value of their anchor (&name), so the tree shows the shared block wherever it is referenced. Merge keys (<<: *defaults), used a lot in Docker Compose and CI files, are applied too: the referenced mapping's keys are copied into the current mapping, and keys written explicitly next to the merge win.

If the input contains several documents separated by ---, the tree root becomes an array with one entry per document, in the order they appear in the file.