BrowserPDF.app's answer:

There is no upload endpoint at all. Every tool (merge, split, compress, OCR, PDF to Word, fill and sign, and ten more) runs inside the browser tab using pdf.js, Tesseract.js, and pdf-lib, so files physically cannot reach a server. The open-source libraries doing the work are pinned to exact versions and verified with a SHA-384 hash before they execute, and a strict Content-Security-Policy backs that up. Free means free: no ads, no account, no watermarks, no usage limits.

BrowserPDF.app's answer:

Most free PDF sites upload your document to their servers, put you in a queue, watermark the output, and push you toward a subscription. BrowserPDF cannot do any of that by architecture: processing is local, so there is nothing to queue, nothing to store, and nothing to charge for later. You get 15 tools with honest limitations stated up front, and you can verify the no-upload claim yourself by watching the network tab while you work.

BrowserPDF.app's answer:

Privacy-conscious people working with sensitive documents: contracts, IDs, medical and financial paperwork, client files. That includes lawyers, accountants, journalists, HR and security professionals, plus anyone who simply finds upload-and-wait PDF sites slow and pushy. No technical knowledge is needed to use it.

BrowserPDF.app's answer:

It started when the founder, a security professional, needed to OCR and compress scanned personal documents and realized every "free" tool wanted those files on its servers first. The first version was a single client-side PDF to Markdown converter; it grew into a 15-tool suite built on one rule: if a feature would require uploading the file, it doesn't get built.

BrowserPDF.app's answer:

Plain JavaScript with no framework, pdf.js for parsing and rendering, Tesseract.js (WebAssembly) for on-device OCR in 14 languages, and pdf-lib for writing PDFs. The .docx exporter and ZIP writer are dependency-free and written from scratch. Libraries load from a CDN at pinned versions and are SHA-384-verified before executing. Hosting is Cloudflare static assets with a tiny worker for redirects and security headers; there is no backend.