Review before replacing a file
Check the result at the real display size. Product texture, skin, gradients and small text can change when a WebP file is decoded and encoded again as JPG.
If the source had transparency, decide on the background before exporting. Letting another system flatten the file later can create an unexpected black, white or checkerboard edge.
1
Keep the original WebP or higher-quality master.
2
Avoid WebP → JPG → WebP loops.
3
Verify sourceName and outputName for batch or agent runs.
Create a fallback without hiding WebP advantages
WebP to JPG is usually needed when a destination still rejects WebP. Treat the JPG as a compatibility export, not proof that JPG is the better format. Before delivery, check whether transparency was flattened intentionally, whether the chosen background color matches the destination, and whether repeated compression has softened product edges or text. Keep the WebP or original master so later exports do not start from the fallback copy.
1
Pick the matte color before flattening transparent WebP files.
2
Check text and product edges after JPG compression.
3
Keep the WebP or source master for future sizes.
Choose the flattening background deliberately
When a WebP contains transparency, JPG export must create opaque pixels. Do not leave that choice to a later upload system. Pick white, brand color or another deliberate background in QuokkaPix and inspect edges after download.
1
Transparent WebP needs a planned matte.
2
Avoid accidental black or checkerboard edges.