PDF vs DOCX for Resumes: Which Format Should You Use?

Send a PDF, unless you have been asked for something else.

That is the answer for almost every application, and the reasoning is worth understanding — partly because there are real exceptions, and partly because a persistent myth about applicant tracking systems pushes people into the wrong choice.

Why PDF wins

It looks the same everywhere. A .docx renders differently depending on the recipient's Word version, installed fonts, and page setup. Fonts you have and they do not get substituted, substituted fonts have different metrics, and a carefully balanced one-page CV becomes a page and a half with an orphaned line of contact details on page two. You will never know this happened. A PDF embeds its fonts and fixes its layout, so what they open is what you built.

It cannot be accidentally altered. Your CV will be forwarded, opened, and saved by several people. A Word file accumulates changes — a stray keystroke, an autocorrect, a recruiter's tracked comment left visible.

It carries no hidden history. This is the underrated reason. A .docx can retain tracked changes, comments, and document properties naming the original author. CVs are frequently built by editing an older version or a friend's file, and Word documents remember more than people expect. Exporting to PDF discards most of that, though not the metadata — see below.

It is the expectation. Sending a Word CV unprompted reads as slightly careless in most professional contexts.

The ATS myth

You will read that applicant tracking systems cannot parse PDFs and that you must submit Word. This was true, and it stopped being true a long time ago. Every major ATS — Workday, Greenhouse, Lever, Taleo, iCIMS — parses PDFs perfectly well.

What actually breaks parsing is not the format but the layout:

• Multi-column designs, which parsers often read straight across, interleaving your job titles with your skills list.
• Tables and text boxes, whose contents are frequently skipped entirely.
• Contact details in the header or footer, which some parsers do not read at all. This is the worst failure mode available: a perfect application the recruiter cannot reply to.
• Graphics, icons, and skill rating bars, which convey nothing to a parser.
• Unusual section headings. "Where I've Made an Impact" may be more interesting than "Experience", but the parser is looking for the standard words.
• A PDF that is really an image. If you exported a scan or a design as a flat image, there is no text to parse and the system sees an empty document. Check by trying to select text in your own CV — if you cannot, neither can they.

A single-column PDF with standard headings and contact details in the body parses cleanly everywhere. The format was never the problem.

When to send DOCX

When it is explicitly requested. Follow the instruction. Some portals accept only .docx, and ignoring a stated requirement is a bad first impression.

When a recruitment agency asks. Agencies commonly rewrite CVs into their own template and strip your contact details before sending you to a client. That is normal practice, and they need an editable file to do it.

When the upload form rejects your PDF. Some older portals still do. Send what works.

If you are unsure, ask. Recruiters answer this question happily and it takes one line in an email.

Producing a good PDF

Build the CV in Word, Google Docs, or a design tool, then export — File → Save As → PDF in Word, File → Download → PDF in Google Docs. Do not use Print to PDF, which discards hyperlinks, so your LinkedIn and portfolio URLs become dead text.

Then check it:

• Open the exported file and confirm the layout survived. Look at it in a different application than the one that made it.
• Select some text. If you cannot, it exported as an image and no parser will read it.
• Click every link. Broken portfolio links are a common and costly mistake.
• Check the metadata. File → Properties. Word puts your account name in the Author field, and it may not be the name you are applying under — this has genuinely embarrassed people whose CV was authored by a friend or a previous employer's account.
• Check the filename. Jane-Okafor-Resume.pdf is right. resume final v3 (2).pdf and CV_for_google.pdf are both bad, the second especially when sent to a different company.
• Check the size. Under 2 MB. If a photo or logo has pushed it higher, compress it.

Last-minute changes

If you need to fix a detail in an existing PDF CV and cannot find the source file, you can patch it — Docento.app adds text in the browser, and how to edit PDF text without Acrobat covers the technique.

But patch only if you must. Fixing the source document and re-exporting is cleaner, and covering old text with a white box leaves the original characters in the file, where a parser may still read them. A CV containing both your old and new job title, invisibly, is not the impression you want. Keep the source file, and keep it somewhere you can find it — you will need it again sooner than you think.

For the wider format comparison, see PDF vs Word.