We read every single message that lands in our inbox. Whether you found a bug, have an idea for a new tool, or just want to say hello, your email matters to us. Image Tools Kit was built by a small team that genuinely cares about making image workflows easier for everyone, and that starts with listening to the people who use these tools every day.
This page walks you through the best way to reach us. Because we are a small team, a little context in your first email goes a long way toward getting you a useful answer on the first reply.
Send us a message
Use the form below and your message will be sent straight to our inbox. You’ll normally hear back from us within two business days.
General inquiries
For anything that does not fit neatly into the categories below, drop us a line at imagetoolskit@gmail.com. We handle general questions, feedback about the site, and anything else you are curious about. We aim to reply within two business days.
What to include
To help us respond with something useful rather than a round of back-and-forth questions, consider including the following details in your initial email:
- Your name or preferred alias
- A clear subject line that sums up your question
- The tool you were using when the issue came up
- Your browser and version (for example, Chrome 124 on Windows 11)
- Your operating system and device type
- Steps to reproduce the problem, listed one through so we can follow them exactly
- Any screenshots or screen recordings that show what you saw
Feature requests
We love hearing your ideas. Image Tools Kit started because someone wished there was a simpler way to compress an image without uploading it to a server, and many of our tools came directly from user suggestions. If there is something you wish these tools could do, please tell us.
How we evaluate ideas
Every feature request gets logged and reviewed. We evaluate ideas based on a few core principles: Does it align with our privacy-first approach? Does it benefit a meaningful number of users? Can it run client-side? We cannot promise that every idea will ship, but we can promise that every idea is heard.
Tips for a strong feature request
- Describe the problem you are trying to solve, not just the solution you have in mind
- Explain how often you would use the feature
- Mention any existing tools or workflows you currently use for the same task
- Include mockups or sketches if you have them, though plain text works just as well
- Let us know if you would be willing to test a beta version before it goes live
Bug reports
Bugs happen, and we appreciate you taking the time to report them. A well-written bug report is one of the most valuable contributions you can make because it helps us fix problems faster and prevents them from affecting other users.
Before you report
If you have a minute, try the following before you send your report. In many cases, the issue resolves itself:
- Refresh the page and try the action again
- Clear your browser cache and local storage, then reload
- Try a different browser to see if the issue is browser-specific
- Check that your browser is up to date
- Disable browser extensions one at a time to rule out conflicts
What to include in your report
When the issue persists, send us an email at imagetoolskit@gmail.com with as much of the following as you can provide:
- The exact name of the tool you were using
- Your browser name and version number
- Your operating system and device
- Step-by-step instructions to reproduce the issue
- Expected behavior versus actual behavior
- Screenshots, screen recordings, or error messages from the browser console (press F12 to open it)
- File size, format, and dimensions of the image you were working with, if applicable
If the issue involves a potential data privacy concern, please escalate it to our security address instead. We take those reports very seriously.
Press and partnership inquiries
Are you a journalist, blogger, educator, or organization interested in covering or integrating Image Tools Kit? Send your email to imagetoolskit@gmail.com with a subject line like “Press inquiry” or “Partnership proposal” so we can route it quickly.
For press inquiries, include your publication name, deadline, and angle. For partnership proposals, let us know what your organization does and how you envision the collaboration.
Security disclosures
If you have discovered a security vulnerability in Image Tools Kit, please send your disclosure to imagetoolskit@gmail.com rather than filing a public issue. Public disclosure before a fix is available puts all of our users at risk.
What to include in a disclosure
A plain-text email is perfectly fine. The following details help us verify and address the issue quickly:
- A brief description of the vulnerability and its potential impact
- The specific tool or page where you found it
- Steps to reproduce, including any relevant configuration details
- The browser and operating system you tested on
- Any proof-of-concept code or screenshots that demonstrate the issue
- Your preferred method of attribution or anonymity (we will respect your preference)
Our commitment
We ask for a reasonable window to investigate and patch the issue before any public disclosure. We will acknowledge your report promptly, keep you updated, and credit you in the fix announcement if you wish.
Response times and expectations
We are a small team, and we believe in setting honest expectations. Here is what you can generally expect after reaching out:
- Security reports: acknowledged within 24 hours, with a substantive follow-up within 72 hours
- Bug reports: acknowledged within two business days, with a fix or status update within five business days when possible
- Feature requests: logged immediately, with a personal reply within five business days
- General and press inquiries: a reply within two business days
During major release cycles or holidays, response times may stretch slightly. We appreciate your patience.
What happens after you write to us
Here is a quick overview of what to expect after you hit send, so you are never left wondering whether your email disappeared into a void:
Acknowledgement
You will receive an automated acknowledgement confirming we received your message. This is simply a receipt. A real human response follows shortly after.
Triage
Our team reviews incoming messages daily and sorts by urgency. Security issues jump to the top of the queue, followed by bugs, feature requests, and general inquiries. We then assign each message to the team member best equipped to handle it.
Follow-up
When we respond, we aim to give you a useful answer rather than a placeholder. If we need more information, we will ask specific questions. If we cannot fix something right away, we will explain why and let you know whether it is on the roadmap.
Frequently asked contact questions
Do you have a live chat or phone support?
Not at this time. Email is our primary support channel because it gives us the space to investigate thoroughly and respond with detailed answers.
Can I send you an image to look at?
Yes, we encourage it. Since our tools are privacy-first and process images in the browser, we are comfortable reviewing attachments. Mention in your email that you are attaching a file so we know to expect it.
Do you offer custom or enterprise features?
Image Tools Kit is free and open to everyone. We do not currently offer paid tiers or custom builds, but we are open to discussing partnerships that align with our mission. Reach out and let us know what you have in mind.
Is there a community forum?
We are building one. In the meantime, the best way to connect with us and other users is through email. We plan to launch a community space where users can share tips, request features, and help each other troubleshoot.
Can I contribute code or translations?
Absolutely. We welcome contributions from the community. Send an email to imagetoolskit@gmail.com describing what you would like to contribute and we will point you to the right resources.
Thank you for taking the time to reach out. Every email we receive makes Image Tools Kit a better product for everyone, and we are grateful for a community that cares enough to write.