Fix Power Automate Word Connector Error When Inserting SharePoint Images
Question details
The user needs to resolve an issue where Power Automate fails to insert multiple Base64-converted SharePoint images into a Word template report.
- Product
- Power Automate, Microsoft Word, SharePoint
- Device & OS
- not provided
- Scenario
- Automating the creation of a Word report using data and multiple images submitted via Power Apps and stored in SharePoint.
- Observed behavior
- The Word connector rejects the Base64 converted image data, returning an error stating that a valid PNG or JPG file is required.
Ensure you have the correct permissions to access the SharePoint document library and that your Microsoft Word template is saved with Picture Content Controls properly configured.
Troubleshoot Base64 Conversion and Word Picture Controls
Verify your file content conversion process and consult the Power Automate community for advanced array handling.
The issue typically occurs because the 'Populate a Microsoft Word template' action requires a specific binary format or properly formatted Base64 string for Picture Content Controls. When handling multiple images, the array mapping from SharePoint to the Word connector must strictly align with the connector's schema requirements.
Verify that the file content fetched from SharePoint is a valid image (PNG/JPG). Use the 'Get file content' action in Power Automate to retrieve the binary data properly.
Ensure the expression used for conversion uses the base64() function directly on the file content. Check that you are not incorrectly passing or omitting the data URI scheme prefix (e.g., 'data:image/png;base64,') if your specific workflow configuration expects a raw string.
Open your Word template, enable the Developer tab, and verify that the image placeholders are strictly set as 'Picture Content Controls'. For multiple images, ensure they are wrapped in a 'Repeating Section Content Control'.
Because handling multiple images in arrays involves complex JSON schema mapping, it is highly recommended to post your flow details (SharePoint column type, conversion expressions) to the official Power Automate Community forums for specialized support.
Create and Edit Professional Documents Seamlessly with WPS Office
While automated workflows can sometimes lead to complex troubleshooting with Microsoft connectors, you can simplify your everyday document editing and report creation with WPS Office. It provides a lightweight, highly compatible, and user-friendly environment for managing documents, images, and reports without steep subscription costs.
- 1. Download the Installer: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the on-screen prompts to complete the setup process in minutes.
- 3. Open Your Documents: Launch WPS Writer and easily open your existing .docx files to insert and arrange your images without formatting errors.

Frequently Asked Questions
Why does Power Automate say the image needs to be a valid PNG or JPG?
This error occurs when the 'Populate a Microsoft Word template' action receives an improperly formatted Base64 string, an unsupported image format, or corrupted file content fetched from SharePoint.
How do I add a Picture Content Control in Word for Power Automate?
Open Microsoft Word, navigate to the Developer tab, place your cursor where you want the image, and click the 'Picture Content Control' icon. You must also assign it a Title and Tag in the Properties menu so Power Automate can recognize and map data to it.
Can I insert multiple images dynamically into a Word template using Power Automate?
Yes, but it requires wrapping your Picture Content Control inside a Repeating Section Content Control in Word. You must then format your Power Automate data as an array of objects that accurately match the repeating section's schema.
Does the base64() expression automatically make SharePoint images compatible with Word?
Not always. You must ensure you are passing the actual 'File Content' dynamic value into the base64() function. Depending on the connector version, you may also need to structure the output explicitly into the $content-type and $content JSON format expected by Word.




