Should you put icons on your resume?

Resume icons are safe only alongside a text label, and only in the header — the condition that decides it is the submission channel. A file uploaded to an application form gets parsed; one emailed to a named person gets read. Do not let an icon replace Phone or Email, and never put one in a section heading.

• A parser reads text, so an icon carries no label no matter how obvious the meaning looks to you
• Pair every icon with its word: "Phone: (555) 123-4567", not a glyph followed by a number
• A section heading is where a parser decides what the content below it is; an icon there risks the whole section
• Rating bars, stars and progress rings contain no text and state nothing a reader can act on
• Two files is the workable answer: a plain one for application forms, a designed one for a portfolio or an emailed introduction
• The plain-text test is the only check you can run yourself, and it is a proxy — no tool shows you what a specific employer's parser did with your file

Can a parser read an icon?​

It reads whatever text the icon is made of, which is usually none.

Three things get called an icon and they fail differently. An image icon — a small PNG or SVG placed in the document — contains no characters at all, so extraction skips it and nothing takes its place. An icon font draws a symbol from a glyph mapped to some character in a private range; extraction may return that raw character, an empty string, or a substitution, none of which is the word you meant. A Unicode symbol pasted in as text is the likeliest of the three to survive, and it survives as a symbol, which is still not a label.

What matters is what happens next. A parser is trying to fill fields — this is the phone number, this is the email, this is the employer — and it uses nearby words as evidence. Replace "Phone" with a handset glyph and the number loses its label, so the parser guesses from shape alone. Sometimes it guesses right. Sometimes the value lands in the wrong field or none, and the record it built for you has no way to reach you in it.

That is the whole risk, stated without inflation: the icon is not offensive to the software, it is invisible, and it takes the label with it. Which is why the advice always lands in the same place — keep the word, and let the icon sit beside it if you want it there.

Where icons are genuinely safe​

Two conditions, and you need both.

The icon is decoration next to a label, not a replacement for one. Write Phone: (555) 123-4567 and put a handset beside it if you like the look. The line survives extraction with its meaning intact, because the meaning was never in the picture.

The file is not being parsed. A resume emailed straight to a hiring manager, handed over at an interview, or posted on your own site is read by a person. One uploaded to an application form goes through intake first. That is the condition that flips the whole answer: same document, different channel, different rules. When you do not know which applies — and on a company careers page you usually do not — assume it is being parsed.

Design-led fields are the exception people reach for, and it is weaker than it looks. A design portfolio is judged on the portfolio; decoration on the resume is not what wins that argument, and the application form in front of it behaves as it does for everyone else.

Which icon habits break a resume outright​

Icons in section headings. The worst case in the set. Headings are how a parser files everything beneath them, so a briefcase glyph where the words "Work Experience" should be puts your entire employment history at risk of landing nowhere. Keep headings as plain text. If a whole section can go missing without you seeing it, that is a parsing failure, and the wider set of them is covered in why an ATS rejects a resume.

Symbols inside a contact value. An at-sign glyph before an email address, or a pin before a location, can merge with the value or drop out of it. Contact details are the fields you can least afford to lose, so give them the least decoration.

Light grey icons on white. Low contrast is hard to read on screen, worse in greyscale print, and invisible to anyone with reduced vision. If an element has to be there, it has to be legible.

Decorative bullets. Custom symbols, checkmarks and arrows in place of standard bullets are the same problem at smaller scale. Use • or a hyphen.

Density. Once every line has a glyph, none of them is doing the emphasis job they were added for.

Do skill rating bars ever help?​

No, and this one is worth separating from the parsing argument, because rating bars fail on their own terms.

A bar showing four fifths beside "Python" contains no text, so extraction gets a skill name with nothing attached to it. But even for the person reading it, four fifths of what? You set the scale, you scored yourself against it, and nobody else can calibrate it. Two candidates who write 4/5 next to the same skill may be a year apart in experience.

Replace it with the thing the bar was trying to imply. "Python: four years, primary language on two production services" is longer, extracts cleanly, and can be checked. The same reasoning applies to the block at the top of a resume, where a scored self-assessment is weaker than a short written claim — that is the case for a summary of qualifications instead.

Should you keep two versions?​

Yes, if you have a real use for the second one. Keep a plain file as the default for everything you upload, and a designed file for the situations where a person definitely opens it: an emailed introduction, a networking follow-up, a printed copy at an interview, your own site.

What must not differ is the content. Same employers, same dates, same numbers, same claims. Two files that disagree is a problem you eventually have to explain, and the drift happens quietly, when you edit one and forget the other. If maintaining both is more admin than the designed version earns you, keep one plain file — that is a perfectly good answer and the one most people should take.

In FluxResume the formatting layer lives in the preview controls on Documents: template, page size, accent colour, font and date style, with Download exporting a PDF. Two constraints come with that. PDF is the only documented download format, so a posting demanding .docx means converting the file yourself. And no documented control reports whether a given design element parsed — the plain-text test is still yours to run. For how a file reads against one specific posting rather than in general, that comparison lives on Job Based Resume. The template gallery is at https://fluxresume.io/resume-templates/.

Common questions​

Do icons look unprofessional?​

It depends on the field, and the split is roughly conservative against everything else. Finance, law, government, medicine and academia expect a plain document, and decoration reads as unfamiliarity with the convention rather than as personality. Product, design and marketing are more relaxed. When you are unsure, plain is the safer default, because a plain resume never reads as a mistake in either group.

Are Unicode symbols safer than image icons?​

Slightly, and not enough to change the advice. A Unicode symbol is real text, so it usually survives extraction where an image icon disappears entirely — but what survives is a symbol, not a label, and it can still substitute or render as a box depending on the font available. The rule is unchanged: keep the word, and treat the symbol as optional decoration next to it.

Can I use icons if I email the resume directly?​

Yes, with one caveat. A file sent to a named person is read by that person, so parsing is not the constraint. The caveat is that emailed resumes are often forwarded into an applicant tracking system by the recruiter, at which point the file gets parsed after all. Keeping text labels beside any icon covers both paths, so you never have to guess which one your file took.

What about a photo?​

Leave it off for US applications. It adds no information a hiring decision should turn on, and it is a large non-text element in a document being read for text, so it costs you space and gains you nothing. Some markets outside the US still expect a photo, so follow the local convention where you are applying — that is a regional norm rather than a formatting preference, and the posting's country decides it.

Originally published June 2025. Reviewed and rewritten for FluxResume in August 2026.