Skip to content

Compare Excel and CSV spreadsheets online

Verify revised pricing sheets, inventory dumps, or financial exports without exposing private workbooks to an online comparison service.

Original (Before)
Updated (After)

How to use Compare Excel & CSV

  1. Load both Before and After spreadsheets. Drop Original (Before) and Updated (After) .xlsx, .csv, or .tsv files, load the sample pricing sheets, and pick each workbook tab when multi-sheet files load.
  2. Set row matching and cell tolerance rules. Choose Key column or Row order matching, select the key header such as SKU, and configure Numeric tolerance, Trim whitespace, or Ignore case.
  3. Run the comparison and filter changes. Click Compare to compute Added, Removed, Modified, and Unchanged counts, then inspect cell edits in the diff viewer.
  4. Download your styled diff report. Choose Download Diff XLSX for a color-highlighted two-sheet workbook or Download Diff CSV for a formula-safe table summary.

Your files are processed on this device and never uploaded. They stay private, and there's nothing to delete afterwards.

How does browser Excel comparison detect row and cell differences locally?

Dropping Original (Before) and Updated (After) files lets you compare Excel and CSV sheets inside a local Web Worker that parses worksheets, unifies header columns, matches records, and highlights changed cells inside browser memory. Because neither file touches a server, sensitive price books and ERP snapshots remain strictly on your device.

The worker inspects incoming spreadsheets using three safety-bounded stages built around the ECMA-376 OpenXML workbook specification:

  • Multi-sheet workbook extraction: Files matching .xlsx extensions or 0x50 0x4B ZIP signatures load every worksheet tab under 180 MB unpacked XML, 100 MB single-entry, and 250,000 row-per-sheet limits.
  • CSV and TSV decoding: Text exports strip leading UTF-8 BOM markers, decode UTF-8 with Windows-1252 fallback, and sniff comma, semicolon, tab, or pipe separators across 10,000 characters and 10 logical rows.
  • Cross-format sheet selectors: Whenever either workbook contains multiple tabs, dropdown lists surface each sheet name and row count so you can compare an updated Excel tab straight against a legacy CSV dump.

Teams archiving individual worksheets in Git repositories before comparing quarterly revisions often extract standalone CSV tabs ready for version tracking alongside binary .xlsx snapshots.

Matching rows by key column versus row position with tolerance

Choosing how rows align decides whether your spreadsheet diff highlights meaningful record updates or floods your screen with line-shift noise. Clicking Load sample sheets loads catalog-before.csv and catalog-after.csv preconfigured with SKU key alignment and a 0.001 rounding tolerance to demonstrate both behaviors immediately.

Key-column alignment, duplicate keys, and unified header order

Matching by Key column indexes rows on a chosen column such as SKU, Order ID, or Email so inserted, deleted, or re-sorted rows never cause false edits below them. Duplicate keys automatically gain numbered disambiguation suffixes (#2, #3) and empty keys receive internal blank markers so repeated records never overwrite one another.

To compare schemas cleanly when columns move or get added, the unified header builder preserves all Before columns in their original order and appends any new After headers matched trimmed and case-insensitively. Delimited files loaded for key matching follow IETF RFC 4180 CSV specification quoting rules so embedded commas inside descriptions stay aligned cleanly.

Numeric tolerance, comma-number parsing, trim, and case rules

Each paired cell passes through Numeric tolerance evaluation first. Comma-formatted strings such as 1,250.50 normalize to floating-point numbers, treating two values as equal whenever their absolute difference stays at or below your tolerance (for example, 14.95 and 14.9504 match under 0.001).

When strings remain after numeric checks, Trim whitespace (enabled by default) collapses consecutive spaces and strips outer padding, while Ignore case lets you treat capitalization edits like Active versus active as unchanged.

Comparison Setting Default Behavior Normalization Rule Primary Purpose
Key column matching Matches selected header name Disambiguates duplicates with #2, #3 Prevents cascading diffs after insertions
Row order matching Compares index i line by line Labels keys as Row 2, Row 3, etc. Compares keyless lists or fixed exports
Numeric tolerance 0 (exact match, configurable) Strips thousands commas before diff Ignores ERP or pricing rounding noise
Trim whitespace Enabled by default Collapses \s+ and trims outer spaces Eliminates trailing-space false positives
Ignore case Disabled (case-sensitive) Compares lowercased normalized strings Skips capitalization-only text edits

For unstructured log files, SQL scripts, or plain JSON configuration snapshots rather than column tables, switch to a line-by-line plain text diff viewer cleanly.

Reviewing Added, Removed, and Modified rows in the diff grid

Once comparison completes, four KPI summary cards report Added rows (+N), Removed rows (-N), Modified rows (~N), and Unchanged rows side by side. Selecting Changed only, All rows, Added, Removed, or Modified filters the interactive table instantly.

KPI summary counters, row status filters, and 300-row viewer cap

The interactive Diff rows table highlights added records in soft emerald, removed rows in soft rose, and modified cells in amber displaying struck-through original values next to the updated value (before -> after). Up to 300 filtered rows render in the browser grid to keep scrolling responsive on large price lists without freezing browser layout painting.

Generated XML report cells follow W3C XML 1.0 specification escaping so ampersands, angle brackets, and quotes inside cell values never corrupt downloaded OpenXML worksheets. Unchanged cells retain plain text styling so stakeholder reviewers focus immediately on genuine pricing, quantity, or description edits.

Pre-comparison table consolidation and clean audit workflows

When revised inventory or invoice exports arrive split across regional batches, analysts frequently combine multiple CSV or Excel tables by key first so comparing before and after snapshots requires only one unified Excel diff pass. Grouping files beforehand ensures missing regional SKUs do not trigger fragmented partial diffs.

Exporting styled XLSX diff reports and formula-safe Diff CSV

Clicking Download Diff XLSX generates spreadsheet-diff-report.xlsx containing all compared rows regardless of the 300-row on-screen preview limit. Column widths auto-fit cleanly between 8 and 60 characters across both worksheets, and every workbook contains two OpenXML sheets built with custom <styleSheet> fills and bold Calibri 11 pt headers:

  • Summary worksheet: Records Before and After filenames, selected worksheet names, total row counts, added, removed, modified, and unchanged KPI metrics, and exact changed-cell totals.
  • Diff Details worksheet: Lists Status, Row / Key, and every unified column using #F1F5F9 gray headers, #DCFCE7 light green added rows, #FEE2E2 light red removed rows, and #FEF3C7 amber modified cells formatting before -> after diffs.

Choosing Download Diff CSV outputs spreadsheet-diff-report.csv with a UTF-8 BOM and MITRE CWE-1236 formula injection guidance enabled, prefixing untrusted leading =, +, @, |, and non-numeric - cells with an apostrophe so desktop spreadsheet apps treat changed values as inert text rather than executable commands. Teams auditing updated meeting timetables exported from calendars can also pair our iCalendar schedule to spreadsheet converter before running a side-by-side schedule diff across quarterly shifts.

Questions

Why does key-column comparison prevent false row shifts after insertions?

Line-by-line row comparison flags every record below a newly inserted or deleted row as modified. Matching by a key column such as SKU or Order ID aligns identical records by identifier regardless of row sorting, isolating only genuine cell edits, additions, and removals.

What happens if a key column contains duplicate or blank identifiers?

Duplicate key values do not overwrite earlier rows silently. Instead, repeated keys receive numbered disambiguation suffixes such as #2 and blank keys receive internal indexed markers so every row from both sheets remains accounted for during comparison.

How does Numeric tolerance handle rounding changes across pricing or ERP exports?

Numeric comparison strips thousands commas and checks whether the absolute difference between parsed numbers stays at or below your tolerance setting. For example, setting tolerance to 0.001 treats 14.95 and 14.9504 as unchanged instead of marking rounding noise as modified.

Can I compare different worksheets from multi-tab Excel workbooks?

Yes. When either Original (Before) or Updated (After) .xlsx file contains multiple tabs, per-side worksheet dropdowns appear showing each sheet name and row count so you can compare Tab A against Tab B or cross-compare a .xlsx tab against a .csv export.

What colors and sheets are inside the exported Diff XLSX report?

The generated spreadsheet-diff-report.xlsx workbook contains a Summary sheet listing file names, sheet names, row counts, and changed cell totals, plus a Diff Details sheet styled with light green added rows, light red removed rows, and amber modified cells showing before -> after text.

Are financial sheets or pricing lists uploaded during comparison?

No. Both workbooks transfer directly into the local everyday Web Worker running inside browser memory, so pricing models, payroll runs, and supplier catalogs never leave your device or touch external servers.

Updated