What cPanel File Manager is and where it opens
cPanel File Manager is the browser tool in cPanel's Files section that uploads, extracts, edits and sets permissions on the files of one cPanel hosting account. It opens at /home/username in a new browser tab, with the live site in public_html. Nothing is installed on your computer, and a one-file change does not need FTP.
- public_html holds the primary domain. An addon domain or subdomain has its own document root, listed under Domains.
- mail and logs belong to the panel. Leave them alone unless support asks for a log line.
- .trash holds deleted files until you empty it, so a wrong Delete is recoverable.
- The editor refuses a file over 1 MB. Download those and edit them on your computer.
File Manager is not a deployment tool. A cPanel-to-cPanel move copies databases and email as well, so it runs through a full backup and restore rather than a drag of public_html; the cPanel full backup guide covers that. If the panel is new to you, the cPanel tour names each section.
Open File Manager in public_html with hidden files visible
Most people meet the wrong folder first, because Settings opens the home directory rather than the site. Set it once and every later visit lands in the right place.
- Log in to cPanel for the domain, at yourdomain.com/cpanel or the server address on port 2083. The billing client area is a separate login.
- Open Files, then click File Manager. It opens in a new browser tab.
- Click Settings in the top right and choose Web Root (public_html or www) as the folder to open by default.
- Tick Show Hidden Files (dotfiles), then click Save. .htaccess and .user.ini are dotfiles and stay invisible without this.
- Read the path bar: /home/username/public_html is the live site, and an addon domain's root is its own folder inside the home directory.
You know it worked when the path bar ends in public_html and the list includes .htaccess. If there is no File Manager icon at all, the host has hidden it in WHM's Feature Manager; email support@webji.services rather than hunting for a workaround.
Upload a folder into cPanel File Manager
File Manager cannot upload a folder. Compress it on your computer, upload the archive, then extract it on the server, which is also faster than sending thousands of small files one at a time.
- Right-click the folder and compress it: Compress on macOS, or Send to then Compressed (zipped) folder on Windows.
- In File Manager, open public_html for the domain that should receive the files.
- Click Upload, drag the archive onto the page, or use Select File. Tick Overwrite existing files only when replacing is intended.
- Wait for the progress bar to finish, then click Go Back to the folder.
- Select the archive, click Extract, confirm /home/username/public_html as the destination, and click Extract Files.
- Click Reload, open the new folder, and delete the archive so it is not downloadable.
You know it worked when the folder sits inside public_html and https://yourdomain.com serves the page instead of a directory listing. The Upload page prints the size limit for the account; a backup larger than that goes over SFTP, not the browser.
Extract an archive without the extra folder layer
If the zip was made by compressing a folder, Extract recreates that folder, so the site lands at public_html/site-name and the domain shows a directory list or a 404. The files are one level too deep, and a second upload repeats the mistake.
- Open the wrapper folder inside public_html.
- Select the files and folders inside it, not the wrapper itself.
- Click Move, enter /home/username/public_html as the destination, and click Move File(s).
- Delete the empty wrapper folder and the archive, then reload the domain.
Compress runs the other way: select files or a folder, choose Compress, and pick .zip, .tar.gz or .bz2 before downloading a copy. That copy is what saves you when an edit goes wrong, so take it before a theme update or a bulk permission change.
Edit a file and confirm the change on the live site
Select the file, click Edit, keep utf-8 in the encoding dialog, change the line, then click Save Changes. File Manager keeps no undo history, so the copy comes first.
- Right-click the file, choose Copy, and save it under the same name with .bak on the end.
- Select the original, click Edit, choose utf-8, and click Edit again.
- Change one block, click Save Changes, and close the tab.
- Load the page in a private window. A caching plugin or CDN can serve the old file for several minutes.
- Once the page is right, delete the .bak file. A backup inside public_html can be downloaded by anyone who guesses its name.
wp-config.php sits in public_html and holds the database name, user and password, which is why it gets the copy treatment. Edit it in File Manager only while the file is under 1 MB; larger files must be downloaded, changed locally and uploaded back. A database is not a file, so imports run in phpMyAdmin, as the MySQL database guide shows.
Set files to 644 and folders to 755
Select the item, click Permissions, type the number, and click Change Permissions. Files are 644 and folders are 755 on a cPanel account; 777 is never the answer.
| Value | Use for | What it grants |
|---|---|---|
| 644 | Files: PHP, HTML, CSS, images | Owner reads and writes; group and world read only |
| 755 | Folders, and scripts that must execute | Owner reads, writes and executes; others read and enter |
| 600 | A config file that holds a password | Owner only, when the host recommends it |
| 777 | Nothing on shared hosting | Everyone can write; often blocked, and always a risk |
Each of the three digits covers owner, group and world, and each digit is a sum: read 4, write 2, execute 1. Tick Recurse into subdirectories only when the whole tree should change, and use the Files or Directories option so a folder is not set to 644 by accident.
A 403 straight after an upload is usually a folder at 644 or a missing index file. php.ini is not normally edited by hand here; Software, then MultiPHP INI Editor, writes the correct file for the domain and keeps the change on record.
File Manager problems and the fix for each
Most File Manager failures are a wrong folder, a wrong permission or a cached page, and each one has a single check.
| Symptom | Fix |
|---|---|
| 403 Forbidden after an upload | A folder sits at 644 or the index file is missing. Set folders to 755 and confirm index.php or index.html is present. |
| Upload stalls or is refused | The archive is over the limit printed on the Upload page. Compress it again, or send it by SFTP. |
| Edit saved but the page is unchanged | Cache, or the wrong domain's folder. Check the path bar and load the page in a private window. |
| Disk quota exceeded | .trash and old archives still count. Empty Trash and delete zips with Disk Usage open. |
| .htaccess is missing from the list | Settings, then Show Hidden Files (dotfiles). The file is present, only hidden. |
| Extract finished but pages return 404 | The files are one folder deep. Move them up to public_html. |
If space is still short after that cleanup, read Disk Usage before buying a bigger plan; a stale backup archive is the usual cause. A white page with an HTTP 500 is a PHP fault rather than a file problem, and the 500 error guide starts from the log.
Frequently Asked Questions
Where is File Manager in cPanel?
Log in to cPanel, open Files, then File Manager. It opens in a new browser tab at /home/username. Click Settings, choose Web Root (public_html or www), tick Show Hidden Files (dotfiles), and click Save so every later visit lands on the site folder.
How do I upload a folder in cPanel File Manager?
You cannot upload a folder directly. Compress the folder on your computer, open public_html in File Manager, click Upload and send the zip, then select the archive and click Extract with /home/username/public_html as the destination. The folder appears after Reload.
What permissions should files and folders have?
Files are 644 and folders are 755. Select the item, click Permissions, type the number and click Change Permissions. A configuration file that holds a password can be 600. Do not use 777 on a cPanel account: every account on the server could write to that file.
Why did my site end up in public_html with an extra folder?
The zip contained a folder, so Extract recreated it. Open that folder, select the files inside, click Move and send them to /home/username/public_html, then delete the empty folder and the zip. Reload the domain and the home page should appear.
Can I edit wp-config.php in File Manager?
Yes, up to 1 MB. Copy the file to wp-config.php.bak first, then select it, click Edit, keep utf-8 in the encoding dialog, change the line and click Save Changes. Delete the .bak afterwards, because a backup inside public_html can be downloaded by anyone who guesses the name.

