Correction, 17 October 2026. An earlier version of this article said two-column layouts fail in "roughly half" of ATS systems. That figure had no source, so we have removed it, and we have softened statements about how specific vendors and "most ATS engines" behave. The guide now rests on how text extraction works and on our own parser tests, which are linked below.
If you Google "ATS-friendly resume format" in 2026, you'll find advice that contradicts itself across articles. Some say PDF, some say Word. Some say one column, some say "modern" two-column. Some recommend specific templates, others say templates are the problem. This guide cuts through the noise, based on how text extraction works and what we've seen in our own parser.
The TL;DR (if you only read one section)
- File format: .docx (Word document), exported as text-based PDF only if the application explicitly requires PDF
- Layout: Single column, top to bottom, left-aligned
- Font: Arial, Calibri, Helvetica, Garamond, or Times New Roman, 10–12pt
- Length: 1 page if <10 years experience; 2 pages if more
- Sections in this order: Contact info → Summary → Experience → Education → Skills → Certifications (optional) → Languages (optional)
- No: tables, columns, headers/footers, text in images, fancy graphics, custom section names
That's it. Everything below is the why, the edge cases, and the things that look right but actually break parsing. (For the wider playbook that goes beyond formatting into keywords and verifying, see how to pass the ATS.)
1. File format: .docx wins almost every time
A .docx file stores its text in reading order, so it is usually the most predictable to parse. PDF parsing has improved a great deal, and most modern parsers handle simple text-based PDFs well, but complex PDFs can still be misread. In our own test of AI-written resumes, the same skills-table resume scored 84 to 85 in our scanner as the AI tool's own PDF export, with table cells glued together, and 99 to 100 as a Word file.
Rule of thumb:
- If the application form lets you choose: upload .docx
- If the form requires PDF: upload a text-based PDF (exported from Word with "Save as PDF," not "Print to PDF" and not scanned)
- Never upload an image-based PDF (scanned printout). Many parsers have no OCR, so they may see a blank candidate profile
How to check if your PDF is text-based: open it, try to highlight text with your cursor. If you can highlight individual words, it's text-based. If you can only highlight rectangular regions, it's image-based and a parser without OCR can't read it.
2. Layout: single column, full stop
Single-column layouts are read cleanly by most parsers. Two-column layouts are a gamble: some parsers handle them, others scramble them, and you can't tell which one an employer uses.
The reason: when a parser converts your document to plain text, it may read straight across the page, left to right, top to bottom. A two-column layout can then be read as: row 1 column 1, row 1 column 2, row 2 column 1, row 2 column 2, etc. Job titles end up next to skills. Dates land between bullets from completely different roles. The output is gibberish to the parser.
"Modern" resume templates often use sidebars or multi-column designs. They look beautiful in Word. They are a real risk in ATS systems. Use them at your own risk.
The other format trap is the functional (skills-based) resume, the one people reach for to disguise an employment gap. It dismantles the dated work history the parser needs and is even worse for your parse than a two-column layout. If that's why you're here, read how to handle an employment gap without breaking the ATS instead.
3. Sections and order
Parsers look for familiar section labels to know where to file specific data. Use the conventional names exactly:
| Section | Use this name | Don't use |
|---|---|---|
| Contact | Top of page (no header label needed) | "Reach Me" / "How to Find Me" |
| Summary | "Professional Summary" or "Summary" | "About Me" / "My Story" |
| Work history | "Professional Experience" or "Work Experience" | "Career Journey" / "What I've Been Up To" |
| Education | "Education" | "Academic Background" |
| Skills | "Skills" or "Core Competencies" | "Stuff I'm Good At" / "Toolkit" |
Standard section order: Contact → Summary → Experience → Education → Skills.
4. Contact information: out of headers, into the body
Some parsers treat the header/footer area of a Word document as page boilerplate and may skip it or file it oddly; others read it, sometimes more than once (see do ATS read headers and footers?). Either way, contact details in a header are less predictable than contact details in the body.
Put contact info in the document body, on the very first line, before everything else.
Format:
FULL NAME (16-18pt, bold) Job Title or Tagline (12pt, italic), optional but powerful for keywords City, Country • +Country-Code Phone • email@domain.com • linkedin.com/in/yourhandle
Don't use icons (📧 ✉ 📞), they may render as boxes or get stripped. Use plain text only.
5. Fonts: stick to the safe list
Fonts can quietly cause trouble. Templates love to suggest "modern" fonts like Avenir, Proxima Nova, or SF Pro. A parser reads the text layer, not the look, so most fonts are fine. The risk is a decorative font embedded in a PDF without a proper character map: then the extracted text can come out as boxes (□□□) or wrong letters. Common fonts avoid that risk.
Safe fonts (use these):
- Arial
- Calibri (default in Word, boring but bulletproof)
- Helvetica
- Garamond (best serif option)
- Times New Roman
- Cambria
- Verdana
Sizes: 10–12pt for body text. Name can be 16–20pt. Section headers can be 12–14pt.
6. Dates: standard formats only
Many systems use dates to compute your "years of experience", a filter recruiters often use. Non-standard date formats can break this.
Use:
January 2021 – PresentJan 2021 – May 202401/2021 – 05/20242021 – 2024(years only is acceptable for older roles; months are safer)
Don't use:
Jan'21, Present(apostrophe-year confuses parsers)1.2021 - 5.2024(period-as-separator is non-standard)2021-Now(use "Present" not "Now" or "Current")
7. Bullets and special characters
Use plain bullets: • or - or *. Avoid:
- Custom Wingdings symbols (✔ ► ◆ ★), which can extract as boxes
- Em-dashes for bullets (—)
- Right-arrow Unicode characters (→ ➤), which can get stripped or turn into stray characters
For dashes between sections, use the standard hyphen-minus (-) or en-dash (–). Em-dashes (—) can be converted to "?" in some plain-text extraction.
8. Length
- 0–10 years experience: 1 page
- 10+ years: 2 pages, but only if every line earns its place
- Academic / research / executive C-suite: 3 pages acceptable in specific industries
The ATS doesn't penalize length directly, but recruiters do. A 3-page resume from a 5-year-experience candidate signals poor editing.
9. What modern templates get wrong
Popular template marketplaces (Etsy, Canva, ResumeGenius) sell beautiful templates that can break ATS parsing. Common red flags in templates:
- Sidebars (multi-column layouts can be read out of order; our Canva-style sidebar test scored 80/100 in our scanner, with the sidebar read before the experience)
- Skills shown as filled circles or progress bars (graphics, not parsable)
- Photos / headshots (parsers ignore them, and most US/UK recruiters don't want them; some countries expect them, so check)
- Custom icons everywhere
- Section headers as colored boxes or images (the parser may not see the text)
- "Modern" fonts (Avenir, Montserrat, Poppins, they may render but inconsistently)
If you bought a beautiful template and it has any of those features: rebuild it as a single-column, plain-formatted document. Save the beautiful version for your portfolio website.
10. Test before you apply
Don't trust your eyes. Run the document through an ATS-style parser and look at what it extracts. Tools like ATS Verification show you side-by-side: your original document on the left, the parser's extraction on the right. If your work history is missing, your skills are scrambled, your name parsed wrong, fix the structure before sending out 50 applications. (Want to self-audit first? Run the 7-point ATS-friendly test.)
The first scan often reveals issues you'd never spot visually. Two-column problems show up as scrambled bullets. Header issues show up as missing contact info. Font problems show up as garbled characters. All fixable, but only if you see them first.
The simplest ATS-friendly template structure
FULL NAME Optional Tagline / Job Title City, Country • +Phone • email@domain.com • linkedin.com/in/yourhandle PROFESSIONAL SUMMARY 2-4 sentences. Lead with years of experience + main expertise + key keyword for the role. End with measurable outcome or unique angle. PROFESSIONAL EXPERIENCE Job Title, Company Name City, Country | Month Year – Month Year • Bullet 1: action verb + measurable outcome + keyword • Bullet 2: action verb + measurable outcome + keyword • Bullet 3: action verb + measurable outcome + keyword Job Title, Previous Company City, Country | Month Year – Month Year • Bullet 1 • Bullet 2 EDUCATION Degree, Institution City, Country | Year SKILLS Comma-separated list. Tools, technologies, methodologies, languages. Keep it scannable. CERTIFICATIONS (optional) Certification, Issuing Organization, Year
This structure works for most roles. Customize content. Don't customize structure.
If you are starting the document from scratch rather than fixing an existing one, the full process, from picking the target role to checking the parsed output, is in how to write a resume.
We ran one resume in six layouts through our own parser to check these rules; the results are in our 2026 ATS parsing benchmark.
For the full safe list of headings parsers recognize (and the creative ones that broke parsing in our test), see ATS resume section headings.
Two shortcuts if you would rather not format by hand: grab one of our free ATS-safe Word templates, or let the ATS resume builder rebuild your existing resume into this exact structure for $5.
→ Scan your current resume free and see what an ATS actually extracts. The fix-list usually surprises people.