PDF vs Word Resume: What ATS Actually Prefers in 2026

The Old Answer Is Outdated

For years the standard advice was "always submit Word, never PDF." That was based on 2015-era ATS systems that struggled with PDF structure. Modern ATS built after 2020 (Greenhouse, Lever, Ashby, modern Workday) handle both formats nearly identically.

But the old advice still works for a reason: older ATS that are still in production (Taleo, iCIMS legacy, BrassRing) genuinely struggle with PDF. So the right answer depends on which ATS is parsing your file.

What Each ATS Handles Well

Modern (2020+) — Both formats work

• Greenhouse
• Lever
• Ashby
• Workday (modern deployments)
• SmartRecruiters
• Recruitee
• JazzHR

Legacy — Prefer .docx

• Oracle Taleo
• iCIMS (legacy deployments, 2018 and older)
• BrassRing
• SAP SuccessFactors (older tenants)

In the US and Europe, about 30% of large employers still run legacy ATS. Which means PDF is risky as a default — if you're applying to a Fortune 1000 company, you might be hitting a legacy system.

What Breaks PDF Parsing

When ATS parse PDFs, the failure modes are specific:

• Multi-column layouts — ATS reads left-to-right, top-to-bottom. A two-column resume often gets read column-by-column, merging unrelated lines.
• Text inside graphics — If your skills section is rendered inside an SVG or image, most ATS can't read it. Your "Kubernetes, Python, Docker" skills become invisible.
• Fancy fonts — Non-standard fonts may get substituted when the PDF is parsed, occasionally corrupting characters.
• Headers and footers — ATS often skip these entirely, so if your name and contact info are in the header, they may not get parsed.
• Scanned PDFs — A PDF that's actually a scanned image (not digitally-typed text) is unreadable to ATS. This happens when people print a Word doc and scan it.

What Breaks Word Parsing

Word has fewer failure modes but they still exist:

• Text boxes — Common in fancy Word resume templates. ATS often skip them entirely.
• Tables — Same column-reading problem as PDF. A two-column table splits your sections.
• Drawn shapes and SmartArt — Invisible to ATS.
• .doc vs .docx — .doc is the old binary format. Some modern ATS won't accept it. Always save as .docx.

The Safe Default for 2026

If a job posting doesn't specify a format, upload a .docx file. Here's the full reasoning:

1. Every modern and legacy ATS handles .docx well. PDF is risky specifically against legacy systems.
2. Recruiters often re-save resumes into their own template. .docx is editable, PDF isn't.
3. .docx files tend to be smaller (often half the size of PDF), which matters for upload size limits on some ATS.

If the posting specifically asks for PDF, use PDF. Always follow the posting. But if you get to pick, .docx is the safer choice.

How to Export Cleanly

From Google Docs: File → Download → Microsoft Word (.docx). Don't use "PDF" export unless required.

From MS Word: Save As → .docx. Avoid "Save As PDF" with compression — it can corrupt embedded fonts.

From LaTeX (Overleaf): This is the one case where PDF wins by default. LaTeX-generated PDFs are digitally typed, cleanly structured, and parse well in modern ATS. If you use LaTeX, stick with PDF.

From Canva or fancy design tools: Stop. Canva resumes routinely fail ATS parsing because they use SVG-based layouts. Rebuild the resume in Word or Google Docs using a simple single-column format. Looks boring. Passes filters.

The Real Test

The only way to know your file parses correctly is to run it through an ATS scoring tool. Upload your resume to something like ATSGuard and a real ATS parser breaks it down the same way a company's system would. If the parse misses your skills section or misreads your dates, fix the formatting before you apply.