How to Use
Enter Your Text
Choose Operation
View Results
Copy Output
Learn More
How to Compare Two Versions of a Document Without Installing Git
Most diff tutorials assume you already have a repository, a terminal and a working git command. Writers, QA testers, support agents, lawyers and students rarely do. This page skips all of that. Paste the older text into the Original box, paste the newer text into Modified, press Compare, and the result appears underneath as one scrollable list you can read top to bottom. Nothing is uploaded: the matching algorithm runs in JavaScript inside your own browser tab, which is why the page still works on locked down office laptops. On a phone the two boxes stack vertically instead of sitting side by side. There is no sign up, no file picker and no waiting on a server round trip. If you can select the text, you can diff it.
What the Added, Removed and Unchanged Counters Are Actually Counting
After you press Compare, three chips appear above the output. Added is green, Removed is red, Unchanged is grey, and every one of them counts lines, never words or characters. A line that exists only in the Modified text is Added and prints with a plus sign. A line that exists only in the Original is Removed and prints with a minus. Identical lines keep a blank prefix and stay grey. Reading the chips before reading the body saves real time: if Removed is zero, nothing was deleted and you only need to scan the green rows. If both counters sit at zero, the two texts match exactly and the tool prints a plain message saying no differences were found rather than an empty panel.
Why a One Word Edit Shows Up as a Deleted Line Plus a New Line
The comparison is line based. It splits both texts on newline characters and runs a longest common subsequence pass over the two arrays of lines, so the smallest change it can describe is a whole line. Change colour to color inside a two hundred character paragraph and that paragraph comes back as one removed line followed by one added line, not as a four character edit. This surprises people comparing prose that was written as long unwrapped paragraphs. The fix is to give the algorithm more line breaks to work with: hard wrap both texts at sentence boundaries before you compare, or compare one section at a time. Code, CSV rows, log files and config files already carry one record per line, so they diff cleanly with no preparation at all.
Checking a Config, JSON or Env File Against the Version Already Deployed
A surprising share of production incidents come down to a single key that differs between staging and live. Copy the deployed config out of your dashboard into the Original box, paste the file you are about to ship into Modified, and the red rows are exactly what you are taking away. Two habits make this trustworthy. First, normalise formatting on both sides before comparing, running each through a JSON formatter so indentation and key order line up, otherwise every single line looks changed. Second, replace secrets with placeholders while you work; the comparison itself stays in your browser, but a screenshot of the result pasted into a ticket will not. Sorting keys alphabetically on both sides removes another whole category of false differences.
Trailing Spaces, Tabs and Line Endings That Create Differences You Cannot See
When two lines look identical on screen yet the diff still paints them red and green, the culprit is invisible whitespace. The usual suspects are a trailing space left behind by an editor, a tab facing four spaces, a non breaking space pasted out of a word processor or a web page, and Windows CRLF endings meeting Unix LF endings. Each line is compared with exact string equality, and there is no ignore whitespace switch on this tool, so every one of those counts as a genuine difference. Clean both sides with a whitespace remover first, or retype the suspicious line in both boxes and compare again. When the phantom rows vanish after cleaning, you have proved the content never changed, only its formatting did.
Frequently Asked Questions
Paste the older version into the Original box, the newer one into Modified, and press Compare. The comparison runs in JavaScript inside your own browser tab, so neither version is sent to a server and no account or file upload is involved. You are pasting text, not attaching a document, which is why it works on restricted work laptops.
Usually one of three things. The two texts use different line endings, so Windows CRLF lines never match Unix LF lines. Indentation changed from tabs to spaces. Or the text was pasted as one enormous unwrapped line, in which case a single word edit makes that whole line both removed and added.
No. It splits both texts on newlines and compares whole lines, so the finest change it can report is one removed line paired with one added line. To narrow down a wording edit, hard-wrap both texts at sentence boundaries before comparing, or paste just the two versions of that single sentence.
There is no enforced character or line cap, but the matching algorithm builds a grid sized by the line counts of both texts. A few thousand lines each is comfortable. Tens of thousands of lines on both sides will make the browser tab stall, so compare those in chunks, file by file or function by function.
The comparison is literal, so reordered keys show as removed and added lines even when the data is identical. Format both versions the same way first, using a JSON formatter with consistent indentation, and sort the keys alphabetically on both sides. Once the structure matches, the only rows left highlighted are genuine value changes.