11 min read
You're not alone if Workable threw unsupported file, upload failed, or a green checkmark with half your jobs missing from preview. That panic hits US startup and mid-market reqs constantly. Most Workable resume upload issues aren't mysterious server bugs. They're file type limits, oversized exports, or layouts the parser can't read in order while the attachment icon still looks healthy.
Check your resume for free after you fix the file, not before you re-upload the same PDF ten times. If Notepad paste shows Skills before your current employer, Workable already lost your Experience block even when the upload succeeded.
Below: five procedural steps with before-and-after file fixes, two edge cases, mistake patterns, and a copy-paste filename convention. You don't need a new design subscription. You need a plain export recruiters can search. Job searching's already draining. You won't fix a layout problem by switching browsers alone.
Quick Wins
- Rename the file First-Last-Resume.pdf with no symbols in the name.
- Export single-column PDF from Word at under five megabytes.
- Paste PDF text into Notepad and confirm employers read top to bottom.
- Open Workable parsed preview before you fill knockout questions.
What happens when Workable accepts your resume
Workable stores the attachment and runs an import pass that tries to map employer, title, dates, education, and skills into searchable fields. Recruiters filter on those fields, not on the PDF thumbnail. Upload success only means the file landed on the server. Parse success means your latest role shows up where keyword searches expect it.
Two different failures hide behind the same symptom. A hard rejection never creates a profile row. A soft failure creates a row with empty Experience while the attachment icon looks fine. Candidates often chase the first problem with browser tricks when they actually have the second problem in a two-column Canva export.
US startups, agencies, and mid-size companies run Workable beside Greenhouse and Lever. The upload screen behaves the same: attach, preview, answer questions, submit. Workable resume upload issues US candidate fixes target what breaks on that attach step and the preview pane right after it.
Edge case: the posting asks you to paste LinkedIn instead of uploading. Treat that as a separate workflow. This page covers file upload failures and parse gaps on reqs that still want a PDF or Word attachment.
Edge case: you're re-applying to the same company within six months. Workable may pre-fill old answers while still letting you swap the resume. Replace the attachment and open preview again. An old parsed profile can linger in recruiter view until the new file parses cleanly.
A composite operations analyst kept failing uploads until she dropped an embedded chart from a Word resume. File size fell under one megabyte and preview populated on the second try. The chart wasn't the problem on paper. The export bloated the PDF enough to timeout on mobile upload.
Read how to preview your resume like an ATS in the US when you want a parse check outside the employer portal. Same logic, less pressure while the req timer runs.
Workable resume upload issues: five steps that fix US applications
Step 1: Confirm file type, size, and name
Workable commonly accepts PDF and DOCX on US reqs. Pages exports, RTF files, image-only scans, and oversized portfolio PDFs fail before parsing starts. Rename with letters and hyphens only. Keep under five megabytes.
Before: Candidate uploads Resume_Final_v7.pages from an iPhone; error says unsupported format.
After: Exports DOCX from Google Docs, saves as Jordan-Lee-Resume.pdf at 420 KB on desktop Chrome; upload completes in one pass.
Step 2: Strip layout the importer cannot map
Tables, text boxes, sidebar skills columns, icon headers, and multi-column templates reorder text on import. Workable may keep the PDF while leaving Experience empty. Rebuild single column with standard headings: Experience, Education, Skills.
Before: Colorful Canva PDF with two columns, skill icons, and a photo header; upload succeeds but preview shows only name and email.
After: Plain Word export, 11-point Calibri, Month Year dates, no tables; preview lists all three employers in order.
Step 3: Run the Notepad paste test
Open your PDF, select all, copy, paste into Notepad on Windows or TextEdit plain mode on Mac. Employers should read top to bottom. If Skills appears before your current job title, fix layout before you upload again.
Step 4: Upload from desktop Chrome with extensions off
Mobile Safari and ad blockers interrupt uploads more often than the ATS itself. Use Chrome or Firefox on desktop. Clear cache or try incognito if the spinner hangs. Screenshot persistent errors and email the recruiting contact on the posting.
Before: Three failed uploads on phone Safari over coffee-shop Wi-Fi with no error message.
After: Same file uploads on home desktop Chrome with extensions disabled; preview populates in under ten seconds.
Step 5: Open parsed preview before knockout questions
Some Workable reqs show a parsed profile or text preview after attach. Read it before you answer salary, sponsorship, or clearance questions. If dates swapped or titles vanished, fix the file and re-upload once. Submitting with empty Experience wastes a req you cared about.
Before: Candidate answers ten screening questions, then notices Workable imported 2019 internship as current role.
After: Checks preview immediately after attach, fixes date format to Month Year, re-uploads once, then completes the application.
Copy-paste filename and export checklist
Copy-paste this checklist before every Workable application:
Filename: First-Last-Resume.pdf (no spaces, no symbols, no version numbers)
Format: PDF from Word Save As or clean DOCX, not Canva or Pages
Size: under 5 MB (compress images if needed)
Layout: single column, no tables, no text boxes, no icons
Dates: Month Year (Jan 2022 to Present)
Contact: top of body, not header/footer
Test: paste all text into Notepad, employers in order
Upload: desktop Chrome, extensions off, stable Wi-Fi
Verify: open Workable parsed preview before submit
Edge case: password-protected or portfolio-heavy PDF
Workable rejects password-protected files outright. Portfolio PDFs with embedded video thumbnails blow past size caps. Export a one-page resume PDF for the attach field. Link the portfolio in the optional URL field when the req allows it.
Before: 12 MB portfolio PDF with password protection shared from Adobe Cloud; upload fails silently.
After: 890 KB single-column resume PDF plus Behance link in the portfolio field; upload and preview both succeed.
Edge case: cover letter uploaded as resume
Workable has separate fields for resume and cover letter. Combining both into one PDF confuses parsing and buries Experience. Keep two plain files. Upload the resume in the resume field only.
Before: One PDF titled Application_Package.pdf with letter on page one and resume on page two; parser imports letter text as job history.
After: Maria-Chen-Resume.pdf and Maria-Chen-Cover-Letter.pdf uploaded in separate fields; each parses in the correct slot.
For Greenhouse-specific quirks that overlap with Workable, read Greenhouse resume upload issues: US fixes that work . Same plain-export logic, different portal skin.
Upload habits that waste time on Workable
Re-uploading the same broken PDF. If preview already scrambled employers, the parser read what it could from that layout. Change the file once, then upload. Ten identical uploads do not train Workable to parse better.
Chasing browser fixes before fixing layout. Incognito mode does not repair two-column templates. Paste test first. Browser second.
Assuming upload success equals recruiter visibility. Recruiters search parsed fields. Empty Experience with a healthy attachment icon still loses to a plain file that imported cleanly.
Special characters in filenames. Apostrophes, hashtags, emojis, and spaces in Resume (Final) 2026.pdf trigger rejections on some configs. Hyphens and letters only.
I've passed on Workable profiles where the candidate uploaded a gorgeous design PDF three times and never noticed Experience was blank in preview. The hiring manager searched for their current title and got zero hits.
Scanned image resumes. A photo of your printed resume looks sharp to humans and empty to parsers. Re-type into Word or export text-based PDF from the source doc.
See resume formatting errors that break ATS parsing for layout patterns that fail across multiple ATS platforms, not only Workable.
Test before you submit on Workable
After you export a plain file, run it through a parse check with the job description pasted in. You're confirming employers and dates survive import, not chasing a vanity score. Fix layout until Experience reads in order, then upload to Workable.
When the req also asks for a cover letter, build it from the same employer names and dates the resume parsed correctly. Mismatched months between files trigger manual review you didn't need.
Run a free ATS check on the fixed PDF, then build your resume in a single-column template if you're rebuilding from scratch tonight.
Your Workable upload checklist tonight
Workable resume upload issues US candidate fixes come down to file type, size, name, and layout the parser can read in order. Export plain. Paste test. Upload on desktop. Read preview before knockout questions.
Rename to First-Last-Resume.pdf. Strip tables and sidebars. Confirm employers parse top to bottom. Then apply. When the portal wants a letter, generate a cover letter that matches the same dates your resume imported correctly.
This won't fix applying to roles you're not qualified for. It does stop a qualified file from dying in the parser because you re-uploaded the same Canva export five times without opening preview.
And if preview still fails after a plain export, screenshot the error and email the recruiting inbox on the posting. A human can sometimes accept a clean DOCX by email when the portal glitches. Don't ghost yourself because the attach button blinked red once.
Save the plain PDF you uploaded somewhere you can find it. Many Workable reqs let you return to the posting later. You'll want the same clean file if a recruiter asks for an updated version without re-building from a broken Canva export.
Read more
Frequently asked questions
Most rejections come from unsupported file types, files over the size cap, or names with special characters. Workable accepts PDF and Word in most US reqs. Pages, RTF, and image-only scans often fail before parsing starts. Rename to First-Last-Resume.pdf, keep under five megabytes, and export from Word or Google Docs instead of a design tool.
Upload success is not parse success. A blank or partial preview usually means the PDF used text boxes, columns, or embedded fonts the importer skipped. Open the parsed field view if the employer exposes it. If Experience is empty, rebuild single-column layout and re-upload. Do not assume recruiters see the PDF thumbnail you see.
PDF from a clean Word export is the safer default for US corporate reqs. DOCX can work when the template is plain, but styled Word files sometimes lose headings on import. Avoid password-protected PDFs and scanned image resumes unless the posting explicitly allows them. Run a Notepad paste test on whichever format you choose.
Yes. Ad blockers, stale cache, mobile Safari quirks, and unstable connections can interrupt uploads or drop attachments. Try Chrome or Firefox on desktop, disable extensions for the session, and retry on stable Wi-Fi. If the file uploads elsewhere but not on Workable, screenshot the error and email the recruiting inbox listed on the posting.
No. If the preview already scrambled employers or dates, the parser read what it could from that layout. Change the file: single column, standard headings, Month Year dates, no tables or icons. Re-upload once after paste test shows employers in order. Repeated uploads of the same broken PDF waste time and sometimes duplicate incomplete profiles.