What “to 1MB” means
TargetKB treats 1MB as a maximum, not a visual guess. An upload-ready result is no larger than that limit. It never adds useless bytes just to make the number look exact.
Compress image to 1MB.
Bring an image below a 1MB upload limit while preserving as much detail as the target allows. The 1MB maximum is already set—add a JPG, PNG, or WebP to begin.
Drop one image here
JPG, PNG, or WebP · up to 60 MB
Your image never leaves this deviceQuality first · Dimensions only reduced when necessary
Your proof appears here
See whether the result passes, what changed, and how the quality looks before downloading.
Exact output sizeBefore / after viewChange report
What changes first
For JPG and WebP, TargetKB searches quality at the original dimensions first. If that cannot meet 1MB and resizing is allowed, it reduces dimensions in reported steps. Auto may use WebP when it is the more practical result.
Where your image goes
Nowhere. Decoding, re-encoding, comparison, and download happen in this browser tab. Account and payment servers never receive the image bytes.
A PRACTICAL 1MB GUIDE
Pass the file-size check without hiding the trade-offs.
The receiving website may also specify dimensions or a file format. Follow those rules together with the 1MB maximum.
Common reasons to use 1MB
- Website and CMS uploads
- Email attachments
- Forms with a 1MB image limit
A reliable way to get there
- Keep the prefilled 1MB limit.
- Select a required format if the destination has one.
- Verify size and dimensions in the result report.
QUESTIONS ABOUT 1MB
Before you upload the result.
Check the destination site’s format and dimension rules as well as its file-size limit.
Does under 1MB count?
Yes. TargetKB treats 1MB as the maximum and does not add unnecessary data just to make the file exactly 1MB.
Does TargetKB keep the original file?
No. Processing stays in your browser, and TargetKB does not receive the image bytes.
Need a different limit?
Open the flexible KB and MB compressor