Static vs dynamic website

What it means

A static website can send prebuilt HTML and assets without generating a new page on each visitor request. A dynamic website commonly uses server-side code to generate or tailor responses from state, data or user context at request time. Static versus dynamic here describes the serving/generation approach, not whether the screen can respond to clicks. Web server types Rendering terminology

A static page may contain JavaScript that opens menus, filters results or calculates values in a visitor's browser. That makes the interface interactive without requiring the server to generate its HTML for every request. Client-side code

Try it

Example — two ways to produce a product page. Same visible result, different work location.

Static generation: source data → build step → product.html → visitors
Request-time:      visitor request → app + data store → HTML response

If the price changes, a purely prebuilt page may need a new build or client-side data fetch. A request-time renderer can calculate a price on demand. The second option is not automatically faster or more accurate; caching, freshness, data sources and infrastructure decide the outcome. Static export boundary

Compare the same criteria

Static exports are appropriate for predictable content, documentation and many marketing pages. Personalized accounts, private updates and payment flows generally require additional backend capabilities, even if the user-facing pages are initially static. Next.js static export limitations

Hybrid designs exist

A dynamic site almost always serves some static CSS, images or JavaScript. A static page can call a separate API, and a framework can pre-render some routes while computing others. The distinction should be applied to a particular page or response, not used as a universal label for the entire business.

Static export excludes request-dependent server functions by design. Next.js's documented static mode produces files at build time, while client-side components can still run in the browser. The limits matter if someone assumes a static upload can provide authenticated server actions or a writable database without another service. Export guide

In practice

Choose prebuilt delivery when public content can be generated ahead of time, and the editorial/rebuild workflow is acceptable. Choose server-side processing when requirements genuinely depend on secrets, private data, current shared state or validated writes. In either approach, plan caching, security, accessibility, backups and rollback.

Common mistake: assuming “static” means “no JavaScript,” or assuming every dynamic page requires a separate database. Neither statement is generally true. JavaScript roles