YAML Viewer — Explore Configuration Trees

How to use

Paste YAML into the editor, upload a .yaml or .yml file, or load the sample.
Wait for the tree, or press Process for input larger than 1 MB.
Open branches to inspect nested mappings and sequence items; search for a key or value.
Use Output only or Full screen for a wider view, then copy or download the complete formatted YAML.

Examples

Inspect a deployment setting

A mapping becomes a branch with a row for each setting.

Input

service:
  replicas: 3
  region: eu-west

Output

root → service → replicas: 3; region: eu-west

Review a list of hosts

Sequence items keep their order and receive numeric labels.

Input

hosts:
  - api.example.test
  - jobs.example.test

Output

root → hosts → 0: api.example.test; 1: jobs.example.test

Find the setting that matters

Configuration files often combine a few top-level sections with deeply nested details. A flat text search can find a word, but it does not show which service or environment owns that value. The YAML viewer keeps the document’s mapping and sequence structure visible. Open only the branch you need to compare a production setting with a staging setting, or expand the whole tree when you want an overview.

Each mapping key appears as a named row. Sequence items use their position, starting at zero. Scalar values appear beside their keys, so strings, numbers, booleans, and nulls are easy to distinguish. Search checks a row’s path as well as its visible value. For example, searching for replicas can locate the setting even if the same number appears elsewhere.

Working with parsed YAML

The viewer uses the JSON-compatible part of YAML. It accepts ordinary mappings, sequences, anchors, and aliases, but rejects custom tags, circular aliases, and non-finite numbers that do not convert safely. This keeps the tree consistent with the site’s YAML converters. A YAML stream containing multiple documents should be split into one document per input.

Comments are useful in source files, but they are not part of the parsed data tree. The Copy and Download actions export newly formatted YAML from that data, so comments and the original quote style are not retained. Keep your source file if you need those details. For a large file, the tree renders rows around the current scroll position instead of adding every node to the page at once. Both panels scroll independently, and the full output remains available for copying or download.

Frequently asked questions

Does the tree change my YAML file?

The tree is a read-only view. Copy and Download provide a newly formatted version of the parsed data, which may omit comments and expand aliases.

Can I search inside nested values?

Yes. Search checks paths, key names, and scalar values in the parsed tree.

How does it handle large documents?

The tree renders only nearby rows while you scroll. Inputs above 1 MB wait for you to press Process so editing stays responsive.

Are custom YAML tags supported?

No. The viewer accepts JSON-compatible YAML values; custom tags and non-finite numbers are rejected.

Does my configuration leave the browser?

No. Parsing runs in a browser worker, and your input is not uploaded to a processing server.