Compare Excel Files Online

Worked example

Two spreadsheet rows, which cell values show up, and which spreadsheet features never enter the diff.

How version 1 is rendered

[Sheet1]
Product | Quantity | Price | Status
Widget | 10 | 25 | Open
Gadget | 4 | 40 | Open

How version 2 is rendered

[Sheet1]
Product | Quantity | Price | Status
Widget | 12 | 25 | Open
Gadget | 4 | 40 | Closed

When this tool may not be the right choice

• Formula auditing. Use Excel’s formula tools when you need precedents, dependents, or a check that a formula was not replaced by a constant.
• Chart comparison, sparklines, or conditional formatting, if those are the change you care about.
• Workbooks larger than the 1,200-row cap per sheet, or files over 10 MB. Split the export or compare it in a spreadsheet with the full file.

Read the full example for what the change means, the limits, and how this input is processed.

What is Excel file comparison?

Excel file comparison identifies differences between two spreadsheets by reading cell values into text lines, then showing added, removed, and changed lines in a diff view. CompareStack accepts XLS, XLSX, and CSV uploads (up to 10 MB each). It is a value-and-row comparison, not a visual workbook layout comparison and not a formula auditor.

How to compare Excel files on CompareStack

1. Export or save both workbooks as XLS, XLSX, or CSV.
2. Upload Excel File A (baseline) and Excel File B (revised).
3. Run Compare Excel Files and review the diff table row by row.
4. Investigate added or removed rows and changed cell values highlighted in the output.

Use cases for spreadsheet diffing

Month-end reporting: Compare last month’s finalized export to this month’s draft to see new GL rows or adjusted totals. Inventory and supply chain: Diff SKU lists between warehouse extracts. HR and roster data: Spot new employees or changed departments between CSV exports saved as Excel. Survey and research data: Verify that cleaned datasets match raw exports after ETL.

Values versus formulas

The tool compares extracted cell values as presented in the file. If a cell displays a calculated total, the diff reflects that displayed value—not necessarily the underlying formula text. For logic changes (formula edits without visible value change yet), open the workbook in Excel or agree on a dedicated formula audit process. Teams often compare values for outcome audits and formulas for model reviews.

Preparing files for cleaner diffs

• Export both files from the same template so column order matches.
• Sort by a stable key column (SKU, employee ID) before export when row order is not meaningful.
• Remove decorative sheets or instruction tabs if they add noise.
• Keep file sizes within the upload limit; split very large datasets by logical partition if needed.

Limitations

Charts, pivot tables, macros, and conditional formatting are not compared as visual objects—only extracted textual/numeric cell content. Merged cells may extract unpredictably; unmerge when possible before export. Multiple sheets may be processed; focus your review on the sheet content shown in results.

Worked example: month-end line moves

Lock last month’s board-approved export as Excel File A. Upload this week’s management draft as Excel File B. Scan for new cost-center rows, removed liability lines, and value edits on revenue accounts. Attach the diff summary to your close ticket with who reviewed and which thresholds triggered escalation. Compare the final board pack against the same locked baseline—not only against yesterday’s email— so cumulative edits stay visible.

Close-week operating rhythm

Finance teams improve control when every new export is compared to one locked baseline (draft close), then again before board distribution. Ad hoc comparisons against “whatever was emailed yesterday” miss drift introduced across review week. Write escalation rules in advance: any revenue line change, any new liability row, or headcount total movement beyond an agreed tolerance.

• Name files with date, version, and owner before upload.
• Sort on a stable key (account code, SKU) when row order is meaningless.
• Prefer values-only audits for outcomes; inspect formulas inside Excel when logic may have changed silently.
• Redact employee-level PII when policy requires cloud processing of HR extracts.

Worked example

Each non-empty row is turned into one line, with cells separated by |. Empty cells are shown as ∅. Sheet names are included as [Sheet] … lines for XLS and XLSX.

Baseline row:

Acme | 1200 | open

Revised row:

Acme | 1500 | open

Because the lines are not identical, the diff marks that row as changed. A new customer row that exists only in the revised file is marked added. A row present only in the baseline is marked removed. At most 1,200 data rows are read per worksheet; further rows are replaced with a truncation note.

Security

Spreadsheets may contain sensitive financial or personal data. Upload only when policy allows cloud processing. Session-based handling is described in our Privacy Policy.

Related resources

• PDF Compare for signed report PDFs
• Text Compare for pasted TSV fragments
• Excel Compare for Finance Teams
• Excel Month-End Close Comparison