Accented characters on a resume break ATS parsing when the file loses UTF-8 encoding—turning José into Jos?, Renée into Renee, or Müller into M ller—so Workday, Greenhouse, and Taleo autofill the wrong name, recruiters cannot search your profile, and background checks may not match your legal ID unless you test the upload and fix encoding before you click Apply.
This is not the same problem as a hyphenated surname splitting across first/last fields . Diacritics fail at the character-encoding layer: the parser never receives é or ñ as readable text. US employers increasingly hire international graduates and bilingual workers, but many application stacks still assume ASCII names. The fix is part typography, part file export, and part how you mirror legal spelling in form fields.
Definition: accented-character ATS failure
An accented-character ATS failure happens when diacritic marks (é, ñ, ü, ç, ã, ø) in your name, school, or employer are dropped, replaced with ? or □, or split into separate tokens during resume import—so structured name fields, keyword search, and recruiter inbox filters no longer match the human-readable resume you uploaded.
- Save the resume as UTF-8 DOCX or a text-selectable PDF with embedded fonts.
- Copy-paste all text into a plain editor; confirm every accent survives.
- Search the PDF for each special character (Ctrl/Cmd+F).
- Upload to the employer ATS and compare autofill name fields line by line.
- Add one ASCII alias in parentheses only if mangling persists.
- Enter legal spelling in government-ID and background-check fields.
- Run an ATS check on contact-block extraction before final submit.
Key Takeaways
- Encoding failures—not employer bias—usually cause ? and □ in name fields
- Image PDFs and Canva exports are the most common accent killers
- One consistent ASCII alias helps search without erasing legal spelling
- Workday, Greenhouse, Taleo, and iCIMS each need a fresh upload test
- Fix the file first; only then simplify characters for autofill
How accented characters break ATS name and contact parsing
After you upload a resume, the ATS extracts plain text and maps tokens into structured fields: first name, last name, email, phone, education, employers. That pipeline assumes each character in the file maps to a Unicode code point the database can store. When the file uses a custom display font without embedding, exports through a graphics tool, or saves in a legacy Windows encoding, the importer receives replacement characters instead of é or ñ.
Recruiters then search candidate pools with ASCII keyboard input. A profile stored as "Jos?" will not match a search for José. Worse, some systems treat ? as a wildcard or discard the row entirely. The Unicode Consortium's guidance on combining characters explains why decomposed accents (base letter + combining mark) sometimes render differently across PDF readers than precomposed characters (single code point)—both are valid Unicode, but parsers handle them inconsistently.
Accents in university names (Université de Montréal), prior employers (Nestlé, São Paulo office), or certifications (licenciatura titles) fail the same way. A missing tilde on "Espanol" is not just a typo; it can drop your bilingual keyword match when the posting requires Spanish fluency.
Common Mistake: assuming the application's name fields fix a bad file—recruiters often see the parsed profile first, and many systems never re-sync after you manually correct autofill.
Which US ATS platforms garble é, ñ, and ü most often?
Platform behavior depends on instance age, employer configuration, and your file—not just the logo on the career site. The table summarizes what practitioners see most on US applications in 2026; your mileage varies by company.
| Platform | Typical accent behavior | Most common failure mode |
|---|---|---|
| Workday | UTF-8 usually fine from clean DOCX/text PDF; autofill sensitive to layout | Name split across columns; accents lost when PDF is image-based |
| Greenhouse | Strong Unicode support on current cloud instances | Design-tool PDFs; accents in header graphics invisible to parser |
| Taleo (Oracle) | Mixed; legacy enterprise configs strip diacritics more often | Autofill replaces ñ/ü with ASCII or blank; search misses legal spelling |
| iCIMS | Generally preserves Latin accents in extractable text | Two-column templates separate accented name from email block |
| ADP Recruiting | UTF-8 OK when file is clean; form fields may enforce ASCII | Manual name fields reject characters that parsed resume contained |
For layout issues that compound accent problems—sidebar names, table headers—see Workday resume format rules for 2026 and how ATS reads contact info . Encoding and layout failures often show up together.
Quick Check: if Ctrl/Cmd+F cannot find ñ in your PDF, no ATS instance—not even Greenhouse on its best day—can search that character in your profile.
Legal name vs. searchable alias: what US employers actually match
Your resume should display the name you use professionally and that matches government ID where possible. US background checks and I-9 workflows compare against documents that may or may not include diacritics depending on issuance country. SHRM's guidance on name consistency in hiring records stresses aligning payroll, ATS, and ID—not forcing applicants to anglicize names, but ensuring records reconcile.
A practical pattern when autofill mangles accents:
- Resume header: André Silva (Andre Silva) — legal form first, ASCII alias once in parentheses
- Application first/last fields: enter characters the form accepts; if the form blocks ü, use ue in the field but keep André on the resume file
- Email and LinkedIn: match the primary accented spelling so humans recognize you
- Cover letter sign-off: use the same primary spelling as the resume header
Do not maintain three different spellings across documents. Recruiters searching "Andre" should still find you because of the parenthetical alias, while HR sees André on the official resume attachment.
Pro Tip: international applicants targeting US roles should read international candidate resume tips for US ATS alongside this guide—phone format and address lines fail parsing for the same encoding reasons accents do.
PDF vs. DOCX: where UTF-8 encoding fails before upload
File type matters less than how the file was produced. A DOCX saved from Word with standard fonts (Calibri, Arial, Times New Roman) almost always carries UTF-8 text. A PDF printed from Canva, Figma, or Photoshop is often a flat image—even if you see perfect accents on screen.
High-risk export paths
- Canva "Share → PDF Print" with decorative name typography
- Mac Preview "Export as PDF" from a screenshot
- Google Docs → PDF when using non-Google fonts not embedded in export
- LaTeX PDFs with custom font packages unless you verify text extraction
- Scanned paper resumes OCR'd with low confidence on accented glyphs
Safer export paths
- Word "Save As → DOCX" with standard fonts; embed fonts on PDF export if offered
- Google Docs → Download → Microsoft Word (.docx), then verify accents in Word
- Adobe Acrobat "Save As Other → Reduced Size PDF" only after text-select test passes
Mid-article diagnostic: run your file through HireFlow's ATS resume checker to confirm the contact block—including accented names—extracts as readable text before you upload to Workday or Taleo.
Common Mistake: switching to DOCX to "fix" accents while keeping a two-column Canva layout—encoding improves nothing if your name sits in a text box the parser reads last.
Before/after contact blocks when accents break parsing
These rewrites fix extraction without hiding your legal name. Each pair shows a failure mode and a parser-safe alternative recruiters still recognize.
Before: JOSÉ MARTÍNEZ (rendered in a Canva script font, PDF image layer)
After: José Martínez (Jose Martinez) · [email protected] · (512) 555-0142 · Austin, TX — Calibri 11 pt, single-column body text
Before: Zoë Müller | zoë@company.com (ë and ü become Zo? M ller in Taleo autofill)
After: Zoë Müller (Zoe Mueller) | [email protected] — exported DOCX from Word, accents verified via copy-paste test
Before: Education: Université de Montréal — name appears as Universit de Montr al in Greenhouse extract
After: Université de Montréal (University of Montreal), B.A. Economics — accent marks preserved in UTF-8 DOCX; English alias aids US recruiter search
| Garbled output | Likely cause | Fix |
|---|---|---|
| Jos? | Non-embedded font / image PDF | Re-export DOCX; search PDF for é |
| M ller | Combining diacritic dropped | Retype ü; use precomposed character |
| Empty first name | Name in header/footer or text box | Move to body; single-column layout |
| Na\u00efve split | Parser treats ï as delimiter | Parenthetical ASCII alias once |
Key Takeaway: fix typography and encoding first; add a single ASCII alias only when autofill still fails after a clean export.
Character-specific notes: ñ, ü, ç, ã, and non-Latin scripts
Spanish ñ and Portuguese ã are single code points—do not substitute "n~" or "a~" manually; some parsers treat the tilde as punctuation and split the token. German ü, ö, ä are often replaced with ue, oe, ae in forms that block extended Latin—acceptable in Taleo first-name boxes if the resume PDF still shows ü.
French ç and é appear frequently in Québec and European employer names on US resumes. Czech and Polish diacritics (ř, ł, ś) fail more often in older ADP instances. Greek or Cyrillic characters in names may require romanization on the resume line (Δημήτριος → Dimitrios) while keeping original script in a cover letter if culturally appropriate—the ATS keyword layer is still predominantly Latin.
The U.S. Bureau of Labor Statistics does not track parsing behavior, but O*NET occupational profiles list foreign-language requirements for many US roles—bilingual keywords with correct accents (Español nativo, français courant) can still matter for match scores when extractable.
Pro Tip: on Windows, use the US-International keyboard or Unicode hex input to type accents directly instead of copying from web pages—pasted characters sometimes carry hidden formatting that breaks DOCX XML.
Pre-submit checklist for accented names on US applications
- Resume saved as UTF-8 DOCX or verified text PDF—not Canva image export.
- Standard font (Calibri, Arial, Helvetica, Times) with accents typed or pasted cleanly.
- Copy-paste into Notepad/TextEdit plain text: all diacritics visible.
- Ctrl/Cmd+F search in PDF for é, ñ, ü, ç—each returns a match.
- Name, email, phone in main body column—not header/footer sidebar.
- One optional ASCII alias in parentheses if prior uploads garbled autofill.
- Upload to employer site; compare every autofill field to resume header.
- Legal spelling entered in background-check and I-9 fields when forms allow Unicode.
- ATS checker run on contact extraction before final Apply click.
Quick Check: if only your email extracts and your accented name does not, the parser never reached the header block—layout fix, not character swap, is the next step.
Accented characters belong on your resume when that is your legal and professional name. The work is making sure UTF-8 text survives export, upload, and autofill on Workday, Greenhouse, Taleo, and iCIMS—not stripping your identity to appease a broken parser.
Run the copy-paste test, fix the file, verify autofill, then confirm extraction with HireFlow's free ATS resume checker before you submit. Correct encoding once and every future application inherits the fix.
Frequently asked questions
Keep your legal name with accents on the resume file, but verify how each employer's ATS displays it after upload. If Workday or Taleo replaces José with Jos? or splits the string, add a plain-ASCII version in parentheses once—José García (Jose Garcia)—or mirror the exact spelling in the application's name fields. Never drop accents entirely without checking whether background checks require a legal-name match.
Modern systems built on UTF-8 databases generally support common Latin diacritics (é, ñ, ü, ç, ã). Support breaks at the file layer: scanned PDFs, legacy Taleo instances, custom fonts, and copy-paste from certain design tools strip or mangle encoding before the ATS ever sees your name. The platform may support Unicode while your specific upload does not.
Question marks and empty boxes mean the importer lost character encoding—often a non-embedded font, a PDF exported as images, or a DOCX saved in an older encoding. Workday's candidate-profile importer reads whatever text the file actually contains; garbled symbols are almost always a document problem, not Workday rejecting your name.
Yes, when done once and consistently. A single line like Renée Dubois (Renee Dubois) helps keyword search and recruiter lookup without hiding your legal spelling. Do not alternate spellings across sections—header says José, email signature says Jose, LinkedIn says Josè. Pick one primary form and one searchable alias, then use them the same way on every application.
Only text-based PDFs with embedded Unicode fonts do. Canva, Photoshop, or print-to-PDF exports often flatten names into images, so parsers return nothing or gibberish. Export from Word or Google Docs, then run Ctrl/Cmd+F for each accented letter in the PDF before uploading to Greenhouse, iCIMS, or Workday.
It can. HRIS and background vendors match against government IDs and payroll records, which usually carry legal diacritics or romanized equivalents depending on the document. If the ATS garbles your name, fix the file encoding first; if you must simplify for parsing, use the legal accented form on the resume and enter the exact legal spelling in required application fields.
Copy-paste the full resume into a plain-text editor and confirm accents survive, search the PDF for each special character with Ctrl/Cmd+F, upload to a test application when possible, and compare every autofill name field to your resume header. An ATS checker that flags contact-block extraction helps catch issues before a live submission.
Greenhouse typically preserves UTF-8 text from clean DOCX and text PDF uploads on current instances. Older Taleo builds at large enterprises are more prone to stripping diacritics in autofill and search. iCIMS and ADP Recruiting fall in between—encoding usually works, but sidebar layouts can separate accented names from email lines. Test per employer, not per brand rumor.