Selling in several places works better when your photography process has a common master and a few deliberate exports. A single final file can sometimes serve more than one channel, but the channels have different rules, display crops and delivery methods.
Use this comparison to plan the handoff. The table summarizes a few useful distinctions; the destination’s current documentation and your product category still determine the full requirements.
At a glance
- Keep a high-resolution original and export for each destination.
- A white-background product view is reusable, while supporting images can explain context and detail.
- Pixel dimensions, visual rules and upload or URL delivery all need checking.
The differences that affect your export
| Destination | Important distinction | Our working approach |
|---|---|---|
| Amazon | General MAIN rules specify pure white, full product and about 85% coverage. | A clean product view; review category instructions. |
| eBay | Condition accuracy matters; the policy requires 500 px on the longest side. | A sharp main view plus actual condition details. |
| Etsy | 2,000 px in both dimensions is recommended; thumbnails use several crops. | Leave central framing room and preview thumbnails. |
| Shopify | Theme and product-gallery behavior shape the presentation. | Test a consistent ratio and variant mapping. |
| Image specifications and publicly crawlable URLs both matter. | Use a sharp 1,500 px-plus asset with a stable URL. |
Treat the final column as an editorial production suggestion. It is useful for setting up a workflow, but it does not replace any platform’s technical limits or product-specific policy. The source links at the end of this article go directly to the relevant official guidance.
Start with a source library that survives new crops
Keep the camera original in a read-only source folder. Store a separate edited master and generate each destination’s upload from it. A larger original with a little room around the product gives you flexibility to make a square catalog image, a landscape listing photo and a closer detail without losing essential parts.
Use stable product identifiers in your filenames and folder structure. A useful pattern includes SKU, variant and view, such as tote-blue-front. Keep the destination and export version in a separate suffix or subfolder. Someone reviewing the catalog should be able to identify the image without relying on the photograph alone.
Create one dependable product view
A clear product photograph on white is a practical reusable asset. It can serve as the foundation of an Amazon main image, an eBay lead photo or a Shopify catalog view when the composition fits. Export an opaque version for destinations that do not handle transparency as you expect.
Review the selection carefully before reuse. Pale products need visible contours, glass needs appropriate translucency and straps need to remain attached. A problem repeated across every destination becomes much more expensive to correct than a problem caught in the master. Keep an original beside the cutout during inspection.
Separate identification, evidence and context
The main view identifies the item. Detail photographs explain construction and finish. Condition photographs record the specific item’s state. Lifestyle photographs explain scale or use. Giving these assets separate roles helps you select the right gallery for each destination.
For example, a secondhand camera kit needs photographs of the actual wear and included accessories. A new handmade bowl benefits from glaze detail and a scale view. A skincare bottle may need label clarity and packaging information. Repeating the same three-quarter view in every slot contributes less than answering these particular questions.
- Maintain a complete contents photo for bundles.
- Shoot a dedicated image for each meaningful color or finish.
- Keep text-free originals when creating optional annotated assets.
- Retain actual-item condition views even when you also create clean cutouts.
Build presets with a written reason
Document dimensions, aspect ratio, color profile, file type and compression for each export. Include why a setting exists: an upload limit, thumbnail behavior or your own visual convention. This prevents a convenient house preset from becoming an invented platform rule.
Use a small representative test set before batch export. Include your tallest product, widest product, finest detail and most difficult edge. Open the resulting files and inspect them at full size. Then upload a few examples through the real destination and review how they display. File validation alone cannot prove that a crop reads well.
Keep rules and publishing checks together
Store the official requirement link with each preset and record when it was reviewed. Platform guidance changes. Google, for example, announces a broader 500 × 500 minimum from January 31, 2027, while recommending larger images. A sharp common master reduces the work needed when an export target changes. Google Merchant Center image_link specification.
Assign a final check to the person publishing the listing: correct variant, included quantity, image order, thumbnail crop and actual storefront or feed status. Photograph preparation and publishing are different stages, and both deserve evidence. The most efficient library is the one you can confidently reuse, update and audit without guessing what a file was meant to show.
Sources and further reading
Sources reviewed October 14, 2026. Check the linked documentation and your product category before publishing.