The PDF-vs-Word debate has been one of the most persistent and least useful arguments in resume advice for ten years. Career advisors regularly tell candidates that "Word is safer" or "PDF breaks the ATS." Both claims are usually wrong in 2026. Modern ATS systems — Greenhouse, Lever, Workday, Ashby, and the contemporary versions of Taleo and SuccessFactors — parse PDFs cleanly. Word still works, but it's not the default in most pipelines anymore.

This post is the honest current picture, including the small number of cases where the advice is still relevant.

What ATS systems actually do with each format

A modern ATS does roughly the same work for both formats:

1. Extracts text from the file. Both PDF and Word are extractable. PDFs use the embedded text layer; Word files extract directly from the XML structure.
2. Identifies structure. Headers, dates, role titles, sections. Both formats produce parseable structure if the resume is laid out cleanly.
3. Matches keywords. The extracted text is searched against the job description's keywords. Format-agnostic.
4. Stores the original file. The recruiter can open the file later in its native format.

The places where parsing breaks are not usually about the file format. They're about layout choices — two-column designs, text-in-images, fonts that don't have a parseable equivalent, header/footer text that gets ignored. PDF doesn't fix these; Word doesn't fix these.

For the broader ATS-parsing context, see how-applicant-tracking-systems-work and ats-friendly-resume-format-myths.

What each format does well

The compare-list is the honest filter. PDF preserves your exact layout — what you designed is what the recruiter sees. Word allows editing on the recruiter's side and can shift layouts when the machine doesn't have your fonts. For modern hiring, PDF's preservation outweighs Word's editability by a wide margin.

The exception: some recruiters genuinely prefer Word because they want to lightly edit the resume before sharing it with hiring managers (removing salary expectations, formatting consistently). This is a real preference at some agencies and headhunters. If a recruiter explicitly asks for Word, send Word.

What the ATS-format preference actually looks like

The numbers above are roughly what ATS vendor documentation and parsing tests find for the major systems in 2024-2025. PDF is the default expectation in roughly 78% of modern deployments. Word still works in nearly all of them. Word is preferred in only a small minority — typically older F500 implementations and government pipelines.

The implication for most candidates: submit PDF unless the application explicitly asks for Word. If the application says "upload your resume" with no format specified, PDF.

The narrow cases where Word matters

A few situations where Word is still the right answer:

Government and federal applications. USAJobs and many state-level systems explicitly request Word format. Send Word.

Some legacy F500 pipelines. Specifically older Taleo or SuccessFactors deployments. The application form usually tells you. Send Word.

Recruiter agencies that resell the resume. Some staffing agencies want Word so they can edit your resume before submitting to their client. They'll tell you. Send Word — for them only.

Applications that explicitly ask for Word. Read the upload prompt. If it says ".docx preferred," send .docx. The instruction is rarely arbitrary.

In all four cases, the application or recruiter has communicated the preference. Don't override it.

How file format actually affects outcomes

The honest finding: file format very rarely determines outcome. Layout, content, and keyword alignment do almost all of the work. The format choice contributes at the margin in legacy ATS deployments where parsing genuinely differs between formats — and even there, the effect is small compared to the impact of a clean layout.

The implication: don't spend more than 30 seconds on the format question. Default to PDF. Switch to Word when explicitly asked. Move on.

What actually breaks parsing — across both formats

The real layout traps that break ATS parsing, regardless of file format:

Multi-column designs. Many ATS systems read left-to-right across the entire page, mixing the columns into a jumbled mess. Single-column layouts parse cleanly.

Text inside images or graphics. Charts, badges, infographics, and icons with embedded text don't get extracted. Anything load-bearing must be live text.

Header and footer text. Some older ATS implementations ignore content inside Word headers/footers entirely. Put contact info in the body of the document, not in the header.

Non-standard fonts. If the ATS can't render the font, the parser may substitute or fail. Stick to standard fonts: Calibri, Helvetica, Arial, Inter, Times New Roman, Georgia. Skip anything decorative or distributor-locked.

Tables. Modern ATS handles simple tables; complex nested tables don't always parse. If you use a table for layout (skills grid, contact info grid), keep it shallow.

For more on the actual layout decisions, see resume-margins-and-spacing and resume-mistakes-that-auto-reject.

How to test your file

If you want to confirm your resume parses cleanly:

1. Open it in a different program. PDF: open in a different PDF viewer than the one you used to create it. Word: open in Google Docs and see what shifted. If the layout breaks, the ATS will see something similar.
2. Copy-paste the text into a plain-text editor. What you see is roughly what the ATS will extract. If the order is jumbled, or chunks of text are missing, the parsing will be similarly broken.
3. Use a free parser like Jobscan or Resume Worded. They simulate the ATS extraction. Imperfect but useful.

A clean parse looks like reverse-chronological role-by-role text, with company names, dates, and bullets in the right order. A broken parse looks like fragments — random words from the sidebar, dates separated from companies, bullet text missing.

The naming convention that helps

Save your file as firstname-lastname-role.pdf, not Resume_FINAL_v3.pdf. The recruiter sees the filename and the cleaner one signals attention to detail. It's a tiny variable but the kind of thing recruiters notice in the negative direction more than the positive.

What this isn't

A few clarifications:

• It's not 2015 anymore. The PDF-breaks-ATS warning is outdated for modern systems. Don't optimize for a problem that's mostly solved.
• It's not a substitute for a clean layout. Both formats fail when the layout is broken. Layout is the load-bearing variable; format is downstream.
• It's not a universal rule. Read the application's upload prompt. If it asks for Word, send Word.

The short version: PDF by default, Word when asked. Modern ATS handles both well. Spend your effort on layout and content, not on format. The format debate is mostly a holdover from older systems and doesn't change outcomes meaningfully.