Text Diff for Application Drafts

How the line diff decides add and remove

The two boxes are split on newline. A longest-common-subsequence pass marks lines that appear in both, in order. A line only on the left is rose (removed). A line only on the right is green (added). Unchanged lines stay white. The sample original is alpha / beta / gamma and the changed text is alpha / beta-revised / gamma / delta, so beta is removed, beta-revised is added, and delta is added. The comparison is the whole line. It does not highlight the changed word inside a line.

A space at the end of a line makes that line different. A blank line is a real line. Reordering two lines shows as a remove plus an add, not as a move. The algorithm is O(n×m) in the number of lines, so it is meant for a declaration, an SOP, or a short config, not a multi-megabyte log. Very long inputs can stall the tab. There is no "ignore case" switch and no word diff.

Use it before you paste a revised answer into an Indian application form: put yesterday’s draft on the left and today’s on the right, and read the green and rose lines. The text is not uploaded. The result is not saved. If the draft was wrapped by a PDF copy, join the line breaks first or every wrapped line will look like a change.

How to use it

1. Put the older draft in Original and the newer draft in Changed.
2. Read rose lines as deletions and green lines as insertions. White lines are the same text.
3. If every line is coloured, check for wrapped lines or trailing spaces.
4. Copy the Changed text into the form only after the coloured lines are the edits you meant.

The text stays in this browser tab. GetFixMyFile does not upload it, store it, or include it in analytics.