Should I send a PDF or DOCX?

Both work when exported correctly. DOCX from Word parses very reliably. PDFs are fine as real-text exports from Word or Google Docs. Avoid design-tool PDFs and scans.

Do ATS systems care about fonts?

Yes, indirectly. Unusual fonts can cause encoding issues or failed character extraction. Standard fonts like Calibri and Arial are safest.

Do I need one format for every ATS?

No. The single-column standard format parses well across Workday, Taleo, Greenhouse, Lever, iCIMS, and SuccessFactors. Platform-specific quirks exist but the fundamentals are the same.

Should my resume be exactly one page?

Not for ATS reasons — parsers handle multiple pages easily. Keep one page early in your career and go to two only when your strongest achievements need the room. Never pad or trim based on formatting.

Can I include a photo, logo, or links on my resume?

Avoid photos and logos — parsers ignore images, and some regions have legal guidance against photo-based screening. Links are fine as plain-text URLs in the contact section, but never hide them in images or QR codes.

Does the file name of my resume matter for ATS?

Yes, indirectly. Clear names like FirstName-LastName-Resume.pdf survive parsing and file handling better than resume_final_v3.pdf. Recruiters also search candidate files by name, so clarity helps after screening too.

Should I repeat my name in the header of page two?

Yes — a simple 'FirstName LastName — Page 2' line helps if pages get separated, but keep it minimal. Contact details belong in the page-1 body, not in headers or footers that parsers ignore.

Do ATS systems read hyperlinks in my resume?

Mostly the text, not the clickable link. Write URLs as visible plain text (linkedin.com/in/name) rather than hiding them behind linked words like 'portfolio' — and never put links inside images or QR codes.

Formatting Guide

ATS Resume FormatFree — No Signup Required

Formatting decides whether an ATS can read your resume at all. Here is the parser-friendly structure that works across every major platform.

Last updated August 11, 2026

Scan My Resume Free Build an ATS Resume

Quick Answer

The safest ATS resume format is a single-column layout with standard section headings — Contact info, Summary, Experience, Education, Skills — exported as a real-text PDF or DOCX from Word or Google Docs. Avoid two-column layouts, tables, text boxes, images, and headers/footers with contact information.

The ATS-Friendly Layout, Section by Section

1Contact information — name, phone, email, city, LinkedIn URL, in the body (not the header)
2Professional summary — 2–3 lines echoing the role's core requirements
3Work experience — standard heading, reverse-chronological, company + title + dates + bullets
4Education — degree, school, year, and certifications
5Skills — plain-text list of hard skills and tools

What Breaks Parsing (and What to Use Instead)

Choice	ATS-safe?	Notes
Single column	Yes	Safest across all platforms
Two columns / sidebar	No	Top cause of scrambled parsing
Tables for layout	No	Cells read in unpredictable order
Text boxes	No	Content can appear at the document end
Icons, skill bars, graphics	No	Ignored by parsers
Header/footer contact info	No	Fails to extract to profile fields
Real-text PDF / DOCX	Yes	Export from Word or Google Docs
Image-based PDF / scans	No	Unreadable without OCR

Formatting choices compared

Fonts, Spacing, and File Types

Use standard fonts — Calibri, Arial, Helvetica, Georgia — and avoid decorative fonts
Keep font sizes between 10pt and 12pt for body text
Use standard round bullets or hyphens, not custom symbols
Export DOCX from Word, or PDF via 'Save as PDF' from Word or Google Docs
Name files clearly: FirstName-LastName-Resume.pdf

How to Test Whether Your Format Is Safe

Copy all the text from your resume into a plain-text editor. If it reads logically top-to-bottom with sections in order, most parsers will handle it. Then run a free ATS format check to confirm there are no hidden parsing traps.

One Page or Two? How Length Affects Parsing

Parsers handle multi-page resumes fine — length is not a parsing problem. The real risk is what the extra pages contain. If a second page exists to fit a two-column layout or a wall of graphics, it is hurting you. If it holds relevant experience, keep it. The 'one page' rule is a recruiter preference, not an ATS requirement.

Under 10 years of experience — one page is usually enough
10–20 years — one to two pages, keeping only the strongest achievements
Executive, academic, or deep technical experience — two pages is acceptable when every line earns its place
Never let formatting choices (columns, sidebars, graphics) dictate your length

Before and After: Reformatting a Resume That Failed Parsing

Two-column sidebar to single-column

Before

A two-column resume with a sidebar of skills, a photo, and contact details in the page header. The parser reads the columns interleaved, drops the skills, and never captures the phone number — the recruiter sees scrambled fragments.

After

The same experience restructured as a single column: contact info at the top of the body, standard headings (Summary, Experience, Education, Skills), and a plain-text skills list. The parser extracts every field cleanly and the recruiter sees a logical top-to-bottom story.

The 30-second check

Open your saved file, select all, and copy it into Notepad or any plain-text editor. What you see is roughly what the ATS sees. If it reads like a normal document, you are safe.

The Pre-Submit Formatting Checklist

1Single column, no sidebar or two-column sections
2Standard headings: Summary, Experience, Education, Skills
3Contact info in the body, not the header or footer
4No tables, text boxes, images, icons, or skill bars
5Standard fonts (Calibri, Arial, Helvetica) at 10–12pt
6Real-text PDF or DOCX exported from Word or Google Docs
7File named clearly: FirstName-LastName-Resume.pdf
8Paste-into-plain-text test passes top to bottom

Section Headings That Parse Everywhere

Parsers map your headings to structured fields — Education goes into the education field, Experience into employment history. Non-standard headings confuse the mapping and scatter your content.

Your heading	Parser field	Avoid
Summary / Professional Summary	Summary	Profile, About Me, Who I Am
Experience / Work Experience	Employment history	Career History, Where I've Worked
Education	Education	Academic Background, Schooling
Skills / Core Competencies	Skills	Toolbox, Strengths (vague)
Certifications	Certifications	Credentials (only if used consistently)
Projects	Projects	Side Work (only if used consistently)

Headings parsers recognize reliably

Dates, Contact Info, and Links: Field-Level Parsing

Use month + year for dates (Jan 2022 – Mar 2025) — parsers map them to start/end fields
Keep contact info in the document body — headers and footers fail to extract
Write URLs as plain text: linkedin.com/in/yourname (link text alone may be missed)
Use a single phone number format consistently — hyphens or dots, not mixed
Avoid tables for contact details — cells parse unpredictably

Platform-Specific Quirks at a Glance

Platform	Common quirk	Your move
Workday	Frequent manual re-entry of work history	Keep your data handy to paste consistently
Greenhouse	Sensitive to non-standard headings	Use the exact standard heading names
Lever	Keyword matching still drives ranking	Mirror the JD's exact terms
Oracle Taleo	Strict parsing on legacy forms	Plain DOCX + standard sections is safest
iCIMS / SuccessFactors	Robust compliance features, standard parsing	Standard format works without changes

Known quirks by platform

Frequently Asked Questions

Rarely. Two-column layouts are the most common cause of parsing failure because parsers read document flow, not visual layout. Single-column is the safe default.

See Where Your Resume Ranks Before You Apply

Upload your resume, paste the job description, and get your ATS score, missing keywords, and formatting fixes in seconds.

Scan My Resume Now