Astro 6 has shipped five times, and each release moved a different part of the framework. The pitch held steady: a web framework for content-driven websites, server-first by default, with no JavaScript shipped unless a component asks for it. Here is what landed in each point release, 6.0 through 6.4.
What Astro 6 stands for
The core stance is server-first rendering: pages render on the server, the browser gets HTML, and zero JavaScript ships by default. Interactive widgets opt in through Astro Islands. There is no lock-in on UI libraries — React, Vue, Preact, Svelte, and Solid all work side by side.
Around that core sit the building blocks most projects reach for: Content Collections for typed, schema-checked content, View Transitions for animated navigation, Actions for typed server functions called from the client, Middleware that runs on every request, and Adapters that target a host at build time.
The performance claim has field numbers behind it. 66% of real-world Astro sites record good Core Web Vitals. On the same measure WordPress sits at 48%, Gatsby at 47%, Next.js at 30%, and Nuxt at 28% — the practical argument for a server-first, zero-JS-by-default design.
Astro 6.0: the foundation release
Astro 6.0 carried the most weight. The dev server was redesigned, and the Cloudflare integration was rebuilt rather than patched. A new Fonts API moved font handling into the framework, Live Content Collections extended collections to fetch at request time instead of only at build, Content Security Policy support landed, and a Rust compiler replaced the prior toolchain.
The dev server and Cloudflare rebuild
The redesigned dev server is the part you touch every time you run astro dev. Separately, the @astrojs/cloudflare adapter was rebuilt here, so anyone deploying to that platform is on new internals.
Fonts, live data, and CSP
The Fonts API gives a first-party path for declaring fonts instead of wiring up tags and preloads by hand. Live Content Collections are the bigger conceptual shift: a collection can pull data live, which suits content that changes between deploys. CSP support means you can serve a Content Security Policy without a separate tool. The Rust compiler underpins all of it.
Astro 6.1 and 6.2: images, i18n, and logs
Astro 6.1 made Sharp the default for image processing, so optimization works without extra setup. It smoothed view transitions on mobile, and added i18n fallbacks so a missing translation resolves to a defined fallback locale rather than breaking the page.
Astro 6.2 turned to tooling: an SVG optimizer, and logging moved to a structured format that is easier to parse and pipe into other systems than free-form text. This release also opened a v7 alpha, an early look at the next major while you stay on 6.
Astro 6.3: Advanced Routing with Hono
Astro 6.3 introduced experimental Advanced Routing built on Hono, the lightweight web router. It is flagged experimental, so treat it as a preview rather than a stable contract. If you have hit the edges of file-based routing, this is the release to watch.
Astro 6.4: a new Markdown processor and Cloudflare helpers
Astro 6.4 brought in Sätteri, a new Markdown processor. For content sites the Markdown pipeline is load-bearing, so a processor swap is worth a look before you upgrade. This release also added cf() helpers for the Cloudflare adapter, giving projects on that platform more direct access to its features.
Which release matters for you
Read the line by what it solves. 6.0 gives you the dev-server rebuild, the rebuilt @astrojs/cloudflare adapter, Fonts, Live Content Collections, and CSP. 6.1 and 6.2 are quality-of-life on images, i18n, and logs; 6.3 and 6.4 are the experimental routing and content-pipeline edges.
For the cadence between releases, the monthly digests track it close: March 2026, April 2026, and May 2026.
Docs sites get their own track: Starlight 0.39 ships on the same foundation. With a v7 alpha already open, the next thing to track is how Advanced Routing and Sätteri move from new arrivals to settled defaults. The full Astro topic hub collects every release breakdown.