What’s next: Quarto 2 – Quarto

[giscus[bot]]

What’s next: Quarto 2 – Quarto

We’ve started working on quarto-dev/q2, a full rewrite of Quarto in Rust.

https://quarto.org/docs/blog/posts/2026-04-06-whats-next-quarto-2/

[renatovargas]

Looking forward to trying out the public release in 6 months. Can't wait! Quarto is a fundamental part of my everyday workflow. We are grateful for your hard work!

[pricele2]

Very excited to see a collaborative editing feature is in the works. Will be great for scaffolding learning Quarto with coworkers who have not yet been convinced

[davidleitch1]

You don’t mention incremental rendering? Or more generally updating the published site only with changes rather than a full publish. Thanks to LLMs I have some workarounds, but they are just workarounds.

Quarto is an excellent product. Along with Typora it makes my work possible.

[mcanouil]

You don’t mention incremental rendering?

See the Current Status section of the post.

The development is happening in a separate GitHub repository. Feel free to look around! However, this code base isn’t ready for public consumption, and is very much in flux: that means we’re not going to spend a lot of time answering architectural questions about it until things have settled, and all discussion of Quarto should remain in our current discussion forum and issue tracker.

There are big, interesting changes in the Quarto 2 architecture, and they deserve a longer exposition. We are working on those documents right now, and will share them with you in the next few weeks. Stay tuned!

This being said, Quarto 1 already supports incremental rendering: quarto render my/modified/file.qmd.