The short answer
For most applications today, a well-formatted PDF is safe. Modern applicant tracking systems parse PDFs reliably as long as the PDF was generated from a text-based document, such as Word or Google Docs exported to PDF, rather than a scanned image of a printed page. The older advice that PDFs universally break ATS parsing is outdated for the large majority of systems in current use, and most major platforms have handled text-based PDFs correctly for years now, including the widely used systems at large and mid-size employers.
That said, outdated advice persists online because it was once true for a meaningful share of older systems, so it is worth understanding the nuance rather than just picking a format at random and hoping for the best outcome without any real reasoning behind the choice.
When a DOCX file is the safer choice
Some older or smaller company systems still handle DOCX more reliably than PDF, particularly niche or homegrown platforms used by smaller employers who never upgraded their applicant tracking stack over the years. If a job application specifically requests a Word document, follow that instruction exactly rather than substituting a PDF because you personally prefer it or find it more polished looking. If you have no other guidance and want to minimize any risk at all, DOCX is the marginally safer default, though the practical gap between the two has narrowed significantly in recent years as parsing technology has generally improved across the industry.
What actually causes parsing problems, regardless of file type
- A resume built as a scanned image or photo, with no actual selectable text underneath the visible letters on the page
- Text placed inside embedded images, text boxes, or headers and footers that many parsers skip over entirely during extraction
- Complex multi-column templates, tables used for layout, or graphics-heavy designs with decorative elements scattered throughout
- Unusual fonts that do not embed properly when exported, causing characters to render incorrectly or drop out entirely
The file format matters far less than these structural issues do. A poorly structured PDF and a poorly structured DOCX will both cause the same kinds of problems; a clean, simply built version of either format usually works fine across nearly any system a company might currently be using to manage applicants.
A practical way to decide
Follow the job posting's instructions first, every time, since that removes all guesswork from the decision entirely. If none are given, submit a PDF, since it preserves your formatting exactly as designed regardless of what device or software opens it later, and it is well supported by current systems across the board. Keep a clean DOCX version ready in a folder you can find quickly, in case a specific application asks for it or a recruiter requests it directly by email during the process.
Naming and sending the file correctly
Whichever format you choose, name the file clearly and professionally, something like FirstName LastName Resume, rather than a leftover working title full of version numbers and the word final repeated several times. When a system or a recruiter downloads dozens of files in a day, a clearly named file stands out as prepared and professional before it is even opened, while a messy file name can create a small negative impression before your actual content has a chance to speak for itself.
What about other file formats entirely
Occasionally a candidate wonders about submitting a resume as a Google Docs link, a plain text file, or an HTML page instead of a traditional document. Unless an application specifically supports or requests one of these, avoid them. A shared Google Docs link depends on permissions being set correctly and can break if access settings change later, a plain text file strips out all formatting and looks unpolished to a human reader even if it parses perfectly, and an HTML page is not a format most systems expect at all. Stick to PDF or DOCX as the two standard, well-supported choices, and reserve anything unusual for situations where a specific employer has explicitly asked for it and you have confirmed it will be received correctly.
What to do when you are emailing a resume directly, not uploading it
When you email a resume directly to a recruiter or hiring manager rather than uploading it through a portal, the same PDF-first guidance applies, with one extra consideration: write a short, clear note in the body of the email itself rather than leaving the message blank and relying only on the attachment. State the role you are applying for, one or two lines about why you are a strong fit, and confirm the attachment format in passing, such as noting that your resume is attached as a PDF. This small bit of context helps a busy recipient understand at a glance what they are opening and why, before they even click on the file itself.
Keeping the file size reasonable
A resume with embedded high resolution images or an overly complex design can sometimes balloon into a file several megabytes in size, which occasionally trips spam filters or upload limits on certain systems, particularly older corporate email servers with conservative attachment caps. A well-built single or two-page resume, even with modest design elements, should generally stay under one megabyte. If your file is noticeably larger than that, check whether an embedded image or an oversized logo is the culprit, and compress or replace it before sending, since a bounced email or a failed upload because of file size is an entirely avoidable way to lose an opportunity.
A quick way to check is simply looking at the file size shown in your folder or file manager before attaching it anywhere. If it is well over a megabyte for a plain text-based document, something in the file is larger than it needs to be and is worth a second look before you send it out.