A finished website sitting on your own computer isn’t accessible to anyone else — hosting and a domain are what make it genuinely public. This guide covers what each actually does and how they connect.
If you’ve worked through our guides on how websites work and web browsers, hosting and domains are the missing piece: where a site’s files actually live, and how visitors find them.
Web Hosting: Where Your Files Actually Live
According to MDN’s guide to publishing a website, web hosting is rented file space on a hosting company’s server — you upload your website files there, and the server delivers that content to visitors whenever they request it.
Domain Names: The Human-Readable Address
According to WPBeginner’s explanation of domains and hosting, a useful analogy: if a domain name is your house’s address, web hosting is the actual house that address points to. When someone types your domain into a browser, it’s translated into the IP address of the server actually hosting your files — the same DNS lookup covered in our guide on how websites work.
Why They’re Often Bought Separately (But Don’t Have To Be)
You can buy a domain and hosting from the same company, or from two different ones entirely. If they’re separate, a small extra setup step is required: pointing your domain’s nameservers to your hosting provider, so visitors typing your domain actually land on your hosted files rather than nowhere. Many hosting providers include a free domain for the first year when you sign up, which is a convenient way to avoid this extra step as a beginner.
Free Hosting Options for Learning Projects
According to MDN, several free services — like GitHub Pages, Netlify, and similar platforms — work well for initial experiments and learning projects, even though they’re more limited in scope than paid hosting. For the static HTML/CSS/JavaScript projects covered throughout this series, a free option is genuinely enough to get a real project online without any cost.
Types of Hosting
- Shared hosting — affordable, beginner-friendly, your site shares server resources with others.
- VPS hosting — more dedicated resources and flexibility, a step up once traffic or requirements grow.
- Static hosting (GitHub Pages, Netlify) — free or low-cost, ideal for HTML/CSS/JS-only projects without a backend.
Anatomy of a Domain Name
A domain like blog.example.com breaks into parts: .com is the top-level domain (TLD), example is the second-level domain — typically your brand or project name — and blog is a subdomain, letting you organize different sections under the same main domain, like shop.example.com or blog.example.com.
How Files Actually Get Uploaded to a Server
According to MDN’s guide to publishing a website, companies use various mechanisms for transferring files to their web servers — common options include a drag-and-drop web interface, an FTP (File Transfer Protocol) program, or, increasingly, deploying directly from a Git repository. This last option is why services like GitHub Pages have become so popular for learning projects: pushing to a Git repository, using the same commands covered in our Git basics guide, is often all that’s needed to publish or update a live site, without a separate manual upload step.
SSL Certificates and HTTPS
As covered in our HTTP and HTTPS guide, a valid TLS/SSL certificate is what enables the encrypted HTTPS connection browsers now expect from every site. According to a beginner’s guide to web hosting from Liquid Web, security — including a valid SSL certificate — is a key factor search engines and browsers both weigh when determining trust and rankings, which is exactly why most modern hosting providers, including free ones like GitHub Pages, issue and renew these certificates automatically at no extra effort from you.
Choosing a Domain Name
A few practical guidelines make a domain name genuinely more usable: keep it short and easy to spell out loud, avoid hyphens and numbers where possible (since they’re easy to mishear or mistype), and choose a TLD that matches your project’s purpose — .com remains the most broadly recognized default, though options like .dev or .io have become common specifically within tech and developer projects.
Common Questions
Do I need to buy a domain to start learning web development? No — free hosting platforms typically provide a subdomain (like yourproject.github.io) at no cost, perfectly sufficient for practice projects and portfolios while you’re learning.
Can I switch hosting providers without losing my domain? Yes — you own your domain independently and can point it to any hosting provider by updating its DNS settings, without needing to purchase a new domain.
Quick-Reference Guide
- Web hosting — rented server space where your website’s files actually live.
- Domain name — the human-readable address pointing to your hosted files.
- Nameservers — connect a domain to a hosting provider when purchased separately.
- Free hosting — GitHub Pages and similar services, great for learning projects.
- TLD / SLD / subdomain — the structural parts of a domain name.
Conclusion
Hosting and domains are the final piece connecting everything covered throughout this Web Development Fundamentals series — HTML, CSS, JavaScript, and the request/response cycle all lead to this moment: a real, publicly accessible website anyone can visit by typing an address.
In the next guide in this series, we’ll cover version control with Git in the context of web projects specifically, tying together deployment and the version control concepts from our Tools & Setup series.
Explore More Web Development Guides →
When not writing, Alex is probably debugging someone else’s code.