What Is a Static Site?

A static site is a website made of files that already exist. When someone visits a page, the server hands them the finished file. That’s the whole transaction. Nothing is assembled, no database is queried, and no software runs to produce the page you’re looking at.

If someone recently told you to look into static sites and you’re trying to work out what they meant, that paragraph is the answer. The rest of this is what follows from it, including the parts the term gets wrong.

What happens when you visit a page

The difference is easiest to see by comparing the two paths a request can take.

On a static site: your browser asks for a page. A server somewhere finds the file and sends it. Done.

On a CMS like WordPress: your browser asks for a page. The server starts a PHP process, loads WordPress, loads your theme, loads every active plugin, runs several dozen database queries to find your content and settings, assembles the HTML, sends it, and discards everything it just built. The next visitor triggers the same work over again.

That second path is why WordPress sites need caching plugins, why they need more expensive hosting as traffic grows, and why they slow down when you add functionality. The site is doing real work on every single request, and everything you add is more work.

The assembly moves to before the visitor arrives instead of during. Everything else follows from that one change.

”Static” is a bad name, and it has cost this approach a decade

I’ll take a position here that not everyone shares: the word is actively misleading, and it’s the main reason business owners dismiss the idea before understanding it.

“Static” sounds like it means unchanging, primitive, or hand-coded. People hear it and picture a 1998 brochure page they’d have to email a developer about every time a phone number changed. That picture is wrong, and it stops the conversation early.

The industry has tried to rename it twice. “Jamstack” arrived around 2016 and mostly confused people who didn’t already know what it meant. Some people now say “pre-rendered,” which is more accurate and less catchy. None of it stuck, so we’re left with a name that describes how the file is delivered and says nothing about what the site can do.

What “static” actually refers to is one narrow thing: the page is not rebuilt per visitor. That’s it.

What a static site generator does

Here’s the part that gets missed, and it’s the part that makes the whole thing practical.

Nobody hand-writes a hundred HTML files. You use a static site generator, which is software that runs on your computer or on a build server. You write content in one place, define your layout once, and the generator produces all the finished pages before anyone visits.

Astro, Eleventy, Hugo, and Jekyll are the common ones. This site runs on Astro.

So in practice:

• Your navigation lives in one file. Change it once, every page updates.
• Your content lives in text files or in a content editor, separate from the design.
• Publishing is one action, the same as hitting Publish in WordPress.
• A blog post you write today gets its own page, its category archive, its tag pages, and an updated sitemap, all generated automatically.

What static sites can and can’t do

The honest version, because the limits are real and worth knowing before you get talked into anything.

The pattern underneath both lists: if a page needs to show something different to different people at the same moment, static is the wrong tool. If a page shows everyone the same thing until you change it, static is the right one.

Most business websites are the second kind. Forty pages that change a few times a year.

Why anyone bothers

Three things, and they’re all consequences of the same architectural change.

Speed. There’s no work left to do when the request arrives, so the page arrives in whatever time the network takes. Sites I’ve rebuilt this way have gone from Lighthouse performance scores in the 40s to the high 90s with the same content and the same images. Nothing clever happened. The pages just already existed.

Cost. Serving files is cheap enough that Cloudflare Pages, Netlify, and Vercel give it away at small business scale. These are production-grade platforms with global CDNs, not throttled trials. A WordPress site running $1,500 to $4,000 a year once hosting, licensing, security, and maintenance are counted becomes a hosting line item of zero.

Attack surface. No database to inject, no admin login exposed to the internet, no plugins written by strangers. The automated probes still arrive, because they arrive for every domain that exists. A low-traffic site I run behind Cloudflare blocked 1,170 malicious requests in a single day against roughly 15 real human visitors. On a static site those requests hit URLs that were never there and find nothing to try.

I want to be careful with that last one. Static sites are not unhackable. Your domain registrar, your hosting account, and your build pipeline all still need protecting, and a compromised laptop is a compromised laptop regardless of architecture. What goes away is the specific path that compromises most small business sites, which is an outdated plugin nobody was watching.

Who actually uses these

Worth knowing, because “static” makes it sound niche.

Most documentation sites you’ve read this year are static. Most developer tool marketing sites. A large share of news and publishing front-ends, which rebuild continuously. Government service pages. The overwhelming majority of small business sites built in the last five years by anyone paying attention to performance.

It’s a mainstream way to build a website that happens to carry a name suggesting otherwise.

When you should not use one

If you run a membership site, a store with real inventory management, a job board, a booking engine tied to live availability, or a newsroom with a dozen people publishing through the day, a database-driven CMS is the correct tool and I’d tell you so.

WordPress is not bad software. It runs a large share of the web and it does its job. The mismatch is that most business websites are a few dozen pages that change a few times a year, running infrastructure built for something much larger, and paying for that every month.

Frequently Asked Questions

What is a static website in simple terms?

It's a website made of finished files. When you visit a page, the server sends you a file that already existed instead of building the page on the spot. That makes it load faster and cost less to run. You still edit and publish content normally. The pages get built after you publish rather than when a visitor arrives.

What's the difference between a static site and a dynamic site?

A dynamic site assembles each page when it is requested, usually by querying a database. A static site serves a page that was assembled earlier. The practical difference is that dynamic sites can show different content to different people at the same moment, and static sites show everyone the same page until it is rebuilt.

Are static sites still used in 2026?

Yes, extensively. Most documentation sites, most developer tool marketing sites, many news front-ends, and a large share of small business sites built recently are static. The approach is more common now than it was a decade ago, because build tools got good and free CDN hosting became widely available.

Can a static site have a blog?

Yes. Blogs are one of the most common uses. You write a post, and the generator produces the post page, updates the index, regenerates category and tag archives, and updates the sitemap and RSS feed. This site runs that way. The workflow feels the same as any CMS.

Do static sites work for e-commerce?

For a modest catalog, yes, using Stripe or Shopify's embeddable checkout. For a store that needs live inventory counts, complex variants, or per-customer pricing, a dedicated commerce platform is the better tool. The dividing line is whether product data has to be correct in real time.

Do I need a developer to update a static site?

No, if it is set up with a git-based editor like Keystatic. You get an admin panel for text and images that works like a normal CMS. Without one, updates mean editing text files, which some owners prefer and others don't. Decide which you want during the build rather than after.

If you came here because you’re weighing this against a site you already have, the practical questions are covered elsewhere: what it takes to rebuild an existing WordPress site as a static site, what running WordPress actually costs per year, and whether you need a content management system at all.