When Eploy refuses a CV or processing crawls to a halt, the file is usually the problem — too large, the wrong format, or full of special characters. This guide helps you clear Eploy upload errors quickly.
TL;DR: Eploy upload problems come from large files (images), unsupported formats (older .doc, scanned images), special characters in names and addresses, and timeouts on big simultaneous batches. Keep files under 2MB, use clean .docx or text-based PDFs, and batch in manageable sizes. Distill automates this prep.
Quick diagnosis: what’s blocking the upload?
| Symptom | Likely cause | Quick check |
|---|---|---|
| Upload slow or times out | Large file with images | Is the file over ~2MB? |
| File rejected outright | Unsupported format | Is it an old .doc or a scanned image? |
| Error on a valid-looking CV | Special characters in name/address | Any unusual symbols in the text or filename? |
| Several uploads fail at once | Too many simultaneous uploads | Are you uploading a large batch together? |
Root causes ranked by frequency
Large files with images PDFs and Word files carrying photos or logos slow uploads and trigger timeouts. Removing images usually fixes it.
Unsupported or poor formats Older .doc files and scanned images are rejected or parse so badly they fail. Use .docx or text-based PDFs.
Special characters Non-standard symbols in the candidate's name, address, or filename can trigger upload errors. Stick to plain alphanumeric text and filenames.
Oversized simultaneous batches Uploading many CVs at once can overwhelm the process and cause failures. Smaller batches are more reliable.
Step-by-step fix
- Strip images and compress. Remove photos and logos; keep files under 2MB.
- Convert to a clean format. Save as .docx, or a text-based PDF if required.
- Clean special characters. Remove unusual symbols from the text and use a plain filename like "Firstname Lastname - Job Title.docx".
- Batch in manageable sizes. Upload smaller groups rather than one huge batch.
- Retry failures individually to isolate a single problem file.
How to prevent Eploy upload issues on future submittals
- Standardise a lightweight, image-free CV template.
- Use a clean filename convention with no symbols.
- Let Distill strip images and standardise formats before upload.
- Keep batches small and run them on a stable connection.
When to escalate to Distill
Use Distill if uploads regularly fail or stall:
- You submit 20+ CVs weekly and keep hitting size or format errors.
- CVs arrive with images that must be removed each time.
- Large batches repeatedly time out.
Distill removes images, compresses files, standardises to clean .docx, and produces upload-ready CVs so Eploy accepts them first time.
FAQ
Q: What file size works for Eploy? A: Keep CVs under about 2MB. Removing photos and logos is the quickest way to get there.
Q: Which formats does Eploy handle best? A: Clean .docx or text-based PDFs. Avoid older .doc files and scanned images.
Q: My valid CV still won't upload. Why? A: Check for special characters in the filename and the candidate's details, and for embedded images.
Q: Why do my batch uploads fail? A: Batches that are too large can time out. Split them into smaller groups.
Q: Does Distill upload to Eploy for me? A: No. It prepares upload-ready files; you import them into Eploy as usual.
If Eploy upload errors keep interrupting your workflow, Distill prepares every CV to spec automatically. Try Distill free and keep your batches moving.