The PDF-vs-DOCX debate is one of the longest-running pieces of resume folklore. Every few years a viral post resurrects the claim that "ATSes can't read PDFs," students panic, and the cycle repeats. In 2026, the technical reality has been settled for years — but the folklore persists. This post is the canonical breakdown of what's actually true.
The direct answer
Both PDF and DOCX parse correctly in modern ATSes. Submit PDF unless the application portal specifically asks for DOCX.
The historical advice "DOCX is safer for ATSes" applied to ATS systems built before 2017 — particularly older Taleo deployments and some corporate ATS systems built on legacy infrastructure. Modern ATSes (Workday, Greenhouse, iCIMS, Lever, Ashby, BambooHR, SmartRecruiters) parse text-based PDFs reliably.
Anecdotally, PDF is the dominant submitted format among the resumes we and other content authors in this space see — but I haven't found a primary-source recruiter survey that publishes the exact split, so I won't put a number on it. What's defensible is the bigger claim: there's no measurable callback-rate difference between formats when the resume is formatted cleanly.
What ATSes actually do with each format
The text-extraction step is the part that matters.
PDF parsing
ATSes use one of two PDF text-extraction approaches:
- Native text extraction — for PDFs created from Word, Google Docs, or our tailor tool, the text is stored as actual text in the PDF. Extraction is direct and reliable.
- OCR (optical character recognition) — for image-based PDFs (scanned resumes, photo-rasterized resumes), the ATS must OCR the image to extract text. This is slower and less reliable.
Most modern ATSes attempt OCR as a fallback if native text extraction fails, but OCR results are imperfect. The fix: always submit a text-based PDF, never an image-based one.
DOCX parsing
ATSes parse DOCX by reading the underlying XML structure. This is more straightforward than PDF parsing but has its own edge cases:
- Tables in DOCX sometimes get flattened or scrambled during text extraction (just like in PDF)
- Headers and footers in DOCX are sometimes ignored or extracted out of order
- Custom fonts that aren't installed on the parser's system fall back to defaults, occasionally affecting line breaks
For a well-formatted single-column resume with standard headers, both formats produce equivalent parses.
When to use each format
| Scenario | Use PDF | Use DOCX |
|---|---|---|
| Application portal accepts both | ✅ | |
| Application portal asks specifically for PDF | ✅ | |
| Application portal asks specifically for DOCX | ✅ | |
| Federal / USAJOBS application | ✅ | |
| Sending directly to a recruiter via email | ✅ | |
| Resume contains complex formatting that must preserve | ✅ | |
| Recruiter mentioned editing the resume | ✅ | |
| Legacy Taleo / older Oracle deployment | ✅ | |
| Designer/visual resume with custom fonts | ✅ |
The default is PDF. DOCX is for the specific cases listed above.
Why PDF wins by default
Three reasons.
Reason 1: Format consistency
PDFs render identically on every device and browser. The recruiter sees exactly what you submitted. DOCX rendering varies by Word version, font availability, and viewer software — your resume might display with different line breaks, missing fonts, or shifted content depending on what the recruiter opens it in.
For high-volume application portals where you don't know what software the recruiter uses, PDF removes the variable.
Reason 2: Print fidelity
If the recruiter prints the resume — which still happens at some employers — the PDF prints exactly as designed. DOCX printouts depend on the printer's interpretation of the Word file and can vary in margin, font rendering, and pagination.
Reason 3: Less risk of accidental edits
A PDF is read-only by default. A DOCX is editable. Recruiters who open a DOCX in Word can accidentally change formatting (selecting text, adjusting margins, etc.) before passing it along. PDFs are safer for the document's integrity.
The remaining cases where DOCX still wins
Case 1: Legacy Taleo deployments
Some pre-2018 Taleo / Oracle Cloud HCM implementations still parse DOCX more reliably than PDF. If you're applying to a Fortune 500 company with old-school HR infrastructure (some healthcare systems, some government contractors, some defense contractors), DOCX is a safer bet. You can usually identify these portals by their dated UI — Taleo's older interfaces have a distinctly 2010-era look.
Case 2: Federal applications (USAJOBS)
USAJOBS applications follow federal resume format requirements that include specific fields, longer descriptions, and sometimes DOCX-only uploads. Use the format the portal requests; don't second-guess federal application instructions.
Case 3: Recruiter wants to edit
If a recruiter explicitly says "send me a Word version so I can update the formatting" (some recruiters reformat resumes before submitting to clients), send DOCX. Don't send a Word version unsolicited — most recruiters don't want to edit the resume.
Case 4: Some international portals
Certain European and Asian application portals still default to DOC/DOCX submission. If you're applying internationally, follow the portal's stated preference.
Image-based PDFs: why they fail
A common student mistake: scanning a printed resume or photographing it, then submitting the resulting image-based PDF.
Image-based PDFs fail across every ATS because:
- Native text extraction returns nothing — the PDF contains an image, not text
- OCR is unreliable — even modern OCR misses some characters in resume scans, with errors clustering around proper nouns (your name, company names, university names)
- Some ATSes skip OCR entirely — defaulting to whatever native text extraction returned (which is empty)
The fix: never submit a scanned or photographed resume. If your resume started as an image, reconstruct it as a text-based PDF before submitting. Word, Google Docs, our tailor tool, and any standard resume builder produce text-based PDFs by default.
Canva, Adobe Express, and design-tool resumes
Visual design tools (Canva, Adobe Express, Figma) export PDFs that look beautiful but often parse poorly. The reasons:
- Multi-column layouts can scramble in ATS parsers — many older single-pass extractors read top-to-bottom, left-to-right, which interleaves a two-column resume's content unpredictably
- Embedded graphics and icons get stripped or mis-extracted
- Custom fonts sometimes cause character-encoding issues during parsing
- Decorative elements (sidebars, dividers, color blocks) sometimes get parsed as text
If you use Canva or similar tools, pick the simplest single-column template, remove all graphical elements, and use a standard font. Test the parse before submitting.
How recruiters actually receive resumes
Most resumes flow through this path:
- Candidate uploads the file to the company's careers portal (which is an ATS — Workday, Greenhouse, iCIMS, etc.)
- The ATS parses the file, extracts structured data, and stores both the parsed profile and the original file
- The recruiter views the parsed profile in the ATS interface, with an option to download or preview the original file
- For top candidates, the recruiter often downloads the original file and views it in a PDF reader or Word
In this flow, the PDF gets viewed twice: once as parsed text by the ATS, and once as a rendered document by the recruiter. PDF wins on the second viewing because rendering is consistent. DOCX risks rendering inconsistencies during the recruiter's manual review.
For more on how ATSes actually handle resumes, see What is an ATS?.
Quick decision flow
Does the application portal specify a format?
→ PDF only: submit PDF.
→ DOCX only: submit DOCX.
→ Both accepted, no preference: submit PDF.
→ Federal / USAJOBS application: submit DOCX (follow the portal's specific instructions).
Is the portal a known legacy Taleo deployment?
→ Yes: submit DOCX as the safer choice.
Are you sending directly to a recruiter via email?
→ Submit PDF unless the recruiter asks otherwise.
That's the full decision logic. PDF wins most cases.
Common mistakes
Mistake 1: Submitting a Google Docs link
Some students share their resume as a Google Docs URL instead of uploading a file. Don't. Recruiters can't reliably download Google Docs files for archiving, and ATSes can't parse a URL. Always download as PDF (or DOCX if requested) and upload the file.
Mistake 2: Submitting a .pages file (Apple Pages)
Apple's Pages format (.pages) almost never parses in any ATS. Always export to PDF before submitting.
Mistake 3: Submitting an .rtf file
Rich Text Format parses inconsistently. Always export to PDF or DOCX.
Mistake 4: Versioning errors in DOCX
If you submit a DOCX created in Word 365 but the recruiter has Word 2010, some formatting may render incorrectly. PDF eliminates this risk.
Where to read more
For more on ATS behavior and resume formatting:
- What is an ATS? — how the major ATS systems actually work
- How to tailor your resume to a job description — tailoring affects which keywords appear in the parse
- How long should a resume be? — page-count rules that affect both formats
- Resume objective vs summary — section header parsing affects both formats equally
Or paste your resume into our free tailoring tool — we export both PDF and DOCX so you have whichever format the portal requests, both ATS-friendly by default.