How to mail merge to separate Word documents

Word finishes a merge by stacking every record into one long document. Getting one file per record is a separate job, and Word has never had a button for it. Here are the four routes that actually work, and what each one costs you.

Why Word does this

When you click Finish & Merge → Edit Individual Documents, Word produces a single new document where each record sits in its own section, separated by a next-page section break. It looks like separate letters because each starts on a fresh page. It is one file.

This trips people up because the menu says "Individual Documents". It means individually merged records, not individual files on disk. Microsoft has never shipped one-record-one-file, and support answers on this question have pointed at macros and third-party add-ins for over a decade.

Splitting a mail merge into separate PDF documents too

The same four routes below produce separate Word files or separate PDF documents — the split is the hard part, the format is a setting.

Route 1: Save each page by hand

Open the merged document, select a section, copy it into a new blank document, save. Repeat.

Fine for five records. At thirty it is an afternoon, and every file gets its name typed by hand, which is where the typos come from. Also worth knowing: copying a section into a blank document does not bring the header, footer, or page setup with it. If your letterhead lives in the header, you lose it.

Route 2: A VBA macro

This is the answer you will get on most forums. You loop over the sections of the merged document and save each one out. The shape of it:

Sub SplitMergedDocument()
    Dim src As Document, out As Document
    Dim i As Long, folder As String
    Set src = ActiveDocument
    folder = "C:\Users\you\Documents\merged\"

    For i = 1 To src.Sections.Count
        src.Sections(i).Range.Copy
        Set out = Documents.Add
        out.Range.Paste
        out.SaveAs2 folder & "record_" & Format(i, "000") & ".docx", _
                    wdFormatXMLDocument
        out.Close SaveChanges:=False
    Next i
End Sub

Treat that as a skeleton, not a finished tool. In practice you will spend your time on the parts it does not handle:

• Names. record_001.docx is not what anyone wants. Naming files from a field means reading the data source separately, or adding helper columns like DocFileName that the popular macros expect.
• Headers and footers. Copy-paste of a section range does not carry page setup. Most working macros copy the whole document and delete what they do not need, rather than copying a section into a blank file.
• An extra empty page. The trailing section break usually comes along for the ride and leaves a blank page at the end of every file.
• Macros may simply be off. On a managed work laptop, macro execution is frequently disabled by policy, and you will not be given an exception for this.

Route 3: The Merge Tools add-in

There is a well-known free add-in from a Word MVP that adds "Merge to Individual Documents" to the ribbon, with filenames taken from a field in your data. It works, and if you can install it, it is a reasonable answer.

The catch is the install: Windows desktop Word only, and it is a template you drop into Word's startup folder. On a locked-down machine, on a Mac, or on Word for the web, this route is closed.

Route 4: Do it in the browser instead

The reason all of the above is awkward is that you are asking Word to undo something it just did. If you skip the merge and go straight from template plus list to a folder of files, the problem disappears.

That is what Docs from Excel does. You upload your .xlsx or .csv and type what the documents are; every row comes back as its own Word file or PDF, named from whichever column you pick. Bring a .docx of your own with {{placeholders}} in it and that one is used instead — headers and footers survive, because the template file is never taken apart. Nothing to install, no macros.