Find changed lines
Isolate the lines that changed so deployment config and document edits are easier to review.
Text Diff Checker
브라우저 내부 처리
Compare two text blocks line by line.
Text diff workflow notes
Spotting what changed between two similar texts — config files, API responses — is something the eye always misses. A line-by-line comparison marking additions and removals speeds up pre-deploy checks and incident tracing. Note that changed line endings or indentation flag everything, so keep formatting and content changes separate.
Copyable diff output
Review changes in a unified diff style that is easy to paste into issues, pull requests, or team chat.
Compare sensitive text locally
The comparison runs in the browser, reducing the need to paste internal values into external diff services.
Errors you will hit
Everything differs but you changed nothing
The line endings differ. Windows uses CRLF while macOS and Linux use LF. Mismatched editor or git settings mark every line as changed.
One character changed but the whole line is flagged
Comparison is line based. To find the exact character on a long line, split it into shorter lines before comparing.
Tabs mixed with spaces
They render at the same width but are different characters. If you see a wall of indentation-only differences, normalize whitespace first.
Things to check
Whitespace can matter
JSON, YAML, and Markdown can be affected by indentation and spacing, so inspect formatting changes deliberately.
Large inputs
Very large logs or files can use a lot of browser memory. Compare only the relevant section when possible.
Whitespace changes show up as diffs
Switching indentation from tabs to spaces, or trimming trailing spaces, marks every line as changed even when the content is identical. Run a formatter first so formatting and logic changes stay separate.
The limits of line-based comparison
Changing one word marks the whole line as removed and added. In long prose or minified code that hides what actually changed. Splitting into shorter lines before comparing makes it readable.
Different line endings mark everything changed
Windows uses CRLF while Linux and macOS use LF. Comparing files from different environments flags every line even when the content matches. Check your git autocrlf setting or the editor line-ending indicator first.
More: step-by-step usage and worked examples
How to use it
- Paste the original text and the revised text into the two input areas.
- Check whether line endings, spacing, or indentation are part of the meaningful change.
- Review added, removed, and changed lines in the result area.
- Mask sensitive values before copying the diff for sharing.
Real input and output
Spotting a config change
Input
Left
timeout: 30
retries: 3
Right
timeout: 60
retries: 3Output
- timeout: 30
+ timeout: 60
retries: 3Tools that pair well
- Regex Tester
- Markdown — The awkward part of writing a README, release note or issue template is not seeing the result until you commit
- Case Converter — Convert API fields, environment variables, filenames, and document titles into camelCase, snake_case, kebab-ca
- Text Cleaner — Text copied from the web or a PDF carries invisible whitespace and zero-width characters.
- Character Counter — Application essays and reports usually come with a character limit, and organisations differ on whether spaces