How to make and host a simple band website yourself

You can build a band website yourself without paying for hosting or wrestling with a CMS. Use a static site generator like Jekyll or Hugo, host it for free on Netlify or GitHub Pages, and point a cheap domain at it. The whole thing can be done in an afternoon, and it will load fast, cost almost nothing, and never go down because of a database crash.

Why static sites make sense for bands

A static site is just a folder of HTML, CSS and image files. There is no database, no admin panel, no PHP to update. That means fewer things to break and nothing to hack. For a band, that is ideal: you are not running a forum or a shop, you are putting up a few pages that change when you have a new record or a tour.

Static sites are also cheap or free to host. Because they are just files, any static host will serve them happily. And they are fast – no server-side processing means pages load instantly, even on a bad venue Wi-Fi.

Step 1: Choose a static site generator (or go plain HTML)

You do not need a generator. If you are comfortable writing HTML by hand, a few files will do. But a generator saves time when you want a consistent header, footer and list of shows.

Jekyll – the old faithful. Works well with GitHub Pages, lots of themes.
Hugo – extremely fast, single binary, good for larger sites.
Eleventy – simpler, JavaScript-based, good if you already know a bit of JS.

Pick one, install it locally, and run its starter template. You will write your content in Markdown files, which are just text with a few symbols for headings and links.

Step 2: Get a domain name

A domain is your address on the web. You do not strictly need one – your host will give you a free subdomain like yourband.netlify.app – but a proper domain looks more professional and is easier to remember.

Expect to pay €10–15 per year for a .com, .net or .org. Some country codes (like .se or .no) cost more. Register with a reputable registrar; Cloudflare Registrar sells at cost, and Gandi and Namecheap are common choices. Avoid anything that bundles “free” hosting with a domain – you will regret it.

Once you have the domain, you will point it at your host by changing DNS records. Your host will give you instructions.

Step 3: Host it for free

Several services host static sites for free, with generous limits:

Netlify – drag-and-drop deploy, free SSL, easy custom domain setup.
GitHub Pages – free for public repositories, integrates with Jekyll.
Cloudflare Pages – fast, free, good if you already use Cloudflare for DNS.

All of these offer HTTPS (the padlock) automatically. You do not need to pay for a certificate.

To deploy, you either connect your Git repository (if you use one) or drag your built site folder into the host’s dashboard. The site goes live in seconds.

Step 4: What to put on the site

A band website does not need to be fancy. It needs to answer the questions people actually have: who are you, what do you sound like, where can I hear it, when are you playing, and how do I book you?

Essential pages

Home – a short intro, latest news (new record, tour dates), and links to listen.
Music – embed Bandcamp or SoundCloud players, or link to Spotify/Apple Music. Include lyrics? Maybe, but not required.
Shows – a list of upcoming gigs with dates, venues and ticket links. Keep it updated; an out-of-date shows page is worse than none.
About – band bio, member names (or pseudonyms), formed year, city, genre. Keep it short.
Contact – an email address for bookings and press. A contact form is nice but not necessary; a plain email link works.
Press kit – a downloadable zip with high-res photos, logo, bio and technical rider. This is what promoters and journalists want.

Optional but useful

Merch – link to your Big Cartel or Bandcamp merch page rather than building a shop.
Blog – tour diaries, recording updates. If you will not update it, skip it.
Mailing list – a simple signup form (Mailchimp free tier) to tell people about new releases.

Step 5: Keep it simple and DIY

The best band websites are plain, fast and easy to update. Do not embed a Facebook feed (it breaks), do not autoplay music, and do not use a page builder that locks you in. Write your content in Markdown, keep images compressed, and update the shows page when you confirm a gig.

If you want to go further, you can version your site with Git and deploy automatically on every push. That is the same workflow used by software teams, and it fits the DIY punk ethic nicely – see our piece on punk and free software for more on that connection.

For inspiration on the early web’s homemade approach, read Punk on the early web: webrings, guestbooks and homemade HTML. And if you are also thinking about releasing music yourself, our guide to starting a small DIY punk label covers tapes, vinyl and distro.

FAQ

What is a static site generator?

A static site generator is a tool that takes plain text files and templates and turns them into a ready-to-upload website. Popular ones include Jekyll, Hugo and Eleventy.

Can I host a band website for free?

Yes. Services like Netlify, GitHub Pages and Cloudflare Pages offer free tiers for static sites. You only pay for the domain name, which typically costs around €10–15 per year.

Do I need to know how to code to make a band website?

Not necessarily. Static site generators often have themes you can customise with minimal coding. However, basic HTML and Markdown skills help.

What should I put on my band's website?

Essential pages: a homepage with latest news, a music section with embedded players or download links, a list of upcoming shows, a contact page, and a press kit with bio and photos.