Skip to content
ListDiff

Check two config versions before you deploy

Last updated: 2026-10-06

Most “did we actually change the timeout?” jobs are two small files, not a Git GUI. Paste the old file and the new file. If they are plain text, use the line diff below. If they are JSON objects that only reformatted, switch tools so key order does not look like an incident.

Pick the mode

  • Text compare (this page) — .env, nginx, INI-like snippets, YAML you are reading as lines, logs. Order and exact wording matter. See text compare docs.
  • JSON compare — valid JSON config / fixtures. Object key order ignored. API JSON workflow or the JSON product.
  • List compare — a list of hostnames, feature flags, or allowlist IDs with no other structure.

Settings that help on configs

  • Ignore blank lines when someone saved the file with extra gaps.
  • Ignore whitespace when indent-only changes are not the review.
  • Leave case on for env keys that are truly case-sensitive.
  • Changes only plus Next/Prev on long nginx files.

Secrets

The compare runs in your browser, but the screen still shows the paste. Do not drop production secrets into a shared screenshot. See Is ListDiff safe?.

Paste config versions here

Text A (original)
0 lines
Text B (changed)
0 lines
Updates as you type

Paste both sides—the diff updates automatically.

FAQ

Should I compare JSON config as text or as JSON?

Valid JSON whose only issue is key order or indent → JSON compare. Otherwise stay on text compare.

Can ListDiff open my Git repo?

No. Paste or upload the two versions.

Related