Astro 7.0 Released: Rust Compiler and Faster Builds Take the Stage

Astro 7.0 Released: Rust Compiler and Faster Builds Take the Stage

On June 4, 2026, Astro officially released Astro 7.0. This version has one clear theme — speed. The team moved the most time-consuming parts of the build from JavaScript to native Rust implementations, and official benchmarks show overall build times improved by 15%-61%, with some sites building more than twice as fast.

What the official benchmark actually shows

The team published finer-grained numbers by site type, and what's worth reading isn't just "how much faster on average" but which workloads benefit most:

The more pages you have, the bigger the win. For a large docs site building dozens of times a day in CI, that's hours of pipeline time saved daily; smaller projects save less in absolute terms, but combined with the new caching machinery, local preview and deploy feel noticeably snappier too.

Upgrading costs almost nothing

The official upgrade command brings projects up from v5/v6 in a few steps:

npx @astrojs/upgrade

Most projects get the new build pipeline with no config changes. If you hand-wrote vite.build.rollupOptions or vite.optimizeDeps in an older version, Vite 8's compatibility layer translates them into Rolldown equivalents automatically; when an individual plugin isn't compatible, startup fails loudly instead of silently degrading — which matches the new compiler's style: if something's wrong, say so.

Vite 8 and the Rolldown bundler

Astro 7 upgrades to Vite 8, the most significant Vite release in years. The headline change is Rolldown — a Rust-based bundler that replaces both esbuild and Rollup with a single unified bundler, benchmarking 10-30x faster than Rollup while supporting the same plugin APIs. For most projects, upgrading delivers faster builds with no config changes; Vite 8 also includes a compatibility layer that auto-converts existing esbuild and rollupOptions config to their Rolldown equivalents.

Rust-rewritten compiler and Markdown pipeline

• A new .astro compiler: fully rewritten from Go to Rust, built on oxc for parsing and Lightning CSS for scoping. It no longer "silently fixes your HTML" like the old compiler — unclosed tags and unterminated attributes now raise errors directly. Stricter, and more predictable.
• Markdown/MDX fully in Rust: the default pipeline switches to Sätteri, a Rust-powered processor that shaved over a minute off the Astro docs and Cloudflare docs builds. GFM tables, smart punctuation, math, and other formerly plugin-required features are now built in.

For content teams the most visible change is in Markdown: tables and math that used to require remark-gfm and rehype-katex now work out of the box, so writers no longer maintain a plugin checklist.

Rendering engine and caching

• Queued Rendering: promoted from experimental to the default rendering engine, using a queue and single loop instead of recursion — roughly 2.4x faster on expression-dense pages with lower memory usage.
• Route caching goes stable + CDN cache providers: Astro.cache and routeRules are now stable APIs, with experimental CDN cache providers for Netlify, Vercel, and Cloudflare that push caching directives to the host's edge network — cache hits never invoke your server function.

Marking the whole site as cacheable takes a few lines of routeRules:

// astro.config.mjs
export default defineConfig({
  routeRules: {
    '/': { cache: { ttl: 3600 } },
    '/blog/**': { cache: { ttl: 86400 } },
  },
});

With a CDN provider, cache hits are served at the edge and neither the origin nor serverless functions are called — a real cost saving for docs sites and marketing pages.

Advanced routing and AI enhancements

Astro 7 adds a src/fetch.ts entrypoint for full control of the request pipeline (Cloudflare Workers / Deno / Bun style, Hono-compatible). For AI-assisted development, it adds a background dev server (astro dev --background, auto-detected by coding agents) and structured JSON logging — one of the most upvoted items on the Astro roadmap.

Who should upgrade

• Docs and content sites: the fully Rust Markdown pipeline pays off most here — hundreds of pages can save a minute or more per build;
• Teams building frequently in CI: faster builds shorten release cycles, and a 15%-61% improvement matters a lot when you deploy several times a day;
• Older v5 projects: go to v6 first to validate plugin compatibility, then to v7, rather than jumping two major versions at once.

One practical tip: before upgrading, run astro check and a build on a branch and compare artifact size and timing against the old version; merge to main only after confirming no regressions. Now that Astro 7 treats strict erroring as the default, markup the old compiler quietly "fixed" will surface directly — those are exactly the bits of technical debt worth clearing out first.

16IDC Take

Astro 7's direction is clear: push performance to the limit while opening the developer experience to AI agents. For Markdown-heavy projects — content sites, docs, and blogs — this release delivers the most value. To build a personal blog with Astro, see the Astro blog building guide; for static vs. dynamic CMS decisions, read static sites vs. dynamic CMS. For more website-building content, see the Website Building Tech category.

Reference: Astro release announcement https://astro.build/blog/astro-7/