A visual text diff that helps finish the edit
Text comparisons appear everywhere: two versions of release notes, a revised policy, Markdown documentation, copied database output, subtitle files, logs, or a draft changed outside its normal editor. Reading both from top to bottom is slow and makes small omissions easy to miss. MergeGlass aligns the documents and highlights the specific changed words inside changed lines.
You can paste text directly or load files. Line-ending normalization prevents Windows and Unix newline conventions from making every line appear changed. Optional whitespace and case controls can narrow the comparison further, but they should be used only when those distinctions do not matter to the result.
Each changed block has an explicit decision. Keeping both is useful when two drafts added separate paragraphs, while A or B is safer when the changes are alternative wording. The combined preview is visible before download, so the result can be read as a document rather than accepted as a series of isolated choices.
Make text comparisons easier to review
Preserve paragraph structure
Place paragraph breaks consistently before comparing. Reflowing an entire paragraph onto different lines can create a noisy diff.
Ignore case cautiously
Case-insensitive comparison is useful for identifiers or lists, but it can conceal meaningful capitalization changes in prose.
Compare related revisions
If versions are far apart, compare intermediate drafts first so each decision covers a smaller conceptual change.
Proofread the combined result
A diff finds textual differences; it cannot judge voice, factual accuracy, grammar, or whether duplicated passages belong together.
A repeatable four-step workflow
- Add or paste both versionsUse recognizable names such as original.md and edited.md so the source labels remain clear throughout the review.
- Set comparison rulesNormalize line endings by default, then decide whether spaces and capitalization must count as changes.
- Resolve from contextRead the lines before and after each changed block. Use both only when the two passages complement rather than contradict each other.
- Read the combined documentReview transitions and formatting in the preview, then copy or download the finished text.
Important limits
- Rich-text formatting from Word or Google Docs is not preserved in plain text.
- Ignore-whitespace can hide intentional spacing changes.
- Large generated logs may be better filtered before comparison.