Batch compression of local images
The first time I used it, I made a stupid mistake: I tried to reduce the quality of an image that was originally 4000 pixels wide by 60%, but the file size still didn’t decrease; instead, the edges of the image became blurry. Only later did I realize that the image actually only displayed 800 pixels in width on the screen – so what needed to be adjusted was the maximum width, not the quality settings.
So, the order should be to consider size first and then quality. For images, starting from a compression ratio of 80%, the loss in image quality is virtually invisible to the naked eye. Moreover, by limiting the maximum width to the actual display size, the file size can usually be optimized in one step. For screenshots, icons, and monochromatic images, PNG format is recommended. This format uses quantization rather than lossy compression, so images with few colors will experience minimal quality reduction without any distortion. However, PNG images used for photos are an exception; converting them to WebP format is usually more efficient than continuing to compress them using PNG.
It features a design that, in my opinion, is quite practical: if the resulting file size after reencoding is larger than the original file size, the original file will be automatically preserved. Some online compression tools lack this feature; you might think the file has been compressed, but in reality, the resulting file could end up being even larger.
You can batch add JPG, PNG, and WebP files together, decode them locally, and then download them one by one or package them as needed.