Upload Files with File Manager
Choose the right folder, protect existing files and verify the upload.
Choose the right folder, protect existing files and verify the upload.
File Manager lets you upload website files through cPanel without installing a separate transfer client. The most important step is choosing the correct destination folder: a successful upload will not update your website if the file lands in the wrong document root.

Decide which domain and URL should serve the file. In cPanel’s Domains interface, check the document root for that domain. The main website often uses public_html, while additional domains can have separate folders.
For example, a file named guide.pdf placed in the correct document root is usually reached as https://example.com/guide.pdf. If it is inside a downloads folder, that folder becomes part of the address.
Download a copy of an existing file before overwriting it. Record its location and current permissions so you can restore it if needed. For an application update, take a matching database backup as well.
Keep private archives and configuration copies outside publicly served folders. A filename ending in .bak does not make a sensitive file private. Our backup guide explains the wider recovery process.
Sign in to cPanel over HTTPS, open Files → File Manager and navigate to the confirmed folder. Read the path shown before proceeding. Use Settings to display hidden files when working with dotfiles such as .htaccess.
If the website is deployed from a Git repository or another automated process, follow that deployment method. Editing generated files manually can be overwritten later and leave the deployed version inconsistent.
Click Upload, choose the file from your computer or use the supported drag-and-drop area, and wait for the progress indicator to finish. Review any overwrite option before confirming a replacement.
Return to the folder and refresh the listing. Confirm the expected filename and size. Consult the cPanel File Manager documentation if controls differ on your server.
For multiple files, a ZIP archive can make a small transfer easier. Upload it to a suitable location, inspect the intended contents and extract into the correct folder. Avoid archives from untrusted sources.
Check for an extra top-level directory after extraction. WordPress, for example, may arrive inside a wordpress folder. Our manual installation guide shows how folder placement affects the final URL.
Use the upload limit displayed by your hosting interface rather than assuming a universal 500 MB limit. Available quota, server limits and browser interruptions can also affect transfers. For large datasets, ask about SFTP or another supported method.
Linux hosting commonly treats capital letters as distinct. Photo.jpg and photo.jpg can be different files. Check permissions and ownership if the upload succeeds but access fails; do not solve it by making everything writable.
Open the intended HTTPS URL in a separate tab. Confirm that the correct version loads and clear only the relevant browser or CDN cache if an old version persists. Check links from the page that should reference it.
Remove installation archives from public folders once you have verified extraction and retained a private backup. Finish by recording what changed and where the recovery copy is stored.
Check the domain’s document root, subfolder and filename. If only WordPress page URLs fail, use the 404 troubleshooting guide rather than repeatedly uploading the file.
Only upload application code you trust and intend to run. Uploading a PHP script into a public folder can make it executable through the website. Keep private configuration files in the location required by the application and hosting setup.
For help with File Manager, contact DigitalBerg with the affected domain, the step you tried and a redacted error message. Never include passwords, private keys or complete configuration files containing secrets.

PHP Configuration: 7 Essential Steps for a Safe Update
