NEWPractice your interview out loud with an AI voice coach.Practice interviews out loud.Try it →

Blog Resume Help

Resume Parsing Errors: The 8 Mistakes ATS Parsers Make and Fixes

Resume parsing errors scramble columns, drop contact info and misread dates. Learn the 8 common ones, a 5-minute test to spot them, and the fix for each.

Illustration of a puzzled man beside a machine scrambling a resume page — resume parsing errors
On this pageWhat are resume parsing errors?

Summary

Resume parsing errors happen when an applicant tracking system turns your file into text and fields and gets something wrong. The most common causes are columns, tables, text boxes, headers and footers, images, unusual fonts, mixed date formats and creative section names. Greenhouse's own support docs list most of these, plus a 2.5MB file limit. You can spot errors by checking the autofilled application fields and running a plain-text test, then fix them with a single-column, text-based file.

Resume parsing errors happen when an applicant tracking system (ATS) reads your file and puts the wrong text in the wrong field, or loses it entirely. The usual culprits are layout choices: columns, tables, text boxes, headers and footers, images and fancy fonts.

You rarely see these errors directly. They show up as a blank phone number on your profile, a job title glued to a skill list, or dates the system cannot read. A recruiter searching the database may then never find you.

This guide lists the eight errors parsers make most often, shows you how to catch them before you apply, and gives a fix for each.

What are resume parsing errors?

Resume parsing errors are mistakes an ATS makes when it converts your resume into searchable text and structured fields such as name, contact details, job titles, employers and dates. Text may be dropped, scrambled or filed under the wrong heading. The cause is almost always formatting, not content.

When you upload a resume, the ATS does two jobs. It extracts the raw text, then it sorts that text into fields. Workday's admin documentation describes it plainly: "Resume parsing populates fields from a resume."2

Errors can happen at either step. If extraction fails, the text never arrives. If sorting fails, the text arrives in the wrong place. Either way, the record recruiters search is not the resume you wrote.

This matters because nearly every large employer uses an ATS. Jobscan found a detectable ATS at 97.4% of Fortune 500 companies in 20266, with Workday alone at over 40%.

What causes the most common resume parsing errors?

Eight formatting choices cause most resume parsing errors: multi-column layouts, tables, text boxes, contact details in headers or footers, images and icons, decorative fonts or symbols, mixed date formats, and creative section labels. Image-only files, password-protected files and oversized files can fail to parse at all.

Greenhouse, one of the most widely used ATSs, publishes its own list. Its support article on an unsuccessful resume parse1 warns against graphics, tables, headers, footers, columns, and contact details in a header, footer or text box. Career centers at George Mason University3 and Santa Clara University4 give the same advice.

Figure 1Greenhouse lists columns, tables, text boxes, header contact details and image uploads as causes of failed parsing. Source: Greenhouse Support1.
ErrorWhat the parser doesFix
Two or more columnsReads across columns, mixing titles with skillsOne column, top to bottom
TablesFlattens cells, detaching dates from jobsPlain lines with tabs or commas
Text boxesSkips the box or drops it at the endType the text in the body
Header or footer contact infoIgnores the region, so name and email vanishPut contact lines in the body
Images, icons, skill barsCannot read text inside graphicsWrite skills as words
Decorative fonts and symbolsTurns characters into boxes or question marksArial, Calibri or Georgia; plain bullets
Mixed date formatsMisreads start and end datesOne format, such as "Jun 2022 – Mar 2025"
Creative section labelsCannot find Experience or EducationStandard headings

Two more problems stop parsing completely. Greenhouse says it "can't parse resumes larger than 2.5MB"1 and cannot read resumes uploaded as images. Parser vendor RChilli adds that "files that are corrupted or encrypted/password-protected cannot be parsed."5

Scrambled columns and tables

Columns are the single most common layout problem. A parser often reads left to right across the whole page, so a sidebar of skills gets spliced into your job history. Our guide to two-column resumes and ATS covers when a sidebar survives and when it does not.

Tables fail in a similar way. GMU's career guide warns that tables, text boxes and charts "can scramble how software reads your content."3

Lost contact details in headers and footers

Many templates put your name and email in the document header. That looks clean, but GMU notes that "some systems ignore these areas."3 The result is a candidate record with no way to contact you.

Misread dates, fonts and labels

Santa Clara's career center flags mixed styles such as "Jun. 2020 - Present" next to "2020/06 - Present" as a source of errors. Odd fonts and custom bullets cause garbled characters. Labels like "Professional Journey" or "Learning Achievements" hide your sections from the parser.

Check as you read

Does your resume follow these 4 rules?

All 4 rules. Next, check the words against a real job post.

Check my resume

Why these rulesSaved on this device

How do you spot resume parsing errors before you apply?

Run three quick checks. Upload your resume to an application form and read every autofilled field. Copy the whole file into a plain-text editor and check that the order makes sense. Then run an ATS checker that shows the parsed result. If any field is blank, merged or out of order, you have a parsing error.

Most guides stop at "avoid tables." The better move is to test the actual file, because you cannot see a parsing error by looking at your PDF.

Figure 2The autofilled application form is the parser's output, so reading it is the fastest way to spot errors. Source: Workday documentation2.

1. Read the autofill output. Many application forms parse your upload and prefill name, contact details, work history and education. That prefilled form is the parser's output. If your title lands in the company field, the ATS record has the same mistake. Our guide on how Workday parses resumes walks through this screen.

2. Run a plain-text test. Open the file, select all, and paste it into Notepad or TextEdit in plain-text mode. Read top to bottom. Text that jumps between columns, missing lines, or symbols turning into boxes all point to errors. A full plain text resume is also handy for forms that ask you to paste.

3. Use a checker that shows the parse. A good ATS checker reports what it extracted, not just a score.

Tip

Note what autofill does not fill

A blank field is not always your fault. Workday's documentation says resume parsing does not auto-fill Languages or Skills, and it skips fields the employer has hidden. Fill those by hand. A wrong value in a field that did fill is the real warning sign.

That Workday detail is easy to miss. Its admin guide states that Workday does not auto-fill Languages or Skills2. So an empty Skills box on a Workday form tells you nothing about your file.

How do you fix resume parsing errors?

Rebuild the resume as a single-column, text-based document. Move your name and contact details into the body, replace tables and text boxes with plain lines, use a standard font and simple bullets, pick one date format, and use standard section headings. Save as .docx or a text-based PDF under 2.5MB.

Fix the structure first, then the details. Most resumes need only a few changes.

  1. Flatten the layout. One column. No tables, text boxes or graphics.
  2. Move contact info into the body. Name on the first line, then phone, email, city and LinkedIn URL.
  3. Rename sections. Use Summary, Experience, Education, Skills and Certifications.
  4. Standardize dates. Same month format and the same dash everywhere.
  5. Use safe fonts and bullets. A common font and round or hyphen bullets.
  6. Save the right file. A text-based PDF or .docx, not a scan or an image export.

Here is a contact block that parses cleanly, typed in the body instead of the header.

ExampleContact block in the body, not the header

Jordan Lee

Chicago, IL(312) 555-0148jordan.lee@email.comlinkedin.com/in/jordanlee

And here is a job entry with one date format and the title and employer on separate, labeled lines.

ExampleJob entry a parser can split into fields

Operations Analyst

Northwind Logistics, Chicago, IL

Jun 2022 – Present

Cut weekly report prep from 6 hours to 2 by automating Excel pulls with Power Query

Our ATS resume format guide covers the full layout. If you design in Canva or a similar tool, check the export before you send it.

Do

  • Put your name and contact details in the main body
  • Use one column and standard section headings
  • Keep one date format from top to bottom
  • Check the autofilled fields after every upload

Don’t

  • Place contact info in a header, footer or text box
  • Show skills as bars, stars or icons
  • Upload a scanned or image-only PDF
  • Send files over 2.5MB or with a password

Does a PDF cause resume parsing errors?

Not usually. A text-based PDF exported from Word or Google Docs parses well in most modern ATSs. Problems come from image-only PDFs, scanned pages and heavily designed templates. If the employer asks for a .docx, send one. Some career centers still say .docx imports more accurately.

The file type matters less than how the file was made. If you can highlight and copy the text in your PDF, a parser can usually read it. If the PDF is a picture of text, it cannot.

GMU's career guide still recommends .docx unless a PDF is requested, saying it "imports more accurately"3 and that some systems flatten PDFs. Follow the posting's instructions first. Our article on whether ATS can read PDFs explains the tradeoffs.

What happens if your resume has parsing errors?

Your application still arrives, but the record recruiters search is wrong or incomplete. Missing contact details, merged job titles and unreadable dates make you harder to find and slower to review. Greenhouse notes that when parsing fails, details must be entered by hand, so you may also face a longer form.

Parsing errors rarely trigger an instant rejection by themselves. The harm is quieter. In Jobscan's research, 76.4% of recruiters6 said they search and rank candidates mainly by skills from the job description. If your skills were dropped or scrambled, those searches skip you.

Automatic rejections more often come from screening questions on the form. Our sibling guide to ATS knockout questions covers those.

Before you apply, run your file through the free Rezoom ATS resume checker. It shows formatting flags and the keywords it found, so you can catch resume parsing errors before an employer's system does.

Related guideHow Workday Parses Resumes: What Autofills, What Breaks, What to FixHow Workday parses resumes, from Workday's own docs: which fields autofill, why Skills stay blank, and how to fix the form before you submit.

Frequently asked questions

Why does my resume autofill wrong on job applications?

The form's parser misread your layout. Columns, tables and contact details in the header are the usual causes. Fix the file, then re-upload, or correct the fields by hand before you submit.

Can an ATS read text boxes?

Often not. Many parsers skip text boxes or move their content out of order. Greenhouse lists contact details in a text box as a cause of failed parsing.

Do icons and skill bars cause parsing errors?

Yes. Parsers read text, not graphics. A five-star rating or a skill bar is invisible, so write the skill and level as words.

What fonts are safe for ATS parsing?

Common fonts such as Arial, Calibri, Georgia and Times New Roman. Avoid decorative fonts, special symbols and custom bullet characters.

Is it worth fixing the autofilled fields by hand?

Yes. The fields you correct become the candidate record recruiters see and search. A few minutes of edits is worth it for a role you want.

How big can a resume file be?

It depends on the system. Greenhouse cannot parse resumes larger than 2.5MB. Most text-based resumes are far smaller, so a large file usually means embedded images.

Sources

We opened and read each page below. The small numbers in the text point here. Pages that carry no publication date show n.d.

  1. Greenhouse Supportn.d.

    Cannot parse resumes over 2.5MB; avoid image uploads, graphics, tables, headers, footers,…

    support.greenhouse.io
  2. Workdayn.d.

    Resume parsing populates fields from a resume; does not auto-fill Languages or…

    doc.workday.com
  3. George Mason University Career Servicesn.d.

    Some systems ignore headers and footers; tables, text boxes and charts can…

    webdocs.gmu.edu
  4. Santa Clara University Career Centern.d.

    Mixed date formats, tables, header/footer contact info, unusual fonts and non-standard headings…

    scu.edu
  5. RChillin.d.

    Corrupted or encrypted/password-protected files cannot be parsed

    help.rchilli.com
  6. Jobscan2026

    97.4% of Fortune 500 companies have a detectable ATS; Workday over 40%;…

    jobscan.co

Written by

Co-Founder and Product Lead, Rezoom

Mohammad has spent more than ten years designing consumer products and leads product at Rezoom. He writes across the whole job search, from resume sections and cover letters to interview answers and career moves.

More from Mohammad GoodiHow we write and fact-check

Was this guide useful?

Cite this guide

Goodi, M. (2026, October 9). Resume Parsing Errors: The 8 Mistakes ATS Parsers Make and Fixes. Rezoom. https://rezoom.io/resume-parsing-errors/

You have the advice. Now build the resume.

Rezoom’s AI writes your first draft, checks it against the job post and formats it in a template the software can read.

Copied