Tauri + Servo = 💡?

[codeit-ninja]

Yesterday, the Linux Foundation released Servo on crates.io, which made me wonder: how feasible would it be for Tauri to support Servo as an alternative browser engine instead of relying exclusively on native webviews?

One of the biggest pain points with native webviews is that they are not truly consistent across platforms. Each operating system ships a different engine with different levels of Web API support, different quirks, and different update cycles. In practice, that means developers often have to account for platform-specific behavior even when building a single Tauri application.

An optional Servo-based backend could be very compelling here. Since Servo is now more accessible to the Rust ecosystem, it seems worth exploring whether it could eventually provide Tauri with a more consistent cross-platform rendering layer, while also aligning well with Tauri’s Rust-first architecture.

To be clear, I’m not suggesting replacing native webviews outright. They are still one of Tauri’s biggest strengths in terms of bundle size and native integration. But Servo could potentially be interesting as an opt-in alternative for use cases where rendering consistency, feature parity, or tighter control over the browser engine matters more than minimizing size.

If this is technically unrealistic, I’d still be interested in understanding the main blockers. It feels like there could be real long-term value in exploring whether Servo could complement Tauri’s current model.

[FabianLars]

We already had something long before: https://v2.tauri.app/blog/tauri-verso-integration/ - just no time to migrate it over to any new apis/packages atm.

[codeit-ninja]

Interesting, thanks for sharing