Should You Send Your Resume as a PDF or Word Document?

Send a PDF by default. Send Word when the posting asks for it, when the upload form only accepts .doc or .docx, or when an agency recruiter asks. Keep both versions of the same resume on hand so you never have to convert one in a hurry.

The rule, in five lines

Most of the confusion comes from treating this as one question with one answer. It is really a short lookup table.

If you remember nothing else: the posting outranks your preference, and a stated format request is a small compliance test you can pass for free.

Why PDF is the sensible default

A PDF is a fixed rendering. Fonts are embedded, margins are frozen, and the page breaks where you decided it breaks. Open it on a Windows laptop, an iPhone, a Chromebook, or inside a recruiting tool's preview pane, and you see the same document.

A Word file is a set of instructions for redrawing the document on the reader's machine, using their fonts, their Word version, and their default paper size. Any of those can shift. The failure is small and ugly: a font substitution nudges your spacing, your contact line wraps, and the tidy one-page resume you spent an evening on arrives with a single orphaned line pushed onto page two. You never see it happen. The reader sees only the result.

That page-break risk is worth taking seriously if you have been deliberate about length — see one page versus two pages for why that decision matters. A PDF is the only way to guarantee the version they open is the version you approved.

Word files also carry things you may not want to send. A .docx keeps document properties, and sometimes tracked changes or leftover comments. If you must send Word, open the document properties and check the author name and company fields before you attach it.

PDF protects the layout. Word protects the recipient's ability to edit. Ask which of those the person on the other end actually needs.

The "ATS can't read PDFs" objection, honestly

You will see this repeated everywhere, usually with no source and no version number attached to it. The accurate version is narrower.

Applicant tracking systems parse text. A PDF that contains a real text layer — one produced by exporting from Word, Google Docs, Pages, or LibreOffice — is text, and mainstream parsers handle it. The PDFs that genuinely fail are the ones that contain no text at all:

• A scan of a printed resume, or a photo of one.
• An image exported from a design tool and wrapped in a PDF.
• A design-tool export with fonts converted to outlines, which turns letters into shapes.
• A "print to PDF" of a screenshot.

To a parser, all four are a picture of a document. There is nothing to extract, so your details arrive blank in the system's fields.

The second, larger risk has nothing to do with PDF versus Word. It is layout. Two-column templates, text in floating boxes, contact details tucked in the page header, and skills laid out in tables can all confuse a parser regardless of which format you save them in. A Word file with a two-column layout is not safer than a PDF with the same layout. We go through the structural fixes in building an ATS-friendly resume.

How to check your PDF has a real text layer

This takes about fifteen seconds and it is the single most useful check in this guide.

1. Open the PDF in any reader or in your browser.
2. Click and drag across a few lines of a job bullet.
3. If the text highlights, copy it.
4. Paste it into a plain text editor, an empty email, or a search box.

If the words come through, you have real text. If nothing highlights, or you get a blue box over the whole page with nothing to copy, it is an image and you need to export it again from the original document. A second check: press Ctrl+F (Cmd+F on a Mac) and search for a word you know is in there, like "Experience". No match means no text.

Then read what you pasted, because the paste order is the reading order a parser will see. This is where two-column templates give themselves away.

The first one is not corrupt. It is exactly what the file contains, in the order the file stores it, and any system reading it inherits that scramble. The fix is not a different file format. It is a single-column layout.

When Word is genuinely the right choice

Recruiters who ask for Word are usually not being difficult. Three situations account for most of it.

Agency and staffing recruiters

An agency recruiter rarely forwards your document as you sent it. They reformat it into their own house template, put their logo on it, and often strip your direct contact details before it reaches the client, so the client cannot go around them. That is their business model, not a slight. Doing it from a PDF means retyping your resume by hand, which is slow and introduces errors into your own employment dates. Sending a .docx means your wording survives intact.

The posting or the portal says so

Public sector applications, some universities, and a number of staffing portals still specify Word. Follow the instruction exactly, including .doc versus .docx if they distinguish. Where a posting says "Word or PDF", pick PDF.

Somebody is going to edit it

A careers adviser marking it up, a friend leaving comments, an internal referrer adding notes for the hiring manager: all of them want an editable file. Send Word and keep your own master copy separate.

When the upload form only accepts .doc or .docx

First, do not rename the file. Changing resume.pdf to resume.docx does not convert anything; it produces a file that either refuses to open or opens as unreadable characters, and the recipient sees a broken attachment with your name on it.

Export properly instead, from whatever you originally wrote it in:

• Google Docs: File → Download → Microsoft Word (.docx)
• Pages: File → Export To → Word
• LibreOffice: File → Save As → Word 2007-365 (.docx)
• Word: Save As → .docx (choose .doc only if the form insists)

If your only surviving copy is a PDF, open the PDF directly in Word or upload it to Google Docs — both will convert a text-based PDF into an editable document. The conversion is never clean, so treat the result as a draft and repair it before sending. That is also why keeping both formats from the start is worth the two extra seconds; if you build documents in SwiftCover, the same resume exports as PDF or DOCX, so there is no conversion step to go wrong.

• Page count is the same as your PDF, with no orphaned final line.
• Bullets are real bullets, not images or stray hyphens.
• Fonts are common ones — Calibri, Arial, Helvetica, Georgia, Times New Roman — so substitution cannot wreck your spacing.
• Your contact line is in the body of the document, not in the page header.
• Section headings survived as text at a readable size.
• Document properties do not carry an old author name or an employer's name.
• You reopened the saved file, ideally on another device or in a browser preview, and it still looks right.

Naming the file so it survives a folder of 300 others

Your filename is metadata the recruiter reads before they open anything. It gets saved to a shared drive, attached to a candidate record, and searched for three weeks later.

The pattern is your name first, the document type second, and the company only if you are tailoring per application — which you should be, and which matching the posting's own keywords makes concrete. Use hyphens rather than spaces, since spaces become %20 in some systems and get mangled in others. Skip version numbers, dates, and anything in parentheses. Name your cover letter to match, so the two files sit next to each other alphabetically.

Common questions