PhotosUpscalerA PictureEditor.com tool

Listing floors, and the queue that clears them

Every pass runs on this machine; only the model travels.

Every marketplace publishes a pixel minimum and none of them publishes the same one. Read the floor, pick the factor that clears it, and let the estimate tell you what that costs in minutes.

Drop the listing folder, or select the files.

One photograph, not a folder? enlargepicture.com does that one properly, with the comparison view this queue has deliberately no room for.

Model weights come from cdn.pictureeditor.com only when you press the control that names their size. Everything else — the runtime, the decoding, the inference, the archive — is served from this domain and executed here.

What this queue is for

A listing is refused for a pixel count more often than for anything else about the photograph, and the number that refuses it differs by platform. The table below is the shape of that problem: five floors, read from the platforms’ own seller documentation in September 2026, next to the factor a 500-pixel supplier file needs to clear each one.

Published minimums, and what a 500 px source needs to clear them
PlatformFloor it publishesFactor from 500 pxPasses a file
Amazon1,000 px longest side9
eBay500 px longest side1× — already clear0
Walmart1,000 px minimum9
Etsy2,000 px shortest side9
Shopify themes2,048 px square, by convention9

The last column is the one worth reading twice. The pass count does not move with the factor, because neither network takes a factor — both work on tiles of your source, and a 500-pixel source is nine passes whether you asked for twice the size or four times it. That is why a small original is such a good input and a large one is such a poor one.

Running a folder

Pick the floor you are listing against, set the factor that clears it with a margin, and press the calibration control. The estimate that comes back is measured on the machine you are sitting at, so it already knows whether that is a coffee or an afternoon.

What it opens, what it refuses

  • Nothing here checks a listing against a platform rule. The table is reading material; the queue changes a size and says how long it took.
  • Aspect ratio, background colour, file-size caps and colour profile are all separate requirements and all outside this domain.
  • A set already past the floor gains nothing from a pass through this queue, and the page would rather say so than run it.

Asked mid-run

Are these floors current?
They were read from each platform's own seller documentation in September 2026 and every one of them has changed at least once in the last three years. Treat the table as the shape of the problem rather than as a citation, and check the floor for the platform you are listing on before you commit a queue to it.
A platform rejected my file even though it clears the pixel floor. Why?
Pixel dimensions are usually the loosest of three or four requirements. Aspect ratio, maximum file size, colour space and a white-background rule all sit alongside them, and none of those is something this queue touches. It changes one number about a photograph.
Should I aim for the minimum or well past it?
The minimum plus a margin. Upscaling past what the platform asks for costs wall-clock time on every file and buys nothing a buyer sees, because the platform downsamples to its own display sizes anyway. The exception is a zoom feature, which reads the full-size file and is the reason the higher floors exist at all.
My supplier files are already over the floor. Do I need this at all?
No, and the tool says so rather than taking your money in wall-clock time: if the set is already past the floor the honest answer is to upload it as it is.

Reference: the numbers