PDF generation · Evaluate
Synchronous vs Asynchronous PDF Generation
Choose a rendering flow based on latency, workload size, retries, user experience, and result lifecycle.
For developer · 7 min · Reviewed Jul 31, 2026
Use synchronous generation for immediate output
Synchronous generation is simple: send data and receive a PDF in one request. It fits interactive downloads when expected rendering time is comfortably inside your request timeout.
Use asynchronous jobs for durable work
An asynchronous request returns a job identifier. Your application polls status and downloads the result after completion.
This isolates rendering from browser or gateway timeouts and provides an explicit state for retries and failures.
Use batch generation for many documents
Batch workflows validate multiple items, create independent jobs, and let the caller handle partial failures without rerunning completed documents.
Plan result storage
PDFDesignAPI job results expire after 24 hours. Download them promptly and apply your own access control and retention requirements.
Decision checklist
- Does the user need the file in the current interaction?
- Can the document exceed normal request timeouts?
- Must failed items retry independently?
- Will one action create many documents?
- Where will completed results be stored and authorized?