Unsupported input
The tool may reject input that does not match the expected content, structure, or file type.
Fix: Confirm the tool input requirements and paste the correct type of data.
header • up to 320x100 / 728x90
Compare two texts and highlight differences
Paste text or upload files on either side to compare them.
Output will appear here...
content bottom • up to 300x250
sidebar • 160x600
Last reviewed:
Diff Checker compares two blocks of text and shows a side-by-side or inline diff with line-level and character-level change highlighting. Under the hood it uses the Myers diff algorithm — the same one git uses — so the output lines up with what you'd see in a git diff.
Modes include plain text, programming-language-aware (syntax-highlighted diffs), JSON-aware (structural diff across key order changes), and XML-aware.
Start with the diff input you want to process in Diff Checker.
Get a diff result from Diff Checker that is ready to review, copy, and reuse in the next step of your workflow.
The tool may reject input that does not match the expected content, structure, or file type.
Fix: Confirm the tool input requirements and paste the correct type of data.
Missing fields or partial content can block processing or produce weak results.
Fix: Provide the full required input before running the tool.
Sample or placeholder values can lead to output that looks valid but is not ready for real use.
Fix: Replace placeholders with your actual values before relying on the result.
Myers diff, the same algorithm used by git, so the output matches what you'd see in `git diff`. For very large inputs with many changes, the tool falls back to Patience diff, which is better at aligning moved blocks of code.
Toggles in the sidebar let you ignore trailing whitespace, collapse consecutive whitespace into one space, and normalize line endings (CRLF vs LF vs CR). Off by default so the diff is exact; enable whichever rules match how your VCS is configured.
JSON diff parses both inputs, walks the object tree, and reports changes at the property level — so reordering keys, rewriting whitespace, or changing indentation doesn't show as a difference. Plain-text diff would flag all of those.
Yes, up to about 5 MB per side. Beyond that, the browser's memory footprint gets expensive — the tool switches to a 'summary mode' that only shows changed hunks rather than the full document to stay responsive.
No. Diff Checker is text-only. For binary diffs (images, archives), use a hex-diff tool or a specialized comparison utility — the output of a textual diff on binary data is unreadable anyway.
Yes. The 'Share' button generates a URL that encodes both sides of the diff (compressed) so opening the URL restores the exact comparison. The diff is computed client-side; nothing is stored on the server.
Continue the workflow with related tools for diff, adjacent input and output steps, or other utilities in the same category. You can also browse the full Visual & Testing Tools category for more options.
View and preview HTML
Test internet ping, download speed, and upload speed in your browser with a live gauge, connection details, and same-origin Mbps measurements.
Test JSONPath expressions against JSON data
View and explore JSON data
Edit and preview Markdown with live preview
Preview Markdown as rendered HTML
Test and debug regular expressions
View and explore XML documents
Test XPath expressions against XML
View and explore YAML data
Check WCAG AA and AAA contrast ratios for text and background color combinations
Check tap target size and spacing against mobile accessibility guidelines