Getting Started: Server-Side-Rendering

The Dioxus VirtualDom can be rendered to a string by traversing the Element Tree. This is implemented in the ssr crate where your Dioxus app can be directly rendered to HTML to be served by a web server.


If you just want to render rsx! or a VirtualDom to HTML, check out the API docs. It's pretty simple:

fn main() {
// We can render VirtualDoms
let mut vdom = VirtualDom::new(app);
let _ = vdom.rebuild();
println!("{}", dioxus::ssr::render_vdom(&vdom));

// Or we can render rsx! calls directly
println!( "{}", dioxus::ssr::render_lazy(rsx! { h1 { "Hello, world!" } } );

However, for this guide, we're going to show how to use Dioxus SSR with Axum.

Make sure you have Rust and Cargo installed, and then create a new project:

$ cargo new --bin demo
$ cd app

Add Dioxus with the ssr feature:

$ cargo add dioxus --features ssr

Next, add all the Axum dependencies. This will be different if you're using a different Web Framework

$ cargo add tokio --features full
$ cargo add axum

Your dependencies should look roughly like this:

axum = "0.4.5"
dioxus = { version = "*", features = ["ssr"] }
tokio = { version = "1.15.0", features = ["full"] }

Now, setup your Axum app to respond on an endpoint.

use axum::{response::Html, routing::get, Router};
use dioxus::prelude::*;

async fn main() {
    let addr = std::net::SocketAddr::from(([127, 0, 0, 1], 3000));
    println!("listening on http://{}", addr);

                .route("/", get(app_endpoint))

And then add our endpoint. We can either render rsx! directly:

fn main() {
async fn app_endpoint() -> Html<String> {
    Html(dioxus::ssr::render_lazy(rsx! {
            h1 { "hello world!" }

Or we can render VirtualDoms.

fn main() {
async fn app_endpoint() -> Html<String> {
    fn app(cx: Scope) -> Element {
        cx.render(rsx!(h1 { "hello world" }))
    let mut app = VirtualDom::new(app);
    let _ = app.rebuild();


And that's it!

You might notice that you cannot hold the VirtualDom across an await point. Dioxus is currently not ThreadSafe, so it must remain on the thread it started. We are working on loosening this requirement.

Future Steps

Make sure to read the Dioxus Guide if you already haven't!