Paste two versions of the same content and see a line-based unified diff: unchanged lines, removals, and additions. Optional trim and case-insensitive compare reduce noise. Swap sides or copy a plain unified diff. Everything stays in your browser — nothing is uploaded to DroidXP.
Line endings are normalized to \n. The algorithm is a longest common subsequence on lines — good for prose, configs, and logs; intra-line edits show as delete + insert of whole lines.
It splits each pane into lines, optionally normalizes them for comparison (trim whitespace and/or case folding), then runs a longest common subsequence (LCS) alignment. Matching lines stay neutral; lines only on the left are removed; lines only on the right are added. That is the same broad idea as many “unified” or “side‑by‑side” tools, tuned for fast in-browser review.
This page is intentionally line-oriented. If you change one word inside a long line, the tool typically shows that as removing the old line and inserting the new line. For fine-grained patches inside a line, use an editor plug-in or a dedicated diff engine — or break long lines before pasting.
Text is not sent to DroidXP. Optional localStorage keys droidxp-tdc-a, droidxp-tdc-b, and droidxp-tdc-opts store panes and checkbox state on this browser.
Clear removes stored text for both panes, resets compare options, and clears the options key.
No. Diffing runs locally. Drafts may be saved in localStorage on this device only.
Line-by-line. A change inside one long line usually appears as deleting that line and adding a new line with the revised content.
Line diff does not detect moves — reordering reads as removals on one side and additions on the other. Semantic or merge tools can sometimes infer moves.
Only equality checks between lines. The preview still shows the exact text you pasted in each pane.
Left and right buffers use droidxp-tdc-a and droidxp-tdc-b; options use droidxp-tdc-opts. Clear empties both panes and removes all three keys.
Paste contents here. Very large files may slow the tab — split into sections or use a desktop diff for multi-megabyte binaries.
It uses a simple unified-style line prefix ( , -, +). It is not a byte-for-byte match to git’s output or options.
Generally yes — lines are JavaScript strings. Extremely unusual combining sequences may compare differently than a byte-level tool.
Even though nothing is uploaded, shoulder surfing and browser extensions remain risks. Follow your org’s policy for sensitive data.