Runs locally in your browser. Nothing you enter is uploaded to our servers.
Result will appear here
Tips for validating YAML
Indentation is significant — use spaces consistently.
Quote values that look like numbers, booleans, or nulls when needed.
Tabs often break YAML parsers.
Validate the document your runtime will actually load.
Be careful with anchors/aliases if your consumer does not support them.
YAML that actually parses
Processing stays in your browser — your input is not uploaded to our servers.
YAML is indentation-sensitive and has more implicit types than JSON. This page tells you whether the document parses, not whether your Kubernetes keys are named right.
Tabs versus spaces and accidental `yes`/`no` booleans are the usual foot-guns.
Validate YAML
Paste the document
Keep original indentation. Do not mix tabs and spaces.
Run the parse check
A failure points at the first syntax problem, not at missing app-level keys.
Quote values if needed
Country codes, versions, and the words on/off often need quotes to stay strings.
YAML validator FAQ
Is YAML a superset of JSON?
Many YAML parsers accept JSON, but the reverse is not true. Invalid YAML will still fail here.
Does this lint Kubernetes manifests?
Only YAML syntax. Resource schemas are a different check.
Is the document uploaded?
No. Parsing stays in the browser.