Skip to main content

​
General

BentoPDF is a privacy-first, browser-based PDF toolkit. It lets you manipulate, edit, merge, convert, and process PDF files entirely in your browser. No files are uploaded to a server — all processing happens locally on your machine.
Yes. BentoPDF is licensed under AGPL-3.0 and is completely free to use. There are no usage limits, no watermarks, no hidden fees, and no premium-only features. Essential tools should be accessible to everyone.
No. Every tool in BentoPDF processes files entirely in your browser using WebAssembly. Your files never leave your device. We cannot see them, and neither can anyone else.
BentoPDF works in all modern browsers:
  • Chrome / Edge 90+
  • Firefox 90+
  • Safari 15+
BentoPDF includes 130+ tools covering PDF organization, editing, conversion, OCR, digital signatures, compression, security, and more.

​
Features

Convert to PDF: JPG, PNG, WebP, SVG, BMP, HEIC, TIFF, PSD, DOCX, DOC, ODT, RTF, XLSX, XLS, ODS, CSV, PPTX, PPT, ODP, ODG, Markdown, plain text, JSON, XML, EPUB, MOBI, FB2, CBZ/CBR, XPS, EML, MSG, Pages, WPD, WPS, PUB, VSD/VSDX.Convert from PDF: JPG, PNG, WebP, BMP, TIFF, SVG, CBZ, Word (DOCX), Markdown, plain text, JSON, CSV, Excel (XLSX), greyscale PDF. Plus: Extract Images, Extract Tables, OCR (searchable PDF), and AI-ready JSON (LlamaIndex format).
By default, OCR uses Tesseract assets loaded from an online CDN, so an internet connection is required for the first use. For air-gapped or fully offline deployments, you can self-host the Tesseract worker, core, language data, and fonts by setting the VITE_TESSERACT_* environment variables at build time. See Air-Gapped Deployment for details.
The PDF Workflow Builder is a visual node editor that lets you automate multi-step PDF processing pipelines. You can chain tools together — for example, merge several PDFs, compress the result, and add a watermark — and run the entire workflow in one click.
The digital signature tool supports X.509 certificates in PFX and PEM formats. Your private key never leaves the browser. Some certificates require fetching issuer data from external certificate authority URLs, which may need a CORS proxy if those servers do not include CORS headers. Self-signed certificates typically work without a proxy.

​
Self-hosting

Yes. BentoPDF is a static site — you can host it with Docker, Nginx, Apache, or any static hosting platform (Netlify, Vercel, Cloudflare Pages, GitHub Pages, etc.). See the Self-Hosting overview to get started.
No. BentoPDF is entirely client-side. There is no backend, no API server, and no database. You only need a web server that can serve static files.
Yes. Use the included prepare-airgap.sh script to download all WASM packages and build a self-contained bundle. The script produces a Docker image and all required WASM assets, which you can transfer into the isolated network via USB or an internal artifact repository. See Air-Gapped Deployment for the full walkthrough.
Office file conversion (Word, Excel, PowerPoint) uses LibreOffice compiled to WebAssembly, which requires SharedArrayBuffer. SharedArrayBuffer is only available in cross-origin isolated contexts. http://localhost satisfies this requirement, but LAN IPs (e.g., http://192.168.x.x) do not — even if the server sends the correct COOP/COEP headers. Serving BentoPDF over HTTPS resolves this.

​
Licensing

Yes. BentoPDF is licensed under AGPL-3.0 and the full source code is available on GitHub.
You need a commercial license if you are building a proprietary or closed-source application, or a SaaS product where you do not disclose the full source code to users. AGPL-3.0 is free to use for open-source projects with publicly available source code, and for internal company tools that are not distributed externally.
The commercial license is a one-time payment of $49. It covers unlimited devices and users, includes all future updates, and has no recurring fees. Purchase here.

​
Customization

Yes. You can replace the BentoPDF logo, name, and footer text at build time using environment variables:
  • VITE_BRAND_NAME — brand name shown in the header and footer
  • VITE_BRAND_LOGO — path to your logo file relative to public/
  • VITE_FOOTER_TEXT — custom footer or copyright text
These variables work across all deployment methods: Docker, static hosting, and air-gapped builds. See Custom Branding for examples.
Simple Mode hides all marketing and branding elements — the navigation, hero section, features list, testimonials, FAQ section, and footer — and displays only the PDF tools. It is designed for internal company deployments and educational institutions where a distraction-free interface is preferred. Enable it by setting SIMPLE_MODE=true at build time. See Simple Mode for details.

Build docs developers (and LLMs) love

Get started for freeTalk to us