How OpenPDF is built and verified
Last updated:
OpenPDF is an independent project maintained by one developer. This page explains how document processing works, what the browser can keep and how we check the tools and their descriptions.
Local document processing
The web tools read, edit and recognise text in PDFs on your device. OpenPDF does not send your document content to its servers for processing. Saving, printing or sharing passes the file to the destination you choose.
Some operations need a connection: OCR resources may need downloading, certificate signing may request public certificates to complete a chain, and optional timestamping sends a signature hash through OpenPDF’s proxy to the selected authority. Desktop AutoFirma exchanges the document with the application on the same computer.
What your browser can keep
Closing a tab does not erase all OpenPDF data. Annotations, notes and placed images can remain in that browser profile, alongside preferences and cached app resources. Local storage is not a backup or an OpenPDF account, and OpenPDF does not add its own encryption to stored annotations.
You can remove annotations in the app. To remove all local OpenPDF data, use your browser’s site-data settings for openpdf.app; this also removes preferences. Save a PDF copy when you want to keep or share your changes. See the privacy policy for details.
Connections, measurement and ads
Local PDF processing does not mean that the website makes no network requests. Hosting, consent management, advertising, usage measurement and support use external services. Contact forms send the information you choose to submit.
Analytics waits for the consent manager to report permission or that the purpose does not apply. Our usage events exclude document names and content. Advertising code waits for known choices from the provider; the provider applies those choices, which may allow personalised, non-personalised or limited ads. Rejecting personalisation does not mean that all advertising requests stop.
Use Help & privacy → Cookie preferences to review the available options. The privacy policy describes providers, local data and these controls in more detail.
How we check reliability
The project includes automated tests for document operations and browser journeys, using sample PDFs. Builds and reviews help detect regressions; they cannot establish compatibility with every PDF, browser or certificate.
Available memory, document structure and the operation affect what can be processed. Compression may change the document’s appearance or properties. Check the resulting PDF before relying on it, especially after compression or signing.
Visible signatures and certificate signatures
Sign PDF places a drawn, typed or image signature on a page. It does not create a certificate-based digital signature or verify the signer’s identity.
Electronic signature signs with a .p12/.pfx certificate, or uses desktop AutoFirma for supported certificates and devices. Validation depends on the certificate, its trust chain and status, the resulting document and the recipient’s validator. Check the recipient’s requirements and validate the saved result; OpenPDF does not guarantee acceptance by a particular organisation.
Content and corrections
Tool descriptions should match the available behaviour and explain relevant limitations. We revise them when we identify a mismatch. Tests provide evidence for the cases exercised, not a general certification or a promise that every issue will be caught before release.
Earlier comparison pages were removed because we could not keep their claims adequately verified. The date on this page records its latest content review, not the date of a complete product audit.
Reporting a problem
Write to support@openpdf.app with the tool, your browser or app version, the steps and what happened. Do not send confidential PDFs, passwords, private keys or certificates. A description of the problem is the starting point; we may ask for more information if needed.
Support is maintained by the project’s developer. There is no guaranteed response or resolution time.
Funding
OpenPDF uses Google AdSense display advertising where available and accepts voluntary Buy Me a Coffee contributions. Advertising is separate from tool controls and editorial content. The project does not accept payment for tool listings or sponsored editorial content.