Table of Contents
The Enforcement Timeline
Google has announced a phased rollout of a stricter minimum product image size requirement. Since July 2026, merchants have begun seeing warnings in Merchant Center on product images that are larger than the previous minimum but smaller than the new 500x500 pixel threshold — these are visible today as informational flags, not disapprovals. Hard enforcement, where images below 500x500 pixels will actually be disapproved rather than just flagged, begins January 31, 2027. That gives merchants a runway of several months between the first warnings and the point where undersized images start actively losing Shopping eligibility.
| Date | What happens |
|---|---|
| July 2026 | Warnings begin appearing for images between the old minimum and 500x500px |
| Now through Jan 2027 | Grace period — warnings visible, no disapprovals yet |
| January 31, 2027 | Enforcement begins — images below 500x500px are disapproved |
It is unusual for Google to give this much advance notice with visible warnings before enforcement. Merchants who ignore the warning now and wait until January 2027 to react will likely be doing a rushed, reactive fix across their whole catalog at the same time as many other merchants — start the audit now while there's no time pressure.
Why Google Is Raising the Minimum
Higher minimum image resolution requirements generally track two things: the increasing size and pixel density of the surfaces where Shopping ads and free listings actually render (larger, higher-DPI mobile screens, richer visual Shopping formats, image-forward placements like Shopping tabs and visual search results), and an ongoing push to improve the baseline quality of the shopping experience as more surfaces lean on product imagery for engagement — including newer AI-driven shopping and visual search features that tend to be less forgiving of low-resolution source images than a simple thumbnail grid was. A 500x500px floor is still a relatively modest bar by modern photography standards (most smartphone cameras produce images many times that resolution by default), which suggests this is mainly targeting older product photos, scraped supplier images, or manually resized thumbnails that were adequate under the old minimum but look visibly soft on today's higher-resolution rendering surfaces.
Finding the Warnings in Your Account Now
The warnings are visible in the Merchant Center diagnostics area, typically under the item-level issues view, with wording along the lines of "image too small" or a resolution-specific warning distinct from the harder "image too small" disapproval reason that has existed for smaller absolute minimums for years. Because this is a two-tier system right now — a genuinely too-small image (below the older hard minimum) is disapproved today already, while an image in the new warning band is only flagged — filter your diagnostics view specifically for the warning-level issue rather than assuming a clean "no disapprovals" status means no image work is needed.
Some merchants check only their top-line "product status" summary and miss item-level warnings that don't yet affect approval status. Go into the diagnostics section specifically and look for size-related warnings at the individual product level, not just the account-level health summary.
Auditing Your Catalog for Undersized Images
Beyond checking Merchant Center's own warning flags, it's worth running an independent audit, since Merchant Center's diagnostics can lag behind a full crawl of your entire catalog, especially for larger inventories. A practical approach: export your product feed, pull the image_link value for every active product, and run a batch script that fetches each image's actual pixel dimensions (a simple script using a standard image library can process thousands of URLs in a reasonable amount of time). Flag anything under 500x500px for remediation, and separately flag anything under the older hard minimum that should already be disapproved if it somehow isn't.
| Image source | Typical risk level |
|---|---|
| Original product photography, unedited | Low — most modern cameras exceed 500x500px by a wide margin |
| Manufacturer/supplier-provided images (especially dropshipping) | High — often small, compressed, or watermark-cropped to reduced sizes |
| Manually cropped or resized thumbnails from years ago | Medium-high — legacy thumbnails built for an older, smaller minimum |
| Images scraped from a marketplace listing rather than sourced originally | High — scraping often nets a display-optimized (small) version, not the original |
Fixing Images at Scale
For a catalog with more than a handful of flagged products, fixing this one image at a time is impractical — prioritize by traffic and revenue rather than trying to fix everything simultaneously. For flagged products that already have a higher-resolution source image somewhere (your original product photography folder, your platform's media library at full resolution, or a supplier's higher-resolution asset that wasn't originally used), the fix is simply swapping the feed's image_link to point at the better source. For products where no higher-resolution source exists at all, this is a signal that new photography or a supplier-provided higher-resolution asset is genuinely needed — resist the temptation to just upscale a small image artificially, since upscaling doesn't add real detail and can look worse under close inspection than the original, and does nothing to address the underlying image-quality goal behind this policy change in the first place.
Platform-Specific Notes
- Shopify: Shopify's own image storage generally preserves full-resolution uploads, but check theme settings and any image-optimization app that might be auto-compressing or resizing images below what you originally uploaded before they reach the feed.
- WooCommerce: WordPress's built-in media library can generate multiple resized versions of an uploaded image; confirm your feed plugin references the original full-size upload rather than an auto-generated smaller "thumbnail" or "medium" size.
- Marketplaces re-syndicated to your own feed (Etsy, eBay, Faire): images pulled through an API sync from another marketplace are a common source of undersized images, since some marketplace APIs default to serving a smaller display-optimized image rather than the seller's original upload.
Historical Context: How Minimums Have Shifted Over Time
Google has adjusted minimum image size requirements for Shopping several times over the years, generally in the same direction — upward — as rendering surfaces and typical device screen resolutions have improved. Each prior adjustment followed a broadly similar pattern to what's happening now: an announcement, a warning period where flagged-but-not-yet-disapproved images were visible in diagnostics, and then a hard enforcement date. Merchants who lived through a prior minimum increase and treated the warning period seriously tended to avoid a scramble; merchants who waited for enforcement to actually start generally found themselves fixing images under time pressure while also dealing with whatever disapproval volume already existed elsewhere in their account. There's no reason to expect this cycle to play out differently.
It's also worth noting this specific change arrives close to the same September 2026 window as the Shopping policy consolidation and the new adult-content labeling requirement — three distinct updates landing in a similar timeframe, which increases the odds a merchant handles one update carefully and overlooks another simply due to attention being split across all three at once. Track them as three separate checklist items rather than one combined "September 2026 changes" bucket to reduce that risk.
Frequently Asked Questions
Will my product be disapproved immediately if it's under 500x500px right now? Not yet — as of this writing, images below the new threshold but above the older hard minimum show a warning only, with disapproval enforcement beginning January 31, 2027.
Does the 500x500px minimum apply to all image types, including lifestyle and additional images? Google's requirement language centers on the primary product image; check current Merchant Center specifications for whether additional image slots carry the identical threshold, since requirements for supplementary images have historically been slightly more lenient.
Can I just upscale my small images with AI upscaling tools to hit the pixel minimum? Technically this can satisfy the pixel-dimension check, but it doesn't address the underlying visual-quality goal and can look artificial on close inspection — sourcing a genuinely higher-resolution original is the more durable fix where possible.
How do I check my whole catalog quickly without manually opening every image? Run a free scan at gmcunbanned.com, or export your feed and script a bulk pixel-dimension check against every image_link value.
Is this the same as the general "image too small" disapproval that already exists? No — that disapproval reason has existed for a separate, lower absolute minimum for years; this is a new, higher threshold currently in its warning phase ahead of the January 2027 enforcement date.
Should I prioritize best-sellers or the full catalog when fixing images? Prioritize by traffic and revenue contribution first if your catalog is large — a best-seller losing eligibility in January 2027 is a materially bigger problem than a slow-moving SKU, and fixing the highest-impact products first gives you the best return on a limited remediation window.
Not Sure How Many Products Have Undersized Images?
Run a free scan at gmcunbanned.com to check your catalog against the new 500x500px minimum before enforcement begins in January 2027.
Run Free GMC Scan →