PDF or Word? The Resume File Format Recruiters Actually Want
PDF by default, Word when asked, never a screenshot. The reasoning, the four cases where Word wins, and how to keep both versions identical in content without maintaining two files.
The format question gets asked as if it were a matter of taste. It isn't. Each format is a promise about what happens to the file after you send it, and recruiters have strong, mostly unstated preferences based on that.
The default: PDF
Send a PDF unless something tells you otherwise. Three reasons, in order of importance:
- It looks the same everywhere. A Word file rendered on a recruiter's laptop with different fonts installed can reflow onto a second page, orphan a heading, or swap your typeface for something worse. A PDF is a picture of your intent.
- It can't be edited by accident. Agencies sometimes strip contact details from Word files before forwarding; hiring managers sometimes leave tracked changes in. A PDF stays yours.
- Modern parsers read PDFs well. The old advice that "ATS can't read PDF" dates from a time when many PDFs were scanned images. A text PDF exported from a document tool is fully parseable. (The ATS check article shows how to verify yours.)
The one hard requirement: the PDF must contain text, not a picture of text. If you can select a word in it, you're fine.
When Word wins
Four situations, and only these, where a .docx is the right file:
- The form asks for it. Some older applicant tracking systems still say "Word only" or reject PDFs silently. Comply; it's their pipe.
- A recruiter wants to edit it. Agencies often reformat resumes into their own template before showing clients. Sending Word saves them the retyping, and retyping is where your numbers get mangled.
- Government and public-sector applications. Many specify .docx, and some mail-merge the contents into standardized forms.
- You've been told the parser struggles. Rarely true today, but if a company says so, believe them.
In all four cases the Word file should be plain: single column, real headings, no text boxes, no tables for layout. Tables and text boxes are the two things Word parsers drop most often, and they're also what breaks when the file opens on a different machine.
Why "just export the PDF as Word" produces a bad Word file
Converting a designed PDF into .docx yields a document full of absolutely positioned text frames. It looks right for one second and falls apart when anyone types into it. The honest Word version of a resume is a different layout of the same content, not a converted picture.
That is why Job SuitUp exports two things from the same data: the PDF in whichever of the fifteen templates you chose, and a Word document that is deliberately single-column with standard headings, your accent color on the section rules and your font choice mapped to typefaces Word ships with. Bold phrases, links and custom sections carry over; the layout does not pretend to. One source, two honest outputs, nothing to keep in sync by hand.
File naming, because it's read before the resume is
Recruiters see the filename in their inbox and in the tracking system. Use First Last - Resume.pdf or, when tailoring per company, First Last - Company.pdf. Avoid resume_final_v3 (2).pdf, which says exactly what it looks like it says. Your exported files should be named for you automatically; if they aren't, rename before sending.
Things that are never the right format
- Screenshots or images. Unparseable, unsearchable, often blurry.
- Google Docs links. They require the reader to click out, and sharing settings fail more often than people think. A recruiter who asked for your resume wants a file they can keep, not a document they have to request access to.
- Pages, ODT, RTF. Convert to PDF.
- Zip files. Nobody unzips a resume.
FAQ
Does the PDF need to be "ATS-optimized"? It needs to be text-based, single-column for portal submissions, and use standard section headings. That's the whole optimization. The template decision rule covers when a creative layout is fine.
My PDF is 4 MB. Is that a problem? Some portals cap uploads at 1 or 2 MB. Large sizes usually come from an embedded photo or an unoptimized font. Export again without the photo (most markets don't want one anyway) or use a standard font.
Should I send both files? Only when asked. Two attachments invite the question "which one is current?" Send the one that fits the channel.
Is a .docx exported from a template as safe as one I wrote in Word? If the export is genuinely single-column with real headings and no text boxes, yes. Open it, click into a bullet, and check that the cursor lands in normal flowing text. If it does, it's safe.