·4 min read·The WunderJob Team

ATS-safe CV formats: a practical guide

PDF or Word? Single column or two? Standard fonts only? Here's what actually matters for ATS parsing in 2026, stripped of the folklore.

atskeywords

A candidate asked me last week if she should submit her CV as .doc instead of .pdf because "PDFs aren't ATS-safe." That advice is from 2014. It hasn't been true in about a decade, and every modern ATS handles PDFs fine — often better than Word docs.

There's a lot of outdated folklore floating around about ATS-safe formatting. Let's go through what actually matters today.

File format: PDF is fine

PDF works. Greenhouse, Lever, Workday, SmartRecruiters, Personio — all parse PDFs natively and reliably. Some even prefer PDFs because the formatting is stable and predictable.

Word (.docx) also works. It's equally well supported.

Avoid: .doc (the old Word format), .pages, image formats (.jpg, .png), and Google Docs share links.

The one exception to "PDF is fine": if you exported a PDF from Canva or a design tool with embedded fonts that aren't standard, or if you saved a PDF as "image-only" or from a scan, the text layer may be broken. Do the copy-paste test (select all, copy, paste into a text editor). If the text comes out as gibberish or doesn't come out at all, you have an image-based PDF. Re-export with a proper text layer.

Quick check: if the job application form says "PDF preferred" or "PDF only," send PDF. If it says "Word only" (rare, but some old systems), send Word. Otherwise, PDF is the default.

Layout: single column, always

If you remember one thing from this post: use a single-column layout.

Two-column CVs are the single biggest cause of ATS parsing failures. The parser reads top-to-bottom, and when you have two columns, it interleaves them in unpredictable ways. Your skills sidebar ends up sandwiched between job descriptions.

A single column is not boring. It's just less error-prone. Strong typography, clear section headings, and good whitespace make a single-column CV look professional without fighting the parser.

Fonts: standard ones, please

The safe list, in rough order of how commonly they render correctly:

  • Arial, Helvetica, Calibri (sans-serif, most common)
  • Times New Roman, Georgia, Cambria (serif, classic)
  • Verdana, Tahoma (sans-serif, very readable)

Font size: 10-12pt for body text, 14-16pt for your name. Smaller than 10pt risks looking cramped and sometimes parses poorly.

Fonts to avoid: anything custom, anything decorative, anything that looks handwritten, and Comic Sans obviously. If your CV uses a font you downloaded from a design site, replace it before sending.

Section headings: boring is better

Use the expected section names: Experience (or Work Experience), Education, Skills, Languages, Certifications.

Don't get creative. "My Journey" as a heading confuses parsers that are looking for "Experience" or "Work History." Same for "What I Bring" or "The Story So Far." These make the parser's job harder for no upside.

Bold the headings. Use a slightly larger font size. That's enough visual hierarchy.

Bullets, dates, and structure

Bullet points are fine. Use standard dot bullets (•) or hyphens (-). Avoid fancy symbols, emojis, and graphic icons inside the body text — they sometimes render as strange characters.

Dates: use a consistent format. "Jan 2021 – Mar 2024" or "01/2021 – 03/2024" both work. Spell out the month or use MM/YYYY; don't mix formats. Always include both start and end dates; "Present" is fine for current roles.

Job structure I recommend:

Job Title
Company Name | City, Country | Jan 2021 – Mar 2024
• Bullet one
• Bullet two

This parses cleanly into almost every ATS because the structure matches what parsers are looking for: title, company, location, dates, then content.

Things that do not matter (despite what you've read)

  • Margins. Anything from 0.5" to 1" is fine. Parsers don't care.
  • Using colour. A bit of colour in headings is fine. Black-and-white is not required.
  • Length. 1-2 pages is the convention, but ATSes don't reject based on length. This is a human-preference thing.
  • File size. Under 5MB is fine. Most CVs should be under 1MB anyway.
  • File name. "FirstName_LastName_CV.pdf" is professional but "cv_final_v7.pdf" will not stop the ATS from parsing it. The recruiter sees whatever file name you used; make it professional.

A quick checklist

Before you hit submit, run through this:

  1. Single column? Yes.
  2. Standard font (Arial, Calibri, Georgia, etc.)? Yes.
  3. Standard section headings (Experience, Education, Skills)? Yes.
  4. Exported as PDF with a real text layer? Do the copy-paste test.
  5. File name looks professional? "Anna_Schmidt_CV.pdf" not "cv_draft5_FINAL.pdf."
  6. Plain-text paste reads in the right order with nothing scrambled? Yes.

A concrete test

Open your CV. Press Cmd+A, then Cmd+C. Open a plain text editor (Notepad, TextEdit in plain text mode, or just a Gmail compose window). Paste.

What you see is approximately what a recruiter's database sees. If your job titles are missing, your dates are in the wrong place, or your name is at the bottom instead of the top — fix it now, before the next application.

The takeaway

ATS-safe formatting is not complicated. Single column, standard font, PDF export, boring section headings, clean dates. That's it. The elaborate rules and anxious advice online mostly protect against problems you don't have. Focus on the basics, do the paste test, and move on.

Build your next CV with intent.

Know your values. Check job fit. Build a CV that matches.

Start Free