Include the page URL, browser and operating-system version, expected result, actual result, and steps that reproduce the issue. Use synthetic sample data whenever possible.
ToolGarden information
Contact ToolGarden
Feedback is welcome for broken workflows, browser compatibility, privacy questions, article corrections, accessibility, and responsible security reports.
Last updated: 2026-08-03
What to include
Protect sensitive information
Do not email passwords, API keys, session cookies, identity documents, confidential files, or unredacted customer data. For a security report, provide the minimum safe proof needed to understand the issue.
Response times and what to expect
The site is maintained by one developer; there is no support team. Email usually gets a reply within a few working days. Security reports are handled first; feature suggestions are recorded without a promised delivery date. To be unambiguous: no service level is offered, and there is no phone or instant-messaging support.
Sorting by type
Putting the type in your subject line measurably speeds things up:
- A tool errors or returns the wrong result; include the page URL, browser and OS version, steps to reproduce, and a sample file you are able to share.
- A correction; documentation that contradicts behaviour, an incorrect format claim, a conclusion that has aged out. Name the page and the passage.
- A privacy question; uncertainty about where a particular tool's data goes, or behaviour that looks inconsistent with the privacy policy.
- Accessibility; keyboard navigation, screen readers, contrast or text size. Tell us which assistive technology you use.
- A security report; read the reporting requirements on the security page first, and include only the minimum evidence needed to understand the issue.
Check here first; most questions need no email
The following already have answers on the site, and looking is usually faster than waiting for a reply:
- "Will my file be uploaded?"; every tool page's Supported range and limits table has a Where it runs row stating that tool's data flow. The privacy policy and security page cover it in general.
- "Why is it slow, or failing?"; the model-based tools (background and watermark removal, upscaling, OCR, transcription, stem splitting) download tens of megabytes on first use and run inference on your device. Each tool page's What to know before you start lists its real limits.
- "The output does not match the original"; the comparison table on each tool page states whether an operation is lossless or lossy and what it discards. PDF to Word, image compression and audio transcoding are especially worth reading first.
- "Which formats are supported?"; the limits table on each tool page enumerates accepted inputs and outputs, which beats guessing from search results.
About feature suggestions
Suggestions are welcome, but please say whether the job can be done end to end in the browser. That is the site's only admission test: anything needing server compute, a private API or a paid third-party service to reach usable quality will not ship, because it contradicts the premise that your files stay on your device.
Suggestions already under consideration get recorded, but with no promised date; there is one maintainer, and scheduling follows available time.
What email cannot help with
A few kinds of request cannot be answered, stated here so you are not left waiting:
- Processing files on your behalf. Please do not attach files; the tools are for you to run, and doing it for you defeats the point of local processing.
- Recovering passwords. A PDF whose open password is lost cannot be opened, which is what encryption is for.
- Business partnerships, advertising placement, link exchanges and sponsored content; none of these receive a reply.
- Requests for source code, deployment details or keys framed as a "compliance check" or "security assessment" are not answered.