A fast check for one common YAML mistake

The YAML Validator on this page is a compact spacing linter. Its job is specific: while you edit configuration text, it looks for a line containing a colon that does not use a space after that colon and is not a key ending in :. When it finds one, the status panel reports the first affected line. With no such line, it displays Valid YAML syntax; an all-whitespace editor displays Empty input.

That narrow definition is worth stating plainly. This is not a full YAML 1.1 or YAML 1.2 parser, despite the familiar “online YAML validator” label. It does not evaluate indentation, flow collections, document markers, quoted scalar rules, anchors, aliases, tags, directives, duplicate keys, or schema types. The status is best interpreted as “no colon-spacing warning detected by this linter,” not as certification that a deployment system will load the file.

Try the check with a realistic config

The editor starts with a valid-looking server example. Replace it with:

server:
  host:localhost
  port: 8080
  tags:
    - web

The linter reports:

Syntax Warning: Line 2 key-value lacks spacing after colon. Expected ": "

Changing host:localhost to host: localhost clears that warning. The check runs whenever the text changes, so there is no Validate button and no output document to copy. The page consists of the editable YAML Config Code area and the read-only Syntax Linter Status message beneath it.

Why colon spacing deserves attention

Block mappings conventionally separate a key from its value with a colon followed by whitespace:

region: eu-west-1
replicas: 3
enabled: true

Without the separating space, text may be interpreted as a plain scalar rather than the mapping developers intended. In configuration work, that can turn an apparent key: value pair into data with a different shape. A tiny visual omission is especially easy to miss in environment maps, CI jobs, and copied snippets.

The linter’s rule is mechanical. Any line containing : is examined. It is accepted if it contains the exact substring : or ends with :. Consequently, it can warn on valid or intentional text where a colon appears inside another construct. It can also accept malformed YAML as long as the spacing pattern passes.

Read the status as a signal, not a verdict

Three status outcomes are possible:

Status	What it establishes	What it does not establish
`Empty input`	The editor has no non-whitespace characters	Nothing about YAML
`Syntax Warning: Line N...`	The first colon-bearing line lacks `:` and does not end in `:`	That adding a space will make the full document valid
`Valid YAML syntax`	No line triggered this spacing rule	Conformance with a YAML specification or application schema

The scan stops at the first warning. After repairing that line, a later warning may appear. This one-at-a-time behavior is useful for a short snippet but should not be mistaken for a complete diagnostics list.

Cases that reveal the boundary

A URL can trigger a warning

https://example.com/path

The line contains a colon, has no : sequence, and does not end in a colon. The tool therefore warns even though the text may be intended as a scalar. Quoting it does not change this linter’s text scan.

Broken nesting can pass

service:
    name: api
  port: 8080

Every mapping delimiter has a following space, so the tool returns its success message. A YAML parser should be used to assess the inconsistent indentation.

An unclosed flow collection can pass

ports: [80, 443

Colon spacing is present, but the bracket is not closed. The linter has no flow-collection parser and will not identify that problem.

A duplicate key can pass

timeout: 10
timeout: 30

Both lines satisfy the spacing rule. Duplicate-key handling varies by parser and policy; this page does not detect it.

A sensible two-stage workflow

Use this free online YAML validator as an early typo check, then use authoritative tooling for the real decision.

Paste the small configuration fragment into YAML Config Code.
Repair the first reported colon-spacing line.
Continue until the status no longer shows a warning.
Inspect URLs, timestamps, namespaced strings, and quoted text that may have produced false positives.
Run the document through the same YAML library and version used in production.
Apply a domain schema where one exists, such as Kubernetes OpenAPI validation, a CI platform validator, or an application configuration model.
Test behavior in a nonproduction environment when configuration semantics carry operational risk.

This division keeps the browser check useful without asking it to make promises it cannot support. It catches an easy typo immediately; your parser checks YAML syntax; your schema checks shape and types; the application checks meaning.

Where this lightweight YAML syntax checker fits

It is effective during a code review when a mapping line simply looks cramped, in a support conversation where someone pasted port:8080, or while drafting a short settings block without an editor extension. Because the status updates directly from the local text state, the feedback feels immediate and requires no command-line setup.

It is not the right final gate for Ansible playbooks, Docker Compose files, GitHub Actions workflows, Helm values, OpenAPI documents, or Kubernetes manifests. Those ecosystems impose rules beyond YAML grammar, and many support custom tags, templates, or schema constraints. Their native linters can identify unknown fields, invalid enum values, duplicate identifiers, and context-sensitive mistakes this generic spacing scan cannot see.

YAML terminology that helps during diagnosis

A mapping associates keys with values. A sequence is an ordered collection, commonly written with block - indicators. A scalar is a single value such as text, a number, or a boolean. Block style uses indentation; flow style uses brackets or braces. Anchors (&name) and aliases (*name) let nodes be referenced, while tags can direct type resolution.

The spacing rule on this page only approximates one visual convention around a block mapping value indicator. It has no model of nodes or collections. Knowing that vocabulary makes it easier to choose the next diagnostic tool: a parser for syntax and composition, then a schema validator for the expected document model.

Triage notes for common failures

If the status cites a normal mapping, insert one space after the delimiter and recheck.
If it cites a URL or another scalar containing :, treat it as a limitation of the scan rather than blindly editing data.
If the status says valid but your application fails, preserve the application error and check indentation, collection closure, quoting, tags, and duplicate keys with a parser.
If a template file contains expressions, validate the rendered YAML as well as the template source.
If different tools disagree, confirm whether they use YAML 1.1 or YAML 1.2 and which schema or duplicate-key policy is active.

FAQ

Does this page parse YAML?

No. It splits the input into lines and checks colon-spacing conditions. It does not build YAML nodes or invoke a YAML parser.

Why does a web address produce a warning?

The check does not distinguish a mapping delimiter from a colon inside a scalar. A URL without a colon-space pair matches the warning condition.

Does “Valid YAML syntax” mean my Kubernetes manifest is valid?

No. It only means the spacing check found no warning. Kubernetes validation additionally requires actual YAML parsing and resource-schema checks.

Will it show every spacing problem at once?

No. Scanning stops at the first line that triggers the rule. Fixing it allows the next matching line, if any, to surface.

Does it check tabs or indentation depth?

No. Use a YAML parser, linter, or the separate formatter’s limited indentation checks for those concerns.

Is there a Copy or Download action?

No. This component edits the YAML in place and displays a status message. It does not generate a second document.

Which YAML standard does it enforce?

It does not enforce YAML 1.1 or YAML 1.2. The rule is a small textual convention that is useful before standards-aware validation.

YAML Validator