ATS friendly CV format: the layout rules that matter

It helps to separate two jobs. Format decides whether software can read your CV accurately. Content decides whether a human, once the CV is in front of them, wants to interview you. An ATS friendly format does nothing for weak content, and strong content can be lost in a format the parser cannot handle.

The good news is that the format rules are few, and none of them require a dull document. A clean, well-spaced, single-column CV with a confident typeface looks professional to people and reads reliably to software. The problems come almost entirely from decorative templates: sidebars, graphics, icons and text boxes that look distinctive in a preview and fall apart in a parser.

There is a human reason to prefer the same simplicity. Recruiters increasingly open CVs on laptops and phones, often inside the applicant tracking system's own viewer rather than in Word. A sidebar that looked elegant in the template can shrink to an unreadable strip on a small screen. A single-column document reflows cleanly wherever it is opened.

Most modern applicant tracking systems read both .docx and text-based PDF files well. The key phrase is text-based. A PDF exported from Word or Google Docs contains real, selectable text. A scanned document, a photo of a CV, or a PDF exported from design software with text converted to shapes contains no readable text at all.

Two simple rules cover almost every case. If the posting or portal asks for a specific format, use it. If it does not, a .docx is the safest choice for older or unknown systems, and a text-based PDF is fine for most others. Check your PDF by trying to select and copy a sentence from it: if you cannot, neither can the software. Avoid older formats such as .doc, and never upload an image file as a CV.

Name the file plainly, for example "Priya-Fernando-CV.pdf". Recruiters download hundreds of documents called "CV-final-v3", and a clear file name keeps yours identifiable once it leaves the system. Keep the file size small by avoiding embedded images; some portals reject large uploads without telling you why.

Parsers generally read a page top to bottom and left to right. Anything that breaks that simple flow risks scrambling the order of your information. These are the layout elements most likely to cause trouble:

An ATS uses your headings to decide where each section starts and what it contains. Creative headings like "Where I've made an impact" or "My toolkit" may not be recognised, so your experience might not be filed as experience. The order matters less than the wording: profile, experience, skills and education in any sensible sequence will parse, provided each heading sits on its own line in plain text, styled with bold or a larger size rather than placed inside a shape or a table cell. Use conventional wording like this:

Use a widely available font such as Calibri, Arial, Aptos, Georgia or Garamond, at a readable body size, usually 10 to 12 points. Unusual downloaded fonts can be substituted or misread, and very small text makes the document hard to read for people as well as software.

Keep bullets simple: standard round bullets or hyphens, not arrows, checkmarks or custom symbols that can turn into stray characters. Write dates in one consistent format, such as "March 2022 to present" or "03/2022 to 06/2024", placed on the same line as the job title or directly below it. Parsers use dates to calculate your experience, and inconsistent formats can produce odd results.

Keep each job's details in a predictable order: title, employer, location, dates, then bullets. Consistency across every role makes both parsing and human skimming easier.

Colour and emphasis are safe in moderation. Bold job titles, a single accent colour for headings and generous white space all survive parsing, because the underlying text is unchanged. What does not survive is meaning carried only by design: a timeline drawn as a graphic, a skill shown as a filled circle, a heading that exists only as a coloured bar. If information matters, it has to exist as words on the page.

Page margins and spacing are a human concern rather than a parsing one. Shrinking margins to squeeze in an extra role makes the page feel crowded and does nothing for the software. If the content does not fit, cut content.

Many templates put your name and contact details inside the document header, the area Word repeats at the top of every page. Some applicant tracking systems skip headers entirely, which means your email and phone number may not reach the candidate record. Put your name and contact details as normal text at the top of the page body instead. It looks identical to a reader.

Keep the details simple: name, phone number with country code if you are applying abroad, a professional email, city and country, and a LinkedIn URL. Write them as text, not as icons, and avoid putting them in a table or a coloured sidebar.

Links deserve a quick check too. Write your LinkedIn URL out in full, or at least as "linkedin.com/in/yourname", rather than hiding it behind the word "LinkedIn". A hyperlink may survive in the file, but the parsed record and any printed copy only keep the visible text. The same applies to portfolio or GitHub links in creative and technical roles.

You do not need special software to catch the most common problems. These checks reveal most formatting issues before an employer's system does: