Contact us
Questions, bug reports, tool ideas or just feedback — we read everything. No contact forms, no tickets, no tracking: just plain email.
Email us directly
Write to [email protected]We usually reply within a couple of days. No auto-responders, no newsletters — your address is used only to reply to you.
What can you write about?
Bug reports
Found a tool misbehaving on your device or browser? Tell us what happened and which browser you use — we fix fast.
Tool ideas
Missing a small utility that should exist as a private, client-side tool? Suggest it — the best ideas get built.
Translation fixes
Spotted an awkward phrase in your language? Native-speaker corrections are always welcome across all 6 locales.
Anything else
Partnerships, press, or just saying the tools helped you — it all lands in the same friendly inbox.
Before you write — quick answers
Where are my files processed?
On your own device, always. Every tool here is client-side JavaScript: the file you choose is read by the page, converted in memory and offered back as a download. It is never uploaded, so there is no server copy to delete and nothing for us to see — which also means we cannot recover a file for you.
Why is there no account or sign-up?
Because nothing needs to be stored. Without uploads there is no per-user state to keep, so an account would only create a database of email addresses worth attacking. Your settings stay in your own browser, and clearing site data resets them completely.
A tool failed on my file — what should I include?
Tell us the tool URL, your browser and version, the operating system, and the approximate file size and format. If the browser console showed an error, paste that text too. Please do not attach the file itself: we cannot accept confidential documents, and the details above are usually enough to reproduce the problem.
A large file froze the tab — is that a bug?
Usually it is a memory limit rather than a defect. Because processing happens locally, very large files compete with the browser for RAM, and mobile devices have far less headroom than desktops. Try a smaller batch, close other tabs, or run the same job on a desktop browser before reporting it — and tell us the size that failed if it still does.
Can I request a new tool?
Yes, and these are the most welcome emails we get. The tools that fit best are small, self-contained jobs that can run entirely in a browser without a server, an API key or a paid third-party service. Describe the task you are trying to finish rather than the interface you imagine, and it is much easier to build the right thing.