What Is a Static Site Generator?
How a static site generator builds a website
A static site generator is a tool that turns source files and templates into a finished set of HTML pages before the site goes live. Hugo and Jekyll are two well-known examples. The output is a folder of plain files that a web server can deliver directly, without a database or page assembly for each visit.
The source is usually written in Markdown, a simple text format for headings, lists and links. Each page starts with a small header of settings, called front matter, that sets its title, date and layout. Templates define the structure, and the generator combines them with the content during a build step.
Strengths and limitations of static sites
Static sites load quickly because the server only sends files. They also have a small attack surface, meaning few parts that attackers can target, since no database or admin login runs on the public site. Hosting is often simple and inexpensive, and a content delivery network (CDN) can copy the files close to visitors.
The trade-offs come from the lack of a live database. Features such as comments, search, forms and user logins need third-party services or client-side code. Editing is less immediate: changes usually need a rebuild, and non-technical editors may need a web-based editor or a headless CMS to work comfortably.
Comparing Hugo, Jekyll and other tools
Tools differ mainly in language, build speed and ecosystem. Hugo is written in Go and is known for very fast builds, which matters for large sites. Jekyll is written in Ruby and is supported natively by GitHub Pages, which makes it a common choice for documentation and personal sites. Other popular options include Eleventy and Astro, each with its own strengths.
Static site generators are a core part of the Jamstack, a wider approach to building sites this way.
Frequently asked questions
What is the difference between a static site generator and a CMS?
A static site generator builds pages once, before publishing, and produces only files. A traditional CMS stores content in a database and assembles each page when a visitor requests it. Many CMS platforms also offer a built-in admin area for editors, which static tools usually lack. For the wider picture, see how a CMS works.
Which static site generator should I choose?
There is no single answer. Choose based on the language your team knows, the size of the site and the features you need. For very large sites where build speed matters, Hugo is a common choice. For a simple documentation or personal site hosted on GitHub Pages, Jekyll is often the easiest path.