Skip to content

cPanel File Manager workflows for support staff

Practical File Manager patterns for support staff handling end-user requests on cPanel, and where to switch to SSH instead of clicking through a tree.

Support staff lean on File Manager because it requires no shell access and leaves an audit trail in the cPanel session log. The problem is that File Manager makes a small set of operations easy and a slightly larger set of operations dangerously slow. Knowing where the line sits saves an afternoon of staring at a spinner.

What’s happening

File Manager is a PHP frontend over the cPanel user’s home directory. It runs as the cPanel user via suEXEC, so every file it creates inherits correct ownership — that’s its main value over uploading by FTP as root. It struggles with three things: directories above ~50,000 entries, archive extraction of very large tarballs, and any operation that needs to traverse symlinks consistently. For those, drop to SSH.

How to verify

Before touching anything, confirm what you are looking at:

ls -la /home/<user>/public_html | head
du -sh /home/<user>/public_html/*
find /home/<user>/public_html -maxdepth 2 -type d | wc -l

A public_html with 80,000 files in a single directory will not browse cleanly in File Manager. A public_html with a normal WordPress layout (~2,000 files) will.

The fix

  1. Use File Manager for: single-file edits (wp-config.php fixes), small uploads under 50 MB, permission changes on individual files, viewing a stuck .htaccess.
  2. Drop to SSH for: extracting any archive over 200 MB, bulk chmod across a tree, copying or moving directories with more than 5,000 entries, anything where the spinner has been running over two minutes.
  3. For end-user file uploads, point the customer at SFTP with a jailed account rather than walking them through File Manager — it’s faster and they keep credentials.
  4. After any File Manager edit on a production file, verify with cat from SSH that what you intended is what landed; the editor occasionally reformats line endings on Windows-uploaded content.

For shared servers where support staff need a reliable runbook for these decisions, Stack Harbor builds the playbook as part of cPanel/WHM management.