Adobe Acrobat Mail Merge: What to Use Instead

By Josh · August 25, 2026

You have Acrobat Pro open, a spreadsheet with 300 rows, and you have been through the tools panel twice looking for the merge. It is not hidden behind a menu you missed.

Does Adobe Acrobat have mail merge? No. Acrobat creates, edits, signs and exports PDFs, and none of that includes reading a spreadsheet and writing one file per row. A PDF mail merge happens somewhere else: in Word before the PDF exists, in a paid Acrobat plug-in written by a third party, or in a batch tool that renders the rows itself.

Which of those is yours comes down to one question, worth answering before you install anything. Where does your template live right now?

A Word document, with the data in Excel. Go to route 1.
A fillable PDF form you built or were sent. Route 2.
Anywhere, but the data is in Google Sheets. Route 3.
A finished design nobody wants to rebuild, from a designer or last year's batch. Route 4.

Why there is no Adobe Acrobat mail merge

Acrobat's job starts after the document is written: annotate it, sign it, split it, redact it, ship it. Merging a data source into a layout is authoring work, and Adobe put that in the authoring tools.

The closest thing Adobe ships is not in Acrobat at all. Installing Acrobat Pro on Windows also installs PDFMaker, an Office add-in, and PDFMaker adds a Merge to Adobe PDF button to Word's Mailings tab. Adobe's own instructions still describe it as Acrobat > Mail Merge, and they cover Windows only. That button is why so many people are certain an Acrobat mail merge exists somewhere. The merge is Word's, and the button only hands the result to Acrobat.

Where it breaks: the button vanishes. An Office or Acrobat update disables the COM add-in, and Word gives you no notice that anything is gone. If you use this once a year, the year you need it is the year it disappears, and the fix is usually to tick Acrobat PDFMaker Office COM Addin again under File > Options > Add-ins > Manage COM Add-ins > Go. Plenty of people never find that and end up borrowing the one machine in the office where it still works.

Route 1: a Word template with the data in Excel

This is most people, and it is the shortest path. Do the merge in Word, where merge fields and an Excel data source are first-class, then deal with the PDFs afterward.

An Acrobat mail merge from Excel, done this way, is two steps: Word fills the template, and something splits the result. Word's own Finish & Merge gives you one long document with every record stacked end to end, which is the wrong shape if you need offer-letter-maria.pdf and offer-letter-david.pdf as separate files. A short VBA macro loops the merge and exports each record on its own. We wrote that macro up, including the counting bug that makes most copies of it silently do nothing, in how to split a mail merge into separate PDF files. Ten minutes, and it costs nothing.

If Merge to Adobe PDF is in your Word ribbon, try it before the macro. Adobe's documentation has it writing one PDF per record, and the same dialog will attach each one to an email for that record's recipient. What it will not do is name the files. You type a base name and get JulyLetter_0000123, JulyLetter_0000124 and on down the list, so if they have to arrive as offer-letter-maria.pdf, you are back to the macro.

Where it breaks: macro policy. A managed workstation that blocks VBA blocks this whole route, and no amount of Acrobat licensing changes that.

Route 2: the template is a fillable PDF form

This is the one case where Acrobat is the right application to have open, and it still has the least satisfying answer on the page.

If your template is an AcroForm, a PDF with named fields you built under Prepare a form, Acrobat can import data into it. Open the form, pick Options > Import data, and the fields populate. The formats Adobe lists there are FDF, XML and tab-delimited text, so a CSV gets converted before it is any use. And that is one record into one open form. Do it 300 times and you have done a mail merge by hand, which is the discovery that sends people looking for a plug-in.

Two ways out of the loop:

A plug-in. EverMap's AutoMailMerge (opens in a new tab) is the one searchers keep landing on, partly because its own how-to PDF turns up in the results for mail merge to pdf. It reads Excel, CSV, tab-delimited text, Access or an ODBC source, maps columns to your form's field names, and writes the batch out as separate documents, each emailed to the address in its row if you want that. It also renames form fields in bulk, which is the chore below. If your template really is a form and you are staying in Acrobat, buy this. Two requirements first: Windows, and a full Acrobat install (Standard or Professional, not Reader). No price appears on the product page, so get that and the supported Acrobat versions from their site.

A script. Form filling is well supported across the PDF tooling, so if you can run code the loop is short. pdftk fills a form from an FDF or XFDF data file:

pdftk form.pdf fill_form row.fdf output out/alice.pdf flatten

The original pdftk stopped at 2.02 in 2013, and most Linux distributions now package pdftk-java, a port that takes the same command line. The interesting work either way is generating one row.fdf per spreadsheet row, a few lines in any language. Python's pypdf skips the FDF step and writes the values straight in, with update_page_form_field_values(page, {"first_name": "Maria"}). Flatten the output in whichever tool, unless you want recipients able to edit what you just filled in.

Where it breaks: field names. A form built by clicking through Prepare a form's auto-detection ends up with fields called Text1, Text12, Text3, in an order that matches nothing. Both routes above map columns to those names, so the first real task is renaming them to first_name and invoice_total and whatever else the sheet calls them. Acrobat does that one properties dialog at a time. AutoMailMerge does it in bulk.

Route 3: the data is in Google Sheets

Then do the merge on the Google side and let the PDF be the output rather than the starting point. Add-ons handle this free at small volumes, with Google's Apps Script quotas as the ceiling you eventually meet. The routes, and the quota numbers that decide between them, are in the Google Sheets mail merge guide.

Exporting the sheet to Excel and going back to route 1 also works, at the cost of the live connection: next month's data is in the sheet, and your merge points at a copy.

Route 4: the template is a design, not a form

Certificates, statements, anything a designer handed you as a finished PDF. The template has no fields, and adding them under Prepare a form means drawing boxes over a layout that was never built to hold them. Text will not reflow, and a long name clips. The result looks like a form, because now it is one.

The tools for this job take a spreadsheet and render one PDF per row against a layout, without asking you to rebuild that layout as an AcroForm. CraftMyPDF (opens in a new tab) and PDFMonkey (opens in a new tab) are two of them, both built around their own template editor plus a JSON API your code calls. If the merge belongs inside software you are already writing, one of those two is the shorter path: your code posts a row and gets the PDF back. CraftMyPDF will import your existing PDF into its editor, where it arrives as loose components you then wire up to your columns. Prices, and which of these run unattended, are in convert a spreadsheet to PDF automatically; if your data is a raw file rather than a live sheet, CSV to PDF covers which ones read it as it sits.

Every tool in this category is a subscription, and none of them live inside Acrobat. If the batch is one afternoon a year, route 1 and a free macro is the better trade.

When nobody is going to rebuild the layout

SheetRender is ours, so price that in as you read this part.

It is built for the reader whose routes 1 and 2 both dead-ended. There is no Word original and no fillable form, only a finished document and a list of people it has to go out to. You upload the PDF Acrobat is showing you right now, or a photo of the printed copy if that is what survived, and Claude reads the layout back as a template with fields pointed at your spreadsheet columns. The data is a CSV or .xlsx upload, or a Google Sheet we pull when the run starts. Look over what it mapped, then generate. Each row lands as its own file, and the file names come out of a column you pick, which is the one thing route 1's PDFMaker button could not do: cert-alvarez.pdf rather than Certificate_0000123. Each file can then be emailed to the address sitting in its row.

The other half of the case is repetition. Acrobat gives you nothing to schedule, and a form-filling script gives you nothing until you wrap it in cron. A run here fires on its own, hourly through monthly, and can be held to rows added since the last one, so the batch is in the folder before it reaches your Monday list. Schedules are paid: when I last checked, $19 a month covered one active schedule and 1,500 documents, and $49 removed the schedule cap and opened the 15-minute option. Our pricing page has the current figures.

Where it breaks: the rebuild. Tight spacing and dense tables are where a reconstructed layout goes wrong, and a crooked photo produces a crooked template, so read the first few PDFs yourself before turning 300 loose on a mailing list. Getting that template built also means the column headers and a handful of your first rows go to Anthropic, because their model is what does the reconstructing; a sheet of salaries or student records is therefore a conversation with somebody in your organization before it is a purchase. Everything comes out as PDF, so the one certificate that needs a line changed afterward gets changed in Acrobat, by hand, and your spreadsheet never hears about any of it. On free you get 50 documents a month, 2 templates, generated files deleted after 30 days, and no scheduling. The "Made with SheetRender" footer lands on document one, not on document 51. Fifty watermarked certificates are enough to judge what came back. They are not enough to send.

The Acrobat features that look like a merge

Four Acrobat features come up in every forum thread on this question. Three of them cost someone an hour before they give up.

Combine files takes a pile of files and produces one PDF. It is the opposite move, the thing you would use to glue a finished merge back together.

Action Wizard runs a saved sequence of Acrobat commands over a folder. It is real automation and earns its keep stamping or flattening a batch you already have, but nothing in its command list reads a spreadsheet, so it applies one action to many files and cannot make many files from one template. The Execute JavaScript step is a genuine escape hatch. Once you are writing code, though, the pdftk or pypdf loop from route 2 is the easier place to put it.

AI Assistant works on documents you already have: summaries with citations, answers, rewrites, even a presentation built out of a stack of files. What it has no version of is a spreadsheet input and a batch. Three hundred personalized letters is not a longer prompt.

Send in Bulk is the one that really does merge data. Upload a CSV and each row becomes its own agreement carrying that row's values, up to 1,000 per send. Adobe lists CSV import under Acrobat Sign Solutions, though; Standard and Pro leave you typing recipients in by hand, and the output goes out for signature rather than landing in a folder as 300 files. If signatures are the point, this is the right door.

Which route is yours

Word template, Excel data, Windows, VBA allowed: Word plus the macro. Free, and the sibling post has the code.
Word template and the Merge to Adobe PDF button is present in your ribbon: use it first, unless the file names have to come from the data.
A real fillable form with clean field names, staying in Acrobat: an Acrobat merge plug-in.
A real fillable form and you can write a loop: pdftk or pypdf.
Data in Google Sheets, small batches: a Sheets add-on.
A designed PDF, no Word original, and the batch comes back every month: a hosted renderer that builds the template from the document you already have.

Questions people ask

Can you do a mail merge in Adobe Acrobat? Not with Acrobat alone. It fills one form from one data file and automates actions across a folder, but nothing in it turns a spreadsheet into a folder of finished PDFs. The nearest thing Adobe sells is Send in Bulk in Acrobat Sign Solutions, which merges CSV values into one agreement per row and sends each one for signature.

How do I mail merge from Excel to PDF? Build the template in Word, connect it to the Excel file through Mailings > Select Recipients > Use an Existing List, insert your merge fields, and export. Word merges to a single combined document by default, so one PDF per row needs the VBA loop in the separate-PDFs guide, the Merge to Adobe PDF button if Acrobat installed it, or a tool that writes separate files natively.

Can you mail merge a fillable PDF? Yes, but not with stock Acrobat, which imports a single record into an open form. Batch filling from a spreadsheet takes a commercial plug-in such as AutoMailMerge, or a script that fills the fields in a loop. Rename auto-detected fields to something meaningful first, or the column mapping is guesswork.

Is there a free way to do a PDF mail merge? Two, and neither involves Acrobat. The Word macro costs nothing if you have Word and your workplace allows macros. Free Google Workspace add-ons merge from a Google Sheet into Docs or Slides templates and export PDFs, within Google's daily script quotas.

What I would tell you if you called

What makes this question so frustrating is that nothing is broken. You are holding a professional PDF application, the task is obviously a PDF task, and the feature lives one application upstream. Nobody at Adobe hid it.

So stop looking, and go back to where the template came from. A Word document finishes in Word. A form means buying a plug-in or writing a loop, and how painful either gets was settled months ago by whoever named the fields.

The designed documents are what people fight hardest, because Acrobat can open one and edit the text in it, which feels like most of the way there. Editing one document and generating 300 are not the same job, and Acrobat only does the first. If that is where you are, stop trying to turn the design into a form and hand it to something that treats the design itself as the template. Then give Acrobat back the work it is good at. The merge happens before Acrobat ever sees the file.