PDF vs. Word: Which Format to Use and When

Every document you send makes a quiet statement about whether you expect it to be edited or read. Choosing the wrong format for that intent causes most everyday document friction: the contract that came back with silently changed terms, the CV that looked broken on the recruiter's machine, the form nobody could fill in.

The fundamental difference

Word documents are living. A .docx file is a description of editable structure — paragraphs, styles, sections — that each copy of Word reflows on the fly. That's its power and its weakness: the same file can look different on different machines (missing fonts, different page sizes, different Word versions), and anyone can change anything, with or without tracked changes.

PDFs are frozen. A PDF describes exactly where every character and image sits on every page. It looks identical on a phone in Tokyo and a printer in Toledo, twenty years from now. Editing one is deliberately awkward — which, when you're shipping a document rather than drafting it, is precisely the point.

The rule that follows: draft in Word, ship in PDF.

Choose Word when…

• The document is being written — by you or collaborators.
• You're inviting changes: a contract under negotiation, a report awaiting comments.
• The recipient asked for it (recruiters who paste CVs into systems, editors who work in tracked changes).
• The content is a template others will adapt.

Choose PDF when…

• The document is done and its appearance matters: CVs, invoices, proposals, certificates.
• It's an official record: signed agreements, statements, receipts. (Their fixity is why courts and archives prefer them.)
• It must print exactly right.
• You need features Word can't ship: password encryption, flattened un-editable forms, or a guarantee that page 7 is the same page 7 everywhere.

The handoffs, in practice

Word → PDF is built in: File → Save As → PDF (or Export) in Word, Google Docs and LibreOffice. Do this as the final step, after the last edit — then make any post-export touches with PDF tools: page numbers if the export lacks them, metadata cleanup before publishing, merging with attachments.

PDF → Word is the messy direction, and honesty helps here: a PDF stores where things sit, not how they flow, so full conversion back to clean editable structure is inherently imperfect — automated converters produce text boxes pretending to be paragraphs. When what you actually need is the text (to requote, rework or translate), pulling it cleanly with PDF to Text and reformatting in your editor is often faster than wrestling a converted layout. For scanned PDFs, OCR first.

Plain text → PDF is the underrated third path: notes, logs, licenses and READMEs become clean, paginated, printable documents in seconds with Text to PDF.

The mistakes to stop making

1. Sending .docx to invite "no changes." If it shouldn't be edited, freezing it is the message. Send PDF.
2. Sending PDF during co-writing. Your reviewer wants to suggest edits, not annotate a frozen page. Send Word.
3. "Editing" by converting back and forth. Each round trip degrades the document. Keep one living source file; export fresh PDFs from it.
4. Forgetting that PDFs carry history too. A PDF exported from Word inherits title and author metadata from the document — check and wipe it before publishing anonymously.