Resume PDF or Word? How to Choose the Right File Format

Send the PDF. That's the short answer for the overwhelming majority of applications, and if you only read one line of this, that's the one. But "always PDF" is repeated so confidently that it obscures the handful of real cases where a Word file is genuinely the better choice — and the more common problem, which is that how you generate the file matters far more than which of the two you pick. If you're still producing the file, our guide to turning a rough draft into a polished PDF covers that end, and every layout in our ATS-safe template collection exports as real text either way. The reason this question exists at all comes down to parsing, which our explainer on what an ATS actually does unpacks, while our ATS-friendly resume guide and our breakdown of which graphics survive export handle the design side. The full format guide collection sits alongside all of it.

Why PDF is the default

A PDF fixes your layout. What you designed is what lands — the same margins, the same fonts, the same line breaks, on every device, in every email client, on every operating system. A .docx does not make that promise. Open a Word file on a machine without your fonts installed, or in a different version of Word, or in Google Docs, and text reflows. A resume that was a tidy one page becomes a page and a third, with a heading stranded at the bottom.

That matters because a hiring manager rarely tells you what went wrong. They just see a resume that looks slightly broken, and there's no way for you to know.

The old objection to PDFs — that applicant tracking systems can't read them — was a real concern roughly fifteen years ago. It isn't now. Every mainstream system parses text-based PDFs. What no system can read is a PDF that contains a picture of your resume instead of text, which is a different problem with the same symptom.

When Word is actually the right call

Four genuine cases:

The posting explicitly asks for .docx. Then send .docx. This isn't a technical question anymore — it's a following-instructions question, and someone will notice.

A recruiter or agency asks for an editable file. Staffing agencies routinely reformat candidate resumes onto their own letterhead before presenting them to a client. They need a document they can edit. Sending a PDF makes their job harder and yours slower.

An older or unusual internal portal rejects PDFs. Rare, but it happens, particularly with heavily customised legacy systems. If the upload field only accepts .doc or .docx, that's your answer.

You're told to fill in a template. Some employers, especially in the public sector and academia, supply a structured form to complete. Complete theirs; don't substitute your own design.

Outside those, PDF.

The thing that actually matters more than either

Both formats parse well when generated properly, and both parse terribly when they aren't. What separates a good file from a bad one isn't the extension:

• It has to contain real text. Select some text in your exported file and try to copy it. If nothing highlights, you've exported an image, and no system can read a word of it. This single check catches the most damaging failure in either format.
• Content has to sit in the main body. Text inside headers, footers and text boxes gets skipped by many parsers regardless of file type. Contact details in a decorative header band fail identically as a PDF and as a .docx.
• Fonts have to be embedded (PDF) or standard (Word). A PDF embeds its fonts by default; a Word file doesn't, which is exactly why the layout drifts on someone else's machine.

If your resume fails those, switching format won't save it. If it passes them, either format works — and you may as well take the one that also protects your layout.

Naming the file

A small thing that costs nothing and quietly helps. Jordan-Reyes-Resume.pdf is findable in a folder of three hundred applications. resume-final-v4-USE-THIS.pdf is not, and tells the reader something you'd rather it didn't. Use your name, the word "resume," and nothing else.

Frequently asked questions

Will a PDF stop my resume from being read by an ATS? No, provided it's a text-based PDF rather than an exported image. This is out-of-date advice from an earlier generation of software. Copy-paste the text out of your file to confirm it's real text; our five-minute parsing test walks through the full check.

What if the posting doesn't say which format to use? Send the PDF. It's the safer default because it preserves your layout for the human reader, and it parses just as well.

Should I send both? No. Attaching two files invites the reader to wonder which is current, and some upload forms accept only one. Pick the right one and send it alone.

Does Google Docs export a safe PDF? Yes — File → Download → PDF produces a proper text-based file. What isn't safe is exporting any document as an image, or screenshotting a resume and placing the screenshot into a PDF, which happens more often than you'd think.

What about .pages, .odt, or other formats? Don't. Convert to PDF first. A file the recipient can't open is functionally the same as not applying, and you won't get told.