Uploading a website in Plesk is a straightforward process, whether you are publishing a new site, moving an existing one, or replacing default placeholder content with your own files. In a hosting environment, Plesk gives you several practical ways to deploy a website, including the File Manager, FTP/SFTP access, and application installers. The best method depends on the type of site you are uploading, how many files you need to transfer, and whether you are working alone or with a developer.
Before you start, make sure your domain is already added to Plesk and assigned to the correct subscription or hosting plan. You should also have access to the website files, database backup if the site uses one, and any required credentials for FTP, SFTP, or the application you plan to install. If your goal is to upload a static HTML site, a WordPress website, or a custom PHP application, the general workflow in Plesk is similar: access the domain, place files in the web root, and verify that the site loads correctly.
Ways to upload a website in Plesk
Plesk supports multiple website upload methods, and the right one depends on your project.
1. Upload through File Manager
This is the easiest option for smaller websites or when you want to upload files directly from the browser. You can open the domain’s document root, drag and drop files, create folders, and extract archives. File Manager is especially useful for static websites, landing pages, or quick updates to a live site.
2. Upload using FTP or SFTP
FTP and SFTP are ideal for larger websites or when you need to transfer many files at once. This method is common for developers and agencies because it works well with desktop clients like FileZilla, Cyberduck, and WinSCP. SFTP is generally preferred because it uses SSH encryption.
3. Install a website application
If your site is based on WordPress, Joomla, or another supported platform, you may not need to upload files manually. Plesk includes application installers and tools that can deploy the website automatically and configure the basic structure for you.
4. Restore or migrate a backup
If you are moving an existing website into Plesk, restoring a full backup may be the fastest option. This is often the best approach when the site already includes files, databases, mailboxes, and settings that need to be preserved.
Before uploading files to Plesk
Preparing the website properly can prevent common errors such as broken links, missing images, permission issues, or a blank page after upload.
Check the domain setup
Open Plesk and confirm that the domain is present under your subscription. If the domain is not yet added, create it first and make sure it points to the correct hosting space. The website files must be uploaded into the domain’s document root, which is usually a folder such as httpdocs.
Prepare the website files
If you are uploading a static site, gather all HTML, CSS, JavaScript, image, and font files into one folder structure. If you are uploading a CMS or custom application, include the application files and any configuration data required by the platform.
For a website migration, it is important to know whether the site uses a database. If it does, you will also need to import the database separately in Plesk and update the application configuration if necessary.
Back up the current site
If there is already content on the domain, create a backup before replacing it. This protects existing files and makes it easier to roll back if something goes wrong during deployment.
How to upload a website in Plesk using File Manager
The File Manager method is best when you want to upload a website quickly without using external software. It works well for small to medium-sized sites and is available directly in the Plesk interface.
Step 1: Log in to Plesk
Sign in to your Plesk control panel using your hosting credentials. After login, open the domain that will host the website.
Step 2: Open the File Manager
Go to Files or File Manager in the domain’s menu. This will show the website’s directory structure. In most Plesk installations, the main web root is the httpdocs folder.
Step 3: Open the document root
Navigate to httpdocs or the folder configured as the website root. This is where the files for the live site must be placed. If your hosting setup uses a different root directory, follow the folder assigned in the domain settings.
Step 4: Upload the website files
You can upload files in one of two common ways:
- Drag and drop individual files or folders into File Manager.
- Upload a compressed archive such as ZIP and extract it after transfer.
If your website contains many files, uploading a ZIP archive is often faster and reduces the chance of incomplete transfer. After the upload finishes, use the extract function in File Manager to unpack the archive into the document root.
Step 5: Verify the default index file
For the website to open correctly, the main entry file should be present in the root directory. Common filenames include index.html, index.php, or the entry file required by your application. If the default page is missing, the server may show a directory listing or an error page instead of the website.
Step 6: Check file permissions
After uploading, make sure the files have proper permissions. Incorrect permissions can prevent the site from loading images, running scripts, or opening configuration files. In general, files should be readable by the web server, while scripts and writable folders should be set according to the application’s requirements.
How to upload a website in Plesk using FTP or SFTP
FTP and SFTP are useful when your website is large, when you need repeated transfers, or when you work from a local development environment. This approach is often preferred for production deployments and ongoing maintenance.
Step 1: Create or confirm FTP access
In Plesk, open the domain settings and check whether an FTP account already exists. If needed, create a new FTP user with access to the website directory. For secure file transfer, choose SFTP if your server supports SSH access.
Step 2: Connect with an FTP client
Open your FTP client and enter the server hostname, username, password, and port number. Typical ports are 21 for FTP and 22 for SFTP. After connecting, locate the domain’s document root folder, usually httpdocs.
Step 3: Upload the files
Transfer all website files to the correct folder on the server. Make sure the folder structure remains intact during upload. If you are publishing a CMS or framework-based site, be careful not to place files one level too high or too low, because this can break routing and asset paths.
Step 4: Confirm the upload completed successfully
Large transfers can sometimes fail before all files are uploaded. Check your FTP client logs for errors and compare file counts if needed. If a file is missing, upload it again before testing the site in a browser.
Step 5: Remove unnecessary placeholder content
Many hosting accounts include a default placeholder page. If your uploaded site is not showing, make sure the document root does not still contain an older index.html file that is overriding your new index.php or other entry file.
How to upload a WordPress website in Plesk
If you are uploading a WordPress site, you can either install it fresh through Plesk or migrate an existing installation. The correct method depends on whether you are starting from scratch or moving a live website.
New WordPress installation
Use the WordPress installer available in Plesk to create a new site quickly. Plesk can set up the files, database, and basic configuration for you. After installation, you can log in to WordPress admin and start building the site.
Migrating an existing WordPress site
If your WordPress website already exists elsewhere, upload the WordPress files to httpdocs and import the database into Plesk. Then update the database credentials in the wp-config.php file so the application can connect to the new database.
After migration, check the site URL, permalinks, and media paths. If the old domain is different from the new one, you may also need to update the WordPress address and site address values.
How to upload a static HTML website in Plesk
Static websites are among the easiest to publish in Plesk because they do not require a database or application installer. Upload the HTML file and supporting assets into the document root, then confirm that the homepage file is named correctly.
Typical file structure
A common static site structure looks like this:
- index.html for the homepage
- css/ folder for stylesheets
- js/ folder for scripts
- images/ folder for image assets
If your website uses relative paths, keep the directory structure unchanged when uploading. A missing folder or renamed file can break page layout or cause 404 errors.
Common static site issue
If the site loads but images or CSS do not appear, the problem is often one of the following: incorrect folder names, uppercase/lowercase mismatch, or files uploaded to the wrong directory. On Linux hosting environments, file names are case-sensitive.
How to upload a website archive and extract it in Plesk
Uploading a ZIP archive is usually the fastest way to deploy a website with many files. This method reduces transfer time and makes it easier to move a complete folder structure at once.
When to use an archive
- Large HTML websites with many folders
- Custom applications with multiple assets
- Website migrations from a local backup
- Temporary staging deployments
How to extract the archive
Upload the ZIP file into the document root using File Manager, then select the archive and choose the extract option. After extraction, confirm that the main files were unpacked into the correct level. A common mistake is extracting a ZIP file that contains another top-level folder, which results in the website files being nested one directory too deep.
Import databases if your website needs one
Uploading the website files is only one part of deploying dynamic sites. If the application uses a database, you must import that database separately in Plesk.
Common examples of database-driven sites
- WordPress
- WooCommerce
- Joomla
- Drupal
- Laravel and other PHP applications
After importing the database, check that the application configuration points to the new database name, username, password, and host. If the connection details are incorrect, the website may show a database connection error even though the files are uploaded properly.
Test the website after upload
Once the files are in place, open the domain in a browser and test the site carefully. A successful upload should result in a working homepage, functioning navigation, and visible assets such as images and stylesheets.
What to verify
- The homepage loads without errors
- Internal links open correctly
- Images, CSS, and JavaScript files load properly
- Forms submit as expected
- HTTPS works if SSL is enabled
- Database-connected pages display content correctly
If the browser shows a blank page, 403 error, 404 error, or redirect loop, check the document root, permissions, application configuration, and SSL settings.
Common problems when uploading a website to Plesk
Even when the upload completes successfully, a few common issues can prevent the website from working as expected.
Wrong document root
If the files are uploaded to the wrong folder, the domain may still show the default Plesk page or an empty directory. Make sure the content is placed in the correct web root.
Missing index file
The server needs an entry file such as index.html or index.php. Without it, the website may not load correctly.
Incorrect permissions
Permissions that are too restrictive can block the web server from reading files. Permissions that are too open can create security risks. Use the recommended settings for your application and hosting environment.
Broken file paths
After migration, asset links may still point to the old domain or local machine. Update paths where necessary, especially in themes, configuration files, and content references.
Database connection errors
If the site depends on a database, confirm that the database exists, the user has access, and the configuration file contains the correct credentials.
Best practices for website uploads in Plesk
Following a few simple best practices can save time and reduce deployment errors.
- Use SFTP instead of plain FTP whenever possible.
- Upload to the correct document root, usually httpdocs.
- Keep a backup before replacing a live website.
- Check file names carefully, especially on Linux-based hosting.
- Import databases separately for dynamic websites.
- Test the site in a browser after every major upload.
- Remove unused files, old backups, and placeholder pages from the web root.
FAQ
Where do I upload my website files in Plesk?
In most cases, upload the files to the domain’s document root, which is usually the httpdocs folder. If your hosting plan uses a custom root directory, use the folder shown in the domain settings.
Can I upload a website without FTP?
Yes. You can use the built-in File Manager in Plesk to upload files directly from your browser. This is convenient for small websites and quick updates.
Should I use FTP or SFTP?
SFTP is generally recommended because it encrypts the connection. FTP can still work, but SFTP is more secure for transferring hosting files.
Why does the default Plesk page still appear after upload?
This usually means the files were uploaded to the wrong directory, the domain is pointing to a different document root, or a default index.html file is still present and taking precedence over your website file.
Do I need to upload a database too?
If your website is dynamic and uses a CMS or application backend, yes. Uploading the files alone is not enough. You must also create or import the database and update the configuration.
Can I upload a WordPress site manually in Plesk?
Yes. You can upload the WordPress files into httpdocs, import the database, and update the configuration file. Alternatively, you can use the WordPress installer or migration tools in Plesk.
What if my uploaded website shows a 403 or 404 error?
Check the file location, file permissions, and the presence of the correct index file. For 404 errors, confirm that the domain points to the right document root and that the file names match exactly.
Conclusion
Uploading a website in Plesk can be as simple as placing the correct files in the domain’s document root, but the best results come from following a structured process. Whether you use File Manager, FTP or SFTP, an application installer, or a backup restore, the key steps are the same: prepare the files, upload them to the right location, confirm permissions, and test the website after deployment.
For hosting customers and managed hosting users, Plesk provides a practical way to publish and maintain websites without requiring command-line access. Once you understand how the document root, file structure, and database setup work together, you can upload new sites and migrations with much more confidence.