Review a revised catalogue
Use a product reference as the key to distinguish a changed description from an added or removed item. Check repeated references before interpreting how their versions have been paired.
Analyze two CSV tables side by side, spot additions, removals, or changes, and get a clear report of the differences.
Use a name or 1-based column number. Leave empty to compare complete rows.
Comparing two CSV exports helps distinguish records genuinely added, removed or changed from a simple change in row order. Put the reference version on the left and the version to inspect on the right, then decide whether one column identifies records. The result is a report rather than a merged file, useful for reviewing a delivery, synchronisation or catalogue update. Identity depends on your key. Without a key, changing a field makes the old complete record a removal and the new complete record an addition.
Without a key column, complete records are compared while retaining their occurrence counts. Two copies of one record in the reference and one copy in the new version produce one removal. Record order is not a difference criterion. With a key, associated records are compared field by field and changed positions are reported. Choose an exact heading or a column position starting at 1. When the file has no header, use a position rather than a name.
Repeated keys are not overwritten. The engine first matches identical records within each group, then pairs the remaining versions. Extra occurrences become additions or removals. A change within a repeated-key group is therefore a technical pairing, not proof that the two records represent the same business object. Empty keys are grouped too; use a populated, unique key for a more reliable interpretation. Columns are compared by position, without automatic realignment based on their headings.
The header option starts enabled and excludes the first record from compared data. Surrounding spaces are ignored initially, while case remains significant unless its option is enabled. These rules affect both keys and values. Numbers are not normalised as quantities. Automatic detection lets each input use its own comma, semicolon, tab or vertical-bar delimiter; an explicitly selected delimiter applies to both inputs. Quoted multiline cells use the same shared CSV reader. The text export contains the numerical summary, while individual difference details are displayed separately on the page.
Paste or import the reference on the left and the new version on the right. Confirm delimiters and matching column order. Added and removed are always interpreted relative to that orientation.
Enter a reliable key to follow modifications, or leave it blank to compare complete records. Confirm the header setting and deliberately choose whether surrounding spaces and case should affect the comparison.
Run the comparison, then inspect additions, removals and changed column positions on the page. Export the summary if needed, retaining both source versions so every difference can be reviewed before an update.
Use a product reference as the key to distinguish a changed description from an added or removed item. Check repeated references before interpreting how their versions have been paired.
Compare the previous delivery with the new one using the same column order. Moving a record elsewhere in the file should not be mistaken for changing its contents.
Leave the key blank to detect added or missing complete records, including cases where several identical records occur in one or both versions of the source file.
With id as the key, reference 1 changes, reference 2 is removed and reference 3 is added. No record is unchanged. Without a key, Alice becoming Alicia would not be classified as a modification of the same identity.
Input
id;name
1;Alice
2;Ben
---
id;name
1;Alicia
3;ChloeResult
Added: 1
Removed: 1
Changed: 1
Unchanged: 0Without a key, one identical record is unchanged and the other is removed. A value merely existing on both sides is insufficient: its multiplicity is compared too, without automatically deduplicating either source before comparison.
Input
id;name
1;Alice
1;Alice
---
id;name
1;AliceResult
Added: 0
Removed: 1
Changed: 0
Unchanged: 1No. Matching searches for complete records or their keys independently of their position in the file. Column order must remain compatible, however, because cells are compared by position rather than automatically associated by heading.
Identical records are paired first, then remaining occurrences are paired in their remaining order. Counts are preserved, but such pairing does not prove the records' real identity. A unique key provides a clearer interpretation.
CSV values are compared as strings after the selected space and case options. Comparison does not convert numbers or currencies. Standardise those formats beforehand only when you are certain that doing so preserves their meaning.
It contains the summary counts for added, removed, changed and unchanged records. Individual details appear separately on the page. The tool creates neither an automatically applicable patch nor a file combining both input versions.
Related tools
Tools similar or complementary to this one.
Compare two Excel or CSV files using a key column and spot the differences.
Remove duplicate CSV rows using the columns you choose as matching criteria.
Select the CSV columns you want to keep in the final result.
Learn how to compare two versions of a table using a stable key and distinguish added, removed and modified records.
Understand how to define a reliable duplicate key, distinguish exact and business duplicates, and validate a CSV before and after deduplication.
Discover when to split a large table by row count or by a column value, and how to preserve a useful structure in every output file.
Learn how tabular data is structured, how CSV, Excel, JSON and TSV differ, and how to choose the right format before cleaning, converting or automating a workflow.