Reduce the file without hiding the product.

Separate compression from resizing

Record the master’s dimensions, format and file bytes. Resizing changes pixel dimensions; compression changes how image data is encoded. If both change at once, you cannot tell which decision reduced the file or damaged a small label. Begin a compression comparison with the same dimensions.

Keep the untouched master and export new candidates from it. Do not repeatedly open a lossy export and save another lossy copy over it. Name each candidate with its format and revision so an owner can choose a particular file instead of an undocumented quality-slider position.

Review the color-space export — Keep the approved master, convert a web copy and inspect the delivered color profile.

Test the format your destination accepts

Lossy encoding trades some image information for fewer bytes. Lossless encoding preserves pixel data while compressing it. JPEG and WebP can be useful for photographs; PNG and lossless WebP serve different needs. Destination support, transparency and the specific image matter more than a universal format winner.

Use an editor or a free comparison tool such as Squoosh to export two candidates. Keep dimensions fixed initially and vary one compression setting. Inspect fine packaging text, high-contrast edges, smooth gradients and small repeated patterns. If a smaller file creates ringing or block artifacts, keep a less aggressive export.

Prepare a supported phone-photo copy — Export HEIC into JPG, PNG or WebP and verify the resulting file before upload.

Measure savings, then inspect the placement

Enter both file sizes below using the same unit. The worksheet reports the arithmetic difference and percentage; it does not predict loading speed, conversion or a search ranking. If the candidate is larger, it reports the increase instead of calling it a saving.

Preview the chosen file at the actual collection thumbnail, product-page display and relevant zoom size. A destination may serve its own transformed version, so inspect the delivered result too. Record bytes and the accepted revision, then test performance in the real storefront if it is part of the project goal.

Keep metadata in the final-file review

Pixel-preserving compression does not by itself prove that color profiles or origin metadata survived the export. Check the final file with your editing or metadata workflow. This matters when a downstream channel needs embedded information, including Google Merchant Center’s AI-origin requirement.

Fayvoro’s downloaded-image metadata has not been verified against that requirement. A re-export, conversion or hosting service may change metadata again. Retain a suitable real-photo fallback until the generated file’s origin information is verified. Fayvoro generates scenes; this worksheet neither compresses a file nor certifies an export.