Quick answer
This Ecommerce uploads processing runs locally and does not upload; browser extensions can still read the page. Ecommerce backends often restrict format/dimensions/KB; read the rules before batch compressing.
Why it matters
Local processing reduces upload risk but is not absolute security.
Main, detail and document images may have different rules.
Step by step
- Back up the original; never overwrite the only copy.
- Confirm the target platform's format, dimensions and size limit.
- Cap the longest side first, then quality; change one variable at a time.
- Compare size and sharpness after compressing, and step back one setting if needed.
- Keep the original until the output is confirmed.
Common mistakes
- Chasing the smallest file and blurring text/edges.
- Converting transparent PNG to JPEG, turning transparency white or black.
- Recompressing the same file and accumulating loss.
- Overwriting the original, so a bad result cannot be undone.
Checklist
- Original backed up.
- Output format/dimensions/size meet the platform.
- Text is readable and transparency is correct.
- Verified in the real page/email/upload field.
- Original kept until confirmed.
Key facts
- Main, detail and document images may have different rules.
- Flatten transparent PNG onto white before JPEG.
FAQ
Does Ecommerce uploads processing upload my files?
This Ecommerce uploads processing runs locally and does not upload; browser extensions can still read the page. Ecommerce backends often restrict format/dimensions/KB; read the rules before batch compressing.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: Amazon image requirements