YAML Tools

Catch the indentation error before the cluster does

YAML runs the modern deployment stack — Kubernetes manifests, GitHub Actions, docker-compose, Ansible playbooks, OpenAPI specs — and its whitespace-significant syntax makes it uniquely easy to break invisibly. A tab instead of spaces, a value swallowed by the wrong indent level, an unquoted string that parses as a boolean: the YAML Validator catches all of these with the exact line and column, before CI or a cluster rollout does it the expensive way. To see the exact data structure your YAML becomes rather than just a pass/fail verdict, the online YAML parser shows the parsed result directly. For a docker-compose.yml specifically, syntax-valid YAML can still be an invalid Compose file — the Docker Compose Validator adds a real check against the Compose Specification schema plus cross-reference checks (undeclared volumes, networks and depends_on targets) the YAML Validator alone can't catch.

The Formatter re-serializes documents at a consistent indent (resolving anchors and aliases in the process), the Viewer renders the parsed structure as a collapsible tree so you can verify what the parser actually understood, and the Parser shows the resulting data model directly. Norway-problem classics — `country: NO` becoming `false` — are immediately visible in the tree view.

YAML in, anything out

Configuration rarely stays in one format. Convert YAML to JSON for tooling that speaks only JSON, YAML to XML for legacy systems, or YAML to CSV when a values file needs to land in a spreadsheet. The reverse direction — JSON to YAML — is the fastest way to turn an API response into a starting manifest. Each converter resolves anchors and merge keys first, so the output reflects the document's true meaning rather than its shorthand. Spring Boot teams get their own pair: YAML to Properties flattens application.yml into dotted .properties keys, and Properties to YAML rebuilds the nesting back, keeping your # comments in the process.