Using cPanel File Manager: Upload, Edit, and Manage Website Files

cPanel's File Manager gives you full access to your hosting account's file system through a browser, with no FTP client required. It's useful for quick edits, uploads, file organisation, and extraction of ZIP archives during migrations. This guide covers everything you need to use it effectively, including situations where you should use FTP instead.

Navigating File Manager and the public_html Directory

Open cPanel and click File Manager under the Files section. By default it opens to your home directory. Your website's public files live in the public_html folder; click into it. This is your web root, anything placed here is accessible at your domain.

A typical WordPress public_html contains:

• wp-admin/, wp-content/, wp-includes/: the core directories
• wp-config.php: your database and configuration settings
• .htaccess: Apache/LiteSpeed server rules (permalinks, redirects, security headers)
• index.php: the WordPress entry point

Hidden files like .htaccess aren't shown by default. Click Settings in the top-right of File Manager and tick "Show Hidden Files" to reveal them. You need this enabled any time you're working with .htaccess or other dotfiles.

Uploading Files and Extracting ZIP Archives

To upload files, navigate to the target directory and click the Upload button in the toolbar. You can drag and drop files directly, or browse to select them. File Manager handles single files and small batches well.

For larger uploads, a full plugin directory, a theme, or a WordPress backup, it's faster to upload a ZIP file and extract it in-place. Upload the ZIP, right-click it, and select Extract. Choose the destination directory (usually the current location) and confirm. This is the standard method for migrations: upload your site's ZIP to public_html and extract there.

To create a ZIP for download or backup, select the files and folders you want, right-click, and choose Compress. Select ZIP format and name the archive. Once created, right-click the ZIP and download it. Note that compressing a large directory tree (thousands of files) can take a minute or two; File Manager will indicate when it's complete.

Editing Files In-Browser

For quick edits, updating a constant in wp-config.php, fixing a rule in .htaccess, or adjusting a hard-coded value in a theme file, right-click the file and select Edit. File Manager opens a basic text editor in-browser. Make your changes and click Save Changes.

Be cautious with PHP files: a syntax error will break your site immediately. For anything beyond a one-line fix, use a proper editor locally (VS Code, Sublime Text) and upload the revised file, or use SFTP with a local editor and direct save to the server. The File Manager editor doesn't have syntax highlighting or error detection.

If you accidentally break a site with a bad edit, restore the file from a backup immediately. If you don't have a recent backup, most of WordPress's core files can be re-uploaded from a fresh download, the only custom files that can't be replaced this way are your theme files, plugins, and wp-config.php.

File Permissions: 644 and 755

File permissions control who can read, write, and execute files on the server. WordPress has specific requirements:

• Files: 644, owner can read and write; group and world can only read. Correct for all PHP files, HTML, CSS, JS, and wp-config.php.
• Directories: 755, owner can read, write, and execute (traverse); group and world can read and traverse. Required for WordPress to access folders like wp-content/uploads/.
• wp-config.php: 640 or 600, more restrictive than standard files, since it contains database credentials. 640 allows the web server group to read it; 600 restricts it to the file owner only. Some hosts recommend one over the other; check your host's documentation.

If WordPress can't upload images or install plugins, check that wp-content/ and its subdirectories are 755. To change permissions in File Manager, right-click a file or folder and choose Change Permissions. You can apply permissions recursively to a directory and all its contents by ticking the "Recurse into subdirectories" option.

Avoid setting files to 777 (world-writable). It's a security risk, any process on the server can write to those files, and many hosts will flag or suspend accounts with 777 permissions on PHP files. There is almost no legitimate reason to set PHP files to 777.

Finding Large Files and Managing Disk Usage

Running low on disk space? In File Manager, you can sort files by size within any directory by clicking the Size column header. For a broader search, use cPanel's Disk Usage tool (in the Files section), which shows a visual breakdown of which directories are consuming the most space.

Common culprits on WordPress sites: wp-content/uploads/ (unoptimised images, old media never deleted), wp-content/backups/ (backup plugin archives that should be stored offsite and deleted locally), and old WordPress core files from failed or interrupted updates.

Inode usage (number of files, not just total size) matters on shared hosting. Thousands of small files, like cache files generated by some caching plugins, or session files, can exhaust inode limits even if disk space is plentiful. Check inode usage in cPanel's Disk Usage tool alongside storage size.

When to Use FTP Instead of File Manager

File Manager is convenient but has real limitations. For bulk operations, uploading hundreds of files, downloading an entire site, or syncing a local copy with the server, use an FTP client like FileZilla. It handles large transfers reliably without browser timeout issues, supports resumable transfers, and lets you compare local vs. remote files side by side.

Use SFTP (SSH File Transfer Protocol) rather than plain FTP when your host supports it. SFTP encrypts both authentication credentials and data in transit; plain FTP sends both in cleartext. In FileZilla, set the protocol to SFTP and use port 22. Your credentials are the same as your hosting account login. All modern hosts support SFTP; there's no reason to use plain FTP.

File Manager is best for quick single-file tasks and in-browser edits. FTP is better for anything involving volume, migrations, or working with your local development environment. Many developers use VS Code with an SFTP extension to edit remote files directly with syntax highlighting and local Git tracking, which is more efficient than File Manager for ongoing development work.