How is this different from CSV Differ?

CSV Comparator gives a structured, cell-level data summary (row counts, added/removed rows, exact cell coordinates that differ). CSV Differ instead gives a line-level unified-diff-style text view (- and + prefixed lines), like the Unix diff -u command, of the raw CSV text.

How are 'added' and 'removed' rows determined?

By exact full-row content match, not by row position. A row counts as removed from A if no row with identical cell content exists anywhere in B, and vice versa for added rows in B.

What happens if the two files have different row or column counts?

Both grids are padded to a rectangle first (missing trailing cells become empty strings), and cell-level comparison only covers the row/column range the two files have in common; the row-count and column-count difference is reported separately.

Does row order matter for cell-level differences?

Yes, cell-level differences are aligned strictly by index, so if a row was inserted or removed, every row after it will show as entirely different even though its content just shifted position.

CSV Comparator - Compare Two CSVs Cell by Cell

Overview

Introduction

Spotting what changed between two versions of a CSV export by eye is error-prone once you're past a handful of rows. This tool compares two CSVs and reports exactly which rows and cells differ, structured as data rather than as a wall of diff text.

It's the tool to reach for when you need to know precisely which coordinates changed, not just that two files aren't identical.

What Is CSV Comparator?

A structured, cell-by-cell CSV comparator: it parses both inputs, pads each to a rectangular grid, and reports a row-count difference, full rows unique to each side, and index-aligned cell-level differences within rows both files share.

It complements CSV Differ, which instead shows a line-level unified-diff view of the raw text.

How CSV Comparator Works

Each input is parsed with the shared RFC 4180-aware CSV grid parser, then padded so every row has the same number of columns. Row uniqueness is computed with an exact full-row content match (order-independent, using a multiset comparison) to find rows present in one file but not the other.

For the rows and columns both files have in common, indices are compared directly, cell by cell, and every mismatch is reported with its (row, column) coordinate and both values.

When To Use CSV Comparator

Use it to audit exactly what changed between two exports of the same dataset, cell by cell.

It's also useful for verifying that a data pipeline transformation only changed the fields it was supposed to.

Often used alongside CSV Differ, CSV File Merger and CSV Data Finder.

Features

Advantages

Reports exact (row, column) coordinates for every differing cell, not just that a difference exists somewhere.
Distinguishes rows that were added or removed entirely from cells that merely changed value.
Runs entirely client-side, so neither CSV ever leaves your browser.

Limitations

Cell-level comparison is index-aligned, so a single inserted or deleted row shifts every subsequent row's comparison out of sync.
Very large CSVs (tens of thousands of rows) may be slow, since row-uniqueness detection is a full-row content comparison.

Examples

Comparing two small CSVs

Input

CSV A:
id,name
1,Ada
2,Alan

CSV B:
id,name
1,Ada
2,Al

Output

Row count difference (A - B): 0
...
Cell-level differences ... (1):
  row 1, column 1: "Alan" -> "Al"

Row 0 matches exactly on both sides; row 1's "name" cell differs, and that exact coordinate is reported.

Best Practices & Notes

Best Practices

If rows might have been inserted or reordered, sort both CSVs by a stable key column before comparing, so cell-level alignment stays meaningful.
Use the added/removed row summary first to understand structural changes before drilling into cell-level differences.
Pair with CSV Differ when you also want to see the change in the context of the raw file layout.

Developer Notes

Row uniqueness uses a multiset (a Map from JSON.stringify(row) to a running count) rather than a Set, so duplicate rows are matched up correctly instead of one duplicate silently absorbing another file's distinct row.

CSV Comparator Use Cases

Auditing exactly what changed between two versions of an exported dataset
Verifying a data transformation pipeline only touched the fields it should have
Reviewing a colleague's manual edits to a shared CSV before merging them

Common Mistakes

Comparing two CSVs that have been re-sorted differently and expecting cell-level differences to reflect content changes rather than row-order shifts.
Ignoring the row-count difference summary and only looking at cell-level output, which only covers rows both files have in common.

Tips

Sort both files by a unique ID column first if you only care about value changes, not row order.
Check the added/removed row counts before assuming every reported cell difference reflects an intentional edit.

CSV Comparator