How to Attach a PDF to a Word Document (And What That Really Means)

Attaching a PDF to a Word document sounds straightforward — but the method you use changes what the recipient actually sees, how the file behaves, and what you can do with it later. There are at least three distinct approaches, and picking the wrong one can mean a PDF that won't open on someone else's machine, a bloated file, or a document that breaks when converted.

Here's a clear breakdown of how each method works, what it's actually doing under the hood, and which variables determine which approach fits your situation.

What "Attaching" a PDF to Word Actually Means

The phrase covers several genuinely different things:

  • Embedding the PDF as an object inside the Word file
  • Linking to the PDF so Word references an external file
  • Inserting PDF content so the text or images from the PDF flow into the document
  • Attaching the PDF as a separate file when sending via email (not technically "in" the Word doc, but often what people mean)

These aren't interchangeable. Each one produces a different result.

Method 1: Embed the PDF as an Object 📎

This is the most common interpretation of "attaching" a PDF inside Word.

How it works: Go to Insert → Object → Create from File, browse to your PDF, and insert it. The PDF becomes embedded inside the .docx file itself. Recipients see a PDF icon (or the first page as a thumbnail) and can double-click to open it — as long as they have a PDF reader installed.

What's actually happening: Word stores a copy of the PDF's binary data inside the document container. The .docx format is essentially a ZIP archive of XML files and media assets — your PDF gets bundled into that package.

Key variables that affect this:

  • File size: The PDF is fully copied into the Word file. A 10 MB PDF makes your Word document roughly 10 MB heavier.
  • Recipient's setup: The embedded PDF opens via the recipient's default PDF application. If they're on a locked-down corporate machine with no PDF reader, the icon sits there useless.
  • Display mode: You can choose to show it as an icon or as the first page rendered as an image. The image preview is static — it won't reflect any updates to the original PDF.

Method 2: Link to an External PDF

Instead of embedding a full copy, Word can store a reference (a file path) to a PDF that lives elsewhere on your drive or network.

How it works: Same Insert → Object path, but check the "Link to file" checkbox before inserting.

What's actually happening: Word saves the file path, not the PDF data. When the document opens, it fetches the PDF from that path in real time.

Key variables here:

  • Portability: If you send the Word document to someone else, the link breaks — because the PDF isn't at the same file path on their machine. This method only makes sense when the document and PDF stay on the same shared network or cloud folder that all recipients can access.
  • Live updates: If the PDF changes, the Word document reflects the latest version automatically. Useful for internal documents that reference frequently updated reports.
  • Use case fit: Linking is genuinely underused in team environments where everyone works from the same SharePoint or network drive. It's almost never right for documents you're emailing externally.

Method 3: Insert PDF Content Into the Document

This approach doesn't attach the PDF — it converts its content and pastes it into Word.

How it works: Go to Insert → Object → Create from File, or simply open the PDF directly in Word (File → Open → select your PDF). Word will attempt to convert the PDF into editable Word content.

What's actually happening: Word uses its built-in PDF rendering engine to interpret the PDF's structure and reflow it as native Word content — paragraphs, tables, images. This is a conversion, not an embed. The original PDF is no longer referenced.

Key variables:

  • PDF complexity: Simple text-based PDFs convert cleanly. PDFs that are scanned images, heavily formatted with custom layouts, or built from non-standard fonts often convert poorly — tables collapse, columns merge, spacing breaks.
  • Whether OCR is needed: A scanned PDF is just an image. Word can attempt to read it, but without optical character recognition (OCR) built in, the text won't be editable. Some versions of Word and some PDF tools handle this better than others.
  • Editability goal: If your goal is to reuse the PDF's text in a new document, this method is right. If your goal is to preserve the PDF as a self-contained file alongside your Word content, it's the wrong tool.

Method 4: The Email Attachment Misconception

Many people searching "how to attach a PDF to Word" actually mean: how do I send a Word document and a PDF together?

The honest answer: Word documents don't have a native "file attachment" container the way email does. What you're actually doing in those cases is attaching both files separately to an email, or zipping them together. There's no built-in Word feature that bundles a secondary file the way an email client does — the Object embedding above is the closest equivalent, with the caveats already described.

The Variables That Actually Determine the Right Method

FactorPoints Toward
Sending externally to unknown recipientsEmbedding (not linking)
Document stays on a shared internal driveLinking
Need the PDF content to be editableConvert/insert content
PDF needs to stay visually intactEmbedding as object
File size is a concernLinking or keeping files separate
Recipient may not have a PDF readerConvert content into Word
PDF is scanned/image-basedConversion with OCR tool

How Word Version and OS Affect Your Options 🖥️

The Insert → Object menu behaves differently across Word versions and platforms. Word for Mac has historically had more limited PDF embedding support than Word for Windows. Word on the web (Microsoft 365 in a browser) doesn't support object embedding at all — you'd need the desktop application.

If you're working in Google Docs rather than Microsoft Word, none of these menus exist in the same form — Docs handles PDF insertion through Drive previews and linked files, which is a different workflow entirely.

The method that's genuinely correct depends on why you're attaching the PDF, where the document is going, and what software everyone involved is actually running — and those answers vary more than most guides acknowledge.