twimco.Let’s talk ↗︎
Menu
Field notes / Commerce

Google Merchant Center wants 500-pixel product images by January 31. Find out where your small ones come from

Most stores don't have a few small product photos. They have one setting, one supplier or one old shoot that produces them over and over. Find that source and the January deadline turns into an afternoon's work.

Editorial engraving of a young photographer reshooting a product on a white tabletop backdrop while an older colleague points to a contact sheet beside him.

From January 31, 2027, Google Merchant Center requires every product image, main and additional, to be at least 500 by 500 pixels. Until then the old minimums apply and small images only show a warning. Export the flagged products, sort them by where the image came from (a feed setting, a supplier, an old shoot, or variant photos), fix each source once, and avoid doing reshoots during Black Friday week.

The warning that's been sitting there since spring

If you sell through Google Shopping, there's a fair chance your Merchant Center account has been showing a quiet warning for months: "Image too small for upcoming enforcement." On January 31, 2027, it stops being quiet.

Google's rule is short. From that date, every product image you submit, the main image and any additional ones, must be at least 500 by 500 pixels, across all product categories and every way Google shows products. Until then, the old floor applies: 100 by 100 pixels for most products and 250 by 250 for clothing. Google's own specification update says the warnings began on April 14, 2026, while its "Image too small" help page says July. Either way, the list has been building for a while.

Five hundred pixels isn't big. Google itself recommends 1500 by 1500 or more for the best results, and Search Engine Roundtable's Barry Schwartz called the minimum "way too small." That's the useful part. If your images miss a bar this low, something systematic is producing them, and that something is usually easier to fix than a few hundred photos.

Small images usually have one cause

Small images usually have one cause, repeated a few hundred times. Start by finding it.

Export the products carrying the warning, with the image URL your feed sends for each. You'll find them in Merchant Center under Needs attention, where Google says the warning appears in the product's history. Then measure the actual image at each URL, because the file a feed points to isn't always the one you uploaded. A spreadsheet with four columns does the job: product, image URL, width, height.

Then sort the list by where the image came from. In most catalogs, you'll see the same few sources again and again.

How the work moves

From warning list to the cause

  1. Export

    Download the products carrying the image-too-small warning, with their image URLs.

  2. Measure

    Record the real width and height of each image the feed points to.

  3. Group

    Sort by where the image came from: feed setting, supplier, old shoot or variant photo.

  4. Fix the source

    Change the setting, ask the supplier, book the reshoot, or replace the variant set.

  5. Re-check

    Confirm the warning clears before you move to the next group.

Decision framework for your own catalog; steps are illustrative, not a Google procedure.
Small images usually have one cause, repeated a few hundred times.

Four places small images come from

The first is a feed setting. Many store platforms and feed apps serve product images from a CDN that can resize on request, and the URL in the feed sometimes asks for a medium or thumbnail size rather than the original. Every product looks fine on your site and too small in the feed. This is the best case: one setting in the feed app or one change to the URL pattern fixes the lot. Check this before anything else.

The second is a supplier. Dropship and wholesale catalogs often come with small images, and nobody notices until a rule like this lands. The fix is a request, not a resize. Ask the supplier for the original files, and tell them the date. If they can't help, those products need your own photos or a decision about whether they belong in Shopping at all.

The third is an old shoot. Products listed years ago were often photographed and exported for a smaller site template. Here, too, the originals may exist on a hard drive or with the photographer. If they don't, it's a reshoot, and that's worth scheduling rather than rushing.

The fourth is variant photos. Swatches, colorway shots and extra angles often go into the additional image field, and they tend to be smaller than the main image. The rule covers them too.

What not to do in a hurry

Don't stretch small images to 500 pixels. Google's specification says not to scale up images or submit thumbnails, and an upscaled photo looks soft at exactly the moment a shopper is comparing you with someone else. The same page bans promotional text, watermarks and borders, which matters if anyone's tempted to make up the size with a frame.

If you use AI tools to clean up or extend product photos, Google's spec asks you to keep the metadata that marks an image as AI-generated, such as the IPTC DigitalSourceType tag. Some export settings strip it, so check the files that come out.

There's also a safety net you shouldn't lean on. Google says it has started "optimizing" some images under 500 pixels so they meet the new requirement, and marks those products with a warning. That may keep a product approved, but you don't choose how the result looks. Treat an optimized image as a to-do item, not a fix.

One more thing: if you run YouTube Shopping ads, Google already requires 500 by 500 for them to serve on TV screens. Some of your products may be missing that placement today.

Keep the next ones big enough

Fixing today's list is half the job. The other half is making sure new products don't add to it next spring.

Find the point where images enter your catalog and put the check there. If a person uploads photos in your store admin, add the 500-pixel minimum, and ideally Google's 1500-pixel recommendation, to whatever guide they follow. If a supplier feed brings images in automatically, ask for a size in the supplier agreement or onboarding sheet, and have the import flag anything under it instead of quietly publishing it. If an agency or photographer delivers the files, put the export size in the brief.

Then look at the warning list again once a month. A short list that stays short means the check is working. A list that grows tells you which of the four sources has come back.

Fix it around the holidays, not during them

The deadline is after the holidays, which is the good news. The bad news is that the obvious time to deal with it, right now, is also the worst time to swap images in bulk. A feed full of new image URLs the week before Black Friday is a lot of change at once, and if something goes wrong you'll be untangling it with orders coming in.

So split the work. This week, do the export and the grouping, and fix anything that's only a feed setting, since that's one change you can check quickly. Through Black Friday and Cyber Monday, leave images alone. In December, send the supplier requests and book reshoots for the slower weeks. Aim to have everything in place by mid-January, so the last week before enforcement is for checking, not shooting.

If your product images pass through several systems before they reach Google, from the photographer to the platform to a feed app, our ecommerce work includes tracing that path and fixing it at the source. Talk to us.

Related work: Nines Style

Sequence of work

A calendar that stays out of Black Friday

  1. Spring-summer 2026

    Google starts warning about images under 500 x 500.

  2. This week

    Export the warnings and group them by source. Change feed settings only.

  3. Nov 27 - Nov 30

    Black Friday through Cyber Monday. No reshoots, no bulk image swaps.

  4. December

    Supplier requests out; reshoots booked for slow weeks.

  5. Jan 31, 2027

    Enforcement begins for every product image under 500 x 500.

Dates from Google Merchant Center Help and its 2026 specification update; the work plan around them is illustrative.
twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Paddle8 ↗︎