Skip to content

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

Try

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.

    Explore deploymentsDownload for MacDownload for Windows

    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.

    Common YAML errors, their causes and fixes
    ProblemFixCause
    Tab used for indentationIndent with spaces only; 2 is the usual step.A tab where YAML expects spaces
    Indentation errorLine up keys and list items that belong together.A line is not aligned with its siblings
    Duplicate keyRename or remove one of them.The same key twice in one map
    No space after the colonWrite key: value.key:value is read as one string
    Value needs quotesWrap the value in quotes.A value starts with @, `, % or a similar character
    Reads differently in YAML 1.1Quote text, or write true, false and plain numbers.no, on, 0755 and 22:22 change meaning in older parsers
    Not a string in KubernetesQuote 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 specification

    Common questions

    YAML,
    explained.

    Keep exploring

    Tools and guides for your next step.

    Your privacy preferences. We use product analytics to improve CtrlOps. Google Analytics cookies and live chat stay off until you allow them. Cookie policy