Compress an image to 1 MB
Three steps. At a 1 MB ceiling format choice almost never matters — both JPEG and WebP produce visually transparent output. Pick whichever the destination accepts.
Upload your image
Drop a JPG, PNG, WebP, HEIC, AVIF, or GIF onto Sukat’s drop zone. iPhone HEIC files are decoded in-browser — no convert-to-JPG detour first.
Set 1 MB as the limit
Type 1 in the Maximum File Size field and switch the unit selector to MB. Pick JPEG for portals that require JPG, WebP for the web (about 25% more visual headroom at this size), or PNG only if you genuinely need transparency.
Convert and download
Click Convert & Download. Sukat binary-searches for the highest quality that still fits under 1 MB. For typical phone and DSLR photos, original dimensions are preserved — the algorithm only touches pixel size if quality alone cannot hit the budget.
When a 1 MB image matters
1 MB is the per-image budget that quietly governs the workflows that move real photos around — email, slides, document portals, and shared albums where size adds up image by image.
- Email photo galleries. Gmail’s 25 MB attachment cap divided by 25 images is 1 MB each — the practical budget when you want to send a small album in a single message. See the Email Attachment Compressor for the per-provider breakdown.
- PowerPoint and Keynote slide images. A 40-slide deck with one 1 MB image per slide stays under the 40 MB sweet spot where decks still email, sync, and screenshare without lag.
- Google Docs and Notion embeds. Both render embedded images comfortably at 1 MB without slowing document scroll on a typical laptop.
- Document portals. KYC verifications, legal evidence uploads, insurance damage claims, and visa supporting documents typically cap each scan at 1–2 MB. 1 MB sits inside almost every portal limit.
- Shopify product hero galleries. The Shopify CDN re-serves anything you upload, but starting from a clean 1 MB hero keeps the source archive lean and skips a lossy round-trip.
- High-quality blog hero images. A 1 MB hero on a WordPress or Ghost article still scores well on Lighthouse when served as WebP and properly lazy-loaded.
- iCloud and OneDrive shared albums. At a 1 MB per-photo budget a 200-photo trip album lands at roughly 200 MB — well under most shared-album quotas.
Built for the 1 MB budget
At 1 MB the constraint is per-image budget arithmetic, not per-pixel quality — the algorithm needs to hit the ceiling exactly, not approximately.
Hits 1 MB, not “around” 1 MB
When you’re packing 25 photos into a 25 MB Gmail attachment, overshooting by 100 KB on each of them tips you over the limit. Sukat’s binary search lands precisely under the ceiling — quality 87, quality 84, quality 86 — until it converges on the highest quality that still fits. Roughly seven re-encodes; you never see the loop.
Original dimensions preserved on nearly every typical photo
1 MB is enough room to fit a full-resolution 24-megapixel DSLR JPEG or a 4032 × 3024 iPhone capture at near-original quality — without any downscaling. The algorithm reduces quality before it touches pixel size; for the photos people actually compress at this ceiling, the output keeps every pixel of the original.
WebP buys you roughly 25% more headroom
The format gap is narrower at 1 MB than it is at tight KB targets, but WebP still carries roughly 25% more visual detail than JPEG at the same file size. Sukat defaults to WebP for that reason. Pick JPEG only when the destination explicitly requires it.
HEIC-aware iPhone input
Most online compressors silently fail on .HEIC. Sukat decodes HEIC in-browser and re-encodes to the target format, so the raw iPhone export goes straight in — no convert-to-JPG detour, no quality loss in translation.
Local, no upload, no signup
Compression runs entirely in your browser via the Canvas API — particularly material when the workflow involves KYC scans, legal evidence, insurance documentation, or visa paperwork. The image never leaves the device. Verify by switching to airplane mode after the page loads.