Runs entirely in your browser — nothing leaves this page.
YAML diff
Structural diff for YAML and JSON documents — compares parsed values, ignores formatting and key order.
Comparing two documents structurally
Both sides are parsed first, then compared by key and index — so reordered keys, different indentation, quoting changes and comments never show up as differences. Only actual value changes do.
This is what you want when comparing a rendered Helm output against what is live, or two environment overlays that a text diff turns into noise.
How is this different from git diff?
A text diff reports every reformatting. This one reports only what a parser would see differently. A file where someone reordered keys and reflowed a list shows as identical here — and behaves identically in the cluster, which is the question being asked.
What do the paths in the output mean?
They are the location of the change in the parsed document: spec.template.spec.containers[0].image points at the first container's image. That is the address you edit, which is usually faster than counting lines.
Are anchors and aliases handled?
They are resolved during parsing, so the comparison sees the expanded values. Two documents that reach the same result — one using an anchor, one written out — compare as equal, which is correct.
Related tools: YAML / JSON / TOML, K8s manifest validator and Regex tester.