How to Insert a PDF into OneDrive Word (w/Examples) + FAQs

Yes, you can insert a PDF into a Word document stored in OneDrive, and you have at least five reliable ways to do it depending on whether you want the PDF to appear as an icon, a picture, an editable block of text, or a clickable cloud link. The right method depends on your version of Word, your OneDrive plan, and the legal or compliance rules that apply to the PDF you are embedding.

The friction comes from a mix of Microsoft 365 service descriptions, OneDrive sync rules, and federal privacy laws like the HIPAA Security Rule, FERPA, and the GLBA Safeguards Rule. Each of these frameworks shapes how you may embed a PDF, where the file may live, and who may open it.

According to a 2025 Microsoft adoption report, more than 1.4 billion people use Microsoft 365 worldwide, and Adobe estimates that over 400 billion PDFs were opened in Acrobat and Reader in 2023 — making PDF-to-Word embedding one of the most common cloud workflows in the modern office.

Here is what you will learn:

• 📎 The five supported ways to insert a PDF into a Word file synced to OneDrive
• 🖥️ How the steps change across Word desktop, Word for the web, and Word mobile
• ⚖️ How HIPAA, FERPA, GLBA, and eDiscovery rules limit what you may embed
• 🛠️ How to fix the most common errors, sync conflicts, and “Word can’t insert this PDF” messages
• 🧠 Real, named-person scenarios that show the right and wrong way to embed a PDF

What “Inserting a PDF into OneDrive Word” Actually Means

When people say they want to insert a PDF into a OneDrive Word document, they usually mean one of three different things, and mixing them up is the single biggest source of frustration. The first meaning is embedding the PDF inside the .docx file so the PDF travels with the Word document. The second meaning is linking to a PDF that lives in OneDrive so the Word file stays small and the PDF stays current. The third meaning is converting the PDF into editable Word text so the content becomes part of the document body.

Each path has different consequences for file size, version control, and legal discovery. An embedded PDF inflates the .docx and creates a frozen copy that may go stale. A linked PDF keeps the document light but breaks if the OneDrive path changes. A converted PDF becomes searchable Word text but loses original formatting and any digital signatures the PDF carried.

A common misconception is that Word for the web behaves the same as Word desktop. It does not. The browser version of Word, documented in the Word for the web service description, supports a smaller set of insertion options than the installed desktop app, and the Word mobile app feature list is smaller still.

The Three Core Outcomes

The first outcome is a static embed, where the PDF sits inside the Word file as an OLE object or as a flattened image. The second outcome is a live link, where Word stores only a URL pointer to the OneDrive copy of the PDF. The third outcome is a content extraction, where Word imports the PDF text and lays it out as native Word paragraphs.

Choosing the wrong outcome creates real consequences. A static embed of a 90 MB engineering PDF can push the .docx past the SharePoint and OneDrive 250 GB single-file limit only in extreme cases, but it routinely breaks email gateways with 25 MB caps. A broken live link in litigation can trigger a Federal Rule of Civil Procedure 37(e) spoliation motion. A content extraction of a signed PDF strips the digital signature governed by the federal ESIGN Act.

For example, Maria, a paralegal in Dallas, embedded a 60 MB exhibit PDF into a brief and could not email it to opposing counsel. She switched to a OneDrive shared link inside the brief and the file shrank from 62 MB to 180 KB.

Why OneDrive Changes the Equation

OneDrive is not just a storage drive. It is a sync engine, a permissions broker, and a co-authoring backbone, all described in the OneDrive technical overview. When a Word file lives in OneDrive, every PDF you embed or link must obey OneDrive’s permissions, sync rules, and retention policies.

The consequence is that an embedded PDF inherits the Word file’s sharing scope, while a linked PDF keeps its own separate scope. If you share the Word file with a vendor but the linked PDF is locked to your internal team, the vendor sees a broken-link icon. A common misconception is that “share the Word file” automatically shares attached files. It does not, unless the PDF is fully embedded as an object.

For example, David, an HR manager in Atlanta, linked an offer-letter PDF inside a Word onboarding packet. He shared the packet with a new hire who could not open the PDF because the link still required corporate sign-in.

Method 1: Insert as Object (Embed the Whole PDF)

The Insert as Object method places the entire PDF inside the .docx file as an icon or as the first page preview, using Microsoft’s Object Linking and Embedding standard described in the OLE documentation. This is the closest you can get to a traditional “attach a PDF inside a Word file” workflow. The PDF travels with the Word file forever, even when the recipient is offline.

The plain-English explanation is simple. Word treats the PDF as a foreign object, stores its bytes inside the .docx package, and shows either an Adobe Reader icon or a thumbnail of page one. Double-clicking the icon opens the PDF in the user’s default PDF viewer. The consequence of using this method is a much larger Word file and a frozen copy of the PDF that will not update if the source PDF changes.

A real-world example: Priscilla, a compliance officer in Boston, embeds a vendor’s signed SOC 2 report inside her annual risk memo so auditors always see the exact version that was reviewed. A common misconception is that the embedded PDF stays editable inside Word. It does not. It is a sealed copy that opens only in an external viewer.

Step-by-Step in Word Desktop

Open the Word file from your OneDrive folder, place the cursor where you want the PDF to appear, and click the Insert tab on the ribbon. Click Object in the Text group, choose Create from File, and click Browse. Select the PDF, check Display as icon if you want a small icon instead of a page preview, and click OK. The full sequence matches the official Microsoft Word insert object guide.

A nuance worth noting is that Word desktop on macOS shows the same dialog but labels the icon checkbox slightly differently. Another nuance is that Display as icon uses the system’s PDF icon, not Adobe’s branded icon, unless Adobe Acrobat is installed and registered as the default handler. The consequence of skipping the icon checkbox is a Word page that suddenly displays only the first page of a 200-page PDF, which confuses readers.

Step-by-Step in Word for the Web

Word for the web does not support full PDF object embedding. The browser app, per the Word for the web limits page, only supports inserting a PDF as a picture or as a link. If you must embed the PDF as an object, open the file in the desktop app by clicking Editing, then Open in Desktop App.

The consequence of trying to force an object embed in the browser is a silent failure or a “feature not supported” toast. A common misconception is that Open in Desktop App changes which copy of the file you are editing. It does not. You are still editing the OneDrive copy through co-authoring, just with the desktop ribbon.

Step-by-Step in Word Mobile

In the Word mobile app on iOS and Android, tap Insert, tap Object, and choose the PDF from OneDrive or your device. The mobile app supports embedding small PDFs but throws a memory error on files larger than roughly 50 MB on most phones, which is consistent with the Word for Android support notes.

The consequence of mobile embedding is that the PDF icon may render as a generic file glyph until the document is opened on a desktop. A common misconception is that mobile embeds compress the PDF. They do not. The full byte stream is stored inside the .docx.

Method 2: Insert as Picture (Flatten the PDF)

The Insert as Picture method converts each page of the PDF into a flat image and drops it into Word as a static graphic. This is the right choice when you want the PDF to display inside Word without the recipient needing a PDF viewer. It is also the right choice when you want to annotate or crop a single PDF page like a screenshot.

The plain-English explanation is that Word, working with the Windows or macOS PDF rendering engine, rasterizes the PDF page into a PNG-equivalent image. The consequence is that the text inside the image is no longer searchable, selectable, or screen-reader-friendly. A common misconception is that this method preserves vector text. It does not. The output is a bitmap.

For example, Jamal, a marketing director in Chicago, drops a one-page product spec PDF into a Word proposal as a picture so the layout looks identical to the original brochure. A real-world consequence is that he loses the ability to copy the spec text out of Word, which his designer later flags as an accessibility violation under the ADA Title III digital guidance.

Two Reliable Picture Workflows

The first workflow uses Word’s built-in Insert > Pictures > This Device after you export each PDF page to PNG using the free tools described in the Adobe Acrobat export PDF help. The second workflow uses the Windows Snipping Tool or Shift + Command + 4 on macOS to capture and paste pages directly.

The consequence of choosing the screenshot route is a fast result with low fidelity. The consequence of choosing the export-then-insert route is higher fidelity but more steps. A common misconception is that Word’s Insert > Screenshot feature can grab a PDF that is open in Acrobat. It can, but only if the Acrobat window is not minimized.

Accessibility and Compliance Notes

Inserting a PDF as a picture creates a real accessibility problem under Section 508 of the Rehabilitation Act when the document is produced for a federal agency. The consequence of shipping a Word file with image-only content and no alt text is a failed conformance review and a possible contract rejection. A common misconception is that adding alt text fixes the issue. It helps screen readers but still fails reflow and text resize requirements under WCAG 2.1 Level AA.

For example, Linda, a contracts officer in Washington, D.C., loses a federal task order because her bid response embedded the technical approach as a flattened PDF image. She rebuilds the document using Method 5 below and wins the next bid.

Method 3: Convert PDF to Editable Word Content

The Convert and Insert method opens the PDF directly in Word, lets Word’s built-in converter re-flow the text into editable paragraphs, and then lets you copy the result into your OneDrive Word document. Microsoft documents this feature in the Edit PDF content in Word article.

The plain-English explanation is that Word performs a structural conversion, mapping PDF tables to Word tables, PDF headings to Word headings, and PDF body text to Word paragraphs. The consequence of using this method is that the text becomes fully editable, searchable, and screen-reader-friendly, but the visual fidelity drops. A common misconception is that conversion is lossless. It is not. Forms, signatures, and complex layouts often break.

For example, Carlos, a small-business owner in Phoenix, converts a vendor’s PDF contract into Word so he can redline terms before signing. He loses the original page numbering and footer formatting, which he restores manually before sending the redline back.

When Conversion Is the Right Call

Conversion is the right call when the PDF is mostly text, when you need to edit or quote the content, or when the recipient must read the text inside the Word body. Conversion is the wrong call when the PDF carries a digital signature governed by the ESIGN Act or the Uniform Electronic Transactions Act, because conversion strips the cryptographic seal.

The consequence of converting a signed PDF is the loss of legal non-repudiation. A common misconception is that re-signing the converted Word file restores the original signature. It does not. The original signer’s intent and timestamp are gone forever.

Conversion Limits in OneDrive Word

Word for the web does not perform PDF-to-Word conversion. You must use the desktop app or the Microsoft 365 PDF converter in OneDrive which opens the PDF in a temporary Word view.

The consequence is that mobile users cannot convert PDFs in place and must rely on a desktop or web teammate. A common misconception is that the conversion happens locally on the phone. It does not. It happens on Microsoft’s cloud rendering service.

Method 4: Link to a PDF Stored in OneDrive

The Link to PDF method inserts a clickable hyperlink to the PDF that lives in OneDrive, leaving the Word file lean and the PDF independently version-controlled. This is the preferred method for long contracts, exhibits, and reference documents that update over time. The full feature is documented in the Microsoft hyperlinks in Word guide.

The plain-English explanation is that Word stores only a URL pointer, and the recipient’s click triggers a OneDrive download or browser preview. The consequence is a tiny .docx, easy versioning, and zero duplication. A common misconception is that the link works for everyone who receives the Word file. It does not. The recipient must have OneDrive permission to the PDF.

For example, Aisha, a project manager in Seattle, links to a master statement of work PDF in OneDrive so her team always opens the latest signed version. When the SOW is amended, she replaces the PDF in OneDrive and every Word file that links to it instantly points to the new version.

How to Generate the Right Kind of Link

Right-click the PDF in OneDrive, choose Share, and select Copy link. Set the audience to People in your organization, Specific people, or Anyone with the link, following the OneDrive sharing options reference. Paste the link into Word using Insert > Link or Ctrl + K.

The consequence of choosing Anyone with the link on a PDF that contains protected health information is a possible HIPAA breach under the HHS Breach Notification Rule. A common misconception is that Anyone links require a Microsoft account to open. They do not. Anyone with the URL can open the PDF.

Preserving Links Across Devices

Links survive when the Word file moves, but only if the OneDrive URL stays valid. The consequence of moving the PDF to a new SharePoint site is a 404 on every linked Word file. A common misconception is that OneDrive auto-updates broken links. It does not, except for renames within the same library.

For example, Mike, an attorney in Miami, linked 120 exhibit PDFs into a brief. When his firm migrated to a new SharePoint tenant, every link broke and he had to manually re-link each exhibit before the filing deadline.

Method 5: Combine Methods for Hybrid Workflows

The Hybrid Insert method uses two or more of the methods above in the same Word document to balance fidelity, file size, and access control. This is how mature legal, healthcare, and finance teams work in practice. A typical hybrid embeds a one-page picture preview, links to the full PDF, and includes a converted text excerpt for accessibility.

The plain-English explanation is that you give the reader the visual, the source of truth, and the searchable text in one place. The consequence of doing this well is a document that survives email gateways, accessibility audits, and litigation holds. A common misconception is that hybrid documents are too complex for non-technical users. They are not, once a template is built.

For example, Sarah, a clinical research coordinator in Boston, builds an IRB packet that previews each consent form as a picture, links to the master PDF in OneDrive, and includes a Section-508-compliant text version below each preview. Her packet passes both FDA 21 CFR Part 11 and HHS IRB review on the first try.

Three Real Scenarios in OneDrive Word

The fastest way to internalize these methods is to walk through three of the most common scenarios I see in production environments. Each scenario maps a goal to a method and shows the direct consequence of choosing that method. The scenarios cover legal, healthcare, and small-business use.

Mistakes to Avoid When Inserting PDFs

Even seasoned Word users repeat the same mistakes when working with PDFs in OneDrive. The cost of these mistakes ranges from a frustrated reader to a failed compliance audit. Each mistake below names the error and the consequence so you can spot the pattern in your own workflow.

• Embedding huge PDFs into Word files that must travel by email, which causes 25 MB gateway rejections.
• Choosing Anyone-with-the-link on PDFs that contain PHI, which can trigger HIPAA breach notification duties.
• Converting signed PDFs to editable Word, which destroys the digital signature and its legal weight.
• Skipping alt text on PDF-as-picture inserts, which fails Section 508 and WCAG 2.1 AA review.
• Forgetting to set Display as icon, which inserts a misleading single-page preview of a long PDF.
• Linking across tenants without checking permissions, which leaves external recipients with broken-link icons.
• Trusting Word for the web to embed objects, which silently fails because the browser app does not support OLE.
• Pasting raw screenshots of PDFs without cropping, which leaks adjacent screen content like email previews.
• Ignoring retention labels on the source PDF, which can pull the Word file into an unintended legal hold.
• Mixing personal OneDrive and OneDrive for Business links, which forces recipients through unexpected sign-in screens.

Do’s and Don’ts for OneDrive Word PDF Inserts

The right habits compound over time, especially when your team produces hundreds of mixed Word and PDF documents. The wrong habits create silent failures that surface only during an audit, a deadline, or a discovery request. Use the lists below as a working checklist.

Do:

• Do check the source PDF’s sensitivity label before choosing a method, because the label often dictates the legal answer.
• Do prefer links over embeds for any PDF over 5 MB, because email gateways and SharePoint previews choke on large .docx files.
• Do run File > Check for Issues > Check Accessibility in Word before sharing, because the built-in checker catches most Section 508 problems.
• Do keep the source PDF in a single, governed OneDrive folder, because moving it later breaks every link in every Word file.
• Do use the desktop app for object embedding, because Word for the web cannot embed PDFs as objects.

Don’t:

• Don’t embed signed PDFs unless you also keep the original PDF outside Word, because the embed copy is the only proof you will have if the original is lost.
• Don’t paste screenshots of PDFs that contain PHI, PII, or trade secrets, because cropping mistakes leak data.
• Don’t assume conversion preserves tables, because Word’s converter routinely flattens complex tables into plain paragraphs.
• Don’t share the Word file with Anyone when the linked PDF requires sign-in, because recipients will see a confusing access-denied screen.
• Don’t ignore the Microsoft 365 file size and path limits, because they cap individual files at 250 GB and paths at 400 characters.

Pros and Cons of Each Method

A side-by-side view of trade-offs helps you choose quickly when a deadline is looming. The table below compares the five methods on the dimensions that matter most in real production work. Use it as a triage tool, not a final answer.

Federal Laws That Shape PDF Embedding

Federal law shapes every decision about embedding PDFs in cloud-stored Word files, and most users do not realize how many statutes apply. Start with the HIPAA Privacy Rule, which governs protected health information and limits how PHI may be transmitted, stored, and shared. The consequence of a casual embed of a lab result is a reportable breach.

FERPA governs student education records and applies to any school that receives federal funding. The consequence of linking a student transcript with Anyone permissions is a FERPA violation that can cost the school its federal funding. A common misconception is that FERPA only applies to K–12 schools. It applies equally to colleges and universities.

GLBA Safeguards Rule governs nonpublic personal information held by financial institutions. The consequence of embedding a customer’s account statement in a Word file shared on personal OneDrive is a Safeguards Rule violation. A common misconception is that GLBA only applies to banks. It applies to mortgage brokers, tax preparers, and many fintech firms.

eDiscovery and FRCP 37(e)

In civil litigation, Federal Rule of Civil Procedure 37(e) imposes sanctions when a party fails to preserve electronically stored information. A linked PDF that is later moved or deleted from OneDrive can be treated as spoliated evidence. The consequence is an adverse-inference instruction at trial and possible monetary sanctions.

A common misconception is that the Word file alone satisfies the litigation hold. It does not. The linked PDF is a separate piece of ESI that must be preserved on its own. The case law in Zubulake v. UBS Warburg and the more recent Klipsch Group v. ePRO E-Commerce sets the standard for preservation duties.

ESIGN Act and UETA

The federal ESIGN Act and the Uniform Electronic Transactions Act give electronic signatures the same legal weight as wet-ink signatures, but only when the signature is preserved with intent and integrity. The consequence of converting a signed PDF to Word is the loss of both. A common misconception is that a screenshot of a signature counts as a valid e-signature. It does not.

For example, Robert, a real estate broker in Denver, converted a signed listing agreement to Word so he could edit a typo. The court later refused to enforce the agreement because the original cryptographic signature was destroyed during conversion.

Troubleshooting the Most Common Errors

Even when you pick the right method, OneDrive Word can throw errors that look mysterious. The fixes below cover the issues I see most often in support tickets. Each fix names the error and the cause so you can resolve it without guessing.

“Word can’t insert this PDF”

This error appears when the PDF is encrypted, password-protected, or built with an unusual structure. The fix is to open the PDF in Acrobat, choose File > Properties > Security, and remove the password using the document owner’s credentials. The consequence of skipping this step is a permanent insertion failure.

A nuance is that some PDFs are certified with a digital signature that prevents modification. The fix is to ask the original signer for an unrestricted copy. A common misconception is that re-saving the PDF removes the certification. It does not.

Sync Conflicts in OneDrive

When two users edit the same Word file at the same time and one of them embeds a PDF, OneDrive may create a conflict copy with the suffix -YourName. The fix is to open both copies, merge the embeds manually, and delete the conflict copy. The consequence of ignoring conflict copies is a slow accumulation of stale files in the OneDrive folder.

A common misconception is that co-authoring eliminates conflicts. It reduces them but cannot prevent them when one user is offline at the moment of insertion. The OneDrive co-authoring guide explains the merge logic.

Scanned, Image-Only PDFs

Scanned PDFs contain no real text, only an image of text. Method 3 conversion will produce empty or garbled Word output. The fix is to run Adobe Acrobat OCR or the OCR tool inside Microsoft 365 before converting.

The consequence of skipping OCR is a Word file that looks empty in screen readers and search indexes. A common misconception is that OCR is always perfect. It is not. Handwritten notes, low-resolution scans, and unusual fonts produce errors that must be hand-corrected.

File-Size and Path-Length Limits

OneDrive supports files up to 250 GB and full paths up to 400 characters, per the Microsoft 365 limits documentation. A Word file with deeply nested folders and a long file name can exceed the path limit and refuse to open.

The fix is to shorten the folder structure and the file name. The consequence of ignoring the limit is a sync error and a file that cannot be opened in Word for the web. A common misconception is that the limit only applies to SharePoint. It applies equally to OneDrive for Business.

Cross-Platform Differences You Must Know

The same Word file behaves differently across the desktop app, the web app, and the mobile app, even when the file lives in the same OneDrive folder. The differences matter most when you are coordinating across a team that uses mixed devices. The table below highlights the gaps.

The consequence of mixing devices without planning is a workflow that works for some teammates and fails for others. A common misconception is that the mobile app is a full replacement for desktop. It is not. The mobile app trades features for portability, and PDF embedding is one of the first features to drop.

For example, Elena, a field engineer in Houston, tries to embed a 30 MB equipment manual into a Word inspection report on her phone. The mobile app fails silently. She switches to a OneDrive link and finishes the report in two minutes.

Personal OneDrive vs. OneDrive for Business vs. SharePoint

Three Microsoft cloud surfaces can host your Word file, and each has different rules for PDF embedding. Personal OneDrive is for consumers and includes 5 GB free, with paid tiers up to 1 TB. OneDrive for Business is for organizations and ships with Microsoft 365 Business and Enterprise plans. SharePoint document libraries are team-shared spaces backed by the same engine as OneDrive.

The consequence of mixing these surfaces is broken links and unexpected sign-in prompts. A linked PDF on personal OneDrive will demand a Microsoft account login from a corporate recipient, and a linked PDF on OneDrive for Business will demand a corporate login from a personal recipient. A common misconception is that the link looks the same. It does not. The hostnames differ between onedrive.live.com and yourtenant-my.sharepoint.com.

For example, James, a freelance consultant in Austin, sent a Word proposal that linked to a PDF stored on his personal OneDrive. The corporate client could not authenticate and missed the deadline to review. James moved the PDF to a Anyone-with-the-link setting and the client opened it on the second try.

Retention Labels and Sensitivity Labels

Microsoft Purview retention labels and sensitivity labels flow through both Word and OneDrive. A PDF labeled Confidential may refuse to embed in a Word file labeled Public, depending on tenant policy. The consequence of ignoring labels is a blocked save or a quarantined file.

A common misconception is that labels travel with the embedded PDF. They do for object embeds, but not for picture inserts or text conversions, which strip the label. For example, Hannah, a financial analyst in New York, lost a sensitivity label when she pasted a PDF chart as a picture and her DLP system flagged the new Word file as a policy violation.

Building a Reusable PDF Insert Template

Once you have picked your preferred methods, save them as a Word template so your team applies them consistently. The template should include a Preview placeholder for the picture insert, a Source hyperlink placeholder for the OneDrive link, and a Text Excerpt placeholder for the converted body. The full template approach is documented in the Word templates guide.

The consequence of skipping the template is inconsistent documents that confuse readers and auditors. A common misconception is that templates are only for branded letterhead. They are equally valuable for compliance and accessibility.

For example, Theresa, a regional compliance lead in Charlotte, built a hybrid template for her bank’s loan files. Her template cut audit prep time from three weeks to four days because every Word file followed the same PDF embedding pattern.

FAQs

Can I insert a PDF into a Word document stored in OneDrive?

Yes. You can embed it as an object, insert it as a picture, convert it to editable text, link to the OneDrive copy, or combine these methods inside one Word file.

Does Word for the web support inserting a PDF as an object?

No. Word for the web only supports picture inserts and hyperlinks, so you must open the file in the desktop app to perform a true object embed.

Will inserting a PDF as a picture preserve the text?

No. Inserting as a picture flattens the page into a bitmap, which means the text is no longer searchable, selectable, or accessible to screen readers.

Can I edit a PDF directly inside Word in OneDrive?

Yes. The desktop app converts the PDF into editable Word content, but the conversion can break tables, forms, and digital signatures, so review the result carefully.

Does linking to a PDF in OneDrive count as embedding it?

No. A link stores only a URL pointer, so the PDF stays separate, and the recipient must have OneDrive permission to open the linked file.

Can a recipient open an embedded PDF without Microsoft 365?

Yes. Any PDF viewer can open an embedded PDF after the recipient double-clicks the icon, because the embed stores the full PDF bytes inside the .docx package.

Will converting a signed PDF to Word keep the signature?

No. Conversion strips the cryptographic signature, which destroys the legal non-repudiation that the federal ESIGN Act and state UETA statutes provide.

Does HIPAA allow me to email a Word file with an embedded PHI PDF?

No. Unencrypted email of PHI violates the HIPAA Security Rule, so you must use encrypted transmission or a OneDrive link with strict Specific people permissions.

Can mobile Word embed a 100 MB PDF?

No. The mobile app fails on most phones above roughly 50 MB, so you should switch to a OneDrive link or use the desktop app for large files.

Do retention labels follow a PDF that I embed inside a Word file?

Yes. Object embeds carry the source PDF’s sensitivity and retention labels, but picture inserts and text conversions usually strip those labels.

Will a OneDrive link to a PDF break if I rename the file?

No. Renames inside the same OneDrive library preserve the link, but moving the PDF to a different library or tenant breaks every Word file that linked to it.

Can I insert multiple PDFs into one Word file in OneDrive?

Yes. You can insert as many PDFs as you want using any combination of methods, but be mindful of the .docx file-size cap and the email gateway limits at your destination.