ATS Resume Format: Formatting Rules That Get Your Resume Past the Bots

Most ATS formatting advice focuses on keywords. The formatting layer is just as important. A resume with perfect keyword density but broken formatting will still be rejected before any recruiter reads a word. ATS systems parse your document structure first, extract text second, and score keywords third. If the parsing step fails, the keyword score never runs. This guide covers every formatting rule that affects parse success, which platforms enforce which rules, and a 15-point checklist to verify your resume before submitting.

ATS by the Numbers

99%

of Fortune 500 companies use ATS to screen applicants (Jobscan, 2024)

75%

of resumes are rejected by ATS before a human ever reads them (Jobscan, 2023)

average number of ATS formatting errors per resume submitted (Resume Optimizer Pro audit, 2025)

63%

of job seekers are unaware that ATS formatting rules differ from visual design standards (CareerBuilder, 2023)

What ATS Formatting Actually Means: Parsing vs. Scoring

ATS systems run two separate processes when they receive your resume. Understanding the difference explains why formatting errors are so damaging.

Stage 1: Parsing

The ATS reads your file and extracts raw text. It identifies which words belong to which section. A table cell labeled "Experience" is treated differently from a text block with the heading "Work Experience."

If parsing fails: Contact info lands in the wrong field, job titles disappear, dates become unreadable. The record is incomplete and gets auto-rejected or buried at the bottom of results.

Stage 2: Scoring

After extraction, the ATS compares your text against the job description. It assigns keyword match scores, evaluates experience length, checks education requirements, and ranks candidates.

If parsing was broken: Scoring never runs accurately. Keywords buried inside a table or text box are frequently missed entirely.

Key insight: You can have every required keyword in your resume and still score near zero if those keywords are inside a text box, table, or header/footer element that the ATS cannot parse correctly.

The ATS-Safe Formatting Rules

File Format: PDF vs. Word

The right file format depends on which ATS the employer uses. Here is the practical breakdown:

Format	When to use	Caution
PDF	Most modern ATS (Greenhouse, Lever, iCIMS, Workday 2020+) parse PDFs reliably. Use PDF when the job posting does not specify a format and the company appears to use a modern ATS.	Older Taleo instances and some legacy systems have inconsistent PDF parsing. If you cannot identify the ATS, submitting Word is the safer default.
.docx (Word)	The universal safe choice. Every major ATS parses .docx reliably. Use it when the posting explicitly requests Word format, or when applying through an older company portal.	Word files can shift formatting between versions. Save as .docx (not .doc) and verify layout before submitting.
PDF from Canva / Figma	Never. These export as image-based PDFs that contain no machine-readable text.	Your entire resume parses as blank. 0% keyword match guaranteed.

Fonts

ATS systems do not render fonts visually. They extract text from font data embedded in the file. Non-standard fonts can cause character-level extraction errors: an "fi" ligature in a decorative font may parse as a single unrecognized character instead of "fi," breaking words like "financial" or "profile."

ATS-Safe Fonts

Arial
Calibri
Garamond
Georgia
Times New Roman
Helvetica
Tahoma
Verdana
Cambria

Fonts to Avoid

Any decorative or script font
Fonts downloaded from design sites (Canva, Dafont)
Fonts with heavy ligatures
Icon fonts (Font Awesome, etc.)
Custom branding fonts not included in standard OS installs

Size rules: Body text should be 10 to 12pt. Section headings should be 14 to 16pt. Going below 10pt causes some parsers to treat text as decorative metadata and skip it.

Margins

Set all margins between 0.5 and 1 inch. Margins narrower than 0.5 inches push text into print zones that many parsers ignore as footer content. Wider than 1 inch wastes space and forces important content onto a second page unnecessarily.

Section Headings: Use Standard Names

ATS systems recognize section headings by matching them against a built-in dictionary of expected terms. When you use a creative heading name, the parser may miscategorize the section or skip it entirely.

Use this	Not this
Work Experience	Career History, Professional Journey, Where I've Been
Education	Academic Background, My Degrees, Learning
Skills	What I Know, Toolkit, Proficiencies
Summary	About Me, Profile, My Story
Certifications	Credentials, Licenses & Certs, Badges
Projects	Work Samples, Portfolio Highlights

Elements to Avoid Entirely

Elements That Break ATS Parsing

Tables: Cell content is often parsed out of order or skipped entirely by older parsers
Text boxes: Treated as floating objects, not document flow. Most parsers ignore them.
Multi-column layouts: Left-to-right parsing reads columns in the wrong order, creating nonsense text
Headers and footers: Contact information placed here is frequently not extracted
Graphics, logos, and photos: Not machine-readable; waste parse processing and trigger rejection on many platforms
Horizontal lines as section dividers: Some parsers treat them as page breaks

Safe Alternatives

Instead of tables: Use plain text with consistent spacing or a bulleted list
Instead of text boxes: Use the main document body with bold headings
Instead of columns: Use a single-column layout with clear section breaks
Instead of header/footer contact info: Place all contact details at the top of the main body
Instead of graphics: Use text-based skill lists or keyword-rich descriptions
Instead of horizontal rules: Use extra line spacing or a bold heading to signal section breaks

Date Formats

Use consistent date formats throughout your resume. ATS systems parse dates to calculate tenure, check for employment gaps, and rank recency. Inconsistent formats confuse parsers and can result in incorrect tenure calculations.

Acceptable: May 2022, 05/2022, 2022
Acceptable: May 2022 to Present, 05/2022 to Present
Avoid mixing: Do not use "May 2022" in one role and "06/2023" in another
Avoid: Approximate ranges like "Early 2022" or "Q2 2022"

Bullet Points

Use standard round bullets (the bullet character in your word processor's default list styles). Unicode symbols, custom arrows, checkmarks, and other special characters are parsed inconsistently. On some systems, a checkmark bullet causes the entire line to be dropped from the parsed record.

Safe bullets: Plain round bullet (•) or hyphen (-). Avoid: Arrows (→), checkmarks (✓), diamonds (◆), stars (★), or any non-standard Unicode character as a list marker.

Contact Information

Place all contact details as plain text in the main document body, not inside a Word header element or a text box. This is one of the most common formatting errors we see. A name and phone number in a document header look fine visually but many ATS systems do not extract header/footer content into the candidate record.

Required fields: Full name, phone number, email address, city and state (or city and country for international applications). LinkedIn URL is strongly recommended. Do not include street address.

Page Length

One page for fewer than 10 years of experience. Two pages maximum for anyone else. Three or more pages are appropriate only for academic CVs, federal resumes, and executive bios. Most ATS systems accept multi-page documents but recruiters using those systems consistently report scanning only the first two pages (The Ladders eye-tracking study, 2023).

ATS Formatting Differences by Platform

Not all ATS platforms parse resumes the same way. These platform-specific behaviors are relevant if you can identify which system an employer uses, often visible in the application URL or the "Apply" button branding.

Platform	File format preference	Known parsing quirks
Workday	PDF or .docx	Strong PDF parser. Handles standard PDFs reliably. Tables in the header section sometimes cause name/email extraction errors.
Greenhouse	PDF preferred	Very reliable modern parser. Multi-column layouts still cause field scrambling. Headers and footers not extracted.
Lever	PDF or .docx	Above-average parser accuracy. Text boxes are ignored. Performs well with standard single-column PDF.
iCIMS	.docx recommended	Older parsing engine with less PDF reliability. .docx submission consistently outperforms PDF on parse accuracy. Tables cause section misclassification.
Taleo (Oracle)	.docx strongly preferred	Legacy parser. Known issues with PDF encoding, text boxes, and special characters. Plain .docx with zero formatting tricks produces best results.

For more detail on each platform, see our guides to ATS resume templates and the ATS-compliant resume standards each platform enforces.

The ATS Formatting Checklist (15 Items)

Run through this before every submission. Each item maps to a specific parse failure mode.

File is saved as .docx or a text-based PDF (not an image-based PDF from Canva or Figma)
Font is from the ATS-safe list (Arial, Calibri, Garamond, Georgia, Times New Roman, Helvetica, Tahoma, Verdana, Cambria)
Body text is 10 to 12pt; section headings are 14 to 16pt
All margins are 0.5 to 1 inch
Single-column layout throughout; no multi-column sections
No tables anywhere in the document
No text boxes anywhere in the document
No graphics, logos, photos, or icons
Contact information is in the main document body, not inside a Word header or footer element
Section headings use standard names (Work Experience, Education, Skills, Summary, Certifications)
Date formats are consistent throughout (e.g., "May 2022" everywhere, not mixed with "05/2022")
Bullet points use standard round bullets or hyphens, not Unicode symbols or arrows
No white-text keywords hidden anywhere in the document
Resume is 1 page (under 10 years experience) or 2 pages maximum (10+ years experience)
File name is clean and professional (e.g., Jane-Smith-Resume.pdf), not "FinalResumev3_ACTUAL.pdf"

How to Test Your Resume Format Before Applying

Three methods to verify your resume will parse correctly:

Method 1: Copy-Paste Test

Open your resume. Select all. Copy. Paste into a plain text editor (Notepad on Windows, TextEdit in plain text mode on Mac). If the result is readable, structured text, your resume will likely parse correctly. If it is garbled or empty, you have a serious formatting problem.

Method 2: Parse Verification

Upload your resume to Resume Optimizer Pro. The parser extracts every field and shows you exactly what the ATS sees: your name, contact details, each job title, date, and skill. Compare the parsed output against your original document to catch any fields that did not extract correctly.

Method 3: ATS Score Check

Paste a job description alongside your resume into an ATS checker. A very low match score on a role you are clearly qualified for usually indicates keywords are present in your resume but are not being extracted due to a formatting issue. Compare the keywords it reports as missing against what you actually wrote.

How Resume Optimizer Pro Catches These Issues

Resume Optimizer Pro's format analyzer checks every item in the checklist above automatically when you upload your resume. It flags specific formatting errors with the exact location in your document, explains why each issue affects ATS parsing, and suggests the precise fix.

Unlike a generic formatting checklist, the analyzer also runs your formatted resume through a simulated ATS parse and shows you the extracted field output: name, email, phone, each position with dates and titles, education records, and the full skills list the ATS would score against a job description.

See the engineer-approved ATS-friendly template and the complete template library for formatting-safe starting points. For a broader overview of ATS-friendly resume best practices, including keyword optimization, see our companion guide.

Optimize My Resume

Frequently Asked Questions

For most modern ATS platforms (Greenhouse, Lever, Workday 2020 and later), either format parses reliably. When in doubt, use .docx. It is the universal safe choice across every major ATS, including older Taleo and iCIMS instances that have inconsistent PDF parsing. Only submit PDF if the posting explicitly requests it or you are confident the employer uses a modern ATS.

Not always outright rejected, but content inside tables and multi-column layouts is frequently extracted incorrectly or skipped entirely. The result is a candidate record with missing job titles, scrambled dates, or gaps in the skills section. This lowers your match score even if you have the right keywords, because the ATS cannot find them in their correct context. Single-column, no-table layouts produce consistently higher parse accuracy across all five major ATS platforms.

No. Canva and Figma export resumes as image-based PDFs. These files contain no machine-readable text. Every ATS parses them as a blank document. Your keyword match score is 0% regardless of how well-written the content is. If you like a Canva design visually, recreate the same layout in Word or Google Docs using a plain single-column structure and a standard font. See our guide to checking your resume score for free to verify your final file parses correctly.