PDF or Word: which resume file to send, and why the answer changed

For years the standard advice was to send a .docx, because applicant tracking systems handled Word better than PDF. That was true, and it stopped being true well before people stopped repeating it.

The modern answer is straightforward: send a PDF, unless the posting asks for something else, and make sure your PDF has a text layer. That last clause is the part that matters, and it is the one nobody mentions.

Why PDF won

A PDF fixes the layout. What you designed is what the reader sees, on any device, with the fonts you chose. A .docx re-flows according to whatever fonts and version the recipient has, which means the second page break you carefully avoided can appear on someone else's screen, and your two-page resume can arrive as a two-and-a-bit-page resume with one orphaned line.

Word files also carry things you did not intend to send. Tracked changes, comments, and the document's revision history and author metadata travel with the file. A resume that arrives with visible tracked changes from the version you were editing for a different company is a real and recurring failure.

Meanwhile the parsing gap closed. Every major applicant tracking system now extracts text from PDFs reliably — that is the format most of their input arrives in. The remaining parsing problems have nothing to do with PDF versus Word and everything to do with layout: columns, tables, and text in headers break both formats equally.

The one PDF that will fail

There is exactly one PDF failure mode, and it is total when it happens.

A PDF can contain text, or it can contain a picture of text. A file exported from a word processor or a browser contains real text that can be selected, searched and extracted. A file produced by scanning a printout, photographing a page, or exporting a design as a flattened image contains pixels arranged to look like letters, and to a parser it is a blank document.

This is not a degraded outcome — it is nothing. Your resume enters the database with no name, no employer, no skills. It will not appear in any search. Nobody will tell you, and it is one of the few genuine cases where a good candidate disappears for a technical reason.

The one-minute check: open your PDF, try to select a line of text with the cursor, and copy it into a text editor. If the words appear, you have a text layer. If you can only draw a box around the region, you have an image, and you need to re-export from the original document rather than from a scan or a screenshot.

While you are there, paste the whole thing into a plain text editor and read it. That is approximately what the parser sees, and it is the fastest way to discover that your two-column layout has interleaved your job titles with your skills, or that your name is missing because it lives in the document header.

When to send a .docx anyway

When the posting says so. Some systems, and a fair number of recruitment agencies, still ask for Word. Follow the instruction — it is usually because they intend to edit the file, which brings us to the next case.

When a recruiter asks for an editable version. Agency recruiters routinely reformat resumes onto their own letterhead before sending them to a client. This is normal, and it is worth knowing that it happens, because it means your careful typography is going to be discarded. Keep your content strong enough to survive being poured into a different template.

When a public-sector or academic application specifies a format. Government portals and university systems have their own rules, sometimes including plain text. These instructions are usually enforced by the upload form itself.

If you do send a .docx: inspect the document properties and remove your name from the author field if it is wrong, accept or reject all tracked changes, delete all comments, and check that nothing important lives in a header, footer or text box.

File names

A surprisingly consequential detail, because the file name is often the first thing a human sees in an inbox or a download folder, and it is sometimes the only thing shown in a list of a hundred applicants.

Use your name and the word resume: Amara-Whitfield-Resume.pdf. Add the role if you are applying to several at one organisation: Amara-Whitfield-Resume-ICU.pdf.

Avoid resume_final_v4_USE_THIS_ONE.pdf, Untitled.pdf, and anything containing another company's name. The last one happens more than you would think and it is the worst of the three.

What about plain text

Some older portals ask you to paste your resume into a text box rather than upload a file. When that happens, do not paste from your PDF and hope — the line breaks and bullet characters usually arrive mangled.

Export or write a proper plain-text version: no bullets except a simple hyphen, no tabs, one column, section headings in capitals. It will look plain, which is correct; the only reader is a form field. Most builders can produce one, including this one, which exports a .txt alongside the PDF for exactly this situation.

The short version

Send a PDF with a text layer, named with your own name, unless you have been told otherwise. Check the text layer by selecting and copying, and read the copied text once to see what the machine sees.

That is the entire file-format question. It has been settled for years, and the residual advice to prefer Word is a survival from a period when parsers were worse. What has not changed is that the layout inside the file matters far more than the extension on the end of it — a beautifully exported PDF with a sidebar will parse worse than a plain .docx in one column, which is a separate problem and a more common one.

Related

• ATS-friendly resume format: what actually breaks the parse
• How long should a resume be?
• Should you put a photo on your resume?