What Format Should a CV Be in for ATS? The Complete 2026 Guide

The format question most candidates get wrong

You spent hours on your CV content. The formatting seemed fine. But if the file format, layout, or section structure doesn't match what ATS software expects, none of that content reaches a recruiter.

"What format should a CV be in?" has a specific answer when the reader is a machine. Here's everything you need to know.

File format: .docx vs PDF

This is the most common source of confusion.

The short answer: .docx is safer for ATS in most situations.

Most applicant tracking systems were built to parse Word documents (.doc, .docx). PDF support varies significantly between ATS platforms. Some read PDFs perfectly. Others scramble the text or fail to extract sections correctly.

When to use PDF:

• The job listing explicitly says "PDF preferred" or "submit PDF"
• You're applying directly via email (where formatting preservation matters)
• The employer uses a known ATS that handles PDFs well (Greenhouse, Lever, Workday all have good PDF support)

When to use .docx:

• The listing says nothing about file format
• You're unsure which ATS the employer uses
• You're applying through an older or unknown portal

Never use: .pages, .odt, rich text format, or any format other than .docx or .pdf unless specifically requested.

Layout: single column, always

Multi-column layouts are the most common cause of ATS parsing failures.

When you create a two-column CV — contact details on the left, content on the right — the ATS reads across the whole page horizontally. This creates garbled output like: "Marketing Manager | email@gmail.com | Managed a team of..." all run together in the wrong order.

Single column rule: Every piece of information should flow from top to bottom in a single column. No sidebars, no split sections, no parallel columns.

If your current CV uses columns and you've been wondering why you're not getting responses — this is likely why.

Section headings: use standard labels

ATS systems look for expected section heading labels. They're programmed to recognise "Work Experience", "Employment History", "Education", "Skills", "Certifications".

They're not programmed to recognise:

• "My Journey" (instead of Work Experience)
• "Where I Studied" (instead of Education)
• "What I Know" (instead of Skills)
• "Highlights" or "Achievements" as standalone sections

Use standard labels. If you want to personalise, do it within the content — not the heading.

Fonts: readable, not decorative

Font choice affects two things: ATS parsing and recruiter readability.

Safe font choices:

• Arial
• Calibri
• Garamond
• Helvetica
• Times New Roman

Avoid:

• Decorative or script fonts (some fail to parse correctly)
• Very light or very thin font weights (poor readability on-screen)
• Font sizes below 10pt (some ATS systems skip content that's too small)

Standard body text at 10–12pt. Section headings at 12–14pt. Name at 16–18pt.

Elements that break ATS parsing

These are common design elements that cause problems:

Tables — Many ATS systems skip table content entirely. If your skills are in a table, they may not be parsed at all.

Text boxes — Same issue. Text inside a text box often doesn't get extracted.

Headers and footers — Critical information (your name, contact details) should never live only in the document header or footer. Some parsers ignore these entirely.

Images and icons — Phone icons, envelope icons, LinkedIn logos — all meaningless or broken to an ATS. Use plain text for contact details.

Horizontal lines — Minor risk, but some older systems struggle with these. If in doubt, leave them out.

Columns created with tables — Some candidates create two-column layouts using invisible tables. This has the same problem as visible tables.

The safe CV structure (ATS-approved)

Top to bottom:

1. Name and contact details (plain text)
2. Personal profile / professional summary
3. Work Experience (reverse chronological)
4. Education
5. Skills
6. Certifications or Additional Sections

Each section clearly labelled with a standard heading. Content in plain paragraphs and bullet points. No tables, no columns, no decorative elements.

CVCircuit handles this automatically

Every CV built in CVCircuit follows these formatting rules by default. The templates are single-column, use standard section headings, export to properly formatted files, and include no elements that break ATS parsing.

You don't need to audit your CV against this checklist — it's built in. Build your CV free and export a correctly formatted document in minutes.