How to Build a Website From Scratch
The fuller process for when you're ready to go beyond a free tier's limits.
Read the guide →
Free website tools are real and genuinely usable — but every one of them hides its limits until you hit them: a subdomain you didn't want, the platform's own branding stuck in your footer, a storage cap you discover mid-project. This guide isn't about finding "the best free website builder" (that list changes constantly) — it's about choosing a free platform with your eyes open, building so you don't paint yourself into a corner, and knowing exactly when upgrading stops being optional.
What you'll be able to do: Get a real, working website live using only free tools — and know exactly which limits you're accepting and when they'll start to matter.
Outcome: "I've picked a free platform knowing exactly what its free tier does and doesn't include, instead of finding out by surprise later."
Write down the three things you actually need your site to do this month — nothing more. A free platform only needs to cover those three things, not every feature you might eventually want.
Nearly every free website tier shares the same four trade-offs, and they're worth knowing before you build rather than after: a free subdomain instead of your own domain name (yoursite.platform.com, not yoursite.com), the platform's own branding somewhere on the page (usually a footer badge you can't remove without paying), limits on storage and monthly visitors (fine for a small personal or portfolio site, a real constraint for anything with photos, video, or growing traffic), and a reduced set of templates, plugins, or features compared to the paid tiers. None of these make the free tier bad — they make it fit certain situations (a portfolio, a hobby project, a test before committing) and not others (a store, anything client-facing where a stuck-on badge looks unprofessional, a site expecting real traffic). Decide which situation you're actually in before picking a tool, not after you've already built three pages in one.
A student building a portfolio to show in job interviews: the subdomain and badge are a minor cosmetic cost, traffic will be low, free tier fits fine. A local business owner trying to look established and take payments: the subdomain and badge actively undermine the goal — this is a case where "free" isn't actually free once you account for what it costs the business in credibility.
Outcome: "I've built a lean, working site that doesn't quietly depend on features that only exist on the paid tier."
List the pages your site needs using the smallest possible number — most free sites need three pages (Home, About or Offer, Contact), not ten.
The biggest free-tier trap isn't a hard limit — it's building half a site around a feature (a contact form with conditional logic, a members area, an online store) only to discover it's locked behind a paid plan once you try to publish. Avoid this by checking which specific features your free tier actually includes before designing around them, not after. Keep the page count minimal: fewer pages means less chance of silently running into a storage or page-count cap, and a smaller site is also easier to rebuild elsewhere later if you do outgrow it. Use the platform's own built-in contact method (a simple form or a mailto: link) rather than trying to bolt on a third-party tool that may need a paid integration to work properly. Images are usually the fastest way to hit a storage cap — compress images before uploading rather than uploading originals straight from a phone or camera.
Someone builds three pages and a contact form, then discovers at publish time that the form's email notifications are a paid-only feature on their chosen platform — meaning submissions arrive with no alert. Checking this on day one (per Chapter 1) would have avoided a wasted afternoon; the fix now is switching to a plain mailto: link instead, which works on every tier.
Outcome: "I can recognize the specific signs that mean it's time to pay, and I know how to move without losing what I've already built."
Check your current site against one question: has anyone ever commented on the subdomain or the platform badge, even once? If yes, that's your first real signal.
Four signals reliably mean it's time to upgrade, and none of them are "I feel like it should look nicer": you need a real domain name because the subdomain is costing you credibility (client-facing work, anything selling something), you've hit the storage or visitor cap and the site is actually failing to load for some visitors, you need a feature that's genuinely paid-only and there's no free workaround (e-commerce checkout, a members area), or the free branding is actively confusing visitors about who runs the site. When you do upgrade, most platforms let you move within the same tool — same pages, same content, just unlocked limits and a connected custom domain — which is simpler than migrating to a different platform entirely. If you do switch platforms, export your content first (text and images, saved locally) so a slow new build doesn't mean retyping everything from scratch.
A free portfolio site starts getting genuine client inquiries through the contact form — at that point, the subdomain and badge are costing credibility with exactly the people the site is meant to convince, which is the specific "is it hurting me" signal that justifies paying, rather than upgrading just because a bigger plan exists.
The complete guide — all 3 chapters, every checklist and exercise — as a clean, printable PDF. No email required.
Every guide on this site is produced with the Self-Directed Learning Framework: instead of an article that explains a topic at you, the framework turns it into a structure you work through — each chapter with one outcome, a starting action under twelve minutes, the minimum you actually need to know, a worked example, a checklist, and exercises. It starts from three questions:
Topic: Building a website using only free tools.
Outcome wanted: Have a real, working free website live, and know exactly when upgrading would actually be worth it — within three days.
Starting point: No budget to spend yet — wants to start free and understand the trade-offs before committing to anything paid.
The prompt framework behind it is public: see the C.R.A.F.T. prompt framework, including the exact prompt that generated this library.
The fuller process for when you're ready to go beyond a free tier's limits.
Read the guide →Free, self-paced guides across everyday, professional and academic topics.
See all guides