File size is not the same as image size. Image size is counted in pixels, the width and the height of the picture; file size is the space the file takes on disk, and it depends on the pixel count, the format and how strongly the file is compressed. Two images of identical dimensions can differ in weight many times over.
An image above a marketplace's limit is rejected at upload or fails to load from a product feed. The usual remedy is to export the same pixels as a JPEG at a slightly lower quality setting, which cuts the weight sharply before any loss becomes visible. Reducing the pixel dimensions is the last resort, because it can take an image below the size that zoom needs.
What makes one photo heavier than another
Compression stores smooth, even areas cheaply and fine, irregular detail expensively. A product on a clean white ground compresses to a small file; the same product on a grainy wooden table, or a photo taken in dim light with visible noise, weighs far more at identical dimensions.
Format and hidden data decide the rest. PNG keeps every pixel exactly and makes photographs heavy; JPEG discards detail the eye rarely misses; WebP and AVIF go further at similar visible quality. Camera details, an embedded preview and editing information also travel inside the file unless the export leaves them out.
Kilobytes, megabytes and why limits are counted differently
Most upload forms count a kilobyte as a thousand bytes and a megabyte as a million. Some operating systems count in steps of a little more than a thousand, so the same file shows a slightly smaller number on one computer than the form measures.
A file that sits just under a limit by one count can therefore sit just over it by the other. Exporting with a clear margin below the stated limit avoids an upload that fails for a reason the file details do not show.
Getting under the limit without visible loss
Each new JPEG save compresses again, so a photo saved, edited and saved several times loses a little in every round. Exporting once, from the original or an uncompressed master, at the final dimensions, gives the smallest loss for a given weight.
Where compression starts to show depends on the picture. Soft gradients in a backdrop turn into bands, fine knits and checks turn blotchy, and the edges of lettering gain halos. Viewing these areas at full size after export is the quick test of whether the quality setting went too low.
Image file size and related terms
- Image compression
- Image compression is the method that makes a file lighter. File size is the result: the same photo can weigh very different amounts depending on how, and how strongly, it was compressed.
- JPEG
- JPEG is the format most product photos are uploaded in. Its quality setting is the main control over file size, and the weight falls steeply in the upper part of that scale while the picture barely changes.
- WebP
- WebP stores a photograph in a smaller file than JPEG at similar visible quality. It helps with a size limit only where the sales channel accepts the format, which not every upload form does.
- Image dimensions
- Image dimensions count pixels; file size counts bytes. Lowering the dimensions does reduce the weight, but it costs detail and zoom, so it comes after compression when a file has to get lighter.
A file size checklist before upload
- The limit was read with its unit, and the export stays a clear margin below it.
- Photos are saved as JPEG, or in another format the channel accepts, and as PNG only where transparency is needed.
- The file was exported once from the original, not re-saved from an earlier compressed copy.
- Gradients, fine fabric patterns and lettering were viewed at full size after compression and show no bands, blocks or halos.
- Data the listing does not need, such as embedded previews and editing information, was left out at export, while the colour profile was kept.
