Free · Fast · Privacy-first

Find Differences Between Two Texts

Need to find every change between two versions of a document, article, report, or policy? FixTools Diff Checker compares both versions instantly and marks every addition, deletion, and modification with colour-coded highlights so nothing is missed no matter how subtle the change.

⚡

Detects even subtle single-word changes

🔒

Colour-coded additions, deletions, and edits

✨

Works for any language or document type

⚡

Browser-based and fully private

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this Diff Checker to your website

Drop the Diff Checker into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/developer/diff-checker?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Diff Checker by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/developer/diff-checker?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Diff Checker by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Finding Differences That Manual Review Misses

When two versions of a document look nearly identical, manual review becomes unreliable in ways that most people underestimate. Research into reading cognition consistently shows that people reading familiar text fill in expected words rather than seeing what is actually printed on the page. This proofreading paradox makes manual comparison especially problematic in high-stakes contexts: legal contracts where a single changed word can materially alter the meaning of a clause, compliance documents where any unauthorised edit must be detected and recorded, or technical specifications where a changed number or unit can have significant downstream consequences. A systematic comparison tool removes human perception from the equation by mechanically comparing every character of both texts without fatigue or assumption.

FixTools Diff Checker applies the Myers diff algorithm, the same algorithm used internally by Git for computing commit diffs. The algorithm finds the longest common subsequence of lines between the two texts, representing all content that stayed the same, and marks all departures from that common sequence as insertions or deletions. Within changed lines, a second pass identifies the specific words or characters that differ, providing fine-grained highlighting at a level below the line. The result is a colour-coded output where every difference is surfaced regardless of how subtle the change is or how deeply it is embedded in a long document.

For non-technical users, the most effective workflow is to paste both document versions into the panels, click Compare, and then work through the red and green highlights from the top of the document to the bottom. Red highlights show content that was present in the original but is absent in the new version. Green highlights show content that is new in the updated version. Lines showing both colours represent content that was modified, with the old version shown in red and the new version shown in green on adjacent lines.

Two structural details of the algorithm are worth knowing because they shape what the output looks like. First, the Myers diff finds the shortest edit script in terms of inserted and deleted lines, which means moved blocks of text appear as a deletion in one location and an insertion in another rather than as a move. This is correct in a strict edit-distance sense but can surprise users who expect a tool to recognise that content was simply relocated. Second, the comparison is line-based by default, so a single-character change inside a long line marks the whole line as modified, then a secondary character-level pass highlights the specific characters that differ within that line. Performance on documents of any realistic length is effectively instant on modern devices, and because everything runs in the browser tab, the comparison is safe for confidential drafts, internal memos, and any other content that should not leave the device.

Myers diff algorithm paper Unix diff utility manual (man7.org)

How to use this tool

💡

Paste both text versions into the comparison panels and click Compare. The tool finds and highlights every difference between the two texts.

How It Works

Step-by-step guide to find differences between two texts:

1
Open the tool
Click "Open Diff Checker" to launch the tool in your browser. No installation or account is required. The tool is ready to use immediately on any modern browser on any device.
2
Paste your original text
Add the older or baseline version of your text to the left panel. This is the reference version, such as the approved document, the version before editing, or the source you want to check against.
3
Paste your revised text
Add the newer or updated version to the right panel. This is the version that contains the changes you want to identify, such as the edited document, the version after review, or the latest draft.
4
Click Compare
Click the Compare button. All differences are highlighted immediately in the result panels. The comparison runs in your browser and shows results in seconds regardless of document length.
5
Review changes
Work through the results from top to bottom. Green highlights mark added content, red marks removed content, and lines showing both colours represent modified content where the old version appears in red and the new version in green on adjacent lines.

Real-world examples

Common situations where this approach makes a real difference:

Reviewing a policy document after committee edits

A governance team chair needs to confirm that the committee applied only the three agreed amendments to a policy document and did not introduce any other changes during their editing session. The Diff Checker produces an exact list of all changes in the document in seconds, confirming the three amendments were applied correctly and that no other lines were altered beyond what was agreed in the meeting.

Checking a translated article for completeness

A content publisher needs to verify that a translated article contains all the same section headings and key talking points as the source English version before publishing. Pasting both texts into the Diff Checker highlights any sections or headings present in the original that are absent from the translation, allowing the editor to flag potential omissions before the article is published to readers.

Comparing two product description versions

An e-commerce manager receives two versions of a product description from a copywriter and needs to confirm exactly what was revised before approving the final version for the product catalogue. The diff highlights every changed sentence and word, letting the manager confirm that all the requested factual updates were applied and that no previously approved content was accidentally removed during the revision process.

Auditing a terms of service update for regulatory review

A regulatory affairs officer needs to document precisely which clauses changed in an updated terms of service document before submitting the change record to a regulator. The Diff Checker produces a precise, clause-level record of every addition, deletion, and modification that can be included directly in the regulatory submission as verified evidence of the specific changes made between versions.

Pro tips

Get better results with these expert suggestions:

Break documents into sections for easier review

For very long documents, compare one logical section at a time rather than pasting the entire document at once. This keeps each diff short and focused, making it easier to review each section thoroughly and discuss specific changes with colleagues without the cognitive load of navigating a very long scrollable diff output covering an entire document in one view.

Use the diff output as a change log

After finding differences, copy the diff output and paste it into a change log or review document. Green-highlighted lines become additions in your change record and red-highlighted lines become removals. This generates a precise and automatically structured change log without having to write it manually, which both saves time and ensures the record is complete and accurate.

Compare against the last approved version

When reviewing any document for unauthorised or accidental changes, always compare against the last formally approved version rather than the most recent version you happen to have. Keep a copy of the approved version in a location you control independently, such as a dedicated archive folder, so you always have a reliable baseline for comparison that cannot be overwritten.

Normalise formatting before comparing business documents

Documents copied from PDFs, word processors, or content management systems often have inconsistent line breaks, smart quotes, hyphenation styles, and spacing. Before pasting both texts, paste each into a plain-text editor and normalise line breaks, remove smart quotes, and standardise spacing. This eliminates formatting noise from the diff and ensures the output shows only genuine content differences between the two versions.

FAQ

Frequently asked questions

FixTools uses the Myers diff algorithm, the same algorithm used by Git for computing commit diffs. It compares text line by line to find all added, removed, and changed lines, then within changed lines performs a second character-level comparison to highlight the specific words or characters that differ. This two-pass approach surfaces differences at both the line level and the fine-grained word or character level within each changed line.

Yes. The character-level highlighting within changed lines makes even a single changed word visible in its sentence context, so you do not need to read the entire line to spot the modification. This precision makes the tool reliable for catching the kinds of subtle changes that manual review misses: a replaced synonym, a changed number, a negated clause, or a modified comparison value. It also catches a class of differences that are entirely invisible in a normal text viewer: zero-width spaces (U+200B), non-breaking spaces (U+00A0), soft hyphens (U+00AD), and byte-order marks (U+FEFF) that some editors or paste paths insert silently. These characters render as nothing or as ordinary whitespace, so two paragraphs that look identical can fail an equality check because one contains an invisible Unicode character the other does not. The diff highlights each invisible character at the exact position it appears, and you can copy the highlighted character into a Unicode lookup tool to confirm the specific code point and then normalise both inputs to remove it cleanly.

Absolutely. Writers and editors use diff checkers to review revisions between drafts, verify that editorial changes were applied correctly and completely, produce a clear record of all changes made between named versions, and discuss specific modifications with contributors. The colour-coded output makes it easy to identify and discuss each change without having to read both versions in full.

Yes. The Diff Checker handles full Unicode text, so any language is fully supported including right-to-left scripts like Arabic and Hebrew, syllabic scripts like Japanese and Korean, and character-based scripts like Chinese. Differences are highlighted correctly at the character level regardless of the script used, with no need to select a language or configure the tool before comparing. One useful normalisation step for multilingual content is Unicode normalisation form NFC, which collapses precomposed and decomposed forms of the same accented character to a single canonical representation. Without this, the letter e-acute can appear as either a single precomposed code point (U+00E9) or as a base letter followed by a combining acute accent (U+0065 U+0301), and a text diff treats the two encodings as different even though they render identically. Most modern editors normalise to NFC on save, but pasted content from PDF extracts or older systems sometimes carries the decomposed form. Running both inputs through an NFC normaliser before pasting eliminates this category of false positive for multilingual documents.

You can copy the text from the result panel directly. For a formatted diff report that preserves the colour coding as a visual record, use your browser print function (Ctrl+P on Windows or Cmd+P on macOS) and save as PDF. This creates a permanent, portable, and shareable record of the differences found that retains the visual highlighting for easy reading by any recipient.

Yes. The Diff Checker was designed to be accessible to anyone who needs to compare documents, regardless of technical background. No technical knowledge is required: paste two texts, click Compare, and read the colour-coded results. The interface is clean, requires no configuration, and the output is self-explanatory. It is used regularly by HR teams, compliance officers, legal assistants, project managers, and content editors.

You can compare the text content from any document format by first copying the text out of each document and pasting it into the panels. This works for Word documents, PDFs, Google Docs exports, web pages, and any other format where the underlying text content is accessible. The diff operates on the text you paste, so format conversion happens before you paste rather than inside the tool.

After comparing, use your browser print function to save the diff view as a PDF. Before printing, note the date, the names of both document versions, and any relevant version numbers at the top of the page. The resulting PDF provides a timestamped change record suitable for compliance files, legal audit trails, and formal document management workflows where a permanent record of tracked changes is required.

When the tool reports no differences but you can see them in the source documents, the most common cause is that you pasted the same version into both panels by accident, perhaps because both versions were on the clipboard in succession and the second paste replaced the first. Clear both panels completely, paste the first version into the left panel and confirm visually that it is the original, then paste the second version into the right panel and confirm it is the revised one. A secondary cause is that you pasted formatted output from one source and unformatted output from another that the tool normalised before comparison, which is rare but can happen with rich-text clipboards.

Most document management systems maintain version history, but their built-in comparison features vary widely in quality and shareability. The portable workflow is to download or copy each version of the document as plain text or rich text, paste both into the comparison panels, and save the result as a PDF for the change record. For documents stored as files in a Git repository, run git show commit:path/to/file to extract the file content cleanly at any commit and paste both extracted versions. This works for any file format that round-trips through text, including markdown, asciidoc, and the body content of HTML or Word documents copied as plain text.

The colour convention is consistent regardless of what kind of document you are comparing: green for additions, red for deletions, neutral for unchanged context. For prose documents, an entire deleted paragraph appears as a single red block followed by its green replacement. For tabular content pasted as text, each row that changed appears as a paired red-and-green row. For structured content like JSON or XML, each property or element change appears as a pair of lines. The character-level highlighting within each changed line points to the specific words that differ, which is especially helpful for prose comparisons where the visible structural unit is a sentence rather than a discrete property.