ATS Resume Format Guide

Last updated 2026-08-04

Most ATS formatting advice is repeated without testing, which is why it contains both real rules and pure superstition. This is the shorter, accurate version: the things that genuinely cause parsing failures, and the things you have been needlessly avoiding.

A two-column resume parses into interleaved, meaningless text. A single-column resume parses in the order it was written.TWO COLUMNSparses asSkills Java 2019 Led team…Dates land inside sentences. Nothing means anything.ONE COLUMNparses asLed team of 6…Exactly what you wrote.
A parser reads left to right, top to bottom. Two columns interleave into nonsense; one column survives intact.

What actually breaks parsing

  • Multiple columns. Text is extracted in stream order, so a two-column layout can interleave your job titles with your skills list. This is the single most damaging formatting choice.
  • Text inside tables. Some parsers read tables cell by cell in an order that has nothing to do with the visual layout.
  • Content in the header or footer region of the page. A meaningful number of parsers skip these entirely — which is catastrophic if your contact details live there.
  • Text inside images. A resume exported as an image extracts as nothing at all.
  • Text boxes and floating shapes, which frequently extract out of order or not at all.
  • Decorative glyphs and emoji, which extract as "?" or vanish, sometimes merging two bullets into one sentence.

What is safe, despite what you have read

  • Bold and italic text. Styling is stripped on extraction; the words survive intact.
  • Horizontal rules under section headings. They are drawing operations, not text.
  • Color, within reason. Keep text dark for print and contrast reasons, not parsing ones.
  • Two pages. There is no parser that truncates at one page. Length is a human attention question.
  • Hyperlinks. The visible text is what gets extracted, so write the readable URL rather than hiding it behind "click here".

Section headings are the hidden failure point

Parsers segment your resume by matching headings against an internal dictionary. "Work Experience" is recognized everywhere; "Where I've Made an Impact" is recognized nowhere, and everything beneath it may be discarded or filed under the wrong field.

Use the conventional headings: Professional Summary, Skills, Work Experience, Projects, Education, Certifications. Creativity in headings has no upside and a substantial downside.

Dates must be consistent

Parsers apply one date pattern per document. If most of your resume says "Mar 2022" and one role says "03/2022", that role can be read as having no dates at all — which means zero months of experience credited for it.

Pick one format and use it everywhere. "Mon YYYY" is the safest.

Frequently asked questions

Is a two-column resume really that bad?
For ATS submission, yes — it is the highest-risk common layout. For a resume you hand to someone directly or attach to an email, it is fine. Keep two versions if you like the design.
Should I use a resume template from Canva or Word?
Most of them use columns, text boxes or header regions, which is exactly what fails. If you use one, run the result through a plain-text check and confirm every line appears in the right order.
Do I need to avoid all graphics?
Avoid anything that carries information — icons replacing labels, charts showing skill levels, photos. Purely decorative lines are harmless.

Check this resume against the rules above

Nine free tools, running entirely in your browser. No sign-up, no upload, no watermark.

Open the builder

Related