Definition: Jamstack is a web architecture approach based on pre-rendering pages as static HTML files at build time, then enhancing them with JavaScript and external APIs for dynamic functionality. The name originally stood for JavaScript, APIs, and Markup — though the term now broadly describes any architecture that decouples the front-end from the back-end, serving pre-built assets from a CDN.
Why It Matters: Jamstack sites load faster than server-rendered equivalents because pages are served directly from a CDN edge node rather than generated on-demand by a server — eliminating database queries and server processing from the critical path. This translates directly into better Core Web Vitals scores and lower bounce rates. The architecture also improves security (fewer server-side attack surfaces) and reduces hosting costs for high-traffic sites. It is popular for marketing sites, documentation, and e-commerce storefronts built on headless platforms.
How It Works: In a Jamstack workflow, a static site generator (Next.js, Astro, Nuxt, Eleventy) builds the site at deploy time — fetching content from a headless CMS, e-commerce API, or data source, and rendering it into static HTML files. These files are uploaded to a CDN (Netlify, Vercel, Cloudflare Pages). When a user requests a page, it is served instantly from the nearest edge node. Dynamic features — search, forms, comments, personalisation — are handled client-side via JavaScript calling APIs, without a traditional application server.
Related: Headless CMS, Content Delivery Network, Edge Rendering, Application Programming Interface, Page Speed