You can save a Word document as a PDF in about eight seconds on any current version: open the file, choose File > Save As (or File > Export), pick PDF from the file-type menu, and click Save. The method that fits your day depends on one question — do you need the PDF once, or do you need 200 of them every month? Everything below uses the exact menu names Microsoft ships in Word for Microsoft 365 on Windows and Word for Mac, with version-specific differences called out where the two drift apart.
Start With the Shortcut That Skips the Menus
The fastest path in Word for Microsoft 365 on Windows doesn't touch the File tab at all. Press F12, and the Save As dialog opens on top of your document with the file-type dropdown already visible below the filename field; select PDF and click Save. On the Mac version, the equivalent is Command + Shift + S, though the Mac dialog puts the format picker in a different spot, labeled Format near the bottom.
Both dialogs then surface a second box labeled Options (Windows) or a button reading Options (Mac). That's where the export decisions actually live, and most people click straight past it. You get three meaningful choices there: export the whole document or just a page range you type in, include or exclude comments and tracked changes, and — the one that matters most — choose whether the PDF should be optimized for standard publishing or for the smallest possible file size.
The shortcut exists in every paid desktop edition from Word 2013 onward. It does not exist in Word for the web, which has no keyboard route to a PDF at all and forces you through the File menu. If F12 does nothing on your machine, check whether your laptop's function keys are set to media control; pressing Fn + F12 gets around that.
One quirk catches people who share machines: the Save As dialog remembers the last folder you used, not the folder your document lives in. If a colleague saved something to a desktop folder last week, your PDF may land there and you'll think the export failed. Read the path bar before you hit Save.
Use File > Export When You Want the Options Panel
File > Save As and File > Export both produce a PDF, and the difference is mostly about what you see along the way. Export opens a dedicated pane with a single large button labeled Create PDF/XPS, followed by an Options link — this is the same engine, just presented as a two-step commitment instead of a dropdown. Microsoft's own support documentation recommends Export for anyone who wants to inspect settings before generating the file.
Clicking Options inside that pane opens a dialog with a checkbox reading "Document structure tags for accessibility" and another reading "ISO 19005-1 compliant (PDF/A)." The accessibility checkbox is on by default in Word for Microsoft 365; PDF/A is off. That first checkbox is not cosmetic — it's what lets a screen reader announce your headings and table cells in the right order instead of reading a flat wall of text.
The PDF/A option matters if you're filing with a government body, an academic journal, or a regulated archive. PDF/A embeds every font and forbids encryption, which makes the file bigger but guaranteed to render identically in fifteen years. The downside is real: PDF/A files can't be password-protected during export, so if your organization requires encryption, you'll have to choose one or the other.
Export also wins for repeat work because Word remembers your last-used settings in that pane for the session. If you're generating five PDFs in a row from the same template, set the options once and the next four take fewer clicks. Nothing about that memory persists after you close Word.
Set PDF Options Correctly for Print, Screen, or Archive
Word's export engine gives you a choice between two optimization presets in the main Save As dialog: Standard (publishing online and printing) and Minimum size (publishing online). The names are misleading. Standard doesn't just mean print-ready, and Minimum doesn't just mean small. What actually changes is the image resolution cap and the font-embedding behavior.
Under Standard, Word downsamples images to 220 pixels per inch and embeds fonts as subsets — meaning only the characters you actually used get embedded. Under Minimum size, images drop to 150 ppi and font embedding gets more aggressive about compression. A 40-page report with a dozen charts can shrink from roughly 8 MB to 2 MB switching between them, though the exact figure depends on your source images and you should check the resulting file size in Windows Explorer or Finder rather than trusting a rule of thumb.
Print shops usually want 300 ppi images, which neither preset delivers on its own. If your document is headed to a commercial printer, Word's PDF output may resample your carefully prepared 300 ppi photos down to 220. The workaround is to save via File > Print and choose Microsoft Print to PDF, which passes images through without downsampling — a route Microsoft's support pages don't emphasize, and one that preserves resolution at the cost of losing the accessibility tagging.
For anything legal or archival, turn PDF/A on and accept the larger file. For email attachments, Minimum size plus a page range of only the sections the recipient needs usually lands under 1 MB, which is the practical threshold where corporate mail filters stop stripping attachments. I've seen a 60-page policy manual go out as a 400 KB PDF simply because the sender exported three relevant pages instead of the whole binder.
What Word's Built-In PDF Button Actually Changes
The single most overlooked fact about Word's PDF export: the file is a snapshot, and the snapshot is frozen the moment you click Save. Your .docx keeps living and updating; the PDF does not. If you send a PDF on Monday and edit the Word file on Tuesday, the recipient still has Monday's version, and there is no link between them. Teams that treat the PDF as a living document learn this the hard way during audit season.
The second thing the button changes is fonts. Word embeds subsets of the fonts you used, so the PDF renders correctly on a machine that has never installed Calibri or Aptos. But if your document uses a font with a restrictive license — some corporate brand fonts are licensed per-seat and forbid embedding — Word may silently substitute a fallback and the PDF will look wrong in ways that are hard to diagnose. Check the fonts panel before you export an important document, and if a substitution happens, the recipient will see it too.
Hyperlinks survive the export by default in Word for Microsoft 365, but internal cross-reference links sometimes break, especially if they point to bookmarks in a section that got excluded by a page range. Bookmarks themselves may not carry over at all — PDF bookmarks (the navigation pane list) only appear if you've applied Word's Heading styles consistently, because Word converts those styles into the PDF outline. A document formatted with manual bold text as fake headings will export as a PDF with no clickable table of contents.
And comments? They vanish unless you explicitly include them. That's usually what you want, but it becomes a problem when someone expects the reviewer's margin notes to travel with the file. If you need to preserve them, tick the comments box in the Options dialog during export, and understand that the resulting PDF will display them as annotation bubbles that some PDF readers hide by default.
The macOS and Web Versions Behave Differently
On Word for Mac, the menu path is File > Save As, the shortcut is Command + Shift + S, and the format dropdown sits under a label reading File Format rather than "Save as type." The Options button is there too, but the Mac version splits its settings across two tabs instead of one dialog, and the PDF/A checkbox hides on the second tab under a heading labeled Compliance. Anyone switching between platforms for the first time will spend a minute hunting for it.
Word for the web is the version that surprises people. It can export a PDF — File > Export > Export as PDF — but it has no Options dialog at all. You get the whole document, Standard quality, accessibility tagging on, and no way to exclude comments, restrict a page range, or pick PDF/A. If your document has tracked changes, the web version exports them as visible markup, because there's no checkbox to turn it off. This is the version most likely to produce an embarrassing PDF in a shared workspace.
The web version also has a size ceiling. Very large documents — think hundreds of pages with heavy imagery — may time out during export, and the browser will show a generic error rather than explaining that the file exceeded a processing limit. Microsoft's support documentation notes that documents over a certain complexity may need to be exported from the desktop app instead, and the practical fix is to open the file in desktop Word rather than retry the browser.
If you straddle Mac and Windows at work, test the export on both before you standardize a template. Font substitution behaves differently between the two builds, and a document that renders cleanly out of Windows Word may look subtly off out of Mac Word. It's worth the five minutes before you send anything to a client.
Batch Convert an Entire Folder Without Opening Each File
Converting one document by hand takes seconds. Converting eighty takes an afternoon unless you automate, and Word can do it from inside the app with a short macro that loops through every .docx in a folder. The steps below assume Word for Microsoft 365 on Windows and a folder path you can type; test on a copy of three files first, because a macro running across a real folder is unforgiving.
1: Put every source document in one folder with no subfolders, for example C:\Invoices. 2: Create an empty sibling folder and note its path, for example C:\Invoices\PDF. 3: Open Word, press Alt + F11 to launch the Visual Basic editor, and choose Insert > Module. 4: Paste a loop that opens each file in the source folder, calls the export routine, and closes without saving — a standard pattern published across Microsoft's developer community, not something you should write from memory under deadline pressure. 5: Run the macro, then open the PDF folder and confirm the file count matches the source folder. 6: If a file fails, it will usually be a .doc (legacy format) or a password-protected document — both break the loop, so convert legacy files to .docx first and remove protection before rerunning.
A macro conversion of 80 typical 5-page documents runs in roughly three to five minutes on an ordinary office laptop, based on the per-file export time Word shows for mixed documents. That's the real argument for automation: it's not the eight seconds per file, it's the context-switching cost of opening and closing 80 windows and the human error rate of doing it while distracted.
Watch out for documents that are protected as read-only or that prompt for a password when opened. The macro stops at the prompt and waits, which means it can hang overnight. Clear passwords and read-only flags on the source folder before you launch anything that runs unattended.
Which Method Fits Which Job
The right export route depends on volume, fidelity requirements, and whether you need a record. There's no universal best method, but there is a best method for each job, and the table below maps them against the dimensions that actually decide the outcome.
| Method | Best for | Accessibility tagging | PDF/A option | Image resolution | Effort per file |
|---|---|---|---|---|---|
| File > Save As (desktop) | Single documents, daily use | Yes, on by default | Yes, one checkbox | Downsampled to 220 ppi | 8–10 seconds |
| File > Export (desktop) | Inspecting settings first | Yes, same engine | Yes, in Options | Downsampled to 220 ppi | 12–15 seconds |
| Microsoft Print to PDF | Commercial print, image-heavy files | No, output is untagged | No | Preserved as prepared | 15–20 seconds |
| Word for the web | Quick one-offs from a browser | On, not adjustable | No | Fixed to web preset | 10–20 seconds |
| Macro batch | 20+ files, recurring projects | Inherits per-document setting | Set in code | Follows each document's settings | 3–5 minutes for 80 files |
The split rule: if a screen reader or an archive will ever touch the file, use Save As or Export on the desktop and leave accessibility tagging on. If the file is headed to a printing press, use Print to PDF and accept the loss of tagging. If you're producing more than twenty PDFs a month from templates, build the macro and stop doing it by hand.
One drawback of the recommended desktop Save As route deserves naming: it silently downsamples your images. Graphic designers and photographers who send proofs to clients from Word have learned to distrust the default and use Print to PDF instead, even though it costs them the accessibility tags. Pick the failure you can live with.
Errors You'll Actually Hit and How to Clear Them
The most common failure — and the one with the least helpful error message — happens when Word tells you the file is in use by another program. That almost never means another program. It usually means you have a PDF with the same name already open in a PDF reader, and Windows won't overwrite a file that another process has locked. Close the PDF and retry; the error disappears without any settings change.
"An error occurred while exporting" is the second most common, and its most frequent cause is a corrupt image. Word export chokes on embedded images stored in formats it can only partially decode, particularly very old WMF or EMF graphics pasted from legacy software. Try File > Save As to .docx first, reopen the copy, and export again — that round trip often rebuilds the internal image references. If it persists, locate the images one at a time and replace them with PNG or JPEG.
Font issues produce a quieter failure: the PDF saves, but the fonts render with extra space or wrong glyphs. That's the font-embedding restriction mentioned earlier, or a font that Word couldn't subset cleanly. Replacing the document's fonts with a standard family like Calibri, Arial, or Georgia for the final export solves it. If your brand guidelines demand the custom font, print the PDF to a second PDF using your PDF reader, which flattens the text into vector outlines.
Protected View is the culprit when the Save As dropdown doesn't offer PDF at all. Files opened from a network location or downloaded from email may open in Protected View, where export is disabled until you click Enable Editing. The dropdown shows no PDF option and newer users assume the feature is missing. Click the yellow banner, then try again — the PDF entry reappears instantly.
Keep File Size and Fidelity in Balance
The tension between a small PDF and an accurate one is real, and Word's presets land you at different points on that curve. A 30-page annual report with 20 photographs will land somewhere between roughly 3 MB and 15 MB depending on the optimization preset and whether you used Print to PDF, based on the downsampling math at 220 versus 150 ppi for the images. The difference in what the reader sees on screen is marginal; the difference in email deliverability is significant.
Text-heavy documents barely respond to the optimization choice, because text compresses well regardless. A 60-page contract of plain text with a few tables might occupy 600 KB under Standard and 500 KB under Minimum size — a savings so small it's not worth the quality loss if the file also contains scanned signature pages. Know which kind of document you have before fussing with settings.
If you need smaller files and don't have a PDF editor, reduce the document's image resolution in Word itself before export: right-click each picture, choose Format Picture, open the Picture tab, and use Compress Pictures to target a lower output resolution. That's a destructive edit to your .docx, so do it on a copy. The one-two of compressing images in Word and exporting under Minimum size can bring a bloated document down by more than half.
Lossless compression in most PDF readers (the Save As Optimized or Reduce File Size command in Acrobat, for example) is the last resort and can re-tag the document, stripping the accessibility structure you carefully preserved. If accessibility matters, don't run the PDF through a second compression pass after export — accept the larger file or produce a print-only version separately.
FAQ
What's the fastest way to convert 50 Word files to PDF?
Use a Word macro that loops through a folder, which processes roughly 50 typical documents in two to four minutes without any manual clicking. The alternative — File > Save As on each file — costs about eight seconds per document plus the time to open and close each window, so 50 files is closer to 15 minutes of attention. The macro route also eliminates the risk of forgetting one file in a long folder.
Why does my exported PDF show comments I thought I'd deleted?
Word exports comments only if the file still contains them and the export options include them. If your PDF shows comments, the Word document itself still holds them — deleting the visible bubble in Word's margin doesn't always resolve a comment, and you may need to delete the comment itself via the Review tab. Check with Review > Show Comments before exporting, then untick the comments box in the export Options dialog as a safety net.
Why is the PDF bigger than the Word document?
PDFs often exceed the source .docx size because the PDF format embeds font data and flattens layout information that Word stores as instructions. A 1 MB document with a custom typeface can export as 3 MB because the font data is baked in. The accessibility tagging and document structure also add weight. If the size difference bothers you, switch the optimization preset to Minimum size and re-export.
Does Save As or Export produce a different PDF?
They produce the same file, because both call the same export engine with the same underlying settings. Export just shows the options pane before committing, while Save As hides the settings behind the Options button. Use Export when you care about accessibility tags, PDF/A, and page ranges; use Save As when you don't. The resulting PDFs are indistinguishable once created.
Can Word for the web create a PDF/A file?
No. The web version exports only in Word's standard PDF mode, with no options dialog and no PDF/A checkbox, so any document that must meet archive standards needs to be exported from the desktop app. If your organization requires PDF/A, open the file in Word for Microsoft 365 on Windows or Mac and use File > Export with the ISO 19005-1 compliance checkbox enabled.
What if the PDF option doesn't appear in the Save As dialog?
That's almost always Protected View. Documents opened from email attachments or network shares can launch with export disabled, and the format dropdown simply won't list PDF until you click Enable Editing on the yellow banner near the top of the window. Other causes are opening the file in a viewer rather than Word, or a very old Word version — anything older than Word 2010 needs the free Save as PDF add-in Microsoft used to distribute.
Is there a way to keep the link between the PDF and the Word file?
No. The PDF is a snapshot with no live connection to its source, and editing the .docx afterward has no effect on the PDF you already sent. If you need recipients to see updates, send the .docx or re-export and send a new PDF with a version number in the filename. Some workflows use SharePoint or OneDrive to distribute a single authoritative PDF, which at least keeps everyone reading the same file.
Are PDF bookmarks preserved from Word?
Only if you structured the document with Heading styles. Word converts its built-in Heading 1 through Heading 9 styles into the PDF's bookmark outline automatically, so a document formatted that way will export with a clickable navigation pane. A document that fakes headings with bold text exports as a flat PDF with no outline at all, and no export setting will add one after the fact.