How to Fix “Image Too Small” in Google Merchant Center

A product photo can look large on your store while Merchant Center receives a small copy. The image on the page, the file uploaded to your media library and the address submitted in your product data are not always the same.

This guide focuses on the image-size issue in shopping ads and free listings. It covers finding the affected file, preparing a replacement and checking the submission. It does not promise approval for a product with other policy or data problems.

Separate the current minimum from the upcoming requirement

As checked on 18 October 2026, Google's 2026 product data update announces a minimum width and height of 500 pixels for both main and additional product images across categories and marketing methods. Enforcement starts on 31 January 2027.

The transition details come from Google's “Image too small” help page. Read the issue on the affected product: a warning about upcoming enforcement is different from a current disapproval. Google may also report that it has automatically optimized an image. Keep a suitable original available rather than relying on that processing.

A minimum of 500 × 500 does not require a square photo. Both sides must reach 500 pixels. A 1200 × 800 image meets that dimension threshold; a 1200 × 400 image does not. Meeting it does not establish that the image has enough detail or satisfies every other requirement.

Find the image Merchant Center actually receives

Start with one affected product. Note its product ID and variant, then inspect the main image address supplied through image_link. This is the product-data field that tells Google where to fetch the primary image. If the issue concerns an additional image, inspect the corresponding additional_image_link entry.

1. Open the affected product in Merchant Center. In Products, look for Needs attention and open the issue and product details. Labels may vary as Google updates the interface.
2. Find the submitted image address. Use the product details or the matching row in your data source. A data source may be a file, an ecommerce integration or an API connection.
3. Open that exact address in a separate browser tab. It should display the product image itself. A product page or a storage-service preview page is not the same as a direct image response.
4. Save that copy and inspect its pixel dimensions. Use file properties or an image editor. How large it looks in the browser is not a reliable measurement.
5. Compare it with the store's original. If the submitted copy is 300 × 300 but your original is 2400 × 2400, the immediate problem is the selected variant or URL.

Google's image-status guidance explains the relationship between submitted URLs, crawling and product diagnostics. Check the exact variant too: a red product should not accidentally inherit the blue product's image when fixing a batch.

Example: check the image field for one product

Suppose the affected product ID is mug-blue. Find that ID in the file or integration that supplies your product data, then read its image_link value. The following addresses are fictional examples:

If your integration does not show this field, check whether it can export or preview the product data. Otherwise, ask its support team which image URL is sent for that product ID. Looking only at the picture displayed on the storefront can miss the problem.

Choose the fix that matches the cause

A URL ending with something like ?width=300 may describe a generated image size, but parameter names differ between services. The larger version must genuinely exist and remain publicly accessible. Ask the person maintaining the integration which image field or size setting is being sent.

Changing the picture in the visible product gallery may not change the image URL in the product data immediately. Follow the actual path from the store to its integration and then to Merchant Center.

Start with a sufficiently detailed original

Use a sharp original showing the correct product and variant. Google's image-link specification recommends images around 1500 × 1500 pixels or larger where possible, and limits files to 16 MB and 64 megapixels. Those are separate from the minimum dimensions.

Use the recommendation as a reason to preserve useful source detail, not an instruction to enlarge every small image. Enlarging a 300 × 300 thumbnail to 1500 × 1500 creates more pixels without recovering a missing label, texture or edge. Google's guidance advises against upscaling submitted images.

1. Choose the source and framing. Keep the whole product clear, including handles or accessories that belong in the main view. Avoid solving a low-resolution source by surrounding it with a large empty border.
2. Crop only when needed. Use Crop Image to remove distractions, then check the dimensions left after cropping.
3. Resize only when there is a reason. For a source that is unnecessarily large, use Resize Image with proportions locked. A source that is already suitable may need no size change.
4. Export a supported file. JPG is a practical choice for an ordinary opaque photograph. If a HEIC source needs conversion, make a JPG copy first. Renaming its extension is not conversion.
5. Check the download. Inspect both dimensions, important product details and file size before replacing the submitted image.

Pixilo accepts files up to 25 MB, but Merchant Center's file limit is lower. Passing Pixilo's input check does not establish that the export meets Google's rules. If compression is needed, compare the finished copy visually; reducing bytes cannot fix an image with too few pixels.

Keep this main product image free of added sale labels, retailer watermarks and decorative borders. A clean image of the correct product matters alongside resolution. The product image guide covers the wider preparation workflow.

If the product image includes generative AI

The ordinary photo workflow above needs an extra check for AI-generated images, including those created with Google's Product Studio. Google's AI image metadata requirements say to retain the embedded information identifying their digital source, such as the IPTC DigitalSourceType property. That information records how the image was created.

Pixilo's crop, resize and conversion tools redraw images and create new files; they do not guarantee preservation of these tags. Use an editing and export workflow that retains the required source metadata, and verify it after editing. Removing private GPS data and keeping required AI-source information are different tasks. Do not pass an AI-generated product image through a metadata-removal workflow intended for ordinary photo sharing.

Worked example: a good original, but a small submitted copy

Imagine a store with a 2400 × 1800 photograph of a ceramic mug, a non-apparel product. The integration submits a generated 300 × 225 copy, and Merchant Center reports an upcoming size warning. That copy exceeds the current 100 × 100 minimum for this category, but its shorter side is below the future 500-pixel minimum. An apparel image of 300 × 225 would already fall below the current 250-pixel minimum in height.

Making the web page display the thumbnail at 900 pixels does not change the dimensions of the file Google receives.

1. Save the file from the submitted URL and confirm that it is 300 × 225.
2. Locate the sharp 2400 × 1800 original. It already exceeds the future minimum in both directions.
3. If the store needs a square main image, make a considered 1800 × 1800 crop from the original. If the landscape composition works better, keep it; the minimum does not require a square.
4. If desired for this example, resize the square crop down to 1600 × 1600 and inspect the product detail. This is an example export, not a universal target.
5. Publish the prepared file and update the integration to submit its direct URL, rather than the 300-pixel thumbnail.
6. Verify the saved product data after the next sync, and check the image fetched from that address again.

The crucial correction is the image supplied to Google. Preparing a good replacement helps only if the data source actually points to it.

Update your product data and recheck processing

For an integration-managed product, correct the store or integration setting that generates the image field. A manual edit in Merchant Center can be replaced by the next sync. For a file-based data source, update the matching product row and resubmit using your normal method.

If a suitable large image already exists, correct the field to use its existing direct URL. You do not need to create another copy merely because the field previously pointed to a thumbnail.

If you actually replace an image's contents, publish the replacement at a new, stable address, such as /images/mug-main-v2.jpg, and submit that URL. Google's image-status guidance recommends a new URL for changed images to help trigger a fresh fetch. Once the file and field are correct, keep the address stable; adding a new timestamp on every sync is unnecessary.

• Open the submitted URL in a signed-out browser window. A successful personal login is not proof of public access.
• Check that the response is an image, with suitable dimensions, rather than a login page, a broken link or a cached thumbnail.
• Confirm that the correct product and variant received the new image address.
• Check the relevant issue again after Google has fetched and processed the update.

The image-size help page gives 24–72 hours as a possible time for changes to appear in Needs attention. Treat that as guidance, not an approval deadline. If the warning remains, inspect the URL and status again rather than repeatedly re-exporting an already suitable file.

If the file is public for you but Google cannot fetch it, review crawler access, hosting security and the image response. Our image access and indexing guide explains those checks. Search Console is not a replacement for Merchant Center's product diagnostics.

Frequently asked questions

Does “too small” mean the file has too few kilobytes?

This issue concerns pixel dimensions. A small file in bytes can still have enough pixels, while a large file in bytes can have insufficient width or height. Check the dimensions of the image at the submitted URL.

Can I fix it by changing DPI to 300?

No. Changing a DPI label without changing the pixels leaves the width and height unchanged. The DPI, PPI and pixels guide explains the distinction.

Can the file be large enough while the product still looks too small?

Yes. A large canvas with a tiny product in the middle can meet the pixel threshold while presenting the item poorly. Check how much useful product detail the image contains. Return to a detailed original and improve its framing instead of adding empty borders around a small thumbnail.

Will this fix every image disapproval?

No. A suitable size does not repair a wrong product image, promotional overlay, unsupported format or inaccessible URL. Read each active issue and fix its cause separately.