Published: 20.09.2026
Uploading files is the oldest way to publish a website: you copy the folder of your site from your computer to the server. Virtual Hosting plans include FTP access, so any standard desktop FTP client can connect. This guide walks through the steps, the folder structure and the errors that beginners meet most often.

Before you start
- Note the connection details from your customer area: the host name, user name, password and port.
- Keep a copy of the current site, so that you can return to it if something goes wrong.
- Check the customer area for the connection modes offered, and prefer an encrypted option when one is available.
Connect with an FTP client
- Install a desktop FTP client that supports the connection mode shown in your details.
- Create a new site entry and enter the host name, user name, password and port exactly as listed.
- If the connection stalls after login, switch between passive and active mode. Passive mode is often needed behind home routers and firewalls.
- Connect and wait until the remote folder list appears.
Find the right folder
The publicly visible folder is the one your control panel names for the website. On many hosts it is called public_html, but use the name your panel shows for your account. Upload the site files into that folder, not into the folder above it. A common beginner mistake is uploading into a sibling folder, so the site looks unchanged and the upload appears to have failed.
Upload and set permissions
Upload the whole folder structure and keep the same nesting. You can drag files from your computer to the remote folder, or use the transfer function of the client. When the transfer finishes, compare the number of files on both sides. On a Linux server, files usually need permission 644 and folders need 755. These settings let the web server read the site without letting others change it. Permission 777 is almost never correct and creates a security risk.
Common errors and their causes
- Login failed. The user name or password is wrong, or you used details from a different account.
- Connection times out. Usually the passive or active mode setting, or a local firewall blocking the data connection.
- Permission denied during upload. You are in a folder you cannot write to, or the target file is locked by another program.
- The site still shows the old version. A browser or server cache holds the previous copy, or the files went into the wrong folder.
- Broken text files. A transfer in text mode can change line endings. Use binary mode for images and archives, and let the client detect text files automatically.
After the upload
Open the site in a private browser window to avoid cached pages. Check the home page, a form and an image. If the site uses a database, confirm that its configuration file still points to the right database name and user. Then save a note with the date and the list of uploaded folders, so the next upload is easier to verify.
Frequently asked questions
Is FTP safe? Plain FTP sends the user name and password without encryption. Use an encrypted option when your connection details offer one.
Can I upload one archive instead of many files? That is faster for many small files. Extract the archive on the server only if your control panel or site software offers a tool for it; otherwise upload the individual files.
Why did an upload overwrite a file? Most clients replace files with the same name without asking, unless you set a rule. Keep a backup of the current version before you upload a new one.