Do not compress logos and screenshots like ordinary photos
A setting that looks fine on a photograph may damage tiny lettering or a transparent logo. Start with the destination so your format and size choices have a reason.
1. Separate content and destination
Does the logo need transparency? Must screenshot text remain readable? Are product colors important? Record these needs and the formats supported by the receiving system. Renaming an extension is not a conversion.
2. Compare the same detail before and after
Use 100% view to compare matching letters, edges or hair. A fit-to-screen preview may hide defects. Consider PNG or supported WebP for transparency and check the white background when converting to JPG. No format guarantees a smaller file for every input.
3. Approve one image before applying a recipe
A team example such as width 1200px applies to shrinking an original that is larger. Save one result and check text and background before processing other images. In Processing recipes, crop, size, format, compression and naming order can affect results; record each step’s purpose.
4. Review the ZIP before delivery
Extract the ZIP and inspect individual files, names and ordering. Failed inputs may be absent: report missing files and retry from originals. Starting from the original makes comparison easier than repeatedly compressing an existing result.
Before-and-after checks
- Logo: transparency needed → consider PNG or supported WebP
- Screenshot: read small text at 100% → adjust dimensions or byte target
- Photo: compare matching colors and edges → reopen the saved result
Numbers are illustrative, not institutional requirements or measured results.