Why WooCommerce CSV product images are not importing

1. Confirm whether the product or only the image failed

Open the imported product and check the import log. If the product exists without an image, focus on the Images field and the remote file. If the entire row was skipped, resolve its SKU, required values, or CSV structure first.

2. Use the Images column as WooCommerce expects

The first entry in the Images field becomes the featured image. Additional entries become gallery images. Multiple images are separated with commas, so confirm that one misplaced delimiter has not shifted the remaining product fields into the wrong columns.

3. Give WooCommerce a directly accessible image URL

External images need a complete http:// or https://URL that the store can fetch without signing in. A cloud-storage sharing page, expiring preview URL, anti-hotlink response, or redirect script can prevent the importer from downloading the file even when the address opens in your browser.

4. Test the URL outside your signed-in browser

Open the address in a private window. It should return the image itself rather than an HTML page, permission request, or download landing screen. If it does not, host the image at a stable public URL or upload it to the WordPress Media Library before importing.

5. Reference existing Media Library files carefully

WooCommerce can use a filename when the image already exists in the Media Library. Match the stored filename exactly. If multiple files share similar names, verify the result on a small test product before importing the catalog.

6. Check delimiters, quotes, and shifted rows

A malformed image field can make the importer read too many columns. Compare the number of fields in the failed row with the header, and check quotation marks around values containing separators. Save the repaired file as UTF-8 CSV rather than renaming a spreadsheet workbook.

7. Know what the FeedFixer scan can prove

FeedFixer flags suspicious image URL formats and row-width problems locally. It does not contact remote image servers, so it cannot prove that a URL is public, permanent, or free of redirects. Use the scan to rule out file problems, then test remote accessibility separately.

8. Retry one product before the full catalog

Back up the store or use staging, then import one product with one image. Confirm the featured image and gallery behavior before retrying a large batch. This separates a single bad URL from a catalog-wide CSV formatting problem.