Last month I needed to compress a PDF. I Googled "compress PDF free", clicked the first result, and processed my file. Then I read their privacy policy.
It said: "We may retain uploaded files for up to 24 hours."
That file was my tax return. My SSN was sitting on a stranger's server.
The Dirty Secret
Nearly every free online PDF tool works the same way:
- You upload your file to their server
- They process it server-side
- You download the result
- Your file may stay on their server for 1-24 hours
For casual use this is fine. But people upload everything: tax returns, contracts, medical records, bank statements.
Why Browser-Based Processing?
Modern browsers can run WebAssembly at near-native speed. PDF libraries like pdf-lib work entirely in the browser. So why do all popular tools still send files to servers?
Because it's easier to build that way. But here's the thing: it's not that hard. I built it in a few weeks.
What I Built
PDF Toolbox — 8 tools, all browser-based:
- Compress PDF (3 quality levels)
- Merge PDF (drag and drop reorder)
- Split PDF (extract specific pages)
- PDF to Word (text extraction)
- PDF to JPG (per-page image export)
- JPG to PDF (batch image conversion)
- Unlock PDF (remove password)
- Protect PDF (add password)
Zero server uploads. No registration. No limits.
The Architecture
Browser
|-- Next.js UI
|-- pdf-lib (merge, split, unlock, protect)
|-- Canvas API (PDF-JPG rendering)
|-- Web Workers (heavy processing)
Server (Vercel)
|-- Static HTML/JS/CSS
|-- Zero file processing
The server never touches your files. It just delivers the JavaScript.
Open Source
Entire codebase on GitHub. MIT licensed. Deploy your own instance if you want.
The Bottom Line
Your PDFs contain sensitive information. There's no reason they should touch a third-party server. Browser-based PDF tools prove you can have fast, free, unlimited PDF processing without sacrificing privacy.
Try it: pdftoolbox.tech
Built with Next.js, TypeScript, pdf-lib, and Tailwind CSS. Deployed on Vercel.
Top comments (0)