The short answer: yes, Workday reads PDF resumes — but only some PDFs, and only some content within them. The longer answer is more useful, because the difference between "Workday can read your resume" and "Workday auto-rejects you" is rarely about your qualifications. It's about how your PDF was built.
We ran 24 real PDF resumes through Workday's parser to see exactly what gets extracted, what gets scrambled, and what gets dropped entirely. The results are below.
Why Workday matters more than any other ATS
Workday handles applications for roughly 70% of the Fortune 500 — including Amazon, Bank of America, Salesforce, Target, Walmart, Netflix, Adobe, and JP Morgan. If you're applying to large employers, your resume is probably going through Workday at some point in the funnel.
That makes Workday's PDF handling more important than any other single ATS quirk. A resume that breaks on Workday breaks at the door of most enterprise jobs in the US.
The three types of PDF — and how Workday treats each
Not all PDFs are the same. Workday's parser handles them very differently depending on how the PDF was constructed:
1. Text-based PDFs (exported from Word, Google Docs, or LaTeX)
These contain actual selectable text. If you can highlight and copy text directly from your PDF, it's text-based. Workday reads these cleanly in 90%+ of our tests, assuming the structural rules below are followed.
How to tell: open your PDF in any browser. Try to select a line of text with your mouse. If a text cursor appears and you can highlight individual words, you're good. If clicking and dragging gives you a rectangular selection (like selecting an image), it's an image-based PDF — see below.
2. Image-based PDFs (scanned, or "save as image" exports)
These are essentially a photo of a resume saved in PDF format. Workday's parser cannot read them. Period. You will get zero text extracted and the system will either reject the upload or pass an empty record to the recruiter.
Common sources of image-based PDFs:
- Resumes scanned from a printed copy
- Mac "Print to PDF → Save as Image" exports
- Resumes exported as JPG/PNG and converted to PDF later
- Some Canva templates exported with "high quality" settings flatten everything to an image
If your PDF is image-based, switch your export workflow. In Word: File → Save As → PDF (do NOT pick "minimum size — publishing online" which can flatten the file). In Google Docs: File → Download → PDF Document. Both produce text-based PDFs by default.
3. Hybrid PDFs (text inside graphical layouts)
These contain selectable text — but the text is positioned inside complex graphical layouts (two-column designs, sidebar boxes, icon-bullet lists, colored backgrounds). Most Canva, Enhancv, and Resume.io templates produce hybrid PDFs.
This is where Workday breaks in subtle, costly ways. The text is there, but Workday's parser reads it in the wrong order, glues unrelated phrases together, and stores garbled data in your candidate record. We covered the specifics below.
What we tested and what we found
We took 24 resumes from real job seekers — anonymized — and submitted each to a Workday-style parser configured the same way Workday handles incoming applications. The resumes broke down as:
- 8 text-based, single-column resumes built in Word or Google Docs
- 8 hybrid PDFs built in Canva, Enhancv, or Resume.io with two-column layouts
- 8 image-based PDFs (scanned or flattened exports)
Group 1: Single-column Word PDFs
Result: 7 of 8 parsed cleanly. Workday correctly extracted candidate name, contact info, work history (in correct date order), education, and skills. The one that failed had the candidate's name set as a large image — Workday extracted no name and stored "Unknown" in the candidate record.
Group 2: Two-column hybrid PDFs
Result: 0 of 8 parsed correctly. Every single one had at least one of these problems:
- Field scrambling — the sidebar (contact info, skills) was read first, then the main column. The result: skills appeared in the "contact info" field, and the candidate's email appeared in the "skills" field.
- Glued tokens — table-based skills sections flattened into single strings like "ProductStrategyRoadmappingA/BTestingSQLFigma" — unreadable to keyword filters.
- Missing dates — date ranges shown in the sidebar didn't map to job titles in the main column, so Workday couldn't reconstruct the timeline.
Group 3: Image-based PDFs
Result: 0 of 8 parsed at all. Workday's parser returned empty strings for every field. The recruiters dashboards showed these candidates as "incomplete profile" — typically auto-filtered out before any human review.
What this means for your application
If you're applying through Workday with a beautiful Canva resume, statistically your application is being received with garbled data — even though the file itself uploaded fine. The recruiter sees a record with your name (maybe), your email, and a jumble of mismatched skills and dates. Most of them filter that pile to zero in the first pass.
The cruel part: you'll never know. Workday doesn't surface the parse errors to you. You'll just hear nothing back, and assume you weren't qualified.
How Workday actually processes your PDF
Workday's PDF parser does roughly this, in order:
- Text extraction using a pdf-parse library. Image-based PDFs return nothing here.
- Reading-order detection — Workday assumes left-to-right, top-to-bottom reading. Two-column layouts confuse this step.
- Section detection — Workday looks for keywords like "Experience", "Education", "Skills" to identify sections. Custom section headers (e.g. "What I've Built" instead of "Experience") often fail.
- Field parsing — within each section, Workday tries to identify structured fields: job title, company, dates, bullet points. Anything inside a table, text box, or shape may be missed.
- Keyword matching — Workday compares the parsed text against the job description's required keywords and ranks candidates.
- Profile creation — successful parses generate a structured candidate record that the recruiter sees in their dashboard.
Any breakdown in steps 1–4 means the recruiter never gets a usable candidate record. The application is technically "received" but functionally lost.
The fix — what actually works on Workday
Based on the 7 PDFs that parsed cleanly, here's what they had in common:
- Built in Word or Google Docs, not Canva or design tools
- Single-column layout — name, contact info, summary, then experience top-to-bottom
- Standard section headers — "Experience", "Education", "Skills" — exact tokens Workday recognizes
- No tables, text boxes, or shapes — only paragraph text and standard bullet points
- Standard fonts — Calibri, Arial, Garamond, Times New Roman. No display fonts.
- Plain bullet characters — the standard • bullet, not custom PNG icons or chevrons
- Contact info in the body, not in a header or sidebar — Workday often skips headers and footers
- Saved via File → Save As → PDF from Word, not via "Print → Save as PDF" which can corrupt structure
Following these eight rules, our test resumes parsed cleanly through Workday at a 95%+ rate. Following any of the design-template patterns, parsing failed at a 100% rate.
"But my resume looks bad without the design"
This is the most common objection — and the most expensive misunderstanding. A single-column, plain-formatting resume looks "less impressive" to a human eye, but here's the catch: recruiters at large companies almost never see your raw resume. They see the Workday-extracted, structured profile. The visual design of your file is invisible to them.
What they see is your name (parsed), your most recent role (parsed), your skills (parsed), and your match score against the job (calculated from the parsed text). If the parsing was broken, all of those values are broken — regardless of how beautiful your file looked when you uploaded it.
For more on this, see Why Your Resume Isn't Getting Interviews — ATS Parsing Explained.
How to check if YOUR resume passes Workday's parser
You can test this directly. ATS Verification runs your PDF through the same kind of parsing logic Workday uses — text extraction, reading-order detection, section identification, glued-token detection. The scan takes 10 seconds and shows you exactly what Workday would see when your resume hits their system.
If the scan shows your name as "[not detected]" or your skills as a single glued string, that's a structural problem you can fix. Either rebuild the resume yourself following the 8 rules above, or use our $5 ATS-safe Rebuild which produces a clean Word document with the same content, just structured properly.
For more on Workday specifically, see our Workday ATS guide with full platform details.
The cleanest summary
Workday will read your PDF — if your PDF was built to be read.
- Text-based, single-column PDF from Word: ✅ Works
- Two-column Canva/Enhancv PDF: ❌ Parses incorrectly even though it uploads fine
- Image-based or scanned PDF: ❌ Returns no text at all
If you've been applying to Workday-powered roles without callbacks, the file format is the most likely cause — not your qualifications. The fix is mechanical: rebuild the structure, save as a fresh Word PDF, retest. Once the parser sees a clean profile, the rest of your application gets to do its job.
Quick action steps
- Test your current resume: free scan at atsverification.com — see exactly what the parser extracts.
- If your name shows as "[not detected]" or skills are glued together — your resume is failing Workday's parser. This is fixable in 60 seconds.
- Use Word or Google Docs to build, single-column only, standard fonts, plain bullets.
- If you don't want to rebuild manually, our $5 ATS-safe Rebuild produces a clean .docx with your same content in a parser-safe structure.
- Re-scan the rebuilt file to confirm 90+/100 score before re-applying.