Runs on your device
Compress an image to 1 MB.
A ceiling that is nearly always a house rule rather than a technical one. You keep the resolution, and very nearly the quality.
Quality is searched automatically. If quality alone can't get under the limit, dimensions step down too.
1 image · drop more here
or drop them here · JPG, PNG and WebP
- Original
- —
- Compressed
- —
- Saved
- —
Compression settings
What must it fit under?
Limits & output
Leave empty to keep the original dimensions. Aspect ratio is always preserved.
JPEG has no transparency — transparent areas are filled with white.
Choosing a format
- JPEG
- The safest choice for photographs, and the one most forms and older software expect. No transparency — transparent areas become white.
- WebP
- The sensible default for the web. Roughly 25–35% smaller than JPEG at matching perceived quality, and it keeps transparency.
- PNG
- Lossless. Keep it for flat graphics, screenshots with text, and anything that must stay pixel-exact. Avoid it for photographs, where it is often larger than the original camera file.
AVIF is smaller still, but it is slow to encode and not yet universal, so it is not offered here. The guide below goes into more detail.
Results
Compressing to 1 MB
A limit that is rarely a real constraint
Unlike the tighter ceilings, 1 MB is almost never imposed by a technical boundary. It is a house rule — an internal wiki, a content management system, a team convention set down once and never revisited since. The practical consequence is that you keep essentially everything that mattered about the original.
A photograph brought under 1 MB retains its full pixel dimensions and a quality setting high enough that finding the difference means zooming in and comparing side by side. On most files the search barely has to work, and the result reports a quality figure close to where it started.
A note on the arithmetic, because forms disagree about it: this tool reads 1 MB as 1,024 KB, or 1,048,576 bytes, which is the binary convention your operating system uses when it reports file sizes. A system meaning exactly one million bytes is asking for about 4% less. If something rejects a file that appears to fit, drop the target to 950 KB.
If this is destined for a web page, aim lower
The honest advice on this page is to question the number. One megabyte is heavy for anything that loads in a browser. A page carrying three images at that weight asks a phone on a poor connection for 3 MB before the content is readable, and that delay is the single most common cause of people leaving before the page arrives.
Where 1 MB genuinely earns its place is when the file still has somewhere to go: an image that will be printed, cropped or re-edited later, or an archive copy you want smaller without regretting it in a year. In those cases the pixels are the point and the kilobytes are secondary.
If the destination really is a website, the smaller ceilings are the same tool with a more useful number. Five hundred is a sensible maximum for anything large on a page; two hundred is the figure most upload forms are asking for anyway.
Other limits, same tool: 100 KB, 200 KB, 500 KB. Or read the full guide to formats, quality and file size.
Frequently asked questions
Is 1 MB here 1,000 KB or 1,024 KB?
1,024 KB — 1,048,576 bytes. That is the binary convention, and the one your file manager uses when it reports sizes. Systems that define a megabyte as exactly one million bytes are asking for a slightly smaller file, so if an upload refuses something that looks like it fits, set the target to 950 KB instead.
Will I notice any quality loss at 1 MB?
On a typical photograph, not without looking for it. The dimensions are untouched and the quality setting stays high, so the difference lives in fine texture visible at full zoom. Images with large flat gradients — a clear sky, a studio backdrop — are the ones where careful eyes might spot banding first.
Is 1 MB too heavy for a web page?
For most purposes, yes. It is several times what a well-built page spends on its largest image, and the cost is paid by whoever is on the slowest connection. Unless the image is the entire point of the page and will be viewed full screen, something in the 200 to 500 KB range serves the reader better.
Should I use 1 MB for photos I intend to print?
It is a reasonable compromise if the file has to be small for some other reason, since the resolution survives intact and resolution is what print consumes. If nothing is forcing a limit at all, send the original — printing is the one use where compressing first buys you nothing.