Contact Us

Every message that reaches [email protected] is read by a person — there is no ticket bot and no auto-responder deciding whether you matter. Messages are triaged into the same four buckets you see in the form above: bugs, suggestions, business inquiries, and everything else. Bug reports get the fastest treatment because a reproducible defect affects every visitor who hits it, not just you.

For bugs, the first step is reproduction: we take your steps, run them in current versions of the major browsers, and confirm the behavior before touching any code. Confirmed bugs are fixed or documented as known issues; things we cannot reproduce get a follow-up asking for the extra detail that usually solves the mystery. Suggestions are logged rather than promised — we keep a running list of requested tools and features, and popular or high-impact requests move up the queue, but no suggestion comes with an implementation date until it is actually scheduled. That is a deliberate honesty policy: we would rather say "logged, no date" than invent a roadmap we cannot keep.

Business inquiries — partnerships, advertising, licensing, media — are answered by a human as well, with a genuine response rather than a brochure. If a proposal is not a fit, we will say so plainly instead of ignoring the thread.

The single most useful bug report contains five things, and the form above pre-fills a template asking for them. The more of these you can provide, the faster we can act:

• The URL of the tool or page where the problem happened.
• The exact steps you took, in order — "uploaded a PNG, set blur to 30, clicked download."
• What you expected versus what actually happened.
• Your browser, version, and platform — for example "Chrome 126 on Windows 11" or "Safari on iPad." Browser bugs are often specific to one engine.
• A screenshot or screen recording if the problem is visual. Anything visible in the picture beats a paragraph describing it.

If the browser console (F12 → Console) shows red error messages, copy them in — they often point straight at the cause. If the bug involves a specific file, describe the file (format, rough dimensions, approximate size) rather than attaching it. Please do not send documents containing personal data: we would rather reproduce the issue with our own test files than have you share something private. And if a tool worked yesterday and fails today with no change on your end, mention that too — timing is a clue.

We aim to send a first reply to every message — bug reports and suggestions included — within about 48 hours, and we usually beat that on business days. That number is a goal, not a contract: volume spikes and holidays can stretch it. If a fix needs investigation, we will acknowledge the report first and follow up once we know more, so you are never left wondering whether the message arrived.

You never need to share sensitive personal information to get help. We do not need your full name, address, phone number, ID numbers, or any account credentials — and you should never send passwords to anyone, us included. An email address (or none at all, if you only want to flag something) and a clear description are enough.

The contact form on this page does not submit anything to our servers. It opens your own email client with the fields pre-filled, and the message travels the same way any normal email does. Your address is used only to reply to your message, and your correspondence is not added to marketing lists, sold, or shared. All of the tools on FreeToolHub also process files locally in your browser, so if you are writing about a file you converted or upscaled, remember that we never saw it in the first place — which is exactly why bug reports that describe the file work better than attachments.