PrestaShop builds every product image size from one file. You upload a single master per image and PrestaShop generates the rest, so the master decides how every size looks. Its own documentation says it directly: you only have to upload one master version of your image, big enough to be resized into all the image sizes (docs.prestashop-project.org, accessed September 2026).
Every flaw in the master then propagates. A soft master gives you soft thumbnails at every size. A master at the wrong shape gives you white bars at every size, which PrestaShop also warns about: if your uploaded image does not have the same width-to-height ratio as the settings in place, you risk seeing whitespace on the resized image.
So the quality gate sits entirely at upload. There is no per-size correction afterwards, only regeneration from the same source. Set the shape once and SKU 300 behaves the same way SKU 1 did.
Key Takeaways
-
One master in, every size out. PrestaShop derives all image sizes from a single upload per image.
-
Ratio mismatch produces whitespace, and PrestaShop documents this rather than hiding it. Match your master’s ratio to your configured sizes.
-
A 2015 post on PrestaShop’s own blog suggests 800 by 800 pixels for product images (prestashop.com, accessed September 2026). Treat that as a floor for a modern store, not a target.
-
Retina doubles your file count. The high-resolution option generates a second file per image at twice the resolution.
-
Regenerating thumbnails erases manually-uploaded ones. PrestaShop states this directly, and it surprises people once.
-
Never delete the default image settings. The documentation says you will need them.
-
One shape across the whole catalog. Pick square, shoot everything to it, and the resizing question stops coming back at every new drop.
How does PrestaShop handle product images?
Through image types. The Image Settings page defines a set of named sizes, each with a width and a height, and PrestaShop renders one file per type from your master upload. Your theme then calls whichever type belongs in each slot: one for the cart line, one for the category grid, one for the main product view.
By default, every image setting is already installed in your store, and PrestaShop’s documentation warns against deleting them because you will need them (docs.prestashop-project.org, accessed September 2026). The sizes shown on that page come from the default Classic theme, so a store running a third-party theme will see a different set. Check the panel in your own installation rather than trusting a number from a tutorial, since themes add and rename types freely.
The high-resolution option is worth a deliberate decision rather than a default. PrestaShop describes it as generating a new file for each image at twice the resolution, and adds its own caution: this will double your number of image files, so use it wisely if you have limited storage space. On a catalog of a few hundred SKUs with several images each, that is a real number, not a rounding error.
What size should the master image be?
Bigger than your largest configured image type, square, and consistent across the catalog.
PrestaShop’s own blog suggests 800 by 800 pixels for product images, noting the software will automatically resize them to fit the default theme (prestashop.com, accessed September 2026). That post dates from 2015. The figure is a reasonable minimum rather than a modern target. If you enable the retina option, PrestaShop is generating files at twice your configured dimensions, so an 800px master starts constraining what it can produce.
A practical target for a store being built now is a square master between 1500 and 2000 pixels per side. That feeds a large product view sharply, survives retina doubling, and leaves headroom if you later change your theme. Going much beyond that trades page weight and storage for detail nobody sees.
The ratio matters more than the pixel count. Because PrestaShop resizes rather than crops intelligently, a portrait master fed into a square image type is where the documented whitespace appears. Pick one shape, usually square, and shoot everything to it. That single decision removes the most common PrestaShop image complaint before it happens.
If your source files are already too small, no setting recovers them. Low resolution product images covers what upscaling can and cannot do.
When do you need to regenerate thumbnails?
After any change to an image type’s dimensions, and after switching themes. Until you regenerate, existing images keep the sizes they were generated at, so your store runs a mix of old and new dimensions and the grid looks subtly wrong without an obvious cause.
The process runs from the Image Settings page: change the settings, select the content type, indicate whether to keep previous thumbnails, then regenerate.
One warning to read before you click it. PrestaShop states that manually-uploaded thumbnails will be erased and replaced by automatically-generated thumbnails (docs.prestashop-project.org, accessed September 2026). If anyone on your team has hand-crafted a specific thumbnail crop for a hero product, regeneration destroys that work. Back up before running it on a live catalog, and note that regeneration on a large store is slow and resource-hungry, which is a maintenance-window job rather than a mid-afternoon one.
What should a PrestaShop product show?
The platform question is settled by now. The photography question is the same one every store faces, with the ratio constraint layered on top.
A working set for physical products:
- A clean packshot on a plain ground, square, centred, generous margin. This becomes the grid tile.
- Two or three alternate angles covering what a buyer would turn over in their hands.
- A detail shot of texture, finish, stitching or closure.
- A scale reference so nobody has to picture the dimensions from a spec table.
- A context or styled shot where the setting is part of the purchase decision.
Shoot all five to the same square ratio and PrestaShop’s resizing behaviour stops being something you think about. Product photography angles covers which angles earn their slot by product type, and ecommerce product photography covers the shoot.
The generous margin in point one is a PrestaShop-specific habit worth adopting. Because different image types have different dimensions and your theme may letterbox, an item photographed tight to the frame edge can end up looking cramped in one size and fine in another. Space around the product travels well across sizes.
How do you fill a PrestaShop catalog without shooting everything?
Many PrestaShop stores are small and self-hosted, and one person often runs the store and the accounts. Five images across three hundred SKUs is not a realistic photoshoot for that team.
The approach that works is one real photograph per product, then derive the rest from it. Shoot the packshot properly, at your standard square ratio, and make the alternate angles and styled scenes from that source. In DesignerBox, a multi-angle template makes more views from a single photo, and a product scene template makes context shots. A marketplace listing set template covers the full set for one product.
Build that setup once and save it as a workflow, then run the same workflow for the next product. You set the brand once, and the workflow reads it on every run, so the standard holds without anyone remembering what they did last time. The page for ecommerce brands shows how DesignerBox fits a store catalog. Batch, which runs one workflow over a whole sheet of products, is coming.
Because PrestaShop derives everything from your master, the AI images need to be made at master resolution and uploaded as masters themselves, not at display size. A 600px scene uploaded as your master gives PrestaShop nothing to work with.
Two limits to hold. Anything that carries a factual claim, colour, finish, material, dimensions, has to derive from a real photograph of the real product. And if you sell in the EU, a realistic AI image of a person can count as a deep fake. Article 50(4) of the EU AI Act requires whoever publishes a deep fake to disclose it, and Article 50 has applied since 2 August 2026 (European Commission FAQ, accessed September 2026). This is general information, not legal advice. Labelling AI-generated images covers the details, and it is worth reading before publishing rather than after.
For stores running inherited supplier photography, the task is standardising rather than creating. AI background removal covers lifting mixed-provenance product shots onto one consistent ground, which is what makes a reseller catalog read as a single shop.
What does a 300 SKU catalog cost?
The photography kit is the usual short list: one window, one board, a tripod, a fixed spot. As a rough estimate, under $50.
The AI images cost credits, and the cost depends on the model the workflow uses. DesignerBox shows what a run costs before you start it. So run ten products first, look at the results at master resolution, and only then plan the other 290.
Do that arithmetic against your own catalog. Three derived images across 300 SKUs is 900 images. Multiply the cost of one test run by the runs you need, then compare it with the plan allocations. The DesignerBox pricing page lists Basic at $15 a month, Pro at $35, Premium at $75 and Ultra at $200, all billed monthly, with 500, 1,000, 2,500 and 8,000 credits a month. The free plan includes 112 credits a month for a first test.
The plan that decides a live store is Pro, because the commercial licence starts there. If more than one person works on the catalog, note that every plan below Ultra is one seat.
If you also run a Shopify or WooCommerce storefront, the image handling is genuinely different on each and the specs do not transfer. WooCommerce product photography covers that platform’s three sizes and its uncropped main image, and Shopify product image size covers Shopify’s limits.
Shoot one master properly, save the setup that turned it into a full listing, and run it again for every SKU after it.
Start from a template, add your brand and your products, and run it. The cost is shown before the run. See the templates.
FAQ
What size should PrestaShop product images be?
A 2015 post on PrestaShop’s own blog suggests 800 by 800 pixels (prestashop.com, accessed September 2026), but treat that as a minimum. Because PrestaShop generates every size from your single master upload, and the retina option doubles the resolution it needs to produce, a square master between 1500 and 2000 pixels per side is a safer target for a store being built now.
Why do my PrestaShop images have white bars around them?
Aspect ratio mismatch. PrestaShop documents this directly: if your uploaded image does not have the same width-to-height ratio as the settings in place, you risk whitespace on the resized image (docs.prestashop-project.org, accessed September 2026). The fix is upstream, in your shooting and cropping, not in the settings.
Do I need to regenerate thumbnails in PrestaShop?
After any change to image type dimensions, and after a theme change. Existing images keep their previous sizes until you regenerate. Be aware that regeneration erases manually-uploaded thumbnails and replaces them with automatically-generated ones, so back up first if anyone has hand-crafted a crop.
Should I enable high-resolution images in PrestaShop?
Check your storage first. The option generates a second file for every image at twice the resolution, which PrestaShop notes will double your image file count. On a modern store the display benefit is real, but plan the storage and confirm your master files are large enough to feed it.
Can I delete unused PrestaShop image types?
PrestaShop’s documentation advises against deleting the default image settings, stating you will need them. Unused types from an uninstalled theme are a different matter, but the defaults that ship with the Classic theme should stay.
Can I use AI-generated product images on PrestaShop?
PrestaShop is store software, and we found no PrestaShop rule about AI images, as of September 2026. The constraints come from consumer law in your market and from any advertising channel you feed. They centre on accuracy: the image must not misrepresent what the buyer receives. If you sell in the EU, a realistic AI image of a person can count as a deep fake under Article 50(4) of the EU AI Act, which requires a disclosure. This is general information, not legal advice.
How many product images does a PrestaShop listing need?
Five covers most physical products: a packshot, two or three alternate angles, a detail shot, a scale reference and a context shot. Shoot them all to the same square ratio so PrestaShop’s resizing never introduces whitespace.
Sources
- PrestaShop 9 documentation, Image Settings: https://docs.prestashop-project.org/v.9-documentation/user-guide/improving-shop/customizing-store-design/image-settings
- PrestaShop 8 documentation, Image Settings: https://docs.prestashop-project.org/v.8-documentation/user-guide/improving-shop/customizing-store-design/image-settings
- Image sizes and types for PrestaShop’s default template, PrestaShop blog (2015): https://prestashop.com/blog/conversion-en/image-sizes-and-types-for-prestashops-default-template/
- European Commission, Transparency obligations under Article 50 of the AI Act (FAQ): https://digital-strategy.ec.europa.eu/en/faqs/transparency-obligations-under-article-50-ai-act
PrestaShop image generation behaviour, whitespace warning, retina behaviour and thumbnail regeneration verified from PrestaShop’s own v9 documentation as of September 2026. Image type dimensions come from the default Classic theme and differ under third-party themes, so confirm against your own installation. DesignerBox plan prices are monthly, from the DesignerBox pricing page (designerbox.ai/pricing), September 2026.
