Two-column resume templates are everywhere — Canva, Notion, every "modern resume" site you can find. Most of them parse correctly through modern ATS systems. Some predictably don't, and the difference matters because a resume that doesn't parse essentially doesn't exist.

This post is about which multi-column layouts work, which don't, and the simple test that tells you where yours lands before you submit.

When multi-column parses and when it breaks

The decision runs on two axes: how complex the column structure is, and how heavy the visual elements are.

Simple columns + light visuals. A narrow sidebar (1/3 width) for contact info, skills, and certifications, with a main column for experience and education. Plain text. This parses cleanly in almost every modern ATS. Use it for design-aware roles where layout matters and the candidate has the design skills to back the choice.

Simple columns + heavy visuals. Same column structure, but with icons, graphic skill bars, or visually styled section headers. The risk increases — parsers often skip the visual elements entirely, which is usually fine, but occasionally they get confused about reading order. Test before submitting.

Complex columns + light visuals. Three columns, sidebars on both sides, or non-standard reading flow. Risk: some parsers concatenate text left-to-right across columns, which mangles the content. Test with at least two parsers before relying on the layout.

Complex columns + heavy visuals. The high-risk zone. Magazine-style layouts, columns with non-rectangular shapes, embedded graphics. Many parsers fail to reconstruct the content reliably. Default to single-column for ATS-heavy applications, and reserve the designed version for direct outreach or portfolio submission.

For the broader ATS-friendly format question, see ats-friendly-resume-format-myths and how-applicant-tracking-systems-work.

What the parse rates actually look like

In informal parsing benchmarks across major ATS systems:

• Single-column plain text parses correctly about 98% of the time. This is the industry baseline — essentially every parser handles it.
• Two-column with simple sidebar parses correctly about 87% of the time. Modern parsers (Workday, Greenhouse, Lever) handle simple two-column layouts cleanly. Older systems still in use at some companies can stumble.
• Two-column with icons and graphics drops to about 68%. The visual elements often get skipped, which is fine, but the column order can occasionally confuse parsers.
• Complex 3-column or magazine layouts parse correctly about 41% of the time. This is the territory where the failure modes start outweighing the design benefits.
• Heavy infographic or portfolio-style PDFs parse correctly about 23% of the time. Most parsers can't reconstruct the content; these resumes essentially require human-only review channels.

The exact percentages vary by which parsers you test against, but the rank ordering is consistent. Each step up in visual complexity costs parse reliability.

Working layouts vs. layouts that break

A working two-column layout has specific properties:

• Narrow sidebar (1/3 width) with contact, skills, certifications. Wider sidebars sometimes get reordered with the main column.
• Main column with experience and education in standard order. Don't move the experience section to the sidebar.
• Plain text throughout. No skill-bar graphics, no progress bars, no rated stars.
• Consistent fonts and spacing. Visual unpredictability sometimes triggers parser quirks.
• Section headers as plain text, not as images or icon fonts.

Layouts that break share opposing patterns: three or more columns with ambiguous reading order, visual skill bars rendered as graphics, headers built from icon fonts, embedded photos, text wrapping around non-rectangular shapes.

The pattern: the more the layout depends on the visual to convey meaning, the worse it parses.

The simple test that tells you what you have

The most useful five-minute test:

1. Save your resume as a PDF.
2. Open it in any free PDF reader and select all the text.
3. Paste it into a plain-text editor.
4. Read what you got.

If the text appears in correct reading order, with all the content present, your resume will parse correctly in most ATS systems. If the text is jumbled, has columns interleaved, drops sections, or shows up as gibberish — those are the same problems an ATS parser will have.

This isn't a perfect simulation of every ATS, but it catches 80% of parsing problems. It's free, takes five minutes, and there's no excuse not to do it before sending a designed resume into a parser-heavy pipeline.

A second test: many free ATS parsing tools (JobScan, Resume Worded, Enhancv's free checker) accept a PDF upload and show you the parsed text. Spot-check with two of them before trusting your layout.

The "keep two versions" strategy

A practical solution for designers and design-adjacent candidates: maintain two versions of your resume.

• The ATS version. Single-column or simple two-column, plain text, conservative layout. This goes into application forms and online submissions.
• The portfolio version. Designed, multi-column, visually rich. This goes to direct outreach, hand-delivered applications, portfolio sites, or shared by referral after an introduction.

Both versions carry the same content. The choice of which to send depends on the channel.

This isn't deceptive — it's pragmatic. The portfolio version represents your design ability; the ATS version represents your career. They serve different audiences.

When the role is design-itself

For roles where layout is the job — graphic designer, product designer, UX, brand — the designed resume signals capability directly, and the ATS-version-only strategy underprices what you're being hired for. In these cases:

• Submit both if the application allows it (some let you attach multiple PDFs).
• If only one, submit the designed version, but make sure the visual layout still has a logical reading order that parses acceptably.
• If the role goes through a heavy-ATS pipeline anyway, the ATS version is the right submission; the designed version goes in the cover-letter portfolio link.

For the broader portfolio-versus-PDF question for designers, see design-resume-portfolio-vs-pdf.

What this isn't

A few clarifications:

• It's not a blanket ban on two-column resumes. Simple two-column layouts work in most modern ATS systems. The warning is about complexity, not columns as such.
• It's not a recommendation to use plain Times-New-Roman everywhere. Conservative doesn't have to mean ugly.
• It's not the only parsing-risk surface on your resume. Date formats, section names, and headers all matter — see related posts on each.

The short version: simple two-column layouts parse fine. Complex multi-column or heavy-graphic layouts often don't. The free five-minute test (PDF → copy-paste into text editor) catches most problems before submission. Maintain an ATS-friendly version even if you also have a designed one.