Contact

Get in touch

Every message is read personally — response time is usually one to three business days, occasionally longer during heavy development periods.

What to write about

Bug reports — If a tool produced a wrong result, failed silently, or broke in your browser, please include: the tool you were using, your browser and version, and what you expected versus what happened. If a specific file caused the problem, describing its characteristics helps (size, whether it contained images, how it was created). Please don't send the file itself — given the privacy design of this site, we'd rather not receive your documents.

Tool requests — If there's a utility you keep looking for and can't find a private, client-side version of, let us know. Requests that can run entirely in the browser get priority, since anything requiring a server doesn't fit the architecture.

Corrections — If documentation on this site is wrong, outdated, or misleading, we want to know. This includes technical inaccuracies in explanations, incorrect translations, or a tool description that overstates what it actually does.

Business inquiries — Advertising, partnerships, or licensing questions.

What we can't help with

We can't provide technical support for third-party software, recover data from corrupted files, or reverse operations performed with these tools — since nothing is stored on a server, there is nothing to recover on our end.

Privacy of your message

Emails you send are stored in a standard email inbox and are subject to that provider's terms. Don't send passwords, private keys, personal identification documents or confidential business information. If you need to describe something sensitive, describe it in general terms rather than pasting the actual data.