The problem with product images at scale
WooCommerce attaches images to products one product at a time. You open the product, click Set product image, pick a file from the Media Library, then do the same for the gallery, then for each variation. For a shop with thirty products that is an afternoon. For a catalogue of two thousand SKUs that arrived from a supplier as a folder of photos, it is weeks of clicking, and the photos were already named correctly before anyone started.
The CSV importer does not solve it either. It accepts image URLs, so the files must already be online somewhere, and it cannot tell a featured image from a gallery image without a column per role. The Media Library can bulk-upload files, but it has no idea which product a file belongs to.
The fix is to let the filename carry the information. If a photo is called NIKE-AIRMAX_M00.jpg, a tool can read the SKU NIKE-AIRMAX, see the suffix _M00 and know it is the main image of that product. Bulk upload then becomes: name the files, drop them in, check the preview, confirm.
A filename convention that assigns itself
The convention used by Product Image Manager, ProCom’s extension on the WooCommerce Marketplace, is the product identifier followed by a role suffix. The identifier is normally the SKU, because the SKU already exists in your spreadsheet, your supplier’s photo folder and WooCommerce.
| Filename | Assigned as | Matched by |
|---|---|---|
NIKE-AIRMAX_M00.jpg | Featured (main) image of the product with SKU NIKE-AIRMAX | SKU |
NIKE-AIRMAX_G01.jpg | First gallery image | SKU |
NIKE-AIRMAX_G02.jpg | Second gallery image, and so on | SKU |
NIKE-AIRMAX_R001.jpg | First frame of a 360° spin | SKU |
NIKE-AIRMAX-42_M00.jpg | Featured image of the variation with SKU NIKE-AIRMAX-42 | Variation SKU |
classic-tee-navy-blue.jpg | Every variation of the product whose colour is Navy Blue | Attribute |
The default patterns cover SKU-based names like these, but the rules are configurable. You can match on SKU, variation SKU, product ID, slug, product name, a custom field, a regular expression for a naming scheme you already have, or fuzzy similarity for names that nearly match. Each match receives a confidence score, and you set the threshold below which an image goes to review instead of being assigned.
Importing step by step
Upload a ZIP or a folder of files
In WordPress, drag in a ZIP archive or select hundreds of files at once. Uploads travel in small chunks, so a large selection does not hit PHP’s
max_file_uploadsorpost_max_sizelimits, and an interrupted upload resumes rather than restarting. Extraction and validation run in the background, so nothing times out, even on shared hosting. Agencies can also import from a folder that is already on the server.Run a Dry Run
Dry Run processes the whole batch without writing to products or the Media Library. You see every proposed match: file, product, role (featured, gallery position or 360° frame) and confidence. This is where you spot a wrong rule or a typo in a SKU before it touches two thousand products.
Clear the Manual Review Queue
Anything below your confidence threshold waits in the Manual Review Queue with the three closest products suggested, its score and a search box. Assign each image with one click or mark it as no match. Typically this is a handful of files out of hundreds.
Commit and let it run
Run the import for real. Assignment happens through Action Scheduler with a time budget per run, so progress is steady even where loopback cron is unreliable. Each image is claimed atomically, so two workers never import the same file twice. From the Batches & Logs screen you can pause, resume, retry or cancel, and a batch is marked Completed only when every image has reached a final state.
Check, and revert if needed
Open a few products to confirm featured and gallery images are in the right order. If something is wrong, Batch Revert restores the previous images of every product the batch touched, and Revert & Delete Media also removes the attachments the import created, so a mistaken run leaves nothing behind.
Variable products: by SKU or by colour
Variations are where manual image work hurts most, because a product with six colours in five sizes has thirty variations and usually only six distinct photos. There are two ways to handle it.
By variation SKU. Name a file with the variation’s SKU and it becomes that variation’s own image. This is exact and suits catalogues where every variation really does look different.
By attribute. Switch on attribute matching and a file named classic-tee-navy-blue.jpg is matched to the product’s own colour attribute and set on every variation that shares that colour, so one photo covers all sizes of Navy Blue. Use the {COLOUR}, {COLOR} or {ATTRIBUTE} placeholder in your filename rule, or let the plugin detect the colour from the product’s attribute terms. The longest match wins, so “Navy Blue” beats “Blue”.
If you also show variations as separate products in your shop, this step matters twice: each variation card displays its own image, so a missing variation image is a blank card.
Optimisation, duplicates and automation
- Optimise on the way in. Resize to a maximum dimension while keeping the aspect ratio, compress at a quality you choose and convert to WebP where the server supports it. Offload plugins are respected.
- Generate SEO metadata. Rename files with a template built from product data and fill ALT text, title, caption and description automatically, so every image is indexable from day one instead of being called
IMG_4821.jpgforever. - Let duplicate detection work. The plugin spots images already in the library by content hash or by filename and size, and lets you skip, replace, merge or send them to review. Re-running an import never litters the Media Library.
- Automate recurring imports. A REST API under
pimw/v1and WP-CLI commands (wp pimw import,status,retry,revert) support scheduled imports from a supplier feed. Email and webhook notifications report when a batch completes or fails, and a reports dashboard exports results to CSV. - Background removal is optional. An integration with PhotoRoom can remove backgrounds during import. It is off by default, uses your own PhotoRoom API key and shows the estimated cost before a batch runs. Nothing else leaves your server.
- Multilingual stores are covered. WPML and Polylang translation image sync keeps translated products in step, and activation is multisite-aware.
With a sensible naming convention and a dry run, the two-thousand-product problem turns into one upload, a short review and a background job. Assignment is HPOS-safe and goes through the WooCommerce product CRUD, so other plugins see the images exactly as if you had set them by hand.
// Next step
Do this with Product Image Manager
Bulk-assign featured, gallery and 360° images to products by matching file names. Sold on the official WooCommerce Marketplace with a 30-day money-back guarantee, updates and support from the ProCom engineers who build it.