PDF vs. Word Resume: Which Format Should You Actually Send?

Short answer: send a PDF unless the application asks for Word, or a recruiter or staffing agency tells you they need an editable file. A modern PDF keeps your formatting perfectly intact and is read just fine by today's applicant tracking systems. The old warning that "PDFs break the ATS" is mostly a myth left over from a decade ago.

That said, the real risk is not PDF versus Word. It is sending the wrong kind of either, an image-based PDF or a Word file stuffed with tables and text boxes. Get the file type right and the format almost takes care of itself. Here is how to decide, and the one rule that keeps you safe in every case.

The honest truth about ATS and file formats

For years, blog posts told job seekers that PDFs were dangerous because the robots couldn't read them. That was true of some early systems and is largely false today. The major platforms, Workday, Greenhouse, Lever, Ashby, iCIMS, all parse properly exported PDFs without trouble. If you want the full picture of how these systems read your file, see what an ATS is.

The actual failure point is not the extension. It is whether the file contains real, selectable text. A PDF you created by exporting from Word or Google Docs is full of text the parser can read. A PDF you made by scanning a printout, or by exporting a design as an image, is just a picture, and no ATS can read a picture. The same goes for screenshots.

The test that settles it: open your PDF and try to select a line of text with your cursor. If you can highlight individual words, the ATS can read them. If your whole resume highlights as one block, or nothing highlights, it is an image and it will fail.

PDF vs. Word, head to head

FactorPDFWord (.docx)
Formatting stays putYes, identical everywhereNo, can shift between machines
Modern ATS parsingReliable when text-basedReliable, sometimes slightly better on older systems
Recruiters can edit itNoYes
Staffing agencies preferRarelyOften, they rebrand your file
Risk of looking brokenLowMedium, depends on their Word version
Safe defaultYesOnly when requested

The pattern is clear. PDF is the safer default for a direct application because what you see is exactly what the hiring manager sees. Word wins in two specific cases: when someone asks for it, and when a recruiter needs to edit or rebrand the file before passing it on.

When to send Word instead

There are real reasons to reach for .docx:

  • The posting asks for it. Always follow the instructions. If it says "submit as Word document," send Word. Ignoring the stated format is a quiet way to look like you don't read carefully.
  • A staffing or recruiting agency requests it. Agencies often strip your contact info and add their logo before sending you to a client. They need an editable file to do that.
  • An older or niche ATS is involved. A handful of legacy systems parse .docx marginally more cleanly. If a company runs visibly dated software, Word is a safe bet.
  • You're told a human will copy-paste it. Some smaller employers paste your text into a template. Word makes that easier.

Outside of those, PDF is the better call.

The formatting that actually breaks parsing (in either format)

Switching file type will not fix a resume that confuses the parser. These break ATS reading whether you save as PDF or Word:

  • Tables and columns for layout. Parsers read left to right, top to bottom, and multi-column designs scramble your content.
  • Text boxes and headers/footers. Contact info tucked in a header often gets dropped entirely.
  • Images, logos, and icons standing in for text.
  • Fancy or non-standard fonts that don't embed cleanly.
  • Graphics-heavy "designer" templates from sites that prioritize looks over parsing.

If any of these sound familiar, the format debate is the wrong question. Start with an ATS-friendly resume format built as a single column of plain text, then export. To catch what a parser will actually choke on, run your file through an ATS resume checker before you apply, it flags the exact spots where your formatting drops content.

How to export a clean file

Whichever you choose, export it the right way:

  1. From Word: File → Save As → choose PDF (or keep .docx). Do not "Print to PDF" from some apps, which can flatten text to image.
  2. From Google Docs: File → Download → PDF Document or Microsoft Word (.docx). Both produce clean, text-based files.
  3. Name the file like a professional: Jane-Smith-Resume.pdf, not resume-final-v3-REAL.pdf.
  4. Open the result and test it. Select the text. If it highlights word by word, you're good.

One more efficiency note: once your resume parses cleanly, you still have to retype most of it into each application form, because uploading the file rarely fills the fields reliably. That repetitive re-entry is exactly the busywork JobRizzer is built to remove, you review every field and submit yourself, but you skip typing your work history for the tenth time. The file format gets you read; autofill saves the hours after.

Common file-format questions, settled

A few situations trip people up beyond the basic PDF-versus-Word call:

  • Google Docs link. Don't paste a "share" link as your resume unless asked. Download a real file first. A link can break, require sign-in, or expose your edit history.
  • Apple Pages or Numbers. Never send .pages. Most recruiters can't open it. Export to PDF or Word from the Pages menu before attaching.
  • "Combined" PDFs. If you merge your resume and cover letter into one PDF, make sure the resume is first and both are text-based. Some ATS forms only parse the first document anyway.
  • File you saved years ago. Old .doc (not .docx) files can parse poorly. Re-save as a current .docx or export fresh to PDF.

When you're genuinely unsure and the posting gives no instruction, default to PDF. It's the format that fails the least, looks the same everywhere, and reads cleanly in every system that matters today.

A quick decision flow

If you want a single path to follow:

  1. Does the posting name a format? Use exactly that.
  2. Is a recruiter or agency handling your application? Ask, and send Word if they need to edit it.
  3. Neither? Send PDF.
  4. In every case: open the final file, highlight the text to confirm it's selectable, and name it Firstname-Lastname-Resume.

The bottom line

Send a PDF by default. It locks your formatting and reads cleanly in every modern ATS, as long as it is built from real text and not a scanned image or a graphic. Switch to Word only when the posting, a recruiter, or a staffing agency specifically asks for it.

The file extension matters far less than people think. What matters is a single-column, text-based layout with no tables or text boxes, exported cleanly and tested by highlighting the text. Get that right, and PDF versus Word becomes a footnote instead of a worry.

FAQ

Is a PDF or Word resume better for ATS?

Modern applicant tracking systems read both well, as long as the file is a real text document and not an image. The old advice that PDFs break ATS is mostly outdated. The bigger risk is a scanned or exported-as-image PDF, which neither format handles.

When should I send a Word resume instead of PDF?

Send Word (.docx) when the application or a recruiter explicitly asks for it, or when a staffing agency needs to edit or rebrand your resume. Some older or niche ATS platforms also parse .docx slightly more reliably. When in doubt, follow the instructions on the posting.

Will a PDF mess up my formatting?

No, that's actually the main reason to use PDF. A PDF looks identical on every device and printer, while a Word file can shift fonts, spacing, and page breaks depending on the reader's software. For preserving how your resume looks, PDF wins.

Should I ever send my resume as an image or Pages file?

No. Never send a .jpg, .png, screenshot, or Apple Pages (.pages) file. Image files cannot be parsed by an ATS at all, and Pages files often won't open on a recruiter's machine. Always export to PDF or .docx first.