Astro 7 — what is actually new (and why your site gets faster)

Astro 7 dropped on 22 June 2026. It is mostly an engine release — the kind that does not give you a new component or a flashy new keyword, but quietly makes your existing site faster, cheaper to host, and easier to ship.

Here is what actually changed, and why I cared enough to upgrade the same week.

1. The compiler is now in Rust

The .astro compiler has been rewritten in Rust. Markdown and MDX go through a new Rust pipeline. The rendering engine itself moved to a queue-based model.

The headline result, paired with Vite 8 and the Rolldown bundler, is build times 15–61% faster in the official benchmarks. Some sites build more than twice as fast. On a typical content site of mine — maybe 80 routes, mostly Markdown — astro build went from around 12 seconds to 5.

Why this matters in practice: every preview deploy is faster, every CMS rebuild is faster, every “I just want to fix this typo” cycle is faster. Compounded across a year, it is real.

2. Advanced Routing — src/fetch.ts

Astro 7 adds an Advanced Routing entrypoint at src/fetch.ts. You get full control over the request pipeline: rewrites, header manipulation, conditional responses, A/B at the edge.

For a static content site you will probably never need this. For a portal where some routes go through an auth check before hitting the CMS, or where you want a custom 404 with a “did you mean” lookup — it is the right hook.

3. Route caching, stable

Route caching is now stable and platform-agnostic. You get a single API; the engine takes care of the rest.

There are also experimental CDN cache providers for Netlify, Vercel and Cloudflare — meaning a single line in your config sets up SWR-style caching at the edge for the routes you mark.

For a school or institution site this is the boring-but-useful kind of feature: the homepage stays sub-100ms even when the CMS just published five news items in a row.

4. AI-assisted development

Astro now detects coding agents (Claude Code, Cursor, the rest), can run the dev server in the background, and emits structured JSON logs when the agent needs machine-readable feedback.

If you build alongside an agent, this turns a fiddly thing — “wait, what did the build print?” — into a clean machine-to-machine handshake. It is small but I notice it daily.

Should you upgrade?

If you are on Astro 5 or 6 and your site builds without warnings, yes. The upgrade is a npm i astro@latest and a npm run build away. I have done five client sites and the only fix needed was bumping @astrojs/sitemap to match.

If you are on Astro 3 or earlier — the upgrade has more steps (Content Collections, the Content Layer change, then this). Worth it, but not a five-minute job. Block an afternoon.

What I am watching next

The two things I keep an eye on:

1. Image service polish. The built-in <Image> is already excellent. With the Rust pipeline they have headroom to push it further — on-the-fly variants, AVIF defaults, smarter LQIP.
2. Forms primitives. Server-side form handling in Astro is still a “wire it yourself” story. With Advanced Routing in place, a first-class primitive would close a gap that React and Next.js solved years ago.

Either of those would be a bigger deal than this release for the sites I build. But this release, on its own, made my last five projects measurably faster — and that is plenty to celebrate.