ATS Resume Format: What Actually Gets Parsed in 2026

Search for ATS advice and you'll meet the same sentence over and over: three-quarters of resumes are rejected by robots before a human ever sees them. It's repeated by resume builders, career coaches, and — increasingly — by AI assistants that learned it from those pages. It is also unsourced. Nobody who cites it can point to the study.

This matters, because the myth produces bad behaviour. People strip their resumes of all personality, stuff them with keywords, and optimise for an adversary that isn't there. The truth is duller and far more actionable: an applicant tracking system is a database with a search box, and your only job is to make sure it can read you correctly.

What does an ATS actually do with your resume?

When you hit Apply, the system runs your file through a parser. The parser's job is to turn an unstructured document into structured fields — name, email, employer, job title, start date, end date, skills, education — and write them into a row in a database.

A recruiter then searches that database. They type senior react engineer into a box, apply a filter or two, and get a ranked list. That's it. There is no hidden score. There is no algorithm deciding your worth. There is a human running a query, and the question that decides your fate is simply: did your record come back in the results?

Which formatting choices actually break the parser?

After looking at how mainstream parsers handle real files, the genuine failure modes cluster into four categories. Everything else is folklore.

The PDF question, settled

PDF versus Word is the most over-litigated question in resume writing. Both are fine with every mainstream ATS. What is not fine is a PDF whose text isn't text — a file exported from a design tool with the type converted to outlines, or a resume that's really a screenshot in a PDF wrapper.

There's a five-second test. Open your PDF, try to select a line of text with your cursor, and copy-paste it somewhere. If you get characters, every parser on earth will too. If you get nothing, you have an image, and you are invisible.

What layout survives every parser?

There is a boring, unglamorous structure that has never failed a parse, and it looks like this:

1. 1Contact block in the body, not the header. Name, email, phone, city, one link.
2. 2A single column, top to bottom. Sidebars are the single most common cause of scrambled output.
3. 3Standard headings, spelled the standard way: Summary, Experience, Education, Skills, Projects, Certifications.
4. 4Reverse-chronological roles, each with a job title on its own line, then employer, then dates in a consistent Mon YYYY – Mon YYYY format.
5. 5A flat skills list — comma-separated or bulleted. Not a grid of five-star rating icons, which parse as nothing.
6. 6Real text, exported to PDF, with selectable characters.

The best-formatted resume is the one you never have to think about again — because the structure is invisible and the content is doing all the work.

So what should you optimise instead?

Once your resume parses cleanly, formatting stops being a lever. You have hit the ceiling of what layout can do for you, and every further hour spent nudging margins is an hour not spent on the thing that actually decides interviews: whether the content matches the role.

That means the vocabulary of the job description appearing in your resume because you genuinely have the experience — not because you pasted a keyword list at the bottom. It means bullets that state an outcome rather than a duty. It means the top third of page one making it obvious, in about six seconds, what you do and how well you do it.