Compress Image to 100KB

100KB: the commerce tier of image compression

Where 20KB serves bureaucracy and 50KB serves applications, 100KB serves commerce. Marketplace listings, classified ads, real-estate portals, and CMS featured images cluster around this cap because it matches how selling works online: buyers scroll grids of thumbnails on phones, tap the promising ones, and expect the detail view to load instantly. A 100KB budget per image lets a category page with thirty products weigh roughly three megabytes of imagery — heavy but tolerable on 4G, and exactly why platforms enforce per-image caps rather than trusting sellers to optimize. The good news for sellers is that 100KB is a comfortable budget rather than a punishment. A 1600-pixel product photo at JPEG 82% typically lands between 150 and 250KB, so reaching 100KB costs only a few quality points or a modest dimension trim — changes no buyer will ever perceive on a phone screen.

Why you should compress before the platform does

Every major marketplace recompresses your uploads into thumbnails, zooms, and CDN variants — and their pipelines optimize for throughput, not your product. When you upload a 4MB original, the platform's batch encoder applies one-size-fits-all settings: fixed quality, fixed sharpening, sometimes a decade-old encoder. The result is generational loss — your camera's JPEG artifacts plus the platform's recompression artifacts, stacked. Compressing to a clean 100KB yourself flips the dynamic. You choose the quality-detail trade-off per image, inspect the result, and hand the platform a file already near its target size, which its pipeline then handles gently. Sellers who control their own compression consistently show crisper zoom views than sellers who dump originals and hope. The ten seconds per image is among the highest-ROI work in listing optimization.

The product-photo pipeline: shoot, standardize, compress

Professional catalog quality comes from standardizing before compressing. Step one is capture: diffuse daylight or a softbox, a neutral sweep background, and the product filling 75% of the frame — every background pixel is budget spent on nothing. Step two is dimensions: pick one canvas for the catalog (1600 × 1600 square for marketplaces, 1920 × 1080 for editorial) and resize every image to it, so listings look uniform and the byte budget buys identical detail everywhere. Step three is cleanup at full size — dust spots, stray threads, sensor dust — since flaws compress into permanent-looking smudges. Step four is the 100KB target run in JPEG for marketplaces or WebP for your own store. Step five is the zoom test: open the output at 100% and check fabric weave, stitching, serial numbers, and reflective highlights. If micro-detail matters for your category — jewelry, watches, sneakers — and 100KB softens it, crop the hero tighter rather than raising the budget; a closer view at the same bytes shows more.

Page speed is a ranking factor, not a nicety

Search engines measure how fast your images load and fold it into rankings through Core Web Vitals, principally Largest Contentful Paint — usually a hero or product image. Each unoptimized megabyte of imagery delays that paint by a second or more on mid-range phones, and the data on bounces is unforgiving: conversion probability drops steeply with every extra second of load. A catalog compressed to 100KB per image, served in WebP with explicit width and height attributes, routinely cuts image payload by 70–85% versus camera originals — often the single largest performance improvement a store can make, bigger than script optimization or caching tweaks. Beyond rankings, there is money: shoppers on metered connections abandon image-heavy pages that burn their data, and marketplaces quietly boost listings with fast-loading media in internal search. Compression is marketing spend with a permanent return.

Format strategy for sellers and publishers

The format decision splits cleanly by destination. Marketplaces (Amazon, eBay, Etsy, property portals, classifieds) dictate JPEG in their seller guides — follow them exactly, since non-conforming uploads risk silent rejection or mangling. Your own website is a different game: serve WebP (or AVIF for the adventurous) at the same visual quality for 25–40% fewer bytes, which compounds across every listing view. A practical dual workflow covers both: keep a master archive at full quality, export JPEG-at-100KB for marketplace listings, and export WebP for your storefront from the same master. Never chain conversions — each JPEG generation loses detail, so always compress from the master rather than re-compressing a previous output. And keep transparency needs in mind: product cutouts on transparent backgrounds must be PNG or WebP, since JPEG has no alpha channel; budget extra pixels accordingly because transparency edges compress poorly.

Troubleshooting listing rejections and ugly renders

When a marketplace rejects a 100KB file, suspect metadata first: verify the extension is .jpg, the color space is sRGB (Adobe RGB exports confuse some pipelines into dull, shifted colors), and dimensions meet the platform's minimums — many require 1000+ pixels on the longest side for zoom to activate. If the listing preview looks worse than your file, compare the platform's rendered variant against your upload; some platforms apply aggressive sharpening that turns clean compression into crunchy halos, in which case uploading a slightly softer file paradoxically renders better. White-background requirements deserve special attention: shoot true white (RGB 255) rather than near-white, because off-white backgrounds compress into visible blotches and fail automated background checks. Finally, keep every submitted file archived by SKU — when a marketplace flags an old listing's imagery, re-uploading the exact approved file beats regenerating and hoping the pipeline agrees twice.