Compress Images to 1MB

Why 1MB is the most common limit

One megabyte is the figure that appears on CMS upload fields, form validators, and email attachment rules more often than any other. It is a compromise between quality and transfer time, chosen when most connections were slower than they are now. Meeting it exactly is therefore a routine requirement rather than an optimisation, which is why a tool that works to a stated byte count is more useful than one that offers a quality slider and hopes.

Resizing usually beats compressing hard

A 24 megapixel photo compressed to 1MB has a very small budget per pixel, and the result looks soft. The same photo resized to roughly 1,600 pixels on the long edge and then compressed to 1MB looks noticeably sharper, because you are no longer paying to preserve detail that will be discarded on a screen anyway. Neither operation is better in the abstract; which one is right depends entirely on how large the image will be displayed.

• Image will display small: resize to about 1,600 pixels, then compress. Sharper at the same file size.
• Image needs full resolution: compress only, and accept a softer result.
• Already under the limit: leave it alone, nothing needs to change.
• Transparent or flat graphic: use PNG or WebP lossless rather than forcing JPG.

NoteCheck the result at 100 percent, not zoomed out. Compression artefacts are invisible at normal viewing size and obvious when you inspect them.

Reading a limit that does not state its convention

A form that says 1MB is ambiguous, and the two readings differ by about 5 percent. This tool targets the smaller figure, so the result is accepted under either reading. If a form rejects a file this tool reported as within the limit, that form is using the larger reading or applying a stricter rule, and you need to go lower. The exact byte count is shown after compression so you can compare rather than guess.

• Decimal: 1 MB is 1,000,000 bytes.
• Binary: 1 MiB is 1,048,576 bytes.
• This tool targets 1,000,000 bytes, which satisfies both.
• Aim slightly under the limit rather than exactly at it.

When the target cannot be reached

Some files cannot reach a target without visible damage, and saying so is more useful than quietly returning something that fails. A PNG converted at a small palette can reach most targets but loses colour depth. A very small source is already under the limit. A lossless requirement and a tight limit can genuinely conflict. When that happens, converting to a more compressible format or reducing the dimensions are the reliable answers.

• Already smaller than the target: the file is passed through unchanged.
• Cannot reach the target at an acceptable quality: the result is reported honestly, not claimed as a success.
• Try WebP or AVIF for a better quality at the same byte count.
• Reduce the pixel dimensions as the reliable option.
• If the form insists on JPG, use the highest quality that still fits.