ATS-Friendly Resume Format: The Complete 2026 Checklist

An ATS-friendly resume format is a layout a parser can read from top to bottom without guessing. That sounds basic, but it is where a large share of applications quietly break.

Your content can be excellent. If the software files your job title under education, or drops your phone number entirely, a recruiter searching that database will not find you. Nothing about your experience changed. The record of it did.

This guide covers the formatting decisions that actually affect parsing: layout, fonts, headings, dates, bullets, file types, and the design elements that look good in a template but cause problems inside a hiring system. There is a checklist at the end you can run before your next application.

What ATS-friendly actually means

When you upload a file, an applicant tracking system does not look at your resume the way you do. It extracts the raw text and tries to sort that text into fields: name, email, phone, company, job title, start date, end date, degree, skills.

Everything in this guide comes back to one question: can the parser tell which piece of text belongs in which field?

A clean, boring, single-column document answers that question easily. A two-column layout with icons and a skills bar chart does not.

Worth saying plainly: parsers in 2026 are better than they were five years ago. Most handle standard PDFs, most recognize common headings, and many understand that "managed" and "management" are related. The failures that remain are concentrated in a small set of specific choices, which is what makes them fixable.

Layout: one column, always

This is the single highest-impact formatting decision.

Parsers read the way you read a book: left to right, top to bottom. A two-column layout breaks that. When a parser hits a line that has your skills list on the left and a job description on the right, it often reads straight across and merges them.

The result looks something like this in the database:

Python Salesforce Excel Senior Analyst, Northwind Logistics, 2021 to present

Your skills and your job title are now one unreadable string. The recruiter searching for "Senior Analyst" may not match it.

Sidebars have the same problem. If your contact details, skills, or language proficiencies sit in a colored sidebar down the left edge, that content is at risk. Move it into the main flow of the document. I've pulled up a parsed profile that listed someone's phone number as a job title, because their sidebar and main column got read in the wrong order and the digits landed in the wrong field entirely.

What to do instead

• Write everything in a single column running down the page.
• Use white space and bold text to create visual separation, not columns.
• If you want your skills to feel compact, list them on one line separated by commas rather than in a grid.

Fonts and sizing

Font choice matters less than people assume, but it is not irrelevant. The risk is with custom or decorative fonts that are not embedded properly in the file. When that happens, the parser can extract characters that do not match what you see on screen.

Safe choices include Arial, Calibri, Helvetica, Georgia, Garamond, Times New Roman, and Verdana. Any of these will parse without issue.

For sizing, body text between 10 and 12 points and headings between 12 and 16 points keeps the document readable for the human on the other end. Going below 9 points to squeeze in more content usually signals that the content needs cutting, not shrinking.

One thing to avoid: font-based icons and symbol fonts. If you use a symbol font to render a phone icon next to your number, the parser may extract a meaningless character instead.

Section headings the system recognizes

Headings are how a parser knows where one section ends and the next begins. It matches them against a list of expected terms.

Standard headings that work reliably:

• Work Experience, Professional Experience, or Experience
• Education
• Skills or Technical Skills
• Certifications
• Summary or Professional Summary

Creative headings cause the parser to file that content nowhere in particular. "My Journey So Far," "What I Bring," and "Toolkit" all read as decoration to software. Your jobs might not register as jobs at all, which means your total years of experience can calculate as zero. I once had to guess whether a section literally titled "The Journey" was work experience or a personal essay, and I did not have time to find out. This is unfortunately the reality for most recruiters.

If you love a distinctive heading, the compromise is to keep the standard term and add character elsewhere, in your summary or your bullet points.

Dates and how experience gets calculated

Many systems calculate your total years of experience automatically by reading start and end dates. If a role requires five years and your dates cannot be parsed, you can be filtered out on a technicality.

Use a consistent format with both a month and a year:

• March 2021 to June 2024
• 03/2021 to 06/2024

Formats that cause problems:

• Year only (2021 to 2024) leaves the system unable to calculate months
• Seasons (Spring 2021) are not recognized as dates
• Durations alone (3 years) give the parser no anchor point

For a current role, "Present" and "Current" both work. Pick one and use it consistently.

Where your contact details go

Put your name, phone number, email address, city, and LinkedIn URL at the top of the page, inside the main body of the document.

The specific trap here is the document header. In Word, the header area is technically separate from the body text, and some parsers skip it entirely. People use headers to save vertical space, which is understandable, and then end up with a candidate profile that has no contact information attached to it.

The same applies to footers. Keep everything in the body.

Bullet points, symbols, and special characters

Standard round or square bullets parse fine. Where things go wrong is with decorative characters: arrows, stars, checkmarks, and emoji used as list markers. These sometimes extract as garbage characters that sit in the middle of your text.

A few related details:

• Use a standard hyphen rather than special dash characters where you can.
• Avoid rating systems built from symbols. Five filled circles next to "Excel" tells a parser nothing and tells a recruiter almost nothing.
• Keep bullets to one or two lines. This is a readability point rather than a parsing one, but it matters for the human review.

Graphics, tables, and text boxes

Three elements cause the most parsing damage, and they tend to appear together in downloadable design templates.

Tables

Text inside a table cell can be extracted out of order or skipped entirely, depending on the system. This matters because tables are a popular way to lay out a skills section. If your core competencies live in a three-column table, there is a real chance your profile shows no skills at all. I've seen a candidate list twelve tools in a neat three-column table, and the parsed profile in front of me showed exactly zero skills, because the whole table had been silently dropped.

Text boxes

A text box floats above the document rather than sitting in the text flow. Many parsers ignore that layer completely. Anything inside disappears.

Images, charts, and logos

Parsers extract text. They do not read pictures. A skills bar chart, a headshot, a company logo, and an infographic timeline all contribute nothing to your parsed profile. If a skill is only represented visually, it does not exist as far as the database is concerned.

Our guide on why an ATS rejects a CV goes deeper on how each of these breaks in practice.

PDF or Word: which file type to use

Both work in most modern systems. The distinction that actually matters is whether your PDF contains real, selectable text.

The image-based PDF is the one that catches people out. It usually comes from exporting a resume out of a design tool that flattens the page into a picture. Everything looks perfect and nothing is readable.

There is a five-second test: open your PDF and try to select a line of text with your cursor. If you can highlight and copy it, a parser can read it. If nothing highlights, your resume is an image.

Formatting choices that do not affect parsing

Some formatting advice circulates without much behind it. These choices are safe:

• Color. A colored heading or a subtle accent line does not break parsing. Keep text itself dark on a light background for readability.
• Bold and italics. Both parse fine and help human readers scan.
• Horizontal lines. Simple rules between sections are harmless.
• Margins. Anything from 0.5 to 1 inch is fine. Narrower margins do not cause parsing errors, though very tight ones hurt readability.

The pattern is consistent: elements that change how text looks are usually safe, and elements that change where text sits in the document structure are the risky ones.

How to test your formatting before you apply

You do not have to guess whether your file parses. There are two reliable checks.

The plain text test

1. Open your finished resume.
2. Select all the text and copy it.
3. Paste it into a plain text editor such as Notepad or TextEdit.
4. Read what comes out.

Is the order correct? Are dates still attached to the right jobs? Did anything vanish? Whatever you see here is close to what the system sees.

A dedicated checker

The plain text test catches structural problems but will not tell you how your content compares against a specific job. Running your file through the ResumeLime ATS Resume Checker shows what a parser extracts field by field and flags formatting issues alongside missing keywords. Our guide on how to check your ATS resume score walks through reading those results.

Formatting is only half the job

A perfectly formatted resume with the wrong vocabulary still will not surface in recruiter searches. Once the parsing is clean, the next step is making sure the terms recruiters search for actually appear in your text.

That means reading the posting closely and mirroring its language where it honestly describes your work. Our guide on how to find job description keywords covers the process, and the Resume Keyword Scanner compares your document against a specific posting to show which terms are missing.

Frequently asked questions

Do I need a different resume format for every ATS?

No. Workday, Greenhouse, Lever, iCIMS, and Taleo have different quirks, but a clean single-column document with standard headings parses well across all of them. Formatting for the lowest common denominator covers every system at once.

Should I include a photo?

In the United States, United Kingdom, Canada, and Ireland, leave it off. It adds no parseable information and some employers screen photos out to reduce bias. In parts of continental Europe and Asia a photo is more conventional, so follow local norms. Either way, it contributes nothing to your parsed profile.

Are the ATS resume templates I download online safe?

Some are, many are not. Templates are often designed to look impressive in a gallery, which means columns, sidebars, and icons. Judge the template against the rules above rather than the label attached to it.

Does the file name matter?

Not for parsing, but it matters for the human. Something like FirstName-LastName-Resume.pdf is easier for a recruiter to find later than Resume_final_v3.pdf.

The five-minute pre-flight checklist

Run this before you submit.

1. The document is one column with no sidebars.
2. There are no tables, text boxes, images, charts, or icons.
3. Contact details sit in the body of the page, not in the header or footer.
4. Section headings use standard terms.
5. Every role has a month and year for start and end dates, formatted consistently.
6. The font is a standard one at 10 to 12 points for body text.
7. Bullets are plain, not decorative symbols.
8. You can highlight and copy the text in the exported file.
9. The file is saved as a text-based PDF, or DOCX if requested.
10. The plain text version reads in the correct order with nothing missing.

Formatting will not get you hired. It only makes sure the work you have already done actually reaches the person deciding. That is a low bar, and it is worth clearing every time.