Contact

Bug reports and corrections to the guides are read first. Feature requests are read second, which is honest rather than discouraging - the tools are deliberately narrow.

Email

contact@example.com

Replies usually arrive within two business days. There is no support queue and no ticket number; it is one inbox.

What to include in a bug report

PDFs are varied enough that "merge does not work" cannot be reproduced. These five details make a report actionable:

  • Which tool, and which option - for example "split, page ranges, value 1-3,5".
  • The exact message shown on the page, if any.
  • Browser and version, and whether it is desktop or mobile.
  • What the source file looks like: page count, whether it was scanned, whether it came out of an office suite, and whether it is encrypted.
  • What you expected and what happened instead.

Please do not attach the document itself unless it is a synthetic file you created for the test. A confidential contract is not needed to debug a page-count problem, and it should not be sent to a stranger's inbox any more than it should be uploaded to a website.

Corrections to the guides

If a guide is wrong about how a reader, a printer or a filing rule behaves, describe the case and the source. Corrections are applied to the page and the "last updated" line changes; there is no public changelog, because a wall of revisions helps nobody who is trying to merge two files.

Advertising and privacy requests

Questions about cookies or about data protection rights go to the same address and are handled under the privacy policy. If your request concerns advertising data, note that Google controls most of it - the privacy page links to the settings where ad personalisation can be turned off.

Written by the PDFNest team. Last updated November 19, 2026.