Report a bug

Found a tool doing the wrong thing? Tell us and it gets fixed. Reports here go straight to whoever built that particular tool, not into a support queue — so the more precisely you describe what happened, the faster it turns into a fix.

What makes a report we can act on

A good bug report answers three things, and it does not need to be longer than that:

• Which tool, by name — “Compress Image”, “PNG to WebP” — so it lands with the right person.
• What you did: the kind of file you gave it, roughly how big, and any setting you changed from the default.
• What happened versus what you expected. “The download was blank” or “the file came back larger, not smaller” tells us far more than “it did not work”.

If you can, add the browser and device you were on — a bug that only shows up in one browser is common, and knowing which one narrows it down immediately. You do not need to attach the file itself, and please do not send anything private; a description of the file is enough, because the tools run on your device and we never see your files anyway.

What happens after you send it

Reports are read regularly. A clear one that we can reproduce usually gets fixed quickly, and because the tools are small and self-contained, a fix to one rarely risks breaking another. If we cannot reproduce what you saw, the details you gave — browser, file type, setting — are exactly what let us work out why, so nothing you include is wasted.

Not a bug, but something’s missing?

If the tool worked fine and you just wish it did more — a format it does not yet handle, an option it is missing — that is a request rather than a bug, and the request form is the better home for it. Same goes for a tool that does not exist yet: describe the job and what usually goes wrong elsewhere, and it may become the next thing built. Either way, the note you send shapes what gets worked on next.

Use the form below to report the bug. The clearer the description, the sooner it is fixed.