The AI-native PDF generator for polished documents and automated workflows.
Describe the document and Claude designs it — or build it yourself in the canvas. Bind the fields that change, and generate by the thousand: from the editor, the API, or AI.
Author with Claude Code
Describe the document and Claude designs it — no canvas required.
Describe the document. Claude designs and renders it.
An open-source plugin for Claude Code — install in two commands, then just ask. Every design lands in your workspace.
# one-time setup $ export IMAGINEPDF_API_KEY=pc_live_•••••••• $ claude > /plugin marketplace add imaginepdf/claude-imaginepdf > /plugin install imaginepdf@imaginepdf > Create an invoice for Brightfox Interiors. Our logo top-left, a line-item table for three services, subtotal with 18% GST and a grand total, a Pay-Now QR in the footer, and net-30 terms. Make the customer name and line items template variables. ⏺ Authoring design · logo, line-item table, totals, QR ⏺ Binding variables · customer_name, line_items ⏺ Checking preview · aligning the totals column ⏺ Rendering PDF ✓ invoice-brightfox.pdf · download ready design saved to your workspace · open it in the editor anytime
Most documents are still produced by hand.
Invoices, certificates, reports, tickets, labels — the volume is real, but the tooling is stuck somewhere between a Word doc and a developer-only PDF library. ImaginePDF fills the gap in the middle.
Word templates that break the moment you touch them
Tables misalign, fonts swap on another laptop, page breaks move every time the numbers change — yet teams keep hand-editing the same doc for every invoice.
Copy-paste workflows that do not scale
Sheet to doc to PDF, fifty times over. The work is mechanical; the errors are not — wrong totals, wrong names, wrong logos quietly ship.
PDF libraries built for engineers, not designers
Python, LaTeX, HTML-to-PDF — the person who owns the brand cannot touch the layout, and the engineer becomes a dependency for every tweak.
ImaginePDF replaces all three with one pipeline: design the template once, then generate — by hand, by code, or by AI.
Everything between your data and the finished PDF.
Turn a designed template into finished documents at any volume — these are the pieces that make it repeatable.
Visual canvas editor
Drag text, tables, images, shapes, QR codes, and barcodes onto a real page — multi-page, with repeating headers and footers. No HTML, no LaTeX, no engineer.
Bind any element to a named field
Select any element — text, image, QR, barcode, or a whole table — hit "Make dynamic," and fill it from a CSV, a form, or an API.
Bulk generation from a dataset
Point a template at a CSV and every PDF renders in parallel — table rows grow to fit each record. Download a zip or pull presigned URLs.
Team workspaces with roles
Owner, admin, and member roles. Templates, fonts, logos, datasets, and history live with the workspace, not the person who made them.
From blank canvas to production in four steps.
The same flow for one certificate or ten thousand payslips — no separate path for bulk, just a larger dataset.
Design the template
Lay it out in the canvas — text, tables, images, QR, barcodes. No code.
Make elements dynamic
Bind any element — text, image, QR, barcode, or table — to a named field.
Feed it data
One row, a CSV, a JSON payload, or an API call — same template, any source.
Generate at scale
One PDF or ten thousand, batched in parallel — a zip, presigned URLs, or streamed back.
Design the template
Lay it out in the canvas — text, tables, images, QR, barcodes. No code.
Make elements dynamic
Bind any element — text, image, QR, barcode, or table — to a named field.
Feed it data
One row, a CSV, a JSON payload, or an API call — same template, any source.
Generate at scale
One PDF or ten thousand, batched in parallel — a zip, presigned URLs, or streamed back.
One engine. Three doors.
Every template renders by hand, by code, or by AI — same fonts, same layout math, same pixel-exact PDF, whichever door you take.
The canvas editor
For the person who owns the brand.
Design on a real page, fill the dynamic fields, and generate — one doc or a whole CSV, without leaving the dashboard.
The REST API
For your product and your pipelines.
JSON in, PDF out. Keys are workspace-scoped, never personal — so service accounts stay clean as the team changes.
# 1,000 invoices from one template curl https://api.imaginepdf.com/api/v1/designs/inv_42/batch \ -H "X-API-Key: pc_live_..." \ -d @invoices.json # → a batch job · zipped download when ready
Claude Code
For when you'd rather just describe it.
Plain English in, designed PDF out — and the design lands in your workspace, ready for the editor or the API.
> Invoice for Brightfox Interiors — 3 line items, Pay-Now QR ⏺ design authored · preview checked · PDF rendered ✓ invoice-brightfox.pdf · download URL returned
Invoices on Monday, certificates after every cohort, labels on every shipment.
Each is a place teams burn hours on copy-paste. ImaginePDF replaces the fragile template with one repeatable pipeline.
Invoices & receipts
Pull line items out of your billing system, render branded invoices, deliver them by email or to a customer portal.
→ INV-2024-0042.pdfPayslips
One payslip template, one row per employee, one button. Tax breakdowns, leave balances, year-to-date totals included.
→ Payslip · April.pdfCertificates
Personalised certificates from an attendee list. Names, dates, signatures, logos — all from a single CSV upload.
→ Certificate of Completion.pdfQuotations & proposals
Polished quotes with auto-calculated totals, tax, and validity dates. Reuse the same template for every deal.
→ Quote #Q-1837.pdfReports
Monthly client reports, internal audits, dashboards rendered as PDF. Tables, charts, and a consistent cover page.
→ Monthly Report.pdfLabels & tags
Shipping labels, product tags, asset stickers with QR or barcodes baked in. Print a sheet, scan in the warehouse.
→ SKU-A1098.pdfMake your first PDF without signing up.
Start from a public maker — no account needed. When you're ready to scale, the same templates wait in your workspace.
And never start from a blank page: pre-styled tables and a ready-made type scale in the editor — and any finished design publishes as a template your whole workspace reuses, variables and assets included.
Questions teams ask before they ship the first template.
If you're trying to figure out whether ImaginePDF (also written Imagine PDF) fits between your spreadsheet and your customer's inbox, this is where to start.
Word templates were never built for repeatable generation — fonts shift across machines, layouts break when content changes, and you can't render a thousand at once from a dataset. ImaginePDF treats the template as data — a designed layout with typed fields — so output is identical whether you generate one or ten thousand.
No. The canvas editor and dashboard are the primary surface — if you've used Canva or Figma, you can design a template and run a batch from a CSV. The REST API and Claude integration are there when you want to trigger generation from your own product.
Text, images, tables, shapes, QR codes, and barcodes — enough for invoices, certificates, reports, tickets, labels, and any document with a layout. Any element can be wired to a dynamic field, image URLs included.
Design a template once, mark the fields that vary as dynamic, then POST a JSON object of values — back comes a presigned link for one PDF, or a job you poll for a zip in bulk. Requests authenticate with a workspace-scoped API key; endpoints and examples live in the docs.
The open-source imaginepdf plugin gives Claude Code two skills: design (author or edit a layout) and generate (one PDF or a batch). Describe the document in plain English — Claude designs it, renders it, returns a link, and saves the design to your workspace for the editor or API.
Yes. You can design templates, create an API key, and generate documents on the free plan; paid plans add batch generation, more credits, and team seats. See /pricing for the full comparison.
You do. Templates are stored in your workspace, generated PDFs are downloadable, and we do not train models on your designs or data. You can export templates and delete a workspace at any time.
Yes. Workspaces support owner, admin, and member roles. Templates, brand assets, fonts, datasets, and generation history are all workspace-scoped, so the work stays with the team — not with the person who happened to create it.
Stop emailing Word docs.
Start shipping PDFs.
Design your first template, point it at a CSV, and generate the whole batch the same afternoon. No setup call, no migration.
- Unlimited templates and dynamic fields
- One engine — editor, API, and Claude Code
- Templates and data stay yours — export anytime