Compress an image to 1 MB
The 1 MB target is preset: the page finds the highest JPG quality that fits and shrinks pixels only when quality alone cannot get there.
Your images
Settings
Generated images
- Nothing uploaded
- Free, no sign-up
- Strips EXIF
- Batch files
Twelve listing photos off a phone, and the brokerage website, the rental portal or the gallery's submission form rejects the first one: file must be under 1 MB. Etsy and eBay took the same photos without complaint — their ceilings sit at 12 to 20 MB, and 1 MB is what Etsy's own photo guidance recommends for quick uploads, not a wall. The systems around them make it one. This page targets 1,048,576 bytes per image and finds the highest JPG quality that still fits.
The files that trip it come straight off a camera roll. A 12 MP phone photo with HDR on is 2 to 4 MB, the 48 MP mode on current iPhones and Pixels produces 5 to 12 MB, and a mirrorless JPG at Fine runs 8 to 14 MB. A listing page displays none of that extra weight, so landing at 1 MB usually costs nothing you can see without zooming in.
Before dropping files in, read the limit twice: 1 MB per file, or 1 MB for the whole upload? Forms word this carelessly, and the two cases need different targets. Per file is this page. For a total budget, the math is below, and it usually ends on the 500 KB or 200 KB page or in one merged PDF.
How it works
The target is already set; what you control is the source files and how you read the result cards.
Drop in the camera-roll originals
Choose, drag or paste (Ctrl+V) JPG, PNG, WebP or HEIC files, one or a whole shoot. Use the originals, not copies that came back through a chat app or a marketplace download — those were compressed once already, and a second pass shows.
Leave the target, check the format
The settings panel opens on JPG with 1 MB (1,048,576 bytes) locked in. Change the format only if the destination insists on PNG or WebP; PNG has no quality dial, so it reaches the target only by shrinking the dimensions.
Generate, read the tags, download
Press Generate images. Each card lists old size → new size, a target met tag, the percentage saved and the output width × height (with an arrow from the original size when the page had to downscale). Compare opens a before/after slider; download each file or all of them as one .zip.
Where 1 MB is a hard cap, and where it is only advice
The marketplaces themselves are roomy: Etsy accepts listing photos up to 20 MB and recommends staying under 1 MB for quick uploads, eBay takes images up to 12 MB, and MLS boards typically allow 10 to 20 MB per photo. A 3 MB phone shot sails through all of them.
The hard 1 MB caps sit in the systems around them: brokerage and property-management websites fed by the MLS, rental-application portals, gallery and photo-contest submission forms, supplier catalogs, job-application headshots, forum attachments. Those reject the file outright and rarely say by how much.
Per file or per upload? Do the division before you compress
"Images up to 1 MB" can mean each image or all of them together. If the form counts the total, divide by the number of photos: five images in 1 MB is 200 KB each, two is 500 KB each, and those target pages do the job. Ten images means 100 KB apiece, where product photos start to soften — cut the count before the quality.
For paperwork that must arrive as a single file, reduce each page's pixels first, then build the PDF on the JPG to PDF page with its quality slider around 60–70. The PDF re-encodes every page at that slider, so its weight is decided there, not by the JPGs you feed it; merging first and hoping the PDF shrinks does not work.
What the 1 MB target does to typical files
The page searches JPG quality between 5 and 96 in up to 12 rounds, pixels untouched, and keeps the highest quality that lands under 1,048,576 bytes. Only when the lowest quality still overshoots does it shrink the image 15% a step, re-encoded at quality 72, up to ten times; if even that fails, the card reads smallest possible instead of target met.
- HDR is the surprise. Photos from recent iPhones and Pixels carry a second, smaller gain-map image to drive HDR screens, often a few hundred KB of the total. The re-encode keeps the picture and drops the gain map, so the output is a standard SDR JPG — what every listing site makes of it anyway.
| Source | Typical original | Usual result at 1 MB |
|---|---|---|
| Phone, 12 MP HDR (4032 × 3024) | 2–4 MB | Pixels kept, quality about 55–75 |
| Phone, 48 MP mode (8064 × 6048) | 5–12 MB | Pixels kept only around quality 10–20, or several 15% steps down to about 3,000 px — set Max width first |
| Camera, 24 MP JPG Fine (6000 × 4000) | 8–14 MB | Pixels kept at quality roughly 25–40; Max width 4000 buys quality 60 or better |
| Real-estate HDR blend, 3000 × 2000 | 1.5–3 MB | Pixels kept, quality 80–90, no visible change |
| PNG screenshot or mockup (2560 × 1440) | 1–4 MB | Saved as JPG at quality 90 or above; fine text may fringe |
1 MB is 1,048,576 bytes here, and 1,000,000 on some forms
This page counts the way Windows does: 1 MB is 1,048,576 bytes, or 1,024 KB. macOS Finder and plenty of upload scripts call 1,000,000 bytes a megabyte. A result the card reports as 1010.0 KB is 1,034,240 bytes: under the first number, over the second, and the error reads file too large either way.
If a form refuses a file this page tagged target met, the size is almost certainly between those two numbers. Lower the quality in the general compressor until the card reads under 976 KB, or take 10 to 15% off the width on the resize page, which costs less visible quality.
Frequently asked questions
Will 1 MB hurt the zoom view on Etsy or eBay?
Not for a 12 MP photo: it fits under 1 MB with every pixel kept at a quality in the 55–75 range, which holds up in a zoom viewer. Etsy displays listings at 2,000 px and eBay's zoom is happy at 1,600 px, so the file carries more pixels than either shows. Check Compare before uploading; blocking usually means the source was already squeezed by a chat app.
Why did the output dimensions change?
Because no JPG quality between 5 and 96 got under 1 MB with the pixels untouched. The page then shrinks 15% a step and re-encodes at quality 72, and the card shows the new width × height. At 1 MB this happens with 48 MP phone shots and 10,000 px scans, almost never with 12 MP photos.
Should I resize to the listing's display size before compressing?
When the photo is far bigger than the site shows it, yes. The search protects pixels first, so a 48 MP or 24 MP file meets the target at a quality that shows in skies and walls. Type 4000 in Max width (px) — or 2000, already more than Etsy displays — and the same 1 MB buys a quality of 60 or better.
My HDR photo looks flatter after compressing. Why?
The gain map that drives HDR displays is dropped in the re-encode, so the output is a standard SDR JPG. Listing sites, email and nearly every CMS strip it on their end, so what buyers see is unchanged, and the file is a few hundred KB lighter for it.
I need 800 KB, or 2 MB, not 1 MB.
The presets run from 20 KB to 1 MB; pick the page just under your limit, which is 500 KB for an 800 KB cap. For anything above 1 MB, use the general compressor's quality slider and read the exact size on the card. Landing a little under a limit is safe; landing over is what gets rejected.
Can I run a whole product shoot at once?
Yes. Drop in the whole folder; each file gets its own search for the best quality under 1,048,576 bytes, and the results come down as one .zip. The only limit is your device's memory, which matters for a phone holding a hundred 48 MP files, not for a laptop.
My file is 1.2 MB. Is it worth running through?
Only if something rejects it. Going from 1.2 MB to 1 MB throws away a little quality for a saving nobody notices; the target pages earn their keep on 3 to 15 MB originals. If yours is the total-upload case, do the per-file division instead.
Are my product photos uploaded to LivreImage?
No. The JPG encoding runs on your own device through the browser's canvas; the site never receives the file. The one thing downloaded is the HEIC decoder, about 1 MB, the first time an iPhone HEIC is dropped in, and it is cached after that.