TL;DR — Paste two text or code blocks into the Diff Checker for instant side-by-side comparison with line and word-level highlighting. For JSON-aware diffing, format both sides first with the JSON Formatter; for pasted content with stray whitespace, the Text Cleaner.
When you reach for a diff (and Git can’t help)
- Two .env files, one works, one doesn’t. 200 lines, the difference is one URL.
- An API response that changed shape overnight. Yesterday’s payload vs today’s — what got added or removed?
- A colleague pasted "their version" of a config in Slack. Diff it against yours before applying.
- A blog draft round-tripped through editing. What did the editor actually change?
- Two SQL migrations from different branches. Will they conflict?
Compare two blocks in 5 seconds
- Open the Diff Checker.
- Paste the "before" on the left, "after" on the right.
- Read the highlights: red = removed, green = added, yellow = changed (word-level inside changed lines).
- Toggle ignore whitespace to filter out indentation-only changes.
- Toggle case insensitive for content review.
Diff tips that catch real bugs
- Pretty-print both sides first. Diffing minified JSON shows the whole line as changed. Format with the JSON Formatter, then diff.
- Sort JSON keys. If the order varies between sources, key ordering changes look like content changes. Sort both sides for true semantic diff.
- Normalize line endings. Windows CRLF vs Unix LF can make every line look changed. The Diff Checker normalizes by default.
- Use word-level highlighting on changed lines. "url = https://api.com/v1" vs "url = https://api.com/v2" — the line is "changed", but word-level shows it’s just v1 → v2.
- Three-way diffs in code review. When merging conflicting changes, compare each variant against the common ancestor — not just against each other.
Privacy: why this matters more than for most tools
The two files you’re diffing are often the most sensitive things on your machine: production .env with secrets, internal API payloads with customer data, source code under NDA. Most "online diff" sites POST both files to their server. The UtilToolkits Diff Checker runs the entire diff algorithm in JavaScript in your browser. Watch the Network tab — zero outbound requests.
FAQ
What’s the file size limit?
Browser memory is the limit — practical comfort zone is up to ~5 MB per side. For larger comparisons, use diff at the command line.
Can I diff JSON intelligently (ignore key order)?
Yes — toggle "sort keys" on both sides before comparing. This makes ordering changes invisible and surfaces only true content changes.
How is this different from git diff?
Git diffs tracked files in a repo. This diffs any two text blocks — paste from anywhere, no repo required. Useful for snippets, configs, API responses, drafts.
Does it work for code (with syntax)?
The diff is whitespace/line-based and language-agnostic. Highlights show what changed, but it doesn’t syntax-color code by language.
Comparison toolkit