Can an ATS Read Tables and Columns? (2026)

Resume templates with side bars, two-column layouts, skill-rating tables, and decorative text boxes look professional on screen. The problem is that a significant number of ATS parsers cannot read them correctly — and when parsing fails, your skills, job titles, and contact details may never reach the recruiter's record at all.

This is not a theoretical concern. A 2021 Harvard Business School study found that 88% of employers admit ATS systems screen out qualified candidates — and formatting failures are one of the most common reasons a strong candidate's content simply does not appear in a search result.

Why Multi-Column Layouts Break Parsers

ATS parsers extract text from documents by reading content in a linear order — typically left to right, top to bottom. A single-column resume matches that reading order perfectly. A two-column resume does not.

When a parser encounters two side-by-side columns, it often reads across the full page width rather than down each column independently. The result is interleaved content: your job title from the left column gets merged with your skills from the right column on the same line. Dates appear next to unrelated headings. Job descriptions from one column spill into the middle of a skills list.

The parsed record that the recruiter searches is not your resume — it is a scrambled version of it. A keyword you know is there may not be findable because it appears in a garbled context the search engine cannot match.

Tables: Sometimes Readable, Often Not

Tables in Word (.docx) files are sometimes parsed correctly, but the extraction order depends entirely on how the parser handles the underlying XML. Some parsers read cells left to right across each row; others read column by column. Neither reliably matches how a human reads a skills table.

Tables in PDFs are more problematic. A PDF does not preserve the concept of a table — it stores text as positioned characters on a page. A parser extracting text from a PDF table must infer the structure from character positions, and this inference fails frequently, especially when cell borders are used for visual alignment rather than strict grid formatting.

Text Boxes: Almost Always Skipped

Text boxes — the floating text containers used in Word, Google Docs, and many resume templates — are treated as objects, not body text, by most document parsers. Their content is frequently skipped entirely.

The most common casualty is the contact block. Many visual templates place name, phone, email, and LinkedIn URL inside a header text box for clean alignment. The recruiter sees it on the PDF. The ATS record contains none of it.

Icons, Images, and Graphical Skill Ratings

Images are not text. A five-dot skill-level indicator next to "SQL" contributes zero keyword signal — the parser may extract "SQL" if the word is rendered as text, but the rating graphic adds nothing. An icon used instead of a bullet point leaves the following text without a prefix, which can affect parsing logic in some systems.

Replace graphical ratings with plain text. Replace icon bullets with standard round bullets or no bullets at all. The content is what matters; the visual decoration is invisible to the system.

What to Use Instead

The safest resume layout for ATS compatibility is a single column with standard section headings, plain text throughout, and no floating elements. Specifically:

• Single-column layout — all content flows top to bottom in one column. No side bars, no split sections.
• Standard section headings — use recognizable labels: Work Experience, Education, Skills, Certifications. Avoid creative substitutes like "Where I've Been" or "My Toolkit."
• Plain text for skills — replace skills tables with a comma-separated list under a Skills heading. Every word is then unambiguously parsed as text.
• Contact info in the body — put your name, phone, email, and LinkedIn URL in the main text flow at the top of the document, not inside a header, footer, or text box.
• Standard fonts — Arial, Calibri, Georgia, or Times New Roman all parse reliably. Decorative or hand-lettered fonts can cause character-recognition errors in some systems.
• No graphics or icons — remove company logos, skill bars, rating dots, and decorative dividers. They are invisible to parsers and add file weight without value.

Frequently Asked Questions

Can ATS systems read two-column resume layouts?

Many cannot reliably. When a parser encounters a two-column layout, it often reads left and right columns line by line across the page rather than top to bottom within each column. This interleaves your job titles with your skills section or scrambles dates with unrelated text. Some modern parsers handle columns better, but you cannot know which system a given employer uses, so a single-column layout is the only safe choice.

Do ATS parsers read text inside tables?

It depends on the parser and the file format. In Word (.docx) files, table content is often readable but may be extracted in the wrong order. In PDFs, text inside table cells can be extracted out of sequence or skipped entirely depending on how the PDF was generated. The safest approach is to present any information currently in a table as plain, line-separated text instead.

Can ATS systems read text boxes in Word or Google Docs?

No. Text boxes in Word and Google Docs are treated as floating objects by most parsers, not as body text. Content inside text boxes is frequently skipped entirely. This is a common reason contact information, placed in a header text box for visual alignment, goes missing in the parsed record.

What about icons and graphics used to show skill levels?

Icons and bar-chart-style skill ratings are images, not text. An ATS parser extracts no information from them. A row of five filled dots next to "Python" tells the system nothing — only the word "Python" as plain text matters. Replace graphical skill ratings with a plain comma-separated skills list.

Does it matter whether I use PDF or Word for ATS submission?

Both formats can cause parsing problems if the underlying layout uses tables, columns, or text boxes. A cleanly formatted single-column PDF generally parses well. A multi-column Word file can parse poorly even though Word is the "native" format for many parsers. Format matters less than layout. When in doubt, a simple single-column PDF is the safer choice.

Related reading: ATS-friendly resume format · the ATS resume checklist · why resumes get rejected by ATS