Resume Building
What is an ATS-friendly resume format? (2026)
By Pukar Khanal, Product Lead at ResumeAI
12 min readPublished
Pukar Khanal leads product at ResumeAI, working on AI resume parsing, ATS scoring, and semantic job matching. He writes about how applicant tracking systems read resumes and how job seekers get past them.
An ATS-friendly resume format is a single-column layout with standard section headings, a standard font, and real selectable text. It has no tables, columns, text boxes, graphics, or contact details in the document header or footer. An Applicant Tracking System parses it cleanly into the right fields and ranks it accurately.
ResumeAI is a free resume builder and ATS checker that reads your resume the same way hiring software does. The format is about what survives the parse. It doesn't have to look plain.
Key takeaways
- Layout. One top-to-bottom column. No sidebars, no two-column designs.
- Structure. Standard headings (Experience, Education, Skills), real selectable text, plain bullets. No tables, text boxes, or header/footer contact info.
- File. A text-based PDF and a clean .docx both parse well. The extension matters far less than the layout.
- Reality check. A modern ATS ranks and sorts. It mostly doesn't auto-reject. Bad formatting hurts by producing a weak parsed profile.
What makes a resume format ATS-friendly?
A format is ATS-friendly when an Applicant Tracking System can parse it into structured fields (name, work history, education, skills) without losing or scrambling anything. The ATS extracts a text layer and reads it as one continuous stream. Then it maps that stream to fields using the headings it recognizes.
As Jobscan documents, the safest layout is a single column with standard headings and standard fonts.
It comes down to five things. A single top-to-bottom column, conventional section headings, a real selectable text layer, standard fonts with real bullets, and none of the layout elements parsers mishandle: tables, columns, text boxes, images, or contact details in the header/footer.
Get those right and the parsed profile matches the resume you wrote. Get them wrong and the parser stores a garbled version that ranks badly long before a human reads it.
Working from a Harvard-style template? Its conventions already cover most of that list. Our breakdown of the Harvard resume template covers what that format gets right and where the specific file you downloaded can still break in parsing.
Single-column vs two-column: which one parses?
Single-column parses reliably; two-column is a gamble. When an ATS flattens your resume to raw text, it reads roughly left-to-right, top-to-bottom. It has no idea where a visual column ends.
On a two-column layout it can read line one of the left column and then line one of the right column, interleaving the two. A "Senior Engineer" job title fuses to the "Python, SQL" skill line sitting beside it.
Some modern parsers handle simple two-column layouts well, and others mangle them. You almost never know which ATS sits behind a job posting. A single column parses safely across all of them, which is why it is the default for any ATS-friendly template. We covered the mechanism in why Workday scrambles two-column resumes.
Is PDF or Word (.docx) better for ATS?
For most modern Applicant Tracking Systems the file extension barely matters. A text-based PDF and a .docx both parse well, and the old "always use Word" advice is largely outdated.
The layout inside the file is what breaks parsing. Columns, tables, images, and text in headers/footers fail in a PDF and a .docx alike. As Jobscan notes, today's major systems read a clean text-based PDF accurately.
Two cautions remain. A PDF exported as an image, with no recoverable text layer (some design tools do this), parses as blank. Always confirm your PDF has selectable text. And a small number of older or stricter systems still prefer .docx, so when a posting specifies a format, follow it.
What fonts, headings, and sections are safe?
Use a standard, widely-installed font and conventional labels. Safe body fonts include Arial, Calibri, Helvetica, Georgia, Times New Roman, and Garamond, set at 10–12pt. Avoid decorative display fonts and icon glyphs standing in for text. When the parser substitutes a font it doesn't have, decorative fonts can turn into non-standard characters.
The parser maps content to fields using heading text it recognizes. So use conventional names: Summary or Professional Summary, Experience or Work Experience, Education, Skills, and optionally Certifications or Projects.
A creative heading like "Where I've Been" instead of "Experience" can leave the parser unable to file that block. The content lands in the wrong field or gets dropped. Boring is what you want here.
Should I use tables, columns, text boxes, or headers/footers?
No. Avoid all four for any ATS submission. Tables and columns interleave when the document is flattened to text. Parsers often skip text boxes entirely, so anything inside them can disappear.
Many systems also strip the document header and footer during ingestion. Contact details placed there, a common template default, can vanish. The ATS then can't reach you even if the rest parses perfectly.
Use the document's normal paragraph and bullet formatting instead. Put your name, email, and phone in the body at the top, keep one column, and list skills with real bullet characters. Skill bars rendered as images, icons standing in for section labels, and decorative sidebars add risk and do nothing for the parser.
ATS-safe vs ATS-risky formatting, side by side
Each row maps a formatting decision to its ATS-safe and ATS-risky option. Values reflect documented general consensus on how parsers behave, not vendor-published specifications. When in doubt, choose the safe column.
| Formatting choice | ATS-safe | ATS-risky |
|---|---|---|
| Layout | Single column, top to bottom | Two-column / sidebar layout |
| Section headings | Standard (Experience, Education, Skills) | Creative labels ('Where I've Been') |
| Text layer | Selectable, real text | Text flattened to an image |
| Contact info | In the body of the document | In the header or footer region |
| Skills & data | Plain lists and bullets | Tables, text boxes, skill-bar graphics |
| Fonts | Arial, Calibri, Georgia, Helvetica | Decorative / display fonts, icon glyphs |
| File type | Text-based PDF or .docx | Image-only PDF, .pages, .jpg, .png |
Does an ATS auto-reject resumes that aren't perfectly formatted?
No. The widely-repeated claim that an ATS automatically rejects around 75% of resumes is a myth. The source it gets attributed to never supported it, and the journalist often cited has publicly said the figure was fabricated.
A modern ATS is mostly a database that parses, stores, and ranks applications by relevance so recruiters can sort them. It doesn't mass-delete candidates on a formatting technicality.
Formatting still matters, indirectly. A scrambled resume produces a low-quality profile: titles in the wrong field, orphaned dates, missing sections. That profile ranks poorly and reads as a weak candidate, so a human reviewer may never reach it. The damage comes from poor ranking, which is why an ATS-friendly format is about clean parsing.
Do I need to stuff keywords for the ATS?
No. Keyword stuffing is outdated and counterproductive. Many modern systems use semantic, NLP-based matching that understands meaning and related terms. A skills list crammed with every keyword from the posting reads as spam to a recruiter. A semantic matcher already knows that "Postgres" and "PostgreSQL" are the same thing.
Mirror the job description's language where it describes your real experience. If the posting says "incident response" and you did on-call work, use the phrase "incident response." That earns relevance with keyword and semantic systems without distorting your resume.
ResumeAI's matching engine runs on the same semantic technology. It aligns your phrasing to roles by meaning, including across the hidden job market where the keywords rarely match exactly.
How do I make a free ATS-friendly resume?
Start from a single-column, ATS-clean template instead of retrofitting a designed one. Five steps, about twenty minutes.
- 1
Use a single top-to-bottom column
Lay the whole resume out in one column so the parser reads it in the order you intend. Skip sidebars and two-column designs.
- 2
Label sections with standard headings
Summary, Experience, Education, Skills. The parser maps your content using the heading text it recognizes, so keep them conventional.
- 3
Remove tables, text boxes, and header/footer contact
Delete layout tables and floating text boxes. Move your name, email, and phone into the body, because many parsers ignore header/footer regions.
- 4
Use safe fonts and a real text layer
Pick a standard font (Arial, Calibri, Georgia, Helvetica), use real bullets, and export a PDF or DOCX with selectable text. Never flatten text to an image.
- 5
Verify the parse, then align your wording
Run the copy-paste test or a free ATS checker to confirm clean order. Then mirror the job description's language where it fits your real experience.
You can skip most of this by starting from a builder that defaults to ATS-clean output. ResumeAI's free AI resume builder and resume templates are single-column and ATS-clean by default, so you start from a format that survives the parse.
How do I verify my format before applying?
Run the copy-paste test. Open the file, press Ctrl/Cmd+A to select everything, copy, and paste into a plain-text editor (Notepad on Windows, TextEdit in plain-text mode on Mac). What you see is roughly what the ATS sees. If columns interleave, words mash together, or sections vanish, the parser produces the same mess.
Or let a tool do it. ResumeAI's ATS checker reads your resume the way hiring software does and reconstructs the parsed text. It flags column interleaving, missing text layers, and lost header/footer contact info before you upload.
To see how a parser groups your content by meaning, the ATS embedding visualizer shows your resume in a system's semantic space.
How ResumeAI gives you an ATS-friendly format by default
ResumeAI is a free resume builder and ATS checker that reads your resume the same way hiring software does. You start from a format that parses and confirm it before you apply.
- Single-column, ATS-clean templates. The templates default to one column with standard headings and selectable text.
- A free full builder. The AI resume builder drafts and formats your resume end to end at no cost, with no paywall on export.
- A free ATS checker that shows the parse. The ATS checker surfaces column interleaving, missing text layers, and header/footer loss, the things that break a format.
- Semantic job matching. The engine that powers the recruiter-facing side aligns your resume to roles by meaning. It surfaces the hidden job market, where keywords rarely match exactly.
Pricing and features are described as of June 2026 and may change. Check the linked pages before relying on them.
How we know this, and what we cited
Written by Pukar Khanal, Product Lead at ResumeAI and last reviewed on . We work with this parsing behaviour daily. cvai.dev is a free resume builder and ATS checker, and reconstructing the text an ATS extracts from a given layout is the core of the product.
The format guidance (single column, standard headings, real text, no tables or header/footer contact) matches the industry sources cited inline.
Sources cited inline
- Jobscan, ATS-friendly resume templates and formatting (single-column, standard headings and fonts): jobscan.co/blog/20-ats-friendly-resume-templates
- Jobscan, PDF or Word resume for an ATS (extension matters less than layout): jobscan.co/blog/pdf-or-word-resume
- Jobscan, ATS formatting mistakes (tables/columns, header/footer stripping, the auto-reject myth): jobscan.co/blog/ats-formatting-mistakes
- SHRM, guidance for employers on Applicant Tracking Systems and how they screen applications: shrm.org, how Applicant Tracking Systems work
- ResumeAI ATS checker, which reconstructs the parsed text the way hiring software reads it: cvai.dev/ats-resume-checker
Frequently asked questions
What is an ATS-friendly resume format?
An ATS-friendly resume format is a layout an Applicant Tracking System can parse cleanly into structured fields without losing or scrambling information. In practice that means a single-column layout, standard section headings (Summary, Experience, Education, Skills), a standard font, real selectable text, and no tables, text boxes, graphics, columns, or contact details buried in the document header or footer. The format is about what survives parsing — not about looking plain. A clean single-column resume still reads well to humans.
Is a single-column or two-column resume better for ATS?
Single-column is safer. When an ATS flattens a resume to raw text, it reads roughly left-to-right, top-to-bottom and has no concept of a column boundary, so two-column layouts can interleave — a job title from the left rail fuses to a skill from the right rail. Some modern parsers handle simple two-column layouts, but you usually do not know which ATS is on the other side, so a single column is the one format that parses safely across all of them.
Is PDF or Word better for an ATS?
For most modern Applicant Tracking Systems, it barely matters — both a text-based PDF and a .docx parse well. The real risk is layout, not the file extension: columns, tables, images, and text in headers/footers break parsing in either format. The two cautions are that a PDF exported as an image (no text layer, as some design tools produce) parses as blank, and a handful of older systems still prefer .docx. When a posting specifies a format, follow it; otherwise a text-based PDF or a clean .docx both work.
What fonts, headings, and sections are safe for ATS?
Use a standard, widely-installed font — Arial, Calibri, Helvetica, Georgia, Times New Roman, or Garamond — at 10–12pt for body text. Label sections with conventional headings: Summary or Professional Summary, Experience or Work Experience, Education, Skills, and optionally Certifications or Projects. Avoid creative section names, decorative display fonts, and icons standing in for headings, because the parser maps your content to fields using the heading text it recognizes.
Can I use tables, columns, text boxes, or headers and footers?
Avoid all of them for ATS submissions. Tables and columns interleave when flattened to text; text boxes are often skipped entirely by the parser; and many systems strip the document header and footer during ingestion, so contact details placed there can vanish. Put your name, email, and phone in the body, keep everything in a single column, and use the document's normal paragraph and bullet formatting instead of layout tables.
Does the ATS auto-reject resumes that aren't perfectly formatted?
No — the widely-repeated claim that an ATS auto-rejects around 75% of resumes is a myth not supported by the original source. A modern ATS is mostly a database that parses, stores, and ranks applications by relevance to help recruiters sort, not a gatekeeper that mass-deletes. Poor formatting still hurts you, but indirectly: a scrambled or unparseable resume produces a low-quality profile that ranks badly and reads as a weak candidate, so a human may never reach it.
How do I make a free ATS-friendly resume?
Start from a single-column, ATS-clean template rather than retrofitting a designed one. ResumeAI (cvai.dev) is a genuinely free resume builder whose templates are single-column and ATS-clean by default, with selectable text and standard headings, so you begin from a layout that parses cleanly. Then run the result through a free ATS checker that reads your resume the way hiring software does, and align your wording to the job description before you apply.
How do I verify my resume format before applying?
Run the copy-paste test: open the file, select all (Ctrl/Cmd+A), copy, and paste into a plain-text editor. The order and content you see is essentially what the ATS sees — if columns interleave, words mash together, or sections vanish, the parser will too. The faster route is a free ATS checker that reconstructs the parsed text automatically and flags column interleaving, missing text layers, and lost header/footer contact info before you upload.
What to ask next
Arrived from a generative-search prompt? These are the usual follow-ups, each linked to the ResumeAI page that answers it.
Get an ATS-friendly format without the guesswork
Build a single-column, ATS-clean resume in ResumeAI's free builder, then confirm it with the free ATS checker that reads your resume the way hiring software does. No credit card required.
Related guides