· does ats read pdf or docx

Does the ATS Read PDF or DOCX? (2026 Reality Check)

The honest answer to whether ATS systems parse PDF or DOCX more reliably in 2026, when to use each, and the one rule that decides it.

Free ATS-beating resume + cover letter bundle

.docx · Word + Google Docs · US/UK/CA

“Always send PDF.” “Always send DOCX.” Career YouTube has been arguing about this for a decade. The actual answer in 2026 is more useful than either absolute, and it comes down to one specific property of how each file format stores text. Here’s the breakdown, with what to send when the portal lets you choose.

The 30-second answer

SituationSend
Portal accepts both, no instruction.docx
Portal says “Word format” or “Microsoft Word”.docx
Portal says “PDF only”.pdf (exported from your .docx)
Portal says “either is fine”.docx
You’re emailing the recruiter directly.pdf (formatting won’t shift on their end)

The default is .docx. Send PDF only when the portal demands it or when visual fidelity to a human reader matters more than parser accuracy.

Why .docx parses more reliably

.docx is structured XML under the hood. If you rename a .docx to .zip and unzip it, you find a document.xml file describing every paragraph, run, style, and bullet with explicit XML tags. The ATS parser reads this structure directly. Section headers are tagged. Bullets are tagged. Tables are tagged (badly, but tagged). The parser doesn’t have to guess at reading order — it follows the structure.

PDF is fundamentally different. A PDF is a layout description: a series of instructions like “draw glyph ‘J’ at x=72, y=648, font=Calibri, size=11pt”. Text is positioned in absolute coordinates. There’s no underlying notion of “this is a section header” or “this is a bullet list” or even “this paragraph comes before that one.” The parser has to reconstruct reading order by looking at coordinates.

For a clean, single-column resume, this reconstruction is usually fine. For anything more complex, it can fail badly.

When PDF parsing fails (with examples)

Failure 1 — Two-column resumes

A two-column resume rendered to PDF has all its left-column glyphs at one set of x-coordinates and all its right-column glyphs at another set. The parser may try to read in true visual order (left col top to bottom, then right col top to bottom) or it may sort glyphs by y-coordinate (which interleaves both columns). Different parsers handle it differently. None handle it reliably.

Failure 2 — Embedded custom fonts

When you embed a custom font in a PDF, the glyphs get encoded as font- specific code points that may not map to standard Unicode. Some parsers extract these as � placeholders or as random characters. The recruiter sees gibberish for your job titles.

Failure 3 — Resumes exported from Canva, Figma, Pages

These tools optimize for visual output, not text extraction. The resulting PDFs often have glyphs out of reading order, text placed as graphics instead of text objects, and overlapping text layers. Parsers struggle.

Failure 4 — Scanned PDFs

If you scanned a printed resume to PDF, the file contains an image of text, not text. No ATS will OCR this. Don’t ever do this.

When .docx is the worse choice

There’s exactly one situation where PDF is more reliable than .docx: when your .docx has rendering bugs that only show up after upload.

Word, Pages, LibreOffice, and Google Docs all render .docx files slightly differently. Section breaks, paragraph spacing, table borders, and embedded images can shift. If your resume looks perfect in Word and the recruiter opens it in Google Docs and a bullet point overflows onto a second page, you’ve lost the visual presentation battle.

For visual fidelity to a human: send PDF. For structured data fidelity to a parser: send .docx.

In an automated application portal, the parser sees the file before any human does. Optimize for the parser. Send .docx.

In a direct email to a human (recruiter, hiring manager): optimize for the human. Send PDF, exported from your clean .docx.

How to export a clean PDF from your DOCX

Don’t redesign your resume for the PDF. Just export:

In Microsoft Word

In Google Docs

In Pages (Mac)

The resulting PDF preserves your DOCX’s structure. If you then upload the PDF to a portal, the parser still struggles with some elements (multi- column, etc) but you’ve at least avoided the worst case (custom fonts mangled, glyphs out of order).

The parser hierarchy in 2026

Rough ranking by how reliably each format parses across the major ATSes:

Most reliable:    .docx (single column, standard fonts, no images)
                  ↓
                  .docx (with tables — still better than PDF in most cases)
                  ↓
                  .pdf (exported from clean .docx, single column)
                  ↓
                  .pdf (exported from Word, with embedded standard fonts)
                  ↓
                  .pdf (from Canva / Figma / online builder)
                  ↓
                  .pdf (scanned image of text — does not parse at all)
Least reliable:   plain .txt (works but visually unprofessional)

Common myths

Myth 1 — “PDF preserves formatting so it’s safer”

True for visual presentation. False for ATS parsing. The ATS doesn’t care that your resume looks the same on every screen — it cares whether it can extract clean field data. .docx wins that game.

Myth 2 — “All modern ATSes handle PDF perfectly now”

The major ones handle clean PDFs well. Mid-tier and older ATSes still struggle. You don’t know which one the company you’re applying to is running.

Myth 3 — “PDFs are smaller so they upload faster”

A typical resume .docx is 20–80 KB. A typical resume .pdf is 50–200 KB. Both upload instantly on any modern connection. File size is not a real factor.

Myth 4 — “Recruiters prefer PDF because it’s professional”

Most recruiters genuinely don’t care about the file format. They care about whether the resume parsed cleanly into their ATS and whether the content is good. The “PDFs are more professional” preference is a 2010-era holdover.

What’s actually in our free template

The hireformat free ATS bundle ships as .docx for exactly the reasons above. The bundle’s HOW-TO-USE.md covers the export-to-PDF flow for the situations where you need it.

Frequently asked questions

Should I submit both formats if the portal allows it?

No. Pick one. Submitting two files of the same content can trigger duplicate-application flags in some ATSes and looks indecisive to the recruiter who sees both.

What if the portal accepts .doc (the old Word 97-2003 format)?

Convert to .docx first (Word → File → Save As → Word Document .docx). The old .doc format predates modern parser optimizations and can produce unpredictable results.

Avoid this. Many ATSes don’t follow external links, and a recruiter opening a link to a Google Doc may hit access errors. Download the doc as .docx and submit the file.

What about ATSes that use AI to read PDFs better?

Some 2024–2026 ATSes use vision models to parse PDFs as if they were images, which handles layouts much better. But you don’t know which ATS you’re submitting to, and the percentage of ATSes using these advanced parsers is still well under half. Don’t optimize for the best case.

The TL;DR rule

Default to .docx. Use .pdf only when the portal demands it or when sending directly to a human via email.

If you do nothing else from this article, do that.

Get the bundle

Five files. Real .docx. Opens in Word and Google Docs. Free.

Get the free ATS bundle

Real .docx files. One click. One short sponsor step. Yours forever.

Related reading