Qt Bridges gives access to a rich, GPU-accelerated, cross-platform frontend for many backend languages.
What Is Qt Bridges?
Qt Bridges is a UI bridging technology that lets you use the mature Qt Quick and QML as the frontend for many backend languages. You write your UI once in QML and keep your application logic in your backend language and workflow.
Scalable
Keep your UI smooth as your application grows, even with advanced UI elements, thanks to built-in GPU acceleration.
Feature-Rich
Use a wealth of trusted UI capabilities, from basic controls to advanced graphics, graphs, and accessibility.
Cross-Platform
Provide native UX and styles, initially across Linux, Windows, and macOS with a UI technology that keeps evolving.
Integrated
Add the frontend cleanly into your existing stack without backend rewrites and stay in your usual workflow.
Common challenges with frontend integration
Many backend languages lack full-fledged UI options that naturally fit your existing stack, let alone an option that works for several languages. Especially for complex applications, there are challenges with cross-platform consistency, UI performance, and integrating with your backend and other systems. You may struggle with customization, native styling, accessibility, or memory gaps. At worst, you spend more time fighting the frontend than shipping features. So we bridged a better option for you. Qt Bridges allows you to switch to a mature, GPU-accelerated UI framework, giving you all the UI capabilities you need with proven, long-term stability.
Feedback Wanted
The first languages, C# and Rust, are now in Technology Preview, and we’re looking forward to hearing your feedback.
How Do You Handle UI Components Across Multiple Tech Stacks?
Use one UI technology for all your backend languages. With Qt Bridges, you write the UI in QML, a declarative language that’s easy to learn and read, and you can re-use the same frontend with many backends. If your application logic is already separate from the UI, it stays untouched, and you add the UI cleanly in front of it.
FEEDBACK WANTED
C# and Rust: Qt Bridges Technology Preview
Since the announcement of a significant expansion of the Qt ecosystem in May 2025, aiming to make Qt compatible with a wide range of programming languages, we've been working on our bridging technology for various backend languages.
Now, the first two bridges, C# and Rust, are in Technology Preview, and waiting for your feedback.
Sign up for the TP intro session for the C# and Rust bridges on November 3rd, 2026. The session covers the Qt Bridges project and its motivation, then digs into both of the bridges with a demo of each Technology Preview.
Speakers:
-
Cristián Maureira-Fredes, Qt Bridges Project Technical Leader, Qt Group
-
Matthias Rauter, Rust Team Developer, Qt Group
Available Languages
Qt Bridges brings one UI technology to many backend languages, one bridge at a time. Bridging works differently in each language, but every bridge gives you the same UI capabilities.
C#
Bridge to Qt’s mature, GPU-accelerated UI framework that works with your existing C# ecosystem. In Technology Preview; feedback wanted.
Rust
Bridge to Qt’s mature, feature-rich, GPU-accelerated UI framework for production-grade Rust frontends. In Technology Preview; feedback wanted.
Early Access: Python, Swift, and Java/Kotlin
Qt Bridges for the backend languages in earlier phases to build modern, cross-platform, Qt-powered UIs.
HELP US MAKE Qt BRIDGES BETTER
Share Your Feedback
The Qt Bridge for C# and the Qt Bridge for Rust are in Technology Preview. Install them, try them out, and tell us what works well, what you’d like improved, and which features or languages you’d like to see next. Your feedback is crucial for us to make Qt Bridges the best it can be.
Sign up also on our mailing list to be among the first to hear news about our project. No spam, we promise. We'll keep you in the loop about how this new UI bridging technology evolves and we may invite you to give us your feedback or try out new, upcoming bridge versions; your comments, observations, and insights will be highly appreciated by the Qt development team.
SIGN UP FOR OUR MAILING LIST
Be the First to Hear Project News
Get in Contact and Learn More
Bug Tracker
Track, report, and discuss bugs, and make suggestions for future improvements.
Forum for Qt Bridges
Get in contact with our developers, join the Qt discussion, share feedback, and learn what’s new.
Frequently Asked Questions
Which programming languages does Qt Bridges support?
- Qt Bridges
The aim of Qt Bridges is to bring Qt’s UI capabilities to as many backend languages as possible; starting with the Qt Bridge for C# and Qt Bridge for Rust now in Technology Preview for you to try and send feedback on. In addition, we have bridges for Python, Swift, and Kotlin/Java in early access phase. We’d also be happy to hear which languages you’d like to see next.
Will Qt Bridges work with my existing backend?
- Qt Bridges
Yes, the Qt Bridges UI layer works very smoothly with your existing backend. There's a separate bridge per backend language. Each bridge installs like any package in your ecosystem, for example, Rust through Cargo or C# through NuGet, and follows that language’s usual practices. The UI follows the MVVM pattern, so your design files stay separate from your backend logic. If your backend already separates logic from the UI, there's no need for backend rewrites; you keep the backend untouched and simply add the QML UI layer in front of it.
Is Qt Bridges just another language binding?
- Qt Bridges
No. Qt Bridges doesn’t try to map every included Qt API one-to-one into another language. It brings over the key part, Qt Quick, in a way that feels native to your language, so you build both UI and backend logic without writing C++.
What’s the difference between Qt Bridges and the Qt Bridge for Figma?
- Qt Bridges
They serve completely different purposes. Qt Bridges lets developers use QML and Qt Quick as the frontend layer for applications written in different backend languages beyond Qt’s traditional C++ scope, such as C# and Rust. Qt Bridge for Figma, then, is a legacy solution nowadays replaced by Figma to Qt, and it converts Figma designs into QML.
Which platforms does Qt Bridges support?
- Qt Bridges
Currently, desktop applications on Windows, macOS, and Linux, on x86 and ARM devices. Embedded Linux also works when it behaves like regular Linux. You can follow each operating system’s native look and feel or keep a custom design consistent everywhere. iOS, Android, and web targets aren’t yet supported in the Technology Preview.
What does Technology Preview mean for Qt Bridges?
- Qt Bridges
It means the first two bridges, the Qt Bridge for C# and the Qt Bridge for Rust, are ready for you to install, try out, and give feedback on, but they’re still evolving. APIs may change between releases and aren’t covered by Qt’s usual compatibility promises. Your feedback during the Technology Preview helps decide how to develop each bridge further.
What licensing options does Qt Bridges provide?
- Qt Bridges
Latest Blogs on Qt Bridges
Qt Bridges Technology Preview: Qt Quick UIs for Rust and C# Developers
When we announced Qt Bridges at Qt World Summit 2025, we had a simple ...
Qt Bridge for Rust 0.3 Beta: CXX-Qt Compatibility and Soundness
As part of the on-going development of Qt Bridges, we are out with a n...
A Cross-Platform C# UI Framework via Qt’s Bridging Technology
Every C# UI framework comes with a familiar pattern: Windows-first, Li...
More on Qt’s UI Capabilities
Qt Framework’s comprehensive set of cross-platform UI libraries and APIs take away your routines from UI controls to 2D to 3D graphics.
More on the QML Language
Qt’s UI language, QML, is a declarative, memory-safe language that allows a clear separation of the frontend and backend.
Get Started with Qt Bridges
Access Qt’s feature-rich, GPU-accelerated, cross-platform frontend for many backends.