An open-source PDF editor you can audit
Most PDF tools ask you to believe a privacy promise. PdfCanvas ships the source, so you can read what it does with your file instead of guessing.
What MIT means in practice
You can use the library in commercial products, modify it, and redistribute it. There is no per-seat fee, no activation server, and no license key that expires. The only requirement is keeping the copyright notice.
The editor UI and the engine are the same code that runs on this site. There is no paid build with extra features hidden behind a plan.
What is in the repository
- The core engine: PDF.js rendering, PDFium text editing, pdf-lib export.
- The full editor shell, importable as pdfcanvas/editor.
- TypeScript types for every public method and option.
- A competitor comparison with the gaps listed honestly.
Why open source matters for documents
A PDF editor handles material people would not post publicly. With closed client code, the only evidence that a file stays local is the vendor's word. With open code, anyone can check where the bytes go, which worker is loaded, and whether a request is made.
It also removes the pricing trap: no feature is unlocked by a subscription, and no export is watermarked to push an upgrade.
Where it is not the right tool
PdfCanvas does not fill AcroForm fields, does not perform certified digital signatures, has no OCR, and does not offer secure redaction. Whiteout covers content visually; it does not remove it from the file. For regulated workflows, use a tool built for them and verify the output.
Frequently asked questions
+Can I use it at work?
Yes. The MIT license allows commercial use. You can embed the editor in an internal tool without paying for seats.
+Is the hosted editor the same as the library?
Yes. The site mounts the published pdfcanvas package, so what you test here is what you install.
+Where do I report a bug?
On the GitHub repository. Include the browser, the PDF type, and the steps that reproduce the problem.
+Do you accept contributions?
Yes, through pull requests. Small, focused changes with a clear reproduction are the easiest to review.