GitHub Issues
Best for bug reports, feature requests, and technical questions.
Open an IssueContact
Have questions, feedback, or found a bug? We'd love to hear from you.
Contact Channels
Twitter / X
Quick questions, feedback, and announcements.
Tweet at UsFor privacy inquiries, security reports, or business matters.
Send EmailBefore You Contact Us
Privacy Questions
Read our Privacy Policy first. It covers all data handling practices in detail.
Feature Requests
Check the About page roadmap section. Your idea might already be planned.
Bug Reports
Include: browser version, OS, image format/dimensions, steps to reproduce, and expected vs actual behavior.
Security Issues
Report security vulnerabilities privately via email, not public GitHub issues.
Common Questions
Can you add support for [format]?
We evaluate format support based on browser compatibility, library size, and licensing. HEIC output requires patent-licensed libraries we cannot include for free. AVIF is planned once browser support is universal.
Why did my compression fail to reach the target size?
Some images cannot reach very small target sizes without unacceptable quality loss or resizing. The tool tells you the minimum achievable size and suggests resizing as an alternative.
Does FileToolkit work offline?
Yes, once the page loads, all tools work without internet. The service worker caches assets for offline use (PWA support coming soon).
Is there an API I can use?
Not currently. FileToolkit is designed for interactive browser use. A CLI version for developers is on the roadmap.
Can I self-host FileToolkit?
Yes! The project is open source (MIT license). Build with <code className='bg-zinc-100 dark:bg-zinc-800 px-1.5 py-0.5 rounded text-sm font-mono'>npm run build</code> and deploy the <code className='bg-zinc-100 dark:bg-zinc-800 px-1.5 py-0.5 rounded text-sm font-mono'>out</code> folder to any static host.
Open Source
FileToolkit is built in the open. Contributions, issues, and discussions welcome on GitHub.