Google's 500 x 500 Image Deadline: Why Your Merchant Center Number Is Wrong

On January 31, 2027, Google starts removing product listings whose main photo is smaller than 500 pixels by 500 pixels. That part is public, dated, and confirmed in Google's own documentation. Here's the part almost nobody has checked: the number sitting in your Merchant Center dashboard right now is very probably not telling you how many of your products are affected.

In August I measured a North Texas retailer's catalog against the new rule. Merchant Center showed one product with an image problem. The real count was 1,086. Both numbers were accurate. They were answering different questions, and the difference between them is a quarter of the catalog.

If you sell online and you have glanced at your account and felt fine, this is worth twenty minutes of your time.

The short version

• Google raises the minimum product image size to 500 x 500 pixels on January 31, 2027. Below that, your main image gets the product disapproved.
• The "Image too small" count on your dashboard measures today's rule, not the 2027 one. Today's minimum is 100 x 100 for most products, so a 386 pixel image passes now and fails later.
• The warning that actually matters is called "Image too small for upcoming enforcement" and it sits four clicks deep, under Products, Needs attention, then View history.
• Google is also quietly resizing some undersized images for you, which prevents disapproval, but it has not published which images qualify and says the behavior can change.

What Google is actually changing, and when

Google is raising the minimum resolution for product images to 500 x 500 pixels across all product categories and all marketing methods. Enforcement begins January 31, 2027. Google's own recommendation is to go well beyond the floor and submit images at 1500 x 1500 or larger, which matters because the floor is a compliance threshold, not a quality target.

One detail gets reported wrong constantly, and it changes the size of the job. The requirement covers both the main product image and your additional images, not just the main one. The consequences differ, though, and that tiering is the useful part:

• Main image below 500 x 500. The product gets disapproved. It stops showing on Google.
• Additional image below 500 x 500. That image simply does not get shown. The product survives.

So your main images are the emergency and your secondary images are housekeeping. Plan the work in that order and the deadline gets a lot less frightening.

Why the number in your dashboard is probably wrong

Here's the trap, and it's an honest one rather than anything sneaky on Google's part.

Merchant Center has an issue called "Image too small." Most owners find it, read the count, and reasonably conclude that's their exposure. But that issue measures today's minimum, and today's minimum is much lower: at least 250 x 250 pixels for apparel, and at least 100 x 100 pixels for everything else, right up until January 31, 2027.

Think about what that means for a 386 pixel product photo. It clears 100 x 100 with enormous room to spare, so it isn't a problem today and doesn't appear in that count. It also misses 500 x 500, so it becomes a disapproval in 2027. It is simultaneously fine and doomed, and the headline number on your dashboard only knows about the first half.

A catalog can be fully approved today and still have a quarter of it scheduled to go dark, and nothing on the front page of your account will say so.

This is why I would push back gently on checking your account and moving on. Your dashboard isn't lying to you. It's answering the question you asked, which is whether you're compliant now.

Where the real warning is hiding

Google does warn about the future rule. It started issuing those warnings on April 14, 2026, and its documentation says you will see them on images that clear the current minimum but fall short of 500 x 500 from July 2026 onward. Credit where it's due. The problem is purely one of discoverability.

The warning is a separate item with a separate name, "Image too small for upcoming enforcement," and finding it goes like this:

1. Open Products in Merchant Center.
2. Select the Needs attention tab.
3. Select View history.
4. Read the orange warnings down the right hand side and look for "Image too small for upcoming enforcement."
5. Use the filter icon to pull the list of affected products.

Four steps and a color cue. How many small business owners do you think have run that path? In my experience the answer is close to none, because nothing prompts you to. The front page of the account says you are approved, and it's right.

If you would rather not go spelunking through Merchant Center, we measure catalogs for a living and can tell you the real number in a day.

Get your catalog measured

The part Google hasn't quantified

There's a second wrinkle, and it cuts the other way. Google has said it will begin automatically optimizing some images that fall below 500 x 500, and that these optimized versions will prevent disapproval without any action from you. There's a corresponding notice, "Image resolution optimizations applied," showing which of your products currently benefit.

That's genuinely good news. It's also unfinished information. Google has not published the criteria for which images qualify, and it has said the behavior can change before enforcement. Nobody outside Google can currently tell you what share of a given catalog is quietly covered.

So treat any raw failure count, including one from us, as an upper bound on your risk rather than a forecast of your losses. That's the honest position, and it's a better place to plan from than either extreme. Don't panic at the big number, and don't lean on Google to fix it for you either.

What this looked like on a real catalog

Numbers on a real store are worth more than the policy summary. This is a North Texas retailer with a large catalog, measured on August 22, 2026 from Google's own Merchant Center product export rather than from the website, so these are feed figures.

Naming the denominator matters here, because there are three of them and they give three different answers:

• 4,247 products in the feed. That's the population.
• 1,086 below 500 x 500, or 25.6 percent. That's the raw exposure.
• 931 of those are in stock and therefore actually earning. That's the number that would hurt.
• 1 product flagged under the current rule. That's what the dashboard showed.

Now the interesting bit. Of those 1,086 failures, 883 were exactly 386 pixels wide. Not roughly. Exactly. That's 81 percent of the whole problem sharing one identical width, which points at a single historical event rather than years of sloppy uploading. In this case a batch of uploads from July 2022 had been written at a hard cap.

Why does that matter to you? Because a clustered failure is a cheap failure. One consistent cause usually means one bulk fix, and 386 to 500 is only a 1.30 times enlargement. Across the whole failing set, 784 products needed between 1.25 and 2 times their current size, 229 needed 2 times or more, and only 73 needed less than 1.25 times. If your own failures cluster the same way, your quote should be nothing like the raw product count suggests.

One more finding from the same pass, and it's the one that surprised the owner most: 23 in-stock products had a main image URL that returned nothing at all. The file was simply gone. That isn't a 2027 problem. Those products have no image on Google today.

How to measure your own catalog

You do not need us for this, and you shouldn't have to wait on anyone. There are three routes, cheapest first.

1. Read the warning Google already gave you. Follow the five steps above. This is free, it's authoritative, and it's the only route that reflects Google's auto-optimization. Start here.

2. Export your feed and measure it. In Merchant Center you can download your product export, which includes the image URL for every product. If you're comfortable in a spreadsheet, that list plus any bulk image-dimension checker gives you a real per-product answer against your actual feed.

3. Spot check by hand. Open ten of your oldest product pages, right click the main photo, and look at its dimensions. If several come back with an identical width, you have likely found a batch event like the 386 pixel one above, and you can stop guessing and go looking for what caused it.

An honest caveat on anything measured from a website, ours included. Your Merchant Center feed is not public, so measuring product pages is a proxy for measuring the feed, not the same thing. Most feed tools pass the main image URL through unchanged, which makes it a fair proxy, and on the retailer above we confirmed that was true. But it's an assumption until it's checked, and we got burned by exactly that shortcut once before. If someone hands you a catalog number without telling you which of the two they measured, ask.

What the fix actually costs

Almost always less than the count implies, for the reason above. The sequence that keeps the bill down:

1. Find the cause before you price the fix. If most of your failures share a width, one import or migration did this, and you may be able to undo it in a batch.
2. Go looking for the originals. A pre-incident backup of your uploads folder, or your supplier's current catalog. For standard catalog goods rather than one-off product shots taken in-house, supplier assets are a realistic source and usually free.
3. Fix main images first, additional images second. Only the first group causes disapprovals.
4. Measure the short side, not the width. This one bites people with tall or wide products. A 3 to 5 ratio image 900 pixels wide is only about 535 tall, so a batch that looks compliant by width can still fail on height.
5. Treat upscaling as a fallback, not a plan. Enlarging a 386 pixel photo will clear the pixel threshold, but Google judges image quality separately and a soft upscale on a product photo is visible. Test a handful before betting the catalog on it.

You have until January 31, 2027, which sounds like plenty. It is plenty, if the answer turns out to be a bulk re-import. It is not plenty if the originals are gone and you need a supplier to re-send a few thousand images. That's the real reason to run the check now rather than next summer: you're not buying time to do the work, you're buying time to find out which job you have.

---

Frequently asked questions

When does the 500 x 500 requirement actually take effect?

Enforcement begins January 31, 2027. Google announced it in April 2026 and has been issuing advance warnings since then, so the rule itself is not new information. What changes on that date is the consequence: main product images below 500 x 500 pixels stop being approved and the products stop showing on Google.

Does this apply to all my product photos or just the main one?

Both, but the penalties differ. If your main image is below 500 x 500, the product gets disapproved and disappears from Google. If an additional image is below the minimum, that specific image just is not displayed and the product itself is fine. Fix your main images first, then work through secondary photos as ordinary housekeeping.

My Merchant Center account says everything is approved. Am I safe?

Not necessarily. The standard "Image too small" issue measures today's minimum, which is 100 x 100 pixels for most products and 250 x 250 for apparel. An image can clear that easily and still fall short of 500 x 500. Check the separate "Image too small for upcoming enforcement" warning under Products, Needs attention, then View history.

Will Google fix my small images for me?

Sometimes. Google has said it will automatically optimize some images below 500 x 500, which prevents disapproval with no action from you, and a notice shows which products benefit. But Google has not published which images qualify and has said the behavior can change before enforcement. It is not something to build a plan around.

Can I just enlarge the images I already have?

Technically yes, and it will clear the pixel threshold. The risk is that Google assesses image quality separately from image size, and an upscaled product photo often looks soft or blurry to a shopper. Try it on a small group and look at the results honestly before applying it across a catalog. Re-sourcing originals is the better answer where it is possible.

We handle product feeds, inventory and marketplace listings for retailers across Hunt County and North Texas. If you want to know your real number before this becomes urgent, let's take a look together.

Talk through your catalog

Not ready to talk to anyone? That's completely fine. Run the five-step check in your own account, write the number down, and put a reminder in your calendar for the autumn. You can also browse our free tools or read how we approach search visibility for local businesses. The worst outcome here is finding out in February 2027, and that outcome is entirely avoidable.

Sources

1. Google Merchant Center Help, Merchant Center product data specification update 2026, retrieved 2026-08-31. support.google.com
2. Google Merchant Center Help, Image link [image_link], retrieved 2026-08-31. support.google.com
3. Google Merchant Center Help, How to fix: Image too small, retrieved 2026-08-31. support.google.com
4. Search Engine Roundtable, Google Merchant Center Product Images Minimum Size Going To 500 x 500 Pixels, 2026-08-24, retrieved 2026-08-31. seroundtable.com
5. PPC Land, Google blocks product images under 500 x 500 pixels from 31 January 2027, retrieved 2026-08-31. ppc.land
6. ScatterBranch Digital Marketing, product image compliance audit of a North Texas retailer, measured from the Google Merchant Center product export, 2026-08-22. Client identity withheld.