- The short answer
- How PDFs parse
- How Word files parse
- When Word is still required
- Export settings that protect your PDF
- File naming: the 3-second rule
The short answer
For most modern ATS platforms, PDF is the safer default — it preserves your layout, fonts and text exactly as designed, and modern parsers handle standard PDFs reliably. The classic advice “send Word so the ATS can read it” dates from an older generation of software. Today, the balance has flipped: a clean, text-based PDF is both human-beautiful and machine-parseable.
How PDFs parse
Parsing quality depends on how the PDF was created. A PDF exported directly from a word processor or the Resume Builder’s print function contains real, selectable text — parsers read it cleanly. A PDF that was scanned from paper is an image: parsers must run OCR, accuracy drops, and some text may come back garbled. Rule: always export, never scan.
How Word files parse
Word documents also parse well in modern systems, and some older or smaller ATS setups still prefer them. The risks are layout-based: text boxes, tables and multi-column designs confuse parsers exactly as they do in PDF. If you send Word, keep the layout as plain as your PDF version.
When Word is still required
Follow the employer’s instructions first — they override every best practice. Three cases where Word remains the right answer:
- The application form explicitly asks for .doc or .docx.
- You are emailing a small company that will edit your resume (rewrite with their template).
- The portal states a preference for Word to avoid parsing issues on their legacy system.
Export settings that protect your PDF
- Export, don’t print-to-image. Use the browser’s “Save as PDF” or the Resume Builder’s print view — never print to a scanned copy.
- Embed fonts (default on). Keeps characters intact when the reader lacks your fonts.
- Keep text selectable. A PDF you can Ctrl+F through will parse fine.
- Strip metadata. Some PDFs embed your name and software details in properties — clean them before sharing publicly (the Anonymizer guide covers privacy).
File naming: the 3-second rule
Recruiters and systems sort dozens of files named “resume.pdf” every day. Make yours identifiable in three seconds: FirstName_LastName_Resume_Role.pdf — for example Alex_Rivera_Resume_SeniorProductDesigner.pdf. The same rule applies to cover letters (Alex_Rivera_CoverLetter.pdf). A clean name signals professionalism before the file is even opened, and it survives every ATS upload unchanged.
Whatever format you choose, open your own file before submitting and read it as text: if you can select and copy every line cleanly, the parser will too.
How to create a text-perfect PDF
The phrase “text-perfect” is the whole game: the PDF must contain selectable, ordered text — not outlines, not images, not embedded-only fonts. Here is the exact routine:
- Build the resume in the Resume Builder or your word processor with standard fonts and one column.
- Use the browser’s Print → Save as PDF (or the Resume Builder’s print view), which embeds real text.
- Open the PDF and press Ctrl+F to search for your name. If you can select and copy every line, you’re good.
- Check the file size — a 100KB–2MB PDF is normal; anything over 10MB usually means embedded images or scanned pages.
PDF pitfalls that quietly hurt you
| Pitfall | What happens |
|---|---|
| Scanned-from-paper PDF | Parser runs OCR; errors garble keywords and contact info |
| Fonts not embedded | Reader substitutes fonts; layout and characters shift |
| Text boxes / tables | Reading order breaks; fields map to wrong sections |
| Metadata with your personal info | Name/email leak into file properties when shared |
| Huge images as background | Slow uploads; parsers ignore or misread decorative graphics |
When Word wins anyway
Keep an updated .docx alongside your PDF for the cases that need it: small employers who edit resumes, portals that explicitly request .doc, and recruiters who ask for an “editable version” after an interview. Keep both versions identical in content, and regenerate them from the same source so they never drift apart.
What recruiters actually do with the file
Understanding the reader’s workflow explains every rule in this guide. A recruiter opens your PDF, spends six seconds confirming role, recency and contact info, then either files it or forwards it. The ATS does the same work in microseconds — it extracts the same three fields, plus your full keyword coverage. So the file must be two things at once: immediately scannable by a human and cleanly extractable by a machine. A text-perfect PDF with standard section names satisfies both. That is why the same formatting rules appear in the ATS guide, the formats guide, and this one — they aren’t separate checklists, they are one requirement seen from three angles.
And if a job portal lets you upload both a PDF and a pasted-text version, do exactly that: upload the clean PDF and paste the plain-text version from the Plain Text Converter into the form. The text version guarantees the parser sees every keyword even if the PDF extraction stumbles.
