Why Icons and Graphics Hurt ATS

9 min read

Your resume can look perfect in preview and still break on upload. The portal doesn't admire your layout. It pulls characters in a line and tries to map them into fields for employer, title, and dates.

That's why a template with phone icons and colored section tabs feels modern on your laptop and ancient inside Workday. The system never saw the icons. It saw holes where your number should be.

Check your resume for free on the exact PDF or DOCX you plan to submit. Fixing keywords on top of a graphic header is like repainting a car with a bent frame.

Below are before-and-after swaps for the four decoration patterns I see most often: contact icon rows, skill bars, infographic sidebars, and chart blocks. You can paste the plain versions tonight.

What the parser keeps when graphics go in

Parsers are greedy for plain characters. They grab letters, digits, and basic punctuation. Anything drawn as a shape, icon font, or embedded picture sits outside that menu.

When a contact row uses a handset glyph instead of the word Phone, many systems drop the digits entirely. The recruiter view shows a blank phone field while your PDF still looks fine.

Skill infographics are worse because they sit in sidebars. Greenhouse and Lever often read left column first. Your star ratings for Python may appear above your university name while your last employer vanishes from the timeline grid.

Charts and progress bars add no searchable text. A bar filled to eighty percent does not become eighty percent in the database. It becomes nothing, and the bullet beside it may not attach to a job block if the bar lived in a floating text box.

I've screened files where the candidate's email parsed correctly but every job title was empty because a colored band sat between contact and experience. The human PDF told a clear story. The ATS row looked like a student with no work history.

This is not about one vendor being picky. Taleo, iCIMS, Workday, and Greenhouse all depend on text extraction before a human sorts. Decoration that does not survive Notepad will not survive the upload.

If you're unsure whether an element counts as graphics, select all text and paste into Notepad. Anything that disappears or turns into a question mark was never real text. Fix that block before you tailor keywords for the next req.

For a wider list of ignored elements, read what ATS ignores on your resume and compare with the formatting swaps below.

Why icons and graphics hurt ATS: before-and-after swaps

Contact row with icons

Before: A row of envelope, phone, map pin, and globe icons with tiny text tucked beside each glyph.
After: Four plain lines at the top: city and state, phone on one line, email on one line, LinkedIn URL spelled out with the https prefix.

Parsers map the first lines to name and contact fields. Icons push text into odd columns so city lands in the email slot. Words beat symbols every time.

Skill bars and star ratings

Before: A sidebar table with Excel, SQL, and Tableau shown as five-star rows or shaded bars.
After: A short Skills line with comma-separated tools, plus one bullet under your analyst role: Built weekly revenue flash in Excel and Tableau for twelve stakeholders.

The bullet ties the tool to scope. Search still hits Excel and Tableau, and humans see where you used them.

Infographic two-column header

Before: Name and summary left, photo circle and icon stack right, experience starting mid-page in a narrow center column.
After: Single column: name, contact, three-line summary, then experience with employer, title, and Mon YYYY dates each on their own line.

Photos are optional for US corporate roles and risky for parsing everywhere. Drop the image block entirely for ATS uploads.

Mini chart in the summary

Before: A doughnut chart showing time split across projects above the summary paragraph.
After: One summary sentence with scope: Operations coordinator supporting three sites and a forty-person field roster.

Counts in prose parse like any other word. Charts do not.

Copy-paste block: plain contact strip

[Full name]
[City], [State] | [phone with area code]
[[email protected]]
LinkedIn: https://www.linkedin.com/in/[handle]

Summary
[Two sentences on role focus and scope, no icons or text boxes]

Experience
[Employer name]
[Job title] | [Mon YYYY] – [Mon YYYY or Present]
• [Bullet with tool names as words, not icons]
              

Run the same test after each swap: select all text in your export, paste into Notepad, and read in order. If Skills appears before your current employer, move sections until the story reads chronologically.

Wingding bullets are graphics too. Switch to standard round bullets or hyphens. Custom bullet glyphs often paste as question marks in Notepad.

Pair layout fixes with formatting errors that break ATS parsing so you are not fighting the same upload twice with different templates.

When deleting icons is not enough

Hidden text boxes survive export. You removed visible stars but the template still wraps your summary in a box object. Copy into Notepad. If the summary is missing, rebuild that section in the main document body.

Tables used for alignment look like tables to the parser. A contact table with invisible borders still reads cells out of order. Use line breaks instead.

Before: Section titles as colored shapes with white text.
After: The word Experience in bold on its own line, black text, no background rectangle.

Before: Watermark logo behind the page.
After: No watermark. Type employer names in bullets, not as brand images.

Emoji checkmarks in bullets fail the same way icons do. Use words: Reduced, Built, Led. Save creativity for work samples you link, not glyphs in the file.

PDF security locks and phone scans turn the upload into a picture. Parsers cannot read pictures. Export a text PDF from Word or Docs.

This will not fix applying ten levels above your scope. It stops a qualified file from looking empty because decoration ate the experience block.

Test the export you will upload

Layout work stays guesswork until you run the same bytes through a checker. You want scrambled order and missing headings flagged on your machine, not after a coordinator closes the req.

After you flatten the file, paste the posting into score your job match so keywords land in experience bullets instead of a dead sidebar.

Run the free ATS checker on the PDF or DOCX you plan to attach. Fix structure first, then tune language.

Keep two versions if you want: a designed PDF for networking and a plain file for every portal. Muscle memory at midnight is how the pretty one gets uploaded by mistake.

Plain file checklist before you apply again

Icons and graphics hurt ATS when they steal reading order from your experience block. Subtraction is the fix: one column, word labels, standard bullets, text-only contact lines.

• Notepad read matches the story you intend.
• No bars, stars, photos, or logo bands in the upload file.
• Tools named inside bullets under the right employer.
• Checker pass on the exact attachment.

Generate a cover letter when the role asks for one, then run a free ATS check on both files so names and titles match.

Job searching is draining enough without a silent parser failure. A boring export is how you make sure recruiters judge your work history, not your template.