⭐ 0

YAML Config Example: Valid Application Settings

Check YAML-like lines for indentation, keys, duplicates, and quotes. This is not a full YAML 1.2 parser.

🔒 Processed entirely in your browser — nothing you enter here is ever uploaded.

The result appears on this page after you run the tool. Nothing you enter is uploaded.

Processing... 0%
Checking YAML spaces
Parsing mapping keys
Matching key-value rules
Validating indentation
Verifying structure

Result

About this tool

This page opens the YAML validator preloaded with a small, realistic configuration file: an application block with a version string and a debug flag, a database block with nested credentials, and a list of tags. It is checked the instant the page loads, and the pass result below is a real, computed check — not a canned screenshot.

The example is deliberately shaped like something you would actually commit: two-space indentation throughout, a quoted version string so it is not misread as a number, a nested mapping for credentials, and a block sequence for tags. It mirrors the structure used in countless real Kubernetes manifests, GitHub Actions workflows and application config files, so it is a useful sanity check for what "correctly formed" YAML looks like before you paste your own file in.

Replace the text in the box with your own configuration to validate it the same way. If your file uses tabs instead of spaces, mixes indentation widths, or repeats a key at the same nesting level, the validator will catch it and point at the exact line — the same class of mistake demonstrated on the indentation-error preset page.

Example. The line key: value is accepted. A second key: other at the same indent fails with Duplicate key detected. A leading tab fails with YAML does not allow tab characters for indentation.

Limit. This is a line scanner, not a YAML 1.2 parser. Anchors, aliases, tags, and flow collections are not implemented. A pass does not mean a Kubernetes or CI schema is satisfied.