JAMstack

Definition

JAMstack is a web architecture pattern built on JavaScript, APIs, and pre-rendered Markup — typically served as static files from a CDN and enhanced with dynamic functionality through client-side API calls and serverless functions.

Overview

The term JAMstack was coined by Netlify around 2016 to describe an architectural shift away from monolithic servers that render every page on request, toward pre-building markup ahead of time (via Static Site Generation (SSG)) and handling anything dynamic — forms, authentication, search, payments — through client-side calls to APIs and serverless functions, rather than a traditional backend server. A typical JAMstack site is built with a static site generator or meta-framework, pulls content from a Headless CMS at build time, and is deployed to a global CDN for fast, cacheable delivery worldwide. Dynamic features are then added incrementally through third-party or custom APIs, so the 'server' for any given feature is really just another API endpoint rather than a single application server handling everything. As frameworks matured to support hybrid rendering — combining static generation with Server-Side Rendering (SSR) and Incremental Static Regeneration (ISR) on a per-page basis — the strict 'everything pre-built' JAMstack definition has blurred into a broader set of hybrid rendering practices, but the core JAMstack values (decoupled frontend, CDN-first delivery, API-driven dynamism) remain influential in how modern web architecture is discussed.

Key Concepts

• Pre-built markup served as static files from a CDN by default
• Dynamic functionality handled through APIs and serverless functions
• Decoupled frontend and backend — no monolithic application server required
• Content commonly sourced from a Headless CMS at build time
• Emphasizes speed, security, and scalability through static delivery
• Often combined with hybrid rendering (SSR/ISR) for dynamic pages

Use Cases

Frequently Asked Questions

Related in Web