Compress Image to 1MB

Detailed guidance

What the 1 MB tier is really asking

A megabyte is rarely an arbitrary number. It is usually a storage or bandwidth line drawn by whoever administers an upload form, and it is generous enough that they expect real documents rather than thumbnails. That means the correct response to a 1 MB rule is usually to keep resolution intact and let the encoder do the work — the opposite of the reflex to shrink a photo to a postage stamp. Scanned contracts, exported PDF pages, and camera originals all typically clear a megabyte without visible cost. Screenshots of dense text are the exception worth knowing: they encode poorly at high quality, so a slight dimension reduction beats a large quality reduction.

Choosing the format at this budget

JPG remains the safest assumption because most forms were designed around it. WebP is the better technical choice when the destination only renders the image in a browser, since the same budget carries more detail. PNG is lossless and therefore hard to fit inside a cap for photographs, but ideal for diagrams and flat UI art. A practical rule: run the file as JPG first, and if the form rejects the extension, rerun as PNG and expect the tool to push dimensions down to reach the target.

Verifying before you submit

The result card pairs the original weight with the delivered weight, so a 4.8 MB scan showing 920 KB is evidence rather than optimism. Open the export once and check the places a form reviewer will: page corners on a scan, faces on a portrait, and any printed text on a product. Then rename the file to something the receiving system can follow, because generic names cause more rejected submissions than marginal quality does. If the form also states pixel requirements, satisfy those with the resizer before compressing — one clean pipeline beats two competing adjustments.

Working in bulk, offline, and privately

Thirty files run in one batch, which is enough for a full set of tender annexures or a semester of scanned receipts. Because decoding and encoding happen in the browser tab, the work continues without a connection, so a train or a dead zone is not a reason to postpone. Medical documents, legal exhibits, and client photography never transit a server either, which is the difference between a tool you can use for real work and one you only use for holiday photos.

Why a file can fail at 1.02 MB

Rejections at this tier usually come from arithmetic rather than the photograph. Some systems mean 1,000,000 bytes; others mean 1,048,576, and a form that rounds the wrong way will bounce a file that looks compliant in the finder. Add the small chance that the server counts request overhead, and a 995 KB upload becomes a mystery failure. Treat the ceiling as a target instead: aim at 900 KB here, keep the encoder inside its comfort zone, and the file passes on either reading. That margin costs nothing visible and removes the most common cause of a rejected tender annexure or claim document at the last minute.