Resume Fonts to Avoid: What AI Screeners Actually Reject
Your resume can look flawless on your screen and still lose to a parser before a person ever opens the file.
Searching an ATS for qualified candidates and opening their resumes to actually read them was my job for years. Inside the system, I never saw the pretty version. I saw the extracted text: names, summaries, and bullet points already stripped down to whatever the parser could pull out.
Some came through clean. Others came through with a name missing, a summary paragraph turned to noise, or a skills section that just wasn’t there. A broken resume was one more reason to move on to the next candidate before I ever weighed their qualifications.
None of them had any idea. On their own screen, the file still looked perfect.
This is the part of resume advice nobody finds interesting, which is exactly why it wrecks people. Nobody gets denied an interview because their bullet points weren’t compelling enough for a piece of parsing software. They get denied because the software never extracted the bullet points at all.
I’ve already written about the structural fundamentals that keep a resume readable: single column, standard headings, reverse-chronological order. This is the fast version of the part that trips people up even when they’ve gotten all of that right: the font itself, and the small formatting choices sitting on top of it.
Font choice: use what the operating system already has
| Do | Don’t |
|---|---|
| Use Arial, Calibri, Helvetica, Tahoma, or Verdana | Use a font downloaded from a type foundry’s website |
| Use Georgia, Cambria, Garamond, or Palatino for serif | Convert text to outlines or curves for a “cleaner” look |
| Export the PDF directly from Word or Google Docs | Print to PDF from a browser or route it through a design tool |
| Select and copy a line of text before you submit it | Assume it’s fine because it looks right on your screen |
Every parser extracts text by matching character shapes to a known encoding table. Standard fonts, the ones already installed on every Mac and Windows machine, are in that table. A font you downloaded from a type foundry’s website and installed yourself might not be, especially once it’s embedded in a PDF export.
Jobscan’s own formatting guidance names the fonts worth sticking to: Arial, Calibri, Helvetica, Tahoma, and Verdana on the sans-serif side, Cambria, Garamond, Georgia, and Palatino if you want serif. Every one of those ships with the operating system. None of them require the reader, human or parser, to have anything special installed to render correctly.
The failure mode when you stray from that list isn’t subtle once you know what to look for. Jobscan describes it plainly: custom fonts and decorative glyphs “often turn into gibberish or ‘[NULL]’ during the parsing process,” and a summary paragraph can come out looking like a broken encrypted message. That’s the exact shape of failure I saw over and over running ATS screens: a name gone, a summary paragraph turned to noise.
The visual design survived the export. The actual text underneath it didn’t.
How you export matters as much as which font you picked. Save your PDF directly from the source document (Word, Google Docs, whatever you built it in) rather than printing it to PDF from a browser or routing it through a design tool, and never let an export option turn your text into outlines or curves for a “cleaner” look.
Outlined text draws perfectly and reads as nothing, because at that point it’s no longer text at all, just a shape shaped like text. If you’re ever unsure whether a specific export preserved a real text layer, the fastest check is trying to select and copy a line of it.
If your cursor can’t grab individual words, neither can a parser. My free ATS resume checker runs that same extractability check automatically, along with a scan for the header, footer, and encoding problems below, if you’d rather not do it by hand every time.
This cuts against a real design instinct, and I feel it too. A distinctive font is doing real work on a portfolio site or a business card.
On a resume headed for an ATS, distinctive is the liability. Save the typographic personality for the document a human opens directly.
Headers, footers, and text boxes: assume they get skipped
Here’s what that looks like on the page. Hover or tap the marked zones below to see which ones a parser actually reads.
Interactive mockup — hover or tap a marked zone to see whether it reaches a parser
A resume built in Word or Canva often puts your name and contact line in the document’s header, because visually, that’s where a header belongs. Structurally, a header is a separate layer from the body text, and a lot of ATS parsers never read that layer at all.
Jobscan’s guidance on this is direct: “Many ATS ‘scrapers’ ignore information tucked away in these layers. Keep your vital contact details and skills in the main body of the document.”
The same applies to text boxes, a common way design tools let you place a sidebar or a pull quote anywhere on the page. If content lives inside a text box rather than the main document flow, treat it as invisible to a parser until proven otherwise.
The fix costs nothing: put your name, email, phone number, and location in a normal line of body text at the top of the page. It’ll look identical to a human reader. It’ll actually exist to a parser.
Icons and graphics: type the word instead of drawing it
Here’s the same failure mode, dressed up as design flourish instead of layout. Hover or tap a marked zone to see what a parser actually gets from each one.
Interactive mockup — hover or tap a marked zone to see what a parser actually extracts
Skill-level bar graphs, a little phone glyph next to your number, a row of dots showing how well you know Figma: all of it reads as an image or a vector shape to a parser. Jobscan’s assessment is blunt: “charts or images (like skill level bar graphs) are unreadable.” Multi-column layouts built around these graphics compound the problem, because the parser can end up reading “the left column, then the right, but mix the sentences together like a deck of cards.”
What matters is what’s doing the communicating.
If a phone icon is standing in for the word “Phone,” type the word. If a five-dot rating is standing in for “Advanced,” write “Advanced.”
A parser can’t infer meaning from a shape. It can only extract what’s actually written as text, so anything that matters has to exist as text somewhere on the page.
The same logic covers a few things people don’t think of as “graphics” at all. A horizontal rule made from a drawn line object instead of a paragraph border.
A profile photo, which most U.S. employers don’t want on a resume for legal reasons on top of the parsing risk. Special bullet characters copied in from somewhere other than your word processor’s own bullet list, which occasionally paste in as an embedded image glyph instead of a real Unicode character.
None of these look unusual to a human eye. Every one of them is a small bet that a parser will treat a picture the way you intended, and that bet loses often enough to not be worth taking.
Reflective Coda
The pattern across all three of these is the same. A parser rewards plain text in the main body of the document, in a font it already recognizes. Every design choice that would read as thoughtful on a portfolio site, a distinctive typeface, a clean header treatment, a small icon doing double duty as decoration and information, is invisible or actively harmful the moment a parser is the first reader instead of a person.
It’s an argument for knowing which document gets read by which audience, and formatting accordingly. If you’d rather not think through every one of these choices from scratch, I’ve already built 11 free templates that follow all of this by default, so you can spend your attention on what you actually wrote instead of whether the font you picked is quietly erasing it.
Somewhere out there, a qualified person is still convinced their resume looks great, because on their screen, it does. The version that actually reaches a parser is a different document, and they won’t know it unless something makes them check.
