Word to PDFWhy Your PDF Is Bigger Than the Original Word Document
A .docx is a ZIP archive, so everything inside it is already compressed; a PDF is not one, and on top of your text it carries a copy of every font you used and stores each image in its own structure. That is why the same document routinely comes out two to ten times larger after export. Almost all of the difference comes from three things: embedded fonts, images that are far bigger than they look on the page, and which preset you chose in the export dialog.
A .docx is a zip file. A PDF isn't.
Rename a .docx to .zip and open it — you will find a folder of XML files describing your text and formatting, plus a word/media folder holding your pictures. The XML is verbose but repetitive, so ZIP compression flattens it to almost nothing. Ten pages of plain text can sit in a 30 KB .docx.
A PDF describes the same document differently. Every page carries drawing instructions for where each glyph lands, the file embeds the font programs needed to draw those glyphs, and each picture becomes its own object. The text content is compressed too, so text is rarely the problem. The fonts and the images are the two costs a .docx does not pay in the same way, and they are the two you can actually do something about.
Reason one: the fonts travel with the file
A PDF has to look identical on a machine that has never heard of your typeface, so the font goes inside the file. Normally Word embeds a subset — only the characters you actually used — which costs tens of kilobytes per typeface and weight. Bold, italic and bold-italic each count as a separate face, so a document using three families in four weights is paying for twelve embeddings.
Full embedding is where megabytes appear. Two settings cause it. In the export dialog, click Options and check whether ISO 19005-1 compliant (PDF/A) is ticked — PDF/A requires complete font embedding, and it can double a small file. Leave it off unless an archive or court filing demands it. Trimming the number of distinct typefaces and weights helps more than any embedding switch, and the embedding options themselves are a document decision rather than a size trick — turning them off to save bytes is what makes the layout move on someone else’s machine. If your concern is the opposite problem — the wrong typeface coming out the other end — see why fonts change during conversion.
Reason two: your images are the original photos, not the thumbnails
This is the usual culprit, and it surprises people. When you drag a phone photo into Word and pull the corner handle until it is two inches wide, Word does not resample it. It stores the entire original — a 12-megapixel JPEG, roughly 3 to 5 MB — and simply draws it small. Ten of those and you have a 40 MB document before you write a word.
Cropping behaves the same way. Word's crop is non-destructive by default: the trimmed-off parts stay in the file so you can un-crop later. And pasted screenshots are often PNG, which is lossless — a full-screen PNG can be several megabytes where the same image as JPEG would be a few hundred kilobytes.
The export carries all of it forward. Note that this is a size problem, not a quality problem; if your pictures come out worse than they went in, that is a different issue covered in why images look blurry after conversion.
Reason three: the export preset you didn't read
In Word for Windows, File > Save As (or File > Export > Create PDF/XPS) with PDF selected shows an Optimize for choice with two options: Standard (publishing online and printing) and Minimum size (publishing online).
The difference is almost entirely about images. Standard keeps them at print-grade resolution. Minimum size downsamples them for screen viewing, which on a photo-heavy document can cut the file by half or more, and on a text-only document changes essentially nothing — so if your ten-page report is 180 KB, switching presets is not the fix you are looking for. Use Minimum size for anything that will be read on a screen, Standard for anything going to a printer.
Word for Mac does not show this dropdown. Its Save As sheet offers its own two-way choice between an electronic-distribution option and a print option, which does the same job.
Fix it in Word, in this order
Work on the .docx before you export. Every one of these is faster and more effective than trying to shrink the PDF afterward.
- Compress the pictures. Click any image, open the Picture Format tab, and choose Compress Pictures in the Adjust group. In the dialog, clear the box that limits the change to the selected picture so it applies to every image in the file, then pick a resolution — the list runs from High fidelity down to an e-mail-grade 96 ppi, with 150 ppi being the sensible default for anything read on a screen and 220 ppi if it will be printed.
- Delete the cropped areas. In that same dialog, tick the option to delete cropped areas of pictures. On a document full of cropped screenshots this alone can halve the file. It is irreversible, so save a copy first.
- Cut the font count and the embedding. Turn off PDF/A in the export options, use the characters-used-only embedding setting, and consolidate to one or two typefaces.
- Re-save the .docx. Word keeps revision data as you edit. Doing a plain Save As to a fresh filename before exporting sometimes drops a surprising amount of accumulated weight.
Font embedding settings themselves belong to the document, not the export: why your font changes when you convert covers which boxes to tick and why turning them off to save bytes costs you the layout.
What a normal size looks like — and what our converter won't do
Calibrate before you start optimizing. A ten-page document of nothing but text and headings should land well under 200 KB as a PDF. Add a logo and a couple of charts and you are still under a megabyte. A document with a dozen phone photos in it can legitimately be tens of megabytes, and no export setting turns that into a 2 MB file without touching the images themselves.
Be clear about what the converter on this site does here: it embeds a font subset and copies your original image bytes into the PDF byte-for-byte, without re-encoding them. That is deliberate — it is why pictures come out exactly as sharp as they went in — but it means a bloated .docx produces a bloated PDF. There is no compression stage and no way to shrink an existing PDF here. Fix the size on the Word side first, then convert.
When it's still too big to email
Gmail refuses attachments over 25 MB per message, and most other mail systems sit in the same 20–25 MB range, so past a certain point you are not compressing your way out. Send a link instead.
Gmail handles this itself: attach the oversized file and it offers to upload it to Google Drive and insert a link. Outlook does the equivalent with OneDrive. Both let the recipient download the real file at full quality, and neither of you has to think about the size again. For a document that has to reach someone's phone, sending it through WhatsApp as a PDF is often simpler than email, and if you are working without Office at all, converting without Word covers the alternatives.