Guide · Google Merchant Center images
Google Merchant Center image requirements guide
Google's product image requirements with the dates attached: the legacy 100×100 and 250×250 minimums, the 500×500 requirement from 2027-01-31, the official sources that disagree about when warnings started, the 64 MP and 16 MB limits, and how each one is actually tested.
64 versioned rules across 3 rulesets · ruleset 1.0.0 · rule data verified 11 November 2026 · no account needed for a local run
Field
image_link (and additional_image_link)
New minimum
500×500 from 2027-01-31
Warning phase
From 2026-04-14 (checker policy; sources conflict)
Last verified
11 November 2026
1. What the requirement is
Google publishes a single image specification for the main product image: a minimum pixel size, a maximum pixel count, a maximum file size, a set of accepted file formats, a rule against animation, and a requirement that the file actually decode as an image. On top of that sit content expectations that no metadata check can settle — no promotional overlays, no watermarks, no placeholders, no wrong product.
The minimum pixel size is the part that changed. Until 2027-01-31 there are legacy minimums that depend on the product category; from 2027-01-31 there is one minimum for every product image.
2. Which field it applies to
- image_link — the main product image for the item.
- additional_image_link — optional extra images; each one must still be a valid absolute URL and comply with the same specification.
- The requirement is per item, not per account: a single file cannot be evaluated for a whole catalog at once by the platform.
3. Required, conditional and recommended
A decodable image in an accepted format, at or above the applicable minimum size, at or below 64 megapixels and 16 MB, and not an animated GIF.
The legacy 100×100 versus 250×250 split applies only until 2027-01-31 and only when the product category is known. The 500×500 destination requirement for YouTube Shopping Ads applies only when that destination is explicitly selected.
1500×1500 or larger. This is advice, not a threshold, and a smaller image is not rejected for it.
Content policy, and the provenance of a generative-AI image. Both are reported as Needs review; the checker never infers creation method from how an image looks.
4. Effective and warning dates
2027-01-31 — 500×500 becomes the minimum for every product image. The legacy category split stops applying.
Warning phase — two official Google pages give different start dates: the dated 2026 annual product-data update says 2026-04-14, while the dedicated image troubleshooting article says July 2026. The checker uses the earlier date (2026-04-14) as its own conservative policy, so it never misses a warning a merchant might already be seeing. That is a checker choice, not a claim that Google warned every account from that day.
Every run records the date it used. The same image can legitimately produce a warning in one run and an error in the next — the rule changed, not the file.
5. Pass and fail examples
- Pass, before 2027-01-31: a 1200×1200 JPEG, 480 KB, non-animated, in a non-clothing category — above the legacy minimum, below the 1500×1500 recommendation, so it passes the requirement and carries an advisory note only.
- Fail, before 2027-01-31: a 90×90 PNG for a non-clothing product — below the legacy minimum, so an error now rather than a warning.
- Conditional: a 200×200 image for a product whose category cannot be determined. Neither threshold can be asserted confidently, so the result is Needs review, not a guessed error.
- Warning, during the warning phase: a 420×680 JPEG for a non-clothing product — above the legacy minimum, below 500×500, so a warning until 2027-01-31.
- Fail, from 2027-01-31: that same 420×680 JPEG — 500×500 now applies to every category, so an error even though it passed a year earlier.
- Fail: a 2000×2000 file of 18 MB — the pixel requirement is satisfied but the file-size limit is exceeded.
- Fail: a .png file whose bytes are actually a WebP, or an HTML error page — the extension is not evidence; the decoded format and decode success are.
- Fail: an animated GIF, even when its dimensions are fine.
- Needs review: a 3000×3000 image covered in promotional text. No metadata check can see this; the rule reports that a human must look.
6. How the checker tests it
- The image is fetched only after you explicitly opt in to remote checks, from the public URL in your row, with bounded size and timeouts and an honest User-Agent.
- Format and dimensions come from decoding the bytes, never from the file extension or the server’s Content-Type header.
- Animated GIF is detected from the decoded frame structure, not from the file name.
- File size is measured on the transferred bytes; boundary cases between the decimal and binary reading of "16 MB" are reported as ambiguous rather than forced into a verdict.
- The minimum-size rule is evaluated against the run’s as-of date, with the warning-phase downgrade applied only when the legacy minimum passes.
- All 15 image rules come from the versioned registry, so the report names the rule ID, version and source for each finding.
7. Known limitations and false positives
- A URL can fail for reasons that have nothing to do with the image: hotlink protection, a CDN that blocks non-browser clients, a WAF, a temporary outage. The checker reports that as Needs review with the HTTP evidence, not as a bad image.
- Category-dependent thresholds require a trustworthy category. When the category is missing or ambiguous, a guessed threshold is worse than an explicit "needs review".
- Format detection reads magic bytes, so a truncated or corrupted file may decode partially; the decode rule reports what it could establish and nothing more.
- Accepted format list: jpeg, webp, png, gif, bmp, tiff. A format accepted by the image specification can still be rejected by a specific destination, which is out of scope here.
- The checker does not evaluate composition, background, or whether the image actually shows the product.
8. How to fix a failing image
- Start from the largest original you have. Re-exporting a small image larger does not add detail and is not what the requirement is about.
- Export as JPEG, WebP, PNG or a static GIF — whichever suits the subject — and keep it under the file-size limit while staying above the pixel minimum.
- Flatten animation to a single representative frame if the asset is an animated GIF.
- Make sure the URL serves the image bytes directly, publicly, without cookies or a login step.
- Update the feed value, then re-run the check and confirm the issue is reported as Resolved rather than persisting under a different rule.
The checker will never replace your image URL, upscale the file, or write a placeholder value. Those would create a feed that passes a check and fails in reality.
10. Last verified and ruleset version
Last verified 11 November 2026 against ruleset version 1.0.0 (schema 1.0.0). Sources are re-checked before release and at least monthly, because platform requirements change; a source change produces a new ruleset version and is recorded in the changelog.
Frequently asked questions
What is the minimum product image size, and when does it change?
From 2027-01-31 the minimum is 500×500 pixels for every product image. Until then the legacy minimums apply — 100×100 for non-clothing products and 250×250 for clothing — and only when the product category is known.
Why does the same image warn today and fail after 2027-01-31?
Because from 2026-04-14 until 2027-01-31 an image that passes the legacy minimum but is below 500×500 is reported as a warning rather than an error. Every run records the as-of date it used, so the same file can legitimately produce a different result after that date: the rule changed, not the file.
Which formats and limits apply?
A decodable image in an accepted format (jpeg, webp, png, gif, bmp, tiff), at or below 64 megapixels and 16 MB, and not an animated GIF. Format and dimensions come from decoding the bytes, never from the file extension or the server’s Content-Type header.
Will the checker upscale or replace my image?
No. It never replaces your image URL, upscales the file, or writes a placeholder value; a re-export at a larger size does not add detail and is not what the requirement is about. It reports the rule, the measured pixels and the source, and the fix is to start from the largest original you have.
When does the checker fetch my images?
Only after you explicitly opt in to remote checks, from the public URL in your row, with bounded size and timeouts and an honest User-Agent. Format, dimensions, animation and decode results all come from the fetched bytes rather than from the URL itself.