Product images under 500 x 500 pixels leave Google on 31 January 2027: how to find and fix yours

If you run Shopping ads, Google has probably told you about this more than once. It emailed Merchant Center users in August that the minimum size for product images goes up to 500 x 500 pixels, put a notice at the top of its image help page, and by late September had labelled that notice "important" as well.

The reason for the noise is simple. On 31 January 2027, every product whose image is too small stops being approved, in every category, unless Google has optimized that image itself. A disapproved product doesn't show in Shopping ads, Performance Max or free listings, however good the campaign around it is.

Most stores have big product photos, so it's tempting to assume this doesn't apply to you. It often does, because Merchant Center doesn't look at the photo on your product page. Here's what changes, why a store with big photos can still fail, how to find the products that are affected, and how we'd fix them before January.

The short version

• From 31 January 2027, images in [image_link] and [additional_image_link] must be at least 500 x 500 pixels for every product. Until then the minimum is 100 x 100 pixels, or 250 x 250 for clothing.
• Products whose main image is smaller will be disapproved, so they drop out of your ads and listings. Google hasn't said how strictly it treats extra images, so treat them the same.
• Merchant Center already warns about products that pass today's minimum but not the new one, with "Image too small for upcoming enforcement", or "Image resolution optimizations applied" where Google has stepped in.
• The usual culprit isn't the photo but the resized copy your feed sends: Google checks the exact file at the URL in your feed.
• Google may serve an optimized version of some small images itself, but it hasn't said which ones. Treat that as a safety net, not a plan.
• 500 x 500 is the floor. Google recommends 1500 x 1500 pixels or larger, and that's the size we'd aim for.

What Google is changing on 31 January 2027

Google announced the new minimum in its product data specification update for 2026, the yearly list of changes to what a product feed must contain.

Today's rules are lenient. Google's page on how to fix "Image too small" says that until 31 January 2027 you can use an image of at least 100 x 100 pixels for most products, and 250 x 250 for clothing. That's small enough for a thumbnail to pass. After the date, one minimum applies to everything: 500 x 500. The image_link page already lists it as the size requirement, next to a maximum of 64 megapixels and 16 MB.

Until the deadline, an image between the old and the new minimum gets a warning, not a disapproval. Google's own pages don't agree on when those warnings started: the specification update says 14 April 2026, while the "Image too small" page says July 2026 for images that pass today's minimum. Either way, if your account has the warning now, it will have disapprovals on 31 January.

The rule has also become stricter relative to Google's other image checks. In October it emerged that Google no longer lets the "Low image quality" issue block products: a blurry image now only gets a note that the product "will continue to show in ads and free listings". A small image gets no such leniency: low quality no longer blocks a product, a small image will.

Why big product photos still fail the 500 x 500 check

Most stores shoot product photos far above 500 x 500 pixels, and the warning still shows up. The reason is almost always the same: Google downloads the exact file at the URL in your feed, and that file is often a resized copy made by the shop system, the feed app or an image service.

The feed sends a catalogue size. Shop systems keep several sizes of every image. WooCommerce, for example, registers a 300-pixel size for product grids, a 600-pixel-wide size for product pages and a 100 x 100 gallery thumbnail. A feed plugin set to the grid size sends 300-pixel images, which pass today and fail in January.

Wide images fail on height. The minimum is 500 pixels on both sides. A product-page image that is 600 pixels wide but only 400 high, because the photo is landscape, fails, even though "600 pixels" sounds safe.

Variants have their own images. Google asks for a distinct image for each variant, and each one is checked on its own. A small image attached to one colour or size fails while the main gallery passes, so the warning hits some variants of a product and not others.

Old and supplier images. Images uploaded years ago are often the small ones, and catalogue images from a manufacturer or dropshipping supplier arrive, as feed platform Feedoptimise puts it, "at whatever size the supplier decided".

An image CDN or optimizer. A service that serves a scaled-down image to whoever fetches it serves one to Google too.

So the question isn't whether your photos are big enough. It's which file Google gets when it follows each URL in your feed.

How one feed setting can cause most of the warnings: an example

Take an online store with 1,200 products, most of them photographed at 2000 x 2000 pixels. Its feed plugin is set to the 300-pixel catalogue size. Today all 1,200 products are approved, because 300 pixels clears the 100-pixel minimum. Merchant Center shows "Image too small for upcoming enforcement" on all 1,200.

The owner switches the feed setting to the full-size original. After the next sync, 1,080 products pick up their 2000-pixel photos, and within a few days the warning goes away. That leaves 120: 80 products whose images came from a supplier at 400 x 400, and 40 variants with a small image of their own.

One setting fixed nine in ten products. The remaining tenth needs new images, and that's where the real work is. The numbers are made up, but the shape is typical: most of the list is one cause, and the rest is a handful of products somebody has to look at.

What Google's own image optimization does and doesn't promise

Google says it will "begin optimizing some images that are smaller than 500 x 500", and that "these optimized images will meet the new image requirements and will prevent product disapproval without any action from you". Products it has changed carry the warning "Image resolution optimizations applied". If you'd rather use your own image, you submit one larger than 500 x 500 and it replaces Google's version.

That sounds like the problem solves itself. It doesn't, for three reasons. Google says "some images", and its "Image too small" page says it "may" serve an optimized version "when possible". Feedoptimise, which sells feed and image tools and so has a stake in you fixing images, makes a fair point anyway: Google "has not published the criteria behind that optimisation, and the behaviour can change before enforcement". And an image Google has optimized from 300 pixels won't look like a real 1500-pixel photo.

We'd treat it as a safety net for the products you miss, not as the plan.

How to find the products Merchant Center will disapprove

Google has already done the counting. Its "Image too small" page gives the route:

1. In Merchant Center, go to Products and open the Needs attention tab.
2. Select View history and look at the orange warnings on the right for Image too small for upcoming enforcement, and for Image resolution optimizations applied.
3. Select View fix, then Download impacted products, to get the list.

Two things to know about that list. Products that already fail today's minimum carry a different issue, plain Image too small, and they're disapproved now, not in January. And the list may not say which of a product's images is the small one, so for a product with several images, check the main image and the extra ones.

How to fix undersized product images

Fix it in the shop, not in Merchant Center. Replace the image where the product lives, in Shopify, WooCommerce or whatever system feeds Merchant Center, and let it sync. A supplemental data source can override an image link, but then the shop and Merchant Center disagree, and the next person to touch the shop won't know.

Check the image size your feed sends first. In your feed app or plugin, find the setting that picks the image size and set it to the original or full size. As the 1,200-product example shows, this one setting often clears most of the list.

Go through the variants. Open the affected products and look at the image attached to each variant, not only the gallery.

Replace small originals with real photos. Where the original really is small, you need a new image: re-shoot, or ask the supplier for the high-resolution file. Google's Product Studio, in Merchant Center and in the Google & YouTube app on Shopify, can increase the resolution of an image, but Google's image rules say an image made with generative AI must keep metadata that says so, such as the IPTC DigitalSourceType tag.

Give the new image a new URL. Google says that if you change an image but keep the same URL, it "may take up to 6 weeks to detect and then crawl the new image". With a new filename and URL, it's usually checked within 72 hours.

Check the result in Merchant Center. Google says changes can take 24 to 72 hours to show on the Needs attention page, so give it a few days before you assume a fix didn't work.

Why 1500 x 1500 matters more than the 500 x 500 minimum

The deadline is the reason to act now, but it isn't the most important number. Google's own wording on the image_link page: "to ensure best performance in all listing formats, we recommend that you provide images 1500x1500 pixels or above."

Shopping ads are the image. In the search results, the Shopping tab and Performance Max placements, the picture is most of what a shopper sees before the click, and Google shows it on screens far bigger than 500 pixels. Barry Schwartz of Search Engine Roundtable called the 500 x 500 minimum "way too small", and we agree: it keeps a product in your ads, but a 500-pixel image scaled up on a large screen looks soft next to a competitor's sharp one. The ecommerce agency Common Thread Collective makes the same point: "The gap between the minimum and the recommended size is where most of the real performance work lives."

So if you're re-shooting or replacing images anyway, do it once, at 1500 x 1500 or more.

And a product that's disapproved on 31 January doesn't stop quietly. It stops selling, in the middle of the January sales, while the campaign around it keeps running on whatever products are left.

Where the usual 500 x 500 fixes fall short

The warning list lags behind your shop. Merchant Center checks images when it fetches them, so a product you fixed yesterday may still carry the warning today, and a product whose image shrank last week may not carry it yet. Download the list again a week after your fixes.

AI upscaling can change the product. Feedoptimise warns that generative models "can shift logos, stitching, textures or proportions", and Google disapproves images that don't show the product as it is. If you upscale, check a sample against the originals before you run the whole catalogue.

Google's dates and details may still move. Google's own pages already disagree on when the warnings started, and how much its optimization covers is Google's call. Plan for the strict reading: every image under 500 x 500 on both sides is disapproved on 31 January.

Size isn't the only image rule. A big image with a "Free shipping" badge, a watermark or a "Coming soon" placeholder is still disapproved. If you're replacing images anyway, replace them with clean ones.

How to get every product image ready before 31 January

Download the list this week. Needs attention, View history, the "Image too small for upcoming enforcement" warning, Download impacted products.

Fix the feed setting before anything else. If your feed app sends a resized copy, switch it to the original, then see how many products are left.

Fix the rest at the source. New images in the shop for the products that really have small originals, variants included, each with a new image URL.

Aim for 1500 x 1500. The minimum keeps the product in your ads. The recommendation makes it look good there.

Check again a week later. The warning should be gone from the products you fixed, and nothing new should have appeared.

If you use Bavian, it reads the status of every product in your Merchant Center feed and shows it on its Shopping page, with Google's reason when a product is not eligible. With Autopilot on and Bavian running your Shopping campaigns, it replaces an image Google refuses as too small with the image the product page itself declares, if that one is at least 500 x 500 pixels, for 14 days at a time and again while Google still refuses the shop's own, so a resized copy in the feed doesn't keep the product out of your ads while the feed setting gets fixed. Bavian acts on Google's refusal, not on the warning before 31 January, and it can't make a small photo bigger: where the shop only has a small original, the new photo is yours to add. We also covered the year's other Shopping rule changes in Starting Google Shopping from scratch and in The 5 Google Ads mistakes Bavian finds in almost every online store.