Is there one free compressor that handles JPG, PNG, and WEBP without converting everything to the same format? I’m updating a small recipe site and have 37 images in a folder, including PNG graphics with transparent backgrounds.
I’ve been reading about lossy and lossless compression, but I’m not sure which distinction matters for a mixed batch. I’d prefer to keep the original file types and save compressed copies separately so I can compare them before uploading.
A PNG can come out as a JPEG. That’s the detail I’d check before getting too pleased with a smaller file, because fewer kilobytes don’t automatically mean I’ve got the right result. For an ordinary photo, that conversion may be fine. For a logo that needs transparency, it changes the decision completely.
My first check wouldn’t be the percentage saved. I’d look at the downloaded image at the size people will actually see it, especially faces, fine edges, and small lettering. A file that meets an upload limit but makes the important text hard to read hasn’t really solved my problem.
That’s also why I wouldn’t apply a batch setting blindly. I’d test a detailed picture first, inspect the result, and then decide whether the same approach makes sense for the rest. Batch processing is available, but it doesn’t remove the need to check what I’m keeping.
I’d keep the original separate, too. The compressed copy is for uploading; I don’t need to give up the starting file just to satisfy a form.
For a 200 KB cap, the direct route is “Fit a size limit” with 200 entered as the target. The same option covers 100 KB or 50 KB requirements. With a strict 1 MB allowance, I’d aim a little below it rather than treat the exact boundary as something worth chasing.
I’d also separate file size from pixel dimensions. They’re different requirements, and meeting one doesn’t guarantee the other. If the file’s still too large, reducing unnecessary resolution through the maximum width setting can make more sense than repeatedly lowering quality on a huge picture.
That’s the part of this image compressor I’d pay attention to: I can work toward a target size or choose a quality setting, then download the result. I’d check the receiving site’s dimension requirements before changing width, though. A smaller file isn’t useful if I’ve made it too narrow for the form.
The practical setup is straightforward: it accepts JPG, PNG, and WEBP, and it’s completely free, with no signup or watermark. Processing happens in the browser rather than by uploading the photos to a server. For several pictures, there’s the batch option once I’ve checked a representative result.
I don’t see a reason to bring a paid photo editor into an everyday attachment-size problem if these controls cover the requirements. Still, I wouldn’t confuse an easy download with a finished check.
My verdict: I’d use it for routine photo uploads with tight size caps. If transparency matters, I’d make the output format my deciding check, not the number of kilobytes saved.
Also keep the file names. If you have an existing recipe site then this is more important than the sizing controls. When you compress they will remain as PNGs but they will also get a suffix added to them. This means you will need to go through renaming them. I would test it with a small mixed batch of files first to ensure that when they download they have the right names and extensions. The fact that it says accepts JPG, PNG and WEBP does not mean it keeps them.
Before compressing an image folder ensure that you know what types of images are being used on your recipe pages. If you’re using any system to generate thumbnails or other image sizes, then you may want to regenerate these after replacing the original image files. This way you will be sure you have a nicely compressed folder without having visitors downloading the old images.
There will be a lot of variation in how much your images save. Some images will really reduce in size whilst others won’t change very much. This could be a good compressor if it’s leaving images that are already compressed as they are.
Yes one compressor will do all three types (JPG, PNG & WEBP). But make sure that it’s not converting them all to the same file type. Whilst it may say it ‘supports’ those file types, unless it says that it will keep the files as their original file type then I wouldn’t rely on it. You’ll want to have the option to keep them as original or individual settings for each file type.
This doesn’t necessarily mean that you’re not losing any image data. Whilst it may keep them as a JPG you’re still going to lose some detail due to it being re-compressed. It may keep them as a transparent PNG but it will reduce the colour palette. This may be fine if you’re using it for a simple graphic but if you’re using it for something like a soft shadow or fade it can look quite poor. You won’t know if it’s been lossy or lossless based on the file extension.
For this job, I’d care more about these controls than a big advertised savings percentage:
This is easy to miss. Just because it has been processed does not mean it will be smaller. If your compressor is not automatic, make sure to check the size of the image before and after. Don’t include them.
This is a cleanup task. You wouldn’t want to run this on the same folder every time you update your recipe. Once an image has been optimised there is no point running it through a lossy setting again. Only process images that are new or have been updated. It’s fine if you get a few images that haven’t changed. You don’t need to reduce the quality to get every row to show a decrease.
