Resume File Format: PDF vs Word (.docx), Settled

The PDF-versus-Word argument is mostly settled, and the answer is that it depends on where the file is going. A resume you email to a person and a resume you upload into a hiring portal are read by different things, and the format that is safest in one case is not automatically safest in the other.

This guide covers what the file format actually changes, what the major applicant tracking systems accept, and when to send each one. The sources at the bottom are the primary ones: ATS vendor documentation, university career offices, and job-board career guidance.

The rule that overrides everything: follow the posting

If the job posting or the application form names a file type, use that type. Nothing else in this guide outranks that. Indeed's career guide and The Muse both make this their first rule, and both point out the same downside: sending the wrong format when a specific one was requested reads as not following directions before anyone has looked at your experience.

Employers sometimes request a specific format because their applicant tracking or resume-scanning system handles it best, and sometimes just as a filter for attention to detail. You do not need to know which. If they asked for one, send that one.

What the file format actually changes

Both PDF and DOCX are containers for a text layer. When you upload either one, the parser pulls out that text plus rough position information and tries to map pieces of it to fields: name, contact, employers, titles, dates, education, skills. A .docx file stores text as structured XML with named paragraph styles, which gives a parser explicit structure to read. A text-based PDF stores text with layout coordinates instead.

What breaks a parse is almost never the choice between those two. It is multi-column and sidebar layouts, tables used for alignment, text boxes, contact details placed in the Word header or footer, and text baked into an image or logo. UC Berkeley's career office spells out the same list: avoid headers, footers, text boxes, tables, colors, pictures, and graphics, whichever format you save in. A clean single-column layout parses well as a PDF and as a DOCX. A two-column template parses badly as both. See our ATS resume format rules for the full structural checklist.

What the major ATS platforms accept

• Greenhouse accepts .doc, .docx, .pdf, .rtf, and .txt uploads, up to 100 MB, per its own support documentation. It converts your file to a PDF preview that the recruiter sees inline, so a text-based PDF is a reasonable default there.
• Workday accepts PDF, Word, and several other types. Its own admin documentation says resume-parsing results 'can vary based on resume format and order of words' and that 'for best results, use resumes that don't have images or image-based styles.'
• Workday also does not auto-populate the Skills and Languages fields from a parsed resume the way it fills employer, title, and dates, and it asks you to review the parsed data. On a Workday application, the form review matters more than which of the two formats you picked.

When to send a PDF

Send a PDF when you are emailing a recruiter or hiring manager directly, applying through a referral, attaching your resume to a portfolio or networking message, or when the posting asks for PDF. A text-based PDF, exported from Word, Google Docs, or a LaTeX toolchain rather than scanned, locks your layout so it looks identical on every machine. University career offices default to PDF for sending: Harvard's career-services guide tells students to check that formatting still translates correctly after converting to PDF, and Berkeley treats the PDF as the 'published' version of a resume that is otherwise a working draft.

One check before you send: open the PDF, select all the text, and paste it into a plain text editor. If it comes out clean, complete, and in reading order, a parser can read it too. If it comes out scrambled, empty, or out of order, the file will fail a parse no matter what its extension says.

When to upload a .docx

Upload a single-column .docx when the form recommends Word, or when you are applying into an older or unidentified applicant tracking system and the form accepts either. The named styles in a DOCX give a parser more explicit structure to map, and it sidesteps the uncommon parser that mishandles PDF text encoding.

Jobscan notes that modern systems read text from both PDFs and Word files, with its own testing leaning slightly toward PDF; other guidance leans DOCX for legacy systems such as Taleo. The formats are close enough that if you cannot tell which system you are facing, a single-column .docx is the conservative pick. Do not upload a pre-2007 .doc, an Apple Pages file, or an exported image.

The mistake that actually costs interviews

The failure mode is rarely picking the wrong one of two good formats. It is a scanned PDF with no text layer, a PDF exported from a design tool where the text was flattened into a graphic, a two-column layout, or LinkedIn's 'Save to PDF' export, which is multi-column and full of decorative elements. Any of those fails a parse regardless of the file extension.

Keep one clean, single-column base resume with real selectable text and contact details in the body. Export it to PDF for people and to .docx for portals that ask for Word. The base is what determines whether you get parsed; the extension is a last-step choice.

The short version

• The posting names a format: use that one, every time.
• Emailing a human, a referral, or a portfolio attachment: text-based PDF.
• An older or unknown ATS, or a form that says Word: single-column .docx.
• Either way: single column, real selectable text, contact info in the body, no tables or text boxes.
• Never: a scanned or image-only PDF, a design-tool export with flattened text, a pre-2007 .doc, or an Apple Pages file.

ResumeSkip exports your tailored resume as a single-column .docx and as plain text, both built to the structural rules above, so you have the right file ready whichever way you apply.