Back to tools

YAML Compare

Diff two YAML files side-by-side. Normalize mode parses and sorts keys so you only see real changes. Good for Kubernetes manifests, Helm values, and CI workflows. Runs in your browser.

0 chars
0 chars
Granularity

Diff result

+0−0=0

Paste content on both sides to see the diff.

How It Works

  1. 1

    Paste both YAML files

    Original on the left, changed on the right.

  2. 2

    Toggle Normalize

    Sort keys and re-emit both sides so you only see real changes.

  3. 3

    Review the diff

    Additions in green, deletions in red. Stats update live.

  4. 4

    Copy or download

    Export the unified diff to share in a PR or apply as a patch.

Use Cases

  • Kubernetes manifest review

    Diff staging vs production manifests before promoting. Catch a missing replica or env var.

  • Helm values drift

    Compare values.yaml across environments to find where overrides have diverged.

  • CI workflow review

    Diff two versions of a GitHub Actions or GitLab CI workflow before merging.

  • Test fixture comparison

    Compare expected vs actual YAML output from a fixture-based test.

Frequently Asked Questions

It diffs two YAML documents side-by-side and highlights every added, removed, and changed line. Use it to spot config drift between two environments, review a Helm values change, or verify a Kubernetes manifest patch.
A YAML diff shows the structural difference between two YAML documents. A plain text diff would flag formatting changes (key order, indentation) as differences. This tool can optionally normalize both inputs first, parsing them, sorting keys, and re-emitting, so you only see real changes.
Two YAML files can be semantically identical but visually different (key order, anchors, quoting). Normalize parses both sides and re-emits them with sorted keys and consistent formatting, so you only see meaningful changes. Not noise from reformatting.
Yes. Anything valid YAML. For Kubernetes manifests with multiple documents (separated by `---`), each document is treated as part of the larger string and diffed in order.
No. Parsing and diffing happen entirely in your browser. Safe for production manifests, internal config, and secrets you do not want leaving your machine.
Normalize mode resolves anchors and aliases. Both sides are emitted as plain YAML without references, so two files that use anchors differently still diff cleanly.
Yes. Copy as a unified diff to your clipboard or download as a .patch file you can apply with `patch -p1` or `git apply`.
If Normalize is on and a side fails to parse, you will see the parser error. Turn Normalize off to run a plain text diff regardless.

Diffing manifests by hand? Stop. Automate the test instead.

Bug0 writes end-to-end tests from plain English, runs them on every deploy, and a forward-deployed engineer reviews every failure. Spend less time on config drift, more time shipping.

From $2,500/mo. Results in 7 days.

Go on vacation. Bug0 never sleeps. - Your AI QA engineer runs 24/7

Go on vacation.
Bug0 never sleeps.

Your AI QA engineer runs 24/7 — on every commit, every deploy, every schedule. Full coverage while you're off the grid.