Check YAML and find the line and column of an error: tabs, duplicate keys, open brackets, missing anchors
Paste YAML to check it. Valid YAML is confirmed with its documents and lines; YAML that isn’t valid shows where it breaks and why, and values some parsers read differently are pointed out.
How to use it
Paste the YAML you want to check, or open a .yaml or .yml file. The status bar says Valid YAML, or Not valid YAML with the line and column of the first problem. Notes under the result name the lines with values YAML 1.1 parsers read differently. Under Options, Resolve aliases writes each *name out as a copy and applies merge keys; Clean characters removes invisible characters and odd spaces. Fix the text and the check runs again as you type.
Examples
A tab used to indent
spec: replicas: 3
Line 2, column 1Tabs are not allowed as indentation
YAML indents with spaces only. An editor that inserts tabs breaks the file without showing it.
NO is not always text
countries: - GB - NO
Line 3: NO is read as false by YAML 1.1 parsers (PyYAML, go-yaml v2). Quote it if it is text.
The file is valid, and NO is Norway here. The note says where a YAML 1.1 parser would read something else.
What it checks
Values YAML 1.1 parsers read differently
Safe with untrusted YAML
Resolve aliases and clean characters
Questions
- Does it show every error at once?
It shows the first one, with its line and column, because one mistake (a wrong indent, an open bracket) often makes the lines after it look wrong too. Fix it and the check runs again. - Can it expand anchors and merge keys?
Yes: turn on Resolve aliases under Options. Each *name becomes a copy, <<: merge keys become the keys they bring (keys written in the map win), and the anchors go. Comments stay. - Can it check a Kubernetes manifest or a GitHub Actions workflow?
It checks that the file is valid YAML, including a manifest with several documents. It does not check that the fields are the ones Kubernetes or GitHub expect. - Is my YAML uploaded?
No. Everything runs in your browser, so your YAML stays on your device. Nothing you paste is uploaded unless you share a result, which is locked with your password first. Config files, Compose files and CI workflows often hold passwords, tokens or keys, and the page warns you if it spots any.