Search this exact question and you’ll get two confident, opposite answers within the first page of results.
Two-column resumes are fine, ATS has moved past that — or two-column resumes are the single biggest formatting risk you can take. Both come from real, disclosed tests, not vague opinion.
That’s not a contradiction to pick a side on. It’s a sign the real answer depends on something more specific than “how many columns” — and that specific thing is exactly what most advice on this skips.
What the largest disclosed test actually found
There is now one large, disclosed test of this question, and its answer is more specific than either side of the usual argument.
In 2026 Enhancv published a test of 357 extraction runs — three resumes of different lengths, rendered through 17 templates, each version pushed through seven different pieces of extraction software and scored against the exact data the PDF was built from.
On text, the result is a null: total word recovery never differed by more than half a percentage point between one column and two, and email, location, phone number and portfolio link came through correctly in all 357 runs.
Structure is the real story. Under the oldest extraction method — the one that reads strictly by position, left to right across both columns — a resume’s sections stayed intact only 35% of the time with two columns, against 60% with one. Under a newer extraction method the gap nearly vanishes, and once an AI model reads the extracted text it shrinks to about three points. One field does not fully recover: employer names fall from 100% to 83%, because interleaving separates a job title from the company it belongs to.
So a two-column resume is not unreadable. Its outcome just depends on which extraction method the employer’s system happens to use — and that is the one thing you cannot check before you apply. If your two-column layout is already built, that is not a reason to panic. If you are choosing now, single column removes the variance for free.
Enhancv’s write-up is explicit about this itself: what decides parsing success is reading order, not how many columns you use.
What actually decides it: reading order, not column count
A parser doesn’t understand “this is a sidebar” or “this is the main column” as concepts. It either follows an explicit reading order stored in the file, or — when that’s missing or ambiguous — it falls back to walking the page by position: left-to-right, top-to-bottom, one visual row at a time.
That fallback behavior is exactly where a two-column layout can go wrong. If your sidebar (skills, contact info) sits to the left of a work-history entry at the same vertical height, a parser reading positionally can interleave them — a line of your skills list, then a line of your job description, back and forth.
The content isn’t lost. It’s just reassembled in an order that makes your five years at one company look scrambled together with your certifications list.
That is precisely the failure mode the extraction testing exposes: not missing text, jumbled order.
A simple table-based two-column layout tends to avoid this because a table has genuinely structured cells with a clear, storable order — row 1 left cell, row 1 right cell, and so on.
A layout built from floating text boxes or a page-layout tool’s “columns” feature often has no such explicit structure. The visual position is all there is — exactly what a position-based fallback struggles with.
How your two-column resume was built matters more than how it looks
Two resumes can look identical on screen and behave completely differently once parsed, purely because of what’s underneath.
Built as an actual table, or from a template designed specifically for ATS parsing with a genuinely linear underlying structure — even though it displays as two visual columns.
Built with floating text boxes, a desktop-publishing “newsletter columns” feature, or copied from a general design template never tested against parsing.
You usually can’t tell which category your file falls into just by looking at it — the visual result can be nearly identical.
This is why “avoid two columns entirely” became the safe, blanket advice for years: it’s genuinely hard to know from the outside which construction method you’re looking at. It’s also more cautious than the evidence actually requires, if you’re willing to verify your specific file.
Content that shouldn’t go in a side column, regardless of construction
Even in a well-built two-column resume, some content is worth keeping in the main flow rather than the side — simply because the cost of it going wrong is higher.
Keep these out of a sidebar, even in a safe layout
- Job titles and employment dates — if these get reordered relative to the company name, your work history reads as incoherent even to a human glancing at the parsed text
- Any skill or certification you specifically need matched against a job posting — safer directly in the flow than isolated in a column a parser might treat inconsistently
- Your name and core contact details — these belong at the very top of the reading order, not to the side of it, regardless of layout
A sidebar is generally fine for supplementary content — a short skills list, languages, a link to a portfolio — where an ordering hiccup costs you little.
The content most worth protecting is whatever a recruiter’s keyword search or an ATS field-match depends on directly. That’s exactly what the formatting-risk category on our ATS resume checker is built to catch.
Test your own file — don’t inherit someone else’s verdict
Neither study above is describing your resume. The only way to know which category yours falls into is to check the specific file — the same way both tests did.
The fastest version of this yourself: copy all the text out of your resume and paste it into Notepad or a blank email, stripping every bit of formatting. Read what comes out, top to bottom.
If your sidebar content and main-column content stay separated and readable in order, your construction is likely fine.
If a line of your skills list appears mid-sentence inside a job description, or dates end up detached from the roles they belong to — that’s the exact interleaving failure the flagged test found. It’s fixable by rebuilding the layout as a proper table, not by abandoning two columns as a concept.
Here’s what that interleaving actually looks like once it happens:
Marketing Manager
Excel
ABC Agency | 2019–Present
Google Analytics
Led digital campaigns that boosted client traffic by 45%
SQL
Managed a five-person content team
Compare that to the same content rebuilt with a clear, linear structure:
Marketing Manager
ABC Agency | 2019–Present
Led digital campaigns that boosted client traffic by 45%
Managed a five-person content team
Skills: Excel, Google Analytics, SQL
Neither version lost any content — every word is present in both. Only the second one is usable by a person or a keyword search skimming it quickly. That’s the entire point of testing reading order, rather than just confirming your text technically “made it through.”
Skip the manual paste test
Our checker flags exactly this kind of formatting risk as part of your score.
This is one piece of a broader self-check worth running on any resume before you send it — see five ATS tests to run yourself for the rest.
If you’d rather not test it at all
Testing your specific file is the accurate answer, but it’s not the only reasonable one.
If you’d rather not spend the time verifying construction, a single-column layout removes the question entirely — there’s no sidebar to interleave, so this specific failure mode simply can’t happen.
Our own ATS-friendly resume templates are built single-column for exactly this reason: not because two columns can’t work, but because it’s the one choice that needs no verification at all.
A well-built two-column resume can look more polished and organize supplementary information more efficiently. What’s not reasonable is assuming your specific file is safe (or unsafe) just because you read a headline that said so.
For the rest of the formatting rules beyond columns — fonts, file type, section headers — the full ATS resume tips guide covers those.
Ready to write your resume?
Build a job-ready resume in minutes with our AI-powered builder.
Create Resume
FAQ
Are two-column resumes ATS-friendly or not?
It depends on how the specific file was built, not on the column count itself. A table-based two-column layout with clearly structured cells can parse as well as a single-column resume. A layout built from floating text boxes is much more likely to read out of order.
What actually goes wrong when a two-column resume fails ATS parsing?
Almost always the same thing: reading order, not missing content. A parser falling back to a position-based reading order can interleave your sidebar with your main column line by line. The text is usually all still there — just reassembled in a jumbled sequence.
How can I tell if my two-column resume is safely built?
Paste the full text into Notepad, stripping all formatting, and read the result top to bottom. If your sidebar and main content stay in coherent, separate blocks, the structure is likely sound. If lines interleave mid-sentence, the file needs to be rebuilt as a genuine table.
Is a two-column resume automatically worse than single-column?
Not usually — but the risk isn’t what most advice says it is. Enhancv’s 2026 test of 357 extraction runs found two-column resumes lose essentially no text: word recovery stayed within half a percentage point of single-column across every tool. What can break is reading order. Under older position-based extraction, section integrity dropped to 35% for two-column against 60% for single-column; newer extraction and AI-based parsing close most of that gap. Because you can’t tell which one an employer runs, single-column is the lower-risk default.
Should I just avoid two-column resumes to be safe?
It’s a reasonable, zero-effort way to remove the risk entirely — no sidebar to interleave if there’s no sidebar. It’s not the only valid answer, though; a properly built two-column resume, verified with a quick paste test, can be just as safe.
