Jamstack
An architecture serving pre-rendered pages from a CDN, with dynamic behaviour added through APIs rather than a server rendering each request.
Development & PlatformsJamstack described sites built as static files, deployed to a CDN, with JavaScript calling APIs for anything dynamic. The benefits were real: fast delivery, a small attack surface, and hosting that costs almost nothing. The original acronym — JavaScript, APIs, Markup — has aged out, and the term now loosely means pre-rendering plus APIs rather than a specific stack.
The limitation that defined it was build time. A site of 50,000 pages rebuilt entirely on every content change took hours, which made the model unworkable for large or frequently-updated content. Incremental regeneration and edge rendering in modern frameworks removed most of that constraint, which is also why the label matters less than it did — the useful question now is which pages are pre-rendered, which are rendered per request, and how stale content is revalidated.
In practice
A documentation site of 8,000 pages took 40 minutes to build, so an urgent typo fix meant a 40-minute wait. Moving to incremental regeneration — only changed pages rebuilt, others served from cache — brought publish latency under a minute and kept the same CDN delivery.
Where teams get it wrong
- Full rebuilds for large sites, where a one-word change means a long wait.
- Pre-rendering content that must be current, so users see stale data.
- Adding so much client-side JavaScript that the performance benefit disappears.
- Choosing the architecture for the label rather than for the page-by-page rendering needs.
- Personalised content in pre-rendered pages, which leaks between users through the CDN.
Learn more
You may ask
Frequently Asked Questions
What does Jamstack mean?
Originally JavaScript, APIs and Markup — sites pre-rendered to static files, served from a CDN, with dynamic behaviour added through APIs. It now loosely means pre-rendering plus APIs rather than a specific stack.
Is Jamstack still relevant?
The ideas are — pre-rendering, CDN delivery, API-driven dynamism — and they are built into modern frameworks. The label matters less now that the same application can pre-render some routes and render others per request.
Related terms
All terms- Headless CMSA content management system that stores and serves content through an API, with no opinion about how it is displayed.
- Headless CMSA content management system that stores and serves content through an API, with no opinion about how it is displayed.
- SitemapA structured list of a site's pages and their hierarchy — used both as a design artefact and as an XML file that tells search engines what exists.
- Design SystemThe single source of truth for how a product looks and behaves: tokens, components, patterns, usage rules and the process for changing them.
Defined by Mara Last reviewed .
Let's talk about your product.
Happy to look at what you're building and say where design would move the needle.
Contact Us