Email Support
The fastest way to reach us is by email. Use the button below to open your mail app with a support subject line already filled in.
Contact Us
Need help, have suggestions, or found a bug? We'd love to hear from you.
🐞 Report a Bug
Found something that isn't working correctly? Let us know and we'll fix it as quickly as possible.
💡 Suggest a Tool
Have an idea for a new tool or feature? We'd love to hear your suggestions.
We're Here to Help
ToolsWithFun is built around practical tools and the people who use them. If something is unclear, a button does not work, a result looks wrong, or you have an idea that would make the website more useful, please tell us. Helpful messages make it easier to find real problems and decide what to improve next.
How to Contact Us
Email is the main support channel. You can write to alithegamer565@gmail.com or use one of the existing buttons above to start a message with the correct subject. Please send one clear request per email when possible, as this makes it easier to understand and track.
Email Support
General support is suitable for questions about how a tool works, difficulty finding a page, unexpected validation messages, or uncertainty about a result. Include the tool name and the page address. Never email passwords, API keys, payment details, or private Firestore data.
Bug Reports
A useful bug report explains what you expected, what actually happened, and the steps that caused the problem. Please mention your device, browser, and whether the issue happens every time. A screenshot can be helpful when it does not reveal private information.
- Include the exact page or tool name.
- Describe the input you used without sharing sensitive data.
- List the buttons or steps you followed.
- Copy any visible error message exactly as it appeared.
Suggest a Tool
New tool suggestions are welcome. Tell us who would use the tool, what problem it should solve, and what a useful result would look like. A focused idea is more helpful than a broad request because we can understand the required inputs, output, validation, and mobile experience.
Feature Requests
If you already use a ToolsWithFun page and want an improvement, explain the current workflow and the step that feels slow or confusing. Examples include an additional export option, a clearer result, better input validation, a new game level, or a more useful sharing action.
Business Inquiries
For appropriate partnership, advertising, or business questions, use the same email address and write a clear subject line. Explain who you represent and the purpose of the inquiry. We do not accept requests involving deceptive promotion, harmful content, or access to private user information.
Response Time
We try to review genuine support messages as soon as practical. Response time can vary depending on message volume, the complexity of the issue, and whether testing is required. Sending the same request repeatedly may slow down review, so one complete email is usually best.
Before Contacting Us
- Refresh the page and try the action once more.
- Check that required fields contain valid values.
- Try a current version of Chrome, Edge, Firefox, or Safari.
- Confirm that JavaScript and required cookies are not blocked.
- Note the page URL, browser, device, and exact error message.
Frequently Asked Questions
Can I request a new free tool?
Yes. Explain the problem, intended users, required inputs, and the result you would find useful.
Where should I report a broken button or link?
Use the Report a Bug option above and include the exact page URL and the button or link text.
Can support recover private passwords or secret keys?
No. Do not send credentials. ToolsWithFun support will never ask you to email a password, API key, or payment information.
Do you answer questions about tool results?
We can clarify how a tool is intended to work, but important medical, legal, tax, or financial decisions should be checked with a qualified professional.
What makes a support request easier to solve?
A concise subject, exact page URL, reproducible steps, expected result, actual result, and non-sensitive screenshot usually provide the best starting point.