ATS-friendly CV format in 2026: what actually works

If you've been job hunting in the last twelve months, you've probably read at least a dozen articles telling you that applicant tracking systems (ATS) reject any CV with an icon, a sidebar, or a custom font. Most of that advice is recycled from 2014 and is partially wrong.

The truth in 2026 is more nuanced. Modern ATS platforms — Greenhouse, Lever, Workday, Ashby, Recruitee — use mature PDF parsing libraries that handle far more than the legacy systems people are still writing about. But there's a small set of formatting choices that genuinely break parsing in every system, and those are the ones worth caring about.

This post separates the urban legends from what actually matters.

What an ATS actually does

Before deciding what to format, it's worth understanding what an ATS is doing with your CV. Most modern systems do three things:

1. Extract structured fields (name, email, phone, work history, education) using a parser like Sovren, RChilli, or an in-house equivalent.
2. Index the full text so recruiters can search ("Python AND fintech AND 5 years").
3. Score the candidate against a job description — if the company has bothered to set scoring up, which most haven't.

The first two are where formatting matters. If the parser can't find your job titles or dates, you might end up with an empty profile that the recruiter has to fix manually — and most won't bother.

What actually breaks parsing

These are the things that consistently cause ATS parsers to misread or miss content:

1. Multi-column layouts where the columns aren't logically separated

A two-column CV with a sidebar for skills and a main column for experience is the single most common parsing failure. The parser reads the page top-to-bottom and ends up interleaving "Python" with your job description at Google.

Some modern parsers handle this; many don't. The risk isn't worth the visual upside.

Fix: use a single-column layout. If you want a "skills" sidebar visually, put it at the top of the page horizontally instead.

2. Text inside images

If your name and headline are part of a banner image, the ATS won't see them. Same goes for skill icons that are images.

Fix: all text should be selectable text, not raster.

3. Headers and footers used for content

Most ATS parsers ignore the page header and footer entirely. If your phone number lives in the footer, it disappears.

Fix: put contact info in the body of the document, near the top.

4. Tables for layout

Some parsers handle tables fine, but many parsers will read a table cell-by-cell, top-to-bottom, left-to-right — which scrambles the meaning.

Fix: use simple paragraph-based layouts. If you must use tables for actual tabular data (e.g. a publication list), keep them simple.

5. Non-standard section headings

Parsers look for keywords like "Experience", "Education", "Skills". If your headings say "Where I've Hung My Hat" and "Things I'm Decent At", the parser won't recognise the section boundaries.

Fix: boring, conventional headings: Summary, Experience, Education, Skills, Projects, Certifications.

6. Smart quotes, em-dashes, and zero-width characters

Pasting bullets from Word or Google Docs often introduces special characters (curly quotes, en-dashes, non-breaking spaces) that parsers can mishandle. The text looks fine to you but breaks search.

Fix: export from a tool that normalises these to plain ASCII, or do a find-and-replace yourself. (CVCL does this automatically.)

What does NOT break parsing (despite what blogs say)

Several pieces of "ATS advice" you'll see on Reddit and LinkedIn are no longer true:

"Use Times New Roman or Arial only"

False. Any common font that ships with a system PDF reader is parsed fine. Space Grotesk, Inter, DM Sans, IBM Plex — all parse correctly. The font choice is purely a visual decision.

"Don't use any colour"

False. Colour doesn't affect parsing at all because the parser sees the text layer, not the rendered visual. You can use teal, navy, dark grey — whatever reads well on paper.

"PDFs get rejected — only use .docx"

Mostly false. Every major ATS has supported PDF parsing well for at least five years. The only exception is some older custom ATS at large enterprises (think 20-year-old internal HR systems). Submit PDF unless the application form specifically asks for .docx.

"ATS rejects you for low keyword match"

Misleading. Most ATS platforms don't actually auto-reject candidates based on a keyword score. They surface a score to the recruiter, who then makes the call. So keyword optimisation matters because the recruiter sorts by it, not because the machine fires you on its own.

"You need exactly one page"

False — and outdated. One page is appropriate for early-career roles (under 5 years' experience). Beyond that, two pages is the norm, and recruiters expect it. ATS systems don't care about page count.

What ACTUALLY moves the needle

If you only do five things:

1. Single column. Standard headings. PDF format.
2. Match the JD's vocabulary in your bullets. If they say "stakeholders", don't say "clients". The recruiter is searching for their words.
3. Quantify outcomes wherever you honestly can. "Reduced infrastructure cost by 30%" beats "Worked on cost optimisation" every time.
4. Lead each bullet with a verb. "Designed", "Shipped", "Migrated", "Owned". Not "Was responsible for".
5. Tailor per role. Same CV for every job is the most common mistake. It signals low effort to the recruiter and produces lower keyword matches in their search.

How CVCL helps

This is the part where the post says "and that's why our product is great", and you're free to ignore it — but it's relevant context.

CVCL was built specifically because tailoring a CV per role is tedious and most people skip it. We:

• Render to a single-column, standard-headings ATS template
• Use Space Grotesk + DM Sans (parses fine — see above)
• Strip smart quotes, em-dashes, and zero-width characters automatically
• Use the JD's vocabulary in your bullets (without inventing new experience)
• Output both PDF and editable DOCX every time

3 free generations on signup. No card needed. If you're applying to more than one job a week, this saves you hours.

TL;DR

Most ATS-formatting advice on the internet is a decade old and either wrong or doesn't matter. The things that actually matter:

• Single column, standard section headings, PDF format
• Selectable text only (no images of text)
• Don't put content in headers/footers
• Match the JD's vocabulary in your bullets
• Tailor per role

Everything else — fonts, colour, exact page count, file format wars — is mostly noise.