PDF or Word? Which résumé file format to send, and when

I've changed industries three times: heavy civil to telecom, telecom to facilities construction, facilities to robotics. Every one of those jumps meant sending out more résumés than I can count. And more than once I stopped, hovered over the export button, and asked the same small question everybody asks: do I send this as a PDF or a Word doc?

It feels like a tiny decision. It mostly is. But it's the kind of tiny decision that can quietly cost you an interview if you get it wrong, so it's worth two minutes to get it right.

Here's the short version, then the reasons.

The short answer

Send a PDF, unless the application specifically asks for a Word document.

That's it. PDF is the safe default for almost every situation: emailing a recruiter, uploading to a company's careers page, attaching to a LinkedIn message. Word (.docx) is the exception you reach for when someone tells you they want it.

If you only remember one line from this post, that's the line.

Why PDF is the default

A PDF looks the same everywhere. The spacing you set, the fonts you picked, the way your bullets line up — all of it stays put on the hiring manager's screen, on their phone, and on the printer in the office they still print things in.

A Word document doesn't promise you that. Open a .docx on a machine that doesn't have your font, or in a different version of Word, or in Google Docs, and the layout can shift. A bullet wraps to a second line. Your one-page résumé becomes a page and a half with a lonely last line hanging on page two. You did the work to make it clean; the format shouldn't get to undo it in transit.

There's an old fear that PDFs confuse applicant tracking systems — the software that parses your résumé before a human ever sees it. That was a real problem years ago. It mostly isn't anymore. Modern parsers read text-based PDFs fine. The thing that actually breaks parsing isn't the file extension — it's what's inside the file. More on that below, because it matters more than the PDF-versus-Word argument does.

When to send a Word document instead

There are a few honest exceptions. Send .docx when:

• The application form only accepts .doc or .docx. Some older portals do. Follow the instructions in front of you — they win over any general rule.
• A recruiter or staffing agency asks for it. Agencies often reformat your résumé onto their own template or strip your contact details before they send you to their client. They need an editable file to do that. This is normal; give them the Word version.
• You're handing it to someone who's going to edit it — a mentor marking it up, a friend in the industry adding notes. Editable is the point there.

Notice the pattern: you send Word when someone downstream needs to change the file. You send PDF when you want it to arrive exactly as you built it.

The file mistakes that actually get you skipped

The format debate gets all the attention, but these are the things that quietly hurt people more:

1. A résumé that's really a picture. If you designed your résumé in a graphics tool, or scanned a printed copy, the "text" might be an image. A human can read it; the parsing software can't — it sees a blank. Test it in ten seconds: open your PDF and try to highlight a line of text with your cursor. If you can select the words, you're good. If you can't, that file is a photo, and half the systems it lands in will read nothing.

2. A vague file name. "resume.pdf" and "resume-final-v3-USE-THIS.pdf" both land in a recruiter's downloads folder next to forty others. Name it so it's obvious whose it is: Scot-Carl-Robotics-Engineer.pdf. Your name, and ideally the role. It's a five-second habit that makes you easy to find and easy to forward.

3. A share link instead of a file. Don't paste a Google Docs or Pages link and call it done. Links can break, can ask the reader to request access, and can quietly show them your edit history. Export the actual file and attach the actual file.

4. Fonts and columns the parser trips on. Heavy multi-column layouts and unusual fonts can scramble the reading order when software pulls the text out. You don't need a boring résumé — you need one where the text still reads top-to-bottom, left-to-right when it's flattened. Simple beats clever here.

One master, exported per job

Here's the workflow that saved me the most time across those three career changes: keep one master résumé, and export a fresh copy for each job you apply to. You tailor the wording to the posting — that part matters, and I've written about how to tailor a résumé to a job description separately — then you export. PDF for the human, Word only if they asked.

You don't want to be maintaining five different files in three formats and losing track of which one you sent where. One source of truth, exported on demand.

This is the part where I'll be upfront that I built a tool for exactly this. ResumAI keeps your master résumé in one place and exports every template as both PDF and DOCX — both formats included on every plan, no download paywall waiting at the finish line. So you tailor once, then send whichever format the situation calls for without rebuilding anything. That's the whole reason the dual export exists: the format shouldn't be a thing you have to worry about the night before an application is due.

The two-line rule

If you want to skip everything above: send a PDF by default. Send Word only when the form or the recruiter asks for it. Make sure your text is selectable, and name the file with your name on it.

Get those right and the file format stops being something that can cost you. Then you can put your energy where it actually moves the needle — the words on the page, and the job you're going after next.