Google Merchant Center product images must be JPEG, WebP, PNG, GIF, BMP or TIFF files whose extension matches the real format, no larger than 64 megapixels or 16 MB, and free of promotional text, watermarks, borders and placeholders. Google has announced a minimum of 500 x 500 pixels for all products beginning January 31, 2027, and recommends about 1500 x 1500 pixels or more. To bring a whole catalog folder into line, OpticBatch from Automata Labs resizes and converts thousands of images locally on Windows, with a quality slider to keep files well under the size cap.
Resize and convert your whole product image folder in one local batch.
Get it from Microsoft
What are Google Merchant Center’s image size requirements?
Google’s help article for the image link attribute lists these limits for the main product image:
| Requirement | Google’s rule |
|---|---|
| Minimum size | At least 500 x 500 pixels, for all products beginning January 31, 2027 |
| Recommended size | Around 1500 x 1500 pixels or above |
| Maximum resolution | No image larger than 64 megapixels |
| Maximum file size | No image file larger than 16MB |
| Formats | JPEG, WebP, PNG, GIF, BMP and TIFF |
| Extension | Should correspond to the file’s real format |
| Image URL | http or https, ASCII only, RFC 3986 compliant, 1 to 2,000 characters |
The note at the top of Google’s article is the one to plan around: “We recently announced new image size requirements of at least 500 x 500 pixels for all products beginning January 31, 2027.” The recommendation to go to 1500 x 1500 or above is “to ensure best performance in all listing formats.”
If your catalog has older thumbnails or supplier images below 500 pixels on either side, list them now. Resizing a small image up does not add detail, so those products need better source photos, not just a bigger export.
Which image formats does Google Merchant Center accept?
Google supports JPEG (.jpg or .jpeg), WebP (.webp), PNG (.png), GIF (.gif), BMP (.bmp) and TIFF (.tif or .tiff). It also warns: “Using incorrect file extensions (for example .jpg for a .png file) can lead to ‘Unsupported image type’ errors.”
That error is common when images are renamed instead of converted, or when a platform serves a different format than the URL suggests. The fix is a real conversion, so the file’s contents and extension agree. Our comparison of WebP vs JPEG vs PNG explains which to choose; JPEG is a safe default for product photos on a plain background.
What gets a product image disapproved?
Google says images that break these rules “won’t appear on Google surfaces,” and you will see a notice in Merchant Center Diagnostics. The main things to avoid:
- Promotional elements and overlays, including calls to action such as “Buy,” price or shipping text like “Free shipping,” warranty claims, words such as “Best” or “Cheap,” and labels like “New.”
- Barcodes, QR codes and serial tags overlaid on the photo.
- Watermarks and stamps, including stock watermarks and copyright symbols.
- Added logos or store names unless they are physically part of the product.
- Placeholders such as “Coming soon” or “No image available,” store logos used instead of a photo, or one generic photo reused across different products.
- Borders around the image.
- Other products that are not sold together with the main product.
Google lists exceptions for some categories. For example, generic images and illustrations are allowed for Hardware, Vehicles and Parts, and Software, and software logos or icons can represent products in Software, Computer Software.
What should I know about AI-generated product images?
Google says “All images created using generative AI must contain meta data indicating that the image was AI-generated,” such as the IPTC DigitalSourceType value TrainedAlgorithmicMedia, and asks you not to remove that metadata.
This matters for batch processing. Many resize and convert workflows drop embedded metadata. If you use AI-generated or AI-edited images, check that the files you upload still carry their IPTC DigitalSourceType tag after processing, for example with a metadata viewer, before you replace your feed images. Our guide to EXIF vs IPTC vs XMP explains where that tag lives.
How should I frame and prepare product photos?
Google’s best practices go beyond the minimums:
- Frame the product so it “takes up no less than 75%, but not more than 90%, of the full image.”
- Submit a unique image for each variant, showing the exact color, pattern, finish and material, and only one variant per image.
- Use additional image links for other angles and detail shots, and the lifestyle image link for in-context photos.
- Use stable URLs without timestamps or session IDs that change on each feed submission.
- Allow Googlebot and Googlebot-image in robots.txt so Google can fetch the images.
- Expect cropping. Google “may test subtle cropping on your image to better frame the item.”
Framing and backgrounds are a photo editing job. The sizing, format and file weight across hundreds of SKUs are a batch job.
Turn a mixed folder of PNG, WebP and oversized JPEG files into consistent feed images.
Get it from Microsoft
How do I batch-prepare a catalog for Merchant Center?
A practical workflow:
- Audit sizes. Find images under 500 pixels on either side and replace them with better originals.
- Pick one format, usually JPEG for photos, and convert properly rather than renaming.
- Set a long-edge limit, such as 2000 pixels, to stay comfortably above the 1500 recommendation and far below 64 megapixels.
- Set a quality level that keeps files light. Product photos rarely need to approach 16 MB.
- Write to a new folder, keep your originals, and spot-check a sample at full size.
- Check metadata on any AI-generated images, as above.
- Upload and check Diagnostics in Merchant Center after the next feed fetch.
OpticBatch handles steps 2 to 5 on your PC. According to its Microsoft Store listing:
- Batch conversion between JPEG, PNG and WebP.
- Resizing by Max Width, Max Height, Percentage Scale or Exact Dimensions, with an aspect-ratio lock to prevent distortion.
- A quality slider from 1 to 100 for lossy formats, with a live estimate of file size savings before you run.
- Fault-tolerant batches that flag corrupted files and keep processing the rest.
- Atomic writes, so originals are never overwritten or corrupted if a batch is cancelled.
- 100% local processing, with no cloud uploads, no forced account and no telemetry, on Windows 10 and Windows 11.
OpticBatch outputs JPEG, PNG and WebP, which are all accepted by Merchant Center. It does not edit the photo itself, so overlays, borders and framing must be fixed at the source. If you sell on several marketplaces, compare these rules with Amazon’s image specs, and for a broader look at the tool, see a fast local bulk image resizer for Windows 11.
Frequently asked questions
What is the minimum image size for Google Merchant Center?
Google has announced at least 500 x 500 pixels for all products beginning January 31, 2027, and recommends about 1500 x 1500 pixels or more.
Does Google Merchant Center accept WebP images?
Yes. WebP is on Google’s supported list, along with JPEG, PNG, GIF, BMP and TIFF.
What is the maximum file size for a product image?
16 MB, and no image larger than 64 megapixels.
Why am I getting “Unsupported image type”?
Often the file extension does not match the real format, such as a PNG file named .jpg. Convert the file properly so they match.
Can I add my logo or a sale badge to the main image?
No. Google disapproves images with promotional overlays, watermarks and added logos, except logos that are physically part of the product.
Try OpticBatch
Get OpticBatch from the Microsoft Store. It is a one-time purchase with no subscription, and the Store listing shows the current price.
If your images are WebP and you need JPEG, see converting WebP to JPG in bulk on Windows.
Prepare feed-ready product images in bulk, privately on your own PC.
Get it from Microsoft
Google and Google Merchant Center are trademarks of Google LLC. Amazon is a trademark of Amazon.com, Inc. or its affiliates. Microsoft and Windows are trademarks of the Microsoft group of companies. OpticBatch is not affiliated with or endorsed by Google, Amazon or Microsoft.
Last updated 23 October 2026. Published by Automata Labs, a software company in Canada.