A text diff answers one question: what changed between two versions? You paste an original on the left and a revision on the right, then scan red removals, green additions, and paired change rows with word-level highlights. This guide is a change-review reference for drafts, configs, and snippets - not a clone of git documentation. Compare privately in the free Diff Checker.
Quick answer
Removed lines appear only on the left (often red). Added lines appear only on the right (often green). When a removal sits next to an addition, many tools pair them as a changed row and highlight the tokens that moved. Turn on ignore whitespace when indentation or space runs are noise. Prefer a browser-only compare when the paste includes secrets. Copy a unified patch when you need a chat- or ticket-ready summary. The tool page owns transactional diff checker searches; this article covers how to read the output.
Added, removed, and changed rows
Line-level compare finds a longest common subsequence of shared lines, then marks everything else as inserted or deleted. Pure inserts show as added. Pure deletes show as removed. When a deleted line lines up beside an inserted line, the UI often treats that pair as a change and runs a second, word-level pass so you see which words or tokens actually moved.
- Removed - present in the original, gone in the revision
- Added - new in the revision, absent from the original
- Changed - adjacent remove+add pair with word-level highlights inside the line
- Unchanged - shared lines; hide them when you only want the edits
- Similarity % - usually based on shared lines relative to both sides (identical text scores 100%)
Changed vs added + removed
If one word inside a long sentence flips, you want a change row with that token highlighted - not two full lines of red and green. If whole paragraphs appear or disappear, expect clean added or removed blocks without pairing.
When ignore whitespace helps
Re-indenting a file, converting tabs to spaces, or pasting from Word can light up half the pane even when the words are the same. Ignore whitespace normalizes runs of spaces and tabs and trims each line before compare, so formatting noise drops out and real wording edits stay visible.
- Use it after auto-format or indent-only edits
- Use it when Windows vs Mac pastes changed trailing spaces
- Leave it off when whitespace itself is the bug (YAML, Makefiles, Python)
- Pair with ignore case when you only care about wording, not capitalization
- Hide unchanged lines after the noise options so the pane shows edits only
Why compare locally (privacy)
Many online diff sites upload both sides to a server even over HTTPS. That is a poor fit for .env files, customer contracts, access logs, or unreleased copy. A private diff checker runs the compare in your browser - longest-common-subsequence in memory - so the paste never leaves the device. Prefer that workflow whenever the text would be awkward to paste into a random SaaS.
- Configs, secrets, and API keys stay on your machine
- Legal and HR drafts do not need a third-party retention policy
- Code snippets outside a PR can be reviewed without opening a repo
- Soft line caps (for example 4,000 lines per side) keep the browser responsive - split huge files into sections
Copy as a unified patch
Side-by-side color is great for reading. Chat threads and tickets often want a pasteable summary instead. A unified diff uses --- / +++ headers and - / + line prefixes in the Git style so reviewers can skim the same edit without opening your browser. Copy counts (added / removed / changed) plus the patch when you need both a headline and the detail.
- Paste into Slack, email, or a bug report without screenshots
- Keep the patch short - hide unchanged lines before copy when possible
- Remember it is a text patch, not a structural JSON report
- For JSON where key order does not matter, use the JSON Diff Checker instead
A practical change-review checklist
- Paste original left, revision right - wait for the side-by-side update
- Toggle ignore whitespace (and ignore case if needed) before you trust the red/green map
- Scan changed rows for the token highlights that matter
- Hide unchanged lines on long files
- Copy the unified patch when someone else needs the edit without the UI
- Never upload secrets to a hosted diff site when a local tool exists
Compare two texts in your browser
Guides explain the colors; they cannot safely hold your drafts. Run the compare locally, then copy a unified summary when you need to share the edit.
- Diff Checker - side-by-side text and code compare with word highlights, ignore whitespace, and copyable unified diff - nothing uploaded.
- JSON Diff Checker - structural JSON compare by keys and values when line order should not matter.
Frequently asked questions
What do red and green mean in a text diff?
Conventionally, red marks removals (original only) and green marks additions (revision only). Changed rows combine both sides with word-level highlights so you see which tokens moved inside the line.
When should I turn on ignore whitespace?
When indentation, tab/space conversion, or trailing spaces create false positives. Leave it off when whitespace is meaningful - YAML, Python, Makefiles, and some templates.
Is a unified diff the same as a Git commit?
No. A unified patch is a portable text format that Git also uses. Copying one from a browser tool does not create a commit - it only gives you a pasteable view of the same line edits.
When should I use JSON Diff instead of text Diff?
Use text Diff for prose, configs as text, and source snippets. Use the JSON Diff Checker when you care about keys and values and key order should not count as a change.
Is my text uploaded?
Not on ToolsMinify. The Diff Checker runs the compare in your browser, so configs, logs, and contracts stay on your device.
Read a text diff without uploading
Open the free Diff Checker, paste original and changed text, toggle ignore whitespace if needed, review added / removed / changed rows, and copy a unified patch for chat or tickets.