Contact Us

We are a small team and we read every message. The best way to reach us is by email — [email protected].

Send us an email at

We aim to respond within 48 hours on business days.

What to write to us about

Report a bug

Did a tool produce unexpected output, fail to convert a file, or behave incorrectly in your browser? Let us know and we will investigate.

What to include: Include your browser name and version, a description of what happened, what you expected, and (if possible) the type of file you were processing — no need to attach the actual file.

Tool feedback or feature request

Missing a format? Want a new preset size in the image resizer? Have an idea for a tool that should exist? We read every message and prioritise based on demand.

What to include: Describe what you wish the tool did and why it would be useful. The more context the better.

Content or documentation issue

Found a factual error in a blog article, an outdated guide, or a broken link? We appreciate corrections — accuracy matters.

What to include: Link to the specific page and describe the error.

Business or partnership enquiry

Interested in licensing our browser-based processing technology, discussing an integration, or proposing a partnership? We are open to conversations.

What to include: Briefly describe your organisation and what you have in mind.

What to expect

Response time: We aim to reply within 48 hours on business days (Monday–Friday). Messages sent over weekends are answered the following Monday.

Language: We respond in English. If you write in another language we will do our best, but English is most reliable for a complete answer.

Attachments:Do not attach sensitive files (medical images, financial documents, personal photos) to your support email. Our tools are browser-based specifically so that files never need to leave your device — this principle extends to support correspondence too. Describe the issue; we don't need the file itself.

Bug reports: The more detail the better — your OS, browser name and version, and the exact steps to reproduce the issue will help us fix it faster. A screen recording is even more useful than a screenshot.

Before you write — quick answers

Many common questions are already answered in our documentation and blog.

Privacy Policy — how we handle (or don't handle) your files Terms and Conditions — acceptable use and disclaimers About 365tools — our philosophy and how the tools work DICOM Converter — removing PHI from medical images Blog — guides on PDF tools, DICOM, image formats

365tools.net is built and maintained by a small independent team. We do not have a support hotline, live chat, or ticketing system — just email. We appreciate your patience, and we genuinely try to respond to every message.

If you're reporting a security vulnerability, please mark your email subject [SECURITY] and we will prioritise it.