Why do repeated WooCommerce image imports create extra Media Library entries?

Separate the Two Paths

A WooCommerce product CSV import has two different operations that may look identical in the spreadsheet: downloading an image from a reachable URL, and referencing an image that already exists in the site’s Media Library. Repeating the same text in an image column does not by itself prove that the importer will reuse the previous attachment. The actual result depends on how the importer recognizes identity and how the row is configured.

Use WooCommerce’s built-in importer schema and mapping rather than instructions written for an extension. Begin with an export from the same store and inspect its image-related column, formatting, and product identity fields. Treat that exported structure as the contract for the test.

When an Images cell contains multiple image references, the native schema uses a comma-separated list: enclose the complete CSV cell in double quotes so those commas stay inside one field. The first reference is the featured image. For an update to existing products, select Update existing products and confirm the ID or SKU mapping. Leave unchanged media out of copy-only updates.

Any addresses using reserved example.test or .invalid names in this exercise are non-working illustrative placeholders. Replace them with the actual direct image reference from your controlled test store before attempting an import; the placeholder cannot pass a download test.

1. Export one existing product that already has media and preserve the original export unchanged.
2. Record the product identity value, the image value shown in the exported row, and the current attachment evidence: attachment title, source URL if displayed, and the product’s assigned image.
3. Create a non-destructive test copy containing only that product and its existing image value.
4. Import the copy once, then inspect the product and Media Library before importing it again.

Evidence That Identifies the Cause

After the first test, compare the Media Library count and attachment records rather than relying only on the product thumbnail. A new attachment with the same visible filename can still be a separate record. Useful evidence includes the attachment record ID, the file or source URL shown by the site, upload time, and whether the product points to the original or newly created record.

If the second import creates another attachment while the product still displays correctly, the repeated value is reaching the remote-download path. If no new attachment appears and the existing record remains assigned, that test demonstrates reuse for that exact exported value and mapping. Do not generalize the result to other URL forms, rows, or importer configurations without testing them.

Illustrative exercise

Illustrative exercise: define Asset A as an existing Media Library attachment whose displayed source value is https://store.invalid/images/blue-mug.jpg. Define Asset B as a separate attachment with the same filename but a different attachment record. These are distinct assets even if the product preview looks identical.

For comparison A, import a test row using the exact image value exported from the product, while retaining the exported product identity. For comparison B, import the same row a second time and inspect whether a second record appears. Pass means the product keeps its intended identity, the intended attachment remains assigned, and no additional Media Library record is created. Fail means the attachment count increases, the new record has a different ID, or the product points to Asset B. This is a procedure to run on your store, not a claim that the exercise has been tested.

1. Compare the exported image representation with the value in the CSV you plan to import.
2. Check the importer’s mapping preview for the image column and product identity fields.
3. Run the one-product test twice.
4. Branch on the attachment evidence: continue only when the observed behavior matches your acceptance condition; otherwise revise the image reference strategy and retest.

Scale Only After Acceptance

Once the controlled test passes, preserve the original CSV and make a small batch using the same schema, identity fields, and image representation. Inspect attachment records and product assignments again. If duplicates return, stop scaling: the difference may be URL normalization, mapping, row identity, or another value in the batch.

Keep the original media and product export available while diagnosing. Do not delete Media Library entries to hide the symptom, because that can remove the only known-good attachment or break an existing product assignment.

Scope of the documentation

The official references below support tool behavior and feature boundaries. The test fixture, branching decisions and acceptance criteria are Itemlume editorial recommendations; citation does not imply endorsement. Illustrative sizes, names and timings are not your production specifications.