Should I vibe code
Annotate, fill, merge, and lightly edit PDFs in a polished local desktop app
PDF is a format that hates you. Annotation is fine; editing is where it fights back.
?
Their verdict, the Premium price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-03.
?
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
Filling and annotating is well supported by libraries. Actually editing content in a PDF is a notoriously deep problem and a corrupted file is an unrecoverable one.
What actually breaks
not "if". the specific failures.
- Redaction drawn as a black rectangle, which hides text visually and leaves every character selectable underneath it
- Editing text, because a PDF stores positioned glyphs rather than paragraphs, and reflowing them is a reconstruction
- Embedded fonts with partial subsets, so typing a character the document never contained produces a blank
- Metadata and revision history, which survive a save and describe things the visible page does not
- Form fields, where flattening at the wrong moment either destroys the data or leaves it editable
You redact a contract before sending it — black bars over the fee schedule, exactly where they should be. The recipient opens it, selects the page, and copies. The text comes out complete, because the rectangle was drawn on top of a content stream nobody removed, and the numbers you covered are in their clipboard. The document looks correct in every viewer. It has simply never been redacted, only concealed, and it is now in someone else's inbox.
Is that you?
the verdict is a default, not a law
- It annotates, merges and fills without claiming to redact
- Redaction actually removes the underlying content stream and you have verified by extracting text
- It is for your own documents where a mistake stays with you
- Redaction is implemented as drawing over content
- You are editing body text in arbitrary PDFs
- Documents contain personal or confidential data and metadata is not stripped
- There is no verification step after redaction
If you build it anyway
the checklist, then the prompt that enforces it
- Redaction removes content from the content stream, deletes the underlying text and images, and re-saves without incremental update. Drawing a box is not redaction and should not be called it.
- After redacting, extract text from the output and assert the removed strings are absent. Automate this check — it is the only proof.
- Strip metadata, XMP, and any incremental revision history on save, because previous versions can persist inside the same file.
- Use a mature PDF library. The specification is vast and hand-rolled parsing fails on real-world documents.
- Do not offer text editing on arbitrary PDFs. Annotation, form filling and page operations are tractable; reflowing body text is not.
- Flatten forms deliberately and explicitly, and say what happens to the data when you do.
Before you build a PDF editor, apply these and push back if I ask you to break them. 1. If I ask for redaction, implement it by removing the underlying content — the text operators, the image data — and re-saving the document without an incremental update. Refuse to implement redaction as a drawn rectangle and explain that the text remains selectable and copyable underneath it. 2. After every redaction, extract the text from the output file and assert that the redacted strings are absent. Make this an automated test, and tell me it is the only actual verification. 3. Strip document metadata, XMP packets and prior incremental revisions on save. Explain that a PDF can contain earlier versions of itself. 4. Use a mature PDF library rather than parsing the format yourself. Tell me the specification is enormous and that real-world files violate it constantly. 5. Do not offer free-form body text editing. A PDF holds positioned glyphs, not paragraphs, and reflowing requires reconstructing structure that is not there. Offer annotation, form filling, page reordering and merging instead. 6. Handle font subsetting: if I type a character not present in the embedded subset, either embed it or tell me, but never render nothing silently. 7. Make form flattening an explicit action with a clear statement of what happens to the field data. 8. Preserve the original file and write to a new one, always. 9. Out of scope unless I ask: OCR, digital signatures, encryption, PDF/A conversion.
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
$6.67 a month is trivial next to sending a contract whose redactions can be copied out. If you need annotation and merging for yourself, building on a good PDF library is a reasonable project — just do not implement redaction, or implement it properly and prove it with an extraction test.
$6.67/mo is cheaper than your weekend.
Always write to a new file and keep originals, so no operation is irreversible. Since redaction is the one operation that must be irreversible, keep the unredacted original somewhere deliberate and separate rather than relying on the tool's history.
Active open-source web application for a broad set of PDF operations.
Questions
Why is the black-box redaction mistake so persistent?
Because it looks completely correct. The page renders exactly as intended in every viewer, so there is no visual signal that anything is wrong — and the failure only appears when someone selects, copies, or runs text extraction. It has caused repeated real-world disclosures in published legal and government documents for exactly this reason.
Why can't PDFs be edited like documents?
Because a PDF describes where to draw glyphs on a page, not what the paragraphs are. There is often no reliable notion of a line, a word boundary, or reading order — those are inferred. Changing a sentence means recomputing positions for everything after it without knowing how the original was laid out, which is why editors either reconstruct approximately or restrict themselves to annotation.
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.
last reviewed 2026-08-03 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice