How to upload website to hosting is straightforward when you have a ready HTML site: place the files in your domain’s web root, then open the domain and test every page. This guide shows the browser-based DirectAdmin method and the FileZilla method, including the common index.html, ZIP-folder and missing-image mistakes.
What you need before uploading
You need four things:
- A hosting account with your domain added and pointed to it.
- The finished website folder from your designer, developer or AI tool.
- The hosting panel login, or an FTP account with its host, username and password.
- A recent copy of the website folder saved on your computer.
First open the site folder on your computer. A simple static site often looks like this:
my-website/
├── index.html
├── about.html
├── css/
│ └── style.css
├── js/
│ └── script.js
└── images/
└── hero.jpg
The key point is that the homepage file and its asset folders must be together. If index.html is inside another folder such as website-final/website-final/, you will need to upload the contents of the inner folder, not just the outer folder.
If you have not purchased hosting yet, HostKarle Basic is designed for one website and costs ₹99/mo when billed yearly at ₹1,188. It includes DirectAdmin, Softaculous, free auto-renewing Let’s Encrypt SSL and self-service website tools.
Step 1: Prepare and check the website files
Why this matters: Uploading a broken local folder only makes the same broken site available online. A quick local check catches most missing-file problems first.
- Open
index.htmlon your computer in a browser. - Click the navigation links and check that the pages open.
- Check images, fonts, CSS and JavaScript in the same folder.
- Keep file and folder names simple. Use lowercase names without spaces, such as
contact.htmlandimages/team-photo.jpg. - If your site is ready, compress the complete site folder into a
.zipfile. Keep the uncompressed copy as a backup.
Look at the ZIP before uploading it. When you open it, you should be able to find index.html and folders such as css, js or images. If the ZIP contains only another folder, plan to move that folder’s contents into the web root after extraction.
Success looks like this: the local copy opens correctly, all visible assets load, and the ZIP contains the site’s files rather than a second ZIP or an unrelated parent folder.
Step 2: Open the DirectAdmin File Manager
Why this matters: DirectAdmin’s File Manager lets you upload a ZIP and extract it in the browser, so you do not need a separate desktop application for a small site.
- Sign in to your hosting account and open DirectAdmin.
- Open File Manager. DirectAdmin describes this as the panel tool for basic file-system operations; its official File Manager documentation explains the feature.
- Open the domain’s web-root folder. In a standard DirectAdmin layout, it is
domains/your-domain.example/public_html. - If a provider-created placeholder
index.htmlis present, download or rename it before replacing it. Do not delete files you do not recognise until you have confirmed what they do. - Choose Upload files and select your website ZIP.
- Wait for the upload to finish completely. Refresh the file list and confirm that the ZIP is in the correct
public_htmlfolder. - Select the ZIP and choose Extract or Extract here.
- Open the extracted folder. If it contains
index.htmldirectly, move its contents intopublic_html. If it contains a second folder first, open that inner folder and move the files from there. - Keep the folder structure intact. For example,
images/hero.jpgmust remain in animagesfolder besideindex.htmlif the HTML refers toimages/hero.jpg.
Success looks like this: index.html sits directly inside the domain’s public_html, and the same level contains the css, js and images folders used by the page.
Step 3: Upload an HTML site with DirectAdmin File Manager
Why this matters: Uploading the individual files is useful when you are changing one page or when you want to see exactly what reaches the server.
- In the domain’s
public_html, click Upload. - Select
index.htmland upload it. - Upload the other HTML pages, then upload the
css,js,images,fontsand other required folders. - Recreate the same folder names and capitalisation shown on your computer.
- Return to the
public_htmllisting and confirm thatindex.htmlis not inside a newly created project folder. - If you are replacing a page, upload the new file with the same name and confirm the overwrite only after checking that you have a local backup.
For a one-off upload, the ZIP-and-extract method is usually easier because it preserves the folder structure. Individual uploads are convenient for a small change, such as replacing about.html or one image.
Success looks like this: opening your domain shows the newly uploaded homepage, and the File Manager shows index.html plus its asset folders directly inside the correct public_html.
Step 4: Upload website files with FileZilla
Why this matters: FileZilla is practical when the site contains many files or when you want to upload a whole folder by dragging it to the server.
FileZilla’s official quick guide explains that the local files appear on the left and remote server files on the right. It also documents drag-and-drop uploads and the default FTP and SFTP ports.
- Install FileZilla Client, then open its official quick guide if you need help finding the connection fields.
- In DirectAdmin, open the FTP account details for the domain. Copy the exact host, username, password and port supplied by your host. Do not guess the host name or reuse your hosting-panel password unless the panel says they are the same.
- In FileZilla, open File > Site Manager and create a new entry.
- Select the protocol and encryption shown in your hosting instructions. If explicit FTP over TLS is available, use it; otherwise use the secure connection method your host provides.
- Enter the host, port, username and password, then connect.
- In the Local site panel, open the folder containing your website files.
- In the Remote site panel, open the domain’s
public_htmldirectory. With a standard DirectAdmin layout, this is underdomains/your-domain.example/public_html. - Select the contents of the local site folder, including
index.html, and drag them into the remotepublic_htmlfolder. Do not drag the outer project folder if that would createpublic_html/my-website/index.html. - Watch the transfer queue at the bottom. Wait until the failed-transfer list is empty, then refresh the remote folder.
If FileZilla reports too many connections, open the Site Manager’s Transfer Settings and limit simultaneous connections, as described in the official guide. If a file fails, retry it and confirm that the remote path is still the domain’s public_html.
Success looks like this: the transfer queue has no failed files, and the remote public_html contains index.html with the same folders and filenames as your local site.
For a full explanation of the hosting choices behind this process, read how to host a website step by step. If you are moving an existing WordPress site rather than uploading a new HTML folder, use the separate WordPress migration guide.
Step 5: Put the homepage in the right place
Why this matters: The server can only show the homepage automatically when its default file is in the domain’s document root.
Your main page should normally be named index.html for a static HTML site. It must sit directly in the domain’s web root:
public_html/
├── index.html ← homepage
├── about.html
├── css/
├── js/
└── images/
This layout will not work as the homepage if the file is buried here:
public_html/my-website/index.html
In that case, either move everything inside my-website up one level or visit the site at the matching subdirectory URL. Moving the contents is usually the right choice for the main domain.
Also check the spelling and capitalisation of every path. Images/logo.png, images/logo.png and images/Logo.png may be different paths on a hosting server. An image that opens locally but not online usually has a wrong relative path, a mismatched filename or was not uploaded.
Success looks like this: visiting the domain opens the intended homepage instead of a directory listing, welcome page or nested project folder.
Step 6: Add SSL and test the live site
Why this matters: Testing the HTTPS version checks both the uploaded files and the domain’s secure connection.
- Confirm that the domain points to your hosting account. If you recently changed DNS, test again after the DNS change has taken effect.
- In DirectAdmin, open SSL Certificates for the domain.
- Choose the Let’s Encrypt or automatic certificate option available in the panel, then request or enable the certificate for the domain and its
wwwversion if you use both. - Open
https://your-domain.examplein a private browser window. - Test the homepage, navigation, contact links, images, CSS, JavaScript and any downloadable files.
- Open the browser developer tools and check the Console and Network tabs if the page looks unstyled or an image is missing.
- Test on a phone as well as a computer. Check both the non-
wwwandwwwversions if your site uses both.
HostKarle shared hosting includes free auto-renewing Let’s Encrypt SSL. DirectAdmin’s ACME documentation explains that certificates can be issued and renewed automatically once the domain is correctly configured.
Success looks like this: the site opens at https://your-domain.example, the browser shows a valid connection, and the main page has no missing assets.
Common upload problems and fixes
Use this table to identify the mistake before uploading the site again.
| What you see | Likely cause | Fix |
|---|---|---|
| The hosting welcome page still appears | The old placeholder index.html is still being served, or your files are in the wrong folder | Check the active domain’s public_html; rename the placeholder after saving a copy; ensure your index.html is at the root. |
| A 403 Forbidden page appears | There is no usable index file, the domain points to another folder, or the request is not reaching the expected site | Confirm the document root and the exact spelling of index.html, then test the domain again. |
| The page is blank or shows an old version | The browser is using a cached copy, or the new file was uploaded to another directory | Open a private window, hard-refresh, and verify the remote path and file modification time. |
| The HTML loads but images are broken | The image folder was not uploaded, or the path uses different capitalisation | Compare the src path in the HTML with the remote filename and folder structure. |
| CSS or JavaScript does not work | The asset path starts from the wrong folder or contains spaces and capital letters that do not match | Inspect the browser’s Network tab and correct the href or src path. |
| The ZIP extracted into an extra folder | The ZIP contained the project folder itself | Move the contents of the inner folder into the domain’s public_html, keeping index.html at the top level. |
| FileZilla shows failed transfers | The connection details, remote folder or transfer queue needs attention | Recheck the FTP details, reconnect, retry failed files and wait for the queue to finish. |
| HTTPS shows a certificate warning | SSL is not active for the domain yet, or DNS still points elsewhere | Confirm DNS and the DirectAdmin SSL certificate status, then test the HTTPS URL again. |
Do not fix a missing image by changing the HTML to a random external image URL. Upload the image with your site and use the correct relative path. This keeps the page’s assets under your control and makes future backups simpler.
Verify the upload with a short checklist
Before sharing the domain, confirm all of these points:
index.htmlis directly inside the correct domain’spublic_html.- Every CSS, JavaScript, font and image folder is present on the server.
- Links work from the live HTTPS URL, not just from a local file.
- The page works after a hard refresh and in a private browser window.
- The
wwwand non-wwwversions behave as intended. - There are no 404 requests for images, stylesheets or scripts in the browser’s Network tab.
- You still have the original website folder and the uploaded ZIP as a backup.
FAQ
Where should I upload my HTML website?
Upload the website files to the domain’s public_html folder. In a standard DirectAdmin account, the full path is usually domains/your-domain.example/public_html; your index.html should sit directly inside it.
Why is my website not showing after I upload it?
The most common causes are an index.html inside an extra folder, an old placeholder file, the wrong domain folder or a browser cache. Check the remote folder structure first, then open the HTTPS URL in a private window.
Can I upload a ZIP file instead of every HTML file?
Yes. Upload the ZIP to the correct public_html, extract it there and move the extracted contents up if index.html is inside an extra folder. Keep the original ZIP on your computer as a backup; it does not need to stay in the public folder after extraction.
Should I use DirectAdmin File Manager or FileZilla?
Use DirectAdmin File Manager for a small one-time upload or a ZIP-and-extract workflow. Use FileZilla when the site contains many files or you expect to upload updates regularly; in both cases, the destination is the same domain public_html.
How do I make my uploaded website secure with HTTPS?
Point the domain to the hosting account, then enable or request the domain’s Let’s Encrypt certificate in DirectAdmin. Once the certificate is active, test the https:// address and update any hard-coded http:// asset links in your HTML.
Want to partner with us, suggest a resource or advertise on this blog? Email partnerships@hostkarle.in



