Plesk File Manager uploads website files without requiring a separate transfer client. Upload into the document root for the intended domain, and check the package contents first so private configuration, development files or backup archives are not accidentally published.
IN THIS ARTICLE
What you need before you begin
Open the domain hosting settings and note its document root. The main site often uses httpdocs, but additional domains and applications can use a different location. Keep a backup before overwriting an existing release and check the subscription storage allowance.
01 Upload website files with Plesk File Manager
- Open Files for the correct subscription, then browse to the intended domain document root.
- Choose the upload action and select the required files or archive. Review the browser upload limit; a larger deployment may require an approved FTP(S), SFTP or deployment workflow instead.
- Wait for completion and check the filenames. For an archive, inspect its directory structure before extracting, since it may create an unexpected extra top-level folder.
- Review overwrite prompts carefully. Keep secrets and database dumps outside the public document root, and remove the uploaded archive after confirming successful extraction if it is no longer needed.
- Check the entry file and application configuration. Use the ownership and permissions supplied by the hosting environment rather than making all files writable by everyone.
02 Example: prove the upload reached the correct website
Upload a new file named upload-check.html into the document root shown for your domain. Do not replace an existing homepage:
<!doctype html>
<html lang="en">
<meta charset="utf-8">
<title>Upload check</title>
<p>Plesk upload check completed.</p>
</html>
Visit https://example.com/upload-check.html, replacing the domain with yours. The expected sentence proves that this URL can serve the uploaded static file. A 404 suggests a path or routing issue; success does not yet prove PHP or database connectivity. Delete the file after checking.
How do I check the uploaded website files?
Visit the intended domain and test a representative page and asset. Confirm the browser is reaching the correct server, and check for unintended directory listings or public backup files. A successful upload does not prove a database-backed application is configured.
Troubleshoot unexpected results
For a failed upload, inspect quota, maximum file size and permissions. For an unchanged page, check the document root and caches before uploading repeatedly. If a release breaks the site, restore the recorded files or approved backup and investigate the application error log.