Word, Google Docs, fillable PDF forms and the code routes
Mail merge to PDF: which route actually gives you the files?
The reason this question is asked so often is that Word's mail merge does not have a PDF answer built into it. Microsoft's own guidance describes a main document, a data source and a merged document, and says nothing about producing a PDF at all, let alone one PDF per record. So everything people do is a workaround, and there are four families of them with genuinely different costs. Two questions and you will know which family you are in, what it will actually take, and which named limitation is about to catch you.
Three parts
what a mail merge is made of: a main document with merge fields, a data source, and a merged document generated per record
Microsoft, use mail merge for bulk email, letters, labels and envelopes
No PDF step
Microsoft's mail merge guidance describes no PDF output and no per-record file, which is why every route on this page is a workaround
Microsoft, use mail merge for bulk email, letters, labels and envelopes
Any database
the data source can be anything Word can connect to: Excel spreadsheets and Outlook contact lists are the most common
Question 1
What do you need out of it?
This is the decision that separates a five minute job from a scripting project, and it is worth being precise about before you start.
What it does and does not check
- One combined PDF against one PDF per record, which is the decision everything else follows from
- Word on Windows, Word on Mac, and why the two are not the same problem
- Google Docs and Apps Script
- Filling an existing fillable PDF form, which is a different job entirely
- Emailing a personalized PDF to each recipient
- Accessibility, which almost every merged PDF fails and which federal policy tells agencies to weigh before choosing the format
- Route selection only. This page does not merge your documents and does not ask you to upload them anywhere
Mail Merge PDF is an independent site operated by Ellul Solutions Ltd. It is not affiliated with, endorsed by or connected to Microsoft, Google, Adobe, the U.S. General Services Administration or any software vendor, and it does not sell, resell or receive commission on any product named or unnamed here. This site does not merge, convert or process your documents and never asks you to upload one. Software behaviour changes between versions and platforms; everything stated here was checked against the vendor documentation cited on this page on the date shown at the top of it, and where a capability is described as absent it means the cited guidance describes no such capability.
Mail merge to PDF: the routes, what each produces and what it costs, 2026
Last updated
Word's mail merge has no PDF step, so every method here is a workaround built on top of it or a way round it. This table sets out what each route actually produces and the named limitation that catches people using it.
The mail merge mechanics are quoted from Microsoft's own support guidance, read on 15 August 2026, including its description of the main document, the data source and the merged output, and the fact that its mail merge pages contain no information about PDF output or about writing each record as a separate file. That absence is stated as an absence rather than inferred from silence elsewhere. The Google route is described against Google's published Apps Script documentation for Docs. The accessibility row is quoted from Section508.gov's guidance on creating accessible PDFs. Effort is described in categories rather than in hours, because how long a route takes depends on the operator and a number here would be invented. No product is named, no price appears, and no route is recommended over another: the right one is decided by the output you need and the tools you already have, which is what the checker above sorts on. Software changes, so the date at the top of this page is the date these behaviours were checked.
| Route | What it produces | What it needs | The limitation that catches people |
|---|---|---|---|
| Word mail merge, export to PDF | One PDF containing every record | Word and a data source. No add-ins, no scripting | Section breaks. The merge inserts one per record, and a template with its own page break gives you a blank page between every letter |
| Word merge plus a splitting macro | One PDF per record, named from the data | Word on Windows, and a macro or an add-in. Microsoft's own mail merge guidance describes no per-record file output | Naming. Files called Document1 to Document400 are no more useful than the combined PDF, so the macro has to pull a field from the source |
| Word on Mac | The same as above, with fewer tools to get there | A different automation model from Windows, so Windows macros generally do not run | Copying a solution from a Windows forum and losing a day. Google Docs or a script is usually the shorter path |
| Google Docs with Apps Script | One PDF per record, named, optionally emailed | A template document, a spreadsheet and a script. PDF export and file writing are both first-class operations | Execution time limits on long runs, and a drive filling with intermediate document copies that nobody deleted |
| Filling an existing fillable PDF | Copies of one fixed document with different field values | A PDF that already has named form fields, and a mapping from your data to those names | It is not a mail merge. A flat PDF with printed lines has no fields to fill, and overlaying text at coordinates breaks when the form is reissued |
| A script, run once | One PDF per record, with full control of layout | A template, usually HTML, and a PDF conversion step | Filenames from real data contain slashes and quotes, and empty fields leave double spaces and blank lines unless handled explicitly |
| A scheduled or product pipeline | The same output, repeatedly and unattended | Everything above plus idempotency, per-row failure handling, template versioning and a retention position | Running twice. Duplicating, overwriting and failing loudly are all defensible; doing one of them by accident is not |
| Any of the above, if the output is published | A PDF that most assistive technology handles poorly | An accessible alternative, and a decision made before the pipeline is built | Section508.gov notes that PDFs are often not the most accessible or mobile-friendly option, and that federal policy requires agencies to prioritize HTML and use PDFs only when necessary |
- Microsoft's mail merge guidance describes a main document with merge fields, a data source, and a merged document generated per record, and contains no PDF output step at all.
- Word can produce one PDF containing every merged record in two steps, and cannot produce one PDF per record without a macro or an add-in.
- The data source for a Word mail merge can be any database Word can connect to, with Excel spreadsheets and Outlook contact lists the most common.
- Word for Mac uses a different automation model from Word for Windows, so splitting macros written for Windows generally do not run on it.
- In Google Apps Script, exporting a document as a PDF and writing it as a separate named file are both ordinary operations rather than workarounds.
- Filling a fillable PDF form is a different task from a mail merge: the document is fixed and only named field values change.
- Section508.gov states that PDFs are often not the most accessible or mobile-friendly option, and that federal policy requires agencies to prioritize HTML and use PDFs only when necessary.
- A merged run inherits accessibility from its template, so a template with no heading styles and no document language produces thousands of inaccessible files rather than one.
Cite this page
“Mail merge to PDF: the routes, what each produces and what it costs, 2026”, Mail Merge PDF, https://mailmergepdf.com/ (updated 2026-08-15). The mail merge mechanics are quoted from Microsoft's own support guidance, read on 15 August 2026, including its description of the main document, the data source and the merged output, and the fact that its mail merge pages contain no information about PDF output or about writing each record as a separate file. That absence is stated as an absence rather than inferred from silence elsewhere. The Google route is described against Google's published Apps Script documentation for Docs. The accessibility row is quoted from Section508.gov's guidance on creating accessible PDFs. Effort is described in categories rather than in hours, because how long a route takes depends on the operator and a number here would be invented. No product is named, no price appears, and no route is recommended over another: the right one is decided by the output you need and the tools you already have, which is what the checker above sorts on. Software changes, so the date at the top of this page is the date these behaviours were checked.
Want somebody to build the pipeline?
Tell us the volume and what has to come out the other end. Document automation suppliers and developers who do this work will contact you directly.
Worth knowing
The longer answers, with sources.
Word mail merge to separate PDF files
Word has no button for this. The three-part workaround, the naming decision that makes it worth doing, and the Excel formatting trap that ruins large runs.
Mail merge to PDF with Google Docs and Apps Script
The route where producing a PDF per record is an ordinary operation rather than a workaround, and the only one that runs unattended on a schedule.
Filling a PDF form in bulk: not a mail merge
A merge builds a document from a template. Filling a form writes values into named fields in a fixed document. Which one you have decides everything.
Merged PDFs and accessibility, which most of them fail
Section508.gov says federal policy requires agencies to prioritize HTML and use PDFs only when necessary. What that means for a merge pipeline you are about to build.
The questions we get
Can Word mail merge produce a separate PDF for each record?
Not on its own. Microsoft's mail merge guidance describes a main document with merge fields, a data source, and a merged document generated per record, and contains no information about producing PDF output or about writing each record as a separate file. What Word does easily is merge to one new document and export the whole thing to a single PDF. Producing one file per record needs a macro that walks the sections and exports each one, or a third-party add-in that does the same.
How do I mail merge to PDF on a Mac?
Word for Mac uses a different automation model from Word for Windows, so splitting macros written for Windows generally will not run. Three routes work better. Do the merge in Google Docs with Apps Script, which runs in the browser and does not care about the operating system. Merge and export to a single PDF on the Mac, then split the PDF, which is a simpler problem with more tools. Or write a short script, which is usually less work than fighting an unfamiliar automation model.
Why are my merged numbers or dates wrong?
Because Word takes the underlying value from the data source, not what the source displays. A spreadsheet cell showing £1,250.00 can arrive as 1250 or as a long decimal. The fix is to format inside the merge field, using a numeric or date picture switch on the field itself, rather than formatting the spreadsheet. This is the defect most likely to produce a large run of correct-looking documents with wrong figures in them, and it stays invisible until somebody reads one carefully.
Is filling a PDF form the same as a mail merge?
No, and confusing the two is the most common wrong turn. A mail merge generates a document from your own template. Filling a form takes an existing PDF that already has named fields and writes values into them, leaving the layout untouched, which is usually the point when the form was designed by somebody else. If the PDF has no real form fields, there is nothing to fill: you either add fields to the source document or overlay text at fixed coordinates, which breaks when the form is reissued.
What is the best way to email a personalized PDF to each recipient?
A script, whichever platform you use, because the job has three steps that have to stay in step: generate the right PDF, attach it to the right message, and send it to the right address. Google Apps Script handles all three natively and runs unattended on a trigger, which is why it suits recurring sends. Whatever route you pick, run it against three records first: an off-by-one that attaches each recipient's document to the next recipient's email is both easy to write and impossible to recall.
Should merged documents be PDFs at all?
Often not, if they are being published rather than posted. Section508.gov states that PDFs are often not the most accessible or mobile-friendly option, and that federal policy requires agencies to prioritize HTML and use PDFs only when necessary. A merged run inherits its accessibility from the template, so a template without heading styles, tagged tables and a document language produces thousands of inaccessible files rather than one. That is cheap to fix before the run and not fixable afterwards.
What changes when a mail merge runs on a schedule?
The requirements, not just the timing. A scheduled job needs a defined behaviour when it runs twice, whether that is skipping, overwriting or failing loudly. It needs per-row failure handling, so one bad record neither stops the run nor disappears. It needs template versioning, so documents generated before a wording change can still be reproduced. And it needs a retention position, because you have built something that generates personal data in bulk and somebody will ask where those files live and for how long.
Find the route before you open Word
What has to come out, and what you are working with. Two answers and the method is decided.
Use this on your own site
<script src="https://mailmergepdf.com/embed.js" async></script>