Skip to calculator
Veomark

Free · Instant · No signup

Line Set Comparison Inspector

Set comparison of lines. Not a unified diff or code-aware patch.

Page updated 2026-09-04.

Line Set Comparison Inspector visual
Sponsored

Calculator

Original lines.

Updated lines.

Calculated Results

Added lines

--

Removed lines

--

Sponsored

What changed between two blocks of lines

Comparing 'alpha / beta / gamma' against 'alpha / beta / delta' shows 1 line added and 1 line removed: '- gamma' and '+ delta' -- 'alpha' and 'beta' appear in both versions and aren't flagged as changes at all.

This is a set-of-lines comparison: it identifies which lines exist in one version but not the other, regardless of their position -- a line that simply moved to a different position without changing its text wouldn't show up as added or removed here, only lines whose actual text content differs between the two sets.

The '-' and '+' prefixes follow the same convention as most diff tools (removed and added respectively), making this output format familiar if you've worked with git diff or similar version-control diff displays.

Why this isn't a full unified diff

Set-of-lines diff. Repeated lines and moved blocks are not a unified diff. A real unified diff (like git diff produces) tracks line position and context, correctly handling cases like a duplicated line appearing twice in one version but once in the other, or a whole block of lines moved to a different location without changing their content -- this simplified tool treats lines as a set, which doesn't capture position or duplicate-count differences.

If Version A has a line appearing twice and Version B has that same line appearing once, a full diff tool would show one instance as removed; this set-based comparison, focused on which distinct lines exist versus don't, handles that case differently.

For source code specifically, a real diff tool that understands line numbers and context (not just presence/absence) is more useful for actually applying or reviewing a patch -- this tool is better suited for quick, simple before/after text comparisons than for code review.

Related comparison and structured-diff tools

For comparing two JSON objects or structures rather than plain text lines, the Structured JSON Diff Viewer is built specifically for that structured comparison.

If you're comparing two lists of installed Python packages specifically, the Pip Freeze Diff Tool applies similar line-comparison logic to that specific use case.

Frequently Asked Questions (FAQ)

Why don't 'alpha' and 'beta' show up in the diff output?

Because they appear identically in both Version A and Version B -- this tool only reports lines that exist in one version but not the other. Since 'alpha' and 'beta' are unchanged between the two, they're excluded from the added/removed output.

Does line position matter for this diff?

No. Set-of-lines diff. Repeated lines and moved blocks are not a unified diff. This compares which distinct lines exist in each version, not where they're positioned -- a line that simply moved to a different line number without changing its text wouldn't be flagged as a change here.

How does this handle a line that's duplicated in one version but not the other?

Since this is a set-based (presence/absence) comparison rather than a full positional diff, exact duplicate-count differences between the two versions aren't tracked the way a proper unified diff tool would handle them.

Is this suitable for reviewing a code change like a git diff would show?

Not ideally. Set-of-lines diff. Repeated lines and moved blocks are not a unified diff. This is better for quick before/after text comparisons. For actual code review with line-number context and proper handling of moved blocks, a real unified diff tool (like git diff) is more appropriate.

What do the - and + symbols in the output mean?

Following standard diff convention, a line prefixed with - was present in Version A but not Version B (removed), and a line prefixed with + was present in Version B but not Version A (added).