Resume PDF vs Word: Which File Format Actually Gets You Hired

Here is the short answer: for most applications, send a clean text-based PDF, unless the posting or the recruiter asks for Word. That one sentence covers maybe 80% of cases. The rest of this guide covers the other 20%, because that is where people actually lose out: the staffing-agency submission, the government portal, the email to a hiring manager, the resume that looks perfect on your screen and arrives as scrambled text on theirs.

The honest truth underneath all of it is that the file extension matters far less than what is inside the file. A well-built PDF beats a messy Word document every time, and a clean Word document beats a designed-to-death PDF. Format is the envelope. Content and structure are the letter.

What the numbers actually say

Start with the biggest survey on this exact question. Resume Genius's 2026 statistics roundup, which draws on its 2024 Hiring Trends Survey and 2025 Hiring Manager Survey, asked hiring managers which file formats work best for applicant tracking systems. The answers were split, not settled: 53% preferred a text-based PDF, 43% favored a Word (.docx) file, 34% liked a PDF with light design elements, and only 13% said design-heavy or graphic resumes work best for an ATS. Note that those numbers add up to more than 100% because managers could pick more than one. The takeaway is not that PDF won. It is that plain, text-based files won in both formats, and heavily designed files lost in both.

A second survey points the other way, and the contrast is instructive. Jobseeker's 2025 survey of 1,013 HR professionals across 59 countries found 76.8% wanted resumes submitted as PDFs, against just 12% who preferred Word files. Why the gap? The two surveys asked different questions. Resume Genius asked what works best inside an ATS. Jobseeker asked what recruiters want to receive. A recruiter opening your file on a laptop cares about how it looks. A parser ingesting it into a database cares about how it reads. Both audiences matter, and they do not always want the same thing.

The scale of the machine audience is worth grasping. Jobscan's 2026 ATS usage report detected an applicant tracking system on the careers pages of 487 of the Fortune 500, or 97.4%. Almost every large employer runs one. But that does not mean the machine rejects you for picking PDF. Enhancv's 2025 study of 25 US recruiters found 92% said their ATS does not automatically reject resumes over formatting or content, and its 2026 myth-busting parse test, run across popular ATS platforms, scored Microsoft Word documents at an average of 88% and PDFs at 85%. Three points apart. That is a rounding error compared with the damage a two-column layout or a scanned image can do.

The distinction that matters more than PDF vs Word

If you remember one idea from this article, make it this one: the real divide is not PDF versus Word. It is text versus image.

A text PDF is what you get when you export from Word or Google Docs. It looks like a document, but underneath it is a layer of real, selectable text that software can read. An image PDF is what you get when you scan a printed page, or export from a design tool that flattens everything into a picture. To a human they look identical. To a parser, the second one is a blank page. One analysis of parsing success rates put image-based PDFs at around 15% parsing success, against roughly 75% for text-based PDFs and 85% for simple .docx files. The exact percentages vary by study, but every study agrees on the ranking: image files fail, everything else mostly works.

Test yours in ten seconds. Open your PDF, try to select a sentence with your mouse, and paste it into a plain text editor. If the words arrive in the right order, you have a text PDF and you are fine. If nothing selects, or the pasted text comes out scrambled, you have a problem no file-extension choice will fix. Re-export from your word processor instead of scanning or screenshotting.

The same logic explains why design-heavy resumes fail. Columns, tables, text boxes, icons, and graphics do not survive parsing gracefully in either format. Enhancv's 2026 test found single-column templates parsed skills sections at 65% on average, while double-column templates managed only 46%. A 2026 experiment that ran one identical resume through four real ATS parsers in 36 layouts found contact details came back perfectly in every layout, but skills and work-history segmentation broke differently on different parsers. The file format was never the variable that broke things. The layout was.

When PDF is the right choice

Send a PDF when a human being is the first audience. That means emailing a hiring manager directly, sending your resume to someone in your network, uploading it to a portfolio site, or attaching it to a LinkedIn message. PDFs look identical on every device, every operating system, and every version of every reader. A Word document, by contrast, can reflow when the recipient's version of Word substitutes a font you do not have, and I have seen a carefully aligned one-pager arrive as a two-page mess with a bullet list spilling onto page two. A PDF cannot do that to you. It is also read-only in practice, which matters when you do not want a recruiter casually editing your dates before forwarding your resume.

PDF is also the right default when the posting says nothing about format. Most job boards accept both, and when nothing is specified, the format that preserves your presentation wins. ResumeCoach, The Muse, and several other career guides all land in the same place: no instruction means PDF. It is the safer-looking choice, it opens on phones without extra software, and it signals that the document you sent is the finished version, not a draft.

One more case for PDF: the UK and European market. In the UK, where the document is called a CV rather than a resume, PDF is the overwhelming norm for emailed applications, and the same text-versus-image rule applies. A UK recruiter receiving a .docx they did not ask for will not reject you for it, but a PDF reads as the finished article in a way Word does not.

When Word is the right choice

Word wins in four situations, and in all four the reason is the same: somebody else needs to work with your file.

First, when the posting explicitly asks for it. This rule outranks everything else in this article. If the listing says ".docx only" or "Word format please," send Word. Ignoring a stated instruction is a worse signal than any format advantage, because it tells the employer you do not read instructions. The Muse's career coaches put it bluntly: the employer is the authority on what they want, and a candidate who sends PDF when Word was requested risks not being read at all.

Second, when you are working through a recruiter or staffing agency. Recruiters routinely need an editable file so they can strip out your contact details before sending your resume to their client (so the client cannot cut them out of the deal), add their own branding or cover sheet, or fix a formatting glitch. Former recruiters say this openly: if you send a PDF to an agency, they may ask you to resend it as Word, or worse, retype it. Send Word first and save everyone a round trip.

Third, when you are applying through an older corporate or government portal. Some legacy systems and government application sites were built around Word and still parse .docx more reliably than PDF. The USAJOBS federal system accepts both, but plenty of state, municipal, and older enterprise portals do not handle PDFs as gracefully. If the portal's upload screen lists .docx first, or PDF uploads have ever failed you there, go with Word.

Fourth, when the resume will be edited collaboratively, for example a career coach or mentor reviewing it, or an internal referral where your contact wants to add a note. Word is a working document. PDF is a finished one. Use each for what it is.

The decision table

If you take nothing else from the table, take this: when in doubt, keep both versions ready. Maintain your master resume in Word or Google Docs, and export a fresh PDF from it for every application. That way the "which format" question becomes a ten-second decision instead of a rewrite, and the two versions never drift apart.

What actually breaks a resume file, in either format

Since format is not the main risk, here is the real checklist of things that break parsing, drawn from the parse tests above and from earlier ZenWrit guides on ATS-friendly resumes:

Two-column layouts. The parser reads left to right across the whole page, not down each column, so your 2023 job can end up merged with your 2019 degree. Single column, always.

Tables and text boxes. Many parsers skip text inside boxes entirely, or read it in the wrong order. If your skills live in a table, some of them may simply vanish from the parsed record.

Contact details in the header or footer. Several parsers never look there. Put your name, phone, email, and city in the body of the document, at the top, in plain text.

Graphics, icons, and images of text. A skills bar chart, a star rating, or a logo with your job title baked into it is invisible to a parser. If it matters, write it as text.

Unusual fonts and symbols. Stick to standard fonts, standard section headings like Experience and Education, and Month Year dates. Fancy headings like "My Journey" confuse section mapping.

The scanned or photographed resume. Already covered, but worth repeating because it is the single most destructive choice: an image PDF can fail completely while looking perfect to you.

None of these are format problems. They are construction problems, and they hurt a Word file just as surely as a PDF. That is why two candidates can send the same format and get different results: one built a clean single-column document, the other built a poster.

Naming the file and testing it before you send

Two small habits prevent an embarrassing number of failures.

First, name the file like a professional. Use Firstname-Lastname-Resume.pdf, or Firstname-Lastname-Role-Resume.pdf when tailoring for a specific job. Recruiters download dozens of files a day; "Resume_Final_FINAL_v3.pdf" is a small indignity that also makes your file hard to find later. Never include the word "final" or a version number. The file you send is, by definition, the final one.

Second, test the exact file you are about to send, not the master copy. Export the PDF, then run the ten-second paste test on it. If you are sending Word, open the .docx on a different machine or in Google Docs and check that nothing reflowed. Then run it through a free ATS checker and read the extracted text section by section, not just the score. The score is a vendor's invention; the extracted text is what an employer would actually see. If a job title, a date, or a skill is missing from the extraction, fix the layout and re-export. Retest after every export, because a PDF exported from a different program can parse differently from the Word file it came from.

The bottom line

The PDF versus Word debate survives because it feels like a decision with a right answer, and people like right answers. The data says it is mostly a tie: 53% of hiring managers in Resume Genius's 2026 roundup prefer text-based PDF for ATS compatibility, 43% prefer Word, and Enhancv's hands-on parse test separated the two by three points, 88% to 85%. The format that actually loses is the one nobody recommends: the image PDF, the designed-to-death PDF, the two-column poster. Those fail in any extension.

So keep it simple. Master copy in Word or Google Docs. Clean single-column layout, standard headings, contact details in the body. Export a text PDF as your default, keep the Word version beside it, and follow the posting's instructions whenever they exist. Then stop worrying about the extension and spend the saved energy on the words inside the file, because that is what gets you the interview.

Want to check whether your resume survives a real parse? Run it through ZenWrit's free ATS resume checker at https://zenwrit.com/ before your next application. It shows you what a parser actually extracts, section by section, so you can fix the layout before an employer ever sees it.

Frequently asked questions

Should I send my resume as PDF or Word? Default to a text-based PDF unless the posting or recruiter asks for Word. PDF preserves your formatting on every device, while Word is the better choice when someone needs to edit your file, such as a staffing recruiter or an older application portal.

Do ATS systems reject PDF resumes? No, not modern ones. Jobscan's 2026 report found ATS software on 487 of the Fortune 500 careers pages, and those systems parse text-based PDFs routinely. What they struggle with is image-based PDFs, which have no text layer to read, and heavily designed layouts with columns, tables, and text boxes.

Is a scanned PDF resume okay? No. A scanned resume is an image, not a document, and parsers can fail on it almost completely. Always export your PDF from Word or Google Docs so it contains real, selectable text, and verify with the copy-paste test before sending.

What if the job posting says PDF or Word, either is fine? Send PDF. When both are accepted, PDF gives you the presentation advantage: it looks exactly as you designed it on the recruiter's screen, while a Word file can reflow if their software substitutes fonts.

Do recruiters prefer Word because they can edit it? Staffing and agency recruiters often do, because they redact contact details and add branding before forwarding your resume to a client. Direct hiring managers usually prefer PDF, because they just want to read it. Match the format to who is receiving it.

Does the file format affect my ATS score? Barely. Enhancv's 2026 parse test scored Word documents at 88% and PDFs at 85% on average, a three-point gap. Layout choices like single versus double column move the result far more than the extension does. Fix the layout first, then pick the format the situation calls for.

Related reading: What "ATS-Friendly" Really Means · What Is a Good ATS Score? · The Best Free ATS Resume Checkers, Tested · How to Find Resume Keywords · Resume Summary vs. Objective