Contact PDFZaap

Questions, bug reports, corrections or feature ideas — email contact@pdfzaap.online.

What to include

  • Bug reports: which tool, what you expected, what happened, and your browser and device (e.g. "Chrome 126 on Windows 11"). Do not send the contents of any document — a description is enough.
  • Corrections: the page URL and what is wrong. Accuracy of the guides matters more than anything else on this site, and corrections get fixed quickly.
  • Privacy questions or requests: see the Privacy Policy for the details of what the site does and does not collect, and how to reach us about data.
  • Feature ideas: what the tool would do and for whom. Local, browser-based ideas fit the project best.

What to expect

This is a small project. Most messages get a reply within a few days; bug fixes and corrections land in the next update to the site. If you report a bug with a document, please do not paste confidential content into the email — a summary is all that is needed.

Quick answers before you email

A large share of the questions we receive already have a full written answer on the site. Checking these first is usually faster than waiting for a reply:

Who replies

Messages are read by the same small team that builds the tools, so a bug report goes straight to the person who can fix it. Replies are currently in English; you are welcome to write in Urdu or Bahasa Indonesia as well, and we will do our best to respond in kind.

One thing we will never ask for

PDFZaap is designed so that your documents never leave your device, and that principle extends to support: we will never ask you to email us your PDF, share a password embedded in a protected file, or send account details. There are no accounts. If a message claiming to be from PDFZaap asks for any of these, it is not from us.