This question comes up in almost every resume workshop I have seen: "Should I submit a PDF or a Word document?" And the answer, frustratingly, is "it depends." But I can tell you exactly what it depends on, and by the end of this article you will know which format to use for every situation.
The short answer
If the job posting specifies a format, use that format. Full stop. If it does not specify, DOCX is the safer default for ATS compatibility. PDF is fine when you are sending directly to a person (a recruiter's email, a networking contact) or when the application system explicitly accepts PDFs.
Now let me explain why.
How ATS platforms handle each format
Applicant tracking systems parse documents by extracting text and mapping it to structured fields - name, email, job titles, dates, skills. The parsing quality depends heavily on how the file was created.
DOCX files are natively text-based. The ATS can read the content directly because the file is essentially structured XML under the hood. Section headings, paragraphs, and tables are all clearly defined in the file structure. This makes parsing reliable and predictable.
PDFs are more complicated because "PDF" is not one thing - it is a container format. A PDF created by exporting from Word or Google Docs usually contains extractable text and parses fine. A PDF created from a design tool like Canva or InDesign may embed text as vector paths or even as part of an image, which many ATS platforms cannot read. A scanned PDF (a photo of a printed document) is essentially a picture - the ATS gets nothing from it unless it runs OCR, and most do not.
| Format | ATS parsing | Layout control | Best used when |
|---|---|---|---|
| DOCX | Very reliable across all major ATS | Can shift slightly between computers | Online application portals, when format is unspecified |
| PDF (from Word/Docs) | Usually reliable | Locked - looks the same everywhere | Direct email to recruiters, networking |
| PDF (from design tools) | Unreliable - text may not extract | Perfect visual control | Portfolio submissions where visual design is being evaluated |
| PDF (scanned) | Fails entirely without OCR | N/A | Never for job applications |
Why DOCX gets the edge for ATS portals
Every major ATS vendor - Workday, Greenhouse, Lever, iCIMS, Taleo, BambooHR - handles DOCX reliably. The file format is an open standard, the internal structure is predictable, and parsing libraries for it are mature. There is simply less that can go wrong.
PDF parsing has improved dramatically over the past five years, and most modern ATS platforms handle well-structured PDFs without issues. But "most" and "well-structured" are doing a lot of work in that sentence. When a PDF is created from a design tool with layered text boxes, non-standard fonts, or complex column layouts, parsing can produce garbled output - names ending up in the skills field, dates disappearing, entire sections getting merged into one block.
If you are applying through an online portal and the posting does not specify a format, DOCX eliminates that uncertainty.
When PDF is actually the better choice
PDFs lock your layout. What you see is what the recipient sees, regardless of their operating system, their version of Word, or their default fonts. That matters when you are emailing a resume directly to someone - a recruiter you met at a networking event, a hiring manager who asked you to send your CV.
In direct-send situations, there is no ATS parsing involved. The person opens the file, reads it, and decides. In that scenario, a clean PDF preserves your formatting perfectly and looks more polished than a DOCX file that might reflow on a different screen.
PDFs are also the right choice for portfolio-adjacent fields where the visual presentation of the document is part of the evaluation - graphic design, architecture, or creative directing. But even then, keep a plain DOCX version ready for when you hit an online application portal.
The test that settles it in 30 seconds
If you want to know whether your PDF is ATS-safe, do this:
- Open the PDF in any PDF reader (Preview, Adobe, your browser).
- Press Ctrl+A (or Cmd+A) to select all text.
- Copy it and paste it into a plain text file.
- Does the text come out in the right order? Are sections intact? Are there weird characters or missing chunks?
If the pasted text looks clean and readable, your PDF will probably parse fine. If it comes out scrambled, with repeated text, or with missing sections, the ATS will have the same problem. Either fix the PDF or switch to DOCX.
What about Google Docs?
Google Docs is a great tool for writing resumes, but it is not a submission format. You cannot upload a Google Docs link to most application portals. What you can do is export from Google Docs to either DOCX or PDF. The DOCX export is generally clean and parses well. The PDF export is also fine - because Google Docs generates text-based PDFs, not image-based ones.
Common mistakes with file formats
- Submitting a Canva PDF and assuming it will parse. Canva produces visually striking documents, but the underlying file structure often confuses ATS parsers. If you love your Canva design, keep it for direct sends and build a plain DOCX for portals.
- Naming the file "resume.docx." Name it with your actual name: "Amira-Hassan-Resume-2026.docx." Recruiters download hundreds of files. Make yours identifiable.
- Using .doc instead of .docx. The old .doc format is from the 1990s. Some ATS platforms still support it, but .docx is the standard. Use it.
- Submitting a Pages file. Apple Pages is not universally supported. Always export to DOCX or PDF before submitting.
What happens when the ATS parses badly
When parsing fails, the recruiter sees a garbled profile. Your job title might be in the education field. Your skills might be missing. Your name might include part of your address. The recruiter does not know this is a parsing error - they just see a messy application and move on.
This is why file format matters more than most people realize. It is not about following arbitrary rules. It is about making sure the information you worked hard to write actually shows up where it belongs.
For a deeper look at how the parsing process works, read our ATS parsing guide. And for formatting choices that keep the document clean, the best resume format for ATS page is a useful companion.
The bottom line
Do not overthink this. DOCX for online portals and application systems. PDF when emailing directly to a person. Both should be text-based, single-column or simple layout, and named with your full name. That handles 95% of situations.
Spend the time you would have spent worrying about file format on making your bullets stronger instead. The content matters far more than the container.
Explore more in the ATS & Automation section, or open the builder to create a clean document that exports properly in both formats.
Trusted external resources
Useful next steps
File format is one piece of the ATS puzzle. The guides below cover the other pieces - how parsing actually works, which visual elements break it, and how to choose a layout that looks polished without creating problems.
- How Applicant Tracking Systems Actually Parse Your Resume
- Can ATS Read Tables, Columns, Icons, and Graphics?
- Best Resume Format for ATS
- Resume Templates
Frequently Asked Questions
Is PDF always bad for ATS?
No. A text-based PDF exported from Word or Google Docs usually parses fine in modern ATS platforms. The risk comes from PDFs made in design tools where the text is embedded in graphics or complex layouts.
Can I use both formats?
Absolutely. Keep a DOCX for online applications and a polished PDF for direct emails. Many job seekers maintain both versions of the same resume.
Does the file name affect ATS parsing?
The file name does not affect parsing, but it affects how recruiters find and identify your file later. Use your name and the word "resume" or "CV" - for example, "Yuki-Tanaka-CV-2026.pdf."