Should I Send My Resume as PDF or Word? Test It Instead

Ask whether you should send your resume as PDF or Word and you will find two camps arguing with equal confidence.

One says Word parses more reliably and recruiters need to edit files. The other says text-based PDFs now match or beat Word across major systems, and PDF locks the layout you designed. Both cite testing. Both are partly right.

The reason the argument never resolves is that the difference between the two formats is small and genuinely disputed, while the thing that actually breaks resumes is large and undisputed — and it has nothing to do with the file extension.

Should I send my resume as PDF or Word?

The first row overrides everything else. Send a PDF to a posting that asked for Word and you hand the reader a small reason to stop. No format advantage is worth that.

Why do the experts disagree?

In fact, the history explains the disagreement better than either side does.

2010–2018. ATS engines could not reliably extract text from PDFs. “Always send Word” was correct advice.

2020–2022. Workday, Greenhouse, Lever and Eightfold upgraded their PDF parsers. PDFs became acceptable, then roughly equal.

2026. Some testing finds .docx still edges ahead across several engines. Other testing finds text-based PDFs match or beat Word for accuracy. The honest reading is that the margin is now small enough that it moves with the test.

That does not make the question meaningless — it makes it secondary. If two options differ by a few percentage points and a third factor decides outcomes outright, you should spend your attention on the third factor.

What actually breaks a resume?

Crucially, this is the part every source agrees on, and it dwarfs the format question.

Image-based PDFs fail completely. A scanned resume, or one exported as an image from a design tool, has no text layer. The parser sees nothing. This is the failure that produced the old “ATS can’t read PDFs” advice — one type of PDF failed, and the blame attached to the whole format.

Layout breaks both formats. Multi-column designs, text boxes, tables and graphics scramble extraction whether the file is PDF or Word. A two-column .docx is worse than a single-column PDF by a wide margin.

Container versus contents

The content structure matters more than the container. A simple, text-based file with standard headings parses reliably in either format. A designed file with text in image boxes fails in either.

Which is why testing your own document beats choosing a side. How an ATS works covers what the parser is actually doing with the file, and an AI resume checker shows you what it extracted rather than what you hoped it would.

A single-column PDF exported from Word. Standard headings, no text boxes, selectable text. Parses cleanly in every modern system.
A two-column .docx with a skills sidebar. The "safe" format, in the layout parsers read in row order — so the sidebar interleaves with the work history and the extracted record comes back scrambled.
The second file is the wrong choice despite having the "right" extension. Format is the small variable; layout is the large one.

Does an ATS reject you for the file format?

Worth stating clearly, because anxiety about whether to send a resume as PDF or Word is out of proportion to the actual risk.

The system does not throw your file away for being a PDF. What happens is worse in a subtle way: your fields extract incompletely, your skills do not register, and you simply do not surface in the recruiter’s searches. Nobody rejected you. You were never findable.

That distinction matters because it tells you where the risk lives — in extraction quality rather than in a rule about extensions.

Why do some employers ask for Word?

Reassuringly, none of these is a trick, and understanding them tells you when to comply happily.

Older systems. Government portals, small-company HR software and legacy enterprise tools sometimes still struggle with PDF.

Internal reformatting. Many companies convert every submission into their own template before circulating it. A Word file makes that a two-minute job.

Agency editing. Third-party recruiters frequently edit resumes before sending them on — often removing your contact information so the client has to go through them. If you are working with an agency, send Word and expect edits.

How do you export cleanly?

Broadly, four rules cover most export failures:

1. Use .docx, not .doc. The older format sometimes parses worse, and there is no reason to use it.

2. Export, do not print. “Save as PDF” or “Export as PDF” from Word or Google Docs produces a text layer. Printing to PDF from a design tool frequently does not.

3. Highlight-test the PDF. Open it and drag your cursor across a line. The text should highlight word by word. If it highlights as a block or not at all, it is an image.

4. Name the file properly. Firstname-Lastname-Role-Resume.pdf. Not Resume-final-v3.pdf, and definitely not Document1.docx.

That last one costs nothing and appears in a folder of a hundred applications alongside everyone else’s.

Career advice from 2010 to 2018 said "always Word, PDFs break ATS parsing." That was true then.

What should you actually do?

Whether you should send your resume as PDF or Word resolves into an order of operations:

1. Fix the layout first. Single column, standard headings, no text boxes or tables — the same structure beating AI resume screening depends on. This is worth more than every format consideration combined.

2. Keep both versions from one source. Export both from the same document so they cannot drift apart.

3. Follow the posting. Every time, without exception.

4. Default sensibly. PDF to humans, .docx to agencies and older portals.

5. Test the file you actually send. The copy-paste test, once, on the version in your folder — not on the one you remember making.

Finally, the reason this ordering matters is that people spend hours on step four and skip step one. A perfectly chosen file extension wrapped around a two-column layout still parses badly, and no amount of format optimisation rescues it.