Repo of the Day
alam00000/bentopdf at v2.8.8
Published: Aug 31, 2026
Open repository ↗The Privacy First PDF Toolkit
Summary
BentoPDF is a privacy-first, client-side PDF toolkit that runs in the browser so files never leave the user's machine. It ships 50+ tools for organizing, editing, converting, and securing PDFs, and is self-hostable. The project is dual-licensed under AGPL-3.0 or a paid commercial license.
What it is useful for
Engineers who want to avoid sending sensitive documents to third-party PDF services can self-host BentoPDF or run it directly in the browser. It covers common tasks like merging PDFs, splitting, cropping, rotating, adding watermarks, page numbers, and Bates numbering, plus an integrated PDF editor for annotations, redaction, and form filling. For format conversions, it supports image-to-PDF (JPG, PNG, WebP, HEIC, TIFF, SVG, PSD), document-to-PDF (DOCX, XLSX, PPTX, ODT, Markdown, EPUB), and PDF-to-image or PDF-to-text exports, with table extraction and OCR for scanned files. A "PDF Workflow Builder" tool lets users chain operations together with a visual node editor.
How engineers can use it
The codebase is JavaScript and TypeScript and uses PDF.js. Processing backends (PyMuPDF, Ghostscript, and CoherentPDF) are loaded as WASM modules from the jsDelivr CDN at runtime by default, so no backend server is required. The README documents a Prerequisites section and a Development Setup, but the exact commands are not fully detailed in the README excerpt provided, so readers should consult the Getting Started section for full instructions. Deployment options documented in the README include static hosting on Netlify, Vercel, and GitHub Pages, Docker Compose or Podman Compose, Podman Quadlet for systemd integration, and air-gapped or offline deployments that require custom WASM hosting. The project also supports custom branding, disabling individual tools, and a commercial build variant. A documented limitation is that the default zero-config setup depends on jsDelivr, which air-gapped networks must replace. Open-source use falls under AGPL-3.0, while closed-source or proprietary products require the commercial license.