How to Upload a Claude Code HTML Website to Hostinger

To publish a simple Claude Code website on Hostinger, make a safe upload copy, put its website files directly inside the correct public_html folder, connect the domain with the values shown in your own hPanel, and test the secure address before sharing it. The key path is public_html/index.html -- not an extra folder wrapped around it.

This guide pairs with my full Hostinger walkthrough. It is written so you can work through the process at your own pace, even if you do not watch the video.

What this guide covers

This is for a simple static website: an index.html home page plus images, CSS, JavaScript or other files it uses. It does not cover WordPress, Hostinger Website Builder, Horizons, a database-backed site or a Node.js application.

Hostinger changes its hPanel labels from time to time. Use this tutorial as the process, then check Hostinger's current website setup guidance and the wording in your own account before changing anything.

1. Make an upload copy first

Keep your original Claude Code project unchanged. Copy the folder and give the copy a clear name, such as website-upload-copy.

In that copy, include the files visitors need:

• index.html
• images, stylesheets and scripts used by the page
• any folders those files depend on, keeping their structure unchanged
• .htaccess, if your working website already has one and you know it is needed

Keep project notes, unused files and a .git folder offline. Your Git history is useful for development, but it does not belong on a simple public upload.

2. Check the folder level before uploading

Open the upload copy and select its contents, not the outer folder itself. The correct end result looks like this:

public_html/
|-- index.html
|-- images/
|-- css/
`-- js/

If you upload the outer website-upload-copy folder, the path can become public_html/website-upload-copy/index.html. That extra layer can stop Hostinger finding your home page.

3. Add the correct type of Hostinger website

In this tutorial's setup, the files are already built, so the relevant Hostinger option is Custom PHP/HTML website. It is not the same as rebuilding the site in Hostinger Website Builder or Horizons.

If you are using an existing hosting slot, confirm that you have selected the correct domain. If the domain already has a live site, make a restorable backup before replacing or removing any files. For a new plan, confirm current features, total payable and renewal pricing directly with Hostinger; plans and regional options change.

4. Upload to the correct public_html folder

In Hostinger, open the selected website's dashboard and then File Manager. Confirm both the domain and the folder path before uploading.

Open public_html, then upload the prepared website contents. For a confirmed new, empty Custom PHP/HTML site, Hostinger may show a temporary placeholder file. Remove only that known placeholder after confirming the site is new and empty. Do not delete unfamiliar files on a live website.

After upload, check that index.html is directly inside public_html. If your website uses asset folders, keep the same internal structure that worked locally.

5. Connect the domain without guessing

Open the domain connection guide in your own Hostinger dashboard. Use the exact nameservers or IP address shown there -- do not copy DNS values from a video or another person's account.

Hostinger commonly offers two routes for a domain registered elsewhere:

• Nameservers: move DNS management to Hostinger. Save your current records first, especially if email is handled elsewhere.
• A records: keep DNS management with your current provider and change only the records Hostinger identifies for the website.

DNS records tell the internet where services such as your website and email live. A nameserver change can affect email, so pause and get current support if you are unsure. Hostinger's domain connection guide is the source to follow for your account.

6. Check SSL and test the live site

Once the domain points to Hostinger, check the SSL status in the website dashboard. Wait until it is active, then open the full https:// address in a private or incognito window. This helps you avoid being misled by an old cached page.

Run a practical first check:

1. Does the home page load at the secure address?
2. Do images, menus and buttons work?
3. Do internal and external links lead where they should?
4. Does the page work on a phone as well as a desktop?
5. Is the correct domain selected, without an unexpected temporary page?
6. Have you kept the known-working upload copy for rollback?

If something is broken, do not keep making random changes. Compare the live folder with your working local copy, confirm the public_html/index.html path, and restore the prior known-working files if necessary.

Get the free launch checklist

Before changing website files or domain records, use the Claude Code Website Launch Checklist. It gives you one practical sequence for the upload, domain, device checks and rollback copy.

If you are still deciding what to build before you invest more time, the free TrueLane assessment can help you explore an online-business direction that fits how you work. It is an educational starting point, not financial or professional advice.

Before you share your site

Your website does not have to be complicated to go live safely. Keep the original project, upload only the files visitors need, check the folder level, and use the current details in your own Hostinger account when you connect the domain.