Updated: 2 hours ago
Drag your finished site files in and get a live URL in seconds. Try Wix Headless →
You made a website. Maybe you coded it yourself, used an AI tool to create it or downloaded the files from another platform. Now you have a folder of website files, but how do you actually get that website online?
You need to put those files somewhere that can make them available on the internet. This is called website hosting. To get your site online, you can take the technical route, using tools such as SFTP or Git, or choose a hosting platform that lets you upload your finished website files directly and takes care of the deployment for you.
Go from files to a live site with Wix Headless. Upload or drag in your HTML, CSS and JavaScript files to get your site live on a Wix URL, with SSL and a global CDN included. You can add ecommerce, bookings, a CMS, payments and more with a single prompt.
TL;DR: how to upload a website
Uploading a website means getting the right files or project onto a service that can make your site available online. The easiest method depends on how your site was created and whether you have finished files or a project that still needs to be built.
You'll learn:
What website files you need and whether they're ready to upload
How uploading, publishing and deploying differ
Which hosting and upload method to use, including File Manager, SFTP and Git
How to upload websites created with AI tools
How to upload finished website files to Wix Headless
How to connect your domain and troubleshoot common issues
How to test and update your live website
What does it mean to upload a website?
A website is made up of files that work together to create the pages people see. The main types are:
HTML creates the structure of a page
CSS controls how the page looks
JavaScript adds interactive behavior
Images, fonts and other files provide the content the site needs
When those files are only on your computer, the website is not available for other people to visit. You need to put a copy of the files on a web server, which is a computer connected to the internet that can deliver your website to visitors.
Uploading a website means transferring your website files from your computer to a web server through a hosting service. Once the files are uploaded to the right location, the server can send them to a visitor's browser when they open your website address.
Upload vs. publish vs. deploy
You'll see these three words throughout website tutorials. They can sound like different versions of the same thing, and sometimes they are.
Upload means transferring your website files from your computer to your hosting service so the site can be accessed online. Depending on the service, you might upload the files through a File Manager, SFTP or another method.
Publish means making a website or your latest changes available for visitors. The term is especially common with a website builder, where you make changes to your site and click "Publish" to put those changes live. Unlike uploading, you don't usually handle the website files yourself.
Deploy means taking a website or application and making it live on a server. Uploading files can be one step in deployment, but deployment can also include building the site, setting up its configuration and making sure everything is ready to run. The term is common with coded websites and applications, especially when using Git or automated tools.
For a simple website, uploading the files can effectively be the same step as putting the site live. For a more advanced project, there can be several steps between writing the code and making the finished site available to visitors.
You don't need to understand all of those differences to upload your first website. Start by finding out what files you have and what your hosting service supports.
What website files do you need to upload?
Before you upload a website, first check what you actually have. The files you receive from an AI tool or coding tool can be very different, and the right upload method depends on them.
If you have finished website files
If your folder contains files such as index.html, CSS, JavaScript and images, you likely have a finished website that can be uploaded directly to hosting that supports this type of site.
A ZIP file containing these files works too. Many hosting services let you upload the ZIP and extract it on the server.
If you have a code project
If you see files such as package.json, a src folder or other project files, you may have the files used to create the website rather than the finished website itself. These projects often need to be built first, which turns the code into the files that can be uploaded and served to visitors.
Don't upload the whole project folder yet. Check the instructions for the AI tool or coding tool you used to find out how to build the project and where it puts the finished files. The resulting folder may contain files such as index.html, CSS, JavaScript and images that are ready to upload.
Does your website need server-side features?
Some websites need more than HTML, CSS, JavaScript and images. If your site has features such as user accounts, saved customer information, a database, online payments or code that runs on the server, you'll need hosting that supports those features.
These are often called server-side or backend features because part of the website runs on the server rather than in the visitor's browser. Uploading a folder of website files to basic static hosting won't provide a database or run that server-side code.
If you're not sure, check the instructions for the tool or coding project that created your site. It should tell you what your website needs to run.
What you need before you upload a website
Before you upload your website, make sure you have the files that make up the site, a place to host them and a way to transfer them to the server. You may also need a domain name if you want people to visit the site at a custom web address.
01. Your website files
This might be a folder on your computer, a ZIP file or the finished files produced by an AI or coding tool. Make sure you have every part the site depends on, including images, CSS, JavaScript and fonts.
02. Web hosting
Hosting is the service that keeps your website files available on the internet. Some hosting services are designed for simple websites, while others support applications, databases, server-side code and other requirements. Managed cloud hosting takes care of the underlying servers for you, so you don't have to manage the hardware yourself.
The hosting service you choose also affects how you upload your website. For example, many shared hosting plans include a control panel with a File Manager, while other services may have you upload files with SFTP, connect a Git repository or use the provider's own deployment tools.
If you are weighing up the options, cloud hosting vs shared hosting is the comparison worth reading first.
Read more:
03. A domain name
A domain is the web address people use to visit your site, such as yourbusiness.com. Domain registration is a separate purchase from hosting. You don't always need a domain before uploading your site. Many hosting services give you a temporary web address that you can use for testing.
04. A way to upload the files
Depending on your hosting service, you may upload your website using one of these methods:
A File Manager in your browser
SFTP
FTP
Git
The platform's own upload or deployment tool
For a first upload, a File Manager is often the simplest option if your hosting provider offers one.
Good to know: You don't need to choose an upload method before you choose your hosting. The options available depend on your hosting service, and you can choose the one that fits your site and how you plan to manage it. You can also connect a domain later.
Learn more about Wix headless CMS and what is headless commerce
Which upload method should you use?
The right method depends on what you have, what your hosting service supports and how often you plan to update your site. For a finished website that does not need a complicated development setup, a direct upload is usually the simplest route.
File Manager is the simplest option for a first upload. It lets you select files and folders in your browser and upload them directly to your hosting account, so you don't need to install or learn another program. The drawback is that uploading large sites or frequent updates can become tedious because files usually have to be selected and uploaded manually.
SFTP is useful when you need more control over your files. It uses a file transfer program to securely move files between your computer and the server, which can make regular updates easier. The tradeoff is that you need to install a program and enter your server connection details, so it has more setup than a browser-based upload.
FTP works in a similar way to SFTP but does not encrypt the connection. It can still be found on older hosting services, but SFTP is generally the better choice when both are available. For a new site, there is little reason to choose traditional FTP over a secure alternative.
Git is designed for websites that are managed as code projects. Instead of treating the site as a folder of files, Git keeps track of changes to the project and can work with a deployment process that sends those changes to your hosting. This is useful for developers and teams, but it adds concepts and setup that most people don't need for a simple finished site.
Automated deployment removes much of the manual uploading. Once it is set up, a change to your code can trigger a process that builds the site and sends the updated version to your hosting automatically. This saves time for sites that change often, but setting up the workflow can be more work than manually uploading a small site.
Some hosting platforms let you upload finished website files directly. This can be a useful middle ground when you have a site created with a coding or AI tool but don't want to configure SFTP, Git or a deployment pipeline. For example, Wix Headless lets you upload or drag in finished website files and handles the deployment to a live URL, so you can go from a completed site folder to a live site without setting up a separate server workflow.
Method | Best for | How it works |
|---|---|---|
File Manager | Simple websites and first-time uploads | Upload files through your browser |
SFTP | Secure file transfers | Transfer files securely between your computer and the server |
FTP | Older hosting setups | Transfer files between your computer and the server |
Git | Coded websites and development projects | Connect a code repository and deploy changes |
Automated deployment | Sites updated through code | Automatically sends new site changes to hosting when you update your project |
Platform upload tool | Hosting platforms with their own workflow, like Wix Headless | Upload or deploy files using the platform's tools |
Drag your finished site files into Wix Headless and Wix handles the hosting, SSL and CDN for you.
How to upload a website with a File Manager
A File Manager is usually the easiest way to upload a simple website because you can do everything from your browser.
01. Log in to your hosting account
Open the dashboard or control panel provided by your hosting company. Look for an option related to your website files.
02. Open the File Manager
The tool might be called File Manager, Files, Website Files or something similar. The name depends on your hosting provider.
03. Find the folder for your website
Your hosting account has a specific folder where your website files need to go. This is sometimes called the document root or web root.
On many hosting setups, the main website uses a folder called public_html. Other hosts may use a different name, so check your hosting provider's instructions if you're not sure.
04. Upload your website files
Upload the files and folders that make up your website. For a simple site, you might have something like this:
index.html
css/
js/
images/Keep the folder structure the same as it is on your computer. If your HTML expects an image at images/logo.png, for example, the images folder needs to be in the correct location on the server too.
05. Upload a ZIP if you have many files
If your site contains a lot of files, you don't need to upload every file separately. Many hosting File Managers let you upload one ZIP file and extract it on the server.
After extracting it, check the folder structure carefully. A ZIP might contain a top-level folder, which can leave your site one level deeper than expected.
For example, you might end up with:
public_html/
my-website/
index.html
css/
images/when you actually need:
public_html/
index.html
css/
images/If index.html is inside an extra folder, your domain may not show the site you expect.
06. Open your website
Visit the temporary URL provided by your hosting service, or your domain if you've already connected it.
Check the homepage, images, navigation and other pages. If something looks wrong, the upload may still have worked correctly. A missing CSS file, image or JavaScript file is often caused by a file path or folder structure that doesn't match the original site.
Where should index.html go?
For many simple websites, the homepage file is named index.html. It needs to be in the folder your hosting service uses as the website's root folder.
For example:
public_html/
index.html
css/
js/
images/If you put it here instead:
public_html/
my-site/
index.htmlyour website may not load at your domain's main address because the homepage is one folder too deep.
Not every website uses index.html, so don't rename files automatically if your project uses another setup. Frameworks and some hosting systems have their own rules.
Good to know: On many hosting setups, index.html is the default file shown when someone visits the site's root address. File names can be case-sensitive, so Index.html and index.html may be treated as different files.
How to upload a website with SFTP
SFTP is another way to transfer website files from your computer to your hosting account. Instead of using a browser-based File Manager, you use an SFTP program to connect to your hosting account and transfer files directly.
You'll usually need:
The server or host address
Your username
A password or SSH key
A port number
The connection details provided by your hosting service
Your hosting provider should give you these details and tell you which connection settings to use.
Once you connect, you'll normally see your computer's files alongside the files on the server. Find your website's root folder and upload your website files there, keeping the same folder structure.
SFTP is useful when you have many files to transfer or need to update your site regularly. It also encrypts the connection, which makes it a safer choice than traditional FTP when both options are available.
FTP vs. SFTP
FTP and SFTP both transfer files between your computer and a server, but they use different types of connections. FTP does not encrypt the connection. SFTP runs over SSH and encrypts the connection. If your hosting provider supports both, SFTP is generally the better choice because the connection is protected.
You don't need to use SFTP if your host's File Manager already does everything you need. It's simply another way to transfer files, and it can be more convenient when you manage files regularly.
Good to know: An SFTP client usually shows your computer's files on one side and the server's files on the other. The tricky part is knowing which folder on the server is the one your host uses for your website. Find that folder first, and transferring the files is straightforward.
How to upload a website with Git
Git is a tool for keeping track of changes to a project. If your website already lives in a Git repository, you may not need to manually upload files every time you make a change. Some hosting and deployment services can connect to your repository and automatically deploy the latest version of your site.
A typical workflow looks like this:
Put your website project in a Git repository.
Connect the repository to your hosting or deployment service.
Choose the branch and any required build settings.
Deploy the site.
Connect your domain.
After that, updating the site can be as simple as making a change, committing it and pushing it to the repository. The connected service can then detect the change and deploy the updated version.
This is useful if you're developing the site regularly. For a small website that you update only occasionally, manually uploading files may be simpler.
Worth knowing: Git takes more setup than a simple file upload, but that setup can save time when you update your site often. Once everything is connected, you can update the site without manually selecting and transferring the files each time.
Skip the deployment setup completely. Upload your build output to Wix Headless and your site goes live on a Wix URL in seconds.
How to upload a website created with an AI tool
AI tools can create websites in different ways. Some give you a ready-to-publish site, some give you finished website files and others give you a code project that needs to be built first. What you do next depends on which one you have.
01. The AI tool gives you a live website
If the AI tool gives you a website that is already hosted, you don't need to upload the files yourself. Use the tool's publishing settings and connect a domain if you want a custom web address.
If you create your site with the Wix Website Builder, the site is already hosted on Wix. You can make changes in the editor and click Publish when you're ready to make them live.
02. The AI tool gives you finished website files
If you receive a folder or ZIP containing a finished website, you can upload those files to a hosting service that supports them. This is the simplest case because the website is already built and ready to run.
Wix Headless lets you upload or drag in finished website files and deploy them to a live Wix URL. This can be useful if an AI or coding tool created the files but you don't want to set up a separate server or Git workflow.
03. The AI tool gives you a code project
If you receive a project with files such as package.json and src/, you may have the source code rather than the finished website. The project may need to be built first, which creates the files that can be put online.
The project may also require server-side code, a database or other services. In that case, you'll need a hosting setup that supports those requirements.
Wix Headless can work with coded websites, but the exact setup depends on the project and what it needs to run. If the project can be built into finished website files, those files can be uploaded through the Headless workflow. Projects that require server-side features need the appropriate Wix or external services as part of the setup.
Paste wix.com/headless/skill.md into Claude Code, Cursor or any AI tool you already use and your project is connected to the full Wix backend instantly.
Expert tip from Yoav Cohen, Head of Education for DevRel at Wix:
“We're seeing an entirely new kind of builder emerge, people who are highly capable with AI tools, move extremely fast, and have real product vision, but don't want to become infrastructure engineers. Wix Headless was built for them.”
How to upload a static website to Wix Headless
If you have a finished static website, Wix Headless lets you upload it directly and have Wix host it. This is useful if you created a site with code or an AI tool and have the finished website files but don't want to set up hosting separately. Wix hosts the files on a global CDN with automatic SSL and gives the project access to Wix business APIs.
01. Get the finished website files
Make sure you have the finished build output, not the development project. Wix serves the files as they are and does not build them for you. If your project needs server-side code, use the CLI deployment route instead of the static upload.
02. Upload the files
Go to the Wix Headless upload page and drag in your build output, or select a folder or ZIP file.Wix creates a new Headless project, hosts the files and publishes the site to a Wix URL.
03. Check the live site
Open the URL provided after the upload and test the pages, images, links, navigation and interactive features.
04. Keep developing if you need to
The upload is a starting point, not a dead end. After setting up the uploaded project locally, you can keep developing it and deploy updates with the Wix CLI. You can also connect the frontend to Wix services such as the CMS, ecommerce, bookings, events and memberships.
If you need a build process or server-side code, use the CLI route instead. Wix Headless can host and run supported existing frontends through that workflow.
Good to know: Wix Headless is free to start. Paid plans unlock features such as custom domains and live payments, so you can start building and testing before committing to a paid plan.
Do you need a domain and hosting?
They do different jobs, and domain hosting vs web hosting covers the distinction in full.
Your domain is the web address people use to find your website. Your hosting is where the website files are stored and served to visitors.
You can upload a website without having a custom domain. Your hosting provider may give you a temporary web address that you can use to test the site, then connect your own domain later.
Learn more: How to host an HTML file online
How to connect your domain to your website
Uploading your website and connecting your domain are separate steps. Uploading puts your files on the hosting service, while connecting your domain tells the internet where your website is hosted.
If your domain and hosting are with the same provider, you can often connect them from the provider's dashboard. If they're with different providers, your hosting service will give you the DNS settings to add where your domain is registered.
Tip: Test your site using the temporary hosting URL first. If the site works there but not on your domain, your website files are probably fine and the issue is with the domain connection.
Why isn't my uploaded website showing?
If your site doesn't look right after uploading, don't start over immediately. Most problems are caused by one of a few things.
01. You see a blank page
Check that your homepage is in the correct website root folder. If you're using a simple static site, check that index.html is there. Then check that your CSS and JavaScript files are in the locations your HTML expects.
02. You see a 404 error
A 404 means the server couldn't find the page you requested. Check these.
The URL
The page's file name
The folder structure
The website root folder
That the page was actually uploaded
If the homepage works but another page doesn't, check the path to that specific page.
03. The page loads but the design is broken
Your HTML may have uploaded correctly while your CSS or JavaScript did not. Check the paths in your HTML and make sure the corresponding files are on the server. File names can also cause problems. On many servers, style.css and Style.css are treated as different files.
04. Your images aren't loading
Check that the image files were uploaded and that their paths match the paths used in your HTML or CSS. For example, if your page refers to this image.
<img src="images/logo.png">then the server needs to have logo.png inside an images folder in the expected location.
05. You uploaded a ZIP and the site doesn't work
Check where the ZIP was extracted. You may have accidentally created an extra folder inside your website root.
website/
index.htmlIf the site expects index.html directly in the root, move the files up one level.
06. Your domain still shows an old site
The domain may still point to your previous hosting service, or DNS changes may not have finished updating. You may also be seeing a cached version of the site.
First, open the temporary URL from your hosting service. If the new site works there, the upload itself is probably fine and the issue is more likely related to the domain or DNS.
How it actually works: almost every problem on this list traces back to a path that does not match or a file that landed one folder off. Keeping your local folder structure and your server folder structure identical removes a whole category of problem before it happens.
How to check that your website is really live
Don't stop at seeing the homepage. Go through the site as a visitor would, and check that everything below works.
The homepage loads
Other pages open
Images and videos appear
Fonts and styling look correct
Navigation and links work
Buttons do what they should
Forms work
Downloads work
The site looks good on a phone
Your domain opens the correct site
HTTPS is working
It's also useful to open the site in a private browsing window. That reduces the chance that an old cached version is confusing your test. If HTTPS is not working, check that a free SSL certificate is active on your domain.
How to update your website after uploading it
You don't usually need to start the entire upload process again every time you change something. How you update the site depends on how you originally put it online.
With a File Manager, edit your files and upload the changed files.
With SFTP, replace the changed files on the server.
With Git, make your changes, commit them and push them to your repository. Your hosting service can then deploy the new version if it is set up for automatic deployment.
With a website builder, make your changes in the builder and publish again.
For a small site that changes occasionally, manually replacing files is perfectly reasonable. If you're making changes every week, a Git-based or automated workflow can save time because you don't have to keep track of which files need to be uploaded.
How to upload a website FAQ:
Can I upload a website without hosting?
Your website needs somewhere to be served from, so you need a hosting service or a platform that provides hosting. You don't necessarily need to buy traditional hosting separately. Some platforms combine the upload, hosting and publishing steps.
Can I upload a website without a domain?
Yes. You can often upload and test a website using a temporary URL provided by your hosting service. You can connect a custom domain later.
Do I need FTP to upload a website?
No. You can often use a hosting File Manager, SFTP, Git or another upload method instead. Some hosting providers still support FTP, and when both FTP and SFTP are available, SFTP is generally preferable because the connection is encrypted.
Can I upload a ZIP file instead of individual files?
Usually, yes. Many hosting File Managers let you upload a ZIP and extract it on the server. After extracting it, check the folder structure to make sure your homepage and other website files aren't hidden inside an extra folder.
How long does it take for an uploaded website to go live?
The files can often be available as soon as they're uploaded to the correct location. If you've also connected a new domain, the domain connection can take longer because DNS changes need time to update.
Can I upload a website created by an AI tool?
Yes, if the AI tool gives you website files that can be hosted by the service you're using. If you receive finished HTML, CSS, JavaScript and assets, you may be able to upload them directly. If you receive a development project that needs to be built first, follow the project's build and deployment instructions instead.
Can I upload a website to Wix?
Yes. Wix Headless supports uploading a finished static site and hosting it as a Wix-managed Headless project. You can upload a folder or ZIP of the finished build output, and Wix handles hosting, SSL and CDN delivery for that site. For a project that needs a build process or server-side code, Wix also provides a CLI-based deployment path for supported frameworks.
