Security

Every file you open in bopdf is processed entirely in your web browser, on your own device. We never upload your documents to our server, we never store them, and we cannot see them. When you close the tab, they disappear from memory. You do not need an account, and you do not need to trust us with the contents of your PDF — the work happens on your computer.

How to verify this yourself

You do not have to take our word for it. Anyone can check, in about two minutes, that files are not being sent to us.

1. Offline test

Open any tool page on bopdf.com and wait for it to finish loading. Then turn off Wi‑Fi or unplug the network, choose a file and run the tool. It still works, because processing happens on your device. After the page has loaded, the tools do not need an internet connection — with one exception for OCR, described below.

2. Browser developer tools

Press F12 (on a Mac you can also use Option + Command + I, or right-click the page and choose Inspect). Open the Network tab, then process a file. You will not see a request that sends your document to a server. If you understand how browsers work, this is the most direct proof: the file never leaves your computer.

Exceptions we want you to know about

A few optional features do use the network. We would rather describe them clearly than make absolute claims.

Optional cloud-save buttons (Google Drive, Dropbox and OneDrive): these upload a file only if you click them. They are currently hidden, because the apps are not configured yet. When they appear, nothing is sent until you choose to save.
Feedback form: if you send us a message, we receive only the text you type, the page you sent it from, and an email address only if you provide one. Your documents are never attached or uploaded.
Cloudflare Web Analytics: a cookieless script that records page views only (which pages are opened, not what is in your files). It never reads the documents you process.
OCR tool: the first time you use OCR PDF, the open-source Tesseract engine and language data (about 2–15 MB) are downloaded from the public jsDelivr CDN. jsDelivr sees a request from your browser (IP address and user agent). Your document is still processed locally and is not sent to jsDelivr or to us. Other tools do not need this download.

Built on trusted open-source libraries

bopdf uses well-known open-source libraries to process files in your browser:

pdf-lib (MIT License) — creates and edits PDFs.
Mozilla pdf.js (Apache License 2.0) — the same rendering engine built into Firefox, used to display PDF pages.
qpdf-wasm (ISC License; wraps the qpdf engine, Apache License 2.0) — encrypts, decrypts and repairs PDFs.
SheetJS (xlsx) (Apache License 2.0) — Excel conversion.
mammoth (BSD-2-Clause License) — reads Word documents.
html2canvas (MIT License) — turns a web page into an image for HTML-to-PDF.
heic2any (MIT License) — converts iPhone HEIC photos.
Tesseract.js (Apache License 2.0) — optical character recognition, loaded from jsDelivr the first time you use the OCR tool, as described above.

All of this file-processing code is served from our own domain (bopdf.com), except Tesseract.js, which is loaded from jsDelivr only when you use OCR. The only third-party script loaded on every page is Cloudflare Web Analytics, which records page views only and never reads your files.

We simply never receive your file, so we have nothing to scan or store. For a full description of the data we do handle (for example feedback messages), see our privacy policy.