Fill PDF forms from Excel, CSV, or Google Sheets. Upload your existing fillable or non-fillable PDF, map columns once, preview real rows free, then export one PDF per row, a ZIP batch, or one merged review PDF—without Acrobat or VBA.
Preview real rows free with a watermark. Full exports use credits (1 credit = 1 PDF page). Excel and CSV stay in the browser. No Acrobat or VBA.

Fill PDF from Excel | One PDF per Row, No Acrobat
Bring one PDF template, an image template (PNG/JPG/WEBP), and spreadsheet rows into one workspace. Map columns to form fields or visual positions, preview real data for free, and export one PDF per row, a ZIP batch, or one merged PDF. Full exports use credits (1 credit = 1 PDF page).
Excel, CSV, or Google Sheets rows
Drop CSV / XLSX here
or click to choose from your device
Fillable or non-fillable PDF form, document, certificate, invoice, contract, or any image (PNG, JPG, WEBP)
Drop PDF / Image here
or click to choose from your device
To batch fill PDF forms from Excel, upload the PDF template and workbook, map each spreadsheet column to a PDF field or page position, preview several rows, then export one completed PDF per row or download the batch as a ZIP. The PDF can be fillable, non-fillable, or scanned.
Start with the spreadsheet that already contains the data you trust. Upload Excel or CSV directly in the browser, paste a shared Google Sheet URL, or launch from the Google Sheets add-on.
Keep one output document per row so the batch stays predictable.
Use clear headers such as Full Name, Invoice Number, Date, Amount, or Signature URL.
The first goal is simple: get real spreadsheet rows into the mapper.
Choose the real PDF your team already uses. It can be a fillable PDF form, a non-fillable static template, a certificate, an invoice, a contract, or a scanned form.
If the PDF already has form fields, they can be detected automatically.
If the PDF is non-fillable, you can still place fields visually on the page.
The strongest workflow keeps the final PDF format intact instead of recreating it somewhere else.
Bind spreadsheet columns to detected form fields, or place text, images, signatures, QR codes, barcodes, and checkboxes visually on the PDF.
Map only the fields that belong on the PDF instead of trying to use every spreadsheet column.
Preview long names, unusual dates, large amounts, and empty optional fields before export.
Preview is where you confirm whether the PDF survives normal rows and messy rows alike.
When the mapping looks right, preview the hardest rows, then export the full batch as separate PDFs, a ZIP package, or one merged review PDF.
Use filename rules based on spreadsheet columns so the export stays organized automatically.
Run a short production-like batch first, then scale up once the filenames and output format look right.
This is the step that turns a one-off document task into a repeatable Excel-to-PDF workflow.
Use 5 to 20 representative rows first. If the preview, filenames, and export format look right, you can rerun the same mapping for the full batch.
See the full Excel-to-PDF mail merge workflow: upload spreadsheet and PDF template, map columns to fields, preview real rows, and export one PDF per row or a ZIP batch—without Acrobat or VBA.

Watch: Batch Fill PDF Forms from Excel — One PDF per Row
Start from a focused document workflow, then use the same Excel-to-PDF mapping engine on this page.
Walk through the workflow on this page: upload Excel, map fields, preview rows, and export one PDF per row.
Batch fill contractor and vendor W-9 PDFs from spreadsheet rows.
Turn billing spreadsheets into ready-to-send PDF invoices.
Create personalized certificates from Excel or CSV.
Generate agreements and contract packets from spreadsheet rows.
Map spreadsheet rows onto W-9, 1099, and similar tax PDFs.
Batch fill your own W-8BEN PDF template from payee rows.
Generate one NDA PDF per counterparty from your approved template.
Export an Airtable view and fill PDF templates one record at a time.
Batch fill PDFs from Excel without Acrobat Pro workflows.
Keep the approved PDF instead of merging through Word.
Spreadsheet batches instead of filling one PDF at a time.
The right tool depends on the job. If you only need to edit one PDF, a manual editor can be fine. If you have spreadsheet rows, a fixed PDF template, and a recurring batch, the workflow needs mapping, preview, filenames, and repeatable export.
| Comparison criteria | PDF Mail Merge Direct final PDF workflow | Word Mail Merge | Adobe Acrobat | VBA and scripts | Zapier / Make / APIs |
|---|---|---|---|---|---|
Uses your existing PDF template | Map fields directly onto the approved PDF | Usually requires rebuilding the layout in Word | Good for editing a PDF, weaker for spreadsheet batches | Possible with custom code | Depends on the PDF service behind the workflow |
Works with non-fillable PDFs | Place text, images, QR codes, and fields visually | Poor fit for static PDF layouts | Often needs form setup or manual placement | Possible, but placement logic must be maintained | Varies by provider |
Final PDF export without extra conversion | Export separate PDFs, one merged PDF, or ZIP directly | Often creates Word files first, then PDF conversion and merge | Fine for individual PDFs, slow for many rows | Can do it, but requires code and testing | Can do it after a larger setup |
Preview real rows before the full batch | Check long names, empty fields, and layout issues first | Preview is tied to the Word document, not the final PDF chain | Manual review is possible, batch preview is not the core flow | Usually depends on custom debug output | Often designed to run automatically, not review manually |
Reusable no-code mapping | Operations teams can rerun the same template without code | Reusable only if the document remains Word-native | Reusable form fields help, but static PDFs remain awkward | Requires code ownership | Reusable after setup, but heavier to change |
The Word path often looks simple at the start, then turns into many Word files, many PDF conversions, and one more merge step. That is exactly the workflow PDF Mail Merge removes.
Word Mail Merge often creates intermediate Word files first, then needs PDF conversion and merging afterward. PDF Mail Merge exports the final PDF batch directly from spreadsheet rows.
When the template is already a certificate, invoice, contract, or static form PDF, PDF Mail Merge keeps that approved PDF as the source instead of rebuilding it in Word.
PDF Mail Merge lets you check long names, missing optional fields, amounts, dates, and layout edge cases before generating the full batch.
A useful Excel-to-PDF workflow should answer the practical questions quickly: can I use my existing PDF, can I run many rows, can I preview before export, and can my team reuse the mapping?
Import Excel data directly and generate many completed PDFs from one spreadsheet instead of copying values by hand.
Use existing form fields when they exist, or place content visually on static PDFs, scans, certificates, and branded templates.
Export separate PDFs for delivery, package the batch as a ZIP, or create one merged review PDF for approval and archive checks.
Use Excel as the default path, or launch from Google Sheets when your source data already lives there and your team wants sheet-based handoff.
Handle more than plain text so the PDF template can stay reusable across real business workflows.
Build names from invoice numbers, names, dates, or IDs so the exported batch stays organized automatically.
Catch layout issues, wrong mappings, and missing optional values before the batch becomes an operational problem.
Test representative Excel rows without signup before using credits for the final batch export.
Use a browser-based workflow instead of maintaining fragile spreadsheet macros, custom scripts, or Acrobat-heavy manual steps.
Use the existing certificate, invoice, contract, claim form, tax form, or scanned layout instead of rebuilding it in Word.
These are the practical reasons people keep using the workflow after they try it on a real Excel or Google Sheets job.
We used to manually update invoices in Acrobat. The first batch with Excel made it obvious the repeat workflow was the real win.
Megan T.
Operations Manager
The fact that it also works with non-fillable certificate PDFs mattered more than anything else. We did not have to redesign the template.
Carlos R.
Training Coordinator
Previewing the hard rows before export saved us from sending broken onboarding PDFs with long names and missing optional fields.
Priya S.
HR Generalist
We wanted something easier than maintaining VBA. This was simpler to explain, simpler to rerun, and easier for the team to trust.
Daniel K.
Finance Lead
We only needed a few client batches each month, so the ability to start without committing to a subscription was a real advantage.
Sophie L.
Agency Producer
The Google Sheets launch path was useful, but the big benefit was having one place to map fields, review the PDFs, and keep filenames consistent.
Jason W.
Compliance Admin
These answers cover the practical questions before you trust a PDF mail merge workflow with real spreadsheet data.
If you couldn't find the answer you're looking for, please feel free to ask us!
Upload the PDF and Excel file you already use. Preview a few rows for free, then rerun the same mapping for the full batch when the filenames and export format look right.
Best first test: use 5 to 20 real rows. The preview is free and watermarked; full exports without a watermark use credits.