Resume File Format & Naming: PDF vs Word, and What to Call the File
You can spend a week on bullets and lose the first impression in the last ten seconds: the wrong format reflows your layout, the wrong file name buries you in a downloads folder, and a careless export hands the screener a PDF with browser clutter in the margins. Three small choices — format, name, export — and each has a clear right answer.
PDF, with one exception
Send a PDF unless the posting says otherwise. The reason is control: a PDF locks layout and fonts, so the document the screener opens is the document you approved. A .docx reflows on machines with different fonts and page settings — your carefully budgeted one page can arrive as a page and a quarter — and it happily carries tracked changes and comments you forgot were there. Modern ATSs parse text-based PDFs without trouble; "PDF breaks the ATS" is a decade out of date (what breaks parsers is layout, not format — the ATS guide covers that).
The exception is mechanical: when a posting or a recruiting agency explicitly asks for Word, send Word. Agencies reformat and re-brand resumes before forwarding them to clients — the .docx request is about their workflow, not your judgment. And a short never-list: Google Docs share links (permissions roulette), .pages (opens nowhere), .txt, and photos or scans of a printed resume.
Name the file like it leaves your computer — because it does
A recruiter's downloads folder is fifty files named resume.pdf, resume(2).pdf, and Untitled document.pdf. Your file name is findability plus a first signal of care:
✗ "resume_new_FINAL_v7 (2).pdf"
✓ "Jordan-Reyes-Resume.pdf"
Name first, then "Resume", hyphens between words. Applying to more than one kind of role? Add the track: Jordan-Reyes-Resume-Data-Analyst.pdf. Version numbers, dates, and drafts markers are metadata for your folder — keep them in your local copies and strip them from what you send. The same convention goes for the letter: Jordan-Reyes-Cover-Letter.pdf, so the pair sorts together (when a letter is worth sending at all).
Export clean, then actually open it
Most resume disasters at this stage come from skipping one step: opening the PDF you just made before attaching it. A ninety-second checklist:
- No browser clutter. Print-to-PDF from a browser can stamp the date, page title, and URL in the margins unless the page controls its print margins. (PlainResume's export sets this up so the PDF comes out clean.)
- Selectable text. Try to select and copy a line. If you can't, the file is an image and an ATS reads an empty page — this is the single most disqualifying export mistake.
- Page count. The PDF, not the editor, is the truth about whether you fit the page.
- Sane size. A text resume is well under 1 MB. Multi-megabyte files mean embedded photos or scans — both problems in themselves.
- Metadata sweep. The file you rename before sending should be a copy, not your "final_v7" original.
Then attach the file rather than pasting the text into the email body — the formatting you locked in the PDF is the whole point.
Export was designed in, not bolted on. PlainResume prints to a clean, text-based PDF with no browser clutter and a live page-count badge, so what you preview is what the screener opens. Free, no sign-up, no paywall — everything stays in your browser.
Build your resume free →Frequently asked questions
PDF or Word?
PDF by default — it locks layout and fonts, and modern ATSs read text-based PDFs fine. Send .docx only when a posting or agency explicitly asks; they reformat resumes and need an editable file.
What should I name my resume file?
Firstname-Lastname-Resume.pdf, plus the role track if you need several versions. Keep version numbers and dates in your local copies, never in the file you send.
How do I know an ATS can read my PDF?
Select-and-copy test: if you can copy the text, a parser can read it. Scans and image exports fail it — and read as an empty document.