Contact & support
If you have a question, hit a bug, or want to suggest something, the email below reaches a real person. Please don't send sensitive documents by email — if you need to share an example of a problem, redact it first or describe it instead.
Response expectations: this is currently a small, independently-run project, not a company with a support team on standby. Expect a reply within a few days for most messages, longer for detailed bug reports that need investigation.
Reporting a bug
To help us actually fix it, please include:
- Which tool you were using (Redact PDF / Convert PDF / Compress files / Metadata viewer)
- Your browser and rough version (e.g. "Chrome, updated this month")
- What you expected to happen, and what actually happened
- Roughly how large the file was and how many pages, if relevant (not the file itself)
- Whether it happens every time or only sometimes
Supported browsers
DocClean is built and tested primarily on recent versions of Chrome and Edge on desktop. It's expected to work on recent Firefox and Safari too, since it relies on standard browser APIs, but OCR and large-file performance can vary more on those. Very old browser versions aren't supported.
Known limitations
- Password-protected PDFs may fail to load
- OCR accuracy depends on scan quality — always review each page manually
- Very large files (100+ pages, or very high-resolution scans) can be slow on lower-powered devices, since everything runs on your own device rather than a server
- Handwritten text is much less reliably detected than printed text
- Exported PDFs are page images, so text isn't selectable afterward — see what survives a DocClean export
Resources
For practical guides and checklists, see Resources, or the FAQ for quick answers.