Should I vibe code
Merge, split, compress, convert, and annotate PDFs without uploading them to a vendor
Merge and compress are library calls. "Sign" is a legal instrument, and yours is a picture of a squiggle.
?
Their verdict, the Premium price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-04.
?
Our verdict, the regret score and everything below it. Editorial and unsponsored — nobody can pay to be moved.
The honest answer
why the verdict is what it is
Half of this is a solved problem and we already say build it — merge, split, compress and convert are mature libraries, and running them locally is better than uploading contracts to a stranger. The half that makes Premium worth paying for is signing, and a self-built signature is an image drawn onto a page: it looks finished, it demos beautifully, and it has none of the properties that make a signature mean anything when someone says they never agreed.
What actually breaks
not "if". the specific failures.
- The word signed, which in your version means an image was drawn on a page and nothing about the file resists being edited afterwards
- The audit trail, which is the actual evidence in a dispute and which nobody builds on the first pass
- Identity, because knowing that the person who clicked was the person named on the contract is the entire problem and a checkbox does not solve it
- Two copies of a signed document, held by two parties, differing — with no way to prove which one is authoritative
- OCR output that is confidently wrong, quietly turning a scanned invoice into a different number
- Malformed PDFs, which are common, and which hang or crash a parser that assumes the specification was followed
Is that you?
the verdict is a default, not a law
- It merges, splits, compresses and converts, and never claims to sign anything
- It runs locally and deletes every file after processing
- Any signature it applies is one you would happily describe out loud as pasting a picture of your name
- OCR output is always read by a human before it becomes a number anywhere
- Anyone will rely on the signature in a dispute
- You are collecting signatures from counterparties rather than applying your own
- The signed file can be edited afterwards without that being detectable
- OCR feeds an amount into accounting unattended
- Documents from other people persist on disk after the response is returned
If you build it anyway
the checklist, then the prompt that enforces it
- Build the transformations, skip the signatures. Merge, split, compress and convert are mature library calls; signing is a different product with a legal standard attached, and the gap between them is not visible in a demo.
- If you sign anyway, sign cryptographically — a PAdES-style digital signature with a real certificate — so that any later edit is detectable. An appearance stamp with no signature dictionary is decoration.
- Record an audit trail from the first version: who, when, from what address, what exact bytes they saw, and what they clicked. The document is the artefact; the trail is the evidence.
- Hash every signed output and store the hash separately, so two disagreeing copies can be resolved.
- Run all parsing in a subprocess with hard memory and wall-clock limits. Malformed and enormous PDFs are the normal case, not the edge case.
- Delete inputs and outputs immediately after the response and sweep for what the happy path missed. Not doing this recreates the exact problem self-hosting was meant to solve.
- Treat OCR output as a suggestion needing confirmation, never as data. A transposed digit in a scanned invoice is silent and expensive.
- If someone asks for redaction, tell them it is a different operation that must remove the underlying content — a black rectangle leaves the text selectable underneath.
Before you build a PDF toolkit that includes signing, apply these and push back if I ask you to break them.
1. Build in this order and tell me why: transformations first (merge, split,
compress, convert), then metadata, then — only if I insist — signatures. Do
not start with the signature feature because it demos well.
2. When I ask for signing, stop and explain the difference between drawing an
image of a name onto a page and applying a cryptographic signature that
makes later modification detectable. Only the second is worth anything if
the other party denies signing.
3. If I still want it, use an established library to produce a real PAdES-style
digital signature with a certificate. Refuse to implement the signature
dictionary or the cryptography yourself.
4. Build the audit trail before the signing UI: signer identifier, timestamp,
source address, SHA-256 of the exact document presented and of the result.
Store it separately from the PDF.
5. Tell me plainly that you cannot verify identity from a browser session — what
I am building records 'someone with this link clicked', not 'this named
person agreed'.
6. Never modify a signed file. Any further operation produces a new document
with its own trail.
7. Run all parsing in a subprocess with hard memory and wall-clock limits, and
validate uploads as PDFs by content rather than extension.
8. Delete every input and output immediately after the response, plus a
scheduled sweep — leftover files reproduce the problem I self-hosted to
avoid.
9. Treat OCR as a draft needing human confirmation. Never let it flow into an
amount, a date or an identifier unattended.
10. If I ask for redaction, tell me it must remove the underlying content
rather than draw over it, and that it is a separate operation.
11. Out of scope unless I ask: multi-party signing workflows, reminders,
certificate management, long-term validation.That one keeps you out of trouble. For the prompt that actually builds it, canivibecodeit.com has one.
their build prompt ↗Or don’t build it
the boring option, and the way back out
The moment a counterparty signs something. $7 a month buys a signature flow whose evidential properties somebody has already had to defend, and that is precisely the part you cannot tell is missing by looking at the output. For merging and compressing your own files, keep your money and use a library.
For the transformation half there is nothing to keep — files go in, files come out, and both should be gone shortly afterwards. For anything signed, the export is the audit trail: signer, timestamp, and hashes of the document before and after, in a plain table. A signed PDF with no record of how it came to be signed is a file, not evidence.
Active open-source web application covering a broad set of PDF operations, self-hosted.
Questions
You rate Smallpdf as SHIP IT and this as DEMO ONLY. They are nearly the same product.
They are, minus one feature, and that feature is the entire difference. The Smallpdf entry deliberately scopes to transformation utilities and rates those exactly as we rate them here: build them. This entry covers what Premium adds on top — signing and document workflows — because nothing else in the set does, and a self-built signature is where an easy build acquires a consequence.
What actually makes an electronic signature hold up?
Not the picture. It is the combination of evidence that a specific person was presented with specific bytes and agreed to them: an identity check of some strength, a tamper-evident seal over the document, an accurate timestamp, and a retained audit trail. eIDAS in the EU and the ESIGN Act in the US both accept a wide range of electronic signatures, which is exactly why the argument in a dispute is about evidence rather than format — and the evidence is the part a weekend build never has.
Can I at least sign my own documents with it?
Yes, and that is close to the SHIP IT case. Applying your own mark to your own outgoing document is a defensible use, because you are the person who would be disputing it. The line is collecting signatures from other people, where you are asserting something about someone else's intent and holding nothing that proves it.
- Regulation (EU) No 910/2014 (eIDAS) — electronic identification and trust services
- US ESIGN Act — 15 U.S.C. ch. 96, electronic signatures in global and national commerce
Every week, someone ships something they shouldn’t have.
New verdicts, the worst thing that landed in the trap, and the occasional incident report. No other email, ever.
PDF is a format that hates you. Annotation is fine; editing is where it fights back.
The best reason to self-host PDF tools: your documents stop being uploaded to strangers.
An e-signature is not a picture of a squiggle. It's the audit trail you'll be asked for two years later.
last reviewed 2026-08-04 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice