Resume file format: PDF vs DOCX vs plain text

The default: text-based PDF

PDF locks your layout on every device and every ATS that will ever open it, and modern parsers read text-based PDFs reliably. Unless the posting says otherwise, export PDF. The one hard requirement: the text must be selectable — if you can’t copy a line out of your own PDF, a parser can’t read it either.

When DOCX is the right answer

Some agency workflows, government portals and older enterprise ATS explicitly request Word files, and a few portals re-render resumes into their own template from DOCX. When the posting names .doc/.docx, send a real DOCX export — never a PDF renamed to .docx; the extension must match the actual format or the upload fails validation.

When plain text wins

Application form fields ("paste your resume here"), some job-board quick-apply flows, and email bodies where attachments are refused. Keep a .txt version with standard headings, hyphen bullets, and one blank line between sections — it pastes cleanly anywhere. RezUp exports TXT alongside PDF and DOCX for exactly this.

Formats to never send

Pages, ODT, RTF, HTML, PNG/JPG screenshots, and Canva/design-tool exports that flatten text into curves. Every one of them either fails to open on the reviewer’s machine or parses as an empty document. If your resume lives in a design tool, re-create it in a text-first editor before applying.

Fonts and embedding

Stick to widely available fonts (system fonts or embedded standard faces). A PDF with non-embedded exotic fonts renders as tofu boxes on machines without them; a DOCX with a missing font silently reflows and can push your resume to a second page. Every RezUp template uses embedded, parser-safe fonts.

File naming

"Maya-Chen-Resume.pdf": your name, the word resume, nothing else. No dates, versions, or "final_v3 (2)". The filename appears in the recruiter’s ATS and download folder — it should identify you, not your revision history.

File size

Keep it under 1–2 MB. Text-based exports are naturally tiny (tens of KB); a multi-megabyte resume almost always means embedded photos or scans — both of which you should remove anyway. Some portals hard-reject uploads over 2 MB.

One column, whatever the format

Format choice can’t rescue a layout parsers can’t read. Tables, text boxes and multi-column designs scramble in every format; a clean single-column structure survives PDF, DOCX and plain text alike. Choose structure first, format second.

The renamed-extension trap

Renaming resume.pdf to resume.docx (or vice versa) is the single most common upload failure: the portal checks the real file signature, not the name. Always export to the requested format from your editor.

Test what the parser sees

Copy-paste your exported file into a plain-text editor. If your sections come out in order, with readable headings, dates and bullets, an ATS will cope. Our free ATS checker parses your actual PDF or DOCX in the browser and shows exactly what was extracted.

Keep all three exports in sync

The dangerous state is a PDF that says one thing and a DOCX that says another. Regenerate every format from the same source after each edit — in RezUp all exports render from the same data, so they can’t drift.

The decision in one line

PDF by default · DOCX only when explicitly requested · plain text for paste-in forms · never images or design-tool exports · name the file after yourself · test the parse before you send.