A static website is a site made of ready-made files (HTML, CSS, JavaScript, images) that the server sends to every visitor exactly as they are stored. Nothing is assembled on the server when someone loads a page, so there is no database query and no application code running per request. If you are asking what is a static website because someone suggested one for your business, the short answer is: it is the simplest, fastest and most secure way to publish pages that do not change for each visitor.
That simplicity has trade-offs. Below we explain how static sites work, what they are good at, where they struggle, and what you need to build, host and maintain one.
What is a static website, exactly?
Every web page you see in a browser is HTML. The difference between site types is when and where that HTML gets made.
On a static website, the HTML for each page already exists as a file before anyone visits. Your about page might literally be a file called about/index.html sitting on a server. When a visitor requests that address, the web server finds the file and sends it. The same file goes to everyone.
On a dynamic website (WordPress, Shopify, most web apps), the server builds the page at request time. It runs code, pulls content from a database, applies a theme and then sends the result. Caching can make a dynamic site behave a lot like a static one, but the machinery underneath is still there.
“Static” does not mean the page cannot move or respond. A static page can have animations, sliders, embedded videos, a booking widget or a contact form that posts to an outside service. JavaScript runs in the visitor’s browser just as it would on any other site. “Static” only describes how the server delivers the page, not how lively it looks.
How a static site gets made
There are three common ways static sites are produced, and knowing which one you have matters when it is time to make changes.
Hand-coded HTML
A developer writes each HTML file directly. This is fine for a one-page landing page or a small brochure site with a handful of pages. It becomes painful as the site grows, because shared elements like the header and footer are copied into every file. Changing the phone number in the footer means editing every page.
A static site generator
A static site generator (Hugo, Jekyll, Eleventy and Astro are well-known examples) lets you write content in simple text files, often Markdown, and keep shared parts like headers in templates. You run a build command and the generator outputs a folder of plain HTML files. You upload that folder. The visitor still receives static files; the generator just saves the developer from repeating themselves.
An export from another tool
Some design tools and website builders can export a site as static files, and some teams take a dynamic site and export a static snapshot of it. This works, but check that the export includes everything: forms, redirects, the sitemap and any scripts the pages rely on.
What static websites are good at
Static sites have real strengths, which is why they remain popular for marketing sites, documentation, portfolios and campaign pages.
- Speed. There is no server-side processing per request, so the server can respond very quickly. Put the files behind a CDN and pages can be served from a location close to the visitor. Fast pages help with Core Web Vitals and with keeping visitors around.
- Security. No database and no login page on the server means far fewer things to attack. There are no plugins to patch and no admin panel to brute-force. You still need to keep the server itself updated and protected, but the attack surface is much smaller.
- Stability under traffic. Serving a file is cheap. A static landing page can usually handle a spike from a launch, an email blast or a mention in the press without the server falling over.
- Low maintenance. There are no core, theme or plugin updates to run each month. A static site that works today keeps working.
- Easy backups and version control. The whole site is a folder of files. You can keep it in Git, roll back any change and copy it to a new server in minutes.
Where static websites fall short
The limitations are just as real, and they are usually what decides whether static is right for you.
- Editing needs a developer or a workflow. There is no built-in dashboard where a marketing person logs in and edits a page. Changes mean editing files and redeploying. You can bolt on a headless CMS to give editors a friendly interface, but that adds setup and cost.
- No server-side features out of the box. User accounts, member areas, carts, search across thousands of products and anything personalised per visitor need a backend. You can connect third-party services for forms, comments, search or payments, but each one is another dependency.
- Forms need somewhere to go. An HTML form on a static page has no server code to receive it. You either point it at a form-handling service, an automation tool, or a small serverless function.
- Large, frequently updated sites get awkward. A news site publishing many times a day, or a store with a large catalogue, will spend a lot of time rebuilding and redeploying. A dynamic CMS handles that more naturally.
If you are weighing these points against a CMS like WordPress, our guide to static vs dynamic websites walks through the decision criteria side by side.
Common examples of static websites
If you are still picturing what is a static website in practice, it helps to look at real use cases. Here are sites that are often built static and work well that way:
- A one-page product or app landing page with a signup form.
- A consultant’s or coach’s site with five to ten pages that change a few times a year.
- A webinar or event registration page expecting a burst of traffic.
- Product documentation or a help centre written by developers.
- A personal portfolio or a resume site.
- A “coming soon” page or a microsite for a single campaign.
What these have in common: the content is the same for every visitor, it changes on a human timescale (days or weeks, not seconds), and there is no need for visitors to log in.
What you need to run a static website
A static site needs less than a CMS site, but it still needs a few things done properly.
- The files. A folder of HTML, CSS, JavaScript and assets, either hand-written or output by a generator. Keep the source (templates, Markdown, build config) in version control, not just the output.
- A domain and DNS. Point your domain at the server or CDN that hosts the files.
- A web server or static host. A server running Nginx or Apache can serve static files very efficiently. The key settings are correct caching headers, compression and clean URLs (so
/about/works without.htmlon the end). - SSL. Every site needs HTTPS. Certificates are free to obtain and should renew automatically.
- A deploy process. Decide how changes get from your computer to the live server. That might be a simple upload, or an automated build that runs whenever someone pushes to a Git repository.
- Redirects and a 404 page. Static servers will not handle redirects for you automatically. They live in the server config. A helpful custom 404 page is a file you create.
- Backups. Even with Git, keep an off-site copy of the live files and the server config.
Search visibility needs its own attention too, because you do not get an SEO plugin. Titles, meta descriptions, sitemaps and structured data are all things you or your generator must produce. We cover that in detail in our guide to SEO for a static website.
Mistakes we see with static sites
Knowing what is a static website is half the job; running one well is the other half. Most static site problems are not about the technology. They come from treating “static” as “set and forget” on things that still need care.
- Losing the source. A freelancer builds the site with a generator, hands over only the output folder, and the next person has to edit generated HTML by hand. Always get the source files and build instructions.
- No caching rules. Without proper cache headers, browsers re-download CSS and images on every visit, which wastes the speed advantage.
- Forms that silently fail. The form-handling service changes, a key expires, or spam filtering eats the messages. Test your forms on a schedule, not just at launch.
- Broken links after a restructure. Renaming a folder changes URLs. Without redirects, old links and search results lead to 404s.
- Heavy JavaScript. Some modern frameworks ship a lot of JavaScript even for simple pages. The site is technically static but still slow on phones. Check what the browser actually downloads.
Is a static website right for your business?
A static site is usually a good fit when most of these are true: your content is the same for every visitor, you update it occasionally rather than daily, you do not need user accounts or a store on the same site, and you either have a developer available for changes or are comfortable editing files yourself.
It is usually the wrong fit when non-technical team members need to publish often, when you need e-commerce or memberships, or when you rely on a large plugin ecosystem for features.
If static sounds right but you do not want to manage servers, certificates and deploys yourself, you can have us host your HTML or static site on a tuned Nginx setup with SSL, Cloudflare and off-site backups. Questions can go to support@growthscribe.com.
FAQ
What is a static website in simple terms?
A static website is a collection of pre-built files that the server sends to every visitor exactly as they are saved. No page is assembled from a database at the moment someone visits, which is why static sites are fast and have little to attack.
Can a static website have a contact form?
Yes. The form itself is plain HTML, but because there is no server code to receive it, you send the submissions to a form-handling service, an automation tool or a small serverless function. Test it regularly so messages do not get lost.
Is WordPress a static website?
No. WordPress is a dynamic content management system that builds pages from a database using PHP. Page caching can make it serve pre-built copies of pages, and some tools export WordPress as static files, but a standard WordPress install is dynamic.
Do static websites need hosting?
Yes. The files still have to live on a web server or static host connected to your domain, with SSL, caching rules, redirects and backups set up. Static hosting is simpler than hosting a CMS, but it still needs to be configured properly.
