Free YAML Validator & Linter with Kubernetes Checks
Find every error by line, check Kubernetes, Compose and CI files, and catch values that change meaning.
Free · No signupChecked in your browser
Valid Kubernetes manifest
No problems found.
2 documents · 38 keys · depth 8
Nothing you paste or upload leaves this page.
From a valid file to a running server
Deploy and manage it with CtrlOps.
Edit config files on your servers and deploy apps from GitHub, all from one desktop workspace.
Keep it handy
Common errors,
and their fixes.
Most broken YAML fails for one of these reasons. The validator names each one and points to its line.
| Problem | Fix | Cause |
|---|---|---|
| Tab used for indentation | Indent with spaces only; 2 is the usual step. | A tab where YAML expects spaces |
| Indentation error | Line up keys and list items that belong together. | A line is not aligned with its siblings |
| Duplicate key | Rename or remove one of them. | The same key twice in one map |
| No space after the colon | Write key: value. | key:value is read as one string |
| Value needs quotes | Wrap the value in quotes. | A value starts with @, `, % or a similar character |
| Reads differently in YAML 1.1 | Quote text, or write true, false and plain numbers. | no, on, 0755 and 22:22 change meaning in older parsers |
| Not a string in Kubernetes | Quote it, as in value: "8080". | A label, annotation or env value is a number or boolean |
How the checks work
Syntax first.
Then meaning.
Every syntax error, with its line
A full YAML parser reads the text, not a set of patterns, and reports every problem it finds: tabs used for indentation, misaligned keys, unclosed brackets, duplicate keys and aliases with no anchor. Each one shows its line and column, and selecting it moves the cursor there.
Checks for the file you actually have
Once a document parses, the validator recognises Kubernetes manifests, Docker Compose files, GitHub Actions workflows and Ansible playbooks, and checks what those tools require: a selector that matches its pods, services that exist, jobs that are defined, plays with hosts. These are quick sanity checks; your cluster or CI still has the final word.
Values that change meaning between versions
YAML 1.2 reads no as text and 0755 as 755. YAML 1.1 parsers, still used by PyYAML and Ansible, read them as false and the octal 493, and turn 22:22 into 1342 and 2024-01-01 into a date. The validator flags each value that would change, so you can quote it once and get the same result everywhere.
Format without losing your notes
Format re-indents with 2 or 4 spaces and tidies spacing inside brackets and around colons, but keeps comments, anchors, merge keys and block text exactly as written. Copy the result, or copy it as JSON.
Read the YAML 1.2 specificationCommon questions
YAML,
explained.
Paste your YAML into the left pane. Validation runs live as you type - the right panel shows a green Valid or red Invalid verdict, the exact line and column of any error, and lint suggestions. There is no button to press and nothing is uploaded.
The most common causes are a tab used for indentation, inconsistent indentation between sibling keys, a missing space after a colon, a duplicate key, or a special character that needs quotes. The validator shows the exact line and column and highlights the offending line so you can fix it fast.
No. YAML forbids tab characters for indentation - you must use spaces. A single tab in the indentation will make the document fail to parse. This tool flags tab-indented lines specifically so you can spot and replace them.
A validator answers a yes/no question: does this parse as valid YAML? A linter goes further and flags style and quality issues that are technically valid but usually mistakes, like trailing whitespace, Windows line endings, or values that read differently in YAML 1.1 and 1.2. This tool does both at once.
Yes. After the syntax check passes, the tool auto-detects the document type and runs required-field checks: Kubernetes manifests need apiVersion, kind, and metadata; Compose services need image or build; workflow jobs need runs-on and steps; Ansible plays need hosts and list-shaped tasks. Files that pass show a type-aware verdict like "Valid Kubernetes Manifest".
Paste the manifest and the validator auto-detects it as Kubernetes (via apiVersion and kind), checks the whole multi-document stream, and verifies required fields: apiVersion, kind, metadata with a name, and for Deployments spec.selector and spec.template. Missing fields are reported with a corrected YAML example. It is a required-field check, not a full OpenAPI schema validation.
No. The same key appearing twice in one mapping is rejected as invalid, because it is ambiguous which value wins. This validator treats a duplicate key as a hard error and points you at the line so you can rename or remove it.
Yes. Documents separated by --- are all parsed as a single stream. The result panel reports the document count, and any error is pinned to the correct line across the whole file, so you never have to split it apart to debug.
Yes. Validation runs entirely client-side with no uploads or network calls, which you can verify in the browser network tab, and it works offline. Your YAML never leaves your machine, so it is safe for manifests, .env files, and secrets.
Yes. When your YAML has no syntax errors, the Format button reformats it with clean, consistent indentation (2 or 4 spaces) while preserving comments. Then copy it to your clipboard or download it as config.yaml. Formatting only runs on syntactically valid input, so fix parsing errors first; formatting does not fix application-specific field errors.
Keep exploring
Tools and guides for your next step.