Diff & Compare Suite
Side-by-side diff for text, JSON, CSV, YAML, XML, and dotenv files.
Sensitive data: Anything you enter is processed in your browser only. It is never uploaded or logged on a server.
Comparing text and structured files
Effective code review depends on seeing what changed, not just that something changed. Line diffs work for source code, but JSON, YAML, CSV, and dotenv files often reorder keys or whitespace without semantic changes. Structured diff modes parse documents first so comparisons focus on values.
Configuration pull requests benefit from side-by-side views of environment files and Helm values. API contract reviews compare two OpenAPI fragments or JSON payloads returned by different service versions. Text diff remains the right choice for logs and shell scripts.
When a diff looks noisy, prettify both sides with the matching formatter, then diff again. For secrets, redact values before attaching output to tickets while keeping key names visible so reviewers understand scope.
Diff tools in the browser suit air-gapped networks and client data policies. Paste before and after snapshots during postmortems to show exactly which keys changed without uploading configs to public diff websites.
Reference Guide
Structural diffs parse input before comparing. Identical semantics with different whitespace may still show hunks after format-first workflow.
| Mode | Best for |
|---|---|
| Text | Logs, scripts, plain config |
| JSON / YAML / XML | API specs and infrastructure files |
| CSV | Data migration and export comparisons |
| Dotenv | Environment variable changes between releases |
Redact secrets before sharing diff output in tickets.
Current mode
Operation: text-diff
All processing runs locally in your browser. Paste input, click Run, and copy the result.
Example Input
alpha beta gamma
Example Secondary Input
alpha beta delta gamma
A sample loads automatically when you open this tool. Use Load Sample to reset it.