Why does a WooCommerce import accept a product row but fail to download its image?

Separate row success from image success

Treat the product record and its media as two results. A created or updated product does not prove that its image was downloaded. WooCommerce’s built-in Product CSV Importer and Exporter has its own schema and mapping, so use its exported sample rows as the reference rather than instructions for a separate import extension.

The importer needs an image URL it can reach. A link that opens a gallery, preview, or login-gated page in your browser may not expose the image file to a server-side fetch. A URL that works only while your browser has a session may also fail when the importer requests it.

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.

Inspect the evidence before editing

1. Export a sample using WooCommerce’s built-in exporter and compare its column names and image-cell format with the row you are importing.
2. Read the import result and logs, and record the exact failing image URL. Preserve the original CSV and product identity; test with a duplicate row or a small separate fixture instead of modifying a large import.
3. Open the URL without relying on a logged-in browser session. Determine whether it serves the image itself or a viewer page, and whether it remains accessible when requested without your session. If you cannot establish that from the available evidence, treat the URL as unverified rather than assuming it is a direct file.

Choose the next test from the failure

If the logged URL resolves to a viewer page, replace it in the test copy with the actual downloadable image-file URL from the asset source, then rerun the small import. Do not substitute a page URL merely because clicking it displays the image.

If it is already a direct-file URL, check whether the same URL is still reachable without a session and whether the log identifies that exact URL. If access is session-bound, use an image location that the importer can reach without that browser session. If it appears publicly reachable but still fails, preserve the URL and log details and investigate the reported fetch failure before changing product mapping or unrelated settings.

Illustrative exercise: isolate the URL

Illustrative exercise only: create a non-production test copy for a fictional product named “Cedar Desk Lamp.” Define Asset A as https://assets.example.test/cedar-preview, a fictional viewer-page URL that displays the lamp image. Define Asset B as https://assets.example.test/cedar-main.jpg, a fictional direct-file URL intended to serve that image without a session. These names and addresses are illustrative, not tested endpoints.

Put each value in the image field of an otherwise identical test row, keeping the product identity and other fields unchanged. Import the rows as separate test cases so the result shows whether the URL form is the difference. The first image in the importer’s image list is treated as the featured image, so keep each test row to one image if the goal is only to isolate fetching.

1. Pass: the test product is imported and its image is present in the product’s media; the logged URL corresponds to Asset B.
2. Fail: the row imports but no image is attached, or the log shows a fetch error for Asset B. Record the exact failure and stop treating a browser preview as proof that the importer can download it.

Accept only a verified image result

Accept the change when a small test import completes, the intended image is attached to the correct test product, and the log no longer reports a fetch failure for that image URL. Confirm the first-image ordering if the image is meant to be featured. If the direct-file test still fails, do not scale the same CSV across products: retain the originals, check the recorded URL and error, and resolve access or URL behavior first.

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.