Merchant Center Image Size Deadline: Your Feed Prep Playbook Before January 31

Google is sending emails this week to Merchant Center advertisers and users about a change that will disapprove product images below 500 by 500 pixels starting January 31, 2027. Warnings started showing up in April 2026, and the enforcement date is now firmly in every ecommerce team’s calendar. If you run Shopping, Performance Max, or free product listings, this is your five-month runway to fix the feed before Google starts pulling products out of ads (Google Merchant Center Help).

The new merchant center image size floor is not a soft nudge. It replaces the old 100 by 100 pixel minimum for non-apparel and the 250 by 250 pixel minimum for apparel with one number, 500 by 500 pixels, across every product category and every marketing method. Google also recommends 1500 by 1500 pixels or larger for best performance. That gap between the enforced minimum and the recommendation is where most agencies are going to lose revenue if they wait.

What the new merchant center image size rule actually says

The change lives in Google’s product data specification. From January 31, 2027, images submitted through the image_link attribute and the additional_image_link attribute must be at least 500 by 500 pixels for every product. Apparel and non-apparel share the same floor. Free listings and paid Shopping surfaces share the same floor. There is no product category exception (Search Engine Roundtable).

Merchant Center has been posting a warning called “Image too small for upcoming enforcement” in the Needs attention view since April 14, 2026. Products that trigger this warning are still serving today. They stop serving on the enforcement date unless the image is replaced. Google says it will auto-optimize some undersized images in the meantime, but the auto-optimization is a safety net for borderline cases, not a permanent fix for a large low-resolution catalog.

The rest of the merchant center image size spec did not change. The file must be under 16 megabytes. The image must be under 64 megapixels. The product should fill 75 to 90 percent of the frame. Watermarks, promotional overlays, and borders on the primary image are still disapprovals with no grace period.

How the merchant center image size change affects your paid Shopping and PMax

If you run Performance Max, this deadline hits harder than it looks. Performance Max leans on the product feed for creative across YouTube, Discover, Gmail, and Search. When Google is short of assets for a placement, it composes creatives from your feed images. A feed full of 400 by 400 pixel product shots today looks fine in a Shopping tab. On February 1, 2027, those same shots stop serving in PMax at all.

The knock-on effect is worse than a simple product disapproval. PMax bidding models tune themselves on the assets they can see convert. When a chunk of your catalog goes dark, the algorithm loses training data for those SKUs and the campaign starts favoring the ones that survived. That shift is invisible in Google Ads for a few weeks, and by the time you notice, your top-line ROAS has already moved.

The safer read is to treat the January 31, 2027 date as a paid media deadline, not a feed hygiene deadline. Our writeup on the AI Max for Shopping playbook walks through how much of the retail bidding stack now depends on feed signal quality. And if your account already runs a hybrid setup around Performance Max, our Performance Max hybrid strategy guide shows why the feed underpins every arm of it.

Audit your merchant center image size warnings this week

Every account should run the same three-step audit before the end of the month. Do this even if you assume your feed is already at 1500 by 1500. The warning population is almost always larger than the eye test suggests, because the images that fail are the ones your team stopped opening years ago.

Step one, pull the warnings list. Open Merchant Center. Go to Products. Open the Needs attention tab. Click View history. Filter for “Image too small for upcoming enforcement.” That gives you the exact SKU list. Export it as a CSV so you have a source of truth outside the UI.

Step two, cross-check the additional_image_link attribute. The enforcement applies to secondary images too, not just the primary image_link. Many teams pushed lifestyle shots into additional_image_link three or four years ago and never revisited them. Those are often the first images to fail, because the primary image usually got updated when the SKU changed.

Step three, segment the population. Anything already at or above 1500 by 1500 is safe indefinitely and needs no action. Anything between the current 100 or 250 pixel floor and 500 is the priority list, because it is passing today and disapproves on the enforcement date. Anything below 500 is a reshoot or a batch-upscale decision. Do not upscale a 200 by 200 pixel thumbnail and expect it to hold up in Shopping. There is no source detail an upscaler can honestly recover from that.

Fix your catalog with new images, not upscaled ones

For the priority list, you have two clean options. The first is to replace the file with a real high-resolution image from your product library. Most brand teams have 2000 by 2000 pixel or larger master files somewhere. Route those to Merchant Center directly through your product feed, not through the smaller web-optimized copy your site uses. Web page images are often compressed and downsampled for load speed. Merchant Center wants the higher-resolution master.

The second option is a controlled reshoot for the SKUs that never had a proper master file. This tends to hit older long-tail SKUs, private-label items, and dropshipped products where you only ever received a thumbnail from the supplier. A phone-camera reshoot at 3000 by 3000 pixels on a plain white sweep runs about $2 to $5 per SKU in labor and gives you an image that clears the recommendation, not just the minimum.

Where you truly cannot reshoot, AI image tools can generate a compliant replacement, but the disapproval risk is real if you get the metadata wrong. Google requires AI-generated images to carry IPTC DigitalSourceType metadata. Skip it and you get a policy disapproval. Our AI image generation tools for ads guide covers the disapproval-safe workflow, including which generators embed the correct metadata by default.

Rebuild your feed pipeline around the merchant center image size floor

The audit fixes today’s population. The pipeline change stops the problem from coming back. Every new SKU your team ships should hit Merchant Center at 1500 by 1500 pixels or larger, not at the 500 by 500 floor. Building to the floor is what gets you disapproved the next time Google raises the bar.

Two workflow changes buy you insurance. First, add an image dimension check to your new-product upload script. If your feed manager is Shopify, Feedonomics, GoDataFeed, or a custom cron, wire a check into the export that flags any file below 1500 by 1500 pixels. Do not let it silently pass. Second, split image_link and additional_image_link into different QA lanes. Additional images are where the pipeline drift shows up first, because they are usually populated by a rule that fires without human review.

If your team runs multiple Merchant Center accounts across brands or clients, the audit workload multiplies fast. Our Merchant Center for agencies writeup covers the account architecture that keeps this manageable at scale, and our Content API migration guide walks through the feed plumbing you should already be on if you migrated during the sunset. Those two moves together take a two-week audit down to a three-day project.

Your 90-day rollout plan for the merchant center image size deadline

Five months sounds like a lot of runway. In practice, most agencies need every week of it, because sourcing high-resolution files at scale involves supplier requests, reshoot logistics, and DAM cleanup. Here is the plan our team is running for retail accounts through the end of the year.

Days 1 to 7: pull the warning list from every Merchant Center account you touch. Export CSVs. Cross-tab against the SKUs that drive 80 percent of Shopping revenue. Those SKUs are the ones you fix first, because a disapproval there is a revenue event, not a feed hygiene event.

Days 8 to 30: replace the top-revenue SKU images with real high-resolution files. Ship the changes through your normal feed cadence and monitor for optimized-image warnings, which now go away as you replace the source. Track the disapproval risk drop in Needs attention weekly.

Days 31 to 60: work the long tail. Batch reshoots by supplier if you can, because a single half-day photo session usually clears 40 to 80 SKUs. For SKUs with no source file and no supplier cooperation, decide on delisting versus AI-generated replacement. Delisting is often the cleaner move for zero-margin SKUs that never earned their shelf space.

Days 61 to 90: rebuild the pipeline. Wire the 1500 by 1500 pixel check into your feed export. Add QA for additional_image_link. Document the process for the next platform spec change, because Google runs one of these every 18 to 24 months. If you need a partner to run this without pulling your top strategists off client work, our team helps ecommerce agencies rebuild their feed pipeline. Book a walk-through on our free consultation page and we will map the audit to your specific stack.

Google gave you a real deadline this time, with warnings running for nine months before enforcement starts. The teams that lose Shopping revenue on February 1, 2027 will be the ones that saw the warning banner and treated it like a suggestion. Let’s Grow!