Documents and notes decision
Smallpdf Pro
A competent developer can build a useful subset of Smallpdf (convert/compress/merge/edit/OCR) using open-source components; enterprise features, certifications, and large-scale polish explain why some customers will still pay Smallpdf.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Upload a PDF, apply a transformation (compress / convert / merge / edit text), return the modified PDF for download.
What it still won’t have
- Enterprise-grade compliance certification (unless you pursue certification separately)
- Scale and global CDN/edge optimizations for large user volumes
- Native mobile apps and tight Sign.com integration
- Polished UI/UX and battle-tested reliability under heavy load
- Proprietary AI tuning and commercial SLAs
What remains hard
- Compliance and regulation
Smallpdf is ISO/IEC 27001 certified, GDPR, CCPA, and nFADP compliant.
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted Smallpdf-like web service using Node.js + Express, React for the frontend, PostgreSQL for user/subscription records, and object storage (S3-compatible). Implement: (1) file upload with size/type validation and virus scanning stub, (2) server worker endpoints that perform compress (qpdf/Ghostscript), merge/split, convert-to-PDF and PDF-to-image (pdf-lib + ImageMagick), (3) text edit API using pdf-lib, (4) optional OCR via Tesseract CLI, (5) a React UI to choose operations and download results, (6) simple JWT auth and one-seat subscription enforcement, rate limits, and daily usage counters, (7) error handling for corrupted PDFs, timeouts, and concurrency limits, plus automated tests for upload, process, and download flows and basic CI. Out of scope: mobile apps, ISO certification, Sign.com integration, and large-scale CDN/edge optimization.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Hard moats found in the evidence-3
- Evidence score57
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productSmallpdf - A Free Solution to all your PDF Problems
- official pricingSmallpdf Pricing and Plans
- open sourcealam00000/bentopdf
- open sourcePDFCraftTool/pdfcraft
Integrity checks
What held up, and what did not.
