Duplicate Records Across Files

Find matching keys across two CSV files and optionally review both source rows side by side.

On-device No sign-up Free to use

Find matching records controls

  1. 1 Add files
  2. 2 Arrange/Options
  3. 3 Download

Drop your CSV files here

or choose them from your device

Exactly two UTF-8 CSV files, up to 2 MiB each, 10,000 combined data rows and 50 columns per file. Each file needs distinct column names.

    ?

    Comma-separated column names present in both files. Names containing commas can be quoted, as in CSV.

    ?

    One key column only. One Unicode code point insertion, deletion or substitution after the chosen normalization, not a full grapheme comparison. Keys up to 80 code points; 120,000 signatures, 20,000 candidate checks and 5,000 total pairs. No automatic merging.

    ?

    Adds the original values from both files to the matching-pairs report. This does not merge records; export is limited to 8 MiB.

    Result

    Showing an example.

    Two CSV tables with key values 001, 002 and 002, 003 respectively.

    Found 1 cross-file row pairs using id. Sample rows: 3 | 2 | Exact selected-key match | 002 | 002.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/duplicate-records-across-files · 20 November 2026

    Was this helpful?

    How to use Duplicate Records Across Files

    1. Choose two UTF-8 CSV files and use their order controls to set file A followed by file B.
    2. Enter key-column names present in both files, then choose whether to trim surrounding spaces or ignore letter case.
    3. Optionally include original source rows side by side. Near-candidate review supports one key column and one code-point edit; treat those pairs as suggestions.
    4. Inspect exact-key pairs separately from near candidates, then download the CSV or JSON review. No source records are merged or deleted.

    Example: Duplicate Records Across Files

    Two CSV tables with key values 001, 002 and 002, 003 respectively.

    You add
    Two CSV files: a.csv contains id,name with 001,Ana and 002,Lee; b.csv contains 002,Sam and 003,Mia. Key columns: id Trim surrounding whitespace in keys: on Ignore letter case in keys: off Also list near candidates for manual review: off
    You get
    Found 1 cross-file row pairs using id. Sample rows: 3 | 2 | Exact selected-key match | 002 | 002.

    Options

    Key columns
    Comma-separated column names present in both files. Names containing commas can be quoted, as in CSV.
    Also list near candidates for manual review
    One key column only. One Unicode code point insertion, deletion or substitution after the chosen normalization, not a full grapheme comparison. Keys up to 80 code points; 120,000 signatures, 20,000 candidate checks and 5,000 total pairs. No automatic merging.
    Show both source rows side by side
    Adds the original values from both files to the matching-pairs report. This does not merge records; export is limited to 8 MiB.

    Supported inputs and limits

    • Two UTF-8 CSV files, 2 MiB each, 10,000 combined rows and 50 columns per file.
    • Up to 5,000 matching pairs.
    • Near candidates support one key column, one Unicode code point edit and bounded signature/comparison counts; they are never merged.
    • Optional full source values use an 8 MiB CSV bound.
    • Preview shows 100 pairs while exports contain every accepted pair.
    More details

    Selected-key equality does not prove all source values agree.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    A pair is evidence for review, not a merge instruction

    Row numbers count the header as row 1. Two matching keys can have different names, addresses or other data, and repeated keys can produce several row pairs. Open both original rows and compare the fields that matter to your task. The exported match list leaves the source files unchanged; its formula guard also means a spreadsheet cell may display an added apostrophe.

    Questions about Duplicate Records Across Files

    Will matching records be merged?

    No. The output identifies pairs for your review.

    Is a near match a confirmed duplicate?

    No. Similar text can describe different records; inspect the selected fields and original data.

    Why are leading zeros preserved?

    CSV key fields are compared as text so identifiers such as 001 keep their entered form.

    Page updated · Project managed by Tony Hines · Report a problem with Duplicate Records Across Files