Contact
For a bug report, include the tool name, browser version and error message. Do not send private images, filenames, EXIF or location data.
Describe a problem without sharing your image
A useful report identifies the failed step, the environment and the visible error. Private pixels and filenames are not needed to explain most converter problems.
In this guide +
What to include in a reproducible report
Describe the route and sequence of actions in ordinary words. A report that says “PNG to JPG, one file, default quality, conversion finished but download did not appear” is more useful than “it is broken.” Include the exact visible error only after removing any private information it contains.
- Tool name and language; no private URL query parameters.
- Browser version, operating system and device category.
- Which step failed: selection, preview, conversion, ZIP or saving.
- Approximate source size, dimensions, file count and chosen settings.
- Expected result, actual result and whether a single-file retry worked.
Use a public sample to separate file and device problems
Try one of the project’s public example images on the matching route. If that sample works while your private source fails, the format, dimensions or file structure may be relevant. If the sample also fails, the browser, blocked assets or device environment may be the better starting point. This is a diagnostic comparison, not a conclusive cause.
Do not upload a private image to another service just to obtain a shareable test case. Instead, describe the characteristics and reproduce with a harmless generated image if possible. A screenshot of an error can expose filenames or other open tabs, so review and redact it before sharing through a configured contact channel.
A short report template
Use this structure and substitute non-sensitive values. Do not include the source filename, image attachment, EXIF or location data. Technical descriptions can still be specific without revealing the image content.
Change one condition at a time when repeating the test: first one file instead of a group, then a public sample instead of the private source. Record which change affected the outcome. Save completed results before restarting, and do not send full browser logs that may contain private URLs or unrelated account information.
Environment
Tool: WebP to PNG. Language: English. Browser: name and version. Device: desktop or phone, with operating system.
Reproduction
One still image, approximately 2 MiB, 1600 × 900. Selected file → preview appeared → Convert → error message. A public sample did / did not work.
Troubleshooting by symptom
Read the specific message before changing settings. A wrong format, an animated input and a memory limit need different fixes. Renaming a rejected file or repeatedly clicking Convert does not address the cause. Save completed results before clearing or reloading a queue.
| Symptom | What to check | Try this |
|---|---|---|
| File rejected | Actual format, animation, bytes and dimensions | Choose the matching tool and a supported still image |
| Conversion stops | Device memory or a decode/encode error | Retry once with one file; use a smaller source if needed |
| ZIP unavailable | Archive byte cap and memory budget | Download individually or split the group |
| Background remains | Opaque pixels rather than alpha | Use an image editor if background removal is needed |
| Page works, tool does not | JavaScript, blocked assets or browser support | Allow required site assets and try a current browser |
Contact support
Use the support email shown above for questions and bug reports. Explain the steps and include a sanitized error message. Do not attach private images, filenames, EXIF or credentials. The site has no upload form for support and does not promise a response time.