Batch Fill PDF Forms from Excel - One PDF per Row
Upload the PDF template and the spreadsheet you already use. Map Excel, CSV, or Google Sheets columns to PDF fields or page positions, preview real rows, then export separate PDFs, a ZIP batch, or one merged review PDF.
Local-first browser workspace: Excel and CSV rows are processed in your browser, and you can test with a short real batch before running the full file.
Batch Fill PDF Forms from Excel - One PDF per Row
Upload a PDF or Image and Excel File to Generate a PDF Batch
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, and export one PDF per row, a ZIP batch, or one merged PDF.
Spreadsheet Data
Excel, CSV, or Google Sheets rows
Drop CSV / XLSX here
or click to choose from your device
PDF or Image Template
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
Continue Or Try A Demo
Batch fill PDF forms from Excel, CSV, or Google Sheets
Start with the files you already have: one PDF template and one spreadsheet. Upload both, map columns to PDF fields or fixed page positions, preview the hard rows, and generate one finished PDF per row.
Upload Excel, CSV, or Google Sheets rows
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.
Upload the PDF template
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.
Map Excel columns to PDF fields
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.
Export one PDF per row, ZIP, or merged PDF
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.
Ready to test one real PDF and a short Excel file?
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.
PDF mail merge guides by data source and template type
Use these guides when you want the same spreadsheet-to-PDF workflow explained for a specific source file, output format, or PDF template problem.
How to Fill a PDF from Excel
Learn the full Excel-to-PDF workflow: upload a workbook, map fields, preview rows, and export the batch.
PDF Mail Merge from Google Sheets
Start from a live Google Sheet and turn rows into filled PDFs without rebuilding the template in Word.
Fill a PDF from CSV
Use CSV exports from business systems as the source data for one-PDF-per-row generation.
Fill a Non-Fillable PDF
Place spreadsheet values visually on static PDFs, scans, certificates, invoices, and fixed layouts.
Generate One PDF per Row
Set up filenames, output format, and batch export when every spreadsheet row needs its own PDF.
Map Excel Columns to PDF Fields
Decide between detected PDF form fields and visual overlay mapping for spreadsheet columns.
Batch Fill PDFs Without Acrobat
Compare a browser-based PDF mail merge workflow with Acrobat-heavy manual form filling.
Fillable vs Non-Fillable PDFs
Understand which kind of PDF template you have before choosing field detection or visual placement.
PDF Mail Merge vs Acrobat, Word Mail Merge, VBA, and automation platforms
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.
Output path: direct PDF vs conversion chain
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.
Template source: existing PDF vs rebuilt layout
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.
Review stage: real-row preview vs post-export fixes
PDF Mail Merge lets you check long names, missing optional fields, amounts, dates, and layout edge cases before generating the full batch.
Built for real PDF batches from spreadsheets
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?
Batch fill PDF forms from Excel
Import Excel data directly and generate many completed PDFs from one spreadsheet instead of copying values by hand.
Supports fillable and non-fillable PDFs
Use existing form fields when they exist, or place content visually on static PDFs, scans, certificates, and branded templates.
One PDF per row, ZIP, or merged PDF
Export separate PDFs for delivery, package the batch as a ZIP, or create one merged review PDF for approval and archive checks.
Excel first, Google Sheets when needed
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.
Map text, checkboxes, images, signatures, QR codes, and barcodes
Handle more than plain text so the PDF template can stay reusable across real business workflows.
Use filename rules based on spreadsheet columns
Build names from invoice numbers, names, dates, or IDs so the exported batch stays organized automatically.
Preview real rows before the full export
Catch layout issues, wrong mappings, and missing optional values before the batch becomes an operational problem.
Run it online without Acrobat or VBA
Use a browser-based workflow instead of maintaining fragile spreadsheet macros, custom scripts, or Acrobat-heavy manual steps.
Keep the approved PDF template
Use the existing certificate, invoice, contract, claim form, tax form, or scanned layout instead of rebuilding it in Word.
What users like after the first real batch
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
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
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
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
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
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
Jason W.
Compliance Admin
Questions about PDF mail merge from Excel and Google Sheets
These are the questions that usually matter before someone trusts a batch PDF workflow with real Excel or Google Sheets data.
Still have questions?
If you couldn't find the answer you're looking for, please feel free to ask us!
Test one PDF template with a short Excel file
Upload the PDF and spreadsheet you already use. If the preview, filenames, and export format look right, rerun the same mapping for the full batch.
Best first test: use 5 to 20 real rows, preview the hardest cases, then choose one PDF per row, a ZIP batch, or one merged review PDF.