One address, no form
Get in touch.
Bug reports, tool requests, security disclosures and corrections all arrive at the same mailbox. There is no contact form here because there is no backend to receive one — and no wish to store messages we do not need.
Please expect days rather than minutes. Naming the tool and your browser in the first line usually removes an entire round of questions.
Read this first
Do not email us your documents.
This matters more than anything else on the page. Please never attach a confidential file to a bug report — not a contract, not a medical record, not an identity document, not a statement. Email is not a private channel, and we deliberately do not want custody of your files.
It would also be self-defeating: the entire architecture of this site exists so that your documents never reach us. Sending one by email would route around the protection you came here for.
- Instead of the file
- Describe it: page count, approximate size, scan or digital original, protected or not.
- If a sample is unavoidable
- Reproduce the fault with a document containing nothing real, and send that one.
Bug reports
Six things that make a report fixable
Your document and its contents stay in your browser during processing. With consent, anonymous content-free events can contribute to aggregate activity and safe failure counts, but they do not give us your document or a replay of your session. If you email us, we receive the details you choose to send. These six details are usually enough to reproduce a fault without ever seeing your file.
- 01
The tool
Its name or the page address — “Split PDF” or /split-pdf. There are enough tools here that “the converter” is ambiguous.
- 02
Your browser and version
Chrome 141 on Windows 11, Safari 18 on iOS, and so on. PDF rendering and WebAssembly behaviour differ meaningfully between engines.
- 03
What you expected to happen
One sentence. Sometimes the tool is behaving as designed and the documentation is what is wrong.
- 04
What actually happened
The exact error message if there was one, or a description of the wrong output — pages in the wrong order, text missing, file larger than the original.
- 05
The steps you took
Options you changed, how many files you added, whether you dropped them or used the picker, and whether a retry behaved differently.
- 06
The file in the abstract
Page count, approximate megabytes, scanned or digitally generated, password-protected, a form, or exported from some specific application. Never the file itself.
Subject lines
What to write in the subject line
- Bug
- A tool produced the wrong result or refused to run. Name the tool in the subject.
- Security
- A vulnerability or a way to bypass a protection. Triaged before anything else.
- Request
- A tool that is missing, or an option an existing tool should expose.
- Correction
- Something on a guide, format or tool page that is factually wrong.
Before reporting a limitation, it is worth checking the tool’s own page — every published tool lists what it cannot do, and the answer may already be written down there.
Before you write
Why is there no contact form?
Because a form needs a server endpoint to receive it, a place to store what it receives, and a spam-filtering layer in front of it — three things that hold your data. Email already solves the problem using infrastructure you already trust, so adding our own would mean collecting more about you in exchange for nothing.
How quickly will I get a reply?
This is a small independent project, not a support desk with shift coverage, so please expect days rather than minutes. Clear reports with the browser and tool named get answered faster, simply because they need no follow-up round trip.
Can I send you the PDF that failed?
Please do not, and especially not if it is confidential. Email is not private and we do not want custody of your documents — that would undo the entire point of processing files locally. If a specific file misbehaves, describe its characteristics instead: roughly how many pages, roughly how large, whether it is a scan, whether it is password-protected, and which tool failed on it.
I found a security vulnerability. Where does that go?
The same address, with “security” in the subject line so it is triaged first. Please include enough detail to reproduce the issue, and allow a reasonable period for a fix before publishing it. The security page sets out the disclosure process in full.
Will you build the tool I need?
Possibly. The constraint is that it must be genuinely achievable in a browser tab without uploading the file — that is what rules out the heavier office-format conversions rather than lack of interest. Tell us the actual task you are trying to complete rather than the feature you imagine solving it; the task is more useful information.