Questions about
Spreadsheet Comparison

CSV, XLS, XLSX, Numbers and ODS are supported. For a workbook, choose the worksheet you want to compare. Each side loads one sheet; the app does not compare every tab, chart, style or macro in an entire workbook.

You can compare a selected workbook sheet with a CSV file. See the Excel comparison guide for preparation steps.

Excel import has technical limits that remain after purchase: a 64 MB workbook, and a selected worksheet range of at most 250,000 rows, 10,000 columns and 5 million cells. The cell limit applies to the declared rectangular range, including empty cells inside it. These are Excel import limits, not CSV row limits.

Cached Excel formula results are read from the saved workbook and are not recalculated. Recalculate and save in the source spreadsheet application when current formula results matter.

A sheet with formatting far beyond its visible data can declare a large range. If import rejects it, create a clean data-only worksheet or export the required records as CSV. Keep the original workbook unchanged.

No. It reads cached results saved in the workbook. Open the file in the spreadsheet application that owns the formulas, recalculate and save before importing if those results need refreshing. Formula expressions and workbook logic are not compared for equivalence.

The app requires macOS 14 or later. The release is built for Apple silicon and Intel Macs. Check the download page for public release availability and installation notes.

Choose the mapped field or fields that identify a record. The comparison uses that key to find counterparts instead of assuming that records occupy the same row number. Read how to choose a stable key.

Yes. Review suggested mappings, then connect the columns that have the same meaning. Header similarity and overlapping values can help suggest a match, but they do not prove that two business fields are equivalent. Units, scope and definitions still need your review.

Your selected key does not uniquely identify every row, or some identifiers are missing. A repeated order ID can be valid when rows represent separate order lines. Add a stable line ID to the key when appropriate. Do not add the value you are trying to detect changes in simply to make the key unique.

Ambiguous groups require inspection; a proposed pairing is not proof of record history. The duplicate-key guide explains this with examples.

Supported JSON object cells expose flattened fields that can map to scalar columns. For example, a billing-address city can map to Billing City. This is not a general standalone JSON import or schema-validation feature. Read the JSON address guide for sparse fields and nested structures.

Compare up to 5,000 data rows per file, excluding the header, for ten successful comparisons in the free trial. The trial includes the normal mapping, key selection, result filtering, row inspection and export workflow.

Failed and cancelled comparisons do not count. Filtering or searching an existing result and exporting a report do not count. Running another comparison that finishes successfully does.

It removes the commercial row and comparison-count limits. The technical Excel import limits above remain, and file handling still depends on available resources. See pricing for the full distinction and current purchase availability.

After purchasing, open Lifetime license… from the app menu, paste the complete signed license and choose Activate license. Verification takes place locally. Keep the license for your own records.

If activation fails, check that you have the latest app and copied the whole license. See license troubleshooting for help.

No input files are uploaded for comparison. Import and comparison run on your Mac without a remote AI service. This site’s interactive example uses synthetic records bundled with the page. There is no website upload form.

See privacy for the distinction between local file processing and ordinary website requests.

Start with the troubleshooting page. Record the app version, macOS version, file format, selected key and exact error. If a reproducible example is needed, create a small synthetic file that preserves the problematic structure without real customer data.