Workflow YAML Validator

Validate Argo Workflows YAML online: syntax, entrypoints, template references, DAG cycles, parameters, CronWorkflow schedules and fields removed in v4.. Free, no sign-up, and everything runs privately in your browser.

How to use the YAML validator

  1. Paste your manifest, upload a .yaml file, or load a sample.
  2. Click Validate (or press Ctrl/⌘ + Enter). Multi-document files are supported.
  3. Fix errors first, then review warnings. Each message names the template, step or task involved.
  4. Copy or download the report to share it in a pull request.

Manifest

Results

    What gets checked

    Validation runs in three layers. First the YAML is parsed, and syntax errors are reported with line and column numbers plus hints for the two most common causes: tab characters and unquoted {{ values. Second, the resource header is checked: apiVersion, kind, and the naming rules that differ between Workflows (which may use generateName) and stored templates (which need a fixed name). Third, the workflow structure is analysed the way the controller would.

    • Entrypoint and onExit match real templates.
    • Every template has exactly one type and the fields that type requires.
    • Steps and tasks reference existing templates and pass required parameters.
    • Steps only reference outputs from earlier stages; DAG tasks only from tasks they depend on.
    • DAG dependencies exist and contain no cycles.
    • {{inputs.parameters.x}} references are declared.
    • CronWorkflow schedules parse, timezones are valid IANA names, and policies are allowed values.
    • Fields removed in version 4.0 — schedule, mutex, semaphore, podPriority — are flagged.

    Validator vs argo lint

    This tool is a fast, private first pass that needs no cluster or CLI. argo lint uses the controller’s own code and can resolve stored templates in your cluster, so run it in CI as the final gate.

    Frequently asked questions

    Does it validate templates referenced with templateRef?

    It checks that the reference is well-formed, but it cannot read templates stored in your cluster.

    Can I validate several documents at once?

    Yes. Separate documents with ---; each is validated and reported separately.

    Is my YAML stored?

    No. Everything runs in your browser; nothing is uploaded.

    More free tools