All posts
Ecommerce Product Image Size: Sizes for Every Channel
November 8, 2026
A 1500 × 1500 px square master is a safe default for ecommerce product images. Use the channel table below to identify where you need a larger original, a different crop, or a smaller delivery file.
The problem isn't that merchants upload small pictures. In Baymard Institute's ecommerce usability benchmark, 25% of sites failed to provide sufficient image resolution or adequate zoom. A listing can display an image successfully and still leave shoppers unable to inspect the product.
The right ecommerce product image size therefore has three parts: an eligibility floor, a quality target, and an export suited to the placement. A reusable master helps you manage all three, but only if you preserve genuine detail and leave enough room to adapt the composition.
Table of Contents
- Recommended Sizes for Every Channel at a Glance
- Google Merchant Center Rules for Feed Images
- Marketplace Main Images and the Longest-Side Rule
- How Much Resolution Shoppers Need to Inspect Products
- Storefront Exports, Formats and File Weight
- Meta Ad Image Sizes by Placement
- Common Problems and How to Fix Them
- Build One Master Image and Export Every Size
<a id="recommended-sizes-for-every-channel-at-a-glance"></a>
Recommended Sizes for Every Channel at a Glance
Start with a square source, then choose its resolution according to the most demanding destination you publish to. Google's product image specification distinguishes 100 × 100 px for non-apparel and 250 × 250 px for apparel from its recommendation of approximately 1500 × 1500 px or larger.
That distinction matters more than finding a single universal size. Passing a published minimum addresses eligibility, not whether the image will look convincing when enlarged. A quality-oriented source preserves inspection detail and gives you more flexibility when preparing crops.
<a id="recommended-product-image-sizes-by-channel"></a>
Recommended product image sizes by channel
The square ratios below are working compositions for catalog consistency, not a claim that every channel requires square images. Where a channel has no numeric floor in the guidance used here, the practical floor is the same 1500 × 1500 px master. That is a production floor, not a claimed platform minimum.
| Channel | Aspect ratio | Practical floor | Recommended |
|---|---|---|---|
| Google Shopping, non-apparel | Square working master | 100 × 100 px eligibility | Approximately 1500 × 1500 px or larger |
| Google Shopping, apparel | Square working master | 250 × 250 px eligibility | Approximately 1500 × 1500 px or larger |
| Amazon main image | Square working master | 1500 × 1500 px working source | Keep clean margins and enough detail for zoom crops |
| Shopify product image | Square working master | 1500 × 1500 px working source | Export the square file at the largest size the storefront uses |
| WooCommerce product image | Consistent square catalog crop | 1500 × 1500 px working source | Size the export to the largest gallery or zoom display |
| Pinterest product pin | Portrait placement crop | 1500 × 1500 px working source | Export the portrait crop from the same master without resizing upward |
Production rule: Choose the largest justified source size, not the smallest accepted upload.
Keep a record for each destination with separate fields for accepted dimensions, desired display quality, format, and file weight. This prevents a feed-management team from treating a technical floor as the photography brief.
A single master can supply the channel versions, but it doesn't have to be the final canvas for every placement. A portrait ad may need an expanded background or a rearranged layout, while a product page may need an additional photograph showing a different angle. One source system is useful. One identical image everywhere isn't.
<a id="google-merchant-center-rules-for-feed-images"></a>
Google Merchant Center Rules for Feed Images
Google accepts JPEG, WebP, PNG, non-animated GIF, BMP, and TIFF, and prohibits scaled-up images and thumbnails, according to its image link specification. This separates source quality from file properties: exporting a weak original into a larger canvas doesn't make it a suitable catalog master.
Published Google pages also describe different resolution baselines. Its current product-image guidance gives 500 × 500 px as a practical minimum, encourages approximately 1500 × 1500 px or larger, limits images to 64 megapixels and 16 MB, and recommends that the product occupy roughly 75% to 90% of the image area.
<a id="separate-eligibility-from-production-standards"></a>
Separate eligibility from production standards
The category-specific floors and the broader quality baseline shouldn't be collapsed into a single claim about universal acceptance. For production, the sensible response is to work above the lower thresholds rather than build a catalog around whichever published number is smallest.
Check the applicable Google help page and any Merchant Center diagnostics before upload. A technically eligible image may still be weak merchandising material, and an image with generous pixel dimensions can still violate a source-quality rule.
The checklist visual groups the main checks. For category minimums, use the written distinctions above rather than treating labels in a graphic as the final authority.
<a id="why-framing-can-defeat-adequate-resolution"></a>
Why framing can defeat adequate resolution
Consider an enlarged thumbnail. Its file properties may show acceptable dimensions, but the edges, printed label, and surface texture still come from the smaller original. Changing the export dimensions doesn't restore missing photographic detail.
Now consider a sharp source with excessive empty space. The file can satisfy the resolution guidance while presenting a product that looks undersized beside more tightly composed listings. Neutral margins should protect the silhouette, not overwhelm it.
Before uploading, run these checks:
- Accepted format: Confirm the file type against the destination specification.
- Original detail: Verify that the source wasn't enlarged from a thumbnail.
- Resolution: Use the quality target rather than designing around a low eligibility floor.
- Product fill: Keep the subject dominant without clipping its outline.
- File limits: Inspect both dimensions and byte size.
- Background: Use a clean, neutral treatment and inspect the edges for masking artifacts.
<a id="marketplace-main-images-and-the-longest-side-rule"></a>
Marketplace Main Images and the Longest-Side Rule
A longest-side requirement measures the larger image dimension. It doesn't mean that both dimensions must reach the same threshold, and it doesn't establish a mandatory square aspect ratio.
Squareshot's ecommerce image-standards article cites Amazon guidance that main product images should be at least 1,000 pixels on the longest side. Separately, CamClo3D's ecommerce photography guide describes 500 pixels on the longest side as a minimum and recommends at least 1,000 pixels to enable zoom.
<a id="acceptance-and-zoom-arent-interchangeable"></a>
Acceptance and zoom aren't interchangeable
These descriptions illustrate why a table headed “minimum size” can mislead. A basic image threshold and a zoom-oriented threshold answer different questions. Treat the marketplace's current help page for your category as the final authority, especially when a secondary guide compresses those distinctions.
For a rectangular photograph, inspect the longer dimension in the file properties. For a square photograph, either dimension provides that measurement. Don't infer compliance from how large the preview looks inside your editing application.
A square main image is a practical catalog choice because it creates predictable space around different product shapes. Prepare a plain white background when the applicable main-image rules call for it, and reserve contextual scenes, scale demonstrations, and feature explanations for the appropriate additional-image slots.
<a id="a-main-image-preparation-procedure"></a>
A main-image preparation procedure
- Export from the original master. Use a square canvas when it suits the category and retain enough source detail for inspection.
- Inspect the silhouette. Leave room around handles, straps, protruding components, and packaging corners.
- Check file properties. Confirm the longest side, encoding, and file weight rather than relying on the filename.
- Build the supporting gallery. Add views that answer questions about scale, materials, construction, and included components.
An eligible main image introduces the product. The supporting gallery should help the shopper evaluate it.
Don't claim a larger export is an Amazon requirement unless current marketplace documentation establishes that requirement. A deliberately larger source can be a sensible internal standard, but label it as your production choice.
Finally, test the uploaded listing rather than stopping at export. Marketplace processing and the actual image viewer determine what the shopper can inspect. A successful upload doesn't prove that the experience is useful.
<a id="how-much-resolution-shoppers-need-to-inspect-products"></a>
How Much Resolution Shoppers Need to Inspect Products
Zoom is a shopping task, not just an interface feature. The shopper is trying to answer a concrete question: whether a seam is finished cleanly, a clasp looks sturdy, or a fabric has the expected texture.
Baymard's benchmark, introduced earlier, identifies the relevant failure: shoppers can receive an image without receiving enough visual information. The practical response is to evaluate the delivered inspection experience, not merely whether the gallery includes a magnifying-glass icon.
The illustration highlights that distinction between seeing the product and inspecting its details.
<a id="bigger-files-dont-fix-missing-information"></a>
Bigger files don't fix missing information
A large image can still conceal the detail that matters. Soft focus, glare across a label, heavy retouching, or an unhelpful camera angle can make additional pixels irrelevant.
For a leather bag, the hero shot might communicate shape and color but hide the stitching and hardware. For a drinking glass, an isolated cutout might show the outline without communicating how it fits in a hand. These are photography and composition problems, not export-size problems.
Close-ups and contextual photographs solve different questions. A detail photograph reveals construction. An in-scale photograph gives the viewer a familiar reference, such as a hand, a person, or the setting where the product is used.
<a id="run-an-inspection-test"></a>
Run an inspection test
Open the published product page on a desktop and use the gallery exactly as a shopper would. Don't inspect only the original file in Photoshop, because that bypasses the theme, image delivery, and viewer behavior.
- Edges: Look for softness, halos, and jagged masking.
- Texture: Check whether grain, weave, or surface finish remains distinguishable.
- Construction: Inspect stitching, joins, fasteners, and printed markings.
- Interaction: Confirm that enlargement opens predictably and allows useful navigation.
- Scale: Ask whether the gallery communicates the product's size without relying solely on written dimensions.
A source that remains sharp under enlargement is necessary, but it isn't sufficient. The photograph also needs to expose the feature the shopper is trying to judge.
Keep the hero composition clean, then select supporting images according to unanswered purchase questions. That produces a more useful gallery than repeatedly uploading the same angle at higher resolution.
<a id="storefront-exports-formats-and-file-weight"></a>
Storefront Exports, Formats and File Weight
An upload limit is not a delivery target. Shopify's image-size guide supports uploads up to 5000 × 5000 px or 25 megapixels, with a 20 MB upload limit, and identifies 2048 × 2048 px as a strong square-product default; images above 800 × 800 px are generally needed for zoom. The same guide recommends much lighter web delivery, often around 200 KB or less, with approximately 500 KB as a broader practical target.
Those figures describe different stages of the workflow. The uploaded asset supplies the source; the delivered asset serves a particular display. Sending the archive everywhere confuses storage quality with browser requirements.
<a id="size-the-export-before-choosing-compression"></a>
Size the export before choosing compression
First identify the largest actual display slot for the derivative. Then account for the display's pixel density and whether the same asset supports enlargement.
Don't shrink the gallery source to match a collection-card thumbnail. Equally, don't force a small collection card to download the full archive when the storefront can serve a suitable responsive version.
Use your theme's image controls and responsive image delivery to select appropriate derivatives. In a custom storefront, inspect the generated srcset and sizes behavior so the browser's selection matches the layout.
<a id="image-formats-and-when-to-use-them"></a>
Image formats and when to use them
| Format | Best use | Transparency | Export note |
|---|---|---|---|
| JPEG | Photographic product images on opaque backgrounds | No | Adjust quality while inspecting fine detail at the rendered size |
| PNG | Cutouts and sharp graphic edges | Yes | Lossless files can be large; optimize before upload |
| WebP | Photographic storefront delivery | Yes | Compare the actual export with JPEG and confirm destination support |
| AVIF | Modern photographic storefront delivery | Yes | Test encoding quality, processing support, and browser delivery |
Avoid declaring a format the smallest in every case. Image content, encoder settings, and the quality you preserve affect the result. Compare real exports of your own products rather than assuming the file extension determines the outcome.
JPEG is a practical starting point for conventional product photography. PNG is useful when transparency or clean graphical edges are essential. Modern delivery formats belong in the workflow when your platform supports them reliably.
Compression test: Preserve the details that distinguish the product, not an arbitrary byte target.
<a id="keep-color-and-composition-consistent"></a>
Keep color and composition consistent
Use an sRGB workflow for ordinary web exports and inspect the result in a browser. Keep the source profile managed during editing rather than stripping or assigning profiles without checking the color.
Maintain a consistent aspect ratio for primary catalog images. The important visual check is whether neighboring products have comparable prominence, not merely identical canvas dimensions.
A tall bottle and a wide shoe won't necessarily need identical internal margins. Match their apparent prominence while protecting the full outline and leaving room for theme cropping.
<a id="an-export-procedure-for-storefront-teams"></a>
An export procedure for storefront teams
- Archive the full-quality square master. Keep editable source files separately from delivery assets.
- Create derivatives for actual slots. Distinguish collection cards, product galleries, and enlargement views.
- Compress and inspect. Check the result at its rendered size, especially labels, mesh, fine patterns, and reflective edges.
- Validate on devices. Confirm that responsive delivery chooses an appropriate file and that the gallery remains usable.
Stop compressing when product information starts to disappear. A smaller file isn't an improvement if a shopper can no longer distinguish the finish or read an important marking.
For mobile grids, serving a smaller derivative can reduce transferred data without changing the visible result, provided it still supplies enough pixels for that display. Confirm that with the actual rendered page rather than judging from desktop thumbnails alone.
<a id="meta-ad-image-sizes-by-placement"></a>
Meta Ad Image Sizes by Placement
Meta defines placements by aspect ratio more than by fixed pixel dimensions, so the table below separates the ratio each placement expects from a common export size that fits it. Treat the pixel figures as working targets that preserve detail through ad compression, not as official Meta mandates.
| Placement | Aspect ratio | Pixel size | Layout note |
|---|---|---|---|
| Feed, square | 1:1 | 1080 × 1080 px | A reusable starting layout for feed creative |
| Feed, portrait | 4:5 | 1080 × 1350 px | Reposition copy rather than stretching the square |
| Stories, Reels and full-screen vertical | 9:16 | 1080 × 1920 px | Keep important content clear of interface overlays |
| Feed, landscape link ad | 1.91:1 | 1200 × 628 px | Build a wide layout suited to the link preview |
| Facebook Shops product image | 1:1 | 500 × 500 px minimum; 1024 × 1024 px suggested | Treat shop catalog images separately from paid-ad layouts |
For Facebook Shops, GraphicDesignEye's image-size guide reports a 500 × 500 px minimum, with 1024 × 1024 px suggested for best results. These are shop-image figures, not evidence for the specifications of every Meta ad placement.
A 1080 px width is the common denominator across the feed ratios, which is why a single square master covers most placements. The exception is full-screen vertical: 9:16 asks for nearly twice the height a square provides, so that format needs a rebuilt layout rather than a resized file.
The diagram shows how placement changes affect composition.
<a id="crop-direction-matters"></a>
Crop direction matters
Turning a square into a portrait by cropping removes material from the left and right, not the top and bottom. A wide product may therefore lose its edges even when it sits vertically centered.
If the subject nearly fills the original square, a narrow crop may be impossible without damage. Extend the background or rebuild the layout around the isolated product instead of cutting off essential features.
This is the limit of the single-master idea: reuse the product source, not necessarily the entire finished composition. Text, badges, logos, and background elements may need independent placement.
<a id="keep-important-content-clear-of-overlays"></a>
Keep important content clear of overlays
Preview each ad in its intended placement. Interface controls, account information, and calls to action can cover parts of the creative, particularly in full-screen layouts.
Use this workflow:
- Select the placement. Confirm its current ratio and export dimensions in the publishing interface.
- Start from the master. Avoid creating a new crop from an already reduced ad export.
- Reposition key elements. Keep the product, headline, and logo away from overlay areas.
- Inspect the preview. Check readability, product integrity, and the final call to action.
The accompanying video provides another visual reference for the workflow.
<iframe width="100%" style="aspect-ratio: 16 / 9;" src="https://www.youtube.com/embed/LM27Q74Lu60" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>Approve the placement preview, where the viewer's interface and your composition appear together. A file that uploads cleanly can still hide its headline behind a reply bar.
<a id="common-problems-and-how-to-fix-them"></a>
Common Problems and How to Fix Them
Diagnose image problems in a fixed order: source dimensions, product framing, format, file weight, and placement crop. This avoids wasting time compressing a file whose real problem is an undersized original.
Read the rejection message before editing anything. “Too small,” “unsupported format,” and “file too large” require different fixes, even when they affect the same image.
<a id="image-problems-causes-and-fixes"></a>
Image problems, causes and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Blurry when zoomed | Insufficient source detail, soft focus, or excessive compression | Return to a sharper original and inspect the delivered enlargement |
| Rejected as too small | Undersized source or an unsuitable thumbnail | Export from a genuine high-resolution original |
| Product looks tiny in grid | Excessive empty space around the subject | Tighten the composition while protecting the silhouette |
| Cut off in a vertical placement | Crop geometry or interface overlays | Rebuild the layout and preview the placement |
| File rejected for size | File exceeds that destination's upload limit | Reduce unnecessary dimensions or adjust encoding |
| Soft on phones | Compression, inappropriate responsive selection, or enlargement | Compare the delivered file with the original and inspect rendering |
<a id="match-the-repair-to-the-failure"></a>
Match the repair to the failure
Blur needs a source check first. If the original is sharp but the published version isn't, inspect the storefront derivative and compression settings. If the original is already soft, changing the export format won't restore the missing detail.
A size rejection needs a specification check. Confirm whether the platform is checking a side length, total resolution, or file weight. Don't repeatedly enlarge an image until the upload succeeds, because acceptance won't prove the result is sharp.
A small-looking product needs a framing check. Compare the subject's prominence against neighboring catalog images. Reduce unnecessary background space rather than increasing the canvas dimensions.
A cut-off ad needs a layout check. If the crop removes a handle or a wide package, moving the logo won't solve it. Reposition or scale the product within a new composition, then assess interface overlays separately.
<a id="find-where-quality-was-lost"></a>
Find where quality was lost
Compare the archive master, the exported derivative, and the downloaded published image. This identifies whether the problem began during photography, editing, encoding, or platform delivery.
Use descriptive filenames that distinguish the source from its derivatives. Keep upload-ready assets separate from old thumbnails so a feed manager or media buyer doesn't accidentally select an obsolete version.
Fix the earliest faulty stage. Re-exporting from a damaged derivative preserves the damage.
Some failures originate in the master; others come from delivery settings. Diagnose that distinction before changing every file in the catalog.
<a id="build-one-master-image-and-export-every-size"></a>
Build One Master Image and Export Every Size
Build a repeatable production sequence around an archived source and destination-specific checks. The master should preserve options, while the export should answer the requirements of a particular placement.
- Keep a full-resolution square master. Use the larger source justified by your storefront and marketplace needs, with a clean background and protected product edges.
- Create storefront derivatives. Separate ordinary display assets from gallery enlargement sources and confirm responsive delivery.
- Adapt the advertising compositions. Reuse the original product photograph, but rearrange text and background elements when a direct crop would damage the subject.
- Validate each export. Check its dimensions, accepted format, file weight, and rendered appearance against its destination.
- Archive the source and export recipe. Save the editable file, chosen photograph, crop treatment, and encoding settings so future updates don't begin with a compressed derivative.
<a id="treat-the-master-as-a-source-not-a-finished-template"></a>
Treat the master as a source, not a finished template
A reusable square asset works best when the product can be separated from its background and placed without distortion. It should preserve genuine surface detail, accurate proportions, and a clean outline.
Keep alternative photographs alongside it. A front view may suit the catalog, while a lifestyle photograph or packaging shot may communicate an advertising angle more effectively. Source consistency doesn't require every placement to use the same camera angle.
The process diagram summarizes the production sequence.
<a id="put-multi-ratio-production-into-practice"></a>
Put multi-ratio production into practice
With ProdSnap, each product can have multiple photographs, including front, side, lifestyle, and packaging shots, and you choose which photograph drives each batch. Every batch includes variants in 1:1, 4:5, and 9:16, with angle-grounded copy, exported as high-resolution PNG files, one per ad per ratio, that can be uploaded directly into Ads Manager.
That supports the advertising branch of the image workflow; it doesn't replace catalog compliance checks. Review generated product details, packaging, text, and composition before treating an output as publishable.
Keep the selected source photograph attached to the production record so later revisions use the intended angle. Review the ratios independently, because a convincing square composition doesn't automatically establish that the vertical version preserves the product correctly.
Before publishing, confirm each export's format and file weight against the storefront format guidance, account for potentially larger PNG files, inspect the placement preview, and treat each platform's current help page as the final authority.
ProdSnap turns selected product photographs into multi-ratio Meta ad creatives with high-resolution PNG exports. Visit ProdSnap to build a batch from your product images, then review each placement's framing and file properties before uploading.