Key-aware matching
Match by a detected header or by row position when order matters.
| Status | Key | Changed fields | Before | After |
|---|
Basics
A structured CSV diff compares records and fields rather than raw text. Key matching keeps the same record aligned when rows are reordered.
The result separates added, removed, changed, unchanged, and duplicate-key records.
What it does
Paste or open two files, choose a key such as id, email, or SKU, normalize harmless formatting differences, and filter a field-level audit table.
Match by a detected header or by row position when order matters.
Optionally ignore case, surrounding whitespace, and null-like placeholders.
See changed fields with before and after values plus source row numbers.
Download the filtered or full difference report as CSV.
How to use
Paste the original and updated CSV, open two files, or load the comparison sample.
Select a unique key; use row position only when both files share the same ordering.
Review duplicate-key warnings and counts for every result status.
Inspect only changed, added, or removed rows, then copy or download the report.
Errors & limits
Repeated identifiers are isolated instead of silently overwriting one another.
Fields missing from one file appear as changes; align header names before comparing when they mean the same thing.
Use the case, whitespace, and null controls deliberately; they change what counts as equal.
A key must be stable and unique. Duplicate or missing keys are reported separately because matching them automatically could hide or invent changes.
FAQ
Yes. Choose a stable key column and row order will not create false changes.
Use a unique, stable field such as id, UUID, email, or SKU. The tool suggests likely keys.
Yes. Position mode compares row 1 with row 1, row 2 with row 2, and so on.
No. Both datasets and the diff stay in your browser.