What to Do When Your Diff Tool Shows No Difference (But You Know Something Changed)

I pasted two config files into a diff checker. It said they were identical. I knew they were not — the server crashed with the new version but worked fine with the old one. Something had changed. The diff tool was not wrong. I was.

A text diff checker is one of those tools you do not think about until it lies to you. Here is what I learned about why diff tools miss changes, and how to actually find what you are looking for.

The Invisible Diff: Whitespace Changes You Cannot See

I spent 20 minutes staring at two identical-looking blocks of JSON before I noticed the indentation was different. The old file used tabs. The new file used spaces. Every line was technically different, but the diff tool showed them as identical because I had ignore whitespace enabled by default.

This is the most common false negative in diff tools. The fix: if a diff shows no changes but you are sure something broke, toggle whitespace sensitivity. Tabs vs spaces, trailing spaces, and indentation depth are invisible to the eye but can break parsers that are whitespace-sensitive. Our diff checker shows changes with and without whitespace — toggle between modes to catch this.

The Case-Sensitivity Trap

Another time, a variable name changed from UserId to userID. The diff caught it. But when I changed ApiKey to apiKey, the diff missed it — I had case-insensitive comparison on. The code broke because the API expected the exact case.

Counter-intuitive lesson: case-sensitive comparison is more useful for debugging than case-insensitive. When something is broken, turn ON case sensitivity first. Most people do the opposite — they make the diff less strict hoping to find real changes, but the breakage is often in the details the relaxed comparison hides.

What to Do When You Still Cannot Find the Difference

If whitespace and case sensitivity are both set correctly and you still see no differences: check line endings. CRLF vs LF. This is the silent killer of cross-platform development. Files written on Windows have invisible carriage returns that files from Mac and Linux do not. The diff tool shows the text as identical. The runtime disagrees. Our diff tool can show these as visible markers so you know what is actually on each line.

If none of those are the issue, compare the file sizes. If they differ but the text is identical, there are non-printing characters — null bytes, BOM markers, Unicode direction characters. These are rare but devastating when present. For 99% of cases, toggling whitespace and case sensitivity catches the problem.