Do two-column resumes break applicant tracking systems?

Some of them, yes. Columns are the single most common cause of scrambled parses, because a parser reading left-to-right can interleave two columns into nonsense. A single-column layout removes the risk entirely and costs you nothing a recruiter values.

Can an ATS read text in headers and footers?

Often not. Several parsers skip the header and footer regions of a document, which is exactly where people put their phone number and email. Keep contact details in the body of the first page, where every parser looks.

Are resume templates from Canva or Word safe?

It depends entirely on the layout, not the tool. Templates built on text boxes, tables, icons and sidebars parse badly regardless of where they came from. A plain single-column template from any source parses cleanly. Run yours through a parse check rather than trusting the source.

The ATS-friendly resume format, tested against nine parsers

Our scoring engine runs every resume through a nine-vendor parser simulation — the same extraction behaviors used by the major applicant tracking systems. This post is the format guidance that falls out of that testing. (For why parsers behave this way, read how an ATS actually reads your resume.)

What you designed

Columns interleaved

What the parser reads

A two-column layout looks organized to you — the extractor reads across both columns and interleaves them.

The layout rules that actually matter

One column. Multi-column layouts are the top parse killer: extractors read across columns and interleave your sidebar skills into your job history — exactly what the figure above shows.
Standard section headings. Experience, Education, Skills, Summary. Parsers segment your resume by recognizing these. Where I've Made an Impact is a heading only a human can love.
Contact info as plain text, in the body. Not in an image, not in an icon font, and not in the document header — several parsers skip DOCX headers/footers entirely, which silently deletes your phone number.
Bullets, not tables. Table cells get read in unpredictable order. A simple - or • bullet survives everything.
Consistent date format. Jan 2023 – Present on every role. Parsers compute your years of experience from these; one Winter '23 can break the chain.

Section by section

Contact block

Name on its own line, then phone, email, city/state, and one link — all as plain text in the body of page one. Skip the street address; nobody needs it and it dates the document. If you include LinkedIn, write the visible URL rather than hiding it behind the word "LinkedIn", because some parsers keep the text and drop the hyperlink.

Summary

Three lines, optional but usually worth it — it's the one place you can put the posting's top requirements in the first thing anyone reads. Write it as substance, not as a personal-brand statement. "Objective" sections asking for "a challenging role where I can grow" are a waste of the most valuable real estate on the page.

Experience

The format parsers read most reliably, every time:

Job Title · Company · City, State
Jan 2021 – Mar 2024
- Bullet starting with a strong verb, ending with an outcome

Keep title, company and dates on predictable lines. Don't split a single role across a page break if you can avoid it, and never rely on a graphical timeline to communicate dates — it parses as nothing.

Skills

A simple comma-separated or short bulleted list under a heading called Skills. No proficiency bars, no star ratings, no five-point scales: they convey nothing to a parser, they're unverifiable to a human, and the graphics routinely break extraction. Group by category if the list is long.

Education

Degree, institution, graduation year. Drop your GPA once you have a few years of experience, and drop your high school as soon as you have anything after it. Certifications can live here or in their own section — write both the full name and the acronym once, as in Project Management Professional (PMP).

Everything else

Projects, publications, volunteering and languages are all fine as clearly titled sections. "Interests" is usually filler. "References available on request" is always filler — it's assumed.

Heading names parsers recognize

Use	Not
Summary / Professional Summary	About Me, My Story
Experience / Work Experience / Professional Experience	Where I've Made an Impact, My Journey
Skills / Technical Skills	Superpowers, My Toolkit
Education	Learning, Academic Adventures
Projects	Things I've Built
Certifications	Credentials & Accolades

The left column isn't more creative-hostile than the right; it's the vocabulary the field-extraction step was trained to recognize. Spend the creativity on the bullets underneath.

The font and file rules

Survives all nine parsers

One standard font — Arial, Calibri, Georgia
PDF exported from Word, Google Docs, or LaTeX
Plain-text bullets and headings
Phone and email typed in the body

Fails at least one

Icon or glyph fonts (render as unicode garbage)
Canva / Figma exports (text becomes outlines or images)
Photos, charts, skill-level progress bars
Contact details inside a header, footer, or logo

Practical settings that keep a resume readable to both audiences: 10–12pt body text, 0.5–1 inch margins, standard • or - bullets, and no more than two font sizes plus bold. Decorative dingbat bullets are a common source of the unicode garbage in that right-hand column.

If in doubt about the file itself, see the full breakdown in PDF vs DOCX.

Should you include a photo?

In the US, UK, Canada and Australia: no. Many employers discard resumes with photos to reduce bias-claim exposure, and the image is dead weight to a parser either way. In much of continental Europe, parts of Asia, and Latin America a photo is conventional and its absence looks odd. Follow local convention, and when you're applying across regions, keep a separate version rather than compromising.

Are Canva and Word templates safe?

It depends entirely on the layout, not the tool. A single-column Canva template exported with a real text layer parses fine. A Word template built on text boxes and a two-column sidebar fails, despite coming from Microsoft. Judge the template by three questions: is it one column, are the headings standard, and is the contact block in the body? If yes to all three, it's safe regardless of origin.

What an ATS template will not do for you

Get the format to pass, then spend your time on keywords and evidence — that's where the real weights are.

The 60-second self-test

Copy your entire resume and paste it into a plain-text editor. What you see is roughly what a parser sees. If the reading order is scrambled, your phone number vanished, or your skills merged into a paragraph of soup — the format is costing you screens.

Or skip the manual check: the free MeritSlate ATS checker runs the nine-vendor simulation on your actual file and flags every extraction failure it finds, line by line.

Frequently asked questions

Do two-column resumes break applicant tracking systems?: Some of them, yes. Columns are the single most common cause of scrambled parses, because a parser reading left-to-right can interleave two columns into nonsense. A single-column layout removes the risk entirely and costs you nothing a recruiter values.
Can an ATS read text in headers and footers?: Often not. Several parsers skip the header and footer regions of a document, which is exactly where people put their phone number and email. Keep contact details in the body of the first page, where every parser looks.
Are resume templates from Canva or Word safe?: It depends entirely on the layout, not the tool. Templates built on text boxes, tables, icons and sidebars parse badly regardless of where they came from. A plain single-column template from any source parses cleanly. Run yours through a parse check rather than trusting the source.

Written by

MeritSlate Team

The team building MeritSlate's deterministic scoring engine — nine evidence-anchored axes, a nine-vendor ATS parse simulation, and every point backed by receipts.