7 releases

0.3.0 Jan 4, 2023
0.2.1 May 3, 2022
0.2.0 Mar 9, 2022
0.1.3 Jan 29, 2022
0.1.0 Sep 25, 2021

#240 in GUI

Download history 60/week @ 2022-12-05 65/week @ 2022-12-12 85/week @ 2022-12-19 107/week @ 2022-12-26 115/week @ 2023-01-02 83/week @ 2023-01-09 72/week @ 2023-01-16 85/week @ 2023-01-23 100/week @ 2023-01-30 56/week @ 2023-02-06 97/week @ 2023-02-13 101/week @ 2023-02-20 83/week @ 2023-02-27 132/week @ 2023-03-06 153/week @ 2023-03-13 288/week @ 2023-03-20

666 downloads per month
Used in 4 crates (3 directly)


3.5K SLoC

Dioxus Server-Side Rendering (SSR)

Render Dioxus to valid html.


This crate is a part of the broader Dioxus ecosystem. For more resources about Dioxus, check out:


Dioxus SSR provides utilities to render Dioxus components to valid HTML. Once rendered, the HTML can be rehydrated client side or served from your web-server of choice.

let app: Component = |cx| cx.render(rsx!(div {"hello world!"}));

let mut vdom = VirtualDom::new(app);
let _ = vdom.rebuild();

let text = dioxus_ssr::render_vdom(&vdom);
assert_eq!(text, "<div>hello world!</div>")

Basic Usage

The simplest example is to simply render some rsx! nodes to html. This can be done with the [render_lazy] api.

let content = dioxus_ssr::render(rsx!{
    div {
        (0..5).map(|i| rsx!(
            "Number: {i}"

Rendering a VirtualDom

let mut dom = VirtualDom::new(app);
let _ = dom.rebuild();

let content = dioxus_ssr::render_vdom(&dom);

Usage in pre-rendering

This crate is particularly useful in pre-generating pages server-side and then selectively loading dioxus client-side to pick up the reactive elements.

In fact, this crate supports hydration out of the box. However, it is extremely important that both the client and server will generate the exact same VirtualDOMs - the client picks up its VirtualDOM assuming that the pre-rendered page output is the same. To do this, you need to make sure that your VirtualDOM implementation is deterministic! This could involve either serializing our app state and sending it to the client, hydrating only parts of the page, or building tests to ensure what's rendered on the server is the same as the client.

With pre-rendering enabled, this crate will generate element nodes with Element IDs pre-associated. During hydration, the Dioxus-WebSys renderer will attach the Virtual nodes to these real nodes after a page query.

To enable pre-rendering, simply configure the SsrConfig with pre-rendering enabled.

let dom = VirtualDom::new(App);

let text = dioxus_ssr::render_vdom(App, Config { pre_render: true, ..Default::default() });

Usage in server-side rendering

Dioxus SSR can also be to render on the server. Obviously, you can just render the VirtualDOM to a string and send that down.

let text = dioxus_ssr::render_vdom(&vdom);
assert_eq!(text, "<div>hello world!</div>")

The rest of the space - IE doing this more efficiently, caching the virtualdom, etc, will all need to be a custom implementation for now.

Usage without a VirtualDom

Dioxus SSR needs an arena to allocate from - whether it be the VirtualDom or a dedicated Bump allocator. To render rsx! directly to a string, you'll want to create an SsrRenderer and call render_lazy.

let text = dioxus_ssr::SsrRenderer::new().render_lazy(rsx!{
    div { "hello world" }
assert_eq!(text, "<div>hello world!</div>")

This can be automated with the render_lazy! macro:

let text = render_lazy!(rsx!( div { "hello world" } ));

Usage in static site generation

Dioxus SSR is a powerful tool to generate static sites. Using Dioxus for static site generation is a bit overkill, however. The new documentation generation library, Doxie, is essentially Dioxus SSR on steroids designed for static site generation with client-side hydration.

Again, simply render the VirtualDOM to a string using render_vdom or any of the other render methods.


~61K SLoC