Find changed lines
Isolate the lines that changed so deployment config and document edits are easier to review.
🔒 Browser-side processing
Compare two text blocks line by line.
Guide
Compare two similar text blocks such as config files, drafts, or API responses and focus on the changed lines.
Isolate the lines that changed so deployment config and document edits are easier to review.
Review changes in a unified diff style that is easy to paste into issues, pull requests, or team chat.
The comparison runs in the browser, reducing the need to paste internal values into external diff services.
Workflow
Examples
Input
Left
timeout: 30
retries: 3
Right
timeout: 60
retries: 3
Output
- timeout: 30
+ timeout: 60
retries: 3
Troubleshooting
The line endings differ. Windows uses CRLF while macOS and Linux use LF. Mismatched editor or git settings mark every line as changed.
Comparison is line based. To find the exact character on a long line, split it into shorter lines before comparing.
They render at the same width but are different characters. If you see a wall of indentation-only differences, normalize whitespace first.
Review
JSON, YAML, and Markdown can be affected by indentation and spacing, so inspect formatting changes deliberately.
Very large logs or files can use a lot of browser memory. Compare only the relevant section when possible.
Related