Skip to main content

Convert PDF to Word in Power Automate

What this action does

PDF4me Convert PDF to Word transforms PDF documents into fully editable Microsoft Word (.docx) files inside your Power Automate flow. Preserves layout, tables, images, fonts, and hyperlinks. Choose Draft mode for fast native-PDF conversion (1 API call per file) or High mode with AI OCR for scanned documents in 8+ languages (2 API calls per page). Replace manual SmallPDF, iLovePDF, or Adobe Acrobat uploads with a single automated action that chains directly into SharePoint, Outlook, Teams, Dynamics 365, and any Microsoft 365 workflow.

Related Blog Posts
No blog post yet for this feature — coming soon.
In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.
Visit the blog

Authenticating Your API Request

Every PDF4me action in Power Automate requires a valid PDF4me connection. Create one with your API key the first time and Power Automate reuses it across all PDF4me actions in your flows.

Important Facts You Should Not Miss

Draft vs High, pick the right mode for cost and accuracy
Draft uses 1 API call per file, ideal for native PDFs with selectable text (5-10× cheaper at scale). High uses 2 API calls per page with full OCR and layout reconstruction, required for scanned PDFs, multi-column layouts, or image-heavy documents. Match the mode to your source.
Output is a true editable DOCX, tables become native Word tables
Text remains selectable and editable; images become resizable shapes; tables become native Microsoft Word tables. Unlike image-style "PDF to Word" converters, the result is a clean DOCX your team can edit, restyle, redline, and integrate with mail merge.
Output is .docx (Office Open XML), not legacy .doc
The action produces the modern .docx format with MIME type application/vnd.openxmlformats-officedocument.wordprocessingml.document, fully compatible with Word 2007+, Word for Web, Word for Mac, Microsoft 365, Google Docs, and LibreOffice.
Power Automate PDF4me Convert PDF to Word action showing File Content mapped from a previous Get file content step, File Name with .pdf extension, and Quality Type set to Draft for native PDFs or High for scanned documents

Map File Content and File Name from a prior step, choose Quality Type (Draft for native PDFs, High for scanned), and run, the editable DOCX is returned in the output.

Parameters

Required: File Content, File Name, and Quality Type must all be provided. The action cannot convert without a binary source PDF and a quality selection.

ParameterRequiredWhat it doesExample
File ContentYesBinary content of the source PDF file. Map from any prior action that returns file bytes: SharePoint Get file content, OneDrive Get file content, Outlook email attachment, Forms file upload, HTTP Request, or Get file content using path.File Content (binary)
File NameYesFilename of the source PDF including the .pdf extension. Used for identification during processing and to derive the default output filename (replacing .pdf with .docx). Map dynamically from prior step variables.contract-2026.pdf
Quality TypeYesConversion quality mode. Draft for native born-digital PDFs (1 API call per file, fast and cost-efficient). High for scanned PDFs, image-based PDFs, or complex multi-column layouts (2 API calls per page with OCR and layout reconstruction).Draft

Quality Type Options

DraftDefault, fast, 1 API call per file
Best for native born-digital PDFs with selectable text, Word exports, Google Docs PDFs, browser print-to-PDF, InDesign output, accounting and BI tool PDFs. Returns a usable DOCX in seconds. 5-10× more cost-efficient at scale than High mode.
HighAccurate, 2 API calls per page with OCR
Required for scanned PDFs, photographed pages, multi-column academic layouts, or any PDF where Draft produces misaligned text. Applies AI OCR + layout reconstruction. Supports English, German, French, Spanish, Italian, Portuguese, Dutch, Polish OCR.

Output Fields

FieldTypeWhat it contains
File ContentBinaryConverted DOCX file as binary content. Map directly into downstream actions: SharePoint Create file, OneDrive Create file, Outlook Send an email attachment, Teams Post a message with attachment, or Word Online (Business) for editing.
File NameStringOutput filename of the generated Word document (e.g. contract-2026.docx). Derived from the input File Name with the .pdf extension replaced by .docx. Use directly as the filename in SharePoint or OneDrive Create file actions.

Quick Setup

  1. In your Power Automate flow, click + New step and search for PDF4me.
  2. Select the Convert PDF to Word action from the PDF4me Connect connector.
  3. Choose your PDF4me connection or click Add new connection with your API key.
  4. Map File Content to the binary output of a previous action: typically Get file content (SharePoint), Get file content using path (OneDrive), Outlook email attachment, or HTTP Response body.
  5. Set File Name dynamically from the prior step (must include .pdf extension): e.g. triggerOutputs()?['body/Name'].
  6. Choose Quality Type:
  • Draft for native PDFs (Word exports, browser print, BI reports): fast and cost-efficient.
  • High for scanned PDFs, photographed pages, or multi-column layouts, applies OCR + AI reconstruction.
  1. Save the flow and test with a sample PDF.
  2. Connect the output File Content to your next action: SharePoint Create file, OneDrive Create file, Outlook attach to email, Teams post with attachment, or Word Online for inline editing.

Workflow Examples

Workflow ExamplesCommon Power Automate flow patterns using Convert PDF to Word.
Counterparty contract PDF → editable Word → legal redlining
  1. An Outlook trigger fires when an email arrives from a known counterparty domain with a PDF contract attachment.
  2. Convert PDF to Word runs with Quality Type = Draft (counterparty contracts are typically native PDFs).
  3. The resulting DOCX is uploaded to a SharePoint "Contracts In Review" library with the original filename pattern.
  4. A Microsoft Teams Adaptive Card notifies the legal team with a link to the editable Word file, they redline directly in Word Online with Track Changes enabled.
  5. A Dataverse row captures the contract metadata (counterparty, received date, reviewer assigned) for the contract lifecycle dashboard.
Scanned legal archive → OCR Word → searchable SharePoint
  1. A SharePoint trigger fires when a new scanned PDF lands in a "Legacy Documents to Digitize" library.
  2. Convert PDF to Word runs with Quality Type = High (scanned source, OCR required).
  3. The OCR-extracted DOCX contains fully selectable, searchable text, paragraphs, tables, and headings are reconstructed from the scanned image.
  4. The DOCX is uploaded to the "Digitized Archive" SharePoint library, where SharePoint's built-in indexing makes it full-text searchable across the entire organization.
  5. An email notification confirms successful digitization to the records-management team with the original scan filename and conversion timestamp.
Bulk PDF report library → DOCX templates → mail merge ready
  1. A scheduled flow runs nightly over a "Source PDFs" SharePoint library containing template-source reports from third-party tools.
  2. For each new PDF, Convert PDF to Word runs with Quality Type = Draft to produce an editable DOCX template.
  3. A second action runs Find and Replace on the DOCX to swap static placeholders with mail merge field markers (e.g. {{CustomerName}}, {{InvoiceTotal}}).
  4. The template-ready DOCX is filed in a "Templates" SharePoint library, organized by report category, ready for downstream Word mail-merge or document-generation flows.
  5. A Power BI dashboard tracks template-creation throughput; legal and finance teams reuse the templates without rebuilding from scratch each quarter.

Frequently Asked Questions

What's the difference between Draft and High quality in Convert PDF to Word?+
Draft mode is the fast path: one API call per file, designed for native born-digital PDFs with selectable text such as Word exports, Google Docs PDFs, browser print-to-PDF, accounting software output, and BI tool reports. It returns a usable DOCX in seconds and is the right choice for the vast majority of modern PDFs. High mode uses two API calls per page and applies AI-powered OCR plus layout reconstruction, designed for scanned PDFs, photographed pages, image-based PDFs, or any PDF where Draft produces missing text, misaligned tables, or character recognition errors. Use Draft for native PDFs and High when the source originated on paper or as a flat image.
Does the converted Word file preserve formatting, tables, fonts, and images?+
Yes. PDF4me retains visual fidelity of the source document. Page layout, embedded images, font sizes, colors, alignment, hyperlinks, and tables are all reconstructed in the DOCX as native Microsoft Word elements rather than flat images. Tables become editable Word tables you can resize and reformat; images become resizable shapes; text remains selectable, searchable, and editable. Font substitution may occur if a custom PDF font is unavailable on the editing system, but standard fonts like Calibri, Arial, Times New Roman, and Cambria are preserved exactly. For maximum fidelity, ensure source PDFs use fonts available on the systems where the DOCX will be edited.
Can I convert scanned or image-based PDFs to editable Word documents?+
Yes. Set Quality Type to High to apply AI-powered OCR over each page. The action extracts text, reconstructs document structure (paragraphs, headings, tables, lists), and produces a DOCX where the formerly image-based text is now selectable, copyable, and editable in Microsoft Word. OCR supports English, German, French, Spanish, Italian, Portuguese, Dutch, Polish, and other major business languages without any extra configuration. Ideal for digitizing legacy contracts, scanned archives, photographed receipts, historical document libraries, and any paper-origin content that needs to flow into modern Microsoft 365 editing workflows.
How does this compare to manual SmallPDF, iLovePDF, or Adobe Acrobat conversion?+
Online tools like SmallPDF, iLovePDF, Adobe Acrobat online, Nitro PDF, Soda PDF, and Zamzar require manual file upload one PDF at a time with daily free-tier limits (typically 2-3 conversions per day on free tier) or paid subscriptions starting around $9-20/month per user. The PDF4me Power Automate action automates the same conversion at scale: triggered by SharePoint file uploads, Outlook email attachments, Microsoft Teams messages, Forms responses, OneDrive folder changes, or scheduled batch flows, and chains directly into downstream Microsoft 365 actions including Word Online editing, Teams approval workflows, SharePoint metadata updates, Dataverse logging, and Dynamics 365 record attachments. Use this when you process dozens to thousands of PDFs per month consistently rather than one-off ad-hoc conversions.
What output format does the action produce: .docx or legacy .doc?+
The output is always the modern Microsoft Word .docx format (Office Open XML standard, ECMA-376 / ISO 29500). This is fully compatible with Microsoft Word 2007 and later, Word for Web, Word for Mac, Microsoft 365 (Office 365), Google Docs (with conversion), LibreOffice Writer, Apple Pages, and all major word processors. The legacy binary .doc format is not produced. The DOCX file ships with proper MIME type application/vnd.openxmlformats-officedocument.wordprocessingml.document for correct handling by SharePoint, Outlook, Microsoft Teams, OneDrive, and any HTTP-based downstream system. The output also enables Word features that .doc does not support: themes, content controls, comments threading, and modern accessibility tags.

Same Task on Other Platforms

Get Help