To upload a website with FTP or SFTP, get the server address, username, password and port from your web host, connect with an FTP client or an editor with built-in publishing, open your site's public folder (often public_html, www or htdocs), and copy your site's files and folders into it. Make sure your home page is named index.html, then visit your domain in a browser to check that it works.
This guide covers where to find your connection details, which protocol to pick, the upload itself, and what to check afterwards.
What you need before you start
Gather these from your host's control panel or welcome email:
- Host name or server address, such as
ftp.example.com,example.comor an IP address. - Username and password. These are often separate from your control panel login. Many hosts let you create extra FTP or SFTP accounts.
- Protocol and port. SFTP usually uses port 22, and FTP and explicit FTPS usually use port 21. Your host may use different numbers.
- The folder for your website, if the host does not put you in it automatically.
You also need your finished site in one folder on your PC, with the home page named index.html in the top level of that folder.
Choose SFTP or FTPS if you can
Plain FTP sends your password and files without encryption. If your host offers SFTP or FTPS, use one of those. They work the same way from your point of view, but the connection is encrypted.
| Protocol | Encrypted | Usual port |
|---|---|---|
| SFTP | Yes | 22 |
| FTPS (explicit) | Yes | 21 |
| FTPS (implicit) | Yes | 990 |
| FTP | No | 21 |
For more detail, read FTP vs SFTP vs FTPS.
Step by step: uploading your site
- Open your FTP client or publishing tool and create a new connection (often called a site or server profile).
- Enter the connection details: protocol, host, port, username and password. Save the profile so you do not have to type them again.
- Connect. The first time you use SFTP, you may be asked to trust the server's key. With FTPS, you may be asked to accept a certificate. If the details match your host's, accept.
- Open the public folder on the server. Look for
public_html,www,htdocsor the folder your host names. If you see your domain name as a folder, the site may belong inside it. - Remove or replace the placeholder page. Many hosts put a default
index.htmlorindex.phpin the folder. Your ownindex.htmlshould replace it. If the host left anindex.php, delete or rename it, as it may be shown instead of your page. - Upload the contents of your site folder, not the folder itself. Your
index.htmlshould sit directly in the public folder, alongside folders such asimagesandcss. - Wait for the transfer to finish and check the log or queue for failed files. Retry any that failed.
Upload the contents, not the folder
This is the most common mistake. If you drag your whole my-site folder into public_html, your home page ends up at example.com/my-site/ and visitors to example.com see a blank listing or the host's default page. Open your site folder and upload what is inside it.
Check the live site
When the upload finishes, test it properly:
- Visit your domain and click through every page in the menu.
- Check that images, styles and fonts load on each page.
- Try your site on a phone, using mobile data rather than Wi-Fi, to see it as a new visitor would.
- Use a private browser window so you are not seeing a cached copy.
If images are missing, the cause is usually a file path or a capital letter in a file name, because many web servers treat Photo.jpg and photo.jpg as different files. If you still see old content, see why website changes are not showing.
If the connection fails
- Timed out or refused: check the host name and that the port matches the protocol. Port 22 with FTP, or port 21 with SFTP, will not work.
- Login failed: retype the password, and check whether your host wants the full username, such as
name@example.com. - Connected but no file list: with FTP or FTPS, turn on passive mode.
- Permission denied when uploading: you may be outside your site's folder, or the account may be read-only. Ask your host.
Updating your site later
You do not need to upload everything each time. Upload only the files you changed, keeping the same names and folders, and they replace the old copies. A few habits help:
- Keep your PC copy as the master. Make changes there, then upload.
- If you rename or delete a page locally, remove the old file from the server too, or it stays online.
- Keep a note of which files you changed, or use a tool that tracks them for you.
- Keep a backup of the site folder before big changes.
The easier way: publish straight from Apollo Editor
Apollo Editor is a Windows desktop HTML editor with optional publishing built in, so you can upload your site without a separate FTP program.
- FTP, FTPS and SFTP publishing, plus local folder and ZIP export.
- Saved server profiles with secure password storage and a connection test.
- Changed file detection, so you can upload only what changed, or choose selected files or the whole site.
- Progress, a publishing log and transfer verification, so you can see what went up.
Your site stays as plain HTML files, so you can still use any other upload method whenever you like. Before you upload, it is worth reading how to organize your website folder and why images might not show after uploading. You can also see all features.
Frequently asked questions
Which folder do I upload my website to?
Usually a folder called public_html, www or htdocs. Your host's control panel or welcome email will say which.
Do I need to upload every file each time?
No. Upload only the files that changed. Publishing tools that track changed files make this quicker and safer.
Why do I see a default host page instead of my site?
Your home page may be in the wrong folder or not named index.html, or the host's placeholder file is still there.
