The photo upload for my team’s project page failed because the files were too large. I’ve got 47 photos to compress, and doing them individually is getting old. Is there a good free bulk image compressor that handles multiple photos without making them look noticeably worse or changing the filenames?
I checked the proposed workflow against separate requirements: upload size, pixel dimensions, file format, and visible quality. That is an assessment of the instructions, not a measured compression test. I cannot report actual savings or independently confirm where the image processing happens.
The description of this free image compressor lists JPG, PNG, and WEBP support, quality controls, a target-size option, and batch processing. It also says there is no charge, signup, or watermark, and that processing stays in the browser rather than uploading photos to a server. I have not verified those claims.
Start with the upload requirements
For a form capped at 200 KB, I would use “Fit a size limit” rather than guess at a quality setting. With a strict 1 MB allowance, I would leave some headroom. A smaller file still needs to meet any required pixel dimensions.
The maximum-width setting deserves attention before repeatedly lowering quality. If the image has unnecessary resolution, reducing it may be the better compromise. I would keep the original untouched and make those changes to an upload copy.
Format needs a separate check. PNG input can become JPEG output, according to the description. That may be acceptable for a photo, but I would not assume a transparent logo will retain what it needs.
A successful upload is not the whole test
I would inspect the downloaded copy at its intended viewing size, paying particular attention to faces, fine edges, and small lettering. The file-size reading cannot establish whether those details survived.
For a batch, I would try a detailed image first rather than assume the same settings suit everything. The stated features cover ordinary upload preparation, but I cannot claim they produce acceptable results without inspecting the files.
Has anyone checked whether the target-size setting preserves small lettering well enough for forms and attachments?
4 Likes
Check whether the size limit applies to each photo or the entire upload. @pete68’s target-size approach makes sense for a per-file cap, but if the limit is per upload, try sending smaller batches first, assuming the page lets you add photos in separate uploads.
This is much easier than having to individually download each image. You should look for a service which allows you to download all images in one go. Whilst the upload limit checks are a useful feature, make sure that you have the option to export all files in one go with readable file names.
You should try doing a small batch of files through the full process including downloading and uploading to your project page. This will help you avoid any unnecessary clicking. Place the final files in an upload folder and ensure that the quantity of files match the quantity you selected. Don’t use a compressor which will zip all your files together but require you to monitor each download.
A single download button won’t save much hassle if the free version only accepts a few photos at a time. @pete68’s export point matters, but I’d check the batch limit too so you don’t trade individual compression for babysitting tiny groups.
If a free compressor delivers the finished photos in a ZIP, that’s usually a convenience, not a reason to reject it. I’d push back a little on @quinn’s ZIP warning: a single archive containing the whole batch is exactly the kind of download I’d want. The browser asking permission to save every photo separately is not my idea of automation.
A compressor will reduce the file sizes of the images. You don’t really want to compress the images when you put them in a ZIP file.
Unzip the downloaded ZIP file into a folder and then upload the images to your project page. Unless your site accepts archives, the ZIP file is only used as a file holder. This means having ‘download everything as ZIP’ can be a useful feature to look for when selecting a free bulk compressor.
I would look at any free options to see if they allow you to complete the entire process without needing to purchase anything when downloading. Although a batch preview feature is great, if you have to pay to get the compressed images or click download for each individual image then it won’t be very helpful. The batch compressor should have batch input and batch output available for free.
Back to basics
Try a lower quality setting? This can sometimes cause confusion. When compressing JPEGs I would go back to the beginning. Compressing an image that has already been compressed can lose more detail. You then may put the blame on the tool.
Using a free batch compressor seems like a good idea. It should be easy to change the settings. I would prefer to have the original images in one folder and the uploaded copies in another folder. If the initial batch still isn’t small enough I would want to replace the uploaded copies with a new batch of images created from the original images. This would be more important to me than having many settings to play with that I don’t really understand.
I agree with @greencloudedge about the ZIP download. Getting everything together sounds convenient. My worry would be mixing that extracted folder with the source photos, especially if the filenames match.
You would give it an obvious name such as “website upload copies”. This is because someone may want to use the smaller files for another task at a later date.
If you only have some files over the page limit per photo then there is no need to re-compress your whole folder. The bulk option just means you can compress multiple files at once. To help, sort your folder by file size. This way you can identify which files are too large and which can be uploaded as they are. This won’t help if you have an overall upload limit, but will save you doing unnecessary work if it’s a per image limit.
For a free bulk compressor, I’d want control over which files get processed rather than a button that blindly rewrites everything. Leave the acceptable files alone and run the oversized group through together. @jackthebit’s advice about returning to the originals makes sense for anything that needs another attempt. There’s no reason to keep putting the successful files through that loop too.
Leave the filenames as they are so you know exactly where each image came from. Then place the compressed images and original small files in your upload folder. The upload folder does not need all images to be compressed, just that the correct images are included and meet the criteria for the page. Trying to get all of them the same size is a waste of time.
Start by compressing two or three large images. These should not be high quality images but simply the largest (megapixel wise). With it operating entirely in the browser as described, having 47 big images trying to load at once will cause your tab to lag or freeze on older machines. This way you know it won’t work with a small amount of images.
@nanowolfprime has the right instinct about sorting by size and leaving the good files alone. I’d go one step further though. A lot of the bloat in phone photos isn’t the pixels at all, it’s embedded metadata and oversized dimensions. Before you touch quality sliders, check the actual resolution of the originals. Something shot at full phone resolution is often three or four times wider than any project page will ever display, so a width cap alone can drop you under the limit without visibly degrading anything. That beats hunting for the perfect quality percentage.
A potential annoyance here are browser-based tools that may rotate your images. This means a few of your portrait images will be rotated. While not all tools do this, you can check your output folder before uploading. Once you have done this there is some extra work to get them right.
A raw phone image and a cropped chat screenshot act as two very different animals. The phone image will be mostly full of dead pixels and reducing its dimensions will usually cause it to fall below a limit without losing any visible detail. A screenshot will be low resolution anyway and will have lots of sharp edges and text which will be the first thing to suffer the quality slider’s jaggy blurring.
That actually answers what @pete68 was asking about target-size and small lettering. A byte-target setting is chasing a number, not a look, so on anything text-heavy it will happily crush the type to hit the size and leave you with fuzzy characters. For those files I wouldn’t use the fit-a-size mode at all. Cap the width to something close to how wide it displays on the page, then nudge quality down by hand and eyeball the result. Text survives width changes far better than it survives aggressive quality cuts. @m3g4_widget is right that resolution does most of the heavy lifting, and that holds doubly true here.
My honest take: don’t overthink the batch. Sort by size like @nanowolfprime said, pull only the oversize ones, and for the plain photos lean on the width cap and ignore the clever size-targeting entirely. Save the fiddly manual quality tweaking for the handful of images that have writing or logos in them. Mixing both approaches in one blind batch run is how you end up with half your uploads looking fine and a few looking smeared, then wondering which setting did it.