Contact

The fastest way to reach us is by email:

wenxin202305@gmail.com

For bug reports about a specific tool, please include the tool name and the browser version. We do not collect anything from this page.

What to include in your email

• The tool name and the page URL.
• Your browser and version (e.g. Chrome 128, Edge, Safari on iPhone).
• What you did, what you expected, and what happened instead.
• For background-remover issues: the first red error line from the browser console (F12 → Console).

How fast do we reply?

Usually within a few days. This is a one-person project, so replies come between other work — but every message is read.

Suggestions are welcome

The most useful emails are not bug reports but "I keep doing X by hand, could a tool do it?" If a small utility would save you time each week, describe the task — if it can be done locally in a browser, it may well end up on the site with a credit to you.

Home

How to reach us

The fastest way to get a reply is email: wenxin202305@gmail.com. It is read by the person who builds and maintains the tools — there is no support queue, no ticket system and no chatbot in between. Most messages get a reply within one to three business days; if your question is about a broken tool, a useful bug report usually gets a fix rather than just an answer.

What to include in a bug report

A tool that misbehaves is almost always reproducible, but only if we know the exact conditions. Please send:

1. The page URL you were on, for example /pdf-editor.
2. Your browser and version (Chrome 141, Safari 18, Firefox 132 …) and whether you were on desktop or mobile.
3. What you did, step by step — "opened a 12-page PDF, clicked Edit text, clicked on a number, pressed Enter".
4. What you expected and what actually happened.
5. Any red error text from the browser console: press F12 (or Cmd+Option+I on macOS), open the Console tab, and copy the first red line.

About file attachments — please read

Do not attach your actual document. Because the tools run entirely in your browser, we have no way to inspect your file, and email is not a secure channel for private paperwork. If a tool fails on a specific file, describe it instead: format, page count, file size, whether it is a scan or a digital PDF, and whether it is password protected. Nine times out of ten that is enough to identify the cause. If we truly need a sample, we will ask you for a scrambled copy with all sensitive content replaced by dummy text.

What we can and cannot help with

• We can help with: a tool that errors out, a calculation that looks wrong, a page that renders badly on your device, or a feature that would make an existing tool more useful.
• We cannot help with: recovering data you deleted. Everything is stored in your own browser's local storage — if you clear site data, switch to private browsing, or use a different device, the content is gone and there is no backup on our side to restore from.
• We will not do: custom development work, bulk processing services, or anything that requires us to receive your files.

Other enquiries

Corrections to a page's technical explanation, accessibility problems, and questions about the privacy policy are all welcome at the same address. If you are writing about the site or want to link to a tool, no permission is needed — a plain link is fine and appreciated.