Do tables and columns break ATS parsing?
Tables and multi-column layouts often break ATS parsing, causing your resume to be read out of order or ignored. Here is what to use instead.
Yes, tables and columns frequently break ATS parsing. Most applicant tracking systems read a resume as plain text from top to bottom, left to right, and layouts that split content into separate cells or columns confuse that process.
The result is scrambled text, missing keywords, or a blank parse. A recruiter may never see your skills or job titles in the right context, even if your resume looks polished in a PDF viewer.
Quick checklist
Pulled from the steps and lists in this guide — work through it as you read.
- Two-column layouts: skills or contact details in a left sidebar, work history on the right. The ATS reads columns in the wrong order or merges them…
- Tables used for skills grids: a 3x4 grid of skills looks clean visually but the ATS may read across rows and lose the relationship between skill na…
- Text boxes: content inside a Word or Google Docs text box is often invisible to parsers because it sits outside the main text layer of the file.
- Headers and footers: contact information placed in the document header is skipped by many parsers. Your name, email, and phone number may not be ca…
- Inline icons and graphics: a phone icon next to your number or a LinkedIn logo next to your URL is an image, not text. The parser reads nothing.
- Fancy fonts and Unicode symbols: bullet points made from decorative Unicode characters sometimes parse as question marks or are dropped entirely.
How ATS systems read your resume
Most ATS platforms, including Workday, Greenhouse, Lever, iCIMS, and Taleo, extract text from your file before storing it. They do not render the visual layout. They read the underlying text stream, which in a Word or PDF file follows the order the content was created, not the order it appears on screen.
A single-column document with standard headings produces a clean, predictable text stream. A two-column layout or a table breaks that stream. The ATS may read all the left-column content first, then all the right-column content, producing nonsense like 'Python Java SQL Managed a team of 12 engineers at Acme Corp 2021 to 2024 AWS Azure'.
Which specific layouts fail parsing
Not every visual element causes problems, but several common ones do. Knowing which ones to avoid is more useful than a general warning to 'keep it simple'.
- Two-column layouts: skills or contact details in a left sidebar, work history on the right. The ATS reads columns in the wrong order or merges them into a single garbled line.
- Tables used for skills grids: a 3x4 grid of skills looks clean visually but the ATS may read across rows and lose the relationship between skill names and any ratings or categories.
- Text boxes: content inside a Word or Google Docs text box is often invisible to parsers because it sits outside the main text layer of the file.
- Headers and footers: contact information placed in the document header is skipped by many parsers. Your name, email, and phone number may not be captured at all.
- Inline icons and graphics: a phone icon next to your number or a LinkedIn logo next to your URL is an image, not text. The parser reads nothing.
- Fancy fonts and Unicode symbols: bullet points made from decorative Unicode characters sometimes parse as question marks or are dropped entirely.
Watch it explained
We have not yet hand-verified an embedded video for this exact topic, so instead of embedding a loosely related one, here is a direct YouTube search for this guide's topic:
Watch: videos about “Do tables and columns break ATS parsing?” on YouTube →Search: “Do tables and columns break ATS parsing? tutorial explained” on youtube.com
What actually parses cleanly
The safest resume structure is a single-column document with standard section headings, plain bullet points, and no tables. This is not a creative limitation. It is the format that gets your content in front of a human reviewer reliably.
Use a Word .docx file or a plain PDF exported from Word or Google Docs. Avoid PDFs created from design tools like Canva, Adobe InDesign, or Figma. Those tools embed text as paths or objects that parsers cannot read.
- Contact block at the top of the main body, not in a header: name, city and state or country, phone, email, LinkedIn URL as plain text.
- Section headings as plain text, not inside shapes or text boxes: Work Experience, Education, Skills, Certifications.
- Job entries in a consistent format: company name, job title, dates, then bullet points describing your work.
- Skills listed as a simple comma-separated line or a short bulleted list, not a table or a bar-chart graphic.
- Standard fonts: Arial, Calibri, Georgia, or Times New Roman at 10 to 12 points.
The contact information problem
One of the most common parsing failures is contact information placed in a Word header. Designers put it there because it looks clean and stays fixed at the top of every page. But Workday, iCIMS, and several other major platforms skip the header section entirely when extracting text.
The fix is simple. Delete the header and paste your name, email, phone, and location into the first lines of the document body. Your resume will look almost identical to a reader but will parse correctly.
Country-specific notes for 2026
In the US and Canada, Workday and iCIMS handle the largest share of enterprise hiring. Both are known to struggle with multi-column PDFs and text boxes. Greenhouse and Lever, common at startups, handle clean single-column PDFs well but still drop content from text boxes.
In the UK, many large employers use SAP SuccessFactors or Oracle Recruit. Both parse Word .docx files more reliably than PDFs. If you are applying to UK roles, submitting a .docx is a safer default than a PDF.
In Australia, Seek's integrated ATS and PageUp are widely used. PageUp in particular has documented issues with tables and multi-column layouts. A plain single-column .docx or PDF works best across all four markets.
How to check your resume before applying
You do not need special software to check your resume. The plain-text paste test described in the aside above catches most problems. If your skills appear next to a job title from a different role, or if your dates appear at the end of a paragraph instead of next to the company name, you have a layout problem.
A second check is to upload your resume to a free ATS preview tool, several of which are available online, and compare the parsed output to your original. Look specifically at whether your contact details, job titles, and dates are captured correctly.
Break-In Bad's resume enhancement conversation reviews your resume line by line and flags content that may not survive parsing. Omar asks up to 20 questions to understand your background, then builds a clean, ATS-ready version that keeps your original facts intact. This is useful if you have been using a designed template and want to convert it to a format that applies reliably across Greenhouse, Lever, and Workday.
Sources & references
General references for this topic area (official and primary sources), checked in October 2026:
- Workday Administrator Guide — Concept: Resume Parsing — Parsing results vary by resume format and word order.
- O*NET Online (US Department of Labor) — Official skills and task language for occupations.
- US Bureau of Labor Statistics — Occupational Outlook Handbook — Official duties, outlook and pay by occupation.
Get a resume that parses on every platform
Break-In Bad's assistant Omar reviews your resume through a short conversation and builds a clean, ATS-ready version from your confirmed facts. No tables, no text boxes, no guesswork. Start with 50 free credits.
Start freeQuestions people also ask
Does a PDF always break ATS parsing?
No. A PDF exported from Word or Google Docs with a single-column layout usually parses well. PDFs created in design tools like Canva or InDesign are the ones that fail, because text is embedded as graphics or paths rather than readable characters.
Can I use any visual formatting at all?
Bold text, italic text, and standard bullet points are safe and parse correctly in most systems. What causes problems is structural formatting: tables, text boxes, multiple columns, and content placed in headers or footers.
Will a human recruiter ever see my formatted resume?
Sometimes. Many companies ask candidates to attach a resume that a recruiter views directly, separate from the parsed version the ATS stores. Keeping a visually clean single-column design means your resume looks professional to both the system and the person.
Comments
Loading comments…