MinifyPic

Text Compare

Put two versions side by side and see exactly what changed — every added, removed and modified line, highlighted.

FreeLine-by-linePrivate
Loading tool…

How it works

A compact workflow from input to download.

1

Paste both versions

Put the original text in the left box and the revised text in the right.

2

Read the differences

Added, removed and changed lines are highlighted so the differences are impossible to miss.

3

Act on the result

Use the highlighted diff to review edits, approve changes or track down what broke.

Frequently asked questions

What exactly does it compare?
It compares line by line, marking lines that exist only in the original, lines that exist only in the revision, and lines that changed between the two. This is the same model used by version control tools, and it is the right granularity for prose, code, configuration files and lists alike.
Can it compare Word or PDF documents?
Not directly — it works on plain text. Copy the text out of the document and paste it in. That has the useful side effect of stripping formatting, so you are comparing what the documents actually say rather than how they are styled.
Is my text uploaded?
No. Both versions stay in your browser and the comparison runs locally, which is what makes it safe to use on contracts, legal drafts and confidential material.
Why do lines that look identical get flagged?
Almost always because of invisible whitespace — a trailing space, a tab where there should be spaces, or a different line-ending convention between Windows and Unix. Run both texts through the Remove Extra Spaces tool first if you are getting spurious differences.

Where a diff earns its keep

The moment you have two versions of anything and a suspicion that they differ, a diff saves you from reading both in full. A contract comes back from the other side's lawyers with the assurance that they have made 'a few small changes'; a diff shows you in seconds that clause fourteen has quietly acquired a new sentence. A configuration file that worked yesterday does not work today, and comparing it against the backup finds the one changed value. A colleague sends a revised draft with no track changes; a diff reconstructs what they actually did. In every case the value is the same: the differences are a tiny fraction of the text, and a diff shows you only those, instead of asking you to hold two documents in your head at once.

Reading a diff properly

A line-based diff has one systematic blind spot worth knowing about. Because it works a line at a time, changing a single character on a long line marks that entire line as changed — the diff will tell you the line differs but not that only one word within it moved. Conversely, adding a single line break can make many subsequent lines appear to have shifted, producing an alarming-looking diff for a trivial edit. And a diff shows you what changed, never why: it will faithfully report that a number went from 30 to 300 without any opinion about whether that was a deliberate decision or a catastrophic typo. The tool narrows your attention to the right places; judging what you find there is still your job.