"Create a PDF" is a request that hides a dozen different intents. Sometimes it means "export this Word doc." Sometimes it means "build a printable form." Sometimes it means "generate a thousand invoices a day from a database." The right approach depends entirely on which one you mean — but a few patterns cover almost every case.
Decide what kind of PDF you actually need
Before reaching for a tool, answer two questions:
- One-off or repeating? A single proposal is different from monthly invoices.
- Designed visually or generated from data? A pitch deck and a 50-page financial report come from different tools.
A 2x2 of these gives you four common cases, and each has a sensible default tool.
Case 1: One-off, designed visually
You want a beautiful one-off document — a CV, a brochure, a proposal. Best tools:
- Word, Pages, or Google Docs for text-heavy documents. Export to PDF when done. See how to convert Word to PDF.
- Figma, Affinity Publisher, or Canva for visually rich ones. All export directly to PDF.
- Markdown + pandoc for technical content with some pride in typography.
For most of these, "create a PDF" really means "design in your normal tool, then export." The PDF is the final delivery format, not the editing format.
Case 2: Repeating, designed visually
You produce a similar document every week or month — a newsletter, a report, a one-pager. The trick here is to set up a template once and reuse it:
- Word styles + a saved template = consistent monthly reports.
- Figma master components + variants = consistent visual design across versions.
- InDesign with Data Merge = visual templates fed by a CSV.
Setting up the template costs a day. Saved time over a year is enormous.
Case 3: One-off, generated from data
A single data-driven PDF — a portfolio with charts, a tax return summary, a research paper. Best tools:
- Jupyter notebooks → PDF for analytical work.
- Quarto or R Markdown for reproducible research papers.
- LaTeX when typography matters (academic papers, books, anything mathematical).
These are heavier to set up than Word, but the result reproduces exactly when the data updates.
Case 4: Repeating, generated from data
Bulk PDF generation — invoices, certificates, transcripts, statements. This is where the real engineering happens:
- WeasyPrint or Puppeteer to convert HTML/CSS to PDF. Modern web designers can build a beautiful invoice template once.
- ReportLab (Python) for full programmatic control.
- DocRaptor / Prince for high-end commercial work where typography matters.
Pair with our batch processing guide for tips on running these at scale.
Case 5: Forms
If "create a PDF" means "create a fillable form," the workflow is different. Either start from a designed PDF and add interactive fields, or use a forms-first tool like Adobe LiveCycle (legacy) or a modern alternative. See how to create a fillable PDF form.
Settings that matter at export time
Whichever tool you use, the export step is where good PDFs are born:
- Embed all fonts. Otherwise the document renders differently on machines without the font.
- Pick the right resolution. 150 DPI for screen, 300 DPI for print, 600 DPI for fine print work.
- Compress images appropriately. JPEG quality 85 is the sweet spot for photos; PNG for screenshots and diagrams.
- Tag for accessibility. Always on for any document a human will read. See accessibility tags.
- Choose PDF/A for archival. Don't use it for everyday sharing — it disables features. Read the PDF/A guide.
After creation: the polish steps
A freshly created PDF is rarely the version you ship. Common polish:
- Add bookmarks for documents over 10 pages. See adding bookmarks.
- Add a clickable table of contents for long documents — generated from the source's heading hierarchy.
- Strip metadata before external delivery. See stripping metadata.
- Compress to reduce file size for email. See reducing PDF file size.
- Sign if the recipient expects an authoritative version. See signing a PDF online.
Anti-patterns to avoid
- Print-to-PDF when a direct export exists. The direct export almost always preserves more (links, bookmarks, accessibility, vector graphics) and produces a smaller file.
- Saving an editable PDF when you mean to deliver final. Flatten interactive elements before delivery if you don't want them edited. See flattening a PDF.
- Forgetting to proof on a different device. PDFs render differently on phone, tablet, desktop, and print. Spot-check at least one of each before shipping.
Conclusion
There is no single "create a PDF" tool. There is the right export step from whichever tool you already use, plus a polish layer at the end. For browser-based polish — bookmarks, compression, watermarks, signatures, metadata stripping — Docento.app covers most of the post-creation steps without uploading the file anywhere.