Inspect a configuration or data file
- Choose a .yaml or .yml file, or paste its content.
- Expand the tree to follow keys, lists and scalar values.
- If the file contains several documents, select one with the Document menu.
- Use Table and Collection to compare a list of records.
service: example
owners:
- name: Alex
active: true
---
environment: test
The --- separator introduces another document. In the first document, owners is a sequence of mappings. The second has its own environment value. Choosing documents separately avoids confusing their fields.
A readable preview, without running the configuration
Opening a deployment configuration here does not deploy anything. Your browser parses the data for inspection. QuickDataView does not evaluate application settings or check whether they are valid for Kubernetes, Docker Compose or another system. Use that system’s validation tools before applying changes.
Indentation and aliases
YAML syntax errors include parser location information. Check indentation, quotes and separators near the reported position. Cyclic aliases, excessive alias expansion and unsupported tags are rejected; duplicate mapping keys are rejected too. The preview is intentionally bounded.
For a secret-containing configuration, local inspection means its content is not uploaded here. If you later share an excerpt elsewhere, that is a separate decision. Compare the XML and JSON views when an export uses a different format.
Credit to the format’s makers
Clark Evans, Oren Ben-Kiki and Ingy döt Net helped design YAML around readable data. The YAML language community continues that work. Its mappings and lists are a thoughtful way to make configuration understandable.
Format reference: YAML specification and history. Reference checked 7 October 2026. These links acknowledge the format; they do not imply endorsement or a partnership.