All tools

YAML Validator & Linter

Data

Validate YAML syntax with detailed errors, find duplicate keys that most parsers silently accept, and expand anchors, aliases and merge keys

Was this tool helpful?
yamlvalidatelintsyntaxduplicate-keysanchorsaliasesmerge-keyskubernetes

About YAML Validator & Linter

Paste a Kubernetes manifest, GitHub Actions workflow or any other YAML file and check it three ways. Validate confirms that it parses, with errors that pinpoint an indentation mistake or invalid character, and a stats panel of key counts and nesting depth. Duplicate keys lists every mapping key repeated within the same scope, with line and column, which matters because most YAML parsers silently keep the last value instead of failing. Anchors & aliases expands every anchor, alias and merge key (<<) inline so you can see the document a parser actually receives, and lists anchors that are defined but never used. All three check YAML structure, not a specific tool's schema: a Kubernetes manifest missing a required field still passes and needs kubectl apply --dry-run. Nothing is sent to a server.

How to use YAML Validator & Linter

  • 1.Paste a YAML file (like a Kubernetes manifest or GitHub Actions workflow) to check it parses correctly before committing it.
  • 2.Use the detailed error messages to pinpoint an indentation mistake or invalid character that a generic parser error wouldn't explain clearly.
  • 3.Check the stats panel to see key counts and nesting depth as a quick sanity check on a large config file's structure.
  • 4.Switch to Duplicate keys before merging a large config: a repeated key usually means one of the two values is silently ignored.
  • 5.Use Anchors & aliases to expand <<: *defaults style merges and confirm what each section really contains.

Frequently asked questions

Is my YAML sent to a server?
No, validation runs entirely in your browser using a JavaScript YAML parser.
Does it support YAML anchors and aliases?
Yes, standard YAML 1.1/1.2 features including anchors (`&`), aliases (`*`), and merge keys are parsed correctly.
Will it catch schema errors, like a Kubernetes manifest missing a required field?
No β€” this validates YAML syntax only, not schema correctness for a specific tool's format. Use a tool-specific validator (e.g. `kubectl apply --dry-run`) for schema-level checks.
Why does my YAML fail here but work in my app?
Different YAML parsers (Python's PyYAML, Ruby's Psych, JS libraries) have minor differences in edge-case handling β€” if this tool flags an error your app doesn't, double-check which parser your app actually uses.
Why check for duplicate keys if the YAML parses?
The YAML spec forbids duplicate keys, but many parsers accept them and keep the last value, so a repeated key in a long file silently overrides the first one. The Duplicate keys mode finds them with line and column.
Why did an old Utilix tool page redirect me here?
Utilix merged several single-purpose tools into the YAML Validator & Linter. Each old URL now opens this page with its mode preselected (via ?mode=<old-tool-slug>), so bookmarks and links keep working. The old tools' REST endpoints, Node.js and Python SDK functions, and MCP tools are unchanged.