Contact

Reporting a bug

The more of the following you include, the faster it gets fixed:

• which tool, and the URL of the page you were on;
• what you expected to happen and what happened instead;
• your browser and version, and your operating system;
• the input that triggers it — the smallest example that still breaks.

If an image causes the problem

Please describe the image rather than sending it: its format, rough dimensions, and anything unusual about it. We do not need your file, and we would rather you did not send it. Everything here is designed so that your images stay on your device, and that applies to support too.

Requesting a format

Requests are genuinely welcome. Say what you would use it for — a concrete use case is far more useful than a format name on its own, because it tells us what the one obvious primary action should be.

Security

If you have found a security issue, please put "security" in the subject line so it is seen quickly, and include enough detail to reproduce it. Please give us a reasonable window to fix the problem before disclosing it publicly. We will confirm receipt and tell you when it is resolved.

Licensing and attribution

Questions about the licence of this site, of the upstream Squoosh project, or of an individual codec are best sent by email. The about page lists what the site is built on.

Response times

This is a side project. Expect a reply within a few days; security reports are prioritised. If you have not heard back in a week, send a follow-up — it means the message was missed, not ignored.