Make the pages workable
Crop, rotate, deskew, remove blank pages, resize, compress, repair, merge, split, reorder, and convert to PDF/A.
Aspirational roadmap
What if a PDF workflow could keep going?
A recurring document job is rarely one operation. The long-term idea is a toolbox of small, composable steps: arrange them in any order, let one result branch into many, add conditions, and save the whole thing to run again.
This page describes possibilities, not live features. Today Papmil runs one ready-made four-step workflow.
Tell us your oddly specific workflownot a product screenshot
when
A PDF arrives
upload · folder · email · schedule
01Crop + deskew
02Understand
if / then
What kind of document is it?
invoice → extract + route
letter → summarize + rename
other → human review
small tools, rearranged into one repeatable ritual
Potential building blocks
A useful toolbox, not a magic button.
Each future tool should do one understandable job. The interesting part is what happens when those jobs can be chained, branched, reused, and inspected.
Make the content legible
OCR, detect language, improve contrast, clean scan noise, remove punch-hole shadows, and cautiously recognize handwriting.
Ask useful questions
Classify, summarize, translate, extract tables or fields, find deadlines, compare versions, and identify missing pages.
Produce the right copy
Watermark, redact, add page numbers, insert a cover, replace an obsolete page, stamp a status, or generate a contents page.
Branch when the document does
Route by type, sender, language, confidence, page count, extracted value, or whether a person needs to review it.
Run the ritual again
Start from an upload, watched folder, scanner, inbox, API, or schedule. Version the workflow and keep exceptions visible.
Possible workflows
Practical, ambitious, and occasionally peculiar.
The scanned-mail morning brief
Split the post, OCR it, identify deadlines and amounts, write a three-line summary, rename every PDF, and send urgent items to review.
split → OCR → extract → summarize → rename → routeThe always-current policy pack
Compare the new policy with last month's, highlight changes, replace obsolete pages, rebuild the contents, and produce a watermarked review copy.
compare → replace → rebuild → watermarkThe mystery-box archive
Separate letters, postcards, receipts, and photographs; group them by likely person and decade; transcribe what is readable; and create a browsable timeline beside the originals.
separate → cluster → transcribe → timelineThe tabletop handout factory
Split player-safe pages from game-master secrets, replace character names, watermark each copy, add a personal cover, and make one packet per player.
classify → personalize → watermark → branchThe appliance “future me” folder
Combine a receipt, manual, warranty, and serial-number photo; extract the deadline; keep the useful manual pages; and create one ownership pack.
merge → identify → extract → crop → remindThe grant-submission checker
Merge contributions, verify annexes, flag missing signatures, normalize page sizes, add dividers and page numbers, and make submission plus review copies.
merge → check → normalize → number → duplicateThe recipe inheritance project
Separate a family notebook into recipes, preserve each handwritten original, create a clean reading copy, extract ingredients, and assemble a printable book. Coffee stains stay in the archive version.
split → preserve → transcribe → group → publishStill only a vision
Have a recurring PDF job that sounds oddly specific? Good.
The most useful future tools will come from real workflows rather than a generic feature checklist. Tell us the job, the awkward parts, and what a genuinely useful result would look like. No promises or delivery dates, just a useful conversation.
Tell us your workflow Or run what is live today