Contact Us

What to include in a bug report

We can usually fix a problem the same week if we can reproduce it. The three details that help most:

1. 1Which tool you were using, and what you were trying to achieve (for example: "compress a 400 MB MP4 down to under 100 MB").
2. 2Your browser and device (Chrome on Windows, Safari on iPhone, and so on), plus roughly how much memory the device has.
3. 3What you expected to happen, and what actually happened — including any error message, exactly as written.

Note: Please never attach the file itself, and never send passwords, identity documents or other sensitive material. A description is enough — your files stay on your device, and that includes when you write to us.

Suggesting a new tool

Tool suggestions are genuinely welcome, and several of the utilities on this site exist because a reader asked for them.

We build a tool when it meets three tests: people actually search for it, it can be done well inside a browser, and it can be done safely and legally. That last one rules out downloaders for other people's hosted media, platform scrapers and document forgery — not because they are hard, but because they harm someone.

If your idea fits, tell us what problem it solves and who it is for. That is more useful than a specification.

Privacy, advertising and business

For anything about data handling, cookies or your rights, please read the Privacy Policy first and then write to support@toolsstars.com with the specific question — you will get a straight answer rather than a link back to the policy.

For advertising partnerships, sponsorships, bulk or API enquiries, or anything else commercial, use the same address with "Advertising / business" as the topic.

Response times

We are a small team, not a support department, but we do read everything. Expect a reply within two business days in most cases, and sooner for security or abuse reports.

There is no live chat and no phone line — email is the only channel, which keeps the service free.