What Is ATS Parsing? How It Works and What Breaks It
Parsing happens before scoring. If your resume doesn't parse correctly, it doesn't matter how well-matched your keywords are — the ATS can't read them.
What is ATS parsing?
ATS parsing is the process by which an Applicant Tracking System reads your resume file and extracts structured data from it. Before a single keyword is scored or a candidate is ranked, the ATS must first parse your resume — identifying and separating your name, contact information, work experience, education, and skills into distinct fields in the system's database.
Parsing happens automatically in seconds, immediately after you submit your application. The recruiter never sees the raw file — they see a structured candidate profile populated from the parsed data. If parsing fails or produces errors, the recruiter sees incomplete or scrambled information, and your resume scores poorly regardless of your actual qualifications.
Understanding how ATS processes applications gives essential context for why parsing accuracy matters so much.
How does resume parsing work?
Resume parsing follows a consistent sequence:
Step 1 — File received. Your resume file (.docx, PDF, or other format) is received by the ATS. The system records the submission timestamp and sends you an automatic confirmation email.
Step 2 — Text extracted. The parser attempts to extract all text from the file. For .docx files, this process is straightforward and reliable. For text-based PDFs, most modern parsers handle this well. For image-based PDFs (Canva exports, scanned documents), text extraction fails completely — the system receives no readable content.
Step 3 — Content categorized. The extracted text is analyzed to identify section boundaries and content types. The parser looks for recognizable patterns: contact information usually appears at the top, dates adjacent to employer names indicate work experience, institution names adjacent to degree titles indicate education, and so on. Standard section headings like "Work Experience," "Education," and "Skills" make this categorization reliable.
Step 4 — Data stored in candidate profile. The categorized content is stored in structured fields in the ATS database. Your name goes into the Name field, your phone number into the Phone field, each job into a separate experience record with employer, title, dates, and responsibilities — and so on. This is the profile the recruiter views when reviewing your application.
Step 5 — Scoring. With the data correctly structured, the ATS runs keyword matching against the job description and calculates your match score. Errors in steps 2–4 mean your content doesn't score correctly.
What causes ATS parsing errors?
Parsing errors occur when the resume contains elements the parser cannot handle. The result is scrambled data, missing content, or incorrectly categorized sections.
Tables. Tables are the most common cause of parsing failures. The parser doesn't understand table structure — it reads the content in an unpredictable order, mixing your job title from one cell with your employer from another, or merging skills from one column with education from another. Even simple layout tables (used to position dates next to job titles) cause problems.
Text boxes. Content inside text boxes in Word or Google Docs is often completely invisible to ATS parsers. A skills section formatted as a text box may simply disappear from the parsed output, contributing nothing to your score.
Multi-column layouts. ATS parsers read text linearly from left to right, top to bottom. A two-column layout is read as if both columns were a single stream of text — mixing the content of the left column with the right column at each line position. The result is job titles merged with education dates, skills merged with company names.
Headers and footers. Most ATS systems cannot read text placed in the header or footer of a Word document. Contact information placed in a header — a common template design — becomes invisible to the parser.
Image-based PDFs. A resume exported as a PDF from Canva, Figma, Adobe InDesign, or Photoshop is saved as an image. The parser receives a picture of text it cannot read. Your entire resume appears blank.
Unusual fonts. Decorative or custom fonts not installed on the ATS server may be substituted or dropped during text extraction, causing characters to be garbled or missing.
Graphics, icons, and images. Any non-text element is invisible to parsers. Skill rating bars, icons, profile photos, decorative dividers — none of these are read or scored.
Non-standard section headings. Section labels that don't match expected patterns cause the parser to misclassify content. If you label your work history "Career Journey," the parser may not recognize it as work experience. That content may be miscategorized or excluded from scoring entirely.
How to test if your resume parses correctly
The plain text paste test is the most reliable method:
- Open your resume in Word, Google Docs, or your PDF reader
- Select all text (Ctrl+A or Cmd+A) and copy it
- Paste into a plain text editor — Notepad on Windows, or TextEdit on Mac set to plain text mode
- Read through the result in order
If your resume parses correctly, you should see:
- Your contact information at the top
- A logical summary (if included)
- Your work experience entries in order, with employer, title, dates, and bullet points
- Your skills listed as plain text
- Your education entry
If sections are scrambled, text from different parts appears merged, or major sections are missing, ATS will have the same problem. Anything that doesn't survive the paste test won't parse reliably.
Check your PDF for selectable text. Open your PDF and try to click and drag to highlight individual words. If you can select specific words, the PDF is text-based and parseable. If clicking selects the entire page as a single block (or as an image), it's an image-based PDF and will fail parsing completely.
ATS parsing by file type
Different file types have different parsing reliability:
| File Type | Parsing Reliability | Notes |
|---|---|---|
| .docx | Best | Most reliable across all ATS platforms. Default recommendation. |
| Text-based PDF | Usually fine | Created from Word/Google Docs. Most modern parsers handle well. |
| .txt | Parses but loses context | All text is extractable but section structure may be unclear without formatting cues. |
| Scanned PDF | Fails completely | An image. No text is extractable. Resume appears blank to ATS. |
| .pages | Unpredictable | Apple format with limited ATS support. Convert to .docx before submitting. |
| Image files (.jpg, .png) | Fails completely | Not a document format. Never submit. |
The practical rule: submit .docx by default. If you must submit a PDF, create it directly from Word or Google Docs (File → Export as PDF or Print to PDF), not from a design tool.
Frequently asked questions about ATS parsing
What does parse resume mean? Parsing a resume means the ATS software reads your resume file and extracts structured data from it — your name, contact information, work experience entries, education, and skills — and organizes them into separate fields in the system's database.
Can ATS read PDF? ATS can read text-based PDFs — those created directly from Word or Google Docs. ATS cannot read image-based PDFs created by design tools like Canva or Photoshop, because these save the resume as an image rather than as extractable text.
Does ATS read tables? Most ATS systems cannot read tables correctly. Table cells are read in unpredictable order, mixing content from different columns and rows into scrambled text. Use plain paragraph text and bullet points instead.
