Google Merchant Center · image rules
Google Merchant Center image checker
Check product images against Google's published image requirements — pixels, format, file size, animation and decode — with the date-aware 500×500 change handled explicitly.
64 versioned rules across 3 rulesets · ruleset 1.0.0 · rule data verified 11 November 2026 · no account needed for a local run
Rules in this check
15 image rules
Input
Image URLs from your feed (one per row), checked after you opt in
Where it runs
Parsing and rule evaluation happen in your browser
Last verified
11 November 2026
Ruleset version
1.0.0
The problem this solves
Image rejections are the least obvious class of Merchant Center error, because the message rarely says which property failed. A JPEG that looks fine on screen can be 300×300 pixels, above 16 MB, an animated GIF, or a WebP that a downstream destination cannot decode. And between now and 2027-01-31 the minimum size is moving, so the correct verdict for the same image depends on the date you check it.
What this check tests
- Dimensions against the applicable minimum: 100×100 for most products and 250×250 for clothing before 2027-01-31, then 500×500 for every product image from 2027-01-31.
- Resolutions below 1500×1500 are flagged as a recommendation, not a hard failure — that size is advice from the official source, not a threshold.
- Pixel count above 64 megapixels.
- File size above 16 MB (16 MB; the exact decimal/binary boundary is not stated in the official requirement, so boundary cases are reported as ambiguous rather than guessed).
- Real decoded format against the accepted set: jpeg, webp, png, gif, bmp, tiff. The file extension and the server's Content-Type header are not trusted.
- Animated GIF, and images whose bytes cannot be decoded as an image at all.
- URL syntax for the main image and every additional image link, including bare relative paths and embedded credentials.
- The 500×500 requirement for the YouTube Shopping Ads destination, only when you explicitly select that destination.
What this check does not do
- It does not judge content policy — overlays, watermarks, promotional text, placeholders or the wrong product. Those need a human looking at the image, and the rule reports Needs review rather than inventing a verdict.
- It does not infer whether an image was created with generative AI. Provenance is metadata evidence, never guessed from appearance.
- It does not upscale or resize your image, and it never substitutes a different image URL.
- It does not promise that Google will accept the image. Passing means the deterministic, published requirements were met with the evidence available.
The date timeline that decides the verdict
2026-04-14 → 2027-01-31
Images that meet the legacy minimum but are below 500×500 report a warning. The official sources disagree on when this phase started: the dated annual update says 2026-04-14, the dedicated image article says July 2026. The checker uses the earlier date as its own conservative policy and says so; it does not claim Google warned every merchant on that date.
From 2027-01-31
500×500 becomes the minimum for every product image, and the legacy clothing/non-clothing split stops applying. Checking with an as-of date after 2027-01-31 reports a failure for any image smaller than 500×500.
Because the verdict is date-dependent, every run records the date it used. Re-running the same file after 2027-01-31 can legitimately produce new errors — that is the rule changing, not the file changing.
Input, limits and privacy
- Images are checked from the URLs in your exported feed; you can also check a single image URL.
- The file itself is parsed locally. Nothing is uploaded.
- Remote fetching of an image happens only for the URLs you explicitly submit, after a separate consent step.
- The scanner downloads only the bytes it needs for metadata, from public HTTP(S) URLs, with bounded size and timeouts. It identifies itself and does not impersonate a crawler.
- Downloading an image tells the host that a request was made, exactly as a browser would. Their logs may record it.
How each finding reads
A finding names the rule, the product row, the field, the raw value from your file, the measured value (for example the decoded 420×680 pixels), the rule version, the as-of date and the official source. Nothing is aggregated into a score, so a single blocking problem cannot be averaged away by passing rows.
See every Google image rule and its sourceFrequently asked questions
Is a passing result a guarantee that Google will show my image?
No. This check verifies published deterministic requirements. Eligibility, rendering and any account-specific enforcement remain entirely with Google.
Why does the same image fail now but pass last year?
Because the minimum moved. Before 2027-01-31, an image below 500×500 may only warn; after that date it fails. The report always shows which as-of date produced the verdict.
Can I fix the image by upscaling it?
No. Upscaling does not add detail and the official guidance is to start from a larger original. The checker never modifies your image and will not suggest an upscale.
Does a valid image URL mean my image is fine?
No. A URL can return HTTP 200 and still serve a placeholder, a 1×1 pixel, or an HTML error page. That is why the check reads the bytes and reports Needs review when the response cannot be interpreted safely.
Sources
- Google Merchant Center image link specification
- Google image too small troubleshooting article
- Google 2026 product data update bulletin (warning-date conflict)
Last verified 11 November 2026 against the ruleset version 1.0.0. Sources are re-checked before release and at least monthly, because platform rules change.