Diff Checker shows exactly what changed between two versions of a text. Paste the original into the first box and the edited version into the second, press Compare, and the result lists the text once with every removed line in red and every added line in blue. When a line was only edited, the changed letters, digits or symbols are marked inside it, so a single typo or a new version number is easy to spot.
It is useful whenever you have two copies of something and need to know how they differ: a configuration file before and after a change, two drafts of a contract or an article, code you copied from a colleague, or two exports of the same data. Developers use it for quick checks when a full version control diff is not at hand; writers and translators use it to see what an editor changed.
The comparison runs in your browser. The texts are not uploaded and not stored, you do not need an account, and the tool is free.
Put the older version into the left box, the one that says Original text. On a phone it is the upper box.
Put the newer version into the second box, the one that says Modified text.
Press Compare in the top bar. On a phone it is the button with the two arrows.
Read the result box: red struck-through text was removed, blue text was added, and plain lines are the same in both versions.
Say the original configuration has two lines, timeout = 30 and retries = 3, and the modified one reads timeout = 60, retries = 3 and a new third line verbose = true.
The result starts with the old timeout line, where only the 3 is red and struck through, followed by the new timeout line with only the 6 in blue. The retries line is identical in both versions, so it stays plain. The verbose line exists only in the modified text and is shown in blue as an added line. Reading from top to bottom you get the whole file once, with every change in place.
Behind the scenes the checker finds the longest sequence of lines that both texts have in common. Everything outside that sequence is a difference. A removed line directly followed by an added one is then compared again, character by character, which is what produces the highlights inside a line.
Yes. It is free and needs no account or sign-up. There is no daily limit; the only practical limit is how much your browser can handle.
No. The comparison runs in JavaScript inside your browser tab and the two texts are never sent to a server. The tool saves nothing either, so keep your own copy of any text you still need.
The result box under the inputs lists the whole text once. Unchanged lines are plain, removed lines are red and struck through, and added lines are blue. When a line was replaced by another one, the old version is shown first and the new version below it, with only the changed characters coloured.
By line first. Lines that match exactly are kept, the rest are marked as removed or added. When a removed line is directly followed by an added line, the two are compared character by character, so a single changed letter or number stands out. There is no separate word mode.
No. The comparison is exact, so an extra space at the end of a line, a tab instead of spaces or a capital letter counts as a change. The only thing it ignores is the line ending style: Windows (CRLF) and Unix (LF) line breaks are treated the same.
There is no file upload. Open each file in an editor, copy its content and paste it into one of the boxes. Any plain text works this way: source code, configuration files, CSV or JSON data, contracts or article drafts.
There is no fixed limit, but the checker compares every line of one text with every line of the other, so the work grows quickly with size. Texts of a few hundred lines compare instantly, while very large texts with many thousands of lines, or extremely long single lines, can make the tab slow or unresponsive.
Yes. On a narrow screen the two boxes stack above each other and the result follows below them. Compare is the button with the two arrows in the top bar.