diffesq.

Diff config files semantically — JSON, YAML, XML

To find the real change between two config files, compare them semantically: Diffesq parses JSON, YAML, and XML locally and reports value and structure changes — not whitespace, reordering, or formatting noise. The one flipped flag stops hiding in a 400-line reflow.

Diff two configs

How it works

  1. Drop the two config files into the workbench (format is auto-detected).
  2. Diffesq parses both on your device and compares the structures.
  3. Review each real change, anchored to its source location.
  4. For whole config directories, use folder comparison instead.

Why semantic beats line diff for configs

  • Reordered keys, re-indentation, and comment moves don't register as changes.
  • Every reported difference is a real value or structure change, anchored to its line.
  • Secrets stay put: configs are parsed and compared locally, never uploaded to a diff site.
  • Works across JSON (incl. JSONC), YAML, and XML.

Free vs Pro

Structured-file comparisons run in full on your device on the free tier, with about a third of the results shown as a preview; Pro unlocks the complete results and clean, unwatermarked exports (HTML, Markdown, JSON, PDF).

See Pricing for plans — $2.97/month, $27.99/year, or $49 once.

Privacy

Every comparison runs locally in your browser. Your files are never uploaded — there is no server that receives them, and the page keeps working with Wi-Fi turned off. Details in the Privacy Policy.

Frequently asked questions

Can I diff two Kubernetes manifests?

Yes — YAML manifests compare semantically, so only actual field changes are reported.

What about .env or ini-style files?

Those compare with the free text diff — line-level with intraline highlighting.

Does it work offline?

Yes — once the page has loaded, parsing, comparing, and rendering all happen on your device. Turn off Wi-Fi and it still works.

Related