Image compressor
Shrink your photos' file size — for a faster website, a smaller email attachment, or an upload limit. Do a whole set at once and see exactly how many kB each one saved before you download. HEIC, TIFF and the other common formats all go in.
Most common formats, both ways
Read: HEIC/HEIF, PNG, JPG, WebP, AVIF, GIF, BMP, ICO, SVG and TIFF. Write: JPG, PNG, WebP, TIFF, BMP, GIF and ICO. So you can go from almost anything to almost anything — an iPhone HEIC to JPG, a scan to TIFF, a logo to ICO, a photo to WebP. Drop in up to five files at once; they all come out in the format you picked, and you can take them one at a time or all together as a ZIP or TAR.GZ.
About HEIC — the iPhone's own photo format. Your iPhone, iPad and Mac can read HEIC themselves, so open this page on the device the photos are already on and it simply works. A Windows or Android browser has no HEIC reader built in, and Apple's is not ours to hand out, so there you get a clear message instead of a file that quietly fails. Same rule as our GIF maker: when something came off a phone, the phone is the shortest road.
Making images smaller without making them look worse
There are two completely different ways to shrink an image, and people usually reach for the wrong one first. Lowering the quality makes the compressor discard more detail while keeping every pixel. Reducing the dimensions throws away pixels entirely. The second is far more powerful and far less visible, because file size grows with area: halve the width and height and you have removed three quarters of the pixels. A 4000-pixel-wide photo shown in a 800-pixel column on a website is carrying five times more detail than anyone will ever see. Resize first, then compress — in that order you can often cut a file by ninety percent and have nobody notice.
What the quality slider is actually doing
JPEG and WebP work by discarding the visual information your eye is least likely to miss, and the quality number decides how aggressive that is. The useful range is narrower than the scale suggests. Around 80 to 85 is the sweet spot for photographs: below 75 the artefacts start showing as blocky patches in smooth areas and halos around sharp edges, while above 95 the file grows steeply for a difference no one can see on a screen. Some images are harder than others — fine detail like foliage, fabric texture or noise from a phone camera at night compresses poorly, while a portrait with a soft background compresses beautifully.
Aim for a target, not for a percentage
Rather than picking a quality number and hoping, work backwards from where the image is going. For a full-width photograph on a website, somewhere around 150 to 300 kB is generous and a hero image under 200 kB is a good discipline. For a thumbnail, aim under 30 kB. For an email attachment, remember that most mail servers reject anything over 20 to 25 MB in total, and that a set of ten phone photos will sail past that without help. For a web form with an upload limit, read the limit and target comfortably under it rather than exactly at it. Having a number in mind turns this from guesswork into a two-minute job.
Why some files barely shrink at all
If the before and after sizes are nearly identical, the file was already compressed. A JPEG straight off a phone has been through this once, and squeezing it again gives little back while degrading it further — every lossy save loses a bit more, permanently. The same is true of a PNG that has already been optimised. In these cases the only real win is resizing. The opposite case is a screenshot or a scan saved as PNG: those are often enormous and shrink dramatically, though a screenshot of text should stay PNG rather than becoming a JPEG, because JPEG makes a particular mess of sharp black-on-white edges.
Choosing the format while you are here
Compression and format go together. WebP is typically 25 to 35% smaller than JPEG at the same visible quality and every current browser supports it, which makes it the obvious choice for anything going on a website. Keep JPEG when the file is going to someone by email or into a system you do not control, because universal compatibility beats a smaller file when you do not know what will open it. Keep PNG for screenshots, logos, line art and anything needing transparency — trying to compress those as JPEG produces a bigger file that also looks worse, which is the rare case of losing on both counts at once.
What happens to the data inside your photo
Photos carry more than the picture. A phone typically embeds the camera model, the exact date and time, the settings, and often the GPS coordinates where it was taken. That last one deserves thought before you upload a picture of something at your home address. Compression here rewrites the image data and does not carry that metadata across, so the output is generally cleaner than the input, but if stripping it is your actual goal you should use a tool built for that so you can confirm the result rather than assume it. Everything on this page runs inside your browser: the photos are never uploaded, which is why it is instant and why there is no queue.
How this shrinks a file
Two things make a file smaller: a lower quality setting (more compression, a little more blur if pushed too far) and a smaller pixel size (fewer pixels to store). WebP usually compresses better than JPEG or PNG at the same visual quality, which is why it's the default.
Can I convert several photos at once?
Yes — drop in up to five at a time and they are all converted to the one format you picked, whatever they were before. You can download them one by one, or press Download all for a single ZIP (or TAR.GZ). Each converted photo counts as one of your free images for the day.
Will this make my photo blurry?
At 70-85% quality, most photos look identical to the original. Below ~50% you'll start to notice it, especially on sharp edges and text.
Is my photo uploaded anywhere?
No — this runs entirely in your browser. Nothing is sent to a server.
