Contact

Tell us what broke, or what is missing.

One inbox, read by the people who build the tools. Expect a reply within two working days — sooner if it is a bug that blocks a release.

Straight to the inbox.

No ticket system and no chatbot. If your message needs an answer you can act on, it will come from a human.

Something broke.
Tell us the tool, the page URL, your browser and what you expected to happen. If a file was involved, the format and rough size are usually enough to reproduce it — please do not send the file itself.
Something is missing.
Tool requests are welcome, and specific beats general: the job you were trying to finish, the format or platform involved, and what you used instead. Requests that fit the browser-first model get built first.
A guide needs a correction.
Code and configuration drift. If a snippet in an article or pro tip no longer works on a current release, send the article URL and the version you tested — corrections go into the piece, credited if you want the credit.

For bug reports, email is faster than social — the message does not get truncated and it stays searchable when we fix it.

Two answers we get asked for constantly: how a tool handles your files is documented on the privacy page, and commercial use is covered by the terms.