Skip to content

cPanel File Manager upload fails or stops part way

Uploading through cPanel File Manager fails, stalls, or silently drops large files. Usually it is PHP upload limits, disk space, or permissions. Here is how to fix each.

When an upload through cPanel’s File Manager fails outright, hangs, or quietly stops before a large file finishes, the File Manager itself is rarely the problem — it runs as a PHP application, so it inherits PHP’s upload limits, the account’s disk and inode quotas, and the target directory’s permissions. A small file uploads fine while a large one fails because it crosses upload_max_filesize or post_max_size; an upload dies at the same percentage every time because the disk filled; a write is refused because the folder is owned by the wrong user. The fix is to find which limit was hit and raise or clear it.

What’s happening

cPanel’s File Manager upload is handled by PHP, so a file has to clear several PHP and account limits before it lands: upload_max_filesize (the largest single file), post_max_size (the whole POST body, which must be larger than the file), max_execution_time and max_input_time (a slow upload over a thin connection can exceed these), and memory_limit in some configurations. Beyond PHP, the account disk quota or inode count can be exhausted (lots of small files hit the inode limit even with disk to spare), the server partition (/home or /tmp) can be full, and the target directory can have wrong ownership or permissions so the write is refused.

The symptom usually points to the cause: a hard size ceiling means a PHP upload limit; a failure at a consistent point or across all uploads means disk/quota; a single folder that fails while others work means permissions; a timeout on a large-but-allowed file over a slow link means the time limits.

How to verify

Check the PHP upload limits for the account first — File Manager obeys the same php.ini as the site.

# Effective upload limits for this account's PHP version
grep -i "<domain>" /etc/userdatadomains       # which ea-phpNN
/opt/cpanel/ea-php81/root/usr/bin/php -i | grep -iE 'upload_max_filesize|post_max_size|max_execution_time|max_input_time|memory_limit'

Check disk space, quota, and inodes — any of the three stops a write.

# Account quota (disk AND inodes/files)
quota -u <cpaneluser>
repquota -a 2>/dev/null | grep <cpaneluser>

# Server partitions — is /home or /tmp full?
df -h /home /tmp
df -i /home          # inodes, not bytes

Confirm the target directory is writable and look for the failure in the log.

# Ownership/permissions of the upload target
ls -la /home/<cpaneluser>/public_html/<targetdir>/

# PHP/Apache log around the failed upload
tail -30 /home/<cpaneluser>/logs/<domain>.error.log

The fix

  1. Raise the PHP upload limits — a hard size ceiling means the file exceeds upload_max_filesize or post_max_size. In cPanel » MultiPHP INI Editor, set upload_max_filesize and post_max_size for that account (e.g. 128M and 144M — post_max_size must exceed upload_max_filesize). Confirm with php -i. These are the limits behind almost every “large file won’t upload.”
  2. Raise the time limits for slow connections — a large-but-allowed file that dies mid-upload on a thin link is hitting max_execution_time / max_input_time. Increase both in MultiPHP INI Editor. For genuinely large files over a slow connection, FTP/SFTP is more reliable than a browser upload regardless of limits.
  3. Free disk space — df -h shows /home (or /tmp, where uploads buffer) full. Clear space — old backups, logs, large unused files — then retry. An upload that fails at the same byte count every time is the classic disk-full signature.
  4. Clear the inode/file quota — df -i or quota shows the file count maxed even with disk free. cPanel quotas cap the number of files, not just bytes; an account full of cache or session files hits this. Remove unneeded small files (cache, old session data) or raise the quota in WHM » Modify an Account.
  5. Fix target directory permissions — File Manager cannot write to a folder owned by root or another user. Reset ownership to the cPanel user and the directory to 0755 (see the permissions runbook). A single non-writable folder fails while every other upload works.
  6. Account disk quota, not just the partition — quota -u shows the account at its limit while df shows the server has room. Raise the account quota in WHM » Modify an Account or have the user free space. The two are separate ceilings and either one blocks the upload.
  7. Use the right tool for very large files — the File Manager upload is fine for ordinary files but is not the best path for multi-gigabyte transfers. For those, use SFTP, or upload a single archive and extract it server-side via File Manager’s Extract — one big file plus an extract beats hundreds of small browser uploads.

Once the relevant limit is raised or cleared, re-upload the file and confirm it appears with the correct size and the cPanel user as owner — a completed upload plus a clean log is the proof. Stack Harbor handles cPanel upload-limit and quota triage under WHM server management — start a conversation.