Static versus dynamic site

The split between a project that hands over fixed files every visitor sees the same way (static) and one that runs code on a server to build a fresh response for each request (dynamic). The category decides where you can host it and what it costs.

A static versus dynamic site is the split between a project that hands over fixed files every visitor sees the same way and one that runs code on a server to build a fresh response for each request. A static site ships pre-built files (HTML, CSS, JavaScript, images) straight to the browser with no per-request processing, so a portfolio or documentation page loads the same content for everyone. A dynamic site runs server code on each visit: a to-do app checks who is signed in, reads that person's tasks from a database, and assembles a page only they should see. Picture a password reset. A static page can show the form, but completing the reset needs server code to verify the link and update the account, which makes the project dynamic.

Builder example

The category decides your hosting options before you write a line of deployment configuration. A static project loads onto many free hosts with almost no setup, while a dynamic one needs an always-on machine to run its server code, which narrows your choices and can cost money. If you tell the AI to ship a marketing page and it adds a sign-in feature, you have quietly turned a static site into a dynamic one and changed where it can live. Ask the assistant to classify the project first so you pick the right host.

Common confusion: What separates the two is whether the server runs code per request, not whether the page looks interactive. A static site can hold animations, menus, and forms that all run in the browser. The moment a request needs the server to check an account, read a database, or use a secret key, the project is dynamic.