Type “merge pdf” into a search engine and Smallpdf is probably the first answer — a polished, genuinely well-made suite. But its model has a fixed cost you pay on every task: your file travels to their servers, and the free tier is a funnel toward a subscription. Document Flare’s merge tool does the same operation in your browser — same result, no trip, no counter. This is an honest comparison, including the places where Smallpdf stays ahead.
What using Smallpdf actually involves
Every cloud PDF suite runs the same loop: upload, server-side processing, download. Smallpdf’s own support pages describe the free tier as limited daily conversions — historically two per day — with limited downloads, while OCR, batch processing, strong compression, e-signatures and the desktop app sit behind the paid Pro subscription. Files are TLS-encrypted in transit and the company states they are deleted after a delay.
None of that is a scandal — it is an architecture. Your document is processed on infrastructure you cannot observe, under a retention policy you cannot verify, metered because every uploaded megabyte costs someone bandwidth and CPU. For an inconsequential file, that trade is fine. The question is what happens when the file is a contract, a payslip or a client’s books.
The local alternative: same core, different architecture
Document Flare runs the entire operation — parsing, transforming, writing the output — in your browser’s memory, inside Web Workers. The document is never sent, so there is nothing to meter, retain or promise to delete.
| Smallpdf Free | Document Flare | |
|---|---|---|
| Where the file goes | Uploaded to their servers | Never leaves the device |
| Usage limits | Daily conversion and download caps | None — device memory only |
| Account | Required past the free tier | Does not exist |
| Per-file limits | Plan-dependent | 50 MiB, 1,000 pages |
| Batch processing | Pro feature | Free: 20 files / 200 MiB per batch |
| Offline work | Desktop app is a Pro feature | Whole app cached after first visit (PWA) |
| e-signature workflow | Yes (Sign.com) | Visual signature only |
| PDF → Word / Office | Yes | Not in the public build |
| Cloud sync | Google Drive, Dropbox integrations | None — nothing to sync to |
The structural difference matters more than any single row: Smallpdf’s limits are commercial decisions that can change; local limits are physics — your device’s memory — stated in the code.
What the coverage actually looks like
The everyday toolbox is fully covered, locally:
- Organize: merge (2–20 files, 50 MiB), split by interval, bookmarks, size or detected text, extract up to 1,000 selected pages, rotate, reorder, delete.
- Optimize: compress with three quality presets (150, 120, 96 dpi rasterization) — the default smart strategy keeps text pages vector and only rasterizes image-dominated pages.
- Secure: password protection that forces AES-256 (PDF 1.7 Extension Level 3, revision 5) regardless of the source file’s age; metadata and script cleanup; and redaction that rasterizes censored pages — with assisted detection of nine personal-data types (IBAN, French social security numbers, bank cards, SIREN/SIRET, e-mails, phone numbers, birthdates, IPv4 addresses).
- Edit: the PDF editor adds annotations, text, visual signatures, watermarks and Bates numbering — with one caveat detailed below.
- Beyond the basics: local OCR (Tesseract, five languages, 100 pages), bank statements to Excel or CSV, page-by-page PDF comparison, and browser-built-in AI summaries and translation on Chrome or Edge 138+ — all running on-device.
- Batch: one operation applied to up to 20 files or 200 MiB — the batch mode article lists the seven eligible operations.
What Document Flare does not do — honestly
A comparison that only lists wins is marketing. Here is where Smallpdf genuinely stays ahead:
- Rich Office conversions. Faithful PDF → Word, Excel → PDF, and similar heavy conversions are exactly what our catalog declares
REMOTE_OPTIONAL— they exist only as simulations, are excluded from the public build, and would require explicit per-task consent if ever enabled. If your daily work is turning PDFs back into editable Word files, Smallpdf does that and we don’t. - E-signature workflows. We offer visual signatures — an image, drawing or typed name placed on the document — not a signing ceremony with audit trails, recipient management or eIDAS-qualified signatures. For that, Smallpdf’s Sign.com integration is a real product.
- Cloud sync and mobile apps. Smallpdf integrates with Google Drive and Dropbox and ships mobile apps. Document Flare has no account to sync to; instead it installs as a PWA — including Android share-target integration so PDFs can be sent straight to it — and works offline after a first online visit.
- Editing existing embedded text. Our editor adds and annotates; it does not rewrite text already in the file. Smallpdf’s Edit (a Pro feature) does.
Verify rather than trust
“Your files stay private” is a claim any website can print — including this one. The difference is that ours is testable in five minutes: open the developer tools, switch to the Network tab, drop a PDF into any of our tools and run the operation. An upload shows up as a large POST or PUT request; on Document Flare, no request carries the document. The full protocol — and the same test run on other tools — is in our study where do your files go, and the architecture is detailed in PDF tools without upload.
Which one for which job
Stay with Smallpdf if you need faithful Office conversions, a real e-signature pipeline, or Google Drive integration — and the files you process are inconsequential. A paid Pro plan is a fair price for those features.
Choose the local route when the document is sensitive (contracts, HR files, client records — see the GDPR angle), when you process PDFs regularly and the daily quota bites, or when you simply prefer a guarantee you can observe over a policy you have to trust. No account, no quota, no upload — and the Network tab to prove it.
