Contact Us
Questions, feedback or partnership ideas? We’d love to hear from you.
How to reach us
General support & feedback
Tool questions, a conversion or export that failed, privacy questions about how local processing works, feature requests and bug reports.
Copyright / DMCA notices
Report infringing content with the page URL, proof of ownership and your contact details. Put “DMCA” in the subject.
Security reports
Found a vulnerability? Email the steps to reproduce with “Security report” in the subject. See our Security page.
Before you write
What we can and cannot do for you
Most messages we receive are one of two kinds: something on the page is wrong, or something on the page did not work. Both are welcome, and both are answered differently.
- We can correct a specification. If a destination's size, pixel window, byte ceiling or face proportion is wrong on one of our pages, send the page URL and the official link you are reading. Corrections are applied and recorded on the change log; the standard we hold ourselves to is on the methodology page.
- We can fix a tool that breaks. A crop that produces the wrong pixel count, an export that drops a file, a batch that stalls — those are ours to repair, and a browser name plus the steps that led to the failure is usually enough.
- We cannot see your files. Every conversion runs inside your browser, so no image ever reaches a server of ours. That is a privacy property we intend to keep, and it has a consequence: we cannot recover, inspect or re-process a file for you.
- We cannot expedite a third party. A visa portal that rejects an upload, a marketplace that flags a listing, or a passport office that returns a print is outside our reach. We can tell you the rule that is being enforced and where it is published; we cannot intervene.
- We cannot promise an outcome. Where an authority says the final decision rests with a human reviewer, no tool on this site changes that. Passing a file check is not passing a review.
How to write so that we can act
For a correction, the useful message names the page, quotes the figure you believe is wrong, and links the official document. For a tool problem, it names the browser, the tool, the input and what you expected instead. Anything else — a screenshot, a sample file description, a console message — shortens the round trip.
We answer in English. Replies come from a person, not an autoresponder, which is also why a weekend message can sit until Monday. Security reports and copyright notices are read on the same mailbox and are routed separately; the Security page lists what a report should contain.