Uploading website files in Plesk is one of the most common tasks when you launch a new site, move content from another platform, or update an existing project. In a managed hosting environment, Plesk gives you several ways to place files on the server, and the best method depends on the size of your website, the type of files you need to upload, and whether you are working directly on the main domain, a subdomain, or an application directory.
If you are managing hosting for a European audience, it is especially important to keep file uploads organised, secure, and consistent. A clean structure in your web root helps with performance, backups, troubleshooting, and future maintenance. In this guide, you will learn how to upload website files in Plesk using File Manager, FTP, and archive extraction, as well as how to verify that the files are placed in the correct directory.
Where website files are stored in Plesk
Before you upload anything, you should know where Plesk serves website content from. In most hosting setups, your domain’s public files are stored in the httpdocs directory. This is the main web root for the domain. When a visitor opens your website, the web server typically reads the files from this location.
Depending on your hosting plan and configuration, you may also see other folders such as:
- httpsdocs or similar secure directories in some setups
- cgi-bin for scripts in older or specialised configurations
- subdomain folders created for each subdomain
- private, logs, or backup-related directories
For a standard website, upload your public files to the domain’s httpdocs folder unless your hosting provider has specified a different document root. If you place files in the wrong directory, the website may not load, or you may see a default page instead of your actual content.
Ways to upload website files in Plesk
Plesk supports multiple upload methods so you can choose the most practical one for your task. The most common options are:
- File Manager in the Plesk control panel
- FTP or FTPS from an external client
- Archive upload and extraction for larger websites
Each method has advantages. File Manager is quick and simple for small changes. FTP is better for recurring updates and working with many files. Archive upload is usually the fastest option for large website migrations or deployments.
How to upload website files with File Manager in Plesk
File Manager is the easiest way to upload files directly through the Plesk interface. It is useful when you need to replace a few files, upload a small theme, add an image, or restore a simple website backup.
Step 1: Open the domain’s File Manager
Log in to Plesk and select the relevant domain or subscription. Open Files or File Manager. You will see the folder structure for that hosting account.
Step 2: Go to the correct directory
Open the httpdocs folder unless your site uses a different document root. If you are uploading files for a subdomain or an application directory, navigate to that specific folder instead.
Step 3: Upload the files
Click Upload and select one or more files from your computer. Depending on the browser and Plesk version, you may be able to drag and drop files into the window as well.
If you are replacing existing website files, make sure you understand which files are being overwritten. For example, if you upload a new index.html or index.php, it may replace the homepage currently used by your site.
Step 4: Confirm the upload
After the transfer finishes, check that the files appear in the correct folder and that the file names are exactly as expected. Hosting platforms on Linux are case-sensitive, so Logo.png and logo.png are different files.
When File Manager is the best choice
- Uploading a few files or images
- Making a quick fix to the homepage
- Restoring a small project from backup
- Managing files without using an external FTP client
How to upload website files using FTP in Plesk
FTP is the preferred method when you work with a full site, need repeated uploads, or want to use a code editor or deployment workflow. In hosting environments, FTPS is generally recommended over plain FTP because it adds encryption to the connection.
Step 1: Create or check FTP access
In Plesk, open the domain or subscription and look for FTP Access or the related user settings. Confirm that you have valid login credentials. If needed, create a new FTP user and assign the correct home directory.
Important details usually include:
- FTP host or server address
- Username
- Password
- Port often 21 for FTP, with FTPS supported depending on configuration
Step 2: Connect with an FTP client
Use a desktop FTP client such as FileZilla, WinSCP, or another client that supports secure connections. Enter the server details provided in Plesk or by your hosting provider. If available, choose FTPS or explicit TLS to keep the connection protected.
Step 3: Open the web root folder
Once connected, browse to the domain’s httpdocs directory. This is where the website files should be uploaded. If you upload content outside the document root, it will not normally be visible on the website.
Step 4: Upload your website files
Select the files on your local computer and transfer them to the server. For a complete site upload, include all required assets such as HTML, CSS, JavaScript, images, fonts, PHP files, and any configuration files used by the application.
If you are deploying a CMS such as WordPress, Joomla, or Drupal, upload the full application structure, not only the visible page files. Missing folders or incomplete uploads can break the site or cause missing styles and images.
Step 5: Verify file permissions and ownership
After upload, check that file permissions are suitable for web hosting. In many Plesk setups, files should not be writable by everyone. Incorrect permissions can create security risks or cause access errors.
As a general rule, the hosting environment should allow the web server to read public files, while write access should be limited to directories that truly need it, such as cache or upload folders used by an application.
How to upload a full website faster with archive extraction
For larger websites, uploading hundreds or thousands of files individually can be slow. A more efficient approach is to compress the site into a ZIP archive, upload the archive, and then extract it directly on the server through Plesk.
Step 1: Create a ZIP archive locally
Compress your website files into a ZIP file on your computer. Make sure the archive contains the actual site files in the correct structure. A common mistake is uploading a ZIP that includes one extra parent folder, which can place the files one level too deep after extraction.
Step 2: Upload the archive to httpdocs
Use File Manager or FTP to upload the ZIP file to the target directory, usually httpdocs.
Step 3: Extract the archive in Plesk
In File Manager, select the ZIP file and choose Extract Files or a similar option. Plesk will unpack the contents into the current directory.
Step 4: Clean up the archive
Once extraction is complete and the website works correctly, delete the ZIP file from the server if you no longer need it. Keeping large archives on the hosting account can waste disk space and may expose unnecessary files.
How to upload website files for a new domain or migration
When you add a new domain in Plesk or move a site from another hosting platform, the upload process should be planned carefully. The file structure, database connection, and domain settings all need to match the application requirements.
For static websites
Upload the HTML, CSS, JavaScript, images, and any other assets into the document root. Make sure there is a valid homepage file such as index.html.
For PHP-based websites
Upload the complete application files, including the entry script, templates, libraries, and configuration files. If the site uses a database, you will also need to import the database separately and update the connection settings in the configuration file.
For CMS websites
When transferring a content management system, upload all core files and folders, then restore the database, and finally adjust site URLs, credentials, and file paths if needed. If the site depends on cached content or generated files, clear the cache after deployment.
Common mistakes when uploading files in Plesk
Many website issues after upload are caused by small but important mistakes. The following problems are among the most common:
- Uploading to the wrong folder instead of httpdocs
- Leaving files inside an extra subfolder after extraction
- Using the wrong file name such as home.html instead of index.html
- Case mismatch in file names or links
- Overwriting configuration files unintentionally
- Missing permissions for required folders
- Incomplete uploads caused by interrupted FTP transfers
If your website still shows an old version or a placeholder page after upload, check whether there is another index file in the directory, or whether the domain is pointing to a different document root.
How to verify that the upload was successful
After uploading website files in Plesk, always test the site before considering the task complete. A quick verification can save time later and help you catch missing files or incorrect paths early.
Check the homepage
Open the website in a browser and confirm that the homepage loads as expected. If the page is blank or broken, inspect the server error logs and verify that the main index file is present.
Check internal links and assets
Browse a few pages and confirm that CSS, images, JavaScript files, and downloadable documents load correctly. Broken assets often indicate incorrect paths or missing files during upload.
Test on secure HTTPS access
If the domain uses SSL, open the website over HTTPS as well. Mixed content, incorrect redirects, or missing secure configuration files can affect the visible result even when the files were uploaded correctly.
Review logs if needed
Plesk provides access to logs that can help identify file-related issues, permission problems, and application errors. Logs are especially useful after a migration or when a site behaves differently after deployment.
Best practices for managing website files in Plesk
Good file management makes hosting maintenance easier and reduces the risk of outages. These practices are especially useful in managed hosting setups where stability and clarity matter.
- Keep public files in the correct document root
- Use descriptive file names and folder names
- Separate application code from uploaded media when possible
- Back up the website before major file changes
- Use FTPS instead of plain FTP when available
- Remove unused archives and old deployment files
- Check file permissions after large transfers
- Test the site after every significant upload
If multiple people manage the same hosting account, agree on a consistent folder structure and naming convention. This is especially helpful for agencies, developers, and businesses that update content regularly.
What to do if uploaded files do not appear on the website
If the files are present in Plesk but the website does not show them, use this checklist:
- Confirm the files are in the correct domain folder
- Check whether the domain uses a different document root
- Verify the homepage file name, such as index.html or index.php
- Look for another default index file that may be taking priority
- Make sure the file permissions allow the web server to read the files
- Clear browser cache and, if relevant, application cache
- Check whether DNS already points to the correct hosting service
In some cases, the site may be loading from a cached version or an old deployment directory. Reviewing the active document root in Plesk is often the fastest way to identify the issue.
FAQ
Which folder should I upload website files to in Plesk?
In most cases, upload public website files to the httpdocs folder for the relevant domain. If your setup uses a different document root, follow the path shown in Plesk for that site.
Can I upload files directly from my browser?
Yes. Plesk File Manager allows browser-based uploads, which are convenient for small changes or quick fixes. For larger sites, FTP or archive extraction is usually more efficient.
Is FTP safe for uploading website files?
Plain FTP is not secure because it does not encrypt data. If your hosting setup supports it, use FTPS or another encrypted transfer method when uploading sensitive website files.
Why does my website still show the old page after upload?
This usually means the files were uploaded to the wrong directory, the homepage file name is incorrect, or another default file is still taking priority. Browser cache can also make it look like nothing changed.
Can I upload a ZIP file and extract it in Plesk?
Yes. This is a common method for larger websites. Upload the ZIP archive to the correct directory and use File Manager to extract it on the server.
What should I do if some images or CSS files are missing?
Check the folder paths, file names, and case sensitivity. On Linux hosting, a mismatch in letter case can prevent files from loading even when they exist on the server.
Conclusion
Uploading website files in Plesk is straightforward once you know where the document root is and which method best fits your task. For small updates, File Manager is usually enough. For larger deployments, FTP or archive extraction is more practical. In all cases, the key is to place the files in the correct directory, keep the structure organised, and verify the result after upload.
By following these steps, you can manage website files efficiently in Plesk, reduce deployment errors, and keep your hosting environment clean and maintainable. Whether you are publishing a new site, updating a client project, or restoring files after a backup, a careful upload process helps ensure a stable result.