How to Mail Merge Word Documents With Embedded Charts per Recipient

Creating personalized documents with unique charts for each recipient is a common need for business reports, invoices, or performance summaries. The standard mail merge in Word can insert text and images, but it does not directly support embedding a different chart per recipient. This limitation exists because Word treats charts as static objects linked to a single data source rather than dynamic fields that update per merge record. This article explains how to use Word’s mail merge fields combined with a separate chart-generation step to produce one document per recipient with a unique embedded chart. You will learn the exact steps to prepare your data, generate the charts, and merge them into final documents.

How Mail Merge Handles Embedded Charts: The Core Limitation

Word’s mail merge engine can insert text fields, images, and even OLE objects from a data source. However, a chart inserted via the Insert > Chart command is a static object that uses a single Excel data sheet stored inside the Word document. When you run a mail merge, this chart does not update its data per recipient. The chart remains identical in every merged copy.

To achieve a different chart for each recipient, you must bypass the built-in chart object and instead use a placeholder that points to an external image file. The image file itself must be a chart rendered outside Word, such as in Excel, a BI tool, or a script. The key is to name each chart image file with a unique identifier that matches a field in your mail merge data source, such as CustomerID or InvoiceNumber.

Prerequisites for This Method

Before starting, ensure you have the following:

• A data source (Excel sheet, Access database, or CSV) with one row per recipient. The data source must include a column that contains the full file path to each recipient’s chart image. For example, a column named ChartPath with values like C:\Charts\Invoice_1001.png.
• All chart image files saved in a folder that Word can access. Use a consistent naming convention that matches the identifier in your data source.
• Word for Microsoft 365 or Word 2021. Older versions support INCLUDEPICTURE but may handle file paths differently on network drives.

Steps to Generate Recipient-Specific Charts and Merge Them Into Word

Follow these steps to create the chart images, set up the merge document, and produce the final personalized files.

1. Step 1: Prepare the chart images for each recipient
   Open Excel and create a chart for one recipient using their data. Right-click the chart area and select Save as Picture. Save the file as a PNG with a name that includes a unique identifier from your data, such as Invoice_1001.png. Repeat this step for every recipient. You can automate this by recording a macro in Excel or using a script in Python with openpyxl and matplotlib to export all charts at once.
2. Step 2: Add a chart path column to your data source
   Open your data source (for example, an Excel sheet). Add a new column named ChartPath. In each row, type the full file path to the corresponding chart image. Example: C:\Charts\Invoice_1001.png. Save and close the data source.
3. Step 3: Create the main Word document for the merge
   Open Word and create a new blank document. Design the layout for your merged output, leaving space where the chart will appear. Do not insert an actual chart object.
4. Step 4: Insert the INCLUDEPICTURE field with a merge field
   Place your cursor where the chart should appear. Press Ctrl+F9 to insert an empty field code. Inside the braces, type: INCLUDEPICTURE “{ MERGEFIELD ChartPath }” \d. The \d switch tells Word to use the image data stored in the field result rather than linking to the file path each time the document is opened. Your field code should look like: { INCLUDEPICTURE “{ MERGEFIELD ChartPath }” \d }. Press F9 to update the field. If Word displays an error, ignore it for now; the path will resolve during the merge.
5. Step 5: Add other mail merge fields as needed
   Insert any other merge fields for text data, such as name, address, or invoice amount. Use Mailings > Insert Merge Field to add them.
6. Step 6: Connect the document to your data source
   Go to Mailings > Select Recipients > Use an Existing List. Browse to your Excel file or CSV and select the sheet that contains your data. Confirm that the ChartPath field appears in the merge field list.
7. Step 7: Preview and complete the merge
   Click Mailings > Preview Results. Word will display the first recipient’s record. The INCLUDEPICTURE field should show the corresponding chart image. If the image does not appear, press F9 to update the field. Once preview works correctly, go to Mailings > Finish & Merge > Edit Individual Documents. Select All and click OK. Word creates a new document with one page per recipient, each containing the correct chart image.
8. Step 8: Save or print the merged document
   Save the new document as a single file with all pages, or use Mailings > Finish & Merge > Print Documents to print directly.

Common Problems and How to Solve Them

The chart image does not appear after the merge

This usually happens because the file path in the ChartPath column is incorrect or the image file is missing. Verify that the path exists and that Word has read permissions for the folder. If you are on a network drive, use a mapped drive letter instead of a UNC path. Also ensure the \d switch is present in the INCLUDEPICTURE field; without it, Word may show a broken link icon.

Word shows a large placeholder instead of the chart

The INCLUDEPICTURE field may display a gray box or a text error like “Error! File not found.” Right-click the field and select Toggle Field Codes to check the syntax. The field should be exactly: { INCLUDEPICTURE “{ MERGEFIELD ChartPath }” \d }. If the inner MERGEFIELD field is missing quotes, add them. After correcting, press F9 to update.

The chart image is distorted or too small

The INCLUDEPICTURE field inserts the image at its original resolution. To control the size, resize the image placeholder in the main document before merging. Right-click the placeholder, select Size and Position, and set exact dimensions. The image will scale to fit that frame during the merge. To maintain aspect ratio, lock the aspect ratio in the Size tab.

The merge runs but every page shows the same chart

This occurs when the INCLUDEPICTURE field is not linked to the MERGEFIELD field correctly. Check that the inner field is a MERGEFIELD and not a plain text placeholder. Also confirm that the ChartPath column in your data source contains unique file paths for each row. Duplicate paths will cause identical charts.

Comparison: INCLUDEPICTURE With Merge Field vs Insert Chart Object for Per-Recipient Output

Item	INCLUDEPICTURE + Merge Field	Insert Chart Object (Standard)
Chart per recipient	Yes, each recipient gets a unique chart image	No, all recipients get the same chart
Data source requirement	Column with file path to each chart image	No special column needed
Chart creation effort	Must create one image file per recipient before merge	Chart is created once in Word
File size of merged document	Larger because each chart is embedded as an image	Smaller because one chart is shared
Dynamic updates	Static image; chart does not update if source data changes	Static chart; data is stored in the document
Supported Word versions	Word 2013 and later, including Word Online (limited)	All versions with chart support

Use INCLUDEPICTURE with a merge field when you need a distinct chart per recipient and can generate the chart images beforehand. Use the standard chart object when the same chart is acceptable for all recipients, as it requires less preparation.

You can now produce personalized Word documents with a unique embedded chart for each recipient using the INCLUDEPICTURE field and a merge field for the file path. Next, consider automating the chart export step with an Excel macro to save time when dealing with hundreds of recipients. For advanced control, use the \d switch to embed the image data directly into the document so the charts remain visible even if the source folder is moved.