what_you_need
Prepare the inputs before opening the apps
- A clean source folder
- The intended use: web, email, marketplace, or archive
- A representative test group
- A separate output location
step_by_step
The working process
-
1
Measure the source folder
Record total size, file count, formats, and the largest files. This gives the batch a measurable target rather than a vague “make it smaller” goal.
-
2
Protect the originals
Keep the original folder unchanged. Compression should create delivery or archive copies unless the loss is understood and accepted.
-
3
Test a representative subset
Use Batch Compress Image on detailed photos, flat graphics, gradients, and text-heavy images. One quality setting can affect these very differently.
-
4
Compare at real viewing size
Inspect edges, faces, text, gradients, and colour blocks. Choose the lightest acceptable setting for the intended destination, not the smallest file at any cost.
-
5
Run and measure the batch
Process the complete folder locally, then compare total size and spot-check outputs before uploading or archiving them.
human_checkpoint
Review before you call it finished
- Was the original folder preserved?
- Were different image types included in the test?
- Is the quality acceptable at the real display size?
- Is the size reduction recorded?
honest_boundaries
Limits and privacy
Practical limitation
Lossy compression removes information. Repeated compression can compound artifacts, and the best setting depends on image content and intended use.
Privacy boundary
Compression and comparison happen locally; the images do not need to leave the PC.
faq
Questions worth answering
Should I compress before or after resizing?
Usually resize first, then compress the final delivery dimensions. That avoids carrying unnecessary pixels and lets you judge the actual published result.