Resize Image to 1500×1500 — Google Shopping Size, Batch Free

Resize to 1500 × 1500 — In One Batch

The answer up front: 1500 × 1500 is the number Google itself puts in its spec — Merchant Center recommends product images “around 1500x1500 pixels or above,” and it is the only square size on the internet whose source is a search engine. Drop a feed folder above and every file leaves as an exact 1500 × 1500 in one ZIP. Nothing uploads.

Why Google Chose 1500 — It Is Crop Headroom, Not a Display Size

Most resize pages quote 1500 × 1500 without saying where it comes from. It comes from the Google Merchant Center image_link spec, in writing: at least 500 × 500, “when possible, we recommend that you provide images around 1500x1500 pixels or above to ensure best performance in all listing formats,” with ceilings at 64 megapixels and 16 MB. The phrase doing the work is all listing formats. Your one product image does not display at one size — Google re-frames it for the shopping tab, image results, retailer badges, comparison cards, and phone screens, and the platform crops and magnifies into your file. A 500² image that is technically compliant collapses at the first crop that zooms; a 1500² master leaves every derived surface sharp. 1500 is exactly 2.25 megapixels — 15× the enforced floor’s area — which is the headroom Google pays itself for when it tests “subtle cropping” on your image, a behavior its own help page discloses. If you serve the floor, you are serving Google a file it must invent detail into. The full batch tool is on the bulk image resizer if you want unlocked dimensions instead of this lock.

January 31, 2027: What the Enforcement Date Actually Changes

Google announced a specification update that lifts the minimum to 500 × 500 across every product category, warnings live since April 14, 2026, enforcement on January 31, 2027. Read the dates carefully, because the feed community keeps misreading this: the hard rule that arrives is not 1500 — it is the floor under it. What dies on that date is the decade-old allowance of 100 × 100 (non-apparel) and 250 × 250 (apparel) images; every thumbnail that scraped by at 250² stops serving entirely. The recommendation stays exactly where it was, which means the strategic move has a clock on it: a feed full of 500²–1000² images passes 2027 but still looks cropped-down next to competitors exporting at Google’s recommended 1500². Normalizing the folder to 1500 × 1500 before the enforcement panic — as one ZIP pass, filenames intact so your feed CSV still matches row-for-row — is a Tuesday afternoon job here, not a Q1 2027 re-shoot project. The companion compliance mechanics (feed-safe backgrounds, what Google disapproves on sight) share ground with the white-background spec page.

Pass / Fail: One 1500 × 1500 JPEG Against Five Destinations

1500 is a Google number — but feed folders rarely feed one shelf. The same honest grading as the other size pages: Google Shopping — this is the stated recommendation itself; pass on every surface. Amazon — clears the 1,000-px zoom threshold with 50% margin, but sits below Amazon’s recommended 2,000+ px, so it is fine for secondary images and a compromise for hero mains that get magnified (the 1000 page grades that gate; the 2000 page is Amazon’s own answer). eBay — passes, and this is the sleeper result: eBay’s published photo-tips window is 800–1,600 px on the long side, making 1500² the rare size that is simultaneously Google’s recommendation and nearly eBay’s stated ideal — eBay is the marketplace where 1500 is not a downgrade at all. Etsy — fails the guideline (longest side ≥ 2,000 px). Walmart — fails (2,200 px required on the longest side). One export, three verdicts by shelf. Multi-channel folders should export masters at 2000² and derive the 1500² Google feed by downsizing — never upscale upward — or run the same folder through both locks.

The Upscale Trap, Now With a Second Failure Mode

Every digital-size page warns against manufacturing pixels; at 1500 the trap is worse, because Google split the diagnostics into two buckets and stretching walks into the second one. A 500² image forced to 1500 clears “Image too small” — the validator reads dimensions, not detail — and lands in “Low image quality”, a separate warning Google introduced precisely because the 2027 floor change would otherwise trigger a mass upscale epidemic. Three times the linear resolution from the same source photo means smeared edges and doubled JPEG blocks exactly in the regions where Google’s automated crops zoom. Flat graphics tolerate ~1.6× invisibly; 3× never works on photographs. The honest ladder: re-export from the original file, re-shoot, or ship a clean true 500² that is compliant-but-small instead of dimensionally-compliant-but-flagged. Before uploading a normalized folder, the bulk screening pass finds sub-floor and off-white offenders in one sweep; if 1500² files come out heavier than the feed needs, one batch compression pass fixes weight without touching dimensions.

A 1500 Batch Pipeline (Feed Normalization Ahead of 2027)

Sort the destination first: Google-first feeds and eBay listings (this page) vs. Amazon hero mains and Etsy/Walmart shelves (use 2000 × 2000 as master and downsize from it).
If mains sit on wrong or off-white backgrounds, fix them before sizing — batch background removal at original resolution beats edge math at 1500 px.
Drop the folder here: exact 1500 × 1500 for uniform squares; pad or center-crop per image as the subject allows — a crop that cuts the product is worse than a pad band.
Export JPEG quality 85–90. At 2.25 MP there is no display surface where q95 is visible and the feed is 30% lighter at 85.
Download the ZIP with filenames preserved so the feed CSV matches row-for-row, then check Diagnostics in Merchant Center for “Image too small for upcoming enforcement” disappearing — that queue is the scoreboard for this job.

Frequently Asked Questions

How do I resize an image to exactly 1500×1500? ▼

Drop the files into the batch tool above — it is locked to exact 1500 × 1500. Square sources are resampled straight in; rectangular ones need a decision first: pad to a square (nothing lost, fill bands on two sides), center-crop to a square (nothing added, frame edges trimmed), or stretch (visibly wrong on photographs). For feed images export JPEG at quality 85–90 — a 2.25 MP square at q95 buys you nothing but file weight. The whole set leaves as one ZIP with filenames preserved, and everything runs in your browser: no upload, no account, no watermark.

Why does Google recommend 1500×1500 for product images? ▼

Because it is the number Google can crop down from. The Merchant Center image_link spec states it directly: minimum 500 × 500 (enforced across all categories from January 31, 2027), and “when possible, we recommend that you provide images around 1500x1500 pixels or above to ensure best performance in all listing formats.” Shopping surfaces do not display one fixed size — the same image gets re-cropped for the shopping tab, image results, retailer badges, and mobile cards. A 1500² master keeps every derived crop sharp; a 500² compliant-minimum image falls apart the moment any surface magnifies it. 1500 is not a display size, it is crop headroom.

Is 1500×1500 enough for Amazon, eBay, and Etsy too? ▼

Graded one honest file against five destinations: Google Shopping — this is literally the recommendation, pass. Amazon — passes the 1,000-px zoom threshold with margin, but sits below Amazon’s own 2,000-px recommendation, so 1500 is fine for secondary images and a compromise for zoom hero mains. eBay — passes; it lands inside eBay’s published “800–1,600 pixels on the long side” optimization window, the one marketplace where 1500 is not a compromise but nearly the stated ideal. Etsy — fails the guideline: longest side at least 2,000 px. Walmart — fails: 2,200 px on the longest side required. A 1500² export is a Google-first size; if the same folder also feeds Etsy or Walmart, export the 2000 page batch instead and derive Google images by downsizing, never the reverse.

What happens on January 31, 2027 — does 1500 become mandatory? ▼

No. The enforced floor from that date is 500 × 500 across all product categories (warnings in Merchant Center began April 14, 2026 for images under it, and images between the old 100 × 100 / 250 × 250 minima and 500 × 500 started warning in July 2026). What changes is where the floor lifts: anything under 500² stops serving outright, so years of “compliant” 250² thumbnails get culled from feeds. 1500 × 1500 stays a recommendation, not a rule — but it is the recommendation that decides how your images look on the surfaces that crop them. Fixing a feed before the enforcement date is a batch job, not a re-shoot: normalize folder-wide to 1500² in one pass and re-submit.

Can I upscale a 500×500 image to 1500×1500 to hit the recommendation? ▼

You can push the pixels, and the feed validator will accept the dimensions — Google’s own Diagnostics flags what that actually produces as “Low image quality,” separate from “Image too small.” Upscaling triples linear resolution without adding a pixel of detail: a 500 px photo stretched to 1500 shows smeared edges and block artifacts exactly where Google’s automated crops zoom in. This is also why the 16 MB and 64-megapixel ceilings exist far above this size — the game is not filling a frame, it is feeding surfaces that magnify into it. Re-export from the original file or re-shoot; if neither exists, a clean 500² (compliant, small) beats a fake 1500² (dimensionally compliant, quality-flagged).

Can I batch-resize many images to 1500×1500 for free? ▼

Yes — the tool above takes any number of files, applies the locked 1500 × 1500 target in one pass, and exports a single ZIP with original filenames intact so feed CSVs still match row-for-row. It is free because the Canvas resize runs on your machine: no upload, no quota, no watermark, nothing leaves the browser. The typical job at this size is a Merchant Center feed cleanup — hundreds of mixed-size product photos brought to uniform 2.25 MP squares ahead of the 2027 enforcement — or preparing 1500² masters for surfaces like Google image search that display cropped derivatives.