πŸ“¬ We read every message

Get in Touch

Bug report, feature request, business inquiry, or just a thank-you note β€” we'd love to hear from you. Pick the channel that suits you best.

βœ‰οΈ
Email Send an email [email protected] Best for detailed bug reports, partnership inquiries, press requests, or anything that needs more than a tweet.
𝕏
Twitter / X @pdfduck twitter.com/pdfduck Follow for updates, new format launches, and quick replies. DMs are open for short questions.
βš™οΈ
GitHub @pdfduck github.com/pdfduck Open issues for bugs you've found, suggest new file formats, or browse our public technical notes.
< 48hAvg. email response
24/7Site uptime target
FreeSupport, always
Before you write

Common questions, answered

Before reaching out, take a look at our homepage FAQ β€” most common questions are answered there. The most common ones we receive:

Bug reports

Found a bug? Help us fix it fast

When reporting a conversion problem, please include:

Privacy note: Please don't email us your original files. Because PDFduck processes everything locally, we don't need them β€” and we'd rather you keep your data on your own device. A description of the problem and a screenshot of the output is usually enough.
Business inquiries

Partnerships, press, and sponsorship

Interested in featuring PDFduck in your publication, partnering on integrations, or sponsoring the project? Email [email protected] with the subject line "Business inquiry" and we'll respond within a couple of business days.

Languages

We respond in English or Turkish

Most of the site is in English, but the team is based in TΓΌrkiye. Feel free to write in either language β€” we read both. For other languages, please use English; we'll do our best to understand.