Get in Touch
Have feedback, a feature request, or found a bug? We'd love to hear from you. Choose the best way to reach us below.
Ways to Reach Us
We're a small team, but we read every message. Click any option below to jump straight to the contact form with the subject pre-selected:
General Feedback
Open contact form →Best for: feedback, feature requests, general questions. Response time: 24-48 hours.
Bug Reports
Open contact form →Best for: reporting broken tools, incorrect outputs, or UI glitches. Please include browser version and steps to reproduce.
Partnerships
Open contact form →Best for: business partnerships, integration requests, media inquiries.
Feature Request
Open contact form →Best for: suggesting new tools or features you'd like to see on ToolsHub.
DMCA / Copyright
Open contact form →Best for: reporting copyright infringement. We respond within 48 hours.
GitHub
github.com/irsalamBest for: developers who want to inspect code, suggest improvements, or report issues via pull requests.
Social Media
Coming soonWe'll be launching our social media accounts soon. Check back later!
Send Us a Message
Fill out the form below. Your message will open in your default email client, ready to send.
🔒 Your message opens in your email client. We don't store your data on any server.
Common Questions
Before reaching out, check if your question is already answered here:
Are your tools really free?
Yes, every tool on ToolsHub is 100% free with no sign-up required. We're supported by unobtrusive Google AdSense ads. See our About page for more details on how we operate.
Can you add a specific tool?
We'd love to hear your suggestion! Send us an email with the subject "Feature Request" describing the tool you'd like to see. We prioritize new tools based on user demand and how well they fit our privacy-first, browser-based architecture.
A tool isn't working for me. What should I do?
First, try refreshing the page or trying in a different browser (we support Chrome, Firefox, Safari, and Edge - latest versions). If the issue persists, submit a bug report with: (1) which tool, (2) what you expected vs what happened, (3) your browser and device, and (4) steps to reproduce.
Do you offer an API?
Currently, no. All our tools run client-side in the browser. However, since our code is open source on GitHub, you can fork the project and integrate the tool logic into your own application.
Can I advertise on ToolsHub?
We use Google AdSense for all our advertising and don't accept direct ad deals. If you're interested in reaching our audience, you can target our site through Google Ads by adding our domain to your placement targeting.
How do I report a copyright issue?
If you believe any content on ToolsHub infringes your copyright, please send a DMCA notice to contact us with the specific URL and proof of ownership. We'll respond within 48 hours.
Response Times
We're a small team, so we appreciate your patience. Here's what to expect:
- Bug reports: Acknowledged within 24 hours, fixed or workaround provided within 3-5 business days for critical issues.
- Feature requests: Acknowledged within 48 hours. We can't promise to build every suggestion, but we read them all and prioritize based on demand.
- General feedback: We read every message but may not respond individually to "thanks" or simple comments.
- Partnership inquiries: Reviewed weekly. Expect a response within 5-7 business days if there's a fit.
- Press / media: We prioritize these and typically respond within 24 hours.
How to Write a Helpful Bug Report
If you're reporting a bug, including the following information will help us fix it much faster:
- Which tool: The exact tool name and URL (e.g. "Image Compressor at /image-compressor/").
- What you did: Step-by-step what you did before the bug occurred. Be specific (e.g. "Uploaded a 5MB PNG, set quality to 50%, clicked Download").
- What you expected: What you thought would happen (e.g. "I expected a compressed JPG to download").
- What actually happened: What went wrong (e.g. "Nothing happened - the button did nothing").
- Browser and version: e.g. "Chrome 120 on Windows 11" or "Safari 17 on iPhone 14".
- Any error messages: If you saw an error message on screen or in the browser console (F12 → Console tab), include the exact text.
- Screenshots: If possible, attach a screenshot of the issue.
The more detail you provide, the faster we can reproduce and fix the issue. Thank you for helping us improve!