PDF Tools is a free, MIT-licensed collection of browser-based PDF tools. Here are the public sources behind the promises on this website, and the limits those promises do not cover.
Open source, with a real license
Inspect the public source repository and its MIT license. Source availability is not a claim that every third-party dependency uses the MIT license or that the software has a third-party security certification.
Local document processing
The currently released PDF tools process selected document contents in the browser, rather than sending them to a document-conversion server. The all-tool local-processing audit documents synthetic-input browser tests for all 14 shipped tools, including network boundaries, temporary resources and reset/exit behavior. These are project-owned tests, not an independent audit or a guarantee against compromised browsers or extensions.
Opening the site still downloads code and assets from GitHub Pages, which receives standard request metadata including IP addresses. That is separate from document processing. Read Privacy and local processing for the hosting boundary and storage details.
Clear and reset: what actually disappears
Clear files and Start over release the app's references to selected files, previews, results and temporary object URLs. They do not securely overwrite operating-system memory, delete files already downloaded or erase originals, caches or printouts. See the data lifecycle specification and the Help and FAQ for the behavior available to users.
Current release and limitations
The public catalog offers 14 implemented browser workflows; the tool directory reflects the available tools. See supported features and limitations for 50 MiB input limits, PDF page quotas, signature changes and unsupported OCR, permanent redaction, password unlocking or cloud features. For the history of published source changes, inspect repository commits. A published workflow is not a promise of support for every PDF or device.
Feedback, contribution and security concerns
Read the contributor and pull-request workflow to propose changes. Ordinary reproducible defects can be reported using public GitHub Issues, with browser details, steps and only synthetic test files.
Never attach private, personal, financial, password-protected or confidential PDFs to public issues. For suspected security vulnerabilities, check the repository's Security page for an enabled private reporting option before sending sensitive details. Private vulnerability reporting is not guaranteed to be available; public issues are not a confidential security inbox.