BigCommerce storefronts load product photos from cdn11.bigcommerce.com at a size the theme picks, so "Save image as" usually gives you a 500 or 1280 pixel copy. If you run the store and want your photos before a migration or as a backup, BigCommerce has an official route through WebDAV, and the storefront will also hand you the stored file once you change one word in the image address.
Products › Export builds a CSV of your catalog with a link to each image and none of the image files. BigCommerce's Supported Product Fields page describes that column, "Internal Image URL (Export)", as a read-only field that "displays an image's URL in the CSV export file", and the import ignores it.
For the files, BigCommerce's "Backing Up Your Store" article says product images live in WebDAV. You connect with a WebDAV client (BigCommerce recommends Cyberduck 8.6.3; the login details are under Settings › File access (WebDAV), and your user account needs Enable WebDAV ticked) and drag the product_images folder to your computer. BigCommerce says that folder "contains all product images, as well as pattern swatches used in color options." It also renames uploaded images and puts them in subfolders it assigns at random, so expect file names that differ from the ones you uploaded.
Two gaps matter before a move. Theme downloads leave out images, so anything you added as a Page Builder image widget has to be saved separately. And restoring product images from that backup only works on the store they came from; for images from anywhere else, BigCommerce points you to the "Importing Product Images" section of its import instructions.
If you own the store and can use WebDAV, that folder holds every product image. The storefront methods below help when you have no WebDAV access, want the photos grouped by product page, or need the Page Builder images the theme download skips.
Right-click a product photo and choose "Open image in new tab". The address looks like this:
https://cdn11.bigcommerce.com/s-l85bzww3lo/images/stencil/1280w/products/890/38645/Final_MVT011_….jpg
The part after stencil/ is the size. Themes use either a width, such as 1280w, or a box the photo is fitted into, such as 500x659. Replace it with original and reload.
I tried this on product photos from four BigCommerce stores. A walking pad photo shown at 1280×1280 came back at 4359×4359, and a PNG shown at 500×500 was 2000×2000. Three other photos shown at 500×500 were 720, 1200 and 1200 pixels square, and one shown at 1280 was 1500×1500.
Nothing got enlarged. A 1217×655 desk photo was the same size at 1280w and at original, and one store's main photo stayed 500×500 at original because that is what was uploaded. The box sizes keep the photo's shape: the desk photo at 500x659 came back as 500×269 with no padding.
original in place of the size in BigCommerce image addresses, and those images show an HD badge.source.txt holding the page link.BigCommerce's image server picks the format from the list of formats the browser says it accepts. Chrome's list includes WebP, so Chrome gets WebP even when the address ends in .jpg. For the 4359×4359 photo, a request with Chrome's list got a 1,869,190-byte WebP and a plain request got a 3,259,013-byte JPEG. No request got AVIF, including one that asked for AVIF only. The 2000×2000 PNG came back as a 6.2 MB PNG to a plain request.
The CDN in front of that server keeps whichever version it fetched first for an address and hands that copy to later requests, whatever formats they list. An address first fetched with Chrome's list kept returning WebP to plain requests, and one first fetched plainly kept returning JPEG to Chrome's list. So the format you get partly depends on who asked before you.
PixLasso's downloads do not ask for WebP, so an address the CDN has not stored yet arrives in the format that was uploaded, and one it already holds as WebP arrives as WebP. Some stores upload WebP in the first place: one store in my sample uploads its newer product photos as .webp files, and those came back as WebP even to a request that asked for JPEG only. Each file in the ZIP is named after the format that actually arrived, so a WebP never hides behind a .jpg name.
Use this on your own store, or on a store whose owner has given you permission. Product photos belong to the store or its photographer, and saving them does not give you the right to reuse them.
The free version saves up to 30 images per download in their original format, with no daily limit; press Download again for the next batch. Right-click "Save image as JPG / PNG / WebP" on a single photo is free. Pro is a single US$9.99 payment (the launch price until 31 December 2026, then US$14.99). It removes the 30-image cap, converts a whole batch to JPG or PNG, resizes and pads photos to a white square, and lets you set your own file names.
PixLasso only sees what the storefront shows. Hidden products, and catalog images that no page you open displays, stay out of the ZIP, so for a full catalog backup the WebDAV folder is the better source. Photos that arrive as WebP, because the store uploaded WebP or the CDN already holds a WebP copy, need the Pro batch conversion, or the free right-click option one at a time, to become JPGs.
Address edits and formats checked 1 November 2026 with product photos from four BigCommerce stores, using curl with Chrome's list of image formats and with a plain request. Export and WebDAV details are from BigCommerce's help pages "Supported Product Fields", "Backing Up Your Store" and "File Access (WebDAV)". I made PixLasso, and I mention it where it helps; the address edit and WebDAV need no extension.