Back to Blog

PDF vs Word (.docx) for Resumes: Which Format Actually Passes ATS in 2026?

The PDF vs Word debate isn't as settled as most advice claims. What actually happens when each format hits Workday, Taleo and Greenhouse.

The 'Always Submit Word' Rule Is Mostly Outdated

If you've spent any time on career forums or LinkedIn, you've seen this advice repeated endlessly: always send your resume as a Word document, ATS can't read PDFs. It was reasonable guidance around 2012. In 2026, it's wrong for the majority of job applications.

Most modern applicant tracking systems parse PDFs without issue. The real question isn't which format is universally better. It's which format the specific system you're submitting to actually reads cleanly, and that depends on the ATS, the employer's setup, and whether your file is built for parsing or built to look good.

Here's what actually happens when your resume hits Workday, Taleo, and Greenhouse.

TL;DR

  • Modern ATS platforms including Greenhouse, Lever, and Workday generally parse PDFs well
  • Older enterprise systems and public-sector portals may still prefer .docx
  • Always check the job posting for accepted file types before submitting
  • A clean, single-column, text-based PDF is the safest default when no format is specified
  • Never submit a designed PDF with graphics, columns, or text boxes to ATS

Table of Contents

  1. When PDF Is Fine
  2. When Word Is Safer
  3. The Actual Rule
  4. PDF vs Word: Side-by-Side
  5. Common Mistakes
  6. Best Practices
  7. FAQ
  8. Key Takeaways
  9. Conclusion

When PDF Is Fine

The majority of companies hiring at scale right now use one of a handful of major cloud-based ATS platforms. These systems have had reliable PDF parsing built in for years:

  • Greenhouse, parses PDFs cleanly; used by thousands of tech companies, startups, and mid-size businesses
  • Lever, handles PDFs well; common in tech and SaaS hiring
  • Workday (modern cloud versions), supports PDF uploads and generally extracts text accurately
  • iCIMS, one of the most widely used platforms; PDF support is solid
  • SmartRecruiters, PDF friendly by default
  • Jobvite, BambooHR, Recruitee, all handle text-based PDFs without issue

The critical caveat: the PDF has to be text-based. If your resume was exported properly from Google Docs, Microsoft Word, or a word processor, it contains actual selectable text and will parse fine. If it was designed in Canva, Adobe Illustrator, or Figma, or scanned from a paper copy, the ATS often sees an image and extracts nothing useful.

When Word Is Safer

There are real situations where .docx is still the better choice.

Older Taleo Installations

Taleo is one of the oldest ATS platforms still in use. Large enterprises, financial services firms, and some government contractors often run older on-premise versions that were configured before PDF parsing was reliable. Some of these still extract Word documents more accurately than PDFs. If you're applying to a Fortune 500 company with a clunky application portal that looks like it hasn't been updated since 2015, lean toward Word.

Public Sector and Government Portals

UK civil service jobs through Civil Service Jobs, US federal positions through USAJOBS, and many local government portals often require or strongly prefer .docx. Some explicitly state this. Others don't say anything but their underlying systems work better with Word.

Staffing Agencies and Recruiters

If a recruiter or agency is submitting your resume to clients on your behalf, they'll almost certainly need a Word document so they can reformat it, add their branding, or strip out your contact details. Always send Word to recruiters unless they say otherwise.

When the Job Posting Says So

This should go without saying, but if the job posting specifies a format, use it. Some companies are explicit. Ignore this and you're giving the hiring team a reason to discard your application before it's been read.

The Actual Rule

There's one rule that beats every general piece of advice about PDF vs Word:

Check the job posting first. If it specifies a format, use it. If it doesn't, submit a clean single-column PDF.

The emphasis on "clean" and "single-column" matters more than the file format itself. A two-column PDF with a sidebar, graphics header, and icons for your contact details will fail parsing on almost every ATS regardless of how modern that system is. The same content in a simple, single-column layout with standard fonts and proper heading structure will parse correctly.

Build your resume in a word processor. Export to PDF. That's it. If you're using a resume template from JD2CV, the export formats are already optimised for ATS parsing, you don't need to guess.

A designed PDF isn't a resume optimised for looks. It's a resume optimised to fail silently.

PDF vs Word Resume: Side-by-Side

>
Factor PDF Word (.docx)
Modern cloud ATS (Greenhouse, Lever, iCIMS) ✅ Parses well ✅ Parses well
Older Taleo / on-premise systems ⚠️ Sometimes problematic ✅ Generally safer
Government / public sector portals ⚠️ Check posting ✅ Often preferred
Staffing agencies ❌ Usually not ideal ✅ Required for reformatting
Formatting consistency across devices ✅ Identical everywhere ⚠️ Can shift between Word versions
Human readability if downloaded ✅ Looks exactly as intended⚠️ May render differently
Risk of accidental edits ✅ Low ⚠️ Higher
Designed / graphic-heavy version ❌ Fails ATS parsing ❌ Fails ATS parsing

Common Mistakes to Avoid

  • Submitting a Canva resume as PDF and assuming it's ATS-friendly. Canva resumes are images. Most ATS systems extract zero useful text from them.
  • Sending a scanned copy as PDF. Same problem. If you can't highlight and copy text from the PDF, neither can the ATS.
  • Assuming Word is always the safer choice. It's not. On modern systems it offers no advantage, and formatting can break between Word versions.
  • Using multi-column layouts in either format. ATS parsers read left to right, top to bottom. Columns cause your experience section to get scrambled with your skills section.
  • Using headers and footers for contact information. Many ATS systems don't read content inside headers and footers. Put your name, email, and phone in the main body.
  • Ignoring the file name. Name your file something professional: Jane-Smith-Resume.pdf, not Resume-FINAL-v3-USE THIS ONE.docx.

Best Practices for ATS-Ready Resume Formatting

  • Use a single-column layout with clear section headings (Experience, Education, Skills)
  • Stick to standard fonts: Arial, Calibri, Georgia, or Times New Roman in 10–12pt
  • Avoid text boxes, tables used for layout, graphics, logos, or icons
  • Use standard section labels ATS systems recognise, not creative alternatives like "Where I've Been"
  • Export to PDF from a word processor, not from a design tool
  • Check your resume against the ATS resume checklist before submitting
  • Keep the file under 5MB, some portals reject larger files
  • If applying to multiple companies, keep both a PDF and .docx version ready

Frequently Asked Questions

Does Greenhouse parse PDFs correctly?

Yes. Greenhouse has reliable PDF parsing built in. As long as your PDF is text-based, not a scanned image or a graphic-heavy design file, Greenhouse will extract your content accurately. It's one of the ATS platforms where PDF is the cleaner choice for most applicants.

Is Word or PDF better for ATS in 2026?

For most modern ATS platforms, both work. The format matters less than the structure. A clean, single-column, text-based PDF is the best default when no format is specified. Word becomes the safer choice for older systems, government applications, and when submitting to recruiters who need to reformat your resume.

Can I submit a Canva resume to an ATS?

Not if you want it to be read. Canva exports PDFs as image-based files in most design layouts. ATS systems parse text, not images. Your beautifully designed resume likely produces a blank parse, meaning the recruiter sees your name at the top and nothing else gets indexed.

What if the job posting doesn't specify a file format?

Default to a clean, single-column PDF. It will look identical on every device the recruiter opens it on, won't shift formatting between software versions, and will parse correctly on all major modern ATS platforms. Just make sure it was exported from a word processor, not a design tool.

Do ATS systems reject PDFs outright?

Rarely in 2026. A small number of legacy systems, particularly older Taleo installations, may have trouble with them, but flat rejection is uncommon. The more likely failure mode isn't rejection, it's a bad parse: your resume gets accepted but the extracted text is garbled, putting your experience in the wrong fields or losing it entirely. That's why the format and the structure both matter.

Key Takeaways

  • The blanket advice to "always use Word" is outdated for most modern ATS platforms
  • Greenhouse, Lever, iCIMS, SmartRecruiters, and modern Workday all parse text-based PDFs well
  • Older Taleo, government systems, and staffing agencies still favour .docx
  • The single most important variable is whether your PDF contains actual text, not images
  • Multi-column layouts, graphics, and text boxes cause parsing failures in both formats
  • Always check the job posting for a specified format, and follow it if one is given
  • Keep both versions ready and choose based on the employer and system

Conclusion

The pdf vs word resume debate has a boring answer: it depends, but PDF is usually fine and often better. The real risk isn't the format, it's the design. A clean, single-column PDF built in a word processor and exported properly will pass through modern ATS without issue. A visually impressive multi-column design with graphics will fail regardless of whether it's a PDF or a Word file.

Know the system you're submitting to. Check the posting. When in doubt, go simple. That's the actual rule.

Test Your Resume Before You Submit

Not sure how your resume is reading in an ATS? Run it through the JD2CV ATS Score tool to see how it parses, what's getting missed, and what to fix before it reaches a recruiter. You can test both your PDF and Word versions side by side.