{"name":"bentopdf: Process PDFs Privately in Your Browser","description":"BentoPDF is a self-hostable PDF toolkit that processes files in your browser, without server-side processing. It uses WebAssembly builds of PyMuPDF, Ghostscript, and CoherentPDF for a broad set of PDF tools, including editing, conversion, and OCR.","github":"https://github.com/alam00000/bentopdf","url":"https://osrepos.com/repo/alam00000-bentopdf","source":"osrepos.com","sourceDescription":"This repository profile is provided by osrepos.com, an open source repository discovery platform.","repositoryProfile":"https://osrepos.com/repo/alam00000-bentopdf","generatedFor":"open source discovery and AI-assisted research","markdown":"https://osrepos.com/repo/alam00000-bentopdf.md","json":"https://osrepos.com/repo/alam00000-bentopdf.json","topics":["javascript","pdf","web-app","self-hosted","pdf-editor","pdf-converter","pdf-ocr"],"keywords":["javascript","pdf","web-app","self-hosted","pdf-editor","pdf-converter","pdf-ocr"],"stars":null,"summary":"BentoPDF is a self-hostable PDF toolkit that processes files in your browser, without server-side processing. It uses WebAssembly builds of PyMuPDF, Ghostscript, and CoherentPDF for a broad set of PDF tools, including editing, conversion, and OCR.","content":"## Overview\n\nBentoPDF is a privacy-first, client-side PDF toolkit for people who want to edit, convert, organize, or process documents without uploading them to a server. It runs in a web browser and can be self-hosted as static files or with Docker. Its PDF processing includes WebAssembly builds of PyMuPDF, Ghostscript, and CoherentPDF, with Tesseract available for OCR.\n\nThe project is aimed at individuals and teams who want a broad set of PDF tools in one browser-based app, including for private or internally hosted use. Its self-hosted build retains the PDF tools while removing the public-facing marketing pages. See the [repository](https://github.com/alam00000/bentopdf) and [project website](https://bentopdf.com/) for details.\n\n## Key Features\n\n- Merge, split, reorder, rotate, compare, and organize PDF pages.\n- Edit PDFs with annotations, text editing, forms, redaction, watermarks, and page numbering.\n- Convert many document and image formats to PDF, and export PDFs to images, text, tables, and other formats.\n- Run OCR on scanned PDFs to make them searchable and copyable.\n- Secure and optimize PDFs with options including encryption, signatures, compression, metadata removal, and sanitization.\n- Build visual PDF processing pipelines with the workflow builder.\n- Self-host using Docker, static hosting, or an air-gapped deployment with locally served processing assets.\n\n## Use Cases\n\n- Individuals handling sensitive documents who want browser-based PDF tools without sending files to a processing server.\n- Organizations deploying a shared PDF toolkit internally through Docker or static hosting.\n- Teams converting office documents, images, or scanned PDFs without relying on a separate desktop application.\n- Administrators preparing an offline or air-gapped PDF tool deployment, with the required WebAssembly and OCR assets hosted internally.\n\n## Our Take\n\nBentoPDF is an actively maintained, broad browser-based toolkit with a substantial contributor base and multiple deployment options, though its AGPL licensing and some external asset requirements deserve attention.\n\n**Good fit if:**\n- You want many PDF operations in one browser app and prefer files to be processed client-side.\n- You need a self-hosted deployment, including Docker or an air-gapped setup.\n- Your project can comply with AGPL-3.0, or you have a suitable commercial license for proprietary use.\n\n**Look elsewhere if:**\n- You need server-side PDF processing or a backend API, which the project does not describe as its operating model.\n- You need a permissive license for a closed-source deployment and do not plan to obtain the commercial license.\n- You require every feature to work without external services or setup, and cannot host the needed WebAssembly or OCR assets yourself.\n\n## Project Health\n\n| Signal | Value |\n|---|---|\n| Status | **Active**: regular commits and releases |\n| Last commit | 2026-10-25 (today) |\n| Commits, last 90 days | 100+ |\n| Releases, last 12 months | 54 (latest v2.8.10, 2026-10-19) |\n| Contributors | 75 (top contributor: 38% of commits) |\n| Issues closed, last 90 days | 28+ (typically closed in 49 days) |\n| Pull requests merged, last 90 days | 39 (typically merged in 8 days) |\n| Project age | 13 months |\n\nChecked on 2026-10-25 with the GitHub API.\n\n## Project Facts\n\n- Language: JavaScript\n- License: AGPL-3.0\n- Stars: 16.1k\n- Forks: 1.4k\n- Topics: adobe-acrobat, docker, hacktoberfest, javascript, jpgtopdf, pdf, pdf-converter, pdf-editor\n- Website: https://bentopdf.com/\n- Archived: no\n\n## What You Need\n\nDetected in the repository:\n\n- Node.js (from package.json)\n- A Dockerfile, so it can run in a container; a Compose file sets up the related services\n- Automated checks on GitHub Actions\n\n## Getting Started\n\nRun the self-hosted Docker image:\n\n```bash\ndocker run -p 3000:8080 ghcr.io/alam00000/bentopdf-simple:latest\n```\n\nThen open `http://localhost:3000`. For other deployment methods and configuration, see the [README](https://github.com/alam00000/bentopdf#readme).\n\n## License in Plain Words\n\n**AGPL-3.0** (network copyleft).\n\n- Commercial use: yes\n- Modify and redistribute: yes\n- You must keep: the license notice\n- Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service)\n- Includes an explicit patent grant from the contributors\n\nA summary, not legal advice: the LICENSE file is what applies.\n\n## Considerations\n\n- BentoPDF is actively developed, with regular commits and releases and contributions from many people; contributor activity is not concentrated in one person. Issue handling is slower than pull request merging, so allow for time when relying on project responses.\n- The project requires a browser for its client-side workflow and Node.js to build from source. Docker and Compose are supported for deployment.\n- Advanced processing modules are configured to load from a CDN by default. Offline deployments require preparing and serving the relevant assets; browser security requirements also apply to some conversions, including Office file conversion.\n- The Digital Signature tool may need a separately deployed CORS proxy when certificate issuer data must be fetched from external providers.\n- The project is dual-licensed under AGPL-3.0 and a commercial license. Proprietary deployments should review the licensing terms before adoption.","metrics":{"detailViews":1,"githubClicks":0},"dates":{"published":null,"modified":"2026-10-25T14:20:27.000Z"}}