Product Photography on a Budget: What Actually Matters for Online Sales

Most "budget product photography" advice stops at the moment you press the shutter. But on a PrestaShop store, the photo that converts a visitor is not the one sitting on your camera roll — it's the one PrestaShop has resized, compressed, cropped to your theme's image type, and served at the right moment in the page load. A merchant can spend a weekend shooting beautiful shots and still ship a product page that loads slowly, crops heads off, and shows the wrong colour. This post is about the decisions that actually move sales: which photography choices are worth your time, which are not, and — the part most guides skip — how to get those photos through PrestaShop's image pipeline without losing the quality you paid for.

Last updated: June 2026.

Two sibling posts cover the parts deliberately left out here so we're not repeating ourselves: the home-studio setup (lighting, backgrounds, tripod, the actual shooting) lives in how to take professional photos at home, and the question of what kind of image sells (composition, lifestyle vs white-background, angles) is covered in what sells and what does not. This one is the prioritisation and PrestaShop-delivery layer that sits on top of both.

The honest hierarchy: what moves sales and what doesn't

Budget is really a question of where you spend attention, not money. After watching a lot of catalogues, the ranking of what affects buying decisions is fairly stable — and it is not the ranking most merchants assume. So here is where to put your limited hours:

The takeaway that saves money: the things at the top are free or nearly free, and the things merchants spend money on (gear, RAW workflows, props) sit at the bottom. A modern smartphone, a window or two cheap softboxes, and a white board will out-convert an expensive camera used carelessly. The home-studio guide covers that kit in detail.

Why the right photo still fails on PrestaShop — and how to fix it

Here is the gap nobody warns budget shooters about. PrestaShop does not display your original file. When you upload an image to a product, PrestaShop generates a set of resized copies — one per image type — and serves those. So even a perfect photo is only as good as how PrestaShop processes it. Four settings decide that, and all of them live in the back office for free.

1. Image types — get the dimensions and crop right

Under Design → Image Settings (PrestaShop 1.7/8/9; it was Preferences → Images in 1.6) you'll find the list of image types — home_default, large_default, cart_default, and so on — each with a width and height. These dimensions feed the product page, the category grid, the cart, and quick-view. Two things matter here:

• The aspect ratio must match how you shoot. If your image type is square (say 600×600) but you shoot tall product shots, PrestaShop either letterboxes or — worse, depending on theme — crops. That's where heads, shoe-tips and product edges get sliced off in the grid. Set the image-type ratio to match your shooting ratio (or vice versa) and the crops stop.
• Bigger isn't free. Every image type multiplies the files generated per product. A catalogue of 1,000 products with eight image types and five photos each is 40,000 generated files. Delete image types your theme doesn't actually use rather than letting PrestaShop regenerate them forever.

2. Regenerate thumbnails after any change

Change an image type's dimensions, switch themes, or notice old products looking wrong? The originals don't update themselves. At the bottom of Design → Image Settings there's a Regenerate thumbnails tool — run it after any image-type change so the whole catalogue is rebuilt to the new dimensions. On a large catalogue this can time out from the browser; if it does, the prestashop:thumbnails:regenerate console command (PrestaShop 9, via bin/console) or your host's task runner finishes the job without the PHP timeout.

3. Format and compression — where most page-speed wins hide

Great photos mean nothing if they tank your page speed, and image weight is the single biggest performance problem on most stores. PrestaShop 8.1+ and 9 can serve WebP (and AVIF where the PrestaShop version and server image library support it) — turn it on under Design → Image Settings via the image format option, then regenerate. WebP is typically 25–35% smaller than JPEG at the same visible quality, which on an image-heavy product page is the difference between a fast first impression and a visitor who bounces before the hero loads. The "So what?": lighter images keep your Google PageSpeed score up and stop many mobile shoppers from staring at a blank frame. On 1.7 (which predates native WebP), a module that converts and lazy-loads images covers the same ground; we walk through all of this in image optimization: alt tags, lazy loading and page speed.

4. Filenames and alt text — the free SEO layer

PrestaShop builds the image URL and the alt attribute from data you control. Two cheap habits pay off:

• Name your exported files cleanly — blue-cotton-tshirt-front.jpg, not IMG_3847.jpg. PrestaShop generates the served image URL from image IDs and the product slug, not from your original filename, so the source name carries no SEO URL value — but a clean, descriptive filename keeps your media library navigable and your shooting workflow sane. The SEO weight lives in the product name and the image legend/alt text below.
• Set the image caption (alt text) by editing each product image's legend/caption in the product image section. PrestaShop renders it as the alt attribute — that's what Google Images reads and what a screen reader announces. Left blank, you're throwing away free product-search visibility. This pairs directly with the descriptive copy you write for the page; see writing product descriptions that rank and convert.

The budget shooting workflow that survives PrestaShop

Knowing the pipeline changes how you shoot. A few decisions made before the camera comes out save you re-doing the whole catalogue later:

• Shoot to your image-type ratio. Decide your product-page aspect ratio first (square is the safest default for grids), then frame every shot to it with margin to spare. Cropping in is free; un-cropping is impossible.
• Shoot bigger than you'll serve, but not absurdly. ~2000px on the long edge is plenty for PrestaShop's large_default and zoom. Anything beyond that is storage you'll never display.
• Lock your setup and batch-edit. Same light, same background, same distance for the whole session, then apply one set of adjustments to every file. Consistency is the cheapest trust signal you have — and it's a discipline, not a purchase.
• Resize and convert before upload, not just inside PrestaShop. Feeding PrestaShop a 6000px, 12MB phone original means it does the heavy resizing on every regeneration and stores a huge useless master. Down-res to ~2000px and reasonable JPEG quality first; let PrestaShop generate the display sizes from that.

When to stop DIY-ing and hire out

Budget photography handles the bulk of a catalogue. Spend money only where DIY genuinely can't reach:

• Hero and category-banner images — seen by every visitor, so the one place professional polish earns its fee.
• Lifestyle / on-model shots — locations, styling and people are hard to fake at home, and they sell differently than white-background shots.
• Jewellery, glass and highly reflective products — these need lighting experience that a window won't give you.
• Product video — a separate skill and kit; if you go this route, PrestaShop can embed it on the product page (see YouTube integration for product videos).

A white-background product shoot typically runs a few euros to ~€15 per product — a one-off cost worth weighing only for the items where it changes the buying decision, not the long tail.

Common questions about photos in the PrestaShop pipeline

Why does PrestaShop crop my product photos in the grid? Because PrestaShop doesn't serve your original — it generates resized copies per image type, and if an image type's aspect ratio doesn't match how you shot, it letterboxes or crops. That's where heads, shoe-tips and product edges get sliced off. Set the image-type ratio under Design → Image Settings to match your shooting ratio (square is the safest default for grids), and the crops stop.

I changed an image type but old products still look wrong — what now? The originals don't re-resize themselves. Run Regenerate thumbnails at the bottom of Design → Image Settings after any image-type or theme change. On a large catalogue the browser tool can time out; the prestashop:thumbnails:regenerate console command (PrestaShop 9, via bin/console) finishes the job without the PHP timeout.

Should I serve WebP, and how? Yes — WebP is typically 25–35% smaller than JPEG at the same visible quality, which on an image-heavy product page is the difference between a fast first impression and a bounce. PrestaShop 8.1+ and 9 can serve WebP (and AVIF where the version and server image library support it) via the image-format option under Design → Image Settings; turn it on, then regenerate. On 1.7, which predates native WebP, a conversion-and-lazy-load module covers the same ground.

Does my image filename affect SEO? Not the served URL — PrestaShop builds that from image IDs and the product slug, so the source filename carries no URL value. The SEO weight lives in the product name and the image legend/alt text. Still name your exports cleanly (blue-cotton-tshirt-front.jpg, not IMG_3847.jpg) to keep your media library navigable, and always set the image caption — PrestaShop renders it as the alt attribute that Google Images reads.

What resolution should I upload? Around 2000px on the long edge is plenty for large_default and zoom. Feeding PrestaShop a 6000px, 12MB phone original means it does heavy resizing on every regeneration and stores a huge useless master — down-res and compress before upload, then let PrestaShop generate the display sizes. Camera resolution beyond ~12MP makes no visible difference on the web.

Photos are one input — fit them to the page

Images don't convert in isolation; they convert as part of a product page that's working. Once your shots are clean, consistent and served fast, the surrounding decisions decide whether they get seen: a layout that puts the gallery where the eye lands (product page design best practices), a clear sense of what makes a visitor click buy instead of back (product page anatomy), and — if you've got a strong set of lifestyle shots — a dedicated gallery page to show them off.

The budget truth, end to end: the photography choices that move sales are mostly free — more angles, consistent framing, honest colour — and the money traps (gear, RAW, props) mostly don't. What separates a good shoot from a good store is the part after the shutter: matching your image types, regenerating thumbnails, serving WebP, and writing real alt text. Get the pipeline right and a phone-shot catalogue can look every bit as professional as one shot on a €5,000 rig — which, for most stores, is exactly the point of doing it on a budget.