The generic cap
Compress an image to 1 MB.
1 MB is the default ceiling of the modern web: university LMS uploads, job portals, messaging avatars. At this cap the fix is usually dimensions, not compression.
- 100% client-side
- Nothing is uploaded
- No account
- Canvas / WebAssembly on your device
Loading compressor…
Why camera photos still bust 1 MB
A 12 MP phone JPEG is 3–6 MB. The portal wants the subject, not the sensor's full output. Downscale to 1600–2000 px on the long edge and the file lands under 1 MB with quality to spare — no aggressive quality search needed.
Expert trap: quality-first at a generous cap
Running a quality search on a 4000 px original wastes bytes on detail nobody will ever see, then softens the parts that matter. Resize first, encode once. Every extra re-encode is another generation loss.
One encode, not two
Go straight from the original to the target in a single pass here: resize, then quality-search to the cap. The tool reports the exact final size so you know what the upload field will see.
Frequently asked questions
Is 1 MB enough for a portfolio image?
For screen display, yes — 1 MB holds a 2000 px JPEG at high quality. For print, keep the original.
JPEG, PNG or WebP under 1 MB?
Photographs: WebP or JPEG. Screenshots and text-heavy graphics: PNG or lossless WebP, which keep glyphs razor-sharp where JPEG would fuzz them.
Does upload speed matter at 1 MB?
On mobile networks, yes. A 400 KB file feels instant where 4 MB stalls; the byte count shown here is the byte count the portal receives.
Can I process a batch of files to 1 MB each?
Yes — the drop zone accepts up to twelve files and each is processed locally, in parallel where the browser allows.
Is metadata stripped?
Yes. EXIF, GPS and camera serials are dropped during re-encode — useful privacy hygiene for any public upload.