Submit a PDF in most cases, and only send a Word document (.docx) when the application explicitly asks for one. A text-based PDF preserves your formatting exactly and is read cleanly by modern applicant tracking systems, so it is the safest default. The two real exceptions: when the job posting or recruiter requests Word, and when you are working with a recruiter who needs to edit your resume before submitting it. Above all, follow the format the application asks for — that instruction overrides any general rule.
Why PDF is the safe default
A PDF does one thing Word cannot guarantee: it looks identical on every device and in every viewer. A .docx can re-flow when it is opened in a different version of Word, on a Mac versus a PC, or in Google Docs — fonts substitute, spacing shifts, and a one-page resume becomes a page and a half. A text-based PDF freezes your layout exactly as you designed it, and modern applicant tracking systems read it without trouble. That combination — stable formatting plus clean parsing — is why PDF is the default recommendation.
| Situation | Best format | Why |
|---|---|---|
| No format specified | PDF (text-based) | Stable layout + parses cleanly in modern ATS |
| Posting asks for Word | Word (.docx) | Follow the instruction — it overrides the default |
| Working with an external recruiter | Word (.docx) | They often edit or re-brand before submitting |
| Upload form only accepts .doc/.docx | Word (.docx) | Use what the form accepts |
| Emailing directly to a hiring manager | Looks polished and cannot be accidentally altered |
The real failure modes (and how to avoid them)
Format choice matters far less than these underlying issues, which break parsing in any file type:
- Image-based files: scanned or picture-exported resumes have no readable text. Always export real, selectable text.
- Tables, columns, and sidebars: these scramble parsing whether you save as PDF or Word. A single-column layout is what actually keeps you safe.
- Non-standard fonts or text in the header/footer: some parsers ignore header and footer regions, so keep your name and contact details in the body.
Follow the instruction first
If a posting says "upload your resume as a Word document," do exactly that — ignoring an explicit instruction is a worse signal than any format debate. When nothing is specified, send a clean, text-based PDF. Guidance from Jobscan and Indeed lands in the same place: PDF by default, Word when asked.
The honest summary
PDF is the right default — stable formatting, clean parsing — and Word is the exception you reach for when the application asks or a recruiter needs to edit. Whichever you send, make sure it is real selectable text in a single-column layout, and name the file like a professional. Format rarely sinks an application; an image-based file or a scrambled multi-column layout does.
Common questions
- Is a PDF or Word resume better for ATS?
- A text-based PDF is the better default. Modern ATS platforms parse PDFs reliably, and a PDF locks your layout so it looks the same to everyone. Word is only safer when an employer specifically asks for it or runs an older system that requested .docx.
- When should I send a Word document instead?
- Send .docx when the application explicitly asks for Word, when an external recruiter needs to edit or rebrand your resume, or when an upload form only accepts .doc/.docx. Otherwise default to PDF.
- Do PDFs get rejected by applicant tracking systems?
- A text-based PDF (one where you can select the text) parses fine in current systems. The thing that actually fails is an image-based PDF — for example, a scanned resume or one exported as a picture — because there is no real text for the parser to read.
- Does the file name matter?
- Yes, a little. Use a clean, professional file name like "Firstname-Lastname-Resume.pdf". It is what the recruiter sees in their downloads and what some systems store, and it looks more polished than "resume-final-v3.pdf".
Sources
Keep reading
What does an ATS-friendly resume look like?
An ATS-friendly resume is single-column and plain-text, with standard headings, readable dates, and no tables or graphics. Here is the exact anatomy.
Can you use tables in an ATS resume?
Avoid tables in an ATS resume — many parsers scramble multi-column tables, jumbling your dates and titles. Here is why, how to check, and what to use instead.
How do I check if my resume is ATS-friendly?
Check two things: that your resume parses (read it as plain text) and that it matches the job (scan it for keywords). Here is the free, step-by-step method.