Quick answer
In File Manager, open the domain's confirmed document root, select Upload, and upload only the intended public files. Keep a recovery copy before replacing an existing file.
Applies to
Interactive Online customers with an authorized cPanel login and the relevant tool enabled. Confirm the hosting service and domain before changing files or settings.
Steps
- Open Domains and confirm the document root for the intended hostname. Then open Files > File Manager and navigate to that exact directory.
- Download or otherwise preserve the files you will replace. Keep secret-bearing backups outside public web access. A WordPress folder must not be replaced with an unrelated static export.
- Select Upload, use Select File or the displayed upload area, and review any overwrite option. For a static site, upload the contents of its public output folder with the required relative asset structure.
- Return to File Manager and check filenames and case. Open the exact HTTPS URL, including a nested page, images and stylesheet.
cPanel screenshots
The screenshot shows demonstration files in an isolated folder outside the public website. For a live website, first confirm its document root in Domains.
Use Select File to choose the intended public file. Keep Overwrite existing files off unless you deliberately intend to replace an existing file and have a recovery copy.
If your static export is a ZIP
Check the archive on your computer first. It should contain only the intended public output, with no private keys, .env files, source-control folder or database dump. Upload it to the intended folder, select it in File Manager and choose Extract. Review the destination carefully; an extra top-level folder can put index.html in the wrong place. Preserve the destination before any overwrite. After verification, keep any recovery archive outside public web access.
For a safe practice run, follow the isolated static-file recovery exercise. Upload progress and extraction completion do not establish that the correct domain serves the files.
Verify the result
Verify the public content and links. A successful upload message alone does not establish that DNS or the domain mapping serves that folder.
Troubleshooting and support
If the public site did not change, check the document root, filename case and relevant cache. A quota or permission error needs a specific fix; making all files writable is not a repair. Contact support from the account that owns the service. Include the domain, the exact tool, the time and time zone, the last successful step, and a redacted error or screenshot. Leave passwords, private keys, cookies, and complete configuration files out of the ticket.
Where do I upload website files?
Use the document root shown for your exact hostname in cPanel > Domains. Upload the public output into that folder, with its entry file at the intended level. A successful transfer into your account's home folder or an extra export folder does not publish the domain. Check the domain-to-folder mapping before replacing files.
File Manager upload failed
- The upload stops or reports a size/storage limit. Keep the exact error and compare the file with the maximum size shown on the upload screen and the account's available storage. An account quota and an upload limit are different constraints. Do not change global PHP settings or repeatedly retry a large archive without identifying the limit.
- A folder cannot be selected. File Manager uploads files. For a complete static export, use a reviewed ZIP and the extraction steps above, or use SFTP if your service enables it. Keep the public folder structure intact.
- Permission denied or overwrite refused. Recheck the account and destination. Preserve the current file, then request a specific ownership/permission correction if needed. Making every file writable can expose the site.
- Website returns 403 after upload. Confirm the expected entry file is in the domain's actual document root. Keep an existing application entry file unless its replacement was deliberate. Follow the 403 Forbidden checks for index, permission and access-rule evidence.
- The page loads but images or styles are missing. Check that the assets were uploaded, paths use the correct filename case, and the HTML does not point to a file on your computer. See the published-site verification steps.
After a targeted correction, open the exact HTTPS page and one nested URL, image and stylesheet. If it still fails, contact support with the public URL, destination, file size, timestamp/time zone and redacted error. Never attach private archives or credentials to a public report.
Related help
- Publish an AI-generated static HTML website to cPanel
- Find the correct document root before an AI tool uploads files
- Fix website file permissions without making everything writable
- Find .htaccess and other hidden files in File Manager
- Upload website files with SFTP: settings and secure connection
- Site shows 403 FORBIDDEN message.
- Send a website support request with useful troubleshooting details
Official references
Content and source review: November 1, 2026. Interface labels depend on the cPanel version and tools enabled for your service.
Customer troubleshooting and related-help review: November 1, 2026. Earlier review notes retain their original scope.
