From the team
Guides, tutorials, and updates on building document workflows with AI.
A one-line invoice change can break every render in production. Here is how to stage it with frozen versions and a staging channel, test it with real data, promote it, and roll it back in one step.
A free Odoo module for 17, 18 and 19 that renders any record through pdfs.build. Install it, map a template to a model, and replace the stock invoice PDF without touching QWeb.
Use the pdfs.build batch render API to generate up to 500 PDFs from one template in a single request, get one webhook when they are all done, and download every document.
A practical guide to generating dynamic PDFs from JSON data in Next.js 15. Avoid heavy Chromium serverless crashes by calling a Typst REST API instead, with a median render of about 220ms.
A complete architectural guide to building a white-label in-app document editor in your React SaaS. Learn how to mint tenant-scoped session tokens, embed @pdfsbuild/react, and render user-designed PDFs programmatically.
Your documents already exist as .docx files. How pdfs.build turns one into a Typst template in two deliberate steps: a faithful static conversion first, then chat-driven parameterization into a JSON-to-PDF endpoint.
An LLM edits Typst code, a JSON schema, and sample data together. Here is the repair loop that turns plausible model output into documents that always compile: deterministic triggers, bounded fixes, and a compiler with the last word.
pdfs.build compiles Typst in three places: a Rust publish gate, a Node server that renders the delivered PDFs, and WASM in the browser for live preview. A war story about what happens when they drift apart, and the rules that keep them aligned.
Most Typst vs LaTeX comparisons are about writing papers. This one is about the other job: programmatically generating invoices, reports, and certificates from data, where the trade-offs look very different.
Most PDF APIs are a headless Chrome with an endpoint in front of it. Here is why pdfs.build compiles documents with a typesetting engine instead, what that buys you when the data grows, and what you give up.
A developer guide to generating dynamic PDF documents from JSON data. Compare approaches (HTML-to-PDF, PDF libraries, template engines), see code examples, and learn how to set up a template-based PDF rendering pipeline.
An MCP server that exposes PDF template authoring and rendering as native tools, so Claude or any MCP-compatible agent can produce documents without integration code.
Learn how to render templates with your data payload and integrate PDF generation into any stack using the pdfs.build REST API.
From sign-up to your first generated PDF in under five minutes. Here's everything you need to know to hit the ground running.