Website types · 12 Nov 2026 · 6 min read
Static website vs dynamic website: how they differ and which to choose
The difference is when a page gets built: ahead of time, or at the moment a visitor asks for it.
The short answer
A static website serves ready-made pages exactly as built, so every visitor gets the same files. A dynamic website builds each page when it is requested, using code and a database, so content can change by visitor, time or action. Static suits simple, rarely changing sites. Dynamic suits logins, shops, bookings and frequent updates.
Static website vs dynamic website in short
In a static website vs dynamic website comparison, the question is when each page gets built. A static site builds its pages ahead of time and stores them as finished files. A dynamic site builds each page at the moment a visitor asks for it. Everything else in this guide follows from that one difference.
What is a static website?
A static website is made of finished files: HTML pages, style sheets, scripts and images. Each page exists as a file before any visitor arrives. When someone asks for it, the server finds the file and sends it unchanged. Every visitor gets the same page.
The word describes how the page is delivered, not how it looks. A static page can contain animation, video and interactive menus. Static files may be written by hand or produced by a static site generator, a tool that takes templates and content and builds all the pages in one go. Changing a page means editing the source, rebuilding if a generator is used, and uploading the result.
What is a dynamic website?
A dynamic website builds pages when they are requested. Code on the server reads content from a database, fills in a template and sends the finished page. The same address can show different things depending on who is asking, what they searched for or what is in stock.
Most sites that run on a CMS or an online shop platform are dynamic. Logins, shopping baskets, search results, booking calendars and member areas all need this kind of page-building. An admin area lets staff change content without touching code.
Static vs dynamic: what happens when someone clicks
Both begin the same way, with the browser asking for a page. The routes then part.
| Point | Static website | Dynamic website |
|---|---|---|
| What the server does | Finds a ready-made file | Runs code that builds the page |
| Where the content lives | In the page files | In a database |
| What differs per visitor | Nothing, unless the browser adds it afterwards | Anything the code decides: language, basket, login |
| When a content change appears | After the files are rebuilt and uploaded | As soon as the database is updated, subject to caching |
Static website vs dynamic website: side by side
| Point | Static | Dynamic |
|---|---|---|
| Speed potential | Quick to deliver, since nothing is built per visit | Fast when well built and cached, slower if every visit does heavy work |
| Hosting | Simple file hosting is enough | A server that runs the site's software, plus a database |
| Security | Fewer moving parts, though the hosting account and any outside services still need protecting | More software to keep updated, and the admin area and plugins need care |
| Editing | A developer, or an editing tool built on top | Staff edit in an admin area |
| Features | Content-led pages, with extras from outside services | Logins, search, baskets, bookings, personalisation |
| Traffic spikes | Serving files is light work | Needs capacity or caching planned in advance |
| Upkeep | Less software to update, but each change needs a build step | Regular updates, backups and monitoring |
Neither type gets an advantage in search by itself. What matters is content that search engines can read, a sensible structure and good speed. Check Google's current documentation for the details rather than assuming one type ranks better.
The middle ground: static pages with dynamic parts
The choice is rarely all or nothing. Many sites serve static pages and add live pieces from outside services: a contact form handled by a form service, a booking widget, a payment page hosted by the provider, site search run by a separate service, or comments loaded from another system. The page is static but the features are live.
A dynamic site can also be made to behave much like a static one. Built pages are stored and served from a cache, so visitors rarely wait for the code to run. The labels matter less than four practical points: who edits the site, how often it changes, which features need live data and what can be built ahead of time.
Which one suits a small business?
For many small businesses the decision comes down to two questions: who will edit the site and how often, and does it need live features. If editors are not technical and publish often, a dynamic CMS is usually easier to live with. If the content is stable and the site is mainly information, static can be simpler to secure and cheaper to run. Whether it is cheaper to build depends on the tools and the team.
| Business | Likely fit | Why |
|---|---|---|
| A consultancy with a few pages that change twice a year | Static, or a simple CMS | The content rarely changes, so speed and low upkeep come first |
| An architecture studio showing a portfolio | Static or dynamic | Image-led, and either works if the images are prepared well |
| A café whose menu changes every week | Dynamic with a CMS, or static with an easy editing tool | Staff need to edit without calling a developer |
| A training provider with a booking calendar | Dynamic, or static with a booking service | Availability changes constantly |
| An online shop | Dynamic, or a hosted store platform | Baskets, accounts, stock and orders need live data |
| A membership site | Dynamic | Logins and personal content |
| A company blog with frequent posts | Either | It depends on who publishes and how often |
| A site in several languages | Either, with more planning | Translated content has to be managed |
Language is worth planning early on both types. The guide to planning a multilingual website covers the decisions to make before the build.
Images, navigation and structure on each type
Oversized images are a common cause of slow pages on both types. On a static site, images are prepared before they are uploaded, and the guide to sizing and compressing website images covers the steps. A dynamic site may resize images automatically, but the originals still need to be sensible.
Navigation behaves differently. On a static site the menu is often part of a shared template, so changing it means editing the template and rebuilding. A CMS usually lets an editor reorder items in an admin screen. Either way, what the menu should contain is a separate question, and website navigation and menu structure explains how to decide.
Moving from one type to the other
Changing type later usually means a rebuild rather than a redesign, because the way pages are produced changes along with how they look. The guide to website redesign vs rebuild explains the difference and how to decide.
Before you commit, ask each supplier to state which type they propose, and why, and to list the ongoing tasks it involves. When you compare website development quotes, check that quotes for static and dynamic builds are comparing like with like, because they often include different things.
Questions to ask your developer
- Is the site static, dynamic or a mix, and why?
- Who will edit content, and how?
- Which features need live data, and where does it come from?
- What needs updating regularly, and who does it?
- What happens to our content if we change platform later?
- How are forms handled, and where do the entries go?
A team that builds both types should be able to explain the trade-offs without steering you towards one. The website development page from Liftup Technologies describes the work it covers.
Related guides
- Wordpress website vs custom website
- Website caching explained
- Wordpress website vs custom website
- Website search box when your site needs one
Questions and answers
What is a static website?
A static website is built from finished files that the server sends exactly as they are, so every visitor sees the same page. The pages may be written by hand or produced by a static site generator, and they can still include animation and interactive menus.
What is a dynamic website?
A dynamic website builds each page when it is requested, using code and usually a database. This lets content change by visitor, time or action, and it supports logins, baskets, search and bookings. Most sites on a CMS or shop platform are dynamic.
Which one suits a small business?
A site with stable content and no live features suits static or a simple CMS. A site that staff update often, or that needs bookings, accounts or a shop, suits dynamic. Who edits the site and what must be live decide it.
Is a static website faster?
Often it is quick to deliver because pages are ready-made, but speed also depends on images, scripts and hosting. A well-built dynamic site with caching can feel just as fast, and a static site with heavy images can be slow.
Is a static website more secure?
It has fewer moving parts, because the public server holds no database or admin software. That removes some risks but not all. The hosting account, the deployment process and any outside services still need protecting.
Can I edit a static website myself?
Sometimes. It depends on the set-up. Some static sites are edited as files by a developer, while others have an editing tool or CMS connected so that non-technical staff can publish. Ask how editing works before you commit.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.