Write to [email protected].
A useful report says which browser you were using, what format the file was, and how large it was. If a file failed to compress, the exact error message is more helpful than a description of it. There is no need to attach the image unless it is the only way to show the problem.
Before you write
Many questions are already answered elsewhere:
- Frequently asked questions on the home page
- Compressing JPG — quality settings and repeated compression
- Compressing PNG — why a PNG sometimes refuses to shrink
- Compressing WebP — format trade-offs
- Privacy policy — what happens to your images
Reporting a problem
A useful report usually contains four things. Without them it can be hard to reproduce what you saw.
- What you did. Which page, which settings, and roughly what kind of image. One file or a batch?
- What you expected, and what happened instead. The exact wording of any error message is genuinely useful.
- Your browser and version. The compressor relies on browser image APIs, and support for them differs, so this is often the answer by itself.
- The image, if you can share it — only if it is not private. Do not send a photo you would not want to hand over.
What is not offered
There is no paid support, no custom development, and no service that compresses images for you on a server. PicCocoon is a browser tool, and everything it does happens on your own device.