Skip to content
ReadableResume

The best font for a resume, and what size to use

Pick one that looks the same in Google Docs, in Word and in the PDF a recruiter opens.

Short answer

Use Arial, Georgia, Times New Roman, Trebuchet MS or Verdana. All five are in Google Docs and come installed on Windows and macOS, so Word won't swap the font when someone opens your .docx. Set body text at 10.5 to 11 pt (never below 10), your name at 18 to 22 pt, and use one font for the whole page. When we exported one resume from Google Docs in 32 fonts, these five kept every character, while 15 of the 32 saved “fi” and “fl” as single characters.

Five fonts that travel well

FontWhat it's likeOur templates using it
ArialNeutral and very legible at small sizes. The safest choice if you're unsure.Plain (parser read 33/33), Compact (parser read 36/36), International CV (parser read 63/63), Modern Bold (parser read 33/33), Technical (parser read 35/35), Healthcare (parser read 35/35), Federal (parser read 47/47)
GeorgiaA serif made for screens. Looks traditional without feeling cramped.Classic (parser read 38/38), Student (parser read 35/35), Executive (parser read 53/53), Two-page Professional (parser read 59/59)
Times New RomanCompact, so more fits on a page. Reads as formal, sometimes dated.Jake's (parser read 46/46), Finance (parser read 44/44), Basic (parser read 33/33), Academic CV (parser read 32/32)
Trebuchet MSA humanist sans with a bit of character. Good for creative and product roles.Modern Accent (parser read 35/35), Creative (parser read 36/36), Career Change (parser read 32/32)
VerdanaVery wide and open. Easy to read, but needs a smaller size to fit.Skills-first (parser read 33/33), Modern Minimal (parser read 31/31)

Every template above was downloaded from Google Docs as a PDF and read by the same open-source parser, and all of them read cleanly. The five fonts also kept every character in the 32-font test below; Verdana, which is wide, ran to a second page there at the same size. Pick the one you like reading.

We exported one resume in 32 fonts

We took the sample resume from our Jake's template, changed only the font, imported each version into Google Docs and downloaded it as a PDF. 9 of 32 came out with every character intact and all 46 fields read correctly: Arial, Book Antiqua, Calibri, Cambria, EB Garamond, Garamond, Georgia, Times New Roman and Trebuchet MS. The most common problem was ligatures: in 16 fonts, including Roboto, Lato and Open Sans, the PDF stores a letter pair such as “fi”, “fl” or “ff” as one character.

  • Ligatures. “first” is stored as first, with “fi” as a single character. In 15 of these 16 fonts the parser also lost the space in front of the word: “checks first” came back as checksfirst.
  • Swapped fonts. Google Docs drew Aptos, the default in recent versions of Word, in Arial, and Helvetica in Helvetica Neue.
  • Company on the date line. With Aptos, Tahoma and Roboto Slab, the parser attached each company name to the date above it: May 2025 – Aug 2025Ironhaw Freight.
  • Inter. The brackets and hyphen in the phone number came out as private-use characters, and the phone field came back empty.
  • Courier New. The parser ran words together, as in Builta shipmentstatusAPI, and read 10 of 46 fields.
  • Length. At the same sizes, 15 fonts pushed the one-page resume onto a second page. Part of the lower scores in those rows comes from that: this parser joins the last line of a page to the first line of the next.
FontPagesWhat went wrongFields read
Aptos1Docs used Arial instead. Company read onto the date line.36/46
Arial1Nothing46/46
Book Antiqua1Nothing46/46
Calibri1Nothing46/46
Cambria1Nothing46/46
Century Gothic2Ran to 2 pages.41/46
Courier New2Parser ran words together. Ran to 2 pages.10/46
EB Garamond1Nothing46/46
Garamond1Nothing46/46
Georgia1Nothing46/46
Helvetica1Docs used Helvetica Neue instead. Ligatures: fi, fl and ffi.43/46
Inter1Some characters saved as private-use characters.44/46
Lato1Ligatures: fi and fl.43/46
Libre Baskerville2Ligatures: fi, fl and ffi. Contact line wrapped. Ran to 2 pages.39/46
Lora1Ligatures: fi and fl.43/46
Merriweather2Ligatures: fi and fl. Ran to 2 pages.40/46
Montserrat2Ligatures: fi and fl. Ran to 2 pages.39/46
Nunito2Ligatures: fi and fl. Ran to 2 pages.40/46
Open Sans2Ligatures: fi, fl and ffi. Ran to 2 pages.39/46
Palatino Linotype2Ligatures: fi, fl and ffi. Ran to 2 pages.40/46
Playfair Display2Ligatures: fi and fl. Ran to 2 pages.40/46
Poppins2Ran to 2 pages.37/46
PT Serif2Ligatures: fi and fl. Ran to 2 pages.30/46
Raleway1Ligatures: fi, fl and ffi.43/46
Roboto1Ligatures: fi, fl and ffi.43/46
Roboto Slab2Ligatures: fi and fl. Company read onto the date line. Ran to 2 pages.29/46
Source Sans 32Ligatures: ff. Ran to 2 pages.43/46
Tahoma1Company read onto the date line.36/46
Times New Roman1Nothing46/46
Trebuchet MS1Nothing46/46
Verdana2Contact line wrapped. Ran to 2 pages.41/46
Work Sans2Ligatures: fi and fl. Ran to 2 pages.40/46

Every version used the same layout and sizes (name 22 pt, body 11 pt) and went through the checks every template on this site goes through: the plain text from pdfminer.six, and the 46 fields read by OpenResume, an open-source parser pinned to one version. Tested October 5, 2026. The .docx files, the PDFs, the scripts and the raw results are in the test repository, and How we test explains the checks.

What it doesn't show: this is one sample, one layout and one parser. Commercial systems such as Workday or Greenhouse may handle ligatures differently, and Google Docs can change how it exports fonts. Our ATS parsing test puts these results next to a test of ten layouts.

Why not Roboto or Lato?

They look good in Google Docs, but they're Google Fonts, not system fonts. If you download a .docx and the recruiter's computer doesn't have the font, Word swaps in another one. Line lengths change, bullets wrap differently and your one-page resume can spill onto a second page. A PDF keeps the font, but that doesn't make it safe: in our test, the PDFs Google Docs made in Roboto and Lato stored “fi” and “fl” as single characters, and the parser ran those words into the one before.

Sizes

  • Body text: 10.5 to 11 pt. Verdana runs large, so 10 pt is fine there.
  • Section headings: 11 to 12 pt, bold. Capitals help a parser spot them.
  • Your name: 18 to 22 pt, bold.
  • Never below 10 pt to squeeze onto one page. Cut a line instead; the one-page guide shows the order to try things.

Templates by font

Five fonts, twenty layouts, all in Google Docs and Word.

Questions

What is the best font size for a resume?
10.5 to 11 pt for body text, 11 to 12 pt for section headings and 18 to 22 pt for your name.
Is Times New Roman bad for a resume?
No. It's compact and comes with Windows and macOS. Some people find it dated; if that worries you, Georgia gives a similar feel with more room.
Serif or sans serif?
Either. Serif fonts like Georgia feel more traditional, sans serif fonts like Arial feel more neutral. In our 32-font test, problems came from particular fonts on both sides, not from the style.
Can a font break resume parsing?
It can. When we exported one resume from Google Docs in 32 fonts, 9 came through with no problems. The most common problem was a letter pair such as "fi" or "fl" saved as a single character, which a parser can misread.
Can I use two fonts?
Keep to one. Use size and bold for hierarchy. A second font rarely adds anything, and it's one more font Word might swap.