SMF·SMALLPDF
Can a prompt replace Smallpdf Pro?
PDF & documents — PDF toolbox with bundled e-signature
Exhibit tracking slip
Verdict
The toolbox half is the same as iLovePDF and Sejda, and self-hosting covers it completely. What makes this one a kinda rather than a yes is the second half: Pro bundles unlimited Sign.com Premium, which is a real e-signature product with an evidence trail, and that is the part a personal build does not reproduce. The other thing worth stealing is the chaining — compress then OCR then split, as one saved recipe.
Exhibit A — The prompt
Received on31.07.2026Build a recipe layer over a self-hosted PDF toolbox.
Deploy Stirling PDF behind Caddy with authentication. Then build the piece it does not have: named recipes that chain operations.
A recipe is a small YAML file — an ordered list of operations with their parameters. The archive recipe might be: OCR, then compress to a named quality, then rename from a pattern using the document date. The share recipe might be: strip metadata, flatten form fields, watermark. Chaining is the whole point, because doing three operations by hand through three separate pages is the friction the paid tools remove.
Run recipes through a real job queue rather than a request handler. Chained OCR and compression on a large scan takes minutes, and a request that times out halfway leaves an intermediate file and no result. The queue should be able to resume, and every job should show which step it is on.
Make failure legible per step: if OCR succeeds and compression corrupts the output, the job report should say exactly that and keep the pre-compression file. Fail forward with the last good artefact rather than discarding the work.
Strip metadata by default on any recipe that produces a file for someone else, and say so — author names, editing software and file paths leak out of PDFs constantly and nobody expects it.
Out of scope: e-signature of any kind, mobile apps, cloud storage connectors. If you need signatures, that is a separate build with a separate honest answer about what it is worth.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the bundled Sign.com Premium subscription and its signature evidence
- B.2 the mobile apps and their document camera
- B.3 Google Drive and Dropbox connectors
- B.4 conversion fidelity on complex Office layouts
- B.5 use from a machine with nothing installed
Prior art
- Stirling PDFLicense: MIT
- DocumensoLicense: AGPL-3.0
Exhibit C — Why people still pay: bundled e-signature and chained operations
Because two subscriptions arrive as one. Someone who needs both PDF tools and signatures is comparing this against buying a signature product on its own, and at that comparison the toolbox is effectively free.
Questions
Can I import files from my Smallpdf account?
Documents download normally. Nothing else carries: Smallpdf stores your tool history and any Sign.com envelopes on its side, and there is no export that another tool reads.
What about the signature half?
It is not in this build, deliberately. Smallpdf Pro bundles Sign.com Premium, and reproducing it means an evidence trail, delivery from a domain that is not blocked, and a counterparty who accepts the result — a much bigger project than the toolbox.
What does it cost to run?
A VPS with room for LibreOffice and a queue worker, roughly $10 a month, plus a domain. All the software is free.
What is the one thing that does not survive the rebuild?
The second subscription. If you are paying Smallpdf mostly for the unlimited signing, self-hosting the toolbox saves you very little and costs you the thing you were actually buying.
Related tools
Receipt