Once a site is ready on a developer's computer, it is only visible on that computer. For the whole internet to see it, a few steps need to happen: from buying a domain to uploading files to a hosting server. Here is the whole path explained in order, so it becomes clear what happens at each stage and why, and which mistakes most often delay a launch by a day or two.
What the site's path to the internet consists of
Publishing a site is not a single action but a chain of several independent parts: the domain (the site's name), DNS (the directory that links the name to a server address), hosting (the server where the site's files live), and finally the files themselves, uploaded to that server. Each part can belong to a different company, and that is normal — what matters is that they are correctly linked together.
If even one link in the chain is set up incorrectly, the site will not open fully or will behave unstably, even if the other parts are fine. That is why developers usually check each stage separately before moving to the next one.
What to prepare before publishing
Before uploading files, it is worth gathering a few things.
- Domain — a unique site name registered with a domain registrar.
- Hosting or server — the place where the site's files will physically live and the database will run.
- Site files — the finished code, built and tested locally before the move.
- FTP or SSH access — the login and password the host issues for uploading files to the server.
Comparing the stages of publishing a site
Each stage solves its own task and happens in its own place, even though from the user's point of view it looks like one process.
| Stage | What happens | Where it happens | Result |
|---|---|---|---|
| Domain registration | the site name is secured for the owner | at a domain registrar | the domain belongs to you |
| DNS setup | the domain points to the server's IP address | in the DNS zone panel | the browser finds the right server |
| Ordering hosting | space on a server is allocated for the site | at a hosting provider | the server is ready to receive files |
| Uploading files | the site code is copied to the server | via FTP, SSH, or a control panel | the site is physically on the server |
A detailed guide to setting up DNS records for a domain is in the article about configuring DNS, and how the domain name system works overall is covered in the article about how DNS works.
How to upload a site to hosting in practice
Once the domain and hosting are ready, the files still need to be moved to the server.
# Example upload over SFTP from a terminal
sftp user@server.example.com
put -r ./public_html /home/user/public_htmlThe put -r command recursively copies the entire site folder to the server, preserving the subfolder structure. Instead of a terminal, a graphical FTP client can be used — the principle is the same: enter the server address, login, and password, then drag the files into the right directory.
What to do step by step to get the site working
- Register a domain with a registrar if it is not bought yet, and make sure it is registered to you.
- Order a hosting plan that fits the expected size and load of the upcoming site.
- Set up NS records or an A record for the domain pointing to the hosting server's IP address.
- Upload the site files to the server via FTP, SFTP, or the hosting control panel.
- Check that the site opens both by domain name and by IP address separately, to confirm DNS has already updated.
If the domain is not bought yet, the registration process from scratch is described in the article about registering a domain.
Frequently asked questions
How do you upload a site to hosting once it is ready locally?
The site files need to be uploaded to the server via FTP, SFTP, or the file manager in the hosting control panel, and then the database on the server needs to be set up the same way as the local copy. After uploading, it is worth checking the site by the server's IP address without waiting for DNS to update.
How long does DNS take to update after changing the server?
The time depends on the TTL value in the DNS record and can take anywhere from a few minutes to a day, rarely longer because of caching at internet providers. Until DNS updates, some visitors may see the old version of the site while others already see the new one.
Can a site be uploaded to hosting without its own domain?
Yes, most hosts issue a temporary technical address like account.hostingpanel.example, through which the site is reachable right after the files are uploaded. That is convenient for testing, but a domain will still be needed for ongoing operation.