When we announced Qt Bridges at Qt World Summit 2025, we had a simple goal: let developers build Qt Quick user interfaces with a backend written in their favorite programming languages. This year, the C# and Rust bridges went through several public betas. Thank you to everyone who tried them and sent feedback. It shaped every release.
Today the Qt Bridge for Rust and the Qt Bridge for C# both reach Technology Preview.
When developing Qt Bridges, we were guided with a few simple guidelines
In practice, Qt Bridges applications have two parts. The user interface is written in QML with Qt Quick while backend is written in Rust or C#. You mark the types the UI should see, using the usual mechanism of your language (attributes in C#, attribute macros in Rust). QML can then read and bind to their properties, call their methods, react to their signals, and show their collections in lists and tables. You don't need hand-written glue or deep Qt knowledge. Because the UI depends only on what the backend exposes, you can change either side independently.
Qt Bridges is not a full binding of Qt API. It focuses on connecting your backend to a Qt Quick UI. For networking, file I/O and everything else, you keep using the libraries of your own ecosystem.
The Technology Preview is the step between our betas and a first stable release. The core feature set is in place and ready for prototypes and evaluation projects. APIs, supported platforms and requirements can still change before the stable release, and your feedback now has the most influence on what ships.
The Qt Bridge for Rust lets you build Qt Quick UIs with a backend in idiomatic Rust: no C++ headers, no manual FFI and no prior Qt experience needed. The API is built on attribute macros and traits. The ownership model maps QML objects to Rc<RefCell<T>>, so borrow rules apply across the boundary, and the bridge shares its foundations with CXX-Qt, so the two can coexist.
With the Rust bridge you can:
All of the details about using Qt Bridge with rust can be found in our docs.
The Qt Bridge for C# is for .NET teams that want a modern, cross-platform UI without rewriting their application. Your C# code stays as it is, and you add a Qt Quick frontend on top.
With the C# bridge you can:
Check out the docs at to learn more!
On Windows, the Qt Bridge for C# extension for Visual Studio is the easiest way to start. It adds project and item templates, so you don't need to install the dotnet templates separately. Projects created with it reference the right NuGet package automatically. It also enables QML language server support, giving you QML IntelliSense for your C# types once the project is built.
If you work in Visual Studio Code, on any platform, install the Qt Bridge C# extension for VS Code. It connects Qt Bridge for C# projects to the Qt Extension for VS Code, providing:
To create a project, run Qt: Create a new project or file and select Qt Bridge for C# application. Build once so the extension can generate the metadata used by the QML tooling. The extension requires the Qt Core extension. We also recommend the Qt QML extension, plus C# Dev Kit for C# editing and debugging.
Join Cristián Maureira-Fredes and Matthias Rauter for a Qt World Summit webinar Modern, Performant UIs to Rust and C#: Qt Bridges Technology Preview Is Here! on 3 November 2026 at 15:00 (UTC+1). They will cover the motivation behind the project and demo both Technology Previews.
We are planning bring Qt Bridges out of Technology Preview in first quarter of 2027 with a few more features.
Your feedback during the Technology Preview helps us most. Tell us what works, what's missing and what gets in your way:
We look forward to seeing what you build!