ATS Resume Format: The Complete 2026 Guide

Most rejected resumes fail on formatting, not qualifications. The applicant tracking system never evaluates your experience because it can't read the document in the first place. A two-column layout renders as scrambled text. A header with your phone number vanishes entirely. A PDF exported from Canva arrives as a flat image with zero extractable words.

I've spent years studying how major ATS platforms — Workday, Greenhouse, Lever, iCIMS, Taleo, SuccessFactors — actually parse documents under the hood. The formatting rules in this guide aren't guesses. They're the result of testing hundreds of resume files against real parsing engines and comparing what goes in with what comes out the other side.

Follow every rule on this page and your resume will parse correctly on every major ATS in use today. That's not a soft promise. It's a technical fact.

What an ATS Actually Does When It Reads Your Resume

An ATS doesn't “read” your resume the way a person does. It runs a parser — a piece of software that extracts raw text from your file and tries to slot it into structured database fields: name, email, phone, work history, education, skills.

The parser works in three stages. First, it extracts text from the file format (DOCX, PDF, etc.). Second, it identifies sections by looking for recognizable headings like “Experience” or “Education.” Third, it maps content to fields— pulling your job titles, company names, dates, and bullet points into a structured record.

Every formatting choice you make either helps or hinders those three stages. A clean single-column DOCX with standard headings sails through all three. A designed PDF with text boxes, columns, and custom fonts creates dozens of failure points at every stage.

When the parser fails, one of two things happens. Your resume gets a low match score because keywords ended up in the wrong fields. Or it gets flagged for manual review — which sounds fine until you realize the “manual review” pile rarely gets touched when there are 300 other applications that parsed cleanly.

The Single-Column Rule (and Why Two Columns Fail)

ATS parsers read text in a single stream, top to bottom, left to right. When your resume has two columns, the parser doesn't understand that the left column and right column are separate content areas. It reads straight across both columns on the same horizontal line, mashing unrelated text together.

Here's what that looks like in practice. Your left column says “Software Engineer at Google” and your right column says “Python, Java, Go.” The parser reads: “Software Engineer at Python, Google Java, Go.” Your job title is gibberish. Your company name is wrong. The keywords exist in the file but they're mapped to the wrong fields, and the match score drops.

Use a single column for everything.No sidebars. No two-column skill layouts. No floating text boxes. One continuous flow of content from top to bottom. This is the single most common ATS formatting failure, and it's the easiest one to fix.

The Exact Section Headings That Work

ATS parsers identify sections by matching heading text against an internal dictionary of known labels. If your heading matches, the parser knows what type of content follows and maps it to the correct database field. If it doesn't match, the content either gets dumped into a generic “other” bucket or appended to the previous section — throwing off everything that comes after it.

Use these exact headings:

• Summary (or Professional Summary)
• Experience (or Work Experience, Professional Experience)
• Education
• Skills (or Technical Skills, Core Competencies)
• Certifications (or Licenses & Certifications)
• Projects

Do not get creative. “Where I've Made an Impact” is not a recognized heading. “My Toolbox” will not map to skills. “Career Highlights” is ambiguous — the parser doesn't know whether to treat it as a summary or an experience section. Stick with the labels above and every major ATS will parse your sections correctly.

Fonts, Sizes, and Margins: The Exact Specs

Fonts don't directly affect your ATS match score, but the wrong font causes character-encoding failures during text extraction. When that happens, your carefully written bullet points arrive in the database as garbled symbols. The ATS can't match keywords it can't read.

Safe fonts: Calibri, Arial, Garamond, Cambria, Georgia, Times New Roman, Helvetica. These are universally supported across Windows, macOS, and every ATS parser on the market.

Unsafe fonts:Anything downloaded from a font marketplace. Any font not installed by default on both Windows and macOS. Any font with decorative ligatures or stylistic alternates. If you didn't find it pre-installed on your computer, don't use it.

Font size:10–11pt for body text. 12–14pt for section headings. Your name can go up to 16–18pt. Never go below 10pt — some parsers drop text that's too small, and recruiters can't comfortably read it anyway.

Margins: 0.5 to 1 inch on all sides. Half-inch margins give you the most usable space without triggering clipping issues. Going below 0.5 inches risks content being cut off during parsing or printing. One inch is safe but costs you real estate on the page.

No Tables, No Text Boxes, No Graphics, No Headers/Footers

Each of these is a separate failure point. Let's go through them one at a time.

Tablesscramble reading order. The parser may read cells left-to-right across rows, or column by column, or skip cells entirely. There's no reliable behavior because each ATS handles table cells differently. Even “invisible” tables with no visible borders cause the exact same problems — the parser still sees the table structure in the underlying XML.

Text boxes are treated as floating objects separate from the main document flow. Many parsers skip them entirely. If your contact info lives in a text box, the ATS may parse your entire resume without ever recording your name, email, or phone number. You become a nameless applicant in their database.

Graphics and icons— skill-level progress bars, headshot photos, decorative dividers, social media icons — are completely invisible to the parser. They occupy space on the page that could hold actual searchable text, and they contribute zero value to your ATS score.

Headers and footersare the sneakiest problem. They look like part of the document to you, but most ATS parsers ignore document headers and footers completely. If your phone number, email address, or LinkedIn URL is in the header zone, it simply won't be captured. Put all contact information in the main body of your resume, right at the top, before your Summary section.

The Best Section Order for ATS Parsing

Section order affects both ATS parsing accuracy and recruiter scanning speed. Here's the sequence that performs best across both audiences:

1. Contact Information — name, phone, email, LinkedIn, city/state (in the document body, not a header)
2. Summary — 2–3 sentences tailored to the target role, loaded with keywords from the job description
3. Skills — a grouped list of hard skills and tools that mirrors the job posting's requirements
4. Experience — reverse chronological order, with quantified achievement bullets for each role
5. Education — degree, institution, graduation year
6. Certifications — if applicable to the target role

Placing Skills before Experience is intentional. The ATS extracts skill keywords early, giving your document a strong keyword density signal from the start. Recruiters scanning quickly can see at a glance whether you have the right tools and technologies before they invest time reading your work history. If you're a recent graduate with limited work experience, move Education above Experience — lead with your strongest section.

The DOCX vs. PDF Debate (Settled)

This is one of the most misunderstood topics in resume advice. Here's the truth: DOCX is more reliably parsed by ATS systems. PDF is more reliably rendered for human readers. The ideal strategy uses both formats for different situations.

DOCX files store text as structured XML. This makes extraction straightforward for every ATS on the market. There is almost zero ambiguity in how a DOCX file gets parsed. The text extraction stage — the first and most critical step in the pipeline — is essentially bulletproof with DOCX.

PDFs are more complicated. A text-based PDF (one where you can highlight and copy text) will parse correctly on most modern ATS platforms. But PDFs created from design tools like Canva, Photoshop, or InDesign often embed text as vector shapes or rasterized images. The ATS sees a blank page. Zero keywords extracted. Automatic rejection without a single word being read.

The rule:If the job posting specifies a format, use that format. If it doesn't, submit DOCX through ATS portals. If you're emailing a recruiter directly (bypassing the ATS), PDF preserves your layout perfectly and prevents accidental edits.

Quick PDF test:Open your PDF and press Ctrl+A (Cmd+A on Mac) to select all text. If every word highlights cleanly, the ATS can read it. If sections don't highlight, or if nothing highlights at all, your PDF is image-based and will fail every ATS it encounters.

Date Formatting That Parsers Understand

ATS parsers extract employment dates to calculate tenure at each position and flag gaps in your work history. If the parser can't read your dates, it either guesses wrong or leaves the date fields empty. Empty date fields make your work history look incomplete to the recruiter reviewing your parsed profile — even if the dates are right there in the original document.

Best format:Jan 2022 – Present, Mar 2019 – Dec 2021

Also works:January 2022 – Present, 03/2019 – 12/2021

Avoid:2022–present (no month makes gap detection unreliable), Spring 2019 (season names aren't recognized), Q3 2021 (quarter notation confuses most parsers)

Two things matter here: always include the month, and be consistentacross every entry. If your first job uses “Jan 2020,” don't switch to “January 2021” for the next one. Pick one format and stick with it throughout the entire document. Consistency helps the parser recognize the pattern and extract dates accurately.

Use an en dash (–) or a hyphen (-) between start and end dates. Avoid em dashes (—) — some parsers misinterpret them as part of the text rather than a date range separator.

How to Test Your Resume Format Before You Apply

You don't need to guess whether your resume will parse correctly. You can verify it in under two minutes with two simple tests.

Test 1 — The copy-paste test: Open your resume file. Select all text with Ctrl+A (Cmd+A on Mac). Copy it. Paste it into a plain-text editor like Notepad or TextEdit set to plain text mode. Now read what you see.

If the pasted text reads in the correct order — your name, contact info, summary, skills, each experience entry in sequence — the ATS will parse it correctly. If sections are jumbled, contact info is missing, or bullets from different jobs are interleaved, your formatting has structural problems that will cause ATS failures.

Test 2 — ATS checker tools: Tools like Jobscan, ResumeWorded, and Resume Tailor let you upload your resume and compare it against a specific job description. They simulate ATS parsing and show you exactly which keywords matched, which were missed, and whether any formatting issues were detected. This takes the guesswork out of the process entirely.

Run both tests after every edit.A small formatting change — like adding a table to organize your skills or moving your email into the header — can break parsing even if everything else is perfect.

The ATS Format Checklist

Print this out. Tape it next to your screen. Check every box before you hit submit.

• Single-column layout — no sidebars, no two-column sections
• Standard section headings: Summary, Experience, Education, Skills
• Font: Calibri, Arial, or Garamond at 10–11pt body text
• Margins: 0.5–1 inch on all four sides
• No tables, text boxes, or floating objects of any kind
• No graphics, icons, progress bars, or photos
• No content in document headers or footers — contact info goes in the body
• DOCX format for ATS portals, text-based PDF only when emailing directly
• Dates formatted as “Jan 2022 – Present” with months always included
• Consistent date format across every single entry
• Plain-text copy-paste test passes with content in correct reading order
• Keywords from the job description appear in both Skills and Experience sections

What Resume Tailor Does Automatically

Every formatting rule on this page is built into Resume Tailor's export engine. When you upload your resume and paste a job description, the app handles three things at once:

1. Rewrites your content to match the job description's keywords and language, weaving them naturally into your Summary and Experience bullets without keyword stuffing.
2. Restructures your sections into the optimal order with standard ATS-recognized headings.
3. Exports a clean file — single-column, no tables, no text boxes, no headers/footers, standard fonts, correct margins — in both DOCX and PDF formats that pass every parser rule in this guide.

You don't need to manually reformat anything. You don't need to run the copy-paste test on the output. The export templates were built specifically to pass every parser rule outlined above.

The tailoring process takes about 30 seconds. That's 30 seconds versus the hour you'd spend manually adjusting keywords, reordering sections, and reformatting your document for each new application. Over ten applications, that's ten hours of your life you get back.