How to Bulk Download Images for E-commerce Catalogs

Every shop launch, platform migration, or marketplace expansion starts the same way: someone has to collect hundreds of product images, one by one, from supplier sites, brand portals, or their own legacy storefront. It is tedious, error-prone, and almost entirely unnecessary. With the right browser tool and a simple naming convention, you can pull a full image set, organized and ready for import, in the time it used to take to download the first twenty files.

The Hidden Time Tax on Every Catalog Build

Catalog image collection is one of those tasks that looks small on a project plan and turns into a two-day slog. You are working through a supplier's product pages, clicking each image to open the full-resolution version, right-clicking to save, remembering (or forgetting) to use a meaningful filename, and then doing it again for the next 400 SKUs.

The same problem shows up in three common scenarios:

• New store launch: You have supplier image libraries spread across brand portals and product detail pages, and you need one clean local folder before you can start your import CSV.
• Platform migration: Moving from Shopify to WooCommerce (or vice versa) means re-exporting every product image in a format and folder structure the destination platform understands.
• Marketplace expansion: Amazon, Google Merchant Center, and Faire each have their own image dimension and format requirements, so you often need to re-pull images in a specific size range from your existing catalog.

In every case, the bottleneck is the same: no efficient way to grab images in bulk, at the right resolution, with usable filenames, from a standard web browser.

If you have already read about downloading every image from a page, you know the core technique. This post goes deeper on the catalog-specific workflow: dimension filtering, SKU-based naming, format normalization, and deduplication across variant pages.

What a Clean Catalog Image Set Actually Requires

Before grabbing a single file, it helps to define what "done" looks like for your catalog. Most platforms and marketplaces share four requirements, and planning for them upfront saves a second round of cleanup.

Consistent dimensions

Amazon requires at least 1000px on the longest side. Google Merchant Center rejects images smaller than 100x100px (and recommends 800x800px or larger). Shopify and WooCommerce will accept anything, but inconsistent product grids look unprofessional and slow down page loads when image sizes vary wildly. A minimum width filter applied during download is the easiest way to enforce a baseline.

Predictable, SKU-tied filenames

A file named IMG_3847.jpg is useless once it is sitting in a folder with 600 others. A file named blue-widget-SKU1042-800x800.jpg maps directly to a row in your product CSV. Filenames should encode at minimum the product identifier and ideally the dimensions so you can spot off-spec files at a glance.

The right format for the platform

JPEG is the safe default for most platforms. WebP delivers smaller file sizes, but not every import tool or older marketplace feed parser handles it correctly. AVIF is even less supported at the catalog-import layer. Knowing your target platform's accepted formats before you download lets you skip a conversion step later.

No duplicates

Product variants (color, size, material) often share the same hero image. If your supplier pages list six color variants of the same jacket, you may end up with six copies of identical files, each named differently. Duplicates inflate your storage, slow imports, and create confusion during the CSV-to-image mapping step.

The Bulk Image Downloader Workflow for Product Pages

Bulk Image Downloader is a free Manifest V3 Chrome extension that scans the active page for every image source, including standard img tags, srcset and picture elements, CSS backgrounds, and data URIs. That matters for product pages because hero images are frequently loaded as CSS backgrounds or responsive srcset sets rather than plain img tags.

Here is the step-by-step workflow for a catalog build:

• Open a supplier product page and click the BID icon in your toolbar. The preview gallery loads every image the extension detected, including thumbnails, icons, and the full-res product shots you actually want.
• Apply dimension filters. Set a minimum width of 800px (or whatever your platform requires). This instantly filters out navigation icons, small thumbnails, and decorative graphics, leaving only the product-grade images.
• Set a filename pattern. BID supports tokens including page title, hostname, image dimensions, and a sequential index. For catalog work, a pattern like {title}-{width}x{height}-{index} gives you a human-readable name. If your supplier page titles include the product name or SKU (most do), this gets you 80% of the way to a usable filename automatically.
• Filter by file type if needed. Select JPG only if your platform does not accept WebP, or leave all types selected and normalize later.
• Download as ZIP. BID packages all selected images into a single ZIP, so you get one tidy download per page rather than dozens of individual browser save dialogs.

The free tier covers 25 downloads per day, which is enough for targeted work on specific product pages. For a migration involving hundreds of pages, the Pro tier (included in the $9/mo Peak Productivity bundle) removes that cap and unlocks the duplicate-skip feature described below.

You can also learn about 5 ways to download all images from a webpage if you want to compare approaches before committing to a tool.

Organizing Downloaded Images for Platform Import

Downloaded images are raw material. Turning them into an importable catalog requires a light organization step that most operators skip and then regret when the import fails.

Folder structure

Keep one folder per product (or per supplier, for a first-pass collection). A flat folder with 600 mixed-product images is nearly impossible to reconcile against a product CSV. A structure like images/SKU1042/ and images/SKU1043/ makes the mapping obvious.

If you are using BID's sequential index token in filenames, images already arrive numbered. Move them into product subfolders as you go, or batch-rename with a tool like PowerToys Rename (Windows) or the Finder rename feature (Mac) using the SKU as a prefix.

Building the image-to-CSV map

Most platform importers (Shopify, WooCommerce, BigCommerce, Faire) accept a CSV where one column holds the image filename or URL. Your job is to make sure every row in that CSV has a filename that matches an actual file in your image folder.

A simple spreadsheet workflow: column A is SKU, column B is the expected filename pattern. If filenames follow a consistent pattern from BID's tokens, you can write a formula to generate column B automatically from column A rather than typing every name manually.

Format conversion

If your downloaded set contains a mix of JPG and WebP and your platform needs JPG only, batch-convert before import. The WebP to JPG/PNG Converter extension handles this in-browser for smaller batches. For bulk conversion, ImageMagick on the command line (mogrify -format jpg *.webp) processes an entire folder in seconds.

Common Pitfalls and How to Avoid Them

Even with a solid workflow, catalog image collection has a few recurring failure modes. Knowing them in advance saves the rework.

Inconsistent resolutions across the catalog

Supplier pages are not designed with your catalog in mind. Hero images for one product line might be 1200x1200px while another supplier uses 600x400px. Set a minimum dimension filter in BID and reject anything that does not meet it. Better to flag a gap in your image set during collection than to discover it after import when your product grid looks broken.

Duplicate images across variant pages

If a product has six color variants, each on its own page, the shared hero image (the studio shot that does not change between colors) gets downloaded six times with slightly different filenames. The Pro duplicate-skip feature in Bulk Image Downloader detects identical image content across your session and skips files it has already captured, even if the URL or filename differs. Without this, deduplication is a manual sort-by-file-size exercise that takes longer than it sounds.

Downloading thumbnails instead of source images

Many product pages lazy-load a small placeholder and only fetch the full image on click or scroll. BID catches srcset candidates and higher-resolution data-src attributes, but you should still scroll the full page before opening the gallery so every lazy-loaded image has a chance to register in the DOM. A quick scroll-to-bottom before clicking the extension icon costs ten seconds and prevents the frustration of finding out your "full-res" download was actually a 300px thumbnail.

Missing CSS background images

Some product pages display the main product image as a CSS background rather than an img tag, which means standard download tools miss it entirely. BID scans computed CSS styles and includes background-image URLs in its gallery, so these are captured automatically without any extra steps on your part.

Building a Repeatable Workflow That Scales

The real value of a tool-based workflow is not the first catalog build. It is the fifth one, when you run it in half the time because every step is already decided.

A locked-in workflow for catalog image collection looks like this:

• Filters saved as defaults: Set your minimum dimension once in BID's settings. From that point on, every session opens with the right filter already applied.
• Filename pattern saved: Settle on one pattern ({title}-{width}x{height}-{index} is a solid default) and save it. Every download produces consistently named files without re-entering the pattern.
• Dedupe enabled at the session level: Pro's duplicate-skip works across the entire browser session, not just per page. As you move from product page to product page, BID remembers what it has already captured and skips re-downloads automatically. Over a 200-page catalog run, this routinely eliminates 30 to 50 redundant files.
• Format decided upfront: Check your target platform's requirements once, note them in your project doc, and apply a type filter before every session. No mid-project surprises.

This compounds most visibly during migrations. When you move platforms every two or three years, the image-collection step goes from a two-day manual task to a few hours of structured browsing, because the workflow is already proven and the tooling is already in place.

A Quick Note on Image Rights

Technical capability is not the same as legal permission. Before bulk-downloading images from any external source, confirm that you are authorized to use them.

For supplier images, the situation is usually straightforward. Most wholesale supplier agreements explicitly permit authorized resellers to use product photography for their own listings. Check your supplier agreement or distributor terms, and if the language is ambiguous, send a one-line email asking for written confirmation. Many suppliers have a brand asset portal precisely for this purpose, which is always the better source than scraping their product pages.

For images sourced from competitor or third-party sites, the answer is almost always no. Even if the image is technically accessible in your browser, downloading and republishing it without a license is copyright infringement.

For your own site, there are no restrictions. BID is particularly useful here for platform migrations: you own the images, you just need an efficient way to recover them from your live storefront before the old platform goes offline.

Frequently Asked Questions

Can I name downloaded files by SKU automatically?

Partially. BID's filename pattern tokens include the page title, hostname, image dimensions, and a sequential index. If your supplier's page title includes the product name or SKU (for example, "Blue Widget SKU1042 | Brand Store"), the {title} token captures that. For a fully automated SKU-based name, you would still need a light post-processing rename step, because BID reads what the page provides rather than your internal SKU database. A batch rename tool like PowerToys (Windows) or a short Python script can apply a SKU prefix to files in a folder after download.

How do I keep image resolutions consistent across a large catalog?

Set the minimum width filter in BID before every session. If your platform requires 1000px, set the filter to 1000. BID's preview gallery will only show images that meet that threshold, so off-spec images are never selected in the first place. For supplier pages that only offer lower-resolution images, flag those SKUs separately and request higher-res assets directly from the supplier rather than using the web page version.

How do I avoid downloading the same image for every product variant?

The Pro duplicate-skip feature handles this at the session level. As you browse variant pages (size, color, material), BID tracks the image content it has already captured and skips identical files even if they appear at a different URL or with a different filename. On the free tier, the practical workaround is to browse the variant page, check the BID gallery before downloading, and skip manually if the hero image is the same as the one you already have from the base product page.

What image format should catalog images be?

JPEG is the safest default for the broadest platform compatibility. Most major platforms (Shopify, WooCommerce, Amazon, Google Merchant Center, BigCommerce) accept JPEG without any conversion requirement. WebP is smaller and works on Shopify and WooCommerce, but feed parsers for marketplaces like Amazon often reject it. AVIF is not widely accepted at the catalog-import layer yet. If your source images are WebP or AVIF, convert to JPEG before import unless you have confirmed your specific platform accepts the source format.

Can I match downloaded images to a product CSV?

Yes, and this is where a consistent filename pattern pays off. If every image filename contains the product name or a SKU fragment from the page title, you can use a VLOOKUP or INDEX-MATCH in a spreadsheet to pair filenames with product rows. The CSV Preview and Quick Edit extension lets you open and scan large import CSVs directly in the browser without downloading and opening in Excel, which makes the verification step faster. For a large catalog, a short Python script that reads a folder of filenames and matches them against a SKU list is even more efficient, but the spreadsheet approach works well for catalogs under a few hundred SKUs.