Compare two texts: word differences, line changes and review reports
A comparison helps you locate changes between two versions. Its settings decide which differences are visible, so begin with the exact text and use normalization only when it suits the review.
Keep the original and revised versions separate
Open Text Compare / Diff Checker. Paste the old version on the original side and the new version on the revised side, or open UTF-8 text files. Try the built-in example when you want to learn the display before using your own draft.
For a short announcement, word mode makes an edited date or added phrase easy to spot. Line mode is useful for structured notes, lists or code where whole lines are the units you want to inspect. An empty original shows additions; an empty revised version shows removals.
Choose word or line mode for the task
A small revision with a large meaning
Original: Send the report by Friday.
Revised: Send the final report by Monday.Word mode highlights both the new description and the changed deadline. Read the complete revised sentence too: the tool locates edits, but cannot tell you whether Monday is the intended date.
In line mode, adding a blank line or moving a paragraph can create several changed sections. A comparison describes the difference between the versions; it does not reliably explain an editor’s intent or identify a moved paragraph as a special move operation.
Use ignore options deliberately
Start with case and spacing differences visible. Then enable ignore case or ignore spaces and tabs only when those differences are irrelevant to your task. Ignoring whitespace means indentation can disappear from the comparison; that matters when reviewing code or formatted data.
Both versions normalize CRLF and CR line endings to LF. This makes text from different operating systems easier to compare, but the tool is not a byte-for-byte file checker. To compare file bytes instead, use the File Checksum Calculator with the same algorithm on both files.
After changing a setting, compare again and make sure the report represents the options you intended. For a final editorial check, inspect an exact comparison as well as any simplified view.
Review changes and choose the right report
- Navigate the change blocks and read each edit in context.
- Check names, dates, amounts and negations such as “not.”
- Use the Word Counter if the revised draft has a length requirement.
- Export TXT for a plain report, JSON for structured segments, or HTML for highlighted versions you can print.
- Open the downloaded report and confirm that it contains the intended drafts and options.
Reports include both versions, so treat them as copies of your source material. They are review reports, not patches to apply to a file. Clear both drafts when the task is complete, and consult the privacy information for production page scripts before handling confidential text.
Questions & answers
Which mode should I use for a paragraph?
Word mode makes small phrase edits easy to locate. Line mode helps when complete lines are the units you want to review. Try the mode that keeps the result understandable.
Why did a capitalization change disappear?
Ignore case may be enabled. Turn it off and compare again when capitalization matters.
Is this a byte-for-byte file comparison?
No. Line endings are normalized, and optional ignore settings can suppress differences. File checksums are useful when you need to compare bytes.
Can I print the comparison?
Download the standalone HTML report, open it in your browser and use the browser’s print command. The report contains both versions and their highlighted changes.
Ready to try it?
Start with Text Compare, or choose another practical guide.