Compress Image to 1MB
Tell us the size you need and we handle the rest. The compressor searches for the highest quality that still fits under 1MB, reducing dimensions only if quality alone cannot get there.
Tell us the size you need. We handle the rest.
Drop your image here
or
Choose ImageYou can also paste an image with Ctrl+V
Images are processed on your device and never uploaded.
• •
Runs on your device — nothing is uploaded.
Working…
0%
- Original
- Result
- Saved
- Quality
How to compress an image to 1MB
- Select your photo — JPG, PNG, WebP, HEIC and AVIF all work.
- The target is already set to 1MB. Change it if you need a different ceiling.
- Press Compress.
- Check the result — it will be at or just below 1MB — and download.
When you need a 1MB image
A 1 MB ceiling is about transport, not display. At this size the visual cost of compression is close to zero for almost any photograph.
- Upload limits on forms and portals that specify "max 1 MB per file" — extremely common for document and certificate uploads.
- Messaging apps that re-compress anything larger; sending a 1 MB file means the recipient gets your compression rather than the app's.
- Website media libraries where you want originals preserved but storage kept sane.
- Sharing RAW-derived exports with a client for review.
- Backing up a photo library at roughly a fifth of the space.
How the 1MB compressor works
Hitting a byte target precisely is a search problem, not a formula. Here is what runs when you press the button:
- Analyse. The image is decoded and measured — dimensions, format, whether it has transparency, and its true byte size.
- Estimate. A first quality guess is derived from the ratio of 1MB to the original size. This is only a starting point, never the answer.
- Binary search on quality. The image is re-encoded and measured, then the quality range is halved toward the target. Eight to twelve encodes are usually enough to land within a few percent.
- Reduce dimensions, but only if needed. If even the lowest
acceptable quality overshoots, the scale factor
√(target / current)is applied with a small safety margin and the quality search restarts at the new size. - Refine upward. If the first success lands well under 1MB, the search tries a larger scale to spend the remaining budget on pixels rather than leaving it unused.
The result is the largest, sharpest image that still fits — not the first one that happens to be small enough. Landing at 1MB minus a hair is the goal; landing at a third of 1MB is a failure, even though it technically fits.
Getting the best quality at this size
1 MB is enough that even a 48 MP photo usually keeps every pixel.
- Expect quality 80–90 at full resolution for a 12 MP photo — that is above the threshold where most people can tell the difference even at 100% zoom.
- Consider WebP for archiving. At a 1 MB budget, WebP holds materially more detail than JPEG and every current browser reads it.
- Do not compress twice. If you will later need a 100 KB version, make it from the original file, not from this 1 MB copy.
Will the quality drop?
Some quality is always lost when a large photo is squeezed into 1MB — the question is whether you will notice. The result panel shows an honest verdict:
- Excellent — indistinguishable from the original at normal size.
- Very Good — differences visible only when pixel-peeping.
- Good — fine for web and messaging use.
- Reduced — visible softening; acceptable for thumbnails and forms.
- Low — the target is aggressive for this image; consider raising it.
If you would rather keep every original pixel and accept whatever size results, tick Keep original dimensions in Advanced Settings — the tool will then solve with quality alone, and tell you if it cannot reach the target.
Supported formats
Input: JPG, PNG, WebP, GIF, BMP, HEIC/HEIF and AVIF. Output: JPG (default and smallest for photographs), WebP (smaller still, keeps transparency), or PNG (only sensible for flat graphics).
HEIC and AVIF decoders are downloaded on demand, so pages stay light for everyone who does not need them.
Frequently asked questions
Are my images uploaded to your server?
No. The image is decoded, processed and re-encoded by your own browser using the Canvas and Web Worker APIs. There is no upload endpoint for this tool — open your browser's network panel while you use it and you will see no request carrying image data.
What if my image is already under 1MB?
The tool tells you so and offers the original file unchanged — there is no reason to re-compress something that already fits. You can still force a pass if you want it closer to 1MB.
Is 1MB compression basically lossless?
Not technically — JPEG and WebP always discard some information. But at 1 MB for a typical phone photo the encoder runs at a quality level where the difference is not visible without pixel-level comparison.
My photo is 900KB already. Should I still compress it?
No, and the tool will tell you so. It offers the original unchanged rather than degrading a file that already meets your limit.
Why is the result slightly under the target instead of exactly on it?
Encoders do not accept a byte count — they accept a quality setting, and the resulting size is whatever it is. The search aims for the 97–100% band below your target and never goes over, because a file one byte too large fails the upload it was made for.
What happens to my file when I close the tab?
It is gone. The image only ever exists in your browser's memory as an object URL; closing or refreshing the page discards it. Nothing is written to our servers, and nothing is stored on your device unless you download the result.