Text Compare and Markdown Diff Checker
Free text compare tool. Diff two texts or markdown files side by side, highlight added and removed lines and words, and compare rendered output.
| 1 | # Release notes | 1 | # Release notes |
| 2 | 2 | ||
| 3 | ## 1.2.0 | 3 | ## 1.2.1 |
| 4 | 4 | ||
| 5 | - Added dark mode | 5 | - Added dark mode |
| 6 | - Fixed table alignment on mobile | 6 | - Fixed table alignment on mobile and tablet |
| 7 | - Improved export speed by 20% | 7 | - Improved export speed by 35% |
| 8 | - Removed the legacy PDF engine | ||
| 8 | 9 | ||
| 9 | Thanks to everyone who reported bugs. | 10 | Thanks to everyone who reported bugs and sent patches. |
What Is a Text Compare Tool?
A text compare tool is a diff checker that takes two versions of a text, finds the lines, words or characters that were added or removed, and shows both versions with the changes highlighted. This page does that for plain text and markdown, side by side or inline, and can also compare the rendered output so formatting-only edits do not show as changes.
It runs in your browser with the same diff algorithm used by many code editors, and the unified patch it produces is compatible with git.
How to Compare Two Texts
- Paste the older version into Original and the newer one into Changed, or open two files.
- Pick Compare by lines for code and markdown, words for prose, characters for tiny edits.
- Choose side by side to read both versions, or inline for a git-style unified view with + and − prefixes.
- Tick Ignore whitespace or Ignore case when indentation or capitalisation changes are noise.
- Tick Compare rendered markdown to diff what a reader sees rather than the syntax.
- Read the added and removed counts in the Differences header, and copy the unified patch if you need to share it.
Diff Modes and Views
| Setting | Best for | How changes are shown |
|---|---|---|
| Lines, side by side | Code, config, markdown source | Two numbered columns; removed lines tinted on the left, added on the right |
| Lines, inline | Sharing a text diff in a review | Single column with − and + prefixes, like git diff |
| Words | Edited prose, translations | Changed words marked inside the sentence |
| Characters | Typos, numbers, punctuation | Individual characters marked |
| Compare rendered markdown | Markdown diff of content, not syntax | Both sides rendered to text first, then diffed |
Markdown Diff: Source or Rendered?
Diffing markdown source shows every change, including ones that do not affect the output, such as switching from asterisks to underscores for emphasis or re-wrapping a paragraph at 80 columns. That is the view you want when reviewing a pull request. Diffing the rendered text hides those and only reports changes in the words, headings, list items and table cells a reader sees, which is what a writer or editor comparing two drafts cares about. Switch between them with a single checkbox.
When to Use Text Compare
Reach for text compare when a collaborator sends back an edited document without tracked changes, when a generated file differs from the checked-in version, or when you need to confirm that a markdown cleanup did not alter the content. The added and removed line counts give a quick size of the change, and the patch output lets you apply it elsewhere. For checking a single document against style rules, use the markdown linter linked below.
Frequently Asked Questions
What is the difference between line, word and character mode?
Line mode treats each line as a unit and is the right choice for code, markdown and anything with meaningful line breaks. Word mode finds the changed words inside otherwise similar sentences, which suits prose. Character mode is the finest grain and is useful for spotting a single changed letter or punctuation mark.
What does compare rendered markdown do?
It converts both texts to HTML with the same renderer the editor uses, strips the tags, and diffs the visible text. Two files that differ only in syntax, such as *emphasis* versus _emphasis_ or a re-wrapped paragraph, show as identical, while an actual wording change still appears. It is the markdown diff mode most editors want.
Can I get a patch file from the text compare tool?
Yes. Copy unified patch puts a standard unified diff on your clipboard, the same format produced by git diff and diff -u. Save it as a .patch file and apply it with git apply or patch, or paste it into a code review to show exactly what changed.
Does ignore whitespace also ignore blank lines?
It collapses runs of spaces and tabs and trims line ends, so re-indented lines and trailing spaces do not count as changes. Blank lines are kept, because adding or removing a paragraph break is usually a real change in markdown.
Are my documents uploaded?
No. The text compare tool and its diff checker run in your browser; both texts stay on your device. That makes it safe for contracts, unpublished posts and internal documentation.