PDF Haven is an open-source project built on a simple premise: everyday document work should not require uploading private files to an unknown server. Every one of the 37 tools runs in your browser using WebAssembly and JavaScript, and the complete source code is public under the MIT licence.
The project is maintained by web engineers and document-tooling contributors who spend their days working with PDFs, spreadsheets and scanned paperwork. The tools are built to solve the same problems we face: a portal that rejects a file for being 200 KB too large, a contract that needs a signature, a scan that needs searchable text, a form that must be flattened before archiving.
There is no company account, advertising network or paid tier behind the site, and no document is ever transmitted. That architecture is also the business model: because processing is local, there is no server bill that has to be recovered through limits, watermarks or upsells.
Each tool is assembled from established open-source engines rather than a black-box conversion service. pdf-lib creates and edits documents, pdf.js renders pages and extracts text, qpdf compiled to WebAssembly handles AES encryption and repair, Tesseract.js performs OCR, Mammoth and SheetJS parse Office files, and PptxGenJS assembles slide decks.
Heavy engines load on demand and are cached for offline use, so the homepage stays light while the tool you choose gets the full machinery. Because the pipeline is visible in the repository, security reviewers can verify that file contents never leave the browser tab.
The guides are written against the live tools, not copied from press releases. Each article is reviewed when a tool or browser behaviour changes, and the updated date is shown beside the byline. We include limitations and trade-offs: which conversions are best-effort, when rasterised output loses selectable text, and which jobs still need a desktop application.
Corrections and reproducible bug reports are handled through the public issue tracker, and security reports through the repository security policy. If a guide claims a workflow works, it has been run end to end on the build that is currently deployed.