Hey — welcome to the PDFops squad 👋
We generate PDFs in serverless and edge runtimes without headless Chrome, a Lambda layer, or native binaries. Two primitives, both over a single HTTP call:
fill-form — flatten AcroForm fields from JSON, byte-identical on every run.
merge — concatenate PDFs deterministically.
What we care about most is determinism: the same input produces the same bytes, so you can hash, cache, and diff generated PDFs in CI instead of eyeballing them. That’s surprisingly hard with browser-based tooling, where a font or timestamp drift silently changes the output.
This squad is for anyone wrangling PDFs in Workers, Vercel, Deno, or Bun — share what you’re building, the gnarly PDF bugs you’ve hit, and tools worth knowing. We’ll post guides and teardowns here too.
Want to poke at it? pdfops.dev/tools/inspect lets you drop a PDF and see its form fields.
What are you generating PDFs for? Drop it below.

The deterministic PDF fill & merge primitive for edge & AI apps. Guides, tools, and discussion on generating PDFs in serverless/edge runtimes — no headless Chrome, no Lambda.

PDFops

PDFops is a service for generating PDFs in serverless and edge runtimes (Cloudflare Workers, Vercel, Deno, Bun) without headless Chrome or native binaries. It offers two HTTP-based primitives: fill-form (flatten AcroForm fields from JSON deterministically) and merge (concatenate PDFs). The key value proposition is determinism — identical inputs produce identical bytes, enabling hashing, caching, and diffing of PDFs in CI pipelines. A free inspection tool is available at pdfops.dev/tools/inspect.

Why we built PDFops: deterministic PDF fill & merge for the edge