Resume PDF vs DOCX: which format do ATS systems prefer?

The PDF-vs-DOCX debate has been going for a decade, and most of the advice online is out of date. Early-2010s ATS platforms struggled with PDFs, which is where the "always submit Word" rule came from. That advice no longer matches how the current dominant systems work.

What modern ATS parsers actually support

The major applicant tracking systems in 2026 - Workday, Greenhouse, Lever, iCIMS, Ashby, Taleo, SmartRecruiters - all parse both .pdf and .docx. Their parsers are built on top of OCR and layout libraries (Apache PDFBox, Textract, Affinda, Sovren, HireAbility) that handle text-layer PDFs without issue.

The edge cases where a parser prefers DOCX are shrinking. Where they still exist, the cause is usually a PDF exported from Canva, InDesign, or a template that placed text inside images rather than a real text layer.

When PDF wins

• Layout fidelity. A DOCX opened in a different version of Word, or in Google Docs or Pages, can shift fonts, kerning, and page breaks. A PDF looks the same to everyone.
• Font embedding. PDFs carry their fonts with them. DOCX files fall back to whatever the recipient has installed.
• No accidental edits. A hiring manager cannot nudge a line break mid-scroll in a PDF. In DOCX they can, and sometimes do.
• Smaller, standard, and portable. Less to go wrong between your builder and the portal.

When DOCX wins

• The application explicitly asks for .docx.Follow instructions. This happens most often at government and agency postings, and with some older Taleo instances.
• Staffing and recruiting agencies. Many agencies edit your resume (adding their header, removing your contact info) before forwarding it to the client. DOCX makes that faster for them, and they will sometimes convert a PDF back into DOCX with poor results if you force their hand.

The format that matters most is the one the application asks for. Everything else is preference.

How to export a clean PDF

• Export, do not screenshot. A PDF that is really just a rasterized image has no text layer. The ATS gets nothing. Copy-paste from the PDF; if you get text back, it is a real text layer.
• Single column, standard fonts. Helvetica, Arial, Calibri, Times, Georgia. Skip the display fonts.
• No tables, text boxes, or columns for content you want parsed. Two-column layouts often read in the wrong order. For the full layout rules, see our ATS resume guide.
• Named section headings. Experience, Education, Skills, Projects. Parsers anchor on these.

How to export a clean DOCX

• Use Word's built-in styles for headings.Not just bold 14pt text. Heading 1, Heading 2, Normal. Parsers use these style tags.
• No text boxes or floating elements. If you cannot click-and-drag a cursor straight through every character top to bottom, the parser will not either.
• Avoid embedded SVGs and icons. They render as binary blobs in the parsed text.
• One font family throughout.Mixing three fonts is an AI-builder signature and tends to fall back badly on the reader's machine.

The "just send both" strategy

Some candidates attach both formats when the portal allows multiple files. This is usually unnecessary and occasionally backfires: parsers that ingest the first attachment may grab the DOCX while a recruiter skims the PDF, and the two can disagree if you edited one and not the other. Pick one, make it good, submit it.

Key takeaways

• PDF by default. DOCX only when explicitly requested.
• Whatever format you send, test that copy-paste returns clean text in reading order.
• Single column, standard fonts, named sections. Format choice does not save a bad layout.
• Agencies often prefer DOCX. Enterprise portals generally do not care.
• If you are hitting other common resume mistakes, file format is not your problem.