Tool support
Something produced the wrong result, a target was not met and you want to know why, or a browser is behaving oddly. Include the tool, the browser and what you expected to happen.
Contact
Contact us
Three mailboxes, one honest promise: a human reads these, and you will get a straight answer. Pick the address that matches your question — it reaches the same small team either way.
Privacy & data
Data-protection questions, access or deletion requests, or a concern that this site collects something it should not. Every one of them is answered from the same short answer: we hold no personal data.
Terms & licensing
Questions about the terms of service, permission to quote or link to the site, or a request that a page be corrected. Written permission for reuse of the guides is welcome.
Why there is no contact form
Every tool here works entirely in your browser, and the privacy policy states that plainly. A web form cannot keep that promise: it needs an endpoint, and that endpoint stores whatever you type — turning the one page on this site that would handle personal data into the one page that handles personal data.
So the contact channel is email, the channel you already control. If you would rather not write at all, the about page and the terms of service answer most questions before a message is needed.
What to include
- Which tool you used, and the page it was on.
- Your browser and operating system — for example, Chrome on Windows 11.
- What you expected, and what happened instead, including any exact wording on the result card.
- The file's format, dimensions or page count and approximate size. Not the file itself — please do not attach documents to email; a description is enough to reproduce a problem, and it keeps your documents off the internet.
Other pages you may want
- Privacy policy — what data exists, and what never does.
- Terms of service — the rules of using the tools, in plain language.
- About — why the tools work this way.
Contact questions
Why is there no contact form?
Because a form would break the promise this site is built on. A form needs somewhere to send your message, and that somewhere is a server that stores what you type. Since every tool already runs in your browser, we kept the contact channel on email too — so writing to us is the one moment where something leaves your device, and only the words you chose to send.
Should I attach the file that failed?
No, please do not. A description of the file — format, dimensions or page count, approximate size, and the target you set — is enough to reproduce most problems. Sending a file would also put your document into an email inbox, which is the opposite of what this site is for.
How quickly will I hear back?
Usually within a few working days. Messages are read by a person, not a ticket router, so a bug report with the details above is usually answered before you need to ask again.
Can I request a feature or a new tool?
Yes — that is what support@ is for. Describe the file you were trying to reduce, the limit you had to meet and the tool you used, and the case for it. Requests that match real limits (a portal cap, a scan that will not compress further) are the ones most likely to become a guide or an engine.