DOCX vs PDF Resume — What ATS systems actually parse

Short answer

Default to PDF. Modern ATSes parse text-layer PDFs reliably, and PDF preserves the visual layout exactly. Send DOCX when the application form asks for it (most commonly: certain Taleo, iCIMS, and Workday deployments, plus many federal and state government portals). Send plain text only when pasting into a portal text box — never as your primary attachment.

The single most important rule is older than the format debate: the resume must have a real text layer. An image-only PDF (exported from a graphic-design tool where every character was rendered as pixels) cannot be parsed by any ATS, regardless of whether the receiving system prefers DOCX or PDF. Always test by selecting and copying text from your exported file before submitting.

When DOCX is the right choice

DOCX is the right choice in three specific cases:

1. The application explicitly requires DOCX. Some Oracle Taleo deployments, some iCIMS configurations, and many federal and state government portals (USAJOBS in some flows, some state HR systems) still ask for DOCX as the primary attachment. Honor the requirement. Submitting PDF when DOCX is asked for can produce an upload error or quietly fail field-mapping inside the ATS.

2. The recruiter asked for an editable version. Staffing agencies and contract recruiters sometimes ask for DOCX so they can add a header with their agency branding, anonymize candidate names, or merge multiple resumes into a single submission package for a client. This is a normal workflow. Send DOCX without a complex layout so the recruiter can edit it cleanly.

3. The ATS's parser is known to handle DOCX better than PDF. This is rarer than it used to be — modern parsers from Greenhouse, Lever, Ashby, Workable, and SmartRecruiters handle text-layer PDFs well. But on some legacy Taleo deployments and certain older Workday tenants, DOCX parsing has historically produced better field mapping. If a recruiter at the company has told you which format to send, follow that guidance over a general rule.

When PDF is safer

PDF is safer than DOCX in most modern applications for four reasons:

1. Layout preservation.A DOCX file rendered on a recruiter's machine can shift depending on which Word version, which Microsoft fonts, and which OS the recipient has installed. Word on a Mac, Word on Windows, Word Online, and LibreOffice can render the same DOCX with different line breaks, page breaks, and font substitutions. A PDF locks the layout — what you see on export is what the recruiter sees.

2. No accidental editing. DOCX files can be edited in place. PDFs require an extra step to edit. This is a small benefit, but it matters when staffing-agency intermediaries are not in the workflow.

3. Modern parser support.Greenhouse, Lever, Ashby, Workable, SmartRecruiters, and modern Workday tenants all parse text-layer PDFs reliably. The historical concern — that PDFs were image-only or used embedded fonts that broke parsers — applies to PDFs exported badly, not to PDFs exported correctly. Export with "preserve text" or "searchable PDF" on, and the parser sees the same text the reader does.

4. Smaller variance across reviewers. A PDF reviewed on a phone, a tablet, a laptop, and a 27-inch monitor looks identical. A DOCX can render differently across all four, especially if the reviewer uses Google Docs to open it.

When plain text wins

Plain text wins in exactly one workflow: paste-into-portal flows. Some Workday tenants, some legacy company forms, and most government portals have a "paste your resume here" text box as an alternative to file upload. Pasting from a DOCX or PDF often imports formatting artifacts — extra line breaks, smart quotes, bullet characters that show up as boxes, and section headers that lose their formatting.

Keep a plain-text version of your resume (Markdown is fine — most paste boxes strip the formatting anyway) and paste from that. Use plain Unicode bullet characters (•) or dashes (-), single line breaks between bullets, and double line breaks between sections.

ATS-by-ATS notes

The behavior varies by ATS. Notes below are based on each vendor's public documentation and applicant-facing help pages. Specific tenant configurations can override these defaults — when the application form tells you the accepted formats, that overrides any general rule.

Greenhouse

Greenhouse's hosted application pages (boards.greenhouse.io) accept DOC, DOCX, PDF, and TXT for resume upload. Modern Greenhouse parsing handles text-layer PDFs reliably. RoleWorth treats Greenhouse as a launch-grade ATS for the submission gate. Default to PDF unless the employer's application form asks for something else.

Lever

Lever's application forms (jobs.lever.co) accept PDF, DOC, and DOCX. Lever's parsing has historically handled both well. RoleWorth treats Lever as launch-grade for submission. Default to PDF.

Ashby

Ashby's application forms (jobs.ashbyhq.com) accept PDF, DOC, and DOCX. Ashby is one of the newer ATSes and its parsing is generally good with modern PDFs. RoleWorth treats Ashby as launch-grade for submission. Default to PDF.

Workday

Workday is a multi-tenant ATS where the form is heavily customized per employer. Most modern Workday tenants accept PDF and DOCX. Some still strongly prefer DOCX, particularly older deployments at large enterprises. Workday also has aggressive auto-fill that reads the uploaded file and pre-populates the form — that auto-fill is sometimes more reliable from DOCX than PDF, depending on the tenant's parser version. RoleWorth routes Workday to manual-required review because the submission form varies too much across tenants for a single automated flow. If the tenant lets you re-upload, try DOCX if PDF auto-fill produced garbage fields.

iCIMS

iCIMS deployments vary widely. Many older iCIMS configurations still prefer or require DOCX. iCIMS's resume parser is most reliable with DOCX in those deployments. If the application form lists DOCX first or only, send DOCX. RoleWorth routes iCIMS to manual-required review.

Oracle Taleo

Taleo is the legacy ATS most likely to require DOCX. Many Taleo deployments at large enterprises and government agencies still ask for DOCX as the primary attachment. Taleo's parser is older and PDF support, while present, is less reliable than DOCX. Send DOCX for Taleo unless the form explicitly asks for PDF.

SmartRecruiters

SmartRecruiters accepts both DOCX and PDF with modern parsing. Default to PDF. RoleWorth routes SmartRecruiters to manual-required review because the form flows have enough employer-level variation to make a fully automated submission unreliable.

LinkedIn Easy Apply

LinkedIn Easy Apply accepts PDF, DOC, and DOCX up to 5 MB. LinkedIn parses the uploaded resume but the recruiter usually receives both the uploaded file and a LinkedIn-rendered profile, so layout matters less than at company ATSes. Default to PDF. RoleWorth routes LinkedIn to manual-required review for legal and policy reasons regardless of file format.

What RoleWorth's exports do today

RoleWorth's Application Kit exports three formats from the approval gate: Markdown (plain text, paste-friendly), PDF (text-layer, ATS-parseable), and DOCX (editable, parser-friendly). DOCX/PDF output is backed by the C-1 export QA matrix across the three launch templates, with deterministic OOXML snapshots, selectable PDF text checks, binary round-trip checks, and ATS preview simulation for Greenhouse, Lever, Ashby, Workday, and iCIMS. A broken DOCX export is worse than no DOCX export, so validation still fails closed before rendering malformed files.

If you need DOCX today, export DOCX directly from the approved Application Kit and open it once in Word or Google Docs before submitting. That final visual check is still the right state for any ATS submission, even when the exporter is QA-backed.

Pre-submission checklist

• The file has a real text layer (you can select and copy text from it).
• The file name is FirstLast_Role_Company.[pdf|docx], not Resume_Final_v3.[pdf|docx].
• If the application form lists accepted formats, you sent one of them.
• If the form requires DOCX, you sent DOCX (not PDF renamed to .docx).
• The file is under 5 MB. Most ATSes cap file size lower than that.
• No images, graphics-only sections, or text in headers/footers that the parser may skip.
• Section headings use standard names (Experience, Education, Skills) so the parser knows where sections start.
• Dates use a consistent format (MMM YYYY) so the parser can extract them.
• No tables or multi-column layouts unless you have tested the parser output.
• The top third of the resume reflects this role's buying criteria — not your generic career summary.