Resume Formatting for ATS: What Works and What Breaks

File format: PDF vs. DOCX

Both PDF and DOCX are standard resume formats, but they behave differently in ATS parsing. A DOCX file is essentially structured XML, which most modern parsers handle well. A PDF can be either a text-based document (easy to parse) or a flattened image (impossible to parse), depending on how it was created.

If you export a PDF from Word, Google Docs, or a similar tool, the text layer is preserved and most parsers read it correctly. If you export from a graphic design tool like Canva or Photoshop, the result may be a flat image with no extractable text — the parser sees a blank document.

Layout: columns and tables

Single-column layouts are the safest choice for ATS compatibility. Multi-column layouts — including two-column templates popular on design-oriented resume sites — cause a well-documented parsing problem: the parser may read across columns instead of down them, mixing content from your skills section with your work history.

Tables present a similar problem. Even when they look like a clean grid visually, parsers may read table cells in an unexpected order or ignore them entirely. If you're using a table purely for alignment, the visual result isn't worth the parsing risk.

Fonts and styling

Standard fonts — Arial, Calibri, Times New Roman, Georgia, Helvetica — are universally supported. Custom or decorative fonts can cause character-mapping issues in some parsers, where characters are extracted as symbols or not at all.

Bold, italic, and underline are fine and can help with readability. Avoid using color alone to convey meaning (e.g., green for strong skills, red for weak), since the parser only sees text. Skill-level bars, star ratings, and progress circles are completely invisible to an ATS.

Section headers and structure

Most parsers identify resume sections by matching heading text against a list of known labels. Headings like 'Experience,' 'Education,' 'Skills,' and 'Contact' are recognized universally. Creative alternatives often aren't.

• Use plain text for section headings, not images or graphical elements
• Avoid all-caps headers in combination with unusual spacing — some parsers misread them
• Keep section headings on their own line, visually distinct from the body text below
• Don't use symbols, emojis, or special characters in section headings

Dates and consistency

Parsers extract employment dates to calculate tenure and identify career gaps. Inconsistent date formats — mixing 'January 2024' with '01/2024' and '2024-01' in the same document — make this harder. Pick one format and use it throughout.

Include both start and end dates for each position. 'Present' or 'Current' are understood by most parsers for ongoing roles.