Contact

Email is the only contact route. There is no contact form because a form would need a server to receive it, and the point of this site is to avoid unnecessary infrastructure. Write to 2961884811@qq.com.

Reporting a bug

A report that can be reproduced gets fixed faster. Include:

• The tool URL. For example /tools/image-compressor/ or /editor/.
• Browser and version. Chrome, Firefox, Safari, or Edge, plus the version number.
• Operating system and device. Desktop or phone matters for memory-related failures.
• The input file. Format, approximate size in MB, and pixel dimensions. Do not attach the file unless it is non-sensitive and you are asked to.
• The steps. What you did, in order, including the control values you used.
• What happened and what you expected. The exact error text on the row or in the browser console is more useful than a summary.
• A screenshot of the tool with the result visible, if the problem is visual.

Do not send identity documents, medical images, client work, or anything else confidential. A description of the file is usually enough to reproduce the problem.

Common issues worth checking first

• A file is rejected as too large. The per-file limit is 50 MB, and images above 40 megapixels are rejected to protect the tab. Both limits apply to the decoded image, not the compressed result.
• A PNG will not reach the target size. PNG is lossless, so the compressor can only reduce dimensions. Convert to WebP or JPEG if the destination allows it. The format guide explains the trade-offs.
• A photo appears sideways. The file carries an EXIF orientation tag that the viewer may or may not honor. Re-encoding through the compressor or editor normalizes it. The EXIF guide covers the details.
• The page is slow with a large batch. Files are processed two at a time to keep the interface responsive. A tab has less CPU than a server, so a large batch of high-resolution photos will take a while.

Corrections and editorial questions

If a guide describes a control that no longer exists, gives a wrong dimension, or states something technically incorrect, send the URL and the sentence. Corrections are applied to the article and the update date is changed. Disagreements about a recommendation are welcome; include the file type and the destination, because the right answer often depends on both.

Privacy and data requests

For access, deletion, correction, or an objection to processing, see the privacy policy for the rights available in your jurisdiction, then email the address above with enough detail to identify the request. Because image processing is local, there is no stored copy of your images to delete. Advertising and server-log data are handled as described in the policy.

Advertising and licensing

Questions about advertising on the site, or about the modified miniPaint editor and its MIT license, can go to the same address. Put a clear subject line so the message is routed correctly.

Response expectations

This is an independent site, not a staffed support desk. Replies usually take a few business days. A reproducible bug report with the browser, tool URL, and exact steps will get a more useful answer than a one-line message. There is no guaranteed response time, and no support by phone or chat.