Paste text above and hit Compare (or just type — it updates live).
Compare two configs — .env, YAML, INI, nginx, anything line-based — without pasting secrets into a server-side tool: the diff below runs entirely in your browser. The sample is a staging vs production .env.
The fastest way to answer is to diff the configs. Paste both versions above (or open the files directly) and every changed key stands out with the changed value highlighted inside the line — in the sample, the pool size, cache TTL, rate limit and a feature flag all differ, and production has a timeout key staging doesn't. That's four suspects for the incident channel in five seconds.
Configs are exactly the text you least want on someone else's server: connection strings, API keys, internal hostnames. This page is static — the comparison runs as plain JavaScript in your browser, and nothing you paste or open is transmitted anywhere. Load the page, go offline, and it still works.
Line-based formats — .env, INI, nginx/Apache blocks, Dockerfiles, crontabs — diff beautifully as-is. YAML too, though tick Ignore whitespace cautiously: indentation is meaningful in YAML, and this tool's ignore option treats all whitespace runs as equal, so keep it off when nesting might have changed. JSON configs are better served by the JSON diff, which pretty-prints and key-sorts both sides so reordered keys don't show as changes.
Copy patch turns the comparison into a unified diff you can paste into the incident timeline or a ticket — a precise, greppable record of what differed, instead of a screenshot.