Text compare example: three config keys
A three-line configuration change, and what a line diff does and does not tell you about it.
Open Text Compare to run this case yourself.
Before
API_TIMEOUT=30
CACHE_ENABLED=false
LOG_LEVEL=infoAfter
API_TIMEOUT=60
CACHE_ENABLED=true
LOG_LEVEL=debugThe problem
Someone hands you two versions of a small configuration snippet. All three lines exist in both versions, so a quick glance can miss that every value changed. The risk is not a missing line. It is a timeout, a cache flag, and a log level that now behave differently in production.
What changed
API_TIMEOUT moves from 30 to 60. Callers wait longer before a request is treated as failed. CACHE_ENABLED moves from false to true, so a process that previously always read fresh data may now serve a cached value. LOG_LEVEL moves from info to debug, which usually increases log volume and can include details you did not want in a shared log.
How Text Compare shows it
Text Compare splits each side on newlines and aligns lines with a longest-common-subsequence diff. None of these three lines match, so each is shown as a changed pair: the old line removed, the new line added, with the differing tokens highlighted inside the pair. A line that was identical would stay unmarked.
CRLF versus LF does not, by itself, mark every line changed. Trailing spaces, a byte-order mark, or a different wrapping of the same sentence will. If a diff looks noisier than the edit you remember, check those before you treat every line as a real change.
When this workflow is useful
Use it when the text is already plain: an environment sample with secrets removed, a config fragment from a ticket, two log excerpts, or two API bodies you have already pretty-printed. Paste the approved baseline on the left and the candidate on the right, then attach the result to the change note so the next reader sees the same three deltas.
When this tool may not be the right choice
- Semantic code analysis. The tool does not know that 60 is a timeout or that true enables a cache. It only shows that the characters differ.
- Git history. If the file is already in a repository, the commit diff is the durable record. Text Compare does not store history.
- Visual document comparison. Fonts, layout, stamps, and images are not part of a pasted text diff.
Processing and privacy
Paste tools also run on the server. The text is sent in the form POST, with a limit of 100,000 characters per field. It is not written into a document library or a user account. Server logs can still record technical request metadata such as IP address and URL. Do not paste secrets, credentials, or personal data you are not allowed to send to a web service.
The Privacy Policy and how processing works are the full description.