A mail merge in one screen
Every mail merge is the same three objects, whatever the software in front of you. Get these right and the rest is menu clicks.
| Data source | A list, spreadsheet or database. One row per recipient, one column per variable |
| Main document | The letter, label or message body that every recipient receives |
| Merge fields | Placeholders in the main document that tell the software where each column goes |
| The real ceiling | Not the software. The daily recipient cap on the mailbox doing the sending |
A mail merge takes one document and one list and produces a personalised copy for every row. It is forty years old, it is built into software you already pay for, and it is still the fastest way to send two hundred letters or two hundred individually addressed emails without writing them twice.
What almost no walkthrough tells you is where it stops. The merge never fails at scale: Word will happily generate ten thousand documents. The mailbox will not send them. That gap is where most first attempts go wrong, so this guide covers the mechanics first and the ceiling second.
What a mail merge actually is
Microsoft describes the process in three parts, and the description is worth borrowing because it is software independent. A data source, such as a list, a spreadsheet or a database, is associated with a document. You work on that main document, inserting placeholders called merge fields. Those fields tell the program where to drop information from the data source.
Everything else is a variation on that. Mail merge letters, mail merge labels, envelopes and email messages differ only in what the finished output is: a printable page, a sheet of labels, or a message handed to a mail client. The data source and the merge fields work identically in all four.
Whether you run a word mail merge, a Google Sheets merge into Gmail or a script against an API, you are assembling the same three objects. The skill transfers.
Mail merge from Excel to Word, step by step
The Excel to Word route is the one most people mean when they ask how to do mail merge from Excel to Word. It is also the one that produces the most support threads, almost always because of the spreadsheet rather than the document.
Prepare the spreadsheet before you open Word
Put the data on the first sheet of the workbook. Give every column a single, short header row: FirstName, LastName, Company, Email. Remove blank rows and blank columns, because a blank row becomes a blank merged record and a blank column becomes a field you cannot map.
Split names into separate columns. A single Name column forces a full name greeting, which reads like a form letter.
Fix formats in Excel, not in Word. Dates, currency and postal codes are the three that break: a postal code beginning with a zero is stored as a number, and the leading zero disappears the moment it is merged. Format that column as text before you connect it.
Build the main document
In Word, open the Mailings tab. Use Start Mail Merge to pick the output type, then Select Recipients to connect the workbook you just cleaned. If you prefer to be walked through it, the same tab offers a step by step mail merge wizard that asks the same questions in order.
Insert your placeholders with Greeting Line for the salutation and Insert Merge Field for everything else. A field shows as its name in angle brackets until you preview. This is the part of mail merge in MS Word that people get wrong by typing the field name manually: typed text is text, and it will print literally on all four hundred copies.
Preview, then finish
Preview Results swaps placeholders for real values and lets you page through records. Check record one, the last, and any row you know is messy. Finish and Merge produces the output.
One check that catches most problems
Merge to a new document first, even when your goal is email. One file, one page per recipient: the fastest way to spot an empty field, a broken date or a row that should never have been in the list. Nothing has been sent, so nothing has to be apologised for.
Mail merge to email through Outlook
A mail merge Outlook job is the same Word document with a different ending. In Start Mail Merge you choose E-mail Messages instead of Letters, build the body the same way, and at Finish and Merge you select Send E-mail Messages.
The dialog that opens asks for three things: the To box, where you pick the column holding email addresses; the Subject line, which you type; and the Mail format, which defaults to HTML and can be set to plain text. You can also send all records, the current record, or a numbered range, which is the safest way to run a test of five before committing the rest.
Three limitations are documented and none of them have workarounds inside Word. Word sends an individual message to each address, so you cannot CC or BCC anyone. You cannot attach files, although links in the body work normally. And the merge needs a MAPI compatible mail program, in practice Outlook, installed and configured on the same machine.
The attachment limitation is what sends people looking for add-ins, though a link to a hosted file is often the better answer: smaller, harder to filter, and measurable. If timing matters too, the mechanics and failure modes of delayed delivery in Outlook apply to a merged batch as much as to a single message.
One thing a merge cannot give you is a second chance. Each message goes to a separate recipient the instant it is generated, so the narrow conditions under which recall actually works almost never apply. Preview is your only real safety net.
Mail merge in Gmail and Google Sheets
There are three distinct routes for a mail merge Gmail job, and they are not interchangeable.
The built in feature. Google Workspace includes mail merge directly in the Gmail compose window on Workspace Individual, Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Standard and Education Plus. You compose as normal, turn on mail merge, and use the placeholders Google provides: @firstname, @lastname, @fullname and @email. Values come from Google Contacts or from spreadsheet column headers.
Personal Gmail accounts do not have it. If the option is missing, the account type is almost always the reason.
Apps Script. Google publishes a mail merge sample that reads rows from a Google Sheet and sends through the account’s own Gmail. It costs nothing, it handles arbitrary column names rather than four fixed placeholders, and it is the honest answer to whether there is a free mail merge for a personal account. It also requires you to be comfortable pasting and authorising a script.
Add-ons. The Workspace Marketplace carries established merge tools that add tracking, attachments and scheduling. They are third party code with access to your mailbox, so treat the permission screen as a real decision.
Whichever route you take, sending happens through the account’s normal outbound path, so the SMTP and IMAP configuration behind a Workspace mailbox is what a script or add-on is ultimately using.
The recipient limits that cap the job
This is the section missing from most tutorials. Your merge does not fail because the document is wrong. It stops because the mailbox refuses to keep sending.
| Platform | Documented limit |
|---|---|
| Gmail built in mail merge | Up to 1,500 recipients per message and 1,500 recipients per day |
| Exchange Online recipient rate limit | 10,000 recipients per day, per user, across outbound and internal mail |
| Exchange Online recipient limit | Customisable from 1 to 1,000 recipients in the To, Cc and Bcc fields of one message |
| Exchange Online message rate limit | 30 messages per minute submitted from one account |
The message rate limit is the one that ambushes a Word merge. Word submits messages as fast as Outlook accepts them, and a merge of a few hundred rows will run past thirty per minute without difficulty. Messages submitted over that ceiling through SMTP client submission are rejected and have to be retried by the client, which is why a large merge can finish in Word and arrive incomplete.
These are recipient limits, not message limits. A merge sends one message per row, so a thousand row list consumes a thousand recipients against the daily cap.
Why merged email lands in spam
A merge produces hundreds of near identical messages leaving one mailbox in a short window. That is, structurally, exactly what a bulk campaign looks like to a receiving filter, minus every signal a real campaign carries.
Three differences do the damage. A merged batch from a desktop client carries no List-Unsubscribe header, so recipients who want out reach for the spam button instead; the header that gives them a one click way out is trivial for a sending platform to add and impossible to add from inside Word. The bodies are near identical, a stronger pattern than most people expect. And the list has usually never been cleaned, so bounces arrive in a cluster.
If the list came out of a CRM export or a signup form nobody has audited, running it through a list cleaning pass before the first send removes most of that risk in one step. The full set of reasons legitimate mail gets filtered covers the rest, and a merged batch trips several of them at once.
When to stop merging and use a relay
Mail merge is the right tool for a bounded, occasional, genuinely personal send: invoices, invitations, a note to forty customers. It is the wrong tool the moment any of these become true.
You are sending the same thing repeatedly on a schedule. You need open and click data to decide anything. You need unsubscribes handled and recorded rather than replied to by hand. Or the list is large enough that a daily recipient cap decides your timeline.
At that point the job is a campaign, and the question changes from which client to which sending path. Relay services built for volume sending supply the unsubscribe handling, bounce processing and reputation separation a personal mailbox cannot, and they keep campaign volume off the mailbox you use for real correspondence.
Merge failures you will actually hit
Field names print instead of values. The placeholder was typed rather than inserted, or Preview Results is switched off. Delete the text and use Insert Merge Field.
Numbers, dates and currency arrive mangled. Word takes the underlying value, not what Excel displays. Fix the format in the source column, or add a numeric picture switch to the field in Word.
Leading zeros vanish from postal codes and account numbers. The column is numeric. Format it as text in the spreadsheet before connecting.
Only the first record merges. The output was set to current record rather than all, or the merge was previewed rather than finished.
Nothing sends. Outlook is not the default mail program, is not running, or a security prompt is waiting behind another window for permission to send on your behalf.
Merged email looks broken on arrival. Word writes HTML no email designer would write, and an elaborate signature is the first thing to collapse. Keep the body plain enough to survive a client rewriting the markup.
If you are choosing between clients before you start, the directory of desktop, web and mobile mail clients lists which ones expose a merge feature natively and which need an add-on.
Mail merge FAQ
How do you do a mail merge?
Prepare a spreadsheet with one row per recipient and one clean header row. In Word, open the Mailings tab, choose Start Mail Merge and the output type, then Select Recipients and point at the spreadsheet. Insert merge fields where personalised values belong, check Preview Results, then Finish and Merge.
What is the purpose of mail merge?
To produce many personalised copies of one document without editing each one. You proofread a single template instead of four hundred files, which removes most of the opportunity for error. Mail merge letters, labels, envelopes and individually addressed email all come from the same mechanism.
How do I do a mail merge in Outlook?
You start it in Word, not in Outlook. Choose E-mail Messages under Start Mail Merge, build the body with merge fields, then use Finish and Merge, Send E-mail Messages. Word asks for the address column, a subject line and a mail format, then hands each message to Outlook.
Is there a free mail merge?
Yes, two of them. Word plus Outlook costs nothing extra if you already have Microsoft Office. For Gmail, Google publishes an Apps Script sample that reads a Google Sheet and sends through your own account. Paid add-ons buy tracking, attachments and scheduling, not the merge itself.
Why do I not have a mail merge option in Gmail?
The built in feature ships with specific Google Workspace editions only. Personal Gmail accounts and the lower Workspace tiers do not have it, and no setting turns it on. Apps Script or an add-on is the alternative.
Can you add an attachment to a mail merge in Word?
No. Microsoft documents this explicitly: each message goes to one address, you cannot CC or BCC, and you cannot attach files. Links in the body do work. If attachments are essential, you need an add-in or a sending platform rather than Word on its own.
How many emails can I send with a mail merge?
Fewer than the merge will generate. Gmail’s built in mail merge allows up to 1,500 recipients per message and 1,500 per day. Exchange Online applies 10,000 recipients per day per user, up to 1,000 per message, and 30 messages per minute. The rate limit, not the daily cap, is what usually truncates a large Word merge.
About this guide
Merge mechanics and UI labels follow Microsoft’s documentation for Word and Google’s for Gmail. Sending limits are quoted from the Exchange Online service description and Gmail Help; no figure here is estimated. Deliverability guidance describes a personal mailbox sending bulk volume, which behaves differently from a dedicated sending platform. Reviewed by the SMTPedia editorial team.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
