Take it step by step
- Paste the old version and new version into the correct panes.
- Choose whether whitespace differences matter for the task.
- Review additions and removals in context.
- Copy or download the result, keeping the original versions separately.
A situation to try.
Changing a space in prose may be cosmetic; changing indentation in Python can alter behavior. Choose normalization accordingly.
Use the tool’s synthetic example first where available. The example here explains a decision; it is not a reported benchmark result.
Before you call it done.
- Check the input order.
- Review line endings when a whole file looks changed.
- Read nearby lines, not just highlighted fragments.
Know the limits.
A text diff does not prove code correctness or semantic equivalence.
This tool’s current boundary: Review the output before using it. Your input remains on this device.
Evidence and scope
Technical source guidance and task-specific output checks. These do not establish that every file, browser or device passes.
Use the checks above on your own exported result. A source explains the format or mechanism; it is not proof that this export preserved every feature.
Technical reference: Git: comparing changes and whitespace ↗
Choose the right tool for this step.
Text differences
Compare additions and removals between two versions.
On your deviceWhy use it: Read additions and removals in context.
Before you start: Text equality is not semantic equivalence.
Text cleanup
Tidy whitespace, casing and repeated text.
On your deviceWhy use it: Normalize text when appropriate.
Before you start: Whitespace can change code behavior.
Preparation tools process locally. Official service links take you to the authority’s website. Inspect any exported copy before sharing it.