You have a photo that is simply too big. A job portal refuses anything over 2 MB, an email bounces back, or the product shots on your site take four seconds to appear on a phone. The reassuring part is that a typical 5 MB photo from a modern phone can usually be brought down to around 300-500 KB with no difference you can actually see. You can do the whole job in a browser tab with a free image compressor - no software, no account, no queue.
Why file size matters
- Upload caps. Job applications, insurance claims, visa forms and university portals routinely cap each file at 1, 2 or 5 MB - and rarely explain why the upload failed.
- Email limits. Most providers reject messages above roughly 20-25 MB once encoding overhead is counted. Four untouched phone photos can break a single message.
- Page speed. Images are almost always the heaviest thing on a web page, and oversized ones are the most common reason a site feels sluggish on mobile.
Lossless, lossy, and what "no quality loss" really means
Lossless compression
Lossless formats such as PNG - and WebP in its lossless mode - store the image so it can be rebuilt pixel for pixel. Nothing is thrown away. On photographs, though, the savings are modest - typically 5-25%.
Lossy compression
Lossy formats such as JPEG and standard WebP deliberately discard information your eye is bad at noticing: subtle colour shifts, fine detail in busy areas, high-frequency noise. At a quality setting around 80, what goes missing is generally invisible on a photograph even at 100% zoom, while the file can be 80-90% smaller.
So be honest about the phrase. "Compress without losing quality" almost never means bit-for-bit lossless. It means without visible quality loss - and that is a target you can hit reliably once you know where to look.
JPEG, PNG or WebP?
| Format | Best for | Watch out for |
|---|---|---|
| JPEG | Photographs and smooth gradients | No transparency; re-saving the same JPEG repeatedly degrades it |
| PNG | Screenshots, logos, diagrams, text, transparency | Enormous files if used for photographs |
| WebP | Almost anything on the web; roughly 25-35% smaller than JPEG at equal quality | Some older desktop software and print shops still prefer JPEG |
A simple rule: if it is a photograph, use JPEG or WebP. If it is a screenshot, a logo or anything with sharp text, use PNG or lossless WebP - a JPEG will smear halos around the letters.
Resize first - this is the big win
Here is the step almost everyone skips. A photo from a current phone is often 4000 pixels across. If it is going into a 1200-pixel slot on a web page, you are shipping roughly eight times as many pixels as anyone will ever see. Cutting the dimensions costs nothing visually and saves far more than any quality slider.
- Email attachments and upload portals: 1600 px on the long edge is plenty.
- Web and blog content: 1200-2000 px wide.
- Full-width hero images: 2400 px, no more.
- Screenshots: keep the native size, or the text goes soft.
A worked example: a 5 MB, 4032-pixel-wide phone photo, resized to 1600 px and saved as JPEG at quality 80, typically lands near 400 KB. That is roughly a 92% reduction, and on any normal screen the two look identical.
Step by step, in your browser
- Open the image compressor in a new tab and drag your photo onto it.
- Set the target width first, choosing from the sizes above rather than guessing.
- Pick the output format - JPEG or WebP for photos, PNG for screenshots and graphics.
- Start at quality 80 and check the resulting size. If you need it smaller, step down to 70, then 60, reviewing the preview each time instead of dropping straight to 40.
- Download under a new filename such as
photo-1600.jpgso the original stays untouched.
The quality check before you send it
- Zoom to 100%, not to whatever fits the window - artefacts hide at 30%.
- Look at gradients such as skies and studio backdrops, where banding shows first.
- Look at skin tones. Faces show mottling long before landscapes do.
- Look at text and hard edges for halos or fuzz.
- Keep the original. Compression is one-way, so archive the untouched file before overwriting anything.
Why a browser-based tool is the privacy-safe option
Plenty of online compressors upload your picture to a server, process it there and hand back a link. For a landscape photo that may not bother you. For a scan of your passport, a payslip or a medical form, it should. A tool that works inside your own browser never transmits the file at all: it is decoded, resized and re-encoded on your device, and nothing crosses the network. That is the approach used across the free tools at 1mail.lt.
One related case: if what you need to shrink is a document rather than a photograph - five scanned pages a portal insists on receiving as one file - compression is the wrong tool. Combine them with the free PDF merger instead, as described in our guide to merging PDF files for free. And if these images are heading into a newsletter, it pays to verify your email list before sending first.
Frequently asked questions
Does compressing an image reduce its resolution?
Not by itself. Compression changes how the pixels are stored; resizing changes how many pixels there are. They are separate steps, and for big savings you usually want both.
What quality setting should I use?
Start at 80 for photographs. Between roughly 75 and 85 you get most of the size benefit while artefacts stay invisible in normal viewing. Below 60 you will start to see it on skies and faces.
Can I restore quality after compressing?
No. Lossy compression permanently discards data, and re-saving at a higher quality number only makes the file bigger without bringing detail back. This is exactly why you keep the original.
How do I get a photo under a limit like 500 KB?
Resize the long edge to 1600 px and save at quality 80 - that alone clears 500 KB for most photos. If it is still too large, reduce the width to 1200 px before touching the quality slider again.
