Resume parsing failed: why it happens and how to fix the file

Part of our ATS application guides: Workday · Greenhouse · Taleo · iCIMS · Status meanings

"Resume parsing failed" means the application system couldn't turn your file into fields: name, employer, title, dates, education, skills. It's almost always the file, and the fix is a plain one: export a single-column, text-based DOCX or PDF with no tables, text boxes, columns, or images, put your contact details in the body rather than a header, and upload it again. Then check every field the parser filled, because a parse that "succeeds" can still be wrong.

What the parser is trying to do

Every applicant tracking system converts your file to plain text, finds the sections, and maps the pieces to fields it can search: this string is a job title, this one an employer, this pair is a date range. The structured result is what recruiters filter and what screening rules read. The attachment itself is for a person to open later. A parse fails when the conversion to text produces nothing usable, or when the layout defeats the section finder.

The six things that break parsers

1. Columns. Parsers read left to right, top to bottom. Two columns interleave into one stream: your job title lands next to a skills list, dates separate from their roles. Fix: one column, full width.
2. Tables and text boxes. Many templates place sections inside tables or floating boxes. Some parsers skip them entirely. Fix: plain paragraphs and bullet lists; no table for the skills section.
3. Scanned or image PDFs. A scan, a photo, or an export from a design tool is a picture of text. The parser extracts nothing and reports a failure or an empty profile. Fix: export from Word or Google Docs, or print to PDF from the document, never from an image.
4. Headers and footers. Contact details in the page header are read last, dropped, or attached to the wrong section. Fix: name, email, phone, and location in the body at the top.
5. Icons, symbols, and decorative bullets. Phone and email icons replace the words the parser keys on; unusual glyphs become garbage characters. Fix: standard bullets, the words "Email" and "Phone" if you label them at all.
6. Date formats it can't read. "Fall 2023," "'21 to '23," or dates in a right-aligned tab column confuse the date finder. Fix: "Jan 2021 to Mar 2023," written with each role.

Two more that produce a hard failure rather than a bad parse: a password-protected or encrypted file, and a file over the system's size limit, often around 2 to 5 MB. Save an unprotected copy; compress or remove images.

How to check what the system parsed

Each system shows the parsed fields somewhere before you submit. Check them there; the parser doesn't run again after you fix the file unless you re-upload.

• Workday. After Autofill with Resume, the My Experience page shows the parsed work history, education, and (rarely) skills. Workday's admin documentation says the parser doesn't auto-fill the Skills or Languages fields at all, so add those by hand. If the employer never turned parsing on, every field is blank and that is normal. See why Workday makes you re-enter your resume and what to add in the skills field.
• Greenhouse. Parsed fields appear on the application form right after the upload. Greenhouse's support site documents the "unsuccessful resume parse" case; when it happens the form stays blank and you type the fields in. Our Greenhouse guide covers the form field by field.
• iCIMS. The profile page shows parsed work history and education; the skills and questionnaire sections are separate and aren't parsed. See the iCIMS guide.
• Taleo. The wizard shows parsed entries on the experience page, then re-asks everything. See the Taleo guide.
• Lever and Ashby. Short forms; the parser fills name, contact, and links. Work history is usually read from the attachment by a person. Check the Lever guide.
• SuccessFactors. SAP's knowledge base documents parsing failures on image-based and protected files; the same single-column fix applies.

Does a failed parse hurt your application?

The failure itself doesn't. Every system keeps the attachment, and a recruiter who opens your application can read it. What hurts is what the failure leaves behind: blank or wrong fields. Recruiter searches, filters, and screening rules run on the fields, so an empty skills field excludes you from a skills filter and a garbled title hides you from a title search. Fix the fields before you submit and the parse error has cost you nothing but time.

A parsing checklist before you upload

• One column, full width, standard fonts.
• Text-based DOCX or PDF, exported from the document, no scans.
• Contact details in the body at the top, written as words.
• Section headings a parser expects: Experience, Education, Skills.
• Month and year on every role, in the same format.
• No tables, text boxes, icons, or images.
• Under 2 MB, not password protected.
• After upload: check every parsed field, then add skills by hand.

Frequently asked questions

Why did my resume upload but parsing failed?

The upload and the parse are separate steps. The file was saved as an attachment, then the parser tried to read it into fields and couldn't. Scanned or image PDFs, password-protected files, and layouts built from tables or text boxes are the usual causes. Re-export as a plain single-column DOCX or text-based PDF and upload again.

Is PDF or Word better for ATS parsing?

Either, as long as the PDF is text-based. A PDF exported from Word or Google Docs parses as well as the DOCX. A PDF made by scanning or by exporting a design tool's artboard is an image and parses as nothing. When a system lists DOCX first, use DOCX.

Can I test how an ATS will parse my resume?

Roughly. Open the PDF, select all, and paste into a plain text editor. If the text comes out in reading order with your headings, dates, and bullets intact, a parser will read it about as well. If columns interleave or sections vanish, fix the layout.

Does a parsing error reject my application?

No system rejects an application for a parse error alone. The risk is what follows: fields left blank or wrong, which hide you from recruiter searches and can trip a screening rule. Fix the fields and the attachment is still there for a human to read.

Why are my skills empty even though the parse worked?

Some systems never fill the skills field from a resume. Workday's own admin guide says the parser doesn't auto-fill Skills or Languages. Enter them by hand in every system; they're the fields recruiters filter on most.

Last updated October 15, 2026. Sources: Workday admin guide on resume parsing; Greenhouse Support, "Unsuccessful resume parse"; SAP Knowledge Base on SuccessFactors parsing. If a system's behavior differs from what is described here, tell us.