Lorixen.
EN

Why Candidates Cannot Upload a CV on Your Recruitment Site: Symptoms, Causes and Fixes

Short answer: When a candidate says the CV will not upload, the cause is almost always one of five things: the file is larger than a limit somewhere in the chain, the format is blocked, a phone sends an unexpected file type, a security layer is rejecting the request, or the connection times out before the file arrives. Each leaves a different symptom. Ask the candidate three questions, check the symptom against the table below, and fix the matching layer. Also make sure a failed upload never costs you the application itself.

The three questions that save an hour

Before touching any settings, collect these from the candidate (or from your form's error log):

  1. What did they see: an error message, a spinning wheel that never ended, or nothing at all?
  2. Which device and browser were they using?
  3. What is the file called, and roughly how big is it?

A reply such as "iPhone, Safari, a Pages document of about 9 MB, spinner forever" already points to two likely suspects. Without it you are guessing.

Symptom, cause and fix

Symptom Likely cause Fix
Message says the file is too large, or the page reloads with no explanation Size limit in the form plugin, web server or hosting plan; the HTTP status 413 means the request body exceeded a limit Raise the limit at every layer, show the limit next to the button, and warn before sending
Upload works on desktop, fails on phones The phone offers a format your form does not accept (Pages, HEIC image of a printed CV, or a cloud file not yet downloaded) Accept common formats and convert, or tell candidates how to export a PDF
Spinner that never finishes on mobile data Large file with a weak signal; no progress shown; server timeout Add progress feedback, lengthen timeouts, and offer "send by email instead"
Generic "forbidden" or a blank page A firewall or security plugin flagged the upload (often macros in older Word files) Review the security log, allow the specific file types, and scan files rather than blocking them blindly
Success message appears but no CV reaches you Form stores the file in a temporary folder that is later cleared, or email notification has an attachment cap Store files in permanent storage and email a link instead of an attachment
Works for some candidates and not others with the same file Filename with unusual characters, very long names or only spaces Sanitise filenames on the server and show the received name back to the candidate
Error only when the form has other fields filled Total request size or maximum fields limit reached Test the whole form with the largest realistic file
File accepted but unreadable by staff Password-protected PDF or scanned image with no text Detect and ask the candidate to resend, and tell them in advance

Layer by layer: where limits hide

A file upload passes through several gates, and the smallest one wins. Check them in order.

The browser and the form

The HTML file input can be told which types to offer through its accept attribute, and it can request the camera on mobile. The MDN guide to file inputs explains these behaviours. Remember that accept is only a hint to the browser. It does not enforce anything, so validate again on the server.

The form plugin or custom code

Many form builders have their own maximum file size, often well below the host's limit. Look for a setting named something like "maximum upload size" and set it consistently with the layers below it.

The web server and PHP or application limits

Servers and application runtimes each set a maximum request size. A candidate sending a 9 MB document to a server limited to 2 MB will receive an error from the server before your form code even runs. If you cannot see the error, ask your developer or host to look at the server log for the 413 status described in the MDN status reference.

Proxies, CDNs and security tools

A content delivery network or web application firewall may impose its own cap, and sometimes blocks uploads that resemble attacks. If the failure is intermittent and produces a short, generic page, suspect this layer. Test from a different network to confirm.

Storage and notification

A successful upload can still lose the file later. If you email the CV as an attachment, your mail provider might drop messages above its attachment size. Storing the file privately and sending staff a link avoids this.

Make the form forgiving

Even a perfect configuration will occasionally fail on a candidate's phone. Design so that failure does not become lost applicants:

  • Separate the application from the file. Submit the name, contact details and role first, then upload the CV as the next step. If the upload fails, you still hold a lead.
  • Offer a fallback. "Having trouble? Email your CV to" followed by a monitored address, or a link to share from a cloud drive.
  • State the rules before the click. "PDF or Word, up to 5 MB" beside the button prevents most errors.
  • Show the received filename and size after upload so the candidate can see success.
  • Do not demand a CV at all for every role. Some candidates apply from a phone while commuting. Allow a short profile or a LinkedIn address as an alternative and ask for the CV later.

Privacy points worth a minute

A CV contains personal data. Store uploads privately, not in a public media folder where anyone with the link can open them. Set a retention period you can explain in your privacy notice, and delete or anonymise old files on schedule. Check the data protection rules that apply to your country with the official regulator rather than relying on a general article.

A short test routine

Once a quarter, run these tests from a phone and a laptop on different networks:

  • A 1 MB PDF and a 7 MB PDF.
  • A Word document with spaces in the filename.
  • A photo of a printed CV taken on a phone.
  • A file with the wrong extension, to confirm the error message is helpful.

Record the results in a simple sheet so changes to the site or host can be compared against them.

FAQ

What is a sensible maximum CV size?

Most CVs are small. A limit between 5 and 10 MB covers almost every document while protecting your storage. State the limit near the button so candidates can check before sending.

Should we accept photos of a CV?

It is better to accept them than to lose the candidate. Treat them as a fallback, and ask for a text version later if the role progresses.

Why does the form work in our office but not for candidates?

Your office network, device and files are not typical. Test with a mobile connection and with files created on phones, not only with documents from your own computer.

Can we avoid uploads entirely?

Yes, by asking for a profile link and a short summary. Many agencies still collect a CV later, once a candidate is shortlisted.

If your application form keeps losing candidates, ask us to audit the upload path and we will report which layer is causing the failures.

Sources

WhatsAppBook a call