Google Merchant Center Image Requirements for 2027
Prepare your product-photo workflow for Google’s announced 500 × 500 minimum. Separate image size, background cleanup and feed updates before changing a whole catalog.
In this guide
What is changing and when
Google announces a minimum product-image size of 500 × 500 pixels from January 31, 2027, and recommends 1500 × 1500 or larger. These dimensions are not a guarantee of approval. Check the official image_link specification for current requirements. This guide was checked on September 9, 2026.
Keep dimension fixes separate from background cleanup. Removing a background does not create missing detail in a small product photograph.
Start with a small inventory of originals
Create a worksheet with one row per product or variant. Record the original filename, dimensions, current image URL, replacement filename and review status. Choose three representative products first: a dark item, a pale item and a reflective item.
Open the largest original you have. Compare its label and texture with the image currently used in your shop. A thumbnail enlarged to a bigger canvas can meet a pixel count while still looking soft; ask the supplier for a better original when necessary.
Clean the background only when it needs it
First check whether the product is fully visible and accurately represented. If an uneven wall distracts from an otherwise usable photograph, the white-background workflow can help. Choose Background, Color and white in the editor, then inspect the downloaded file.
Google also offers Product Studio, including background removal. If that is available in your account and solves the problem, you can use it. Choose a workflow based on your actual images and the editing steps you need.
Review the image separately from the product feed
Use two review passes. For the image, check the item, variant, outline, readable details and final dimensions. For the feed, check that the product row points to the correct final image. A beautiful replacement attached to the wrong variant is still the wrong listing.
Keep an untouched original and a clearly named edited copy. Before processing hundreds of files, have another person compare a few samples with the real products. Where the result needs retouching, record the issue instead of silently substituting another item’s photograph.
Update a pilot group and watch its status
Update a small group through your usual shop or feed workflow and check Merchant Center afterward. Save the exact issue text if a product remains rejected. An image-size problem, an inaccessible image URL and an incorrect product image need different fixes.
Google’s image-too-small help page explains that particular issue. Use the issue-specific guidance rather than repeatedly editing the background for a problem unrelated to it.
A repeatable handoff for the rest of your catalog
Once the pilot looks right, keep the same original-to-output naming scheme and a record of which product rows were updated. Review a sample of each new batch. A short checklist is easier to repeat than relying on someone to remember every decision.
Need help preparing the images or organizing the catalog? Send an enquiry with the approximate image count, where you sell and the problem you are seeing. Do not include account passwords or private customer data. We can discuss the photo or catalog work before you commit to a larger job.
Frequently asked questions
Does every product photo have to be square?
The announced minimum gives a minimum width and height; it is not a blanket instruction to crop every product into a square. Review the current specification and preserve the whole item.
Can background removal fix a small image?
It can change the background, but it cannot recover detail that was absent in the original. Find a larger source when the product is too small or blurry.
Will BGClear guarantee Merchant Center approval?
No. Approval depends on the product, image, feed and current platform requirements. Review the specific issue in Merchant Center.