When to ignore whitespace when comparing code
Ignoring whitespace removes noise from reformatted code, but in some languages it hides real changes. Here is how to choose.
1 min read
Compare JavaScript
untitled.js
Paste content in both editors
Original1 line
Loading editor…
Modified1 line
Loading editor…
NOTHING UPLOADED · RUNS LOCALLY · FREE TO USE
About JavaScript comparison
Compare JavaScript with confidence.
Review a refactor or compare a minified bundle with its source. Syntax highlighting keeps the code readable while differences are marked.
01
Ignore whitespace
Skip formatting-only changes from Prettier or editor settings.
02
Swap sides
Use Swap to reverse the comparison without re-pasting.
03
Private by design
Your code stays in the browser and is never uploaded.
Features
Quiet tools, sharp results.
01
Aligned side by side
Two editors scroll together so the line you are reading always faces its counterpart.
02
Every change, coloured
Ember marks edits and removals. Ink marks additions. No other colours to learn.
03
Jump between differences
Step forward and back through each change with a count of how many remain.
04
Ignore the noise
Switch off whitespace and letter-case differences to focus on what really matters.
05
Changes, explained
A line-by-line list says what happened to each line, such as “Friday” became “Monday” or a number went from 3 to 4. Click any entry to jump straight to it.
How it works
Three steps. No account.
i
Paste
Drop the original on the left and the new version on the right.
ii
Compare
Differences are highlighted as you type, line by line.
iii
Decide
Review the summary, swap sides or clear the editors and go again.