Guide 3 min read

Can ATS read PDF resumes? Yes — with one caveat

Yes, every major applicant tracking system reads PDF resumes — as long as the PDF contains a real text layer. A PDF exported from Word, Google Docs, or a resume builder parses fine. A PDF that is secretly a photograph — scanned pages, or a design tool exporting text as outlines — contains nothing a parser can read.

Updated September 1, 2026

Text-layer PDFs vs picture PDFs

A PDF is a container, and what it contains decides everything. Export from a word processor and the file stores actual characters with position data — parsers extract them cleanly. Scan a printed resume, or export from a design tool with text converted to curves, and the file stores an image of letters instead of letters. To a parser that PDF is as readable as a photo of a menu.

The ten-second test: open your PDF and try to select and copy a sentence. If you can highlight individual words and paste them elsewhere, you have a text layer. If your cursor draws a selection box over the whole page like it is a picture, you have an image PDF, and no application portal will extract anything from it. Some systems run fallback OCR on image PDFs, but OCR output is unreliable enough that you should never depend on it.

When DOCX beats PDF

A handful of older or heavily customized ATS configurations still parse DOCX marginally better, because Word files store text in document order with explicit structure, while PDFs store positioned fragments the parser must reassemble. If a specific application portal explicitly asks for Word format, believe it — that employer knows their own pipeline.

The other DOCX case is recruiting agencies. Agency recruiters often edit resumes before forwarding them to clients — stripping contact details, adding a logo — and they will ask for Word because they need an editable file. For direct applications to companies, a text-layer PDF is the default: it locks your layout, renders identically everywhere, and parses reliably in every mainstream system.

PDF settings that quietly cause trouble

Avoid password protection and printing restrictions — a locked PDF can refuse to yield text to a parser at all. Avoid gigantic file sizes from embedded photos; portals enforce upload limits and photos add nothing an ATS can use. Flatten unusual fonts by embedding them on export, which every mainstream editor does by default, so characters do not silently substitute.

If your resume comes from a design tool, check the export settings for an option like "outline text" or "convert text to curves" and make sure it is off. And after any export, repeat the copy-paste test once. The failure mode is silent — the file looks perfect to you, contains nothing for the machine, and you would never know why applications disappear.

Frequently asked questions

How do I know if my PDF has a text layer?

Open it and try to select a single word with your cursor. If you can highlight words and copy them, the text layer exists. If selection draws a box over the page like an image, it is a picture PDF and parsers will extract nothing from it.

Should I ever submit a Word file instead of a PDF?

Submit DOCX when the portal explicitly requests Word format or when a recruiting agency asks for an editable file to forward to clients. Otherwise a text-layer PDF is the safer default — fixed layout, universal rendering, and reliable parsing in every major system.

Do ATS run OCR on scanned resumes?

Some systems attempt OCR as a fallback, but the output is error-prone — misread characters, merged words, broken dates. Treat OCR as a safety net you never want to rely on. If your resume exists only as a scan, rebuild it as real text before applying.


Upload your PDF to the free scorer — it parses the file exactly the way an ATS does and tells you immediately if your text layer is missing or scrambled.

Apply this to your role
More guides
Do ATS automatically reject resumes? The truth
The '75% of resumes are rejected by ATS' claim is folklore. What actually filters you out — recruiter search and knockout questions — and how to survive both.
ATS-friendly resume checklist: what actually matters
The 12-point checklist that keeps resumes parseable in Workday, Greenhouse, Lever and iCIMS — and the popular 'rules' you can safely ignore.
Resume keyword stuffing: why it backfires
Cramming keywords into your resume doesn't beat modern ATS — and the recruiter who opens it will see exactly what you did. What to do instead.
The white text resume trick: why it fails in 2026
Hiding invisible keywords in white font is the oldest ATS hack — and the fastest way to look dishonest, because every parser reveals it instantly.
Can employers tell if AI wrote your resume?
Recruiters can't run a detector, but AI-written resumes have tells — inflated adjectives, no numbers, generic bullets. How to use AI without the slop.
Resume parsing errors: why your resume looks scrambled
Uploaded your resume and watched the fields fill with garbage? The seven layout choices that scramble parsers, and how to fix each one.
Icons, skill bars and graphics on a resume: the cost
Phone icons, star ratings, and skill bars look polished — and parse as nothing. What ATS do with resume graphics, and what to use instead.
Tables and text boxes on resumes: how they break parsing
Tables and text boxes are the stealthiest resume killers — content inside them extracts out of order or vanishes. Why it happens and the clean alternative.
Contact info in resume headers: the silent failure
Putting your name and contact details in the document header looks tidy — and many parsers never read it. Where contact info must actually live.