Why does my WooCommerce CSV import keep only the first product image?

Start With the Native Format

The built-in WooCommerce importer uses a comma-separated list in the Images cell. Enclose that entire cell in double quotes when saving the CSV so its internal commas do not create extra columns. An extension may use different conventions; do not copy a pipe-separated extension example into the native field. Export one product that already has a featured image and a gallery image, and use that row as a local comparison.

Inspect the exported header, the exact Images cell, and the image order. Also inspect the importer’s mapping screen before completing an import. The image column must be mapped to the native image field, rather than to a custom attribute, description field, or an unmapped column. Preserve the product identifier and the original export while preparing the test file.

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.

1. Create a non-destructive test copy containing one existing product row and one new test product row.
2. Copy the exported image-field structure into the test row, changing only the image values needed for the test.
3. Open the native WooCommerce importer, select the test CSV, and verify the image column’s mapping before starting.
4. Run the test import, then open the resulting product and inspect both the featured image and the product gallery.

Use Reachable Image Evidence

Every image URL in the native image field must be reachable by the importer. Inspect the URLs independently in a browser or with the same access path used by your store. Look for redirects, authentication requirements, blocked hosts, malformed separators, and URLs that return something other than the intended image. A URL that works only inside your own logged-in session is not reliable evidence for an importer.

The first listed image is designated as the featured image; verify all referenced files can be imported. Later valid images should remain gallery candidates. If the first image appears but later images do not, compare the raw exported cell with your submitted cell character by character: the likely evidence is a formatting, mapping, or reachability difference rather than a featured-image rule.

Branch Before the Full Import

If the exported sample and your test row produce the same gallery structure, proceed in small batches while retaining the original CSV and product identity fields. If the sample imports multiple images but your test row does not, stop expanding the import: the next action is to repair the image-cell syntax or mapping, not to change unrelated product data.

If an existing product is being updated, confirm that the row matches the intended product identity. A row that does not match the existing product may create or target a different product, making the media result difficult to interpret. Keep the test product clearly identifiable and inspect the final product record rather than relying only on an import status message.

Illustrative exercise

This is an illustrative fixture, not a report of a completed test. Suppose the exported native sample shows product “Cedar Mug” with image values “cedar-front.jpg” followed by “cedar-handle.jpg”. A test copy uses product “Cedar Mug Import Check” with two reachable, distinct values: “blue-front.jpg” and “blue-handle.jpg”, arranged in the same native field structure.

Pass means the test product has blue-front.jpg as its featured image and blue-handle.jpg in its gallery, with the intended product identity preserved. Fail means only blue-front.jpg appears, the second value is ignored, or the wrong product is updated. On failure, compare the two raw image cells and the mapping screen, then test the second URL separately before editing the larger file.

Acceptance Condition

Accept the CSV only when the non-destructive test creates or updates the intended WooCommerce product, the intended first listed image is featured, every additional intended image appears in the gallery, and the result matches the exported native sample’s structure. If any one of those conditions fails, keep the full import paused and preserve the evidence: source row, mapped field, raw image cell, URL checks, and resulting product media.

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.