Short answer: yes, every major ATS in 2026 reads both PDF and Word — as long as the PDF is text-based. The longer answer matters because "text-based" excludes a lot of resumes people send.
Here's the breakdown, plus the format choice that gives you the safest result.
What every major ATS accepts
| ATS | .docx | .pdf (text-based) | .pdf (image-based) | .txt / .rtf |
|---|---|---|---|---|
| Workday | ✅ | ✅ | ❌ | ✅ |
| Greenhouse | ✅ | ✅ | ❌ | ✅ |
| Lever | ✅ | ✅ | ❌ | ✅ |
| iCIMS | ✅ | ✅ | ❌ | ✅ |
| Taleo (Oracle) | ✅ | ✅ | ❌ | ✅ |
| SmartRecruiters | ✅ | ✅ | ❌ | ✅ |
| Ashby | ✅ | ✅ | ❌ | ✅ |
The "no" column is the one to pay attention to. Image-based PDFs are PDFs where the content has been rendered as an image — the text isn't selectable or searchable. No parser can read them. This happens with:
- Resumes exported as PDF from design tools (Canva, Figma) when fonts aren't embedded or the export settings flatten everything to image.
- Resumes that were printed and then scanned.
- Phone photos of a printed resume saved as PDF.
- Some "pretty" templated resumes from non-standard builders.
The 10-second test
Open your resume PDF. Try to select text and copy a paragraph. Paste it somewhere.
- If you got selectable text: The PDF is text-based. Every modern ATS can read it.
- If you couldn't select anything: The PDF is image-based. Re-export, switch tools, or send a Word document instead.
Three seconds, every time, before you submit.
The case for PDF
- Layout fidelity. Your formatting renders the same way for the recruiter as it does in your local Word. Word documents can shift fonts and spacing when opened in another version of Word.
- Tamper-resistant. A recruiter can't accidentally edit a PDF.
- Professional polish. A clean PDF reads as more finished than a Word file with Track Changes still on.
The case for Word (.docx)
- Most reliable parse. Even though all major ATS can parse text-based PDFs, the Word parse is virtually always cleaner — fewer formatting artifacts, more consistent section detection.
- Recruiter editing. Some agency recruiters need to add a cover sheet or remove your contact info before submitting you to a client. Word is easier for them.
- Faster to update. If you're sending a lot of applications, working in Word and resaving to PDF only when needed is faster than maintaining a PDF.
The verdict
If the application portal lets you pick:
- For most roles: Submit
.docx. Marginal parse advantage, no real downside. - For design / creative roles, or when sending directly to a hiring manager: Submit PDF. The visual quality matters more, and you're past the ATS.
- For agency or contract recruiters: Word. They almost certainly need to edit.
If the portal forces a specific format, submit what they ask for. Don't second-guess clear instructions.
The Google Docs gotcha
"Download as PDF" from Google Docs gives you a text-based PDF (good). "Download as .docx" gives you a Word file (good). But "Print → Save as PDF" sometimes produces a flattened, image-like PDF depending on your browser. Use the explicit File → Download → PDF option.
How to make a "designer" resume parser-safe
If you have a visually elaborate PDF from Canva or Figma, two questions:
1. Is the text selectable? If yes, the ATS can parse it. The layout still matters — multi-column designs may scramble, even with selectable text.
2. Is your contact info, name, and section headers in actual text (not as image elements)? If your name is a hand-drawn logo and your section headers are stylized graphics, the parser will miss them. Switch to plain text for these elements.
The safer pattern for design-forward applicants: maintain two versions. A Word/text-PDF version for ATS portals, a designed version to send when a hiring manager asks for it.
Common myths to discard
- "ATS can't read PDFs at all." True in 2010, false in 2026. Modern ATS handle text-based PDFs as well as Word.
- ".docx is universally better." Only marginally, and only for parsing. A bad Word resume (multi-column, tables, header content) still parses badly.
- "Convert your resume to a TXT file for safety." Submitting a plain text file when the portal accepts .docx or .pdf usually loses formatting and looks unfinished. Don't.
- "PDFs are slower to upload, hurting your application." No portal scores applications on upload time.
- "Image-based PDFs are fine because recruiters open them." They might, but you don't get to the recruiter if the ATS ranks you near the bottom of every keyword search.
What about non-standard formats?
- Pages (Apple): Export to .docx or text-based PDF before submitting. Native .pages files don't parse on most ATS.
- Google Docs link: Don't paste a link unless the portal asks for one. Upload an exported .docx or PDF instead.
- LinkedIn "Easy Apply" auto-PDF: Fine. LinkedIn produces a clean, parser-friendly version.
- Notion or other web-based tools: Export to PDF and verify with the copy-paste test. Some Notion exports are surprisingly clean; others are not.
Download a parser-safe template in both .docx and .pdf
Free, ATS-tested, available in Word format for editing — exportable to clean text-based PDF when you need one.
Browse TemplatesFAQ
Does the file name affect parsing?
No. But it affects the recruiter's perception. Use FirstName_LastName_Resume.pdf, not resume_v3_final_FINAL_USE_THIS_ONE.pdf.
Can I submit multiple file formats?
Some portals allow it, most don't. If allowed, send the .docx as the primary resume and the PDF as a supporting document — but it's overkill in most cases.
Should I password-protect my resume?
No. The ATS won't enter a password, and the resume will fail to parse.
What about a video resume?
Skip, unless the role explicitly invites one. Most ATS don't process video, and recruiters generally don't watch.