The short answer
A two-column resume is not automatically unreadable by an applicant tracking system, but it fails in more ways than a single column does. Use one when the sidebar carries only short, self-contained items — and never for your work history.
What matters most
- A parser reads a page as one stream of text. Columns force it to guess the order.
- Short, self-contained sidebar items survive that guess. Job entries do not.
- Never split a single job's title, dates and bullets across two columns.
- Test by copying the text out of your own exported PDF and reading what comes back.
What actually goes wrong
When an applicant tracking system reads your resume, it does not see a layout. It extracts the text and reconstructs a reading order from position information. With a single column, that order is unambiguous — top to bottom, and there is only one possible answer. With two columns, the system has to decide whether a line at the top of the right column comes before or after a line halfway down the left one. Some systems handle it correctly. Some read straight across the page, interleaving the two columns line by line, which turns your sidebar and your experience section into alternating fragments.
The consequence is rarely outright rejection. It is subtler and worse: your job titles end up separated from their dates, your skills end up glued to the middle of a role description, and the structured fields the system tries to populate — employer, title, start date, end date — come back partly empty. A human reviewing that record sees an incomplete profile, and incomplete profiles get passed over without anyone concluding anything about you.
The difference between a good and a bad column split
Left sidebar: your entire work history, with job titles, dates and three bullets each, squeezed into a 5cm column. Right column: a long profile paragraph and a skills grid.
Left sidebar: contact details, a short skills list, certifications, languages — each item one or two lines and complete in itself. Right column: summary, then the full work history, uninterrupted, top to bottom.
What belongs in a sidebar
Judge each candidate section by one question: if this appeared in a random position in a plain text file, would it still be understood?
| Content | Safe in a sidebar? | Why |
|---|---|---|
| Contact details | Yes | Self-contained, and most parsers find email addresses and phone numbers by pattern rather than position. |
| Skills list | Yes | Short independent items. Keyword matching does not depend on where they sit. |
| Certifications and licences | Yes | Each is a complete fact on one line. |
| Languages | Yes | Same reason. Keep the proficiency description as words, not bars. |
| Education | Usually | Fine if each entry is one or two lines. Risky if you list modules, honours and coursework beneath each degree. |
| Professional summary | No | It is the argument of the document and belongs at the top of the main column where every reader meets it first. |
| Work experience | No | Multi-line entries whose parts must stay together. This is where column parsing does the most damage. |
| Volunteering with descriptions | No | Same structure as work experience, so the same problem. |
How the columns are built matters too
Two visually identical two-column resumes can parse completely differently depending on the underlying construction. This is invisible in the finished document, which is why it catches people out.
- A single borderless table with two cells is generally the most reliable construction in a word processor. Parsers handle tables reasonably well and the reading order is usually cell by cell.
- Genuine column formatting is next best and behaves predictably in most systems.
- Two floating text boxes side by side is the worst option. Text boxes sit outside the main text flow and are the element most often dropped entirely, which can silently delete your whole skills section.
- Nested tables — a table inside a table cell — compound the ambiguity and should be avoided in a document this short.
- A properly exported PDF from a purpose-built builder is usually safe, because the export can be constructed with a defined reading order rather than left to chance.
This is also why an old warning circulates that you must never use a table on a resume. It is too broad. One simple table used for layout, with no merged cells and no nesting, is fine in practice. Four nested tables holding your entire document is where the trouble starts.
Testing your own layout in five minutes
You do not have to guess. The test that matters is the one a parser performs, and you can run a rough version of it yourself.
- Step one
- Open your exported PDF, select all the text, and copy it.
- Step two
- Paste it into a completely blank plain-text document, so no formatting comes with it.
- Step three
- Read what you get. This is approximately what a parser sees, and any scrambling here is a real problem rather than a hypothetical one.
- What passes
- Sidebar items appear as a block, before or after the main column, each still intelligible. Job titles stay attached to their employers and dates.
- What fails
- Lines alternating between the two columns, dates orphaned from titles, or a section missing entirely — the last usually meaning a text box was dropped.
- Then check the matching
- Run the extracted text and the job posting through our free ATS checker to see which terms a system finds in what it can actually read.
Deciding whether to use one at all
The honest position is that a two-column layout is a modest visual gain in exchange for a modest additional risk, and the balance shifts depending on how you are applying. If you are uploading through a large employer's application portal, the parsing risk is real and a single column is the conservative choice. If you are emailing a small company directly, or handing the document to someone at an event, a human reads it first and the design advantage is worth having.
A reasonable compromise, and what many people end up doing, is keeping two versions: a single-column document for portal applications and a two-column one for direct approaches. Both are generated from the same content in our free resume builder, so switching layouts is a click rather than an evening of reformatting.
It is worth knowing the shape of our own gallery here, because it reflects this trade-off directly. Of the seventy-two layouts available, fifty-five are single-column and seventeen use two columns; forty of the seventy-two are marked ATS-safe, and the single-column layouts make up the large majority of that group. That ratio is deliberate rather than a limitation — the safe default is single column, and the two-column layouts exist for the situations where a person reads the page first.
- No work-experience entry is split across the two columns.
- Every sidebar item makes sense read on its own, out of order.
- The professional summary is at the top of the main column.
- The columns are built from one simple table or real column formatting, not floating text boxes.
- Copied and pasted text from the exported PDF still reads sensibly.
- A single-column version exists for large-employer portal applications.
Questions people actually ask
Can an ATS read a two-column resume?
Many can, and modern systems are considerably better at it than they were. The risk is not a flat refusal but a wrong reading order, which separates job titles from dates and leaves the structured fields incomplete. That incomplete record is what costs you, rather than any explicit rejection.
What should go in a resume sidebar?
Short, self-contained items: contact details, skills, certifications, licences and languages. Anything whose meaning depends on the lines around it, especially work experience, belongs in the main column where the reading order is unambiguous.
Are tables bad on a resume?
One simple table with no merged or nested cells, used to create a layout, is generally read without difficulty. The advice to avoid tables entirely comes from documents built out of several nested tables, which genuinely do confuse parsers.
Is a two-column resume better for fitting more on one page?
It does fit more, mainly because a narrow column of short items wastes far less horizontal space than a full-width list. Whether that is worth the parsing risk depends on how you are applying — directly to a person, probably yes; through a large employer portal, probably not.
How do I check whether my columns parse correctly?
Copy all the text out of your exported PDF and paste it into a blank plain-text file. What appears is close to what a parser extracts. If the two columns come back interleaved line by line, or a section has vanished, the layout needs changing before you send it.
