How ATS Parsers Actually Read Your Resume
If you've ever submitted a polished resume and heard nothing back, the problem may not be your experience — it may be that an applicant tracking system (ATS) couldn't read your file. This article is for job seekers who want to know exactly which fonts, margins, and layout choices keep their resume parseable, and which silently kill their chances before a human ever opens the document.
An ATS parser doesn't see your resume the way you do. It extracts raw text from your file — layer by layer, character by character — before any recruiter lays eyes on it. The system is looking for keywords, job titles, dates, and section labels. It doesn't appreciate design. It processes text.
That creates two distinct failure modes this article will help you avoid:
- Unreadable characters — caused by non-standard fonts, special glyphs, or icon-based bullets that the parser renders as symbols or blank space.
- Unparseable structure — caused by columns, text boxes, tables, and graphics that fragment or reorder your content during extraction.
Garbled text means missed keywords. Missed keywords mean a lower ATS score, regardless of how qualified you actually are.
The Best Resume Fonts for ATS (and the Ones to Avoid)
Choosing the best resume font for ATS is less about aesthetics and more about encoding reliability. A font that looks sharp in your PDF editor may map its characters to non-standard Unicode values, produce ligatures that an OCR layer misreads, or fail to embed correctly when the file is saved. The result: the parser reads "financial" as a garbled string instead of "financial."
Fonts That Parse Reliably
These fonts work because they are widely installed across operating systems, use standard glyph encoding, and have clean, unambiguous letterforms:
| Font | Style | Why It Works |
|---|---|---|
| Calibri | Sans-serif | Microsoft default; near-universal system support |
| Arial | Sans-serif | Clean glyphs, no ligature issues, extremely broad support |
| Georgia | Serif | Well-hinted for screen and print; standard encoding |
| Garamond | Serif | Readable at small sizes; ships with most Office installs |
| Cambria | Serif | Designed specifically for print readability; reliable PDF embedding |
| Times New Roman | Serif | Legacy-safe; every ATS was built expecting it |
None of these are exciting. That's the point. They are tools, not statements.
Fonts to Avoid
- Script and handwriting fonts (Pacifico, Lobster, Brush Script): OCR layers frequently misread connected letterforms as unrecognized characters.
- Icon fonts (Font Awesome used inline, Wingdings): render as symbols or empty boxes in plain-text extraction.
- Niche design fonts downloaded from sites like Google Fonts or Dafont: may not embed correctly in every PDF exporter, leaving the parser with a fallback substitution that shifts spacing and character mapping.
Quick rule: If you downloaded the font specifically because it looks unique, don't use it on a resume.
Point Size Guidance
- Body text: 10–12pt
- Section headers: 13–14pt
- Your name: 14–16pt
Anything smaller than 10pt risks poor extraction in some parsers. Anything larger than 16pt for body text wastes space and can confuse section-detection logic.
Resume Margins: The Narrow Range That Keeps Parsers Happy
Set your margins to 0.5–1 inch on all sides. That range works for virtually every ATS and for every recruiter who reads the document afterward.
Here's what happens outside that window:
- Below 0.5 inches: Text runs close to the parse boundary in some ATS implementations. Content near the margins may be clipped or ignored entirely, depending on how the file was exported.
- Above 1 inch: You're trading content space for white space. A one-page resume with 1.25-inch margins is a resume that probably needed a second page and didn't get one.
Why Margin-Shrinking Backfires
A common workaround is to shrink margins to 0.3 or 0.35 inches to squeeze everything onto one page. This is a bad trade. You risk parse-boundary clipping, and you still haven't solved the underlying problem — too much content, too little prioritization. Fix the content; don't fight the margins.
Margins also serve a purpose after the ATS passes your resume to a recruiter. A visually comfortable document gets read more carefully at the human review stage. The margins earn their space twice.
Single-Column vs. Two-Column Layouts: What ATS Can and Can't Handle
This is where most formatting mistakes happen, and it's worth being direct: the two-column resume layout is a significant ATS risk for most candidates.
How Parsers Read Columns
Most ATS parsers don't recognize column structure. They read your document left-to-right across the full page width, as if columns don't exist. A two-column layout that looks clean on screen becomes a garbled merge in plain-text extraction.
Concrete example:
Suppose your left column reads:
Project Manager | Acme Corp | 2019–2022
And your right column, at the same vertical position, reads:
Skills: Python, SQL, Agile
The parser reads across the page and produces:
Project Manager | Acme Corp | 2019–2022 Skills: Python, SQL, Agile
That's a nonsensical string. Your job title, employer, dates, and skills section are fused. The parser may fail to extract any of them correctly.
The One Exception
PDFs built with properly tagged reading order — where the document's accessibility structure explicitly defines column flow — can survive two-column layouts in modern ATS platforms. The problem: most candidates have no reliable way to verify whether their PDF exporter applied correct tagging. Word-to-PDF conversion tools vary widely. Unless you can confirm the tagged reading order in Adobe Acrobat Pro, treat this exception as theoretical.
Single-column, top-to-bottom layout is the safe default. Full stop.
What Gets Lost in Sidebars
Contact information placed in a sidebar or text box is among the most commonly dropped content in ATS parsing. If your phone number, email, and LinkedIn URL live in a left-column sidebar, many parsers will skip them entirely. Put all contact details at the top of the main text column.
Other Layout Elements That Break Parsers
Headers and Footers
Most ATS platforms either ignore document headers and footers or handle them inconsistently — sometimes duplicating content, sometimes skipping it entirely. Never put your name, contact details, or job title in a Word header or footer. Keep everything in the main body.
Tables
Tables look like a clean way to align dates and job titles. In practice, many parsers merge table cells into a single run of text, destroying the relationships between fields. Use tab stops or consistent spacing to align content instead.
Text Boxes
Text boxes are treated as floating objects by most parsers. The extraction engine frequently skips them entirely — no error, no warning, just missing data. If you've placed a summary statement or key skills list in a text box, that content may never reach the keyword-scoring stage.
Graphics, Logos, and Icons
Headshots, company logos, and decorative icons are stripped silently during text extraction. The parser doesn't flag them as errors — it simply ignores them. Skill-rating graphics (five stars, horizontal bars) are especially problematic: they communicate proficiency visually, but that information is completely invisible to an ATS.
Horizontal Rule Lines
Simple horizontal lines used as section dividers are generally safe — if they're drawn as a paragraph border rule rather than inserted as a shape object. A border rule stays in the text layer; a shape object floats above it and can interfere with text extraction in the surrounding area.
Underlying principle: If it isn't flowing body text, verify that it survives parsing before you rely on it.
Formatting That's Safe AND Looks Professional
There's a persistent myth that an ATS-safe resume has to look like a 1998 fax. It doesn't.
Strong visual hierarchy comes from:
- A well-chosen font at the right size
- Consistent spacing between sections
- Bold section headers that stand out without requiring a design tool
- Clean, left-aligned text that's easy to scan
None of those require columns, text boxes, or custom fonts.
Before / After: The Skills Sidebar Problem
Before (two-column, sidebar skills): A left sidebar lists: Python | SQL | Agile | Stakeholder Management. The main column carries work experience. Looks clean in the editor. Parses as scrambled text.
After (single-column, inline skills section): A "Core Skills" section sits below the summary in the main column: Python, SQL, Agile, Stakeholder Management — listed in a simple bulleted or comma-separated format. Identical information. Fully parseable. Still readable.
Same content. Better outcome.
File Format Guidance
- .docx is the most reliable format across legacy ATS platforms. When in doubt, submit .docx.
- PDF is safe on modern ATS platforms — provided the text is embedded, not rendered as an image. Export from Word or Google Docs; don't scan a printed copy.
- Never submit a scanned PDF. A scanned document is an image. Parsers can't extract text from images without OCR, and many don't attempt it.
ATS Formatting Checklist
Before you submit, confirm:
- ✅ Safe font (Calibri, Arial, Georgia, Garamond, Cambria, or Times New Roman)
- ✅ Font size: 10–12pt body, 13–14pt section headers, 14–16pt name
- ✅ Margins: 0.5–1 inch on all sides
- ✅ Single-column layout, top-to-bottom flow
- ✅ No text boxes, no tables used for layout, no floating shapes
- ✅ No graphics, icons, or headshots in the text layer
- ✅ Contact info in the main body, not a header or sidebar
- ✅ File saved as .docx or a properly exported (non-scanned) PDF
Verify Your Formatting Actually Works Before You Apply
Visual inspection is not enough. A resume can look perfect on screen and still parse badly. The two failure modes described at the top of this article — garbled characters and scrambled structure — are invisible until you check the extracted text directly.
The DIY Plain-Text Check
Open your resume file, select all text, and paste it into a plain-text editor (Notepad on Windows, TextEdit in plain-text mode on Mac). Read it top to bottom. Ask:
- Is the reading order logical?
- Are any sections missing?
- Is any content fused together that shouldn't be?
If the answer to any of those questions is yes, an ATS is likely seeing the same problem.
How Scoring Makes the Problem Visible
A plain-text check tells you something is wrong. ATSEye's scoring engine tells you what it cost you. Upload your resume alongside a job description and the keyword gap report shows exactly which terms were detected and which weren't. If a keyword you know is on your resume is missing from the detected list, it may be buried in a text box, table, or sidebar that the parser dropped.
After fixing the formatting, re-scoring the same resume against the same job description shows whether the change actually moved the needle. You don't have to guess whether the fix worked — the score either improves or it doesn't.
What to do next: Open your current resume, run the plain-text paste test, and work through the checklist above. If you want to see exactly which keywords your resume is registering — and which are being lost — upload your resume and a target job description to ATSEye and review the gap report.
Written by
ATSEye Careers Team
Resume & job-search strategists
The ATSEye Careers team helps job seekers turn a scan score into interviews — combining ATS mechanics with the recruiter-relevance signals that get resumes shortlisted.