We built the PDF site we wanted to use
Every other online PDF tool asks you to upload a document you may not be allowed to upload. ZappoPDF does the same work without ever asking for that.
The problem with “drop your file here”
Online PDF tools are genuinely useful. They are also, almost without exception, built the same way: your file is uploaded to a server you know nothing about, processed there, and held for some number of hours before deletion. That is fine for a restaurant menu. It is a different conversation for a signed contract, a payslip, a medical letter, or a client deliverable covered by an NDA.
Most people resolve that tension by not thinking about it too hard. We would rather remove the tension entirely. Modern browsers can do real document processing on their own — so ZappoPDF does the whole job locally and never asks you to hand anything over.
The short version: ZappoPDF has no upload endpoint. There is no server that could receive your document, which means there is nothing to breach, subpoena, retain past a deletion window, or quietly train a model on.
How it actually works
When you drop a file onto a ZappoPDF tool, the browser reads it into memory using the standard File API — the same mechanism that lets you preview a photo before posting it. From there, two well-known open-source libraries do the heavy lifting: pdf-lib writes and edits PDF structure, and PDF.js — the engine inside Firefox’s built-in PDF viewer — renders pages when a tool needs pixels rather than objects. Your finished document is assembled in the tab and handed back as a normal download.
The site itself is static: a handful of HTML, CSS and JavaScript files. There is no database, no user account system, no session, and no request that carries your document anywhere.
Office files, without the upload
Word and Excel conversion is the one thing everybody assumes needs a server, and it is where most “private” PDF tools quietly give up. We took a different route: instead of photographing a rendered page, ZappoPDF reads the content and re-flows it.
A .docx is a zipped bundle of XML, so we parse it directly and lay the content back out onto PDF pages — headings, bold and italic, bullet and numbered lists, tables and embedded pictures all carry across, as real text that stays selectable and searchable. Spreadsheets get columns sized to their content and header rows that repeat on every page. Going the other way, we read where every fragment of text sits on the PDF page, rebuild paragraphs from wrapped lines, promote larger lines to genuine Word headings, and cluster text positions into columns to recover tables into a real .xlsx.
The honest trade-off: this is content-faithful, not pixel-faithful. Your words, structure, tables and images come across reliably. Exact page breaks, multi-column magazine layouts and heavily designed templates will shift. For the everyday job — a report, a CV, a statement, a data export — that is exactly what you want. If you need a byte-perfect clone of the original design, keep the original.
What we deliberately left out
We would rather have an honest gap than a broken promise. A few things that competitors offer are not here, and will not be until they can be done locally:
| Not offered | Why not |
|---|---|
| PowerPoint ↔ PDF | Slides are absolutely positioned shape canvases rather than flowing text, so a re-flow approach produces something worse than useless. It needs a real rendering engine. |
| OCR for scanned documents | In-browser OCR is possible but currently slow and inaccurate enough that we would be shipping a disappointment. It is the feature most likely to arrive next. |
| Password-protect / unlock | Reliable PDF encryption is not yet available in the browser libraries we trust. We would rather ship nothing than ship weak encryption. |
| Accounts, cloud storage, sync | Storing your documents is exactly the thing we are avoiding. |
For maximum compression on scanned documents, and for password protection, a desktop tool such as Ghostscript or qpdf will serve you better — and it also keeps everything on your machine.
What you get instead
No limits
No two-tasks-per-hour cap, no file size ceiling beyond your own device’s memory, and no queue at busy times.
No account
Nothing to sign up for and no email address to hand over. Open a tool and start working.
No watermark
Your output is your output. We do not stamp it, downgrade it or hold quality back for a paid tier.
No tracking
No analytics scripts, no advertising pixels, no cookies. The only thing stored locally is whether you prefer dark mode.
How this is paid for
It is barely paid for at all, and that is the point. A static site with no processing backend costs almost nothing to run, which is what lets us keep every tool free without an upsell. If that ever changes, it will change through something optional and clearly labelled — never by starting to collect your files.
Who is behind it
ZappoPDF is a small independent project, not a venture-funded document platform. Bug reports, tool requests and blunt feedback are all genuinely welcome — there is a real person on the other end of the contact page.
Try it on something that matters
Open your network inspector first if you like. Watching a merge finish with zero requests is the fastest way to believe us.
Browse all tools