Resize to 1000 × 1000 — In One Batch

The answer up front: 1000 × 1000 is the compliance floor of e-commerce imaging — exactly 1 megapixel, and the smallest square that clears Amazon’s 1,000-pixel zoom threshold. Drop a catalog folder above, and every file leaves as an exact 1000 × 1000 in one ZIP. Nothing uploads.

JPG, PNG, WebP, BMP — drop 10 or 500 files

×

stretches to the exact box — use only when sources already share one aspect ratio.

90

What the 1,000-Pixel Rule Actually Measures

Amazon’s product image guide is precise in a way most resize pages are not: images under 500 px on the longest side cannot be uploaded, images with 1,000+ pixels on the longest side enable the zoom function, and the ceiling is 10,000 px. Read that twice — the zoom gate fires on the longest side, not on width and height both. A 1333 × 1000 landscape and a 2000 × 1500 scan enable zoom just as well as any square. So why does everyone resize to 1000 × 1000? Because a uniform 1:1 tile is the cheapest way to guarantee the threshold for a mixed folder of photos in every orientation at once, and 1000 × 1000 is exactly 1,000,000 pixels — 1 MP, a round number a listing CSV author can reason about. If you serve a rectangular image at 1000 on the long edge you pass; if you force the square you also keep the grid. Both are legitimate; only one of them is actually required. The tool above is locked to the square, and the full resizer has a fit-inside mode for the long-edge reading.

1000 Is the Floor, Not the Target

The same guide that sets 1,000 as the zoom trigger recommends 2,000 px or more — and those two numbers are not in conflict, they are a floor and a ceiling of expectation. At 1000 × 1000 the zoom feature switches on, then a customer on a retina display magnifies into a 1 MP image and finds soft edges and JPEG blocks at 200%. Where 1000 × 1000 genuinely wins: file-weight budgets across thousands of SKUs, slow-connection markets, upload forms that cap dimensions or size, and thumbnails derived from larger masters. Where it loses: the hero main image of anything inspected closely — jewelry, fabric, food — which is why the marketplace default most sellers should actually export is the 2000 × 2000 size that satisfies zoom plus perceived sharpness in one file. Pick the floor when weight is the constraint; pick the square-catalog target when zoom sharpness sells.

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

The number that made this page famous is Amazon’s, but catalogs go places. A single exact 1000 × 1000 export, honestly graded: Amazon — passes upload (500 min), zoom switches on (longest side ≥ 1,000), under the 2,000 recommendation; fine for secondary images, a compromise for mains. eBay — passes the minimum, below the 1600-px recommendation. Etsy — fails: the guideline is a longest side of at least 2,000 px. Walmart — fails: 2,200 px on the longest side is required. Shopify — works, but HD theme thumbnails want 2048+, so 1000 looks dated on a modern theme. One spec does not serve all shelves; the per-platform table with legal background values lives on the product photo spec page, and the white-background mechanics Amazon enforces (pure RGB 255, 255, 255, not “looks white”) are on the Amazon background page.

The Upscale Trap — and Amazon’s Sentence About It

The fast way to “hit 1000 px” is to drag a small image into any resizer and type the number. Amazon’s guide closes that door explicitly: do not artificially enlarge small images. Listing review teams suppress obviously upscaled mains, and customers who zoom are the worst audience for them — upscaling adds pixels, not detail, and a 600 px photo forced to 1000 magnifies its own blur. Flat artwork (a logo on white, simple packaging) survives 1.6× almost invisibly; photographs never do. If the only copy you own is small, re-export from the original file, re-shoot, or keep the honest size and lose zoom — do not manufacture a threshold. The bulk audit pass for finding sub-1000 and off-white offenders across a folder before upload is bulk background screening; the reverse problem — 1000 × 1000 files still too heavy — is a one-pass batch compression job.

A 1000 Batch Pipeline (Catalog Normalization)

  1. Sort the destination first: floor-for-weight or form-upload limits (this page) vs. sharp-zoom hero mains (use 2000 × 2000 instead).
  2. If mains sit on wrong backgrounds, fix them before sizing — batch background removal at original resolution beats edge math at 1000 px.
  3. Drop the folder here: exact 1000 × 1000 for uniform squares; pad or center-crop per image as the subject allows.
  4. Export JPEG quality 85–90 for photographs — at 1 MP there is no reason to bleed file weight on q95.
  5. Download the ZIP with filenames preserved so listing CSVs still match, and spot-check one long-edge case (e.g. 1333 × 1000) if your platform reads the rule literally.

Frequently Asked Questions

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

Drop the files into the batch tool above — it is locked to exact 1000 × 1000. Square sources just get resampled; rectangular ones need a decision first: pad to a square (nothing lost, bands of fill on two sides), center-crop to a square (nothing added, frame edges trimmed), or stretch (always visibly wrong on photos). Export JPEG at quality 85–90 for product shots, PNG if transparency must survive, and download the whole set as one ZIP. Everything runs in your browser — no upload, no account, no watermark.

Is 1000×1000 enough for Amazon product images? ▼

It is exactly the threshold that turns zoom on — and nothing more. Amazon's published rule is 1,000+ pixels on the longest side to enable the zoom function; the upload minimum is 500 px and the maximum 10,000 px. A 1000 × 1000 square clears the zoom gate with the fewest pixels any square can. But Amazon separately recommends 2,000+ px, because a 1000-px image magnified on a retina desktop shows soft edges and JPEG blocks. So 1000 × 1000 is the compliance floor, 2000 × 2000 is the quality target — use this size when file weight matters (large catalogs, slow-connection shoppers, form uploads), not when zoom sharpness sells the product.

Does the 1000-pixel rule count width and height, or just the long edge? ▼

Just the long edge — and this is the most-misread number in e-commerce image specs. Amazon's zoom requirement fires on the longest side ≥ 1,000 px, so a 1333 × 1000 or a 2000 × 1500 image enables zoom too; nobody at Amazon requires a square. The square is a convention, not a spec: uniform 1:1 tiles keep catalog grids tidy, and resizing a mixed folder to 1000 × 1000 is the cheapest way to guarantee every image passes the threshold regardless of orientation. If your real constraint is 'longest side ≥ 1000', fit-inside mode at 1000 does that without forcing the square.

Can I just upscale a 600 px photo to 1000×1000 to pass the check? ▼

You can, and Amazon says not to — their image guide explicitly warns against artificially enlarging small images, and listing teams do suppress obviously upscaled mains. Upscaling adds pixels, not detail: a 600 px photo at 1000 shows smeared edges and doubled compression artifacts under zoom, which is precisely the surface customers magnify into. Flat graphics (logos on white, simple packaging) upscale ~1.6× almost invisibly; photographs do not. The honest moves: re-export from a larger original, re-shoot, or keep the true size and accept no zoom. This tool resizes without silently upscaling beyond what you ask for.

What is the difference between 1000×1000 and 1024×1024? ▼

One is a human round number, the other a machine one. 1000 × 1000 is exactly 1 megapixel and is the number marketplaces write their policies around — Amazon's zoom threshold, countless form upload limits. 1024 × 1024 is 2^10 (1,048,576 px) and is what software stacks standardize on: Apple's app-icon master, SDXL's native diffusion canvas. They are 2.4% apart visually but serve different worlds: if the image feeds a marketplace listing or an upload form, the spec said 1000 and you should use 1000; if it feeds an app build or an AI pipeline, use the 1024 page. Do not round-trip a JPEG between the two repeatedly — each re-encode costs a generation of quality.

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

Yes — the tool above accepts any number of files, applies the locked 1000 × 1000 target to all of them in one pass, and exports a single ZIP with original filenames preserved. It is free because the Canvas resize runs on your machine: no upload, no quota, no watermark, nothing leaves the browser. The typical bulk job at this size is a catalog normalization — mixed phone photos and scans brought to uniform 1 MP squares before a marketplace upload — or trimming oversized exports down to the zoom floor when file weight per listing is the constraint.

🔒 BatchBG processes images locally in your browser. We use Plausible Analytics (cookieless, privacy-friendly) for anonymous usage statistics. Privacy Policy