Upload Excel, Google Sheets, or CSV data to auto fill PDF forms online. Populate fillable or non-fillable PDF templates, preview real rows, and export one PDF per row, a merged review PDF, or a ZIP batch.
Start with Excel when the spreadsheet is local. Use Google Sheets when the source of truth already lives there.

Fill PDF from Excel Online - Auto Fill and Populate PDF Forms
Automatically fill PDF forms with data from Excel or Google Sheets, 100% locally.
Spreadsheet or Google Sheets
Drop CSV / XLSX here
or click to choose from your device
Fillable PDF form
Drop PDF here
or click to choose from your device
Upload the spreadsheet, upload the PDF, map Excel columns to PDF fields or page positions, preview real rows, and export the batch with a repeatable PDF mail merge workflow.
Start with the spreadsheet that already contains the rows you trust. Upload Excel or CSV directly in the browser, paste a public Google Sheet URL, or launch from the Google Sheets add-on.
Keep one document record per row so the output 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 that 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 form fields or place text, images, signatures, QR codes, and checkboxes directly 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 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 a small real batch first. If the preview, filenames, and output format already feel better than your current process, the workflow is a fit.
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.
The strongest spreadsheet-to-PDF tools answer the same questions quickly: does it work with my PDF, can it run in bulk, can I preview real rows first, and can I reuse the setup later?
Import Excel data directly and generate many completed PDFs from one spreadsheet instead of editing documents one by one.
Use existing form fields when they exist, or place content visually on static PDFs, scans, certificates, and branded templates.
Export separate PDFs for delivery or a merged review PDF for internal approval, printing, or 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.
Use a browser-based workflow instead of maintaining fragile spreadsheet macros or Acrobat-heavy manual steps.
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 are the questions that usually matter before someone trusts a batch PDF workflow with real Excel or Google Sheets data.
If you couldn't find the answer you're looking for, please feel free to ask us!
If the preview, filenames, and export format already feel better than your current process, you will know quickly whether this deserves a place in your recurring document workflow.
Best first test: use 5 to 20 real rows, preview the hardest cases, then choose whether you need one PDF per row or one merged review PDF.