Back to Blog

ATS Resume Fonts and Margins: The Formatting Rules Almost Nobody Follows

Fancy fonts and tight margins don't just look bad -they can break how an ATS reads your resume. The exact fonts, sizes and margins that parse cleanly.

Fancy fonts and tight margins do not just look bad on screen. They can break how an ATS reads your resume entirely. The parser extracts your text character by character, and when it cannot interpret a glyph, a column, or an embedded text box, it either drops the content or produces garbled output. Your experience, your skills, your job titles, gone before a recruiter sees them.

This guide covers the exact fonts, sizes, and margins that parse cleanly across the major applicant tracking systems, and the formatting choices that quietly kill applications every day.

TL;DR: Stick to Arial, Calibri, Helvetica, or Georgia at 10–12pt. Keep margins between 0.5″ and 1″. Avoid columns, text boxes, script fonts, and watermarks. To confirm your ATS formatting is clean, paste your resume into Notepad or TextEdit, if it reads logically top to bottom, it will likely parse correctly.

Table of Contents

Fonts That Parse Cleanly

Font choice is one of the most overlooked parts of ATS formatting. Most applicant tracking systems convert your resume into plain text during parsing. If the font contains unusual ligatures, custom glyphs, or characters outside standard Unicode ranges, the parser can misread or skip them entirely.

The safest approach is to choose fonts that were designed for screen rendering and digital documents, not print or design portfolios.

Recommended ATS-Safe Fonts

Font Type Recommended Size ATS Safety
Arial Sans-serif 10–12pt body Excellent
Calibri Sans-serif 10–12pt body Excellent
Helvetica Sans-serif 10–12pt body Excellent
Georgia Serif 10–12pt body Good
Times New Roman Serif 11–12pt body Good
Garamond Serif 11–12pt body Acceptable

Sans-serif fonts are generally preferred for ATS formatting because they render cleanly at smaller sizes and convert accurately during text extraction. Calibri became a default in Microsoft Word precisely because it was designed for digital readability, which makes it a natural fit for resume parsing.

Keep your body text between 10pt and 12pt. Section headings can go up to 14–16pt. Going smaller than 10pt may cause parsing errors in older systems, and going larger wastes space without any parsing benefit.

Margins and Spacing

Resume margins affect more than appearance. Tight margins can cause some parsers to treat content near the edge as a separate column or a header/footer element, both of which are often ignored or misread.

The standard guidance is to keep margins between 0.5 inches and 1 inch on all sides. One inch is the safest default. If you genuinely need more space, you can reduce to 0.5 inches, but going below that creates risk.

Line Spacing

Avoid condensed line spacing (below 1.0). Single spacing at 1.0 is fine. Many designers reduce line spacing to squeeze more content onto a page, this can cause ATS parsers to merge adjacent lines and lose structure entirely.

Between sections, a clear visual break matters. A blank line or a simple horizontal rule created with dashes or underscores works. Graphical dividers or decorative lines drawn with shapes are not parsed as whitespace, they often appear as symbols or get dropped.

Section Header Spacing

Leave at least one blank line above each major section heading. This helps the parser identify where one block of content ends and the next begins. Parsers like those used in Workday and Taleo use whitespace as a structural signal when headers are not explicitly tagged.

What to Avoid

This is where most ATS formatting errors actually happen. The design choices that make a resume look polished on screen are often the same ones that destroy it inside a parser.

Script and Decorative Fonts

Script fonts, handwritten-style typefaces, and display fonts introduce characters that standard parsers cannot reliably convert. Your name rendered in a script font may come through as a string of unrecognised symbols, or not at all.

Text Boxes

Text inside a text box is frequently invisible to ATS parsers. The box is treated as an embedded object, not as document text. If you have put your contact information, a skills summary, or any other content inside a text box, a parser may skip it entirely.

Columns and Tables Used for Layout

Two-column resume layouts look clean in Word or as a PDF. Inside an ATS, the parser often reads across columns left-to-right, row by row, producing output like "Python | 2018–2021 | Led a team of" with no coherent structure. Check the ATS resume checklist to see whether your layout is flagging this issue.

Watermarks and Background Images

Watermarks, background patterns, and embedded images add visual noise that parsers cannot process. They do not harm your content directly, but they increase parsing complexity and can corrupt surrounding text extraction.

Headers and Footers

Contact details placed in a Word or PDF header are commonly missed. Many parsers do not extract document headers and footers, they read the body text only. Put your name, email, phone number, and LinkedIn URL directly in the main body of the document.

Quick Self-Test

You do not need specialist software to do a basic ATS formatting check. This plain-text test takes about two minutes and catches the most common parsing problems.

  1. Open your resume in Microsoft Word or Google Docs.
  2. Select all the text (Ctrl+A or Cmd+A) and copy it.
  3. Paste it into a plain text editor, Notepad on Windows, TextEdit on Mac (in plain text mode).
  4. Read through the result top to bottom.
  5. Ask yourself: does the content appear in a logical order? Is your contact information at the top? Are job titles followed by employers, dates, and bullet points in the right sequence?

If the plain-text version reads cleanly, your resume will likely parse correctly. If columns have merged, if content appears in the wrong order, or if symbols have replaced text, those are formatting problems to fix before you apply.

For a more thorough check, run your resume through the JD2CV ATS scorer, it flags specific formatting issues and calculates a match score against the job description at the same time.

Common ATS Formatting Mistakes

  • Using a creative template from a design site. Most visual resume templates are built in design tools that output graphical layouts. These rarely parse cleanly.
  • Saving as .pages or .odt. Submit PDF or .docx unless the job posting specifies otherwise. PDF is safe when created from Word or Google Docs, not from design software.
  • Putting skills in a sidebar column. Sidebar content is frequently parsed out of order or skipped entirely.
  • Using icons or symbols instead of text labels. A phone icon next to your number may not be parsed as a phone number. Write "Phone:" or simply list the number as plain text.
  • Embedding a photo. Not only do photos introduce parsing noise, they also create legal complications for employers in some regions. Leave them out.

If you want a layout that avoids all of these issues from the start, browse the JD2CV parser-safe templates, each one is tested against the formatting rules covered here.

FAQ

What is the best font for an ATS resume?

Arial, Calibri, and Helvetica are the most reliable choices for ATS formatting. They are sans-serif, widely supported, and convert cleanly during text extraction. Georgia and Times New Roman are acceptable serif alternatives. Avoid any font described as "decorative," "script," or "display."

Do resume margins affect ATS parsing?

Yes. Margins that are too narrow (below 0.5 inches) can cause parsers to misidentify content near the page edge as a separate column or header element. Keep margins between 0.5 and 1 inch on all sides to stay within the safe range for standard ATS formatting.

Can I use a two-column resume layout?

Not safely. Two-column layouts are one of the most common sources of ATS parsing errors. The parser typically reads across rows left-to-right, merging unrelated content from the two columns. Use a single-column layout to ensure your information is extracted in the correct order.

Should I save my resume as a PDF or Word document?

Both are generally accepted, but the answer depends on how the file was created. A PDF exported from Microsoft Word or Google Docs is safe. A PDF exported from Canva, Adobe Illustrator, or another design tool may not be, the text layer can be missing or incomplete. When in doubt, submit .docx.

Where should I put my contact information on an ATS resume?

Always in the body of the document, not in a Word or PDF header. Many parsers do not extract content from document headers and footers. List your name, email address, phone number, and LinkedIn URL as plain text at the very top of the main body.

Key Takeaways

  • Use Arial, Calibri, Helvetica, or Georgia at 10–12pt for body text, these are the safest choices for ATS formatting.
  • Keep margins between 0.5″ and 1″. Never go below 0.5″.
  • Avoid text boxes, columns, script fonts, watermarks, and document headers for important content.
  • Place contact details directly in the body of the document, not in a Word or PDF header section.
  • The plain-text paste test is a quick, free way to check whether your resume will parse correctly.
  • Submit .docx or a Word-generated PDF. Avoid PDFs from design tools.

Conclusion

Most resume advice focuses on what you write. This article is about whether what you write can even be read. A parser-safe font, sensible margins, and a single-column layout cost you nothing, but getting them wrong costs you the interview.

The formatting rules that matter are not complicated. They just get ignored because nobody tells you about them until after you have already sent fifty applications and heard nothing back.

Start from a layout that is already clean. Skip the guesswork, build your resume from a parser-safe template at JD2CV, then run it through the ATS resume checker before you apply.