Comparing config, not whitespace
YAML lets you write the same data many ways: image: {tag: "1.9"} on one line or a nested block, keys in any order, comments anywhere. A text diff sees all of those as changes. This tool parses both files and compares the resulting data, so a reformatted file with no real change comes back as Equivalent.
Watch the Type changed rows: YAML guesses types, so FEATURE: false is a boolean but FEATURE: "false" is a string, and old YAML 1.1 parsers read no as false. A type change is often the bug you're looking for.
Need to see the files as text too? Open "Show as a line-by-line diff" under the results, or use the code compare for a raw view that keeps comments.
Questions
Does YAML compare ignore comments and formatting?
Yes. Both sides are parsed into data first, so comments, quoting style, indentation width, flow vs block style and key order do not count as differences. Only the values do.
Can it compare Kubernetes manifests, docker-compose or GitHub Actions files?
Yes. Any single-document YAML file works. For files with several documents separated by ---, compare them one document at a time or use the text compare.
Are anchors and aliases supported?
Yes. Anchors (&name) and aliases (*name) are resolved while parsing, so the comparison sees the expanded values.
Is my YAML uploaded?
No. It is parsed in your browser with the open-source js-yaml library.