Why lowering JPEG quality is not always enough
File size depends on pixel dimensions, image detail, format, metadata, and encoder quality. A high-resolution product photo can remain above 200KB even when quality is already visibly degraded.
A more reliable workflow is to constrain the long edge first, then let the encoder find a quality level inside the target size. If the image is displayed at 800 pixels wide, retaining a 6000-pixel original may add bytes without visible value.
Step by step
- Open the batch image processor and add JPG, PNG, WebP, or AVIF files.
- Choose target-size compression and enter 200KB.
- Optionally set the long edge or fixed dimensions for a consistent export size.
- Run the batch and inspect text, facial features, product edges, and transparent areas.
- Download individual files or the complete ZIP archive.
Choose the right format
JPEG is usually a practical choice for photographs, while WebP can produce smaller files at similar perceived quality on supported platforms. Keep PNG or WebP when transparency is required. AVIF can be even smaller, but upload systems and older browsers may not support it.
A PNG screenshot converted to JPEG may shrink dramatically, but transparency and crisp text can suffer. Match the format to the delivery requirement rather than optimising for file size alone.
Local processing and limits
The selected image batch is decoded and encoded in your browser rather than uploaded to an image-processing server. The app, fonts, and dependencies still load over the network.
Large batches consume memory and CPU. Process a smaller group on older phones, and keep the originals until the exported files have been reviewed.