blog

Does an ATS Read PDF Resumes? What Actually Happens to Your File

by

If you've ever submitted a polished PDF résumé and heard nothing back, you've probably wondered: does an ATS even read PDF resumes?

Short answer: yes, most modern Applicant Tracking Systems can read PDFs — but reading and parsing correctly are two different things. A PDF that looks perfect to you can come out scrambled, reordered, or half-empty once the software strips it down to plain text. And what the ATS extracts is what a recruiter searches and filters on.

Here's exactly what happens to your file, what breaks it, and how to make sure yours survives the trip.

What an ATS actually does with your resume

An Applicant Tracking System (ATS) is the software employers use to collect, store, and filter the resumes they receive. When you hit "Apply," the system doesn't see your layout, your fonts, or your two-column design. It does one thing first: it converts your file into raw text and tries to map that text into fields — name, contact, work history, skills.

Recruiters then search and filter that extracted text by keyword. If the parser mangled your layout, or your resume is missing the terms they search for, you can be screened out before a human ever opens your file.

So the real question isn't "does an ATS read PDFs" — it's "does the ATS read my PDF correctly?"

Yes, an ATS reads PDFs — with one big caveat

Years ago, the safe advice was "never use a PDF." That's outdated. Today, the major ATS platforms — Workday, Greenhouse, Lever, Taleo, iCIMS and others — parse text-based PDFs without much trouble.

The caveat: they parse text-based PDFs. They struggle, or fail completely, with:

  • Scanned or image-only PDFs. If your resume is a picture of text (a scan, a screenshot, or exported from a design tool as an image), there is no selectable text for the ATS to read. It sees a blank page. This is the single most common way candidates get auto-rejected without knowing it.
  • PDFs built for visual layout, not for reading order. This is where most "text-based" PDFs quietly fail.

Do different ATS platforms read PDFs differently?

Yes — and it's worth knowing where your application is headed. Modern, cloud-based systems like Greenhouse, Lever, Workday and Ashby have solid PDF parsers and handle clean, single-column text PDFs well. Older or more rigid platforms — Taleo is the classic example — are far less forgiving, and they're a big reason "just use a Word doc" became standard advice in the first place.

The catch: you almost never know which ATS an employer uses. A job posting on a company careers page might run on any of a dozen systems, and large companies often run several. That's why the smart move isn't to optimise for one parser — it's to keep your file simple enough that every parser reads it correctly. A clean, single-column layout is the lowest common denominator that works everywhere, from the newest platform to the oldest.

What breaks PDF parsing

Even a proper text PDF can parse badly. The usual culprits:

  • Multiple columns and sidebars. An ATS reads top-to-bottom, left-to-right. A two-column layout often gets read straight across — so your skills column and your job titles get interleaved into nonsense.
  • Tables. Skills or experience laid out in a table frequently lose their structure or get dropped entirely.
  • Headers and footers. Many parsers ignore content in the header/footer region — which is exactly where people put their name, email, and phone number.
  • Icons and graphics. A phone icon next to your number carries no text. "Skill bar" graphics that show "Python ▰▰▰▰▱" tell the ATS nothing — there's no word "Python" it can read.
  • Text inside images. A logo, a headshot, or a designed banner with text in it is invisible to the parser.
  • Unusual fonts or heavy styling. Decorative fonts and exotic character encodings can produce garbled output.

The frustrating part: none of this is visible to you. Your PDF looks great on screen. The damage only shows up in the extracted text the ATS actually reads.

A real example: how a two-column resume falls apart

Say you use a popular two-column template — a narrow left column with "Skills" and "Contact," and a wide right column with your experience. To you it looks clean and organised. To a parser reading left-to-right, top-to-bottom, the text can come out interleaved like this:

Skills Python SQL John Smith Senior Engineer Contact Acme Corp 2021–Present john@email.com Led a team of...

Your skills, your name, your job titles and your employer all blur into one unreadable run of text. The system can't tell which is which, so the fields it maps — and the keywords a recruiter later searches — end up wrong or missing entirely. The resume looks perfect; it just doesn't survive being flattened into plain text. A single-column version of the exact same content parses cleanly every time, because there's only one possible reading order.

How to see what an ATS extracts from your PDF

This is the part most candidates never check — and it's the fastest way to catch a parsing problem.

You can preview the exact plain text an ATS pulls out of your file with our free ATS resume checker. Upload your PDF and it shows you, in seconds, the raw text a machine reads — no colors, no columns, no design. If your name is missing, your sections are jumbled, or whole chunks are gone, the ATS sees it that way too. Paste a job description and it also scores how well your resume matches and flags the keywords you're missing.

If the preview looks clean and complete, your PDF parses fine. If it looks scrambled, that's your fix list.

PDF vs DOCX: which is safer for ATS?

Both work for most modern systems, but they fail differently:

  • A simple, single-column .docx is the most universally safe choice, especially for older or more rigid ATS platforms. Word documents have a predictable structure that almost every parser handles well.
  • A text-based PDF is fine for the majority of modern ATS as long as it avoids columns, tables, headers/footers and images. PDFs also preserve your formatting consistently across devices, which DOCX doesn't always do.

A good rule of thumb: if the job portal accepts either, and your design is anything other than a clean single column, submit the .docx. If your resume is already simple and single-column, a text PDF is perfectly safe.

Never submit a scanned or exported-as-image PDF in either case.

How to make your PDF ATS-friendly

A quick checklist:

  1. Use a single column. No sidebars, no text boxes, no tables for layout.
  2. Put contact details in the body, not in the header or footer.
  3. Use standard section headings — "Experience," "Skills," "Education." Creative headings confuse parsers.
  4. Spell out skills as text, including the full name and common abbreviation (e.g. "JavaScript (JS)"). Skip skill-bar graphics.
  5. Drop icons, logos and headshots — they carry no readable text.
  6. Export real text, not an image. From Word or Google Docs, use "Save/Download as PDF," not "print to image" or a design-tool image export.
  7. Check the output. Run it through an ATS checker and read the extracted text before you apply.

Quick answers

Does an ATS read PDF resumes? Yes — modern systems parse text-based PDFs. The risk is layout (columns, tables, headers, images) and scanned/image PDFs, which parse poorly or not at all.

Is PDF or Word better for ATS? A simple single-column .docx is the safest default; a clean, single-column text PDF is also fine for most modern systems.

Why does my PDF look fine but get rejected? Because the ATS reads the extracted text, not your layout. A nice-looking PDF can produce scrambled or incomplete text. Preview it to be sure.

How do I know if my PDF is ATS-friendly? Check the plain text an ATS pulls from it. If everything is present and in order, you're good.

Do ATS systems reject PDFs automatically? No — they don't reject by file type. They reject based on what they can (or can't) read from the file. A clean PDF is fine; a scrambled or image-based one effectively rejects itself by producing unusable text.

Does the length of my PDF matter to an ATS? Length doesn't break parsing, but very long resumes dilute your keywords and some systems truncate them. One to two focused pages is the safe range.

Should I remove my photo for an ATS? Yes. A headshot is an image with no parsable text, it can confuse some parsers, and in many markets it invites bias. Leave it off.

A clean PDF gets you read; the right keywords and results get you shortlisted. Before you send your next application, see exactly what an ATS sees in your resume — free, no sign-up.

Looking for your next role? Join Hiretop's talent network and get matched with real engineering jobs.