PDF or Word for an ATS? The question behind the question

The short answer

Send a .docx unless the posting asks for something else. It is the most consistently parsed format across applicant tracking systems, and it carries almost no risk of the failure mode that silently destroys PDF applications.

But the format label is not really what determines success. A well-made PDF parses fine. A badly-made PDF parses as a blank page. The difference has nothing to do with the extension and everything to do with whether the file contains real text.

The failure that actually costs people interviews

A PDF can hold text in two completely different ways. It can store actual character data with font information — selectable, copyable, extractable. Or it can store a picture of a page, where the letters are just pixels arranged to look like writing.

Both look identical on screen. To a parser, the first is a document and the second is a photograph containing no words whatsoever. Design tools, some browser-based resume builders, scanners, and any workflow that renders a page to a canvas before saving will produce the second kind.

This is not a rare edge case. It is the single most complete way to fail an application, because you submit something that looks perfect and arrives containing nothing.

How to test your file in five seconds

You don't need a tool for this.

Open your PDF and try to select a single word with your cursor:

• Individual words highlight cleanly — good, you have a real text layer.
• The entire page highlights as one rectangular block — it's an image. Re-export it.
• Nothing highlights at all — it's an image. Re-export it.

A second test worth doing

Select the whole document, copy it, and paste it into a plain text editor. This strips every visual element and shows you approximately what a parser extracts.

Read what comes out. Is your name and email there? Are the job titles attached to the right employers? Do the bullet points follow their roles, or has a sidebar been spliced into the middle of your work history? If the plain text version is incoherent, your layout is costing you the application regardless of file format.

When each format is the right call

The decision is usually simple, and the posting often makes it for you.

Practical guidance:

• The posting names a format — send exactly that, every time. This is also a compliance signal.
• No format specified — send .docx. Broadest, most predictable parsing.
• Applying by email to a named person — PDF is fine and looks more finished, provided it has a text layer.
• Uploading to a large enterprise careers portal — .docx. These systems are the oldest and least forgiving.
• A form that offers to parse and pre-fill your details — upload, then read what it extracted. That preview is a free, direct look at exactly how the parser sees your file.

What matters more than the format

Once your file has real text, the remaining risk is structural. Single column throughout. Standard section headings — Experience, Education, Skills — rather than inventive alternatives. No tables, no text boxes, no sidebars. Contact details in the body of the document, never in the header or footer region. Conventional month-and-year dates.

A plain single-column .docx with dull headings beats a beautifully designed two-column PDF in every system that matters. The visual polish is for the human who reads it after the parser has already decided whether you exist.