If product images are missing after a WooCommerce import, start with one affected product and one image. Check that the source supplies a downloadable image, that the importer reads the intended value, and that the resulting attachment is assigned to the correct product or variation. Retry that small case before sending the whole catalogue through again.
Keep the CSV and import report from the failed run. Note the product identifier and exact image reference. A missing picture, a wrong-colour picture and a blurry picture point to different stages of the process.
Find the stage where the picture goes missing
Open the affected product in the editor and inspect its assigned image and gallery. Then search the Media Library for the intended file. You are trying to distinguish three situations:
- The file never reached the Media Library: investigate the source, download and import mapping.
- The file exists, but the product uses no image or the wrong attachment: investigate record matching and assignment.
- The correct attachment is assigned, but the storefront looks wrong: investigate the selected variation, generated image size, template or cache.
Record which situation you actually found. Replacing all image URLs is unlikely to help if the correct files are already present and only their product assignment is wrong.
Check the source without relying on your signed-in browser
A supplier’s sharing page may display an image to you while returning a login screen or a web page to the shop’s server. A page containing a photograph is different from a direct image download. Ask for the intended downloadable file route or a permitted copy of the image.
WooCommerce’s core CSV documentation says imported images must already be uploaded or available for the store to download. It specifically notes that remote hosts can require authorisation, block requests or return a page instead of an image.
Try the source in a browser session without the supplier login. That is a useful preliminary check, but a successful browser view does not prove that the WordPress server can retrieve it. If the import still fails, give the host or developer the clean source URL and the relevant error so they can check the server-side request.
Do not publish private access tokens in a CSV shared for support. If the supplier’s download requires authentication, agree a supported secure transfer process. Where you have permission to use the file, uploading a small sample to your own Media Library can help separate a remote-download problem from a product-assignment problem.
Confirm the importer and image-column format
Write down the importer’s exact name and version. WooCommerce’s built-in CSV tool and similarly named extensions have different instructions. A gallery separator copied from the wrong plugin guide can make a sensible-looking cell fail to represent the intended images.
Compare the working file with a fresh export or documented example from the tool actually being used. Inspect the saved CSV as well as the spreadsheet. Check that quotation marks, separators and line breaks have not split the image reference across columns.
On the mapping screen, confirm that the image column is assigned to the intended destination. Keep unrelated fields outside the test. A single-product file makes it easier to see whether changing the source or mapping resolved the failure.
The broader CSV import checklist covers file preparation, matching and reconciliation. Use it when other product fields are also arriving incorrectly.
Check the file and attachment that actually arrived
Open the imported attachment and compare it with the intended source. Confirm the subject, colour and contents of the set. Similar supplier filenames can hide different products or views. Check the file itself before assuming that the thumbnail beside its name is sufficient identification.
If you are referring to an existing Media Library file, check the filename and the result for one record. Avoid creating another copy merely to make the name look right. Repeated full imports can leave you with several similar attachments and no clear record of which one the product uses.
For a failed upload, retain the actual error and inspect the prepared file. Check that it is a supported image format, has not been damaged and falls within the upload limits shown by the installation. Rename neither its extension nor its contents as a shortcut to format conversion.
If every remote image fails but a permitted local sample uploads normally, investigate the remote retrieval route. If a particular file fails by both routes, investigate that file.
Match the image to the product and selected option
Use the product identifier to confirm where the import wrote its changes. A matching title is not enough when the catalogue contains similar models or different pack sizes. Check the actual main-image and gallery assignments on that record.
For a variable product, select the relevant option in the storefront. A correct parent photograph does not establish that each colour has the intended variation image. Check a second option too, so you can see whether the photograph changes as expected.
Inspect gallery order deliberately. Put the identifying view first, then useful details such as the back, fastening or supplied components. Retain your own approved photography if the job was only intended to update stock. The catalogue update-method guide explains how to keep fields with different owners outside an update.
Handle alt text as a separate acceptance check
The core WooCommerce CSV importer does not add or update product-image alt text. Include a separate image-description step instead of assuming an image import has completed it.
Describe the information that matters in the view: “Blue ceramic mug, side view showing the handle” identifies more than “mug image”. Keep decorative props out of the description unless they affect what the photograph communicates.
Check the saved product page’s image description in context. WordPress’s image guidance distinguishes a Media Library default from text set on an individual block. Product galleries and page builders can render images differently, so do not assume that editing a library field updates every existing use.
When the image is present but looks wrong
If the correct photograph is assigned and visible but looks soft or cropped, stop changing the import. Compare the original, uploaded attachment and displayed view. The existing WooCommerce image-size and sharpness guide covers source dimensions, composition, compression and generated sizes.
For an old picture that remains after the assignment has changed, compare a fresh customer-facing view with the editor. Use the site’s supported cache-refresh process if appropriate. Keep the source files and attachments while investigating; deleting an image can affect other places that use it.
Retest one complete product before the batch
Run the corrected sample and retain its report. Inspect the image and gallery in the product editor, then open the customer-facing page on desktop and phone. Select relevant variations and check the identifying view, details, enlargement and image descriptions.
Also confirm that the test left descriptions, stock and other fields outside its scope intact. Once the sample behaves as intended, process a controlled batch and inspect representative results. Keep the file version and the change that resolved the fault for the next import.
If the same controlled case still fails, describe the WooCommerce problem and share your shop URL. For projects in Formby, Freshfield and L37, a product link, importer name, clean source-image URL and error wording help scope the work. Do not send credentials or customer data.
