Astro 7.0 replaces JavaScript Markdown processor with Rust-based Sätteri for up to 61% faster builds

Astro 7.0 has adopted Sätteri as its default Markdown and MDX processor, replacing a JavaScript-based pipeline with a Rust implementation. The change targets build performance, with benchmarks showing improvements of 15 to 61% for Astro projects. The gains stem from moving parsing logic out of JavaScript, where the previous unified pipeline relied on a sequence of remark and rehype plugins that processed the full syntax tree in each pass. Sätteri’s Rust engine, using pulldown-cmark and Oxc, eliminates this overhead while maintaining compatibility with the unified AST format for plugins.

The performance boost is most noticeable in large documentation sites, where builds reportedly shaved over a minute off runtime. However, the speed comes with a compatibility cost: Sätteri does not run existing remark or rehype plugins. Projects without plugins require no changes, but those relying on plugins must either port them to Sätteri’s MDAST or HAST plugin system or opt out by installing @astrojs/markdown-remark. The Astro team has provided an upgrade tool to handle the transition, but the migration effort will vary depending on plugin complexity.

Sätteri’s design reflects a growing trend of offloading JavaScript tooling to native code for performance. Similar projects like Bun.markdown, written in Zig, have reported comparable speedups but lack plugin ecosystems. Sätteri’s reuse of the unified AST format distinguishes it, offering a middle ground between raw speed and extensibility. The processor ships with platform-specific binaries and a WASM fallback, mirroring Astro’s approach with its Rust compiler. This ensures broad compatibility but may introduce deployment considerations for environments where native binaries are restricted.

Beyond performance, Sätteri consolidates features that previously required separate plugins, including GitHub Flavored Markdown, smart punctuation, and frontmatter. These are enabled through configuration, reducing dependency bloat. The processor is maintained separately from Astro under the Bruits collective but has become a core dependency. While the shift to Rust improves build times, it also introduces a new maintenance surface for the Astro team, particularly around plugin compatibility and native binary updates. Engineers will need to weigh the performance benefits against the effort of migrating or maintaining legacy plugin support.