Skip to content
ToolsOnDuty - free online tools
Developer ToolsNovember 6, 2026

How to Compare Text and Selectively Merge Changes Online

Compare a four-line project note, merge only one chosen change, undo it, and understand the privacy and export limits of a browser text-diff workspace.

By ToolsOnDuty Editorial Team

Text Diff workspace showing two changed lines in a four-line project note.

Comparing versions is not the same as deciding which version is correct. A text diff makes additions and removals visible so you can review them deliberately. Selective merging is useful when one edit should be accepted while another still needs discussion, especially for small notes, configuration snippets or copied text.

This guide uses the ToolsOnDuty Diff Checker with an original and changed project note. We verified both change blocks, accepted only the status change, undid that merge and checked the downloaded diff text. The screenshots show the real workspace before and after the selective merge.

Understand local autosave before pasting private text

Open Diff Checker. The original and changed text fields are processed in the browser, but they also autosave to this browser's local storage and can be restored after a reload. This is different from a disposable form whose contents disappear immediately when the tab closes.

Avoid pasting credentials, personal records or confidential documents on a shared device. Keep authoritative files outside the workspace and use anonymized examples when possible. Clear the workspace when finished and confirm the fields are empty; downloaded reports, clipboard content, backups and other browser traces are separate copies that may still need attention.

Load two versions with two deliberate changes

Paste the first block into Original text and the second into Changed text. Both have four lines. The project name and owner are unchanged, while Status changes from draft to approved and Deadline changes from Friday to Monday. Using a small fixture makes it easier to check each merge operation without guessing what a large comparison contains.

Click Find difference. The split result should show two removals and two additions in two change blocks. A modified line is represented by its removed old version and added new version, rather than counted as a single abstract replacement. Confirm which side is original before touching the merge controls.

text
Project: Atlas
Status: draft
Owner: Design
Deadline: Friday
text
Project: Atlas
Status: approved
Owner: Design
Deadline: Monday
Original and changed project notes with Status and Deadline highlighted as two change blocks.
Actual comparison: two removed lines and two added lines, grouped into two changes.

Review display options without hiding meaningful edits

Split view places the versions side by side; unified view combines additions and removals into one sequence. Word or character precision can help inspect small changes inside a line. These choices affect how you inspect differences, not which version your team should approve.

Ignore settings can suppress case, whitespace and other chosen differences. Use them only when those distinctions are genuinely irrelevant. Whitespace can matter in configuration or programming languages, and letter case can distinguish identifiers. Start with the normal comparison, document any ignore settings, and recheck the unfiltered result before accepting consequential edits.

Accept the status change without accepting the deadline

For the Status block, use the merge control whose tooltip says Apply the right (changed) version to the left. This direction copies the changed block into Original text. The opposite control copies the original block into the changed side; choosing a button by color alone can therefore apply the reverse edit.

After this operation, Original text should contain Status: approved but still Deadline: Friday. The changed side retains Deadline: Monday. We checked those exact values. One addition and one removal now remain because the deadline still differs. This demonstrates a selective merge, not replacement of the entire original note.

Both notes have approved status after merging, while Friday and Monday remain as the only deadline difference.
Verified selective merge: status is accepted, but the original Friday deadline is preserved.

Undo mistakes and preserve the final text explicitly

Click Undo merge if you applied the wrong change. In our test, it restored the original note exactly, including Status: draft and Deadline: Friday. Merge history belongs to the current workspace session; do not treat it as a permanent version-control history or a reliable recovery mechanism after arbitrary browser changes.

When the review is complete, copy the intended source panel back to its maintained file and compare that saved file as well. Swap sides changes which text is on the left and right, so re-establish direction before another merge. A displayed edit is not evidence that a separate file, repository or production configuration has been updated.

Read diff exports before applying them elsewhere

Export .diff downloads unified-style hunk text. The verified export below contains the old and new Status and Deadline lines with minus and plus prefixes. Export HTML provides a standalone visual report for review. Both outputs can reveal the source content, including unchanged context lines, and should be checked before sharing.

The current .diff export does not include file-path headers such as the usual old-file and new-file lines. Do not assume it is a complete repository patch ready for git apply. For source-controlled work, generate an appropriate patch through your version-control workflow with the real file paths and context, then review it using that workflow's normal safeguards.

diff
@@ -1,4 +1,4 @@
 Project: Atlas
-Status: draft
+Status: approved
 Owner: Design
-Deadline: Friday
+Deadline: Monday

Do not mistake the similarity percentage for meaning

The initial workspace displays 33% similar, even though two of the four original lines are unchanged. Its percentage is derived from equal rows in the unified result, where a modified line contributes both a removal and an addition. It is therefore not simply the percentage of original lines or words retained.

After accepting the status edit, the displayed value becomes 60% while one deadline change remains. Neither number is a plagiarism assessment, semantic-equivalence test or measure of business correctness. Read the actual changed lines and their consequences instead of using a percentage to approve a document.

Finish with a deliberate cleanup and a smaller comparison if needed

For a very large input, compare the relevant section first and keep full files in a suitable local editor or version-control tool. The workspace is a text comparison interface, not a rich-document renderer; copying formatted documents can discard structure that a plain-text diff cannot evaluate.

We finished by clicking Clear and verified that the original autosaved value became empty. Clear also resets the visible source fields and merge history. On a shared browser, check the resulting state rather than assuming that local processing means no local persistence. Keep any intentionally retained report in an appropriate location.

Apply the steps from this guide directly in your browser.

Frequently asked questions

Does the tool save my pasted text locally?

Yes. Both source fields autosave in the current browser's local storage and may be restored after reload. Clear the workspace and verify it is empty when finished.

Can I accept only one of several changes?

Yes. Use the appropriate block merge control and check its direction. In the example, we accepted approved status while preserving the original Friday deadline.

Is the similarity value a plagiarism or correctness score?

No. It is based on equal rows in the unified diff representation. It does not assess meaning, authorship or whether the changes are appropriate.

Is Export .diff automatically a complete Git patch?

No. The current export contains unified-style hunk text without file-path headers. Use your repository's patch-generation workflow for patches intended to be applied to files.