Should Your Resume Be a PDF or Word Doc? (The ATS-Safe Answer)

Do you upload your resume as a PDF or a Word file? Send a PDF, unless the job posting asks for Word.

That is the answer for almost everyone. But the reason behind it is worth knowing, because it tells you the handful of times you should break the rule.

TL;DR: Send a PDF unless the posting asks for .docx. A PDF locks your layout so every reader sees the same page, and modern applicant tracking systems parse a clean PDF fine. When a posting names a format, follow it exactly.

The real difference between PDF and Word

A PDF and a Word file behave differently the moment someone else opens them, and that is the whole thing you are choosing between.

A PDF is fixed. Your fonts, your spacing, the column you spent twenty minutes aligning, all of it stays exactly where you put it. It looks identical on a recruiter’s laptop, on a phone, on a printout, and on a machine that has never seen your font. What you export is what they see.

A Word .docx is not fixed. It can reflow on the reader’s machine. If they open your file in a different version of Word, or on a computer that lacks your font, the software substitutes another one and your spacing shifts. Bullets move. A resume you fit onto one page spills onto a second. The recruiter reads a version you never approved and never saw.

So the default is easy. A PDF hands the reader the exact page you built. A Word file hands them a page their software rebuilds. For a human reading your resume, or an application you are emailing straight to a person, the PDF is the safe pick every time.

Can ATS systems actually read PDF resumes?

Yes. This is the myth worth killing first, because it is the reason people talk themselves out of PDFs.

Applicant tracking systems, the software that scans and files incoming applications, have read PDF files reliably for years. The platforms most companies actually use, like Workday, Greenhouse, and Lever, pull text out of PDFs without trouble. They lift your name, your job titles, your dates, and your skills, then drop them into searchable fields.

The “PDFs break ATS” warning is recycled advice from roughly a decade ago. Parsing engines were cruder then and sometimes choked on PDF structure. That stopped being true a long time ago. A 2015 blog post telling you to avoid PDF was probably right for 2015 and wrong for now.

There is one honest wrinkle here, and it is why Word has not disappeared. Some older or custom systems still parse .docx more reliably than PDF. It is not common with the big modern platforms, but it exists, and it is the reason a posting might ask for Word on purpose. If a listing names an ATS or asks for .docx, take that as a real signal and follow it. You do not need to guess which systems are old. The posting tells you.

The trap that matters more than the file type

Here is the part most articles skip. The bigger parsing risk is not PDF versus Word. It is your layout.

A parser reads a page in an order, and a fancy design breaks that order. Two columns, and it can read straight across, mixing your job title into your skills list. Tables, and it can lose the structure. Text boxes, headers, and footers, and it can read them last or skip them. Graphics and icons, and it reads nothing at all where they sit. None of that has anything to do with whether you saved a PDF or a .docx. A cluttered Word file parses just as badly as a cluttered PDF.

So the rule underneath the rule is this. Build a simple, single-column resume with real text, and it parses well either way. Build a two-column design packed with tables and icons, and no file format saves you. Fix the layout first. The extension is a smaller decision than it feels like.

Watch out for the image PDF

There is one PDF mistake that genuinely breaks applications, and it is separate from layout. It is the difference between a text PDF and an image PDF.

A text-based PDF stores your words as real characters the computer can read. An image-based PDF is a photograph of a page, and a parser sees nothing but pixels. Both end in .pdf, so the file name tells you nothing.

You get a text PDF when you export straight from Word, Google Docs, or a resume builder. You get an image PDF when you scan a printed copy, take a photo of your resume, or run it through a “print to image” tool. The image version looks identical on screen. To the software reading it, one is a clean transcript and the other is a blank wall.

Here is the ten-second test. Open your PDF, then try to drag-select a line of text with your mouse. If the words highlight and you can copy them, you have a text PDF and you are safe. If your cursor selects nothing, you have an image PDF that an ATS reads as empty. Fix that before you upload anything.

When should you send a Word document instead?

Send Word when someone asks for Word, and not really before then.

The clearest signal is the posting itself. If it says “submit a .doc or .docx file,” follow that exactly. The portal behind it may only accept that format, or the ATS behind it may parse Word more cleanly. Ignoring an explicit format request is a small thing that can get an application flagged.

The other common case is recruiters and staffing agencies. A recruiter often edits your resume before forwarding it to their client, sometimes to add their logo or strip your contact details so the client cannot go around them. They need an editable file to do that, so they ask for Word. Give them what they ask for. A recruiter who plans to rewrite your wording will always prefer a .docx over a locked PDF.

Outside those two cases, a PDF stays the safer choice. When the instructions say nothing, send the PDF and move on.

How to export a resume to PDF without wrecking it

Export from the original document, never from a scan or a photo. In Microsoft Word, use File, then Save As or Export, and choose PDF. In Google Docs, open File, then Download, then “PDF Document (.pdf).” Both routes produce a text-based PDF, because the words start as real text and stay that way.

A few habits keep the result clean. Use a common font like Calibri, Arial, or Georgia, so nothing has to be substituted on the reader’s end. Keep the structure simple, one column, no tables or text boxes for anything important, since parsers read those fields last or skip them. Name the file something sensible like Firstname-Lastname-Resume.pdf rather than resume-final-v7.pdf.

If you build your resume in a dedicated tool, the export is handled for you and the output is text-based by design. After exporting, run the drag-select test from earlier. Five seconds of checking beats finding out three weeks later that nobody could read your file.

Should you keep both a PDF and a Word version?

Keep both, and treat the editable file as the source of truth. Your Word or Google Docs version is the master copy where you make every change. The PDF is the export you send out. That split stops the classic mistake of editing the PDF directly with a converter and slowly mangling the layout.

The payoff shows up at the worst moment. A recruiter emails on a Friday afternoon and asks for your resume “in Word, please.” If you already have a current .docx sitting beside your PDF, you reply in under a minute. If you only saved a PDF, you are wrestling with a converter while the recruiter waits. Store both in one folder, and re-export the PDF whenever you touch the master so the two never fall out of sync.

So the format question comes down to a short rule. Default to a PDF, switch to Word only when a posting or recruiter asks, fix your layout before you worry about the extension, and never upload a scanned image of your resume. When you want the export handled cleanly with no font surprises, build it in the free resume builder at resume.hivly.net, which produces a text-based PDF by default. If you already have a file and just want to confirm it parses, the ATS resume checker will tell you what a machine actually sees.