ATS-Friendly CV Format: The Rules That Actually Matter in 2026

If you've spent an evening googling CV formatting, you've probably collected forty rules that contradict each other. Never use PDF. Always use PDF. One page or the bin. Times New Roman or the robots reject you. Most of it is folklore: advice recycled from American resume blogs, decade-old software, or thin air.

Here's the honest version. An ATS-friendly CV format comes down to a single question: can parsing software read your CV top to bottom and turn it into accurate, structured data? Once you understand what the parser is actually doing (our plain-English explainer What Is an ATS and How Does It Actually Read Your CV? walks through it), the rules sort themselves into two piles: a short list that genuinely affects parsing, and a tall pile you can ignore. This guide separates them, then gives you a copyable format spec for UK graduate CVs.

Why format matters: what a parser actually does

When you upload your CV, the system doesn't "look" at it the way a person does. It extracts the raw text, then tries to segment it: this block is contact details, this heading starts work history, each entry underneath is an employer plus a job title plus a date range, this list is skills. The result is a structured profile that recruiters search, filter and skim.

Every formatting rule worth following exists to protect that extraction. A gorgeous two-column CV that parses into scrambled data makes you effectively unsearchable: your job titles land in the wrong field, your dates attach to the wrong employer, and the recruiter filtering for "graduates available from September" never sees you. Note what's not happening: most systems don't auto-reject on formatting. A human still reads the record. But if the record is gibberish, the human reads gibberish, and gibberish rarely gets an interview.

The ATS-friendly CV format rules that actually matter

One column, top to bottom. Parsers read text in sequence. Multi-column layouts and tables can interleave: the parser stitches your left sidebar into the middle of your work history, or reads straight across both columns. Some modern parsers handle columns gracefully; you have no way of knowing whether the one reading your CV is one of them. A single column removes the gamble.

Standard section headings. Parsers map headings to database fields, and they're trained on the boring ones: Experience (or Work Experience), Education, Skills. "Where I've Made a Dent" maps to nothing, and everything underneath it becomes orphaned text.

Contact details in the body. Many parsers skip document headers and footers entirely. Put your name, phone number, email and location in the body of the page, never in the header, or the system may file you as a candidate with no way to be contacted.

Real text, not pictures of text. Anything rendered as an image is invisible: logos, charts, infographic timelines, and those skill-rating bars ("JavaScript ●●●○○") that parse as nothing and tell a human nothing either. Icons and emoji fare no better: at best ignored, at worst garbled into your text.

Reverse-chronological order. Most recent role first, in every section. It's what parsers expect and, more importantly, what recruiters expect.

Dates, headings and wording parsers trust

Dates deserve their own paragraph because they do so much work: they build your timeline, power the "recent experience" filters, and expose gaps. Use one format everywhere, Month YYYY ("Jun 2025 – Sep 2025"), and give every role a start and end. "Summer 2025" or a bare "2024" forces the parser to guess. If you have a genuine gap, a one-line explanation beats letting the timeline ask the question for you.

Wording matters too, because recruiter searches are still mostly literal. Include both the spelled-out and abbreviated forms of key terms, "Search Engine Optimisation (SEO)", "Customer Relationship Management (CRM)", so you match whichever one the recruiter types. Keep job titles plain: "Marketing Intern", not "Growth Ninja".

That's formatting done, but a perfectly parsed CV can still say the wrong things. That battle is covered in 3 CV Lines Quietly Getting You Auto-Rejected, the content-level companion to this guide.

PDF or Word? The file type truth in 2026

"Never send a PDF" is the most persistent rule on this list, and it's years out of date. It comes from an era when some parsers genuinely handled PDFs badly. Virtually every modern system parses a text-based PDF without complaint, and PDF has the advantage of looking identical on every machine.

The real distinction is what's inside the file. Try to select and copy the text in your exported PDF: if you can, it's real text and it will parse. If you can't (because it's a scan, a photo, or a design tool that exported your CV as one big image), the parser sees a blank page. The file type almost never fails you in 2026; what's inside the file does.

Keep a Word version only as a fallback for the rare portal that explicitly demands one. And name the file sensibly: Firstname-Surname-CV.pdf, not cv_final_FINAL_v9.pdf.

The formatting folklore you can ignore

The white-text trick deserves a special mention because it actively backfires. Parsing extracts all text regardless of colour, so your hidden keyword block appears, in full, in the plain-text record every recruiter reads. It's also revealed by a simple select-all. Either way, you've just shown a stranger that your first instinct is to deceive them.

A copyable ATS-friendly CV format for UK graduates

Here is the whole spec, top to bottom. It is deliberately unexciting: that's the point.

1. Name: plain text, the largest thing on the page. No photo (standard UK practice, and it parses as nothing anyway), no "Curriculum Vitae" title.
2. Contact line (in the body): phone, email, town or city, LinkedIn URL as plain text.
3. Profile (optional): two or three plain lines: what you've studied, what you can do, what you're looking for.
4. Education: first while your degree is your strongest card. Institution, degree title, grade or predicted grade, Month YYYY – Month YYYY. One bullet for a relevant dissertation or standout modules.
5. Experience: reverse-chronological. Each entry: employer, job title, location, Month YYYY dates, then two to five achievement bullets. Part-time and casual work absolutely counts.
6. Skills: a plain list, with spelled-out and abbreviated forms of anything searchable.
7. Extras (optional): projects, volunteering, awards, languages, under those exact headings.

Formatting rules for the whole document: one column; a common font at 10.5–12pt; hierarchy from bold and size only (no tables, text boxes, icons or rating bars); standard round bullets; consistent Month YYYY dates; maximum two pages; exported as a text-based PDF with a sensible filename.

If you were educated outside the UK, the structure above still applies, but a few conventions differ: grading, personal details, what to leave off. Our guide to UK CV format for international students covers the differences.

Check it parses before you send it

You don't have to take any of this on faith: parsing is testable. The crude version: select all the text in your finished PDF, paste it into a plain text editor, and read it top to bottom. If your contact details are present, the sections appear in order, and every job keeps its title and dates, a parser will cope. If your work history arrives shuffled like a dropped deck of cards, fix the layout before a recruiter's software finds out for you.

Frequently asked questions

Is PDF ATS-friendly? Yes, provided it's a text-based PDF, which is what Word, Google Docs and every mainstream CV builder export by default. Modern parsers handle PDFs routinely; the "never send a PDF" rule describes software from years ago. The genuine risk is an image-based PDF, such as a scan or a design-tool export, where the parser finds no text at all. If you can select and copy the text, you're fine.

How long should a graduate CV be in the UK? Two pages is the standard UK convention, and it's comfortably enough for a graduate: education, a handful of roles, skills and a project or two. The strict one-page rule is American resume culture that migrated over the internet. One page is fine if your content fits naturally, but never squeeze the font or cut real achievements to hit an arbitrary page count.

Does an ATS automatically reject CVs with the wrong format? Rarely. Outside of knockout questions ("Do you have the right to work in the UK?"), most systems don't reject anyone automatically: they parse your CV into a searchable record that humans filter and read. Bad formatting doesn't trigger a rejection letter; it quietly corrupts that record, so you stop appearing in searches. The failure is silent, which is exactly why it's worth testing.

Are two-column CV templates ATS-friendly? They're a gamble. Some modern parsers read columns correctly; others read straight across the page or splice the sidebar into your work history, scrambling the order of everything. Since you can't know which parser an employer runs, the rational move is a single column. If you love a two-column design, keep it for networking and paper. Upload the single-column version.