Window handling library in pure Rust
Alternatives To Winit
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Glfw11,1061513 days ago6April 06, 2023610zlibC
A multi-platform library for OpenGL, OpenGL ES, Vulkan, window and input
2 months ago88otherRust
Use your tablet as graphic tablet/touch screen on your computer.
2 months ago26mitShell
Run GUI applications and desktops in docker and podman containers. Focus on security.
Winit3,7248065529 hours ago86June 30, 2023409apache-2.0Rust
Window handling library in pure Rust
22 days ago219gpl-3.0C++
ksnip the cross-platform screenshot and annotation tool
7 days ago517gpl-2.0C++
QML based X11 and Wayland display manager
3 days ago28mitRust
Key remapper for X11 and Wayland
Gromit Mpx813
15 days ago33gpl-2.0C
Gromit-MPX is an on-screen annotation tool that works with any Unix desktop environment under X11 as well as Wayland.
18 hours ago34mitC++
Cross-platform window customization framework for Qt Widgets and Qt Quick. Supports Windows, Linux and macOS.
10 days ago5February 04, 20222mitPython
Emoji, unicode and general character picker for rofi and rofi-likes
Alternatives To Winit
Select To Compare

Alternative Project Comparisons

winit - Cross-platform window creation and management in Rust CI Status

winit = "0.29.1-beta"


For features within the scope of winit, see

For features outside the scope of winit, see Missing features provided by other crates in the wiki.

Contact Us

Join us in any of these:

Matrix Libera.Chat


Winit is a window creation and management library. It can create windows and lets you handle events (for example: the window being resized, a key being pressed, a mouse movement, etc.) produced by window.

Winit is designed to be a low-level brick in a hierarchy of libraries. Consequently, in order to show something on the window you need to use the platform-specific getters provided by winit, or another library.

use winit::{
    event::{Event, WindowEvent},

fn main() {
    let event_loop = EventLoop::new();
    let window = WindowBuilder::new().build(&event_loop).unwrap(); |event, elwt| {
        match event {
            Event::WindowEvent {
                event: WindowEvent::CloseRequested,
            } if window_id == => elwt.exit(),
            _ => (),

Winit is only officially supported on the latest stable version of the Rust compiler.

Cargo Features

Winit provides the following features, which can be enabled in your Cargo.toml file:

  • serde: Enables serialization/deserialization of certain types with Serde.
  • x11 (enabled by default): On Unix platform, compiles with the X11 backend
  • wayland (enabled by default): On Unix platform, compiles with the Wayland backend
  • mint: Enables mint (math interoperability standard types) conversions.

MSRV Policy

The Minimum Supported Rust Version (MSRV) of this crate is 1.65. Changes to the MSRV will be accompanied by a minor version bump.

As a tentative policy, the upper bound of the MSRV is given by the following formula:

min(sid, stable - 3)

Where sid is the current version of rustc provided by Debian Sid, and stable is the latest stable version of Rust. This bound may be broken in the event of a major ecosystem shift or a security vulnerability.

The exception to this is for the Android platform, where a higher Rust version must be used for certain Android features. In this case, the MSRV will be capped at the latest stable version of Rust minus three. This inconsistency is not reflected in Cargo metadata, as it is not powerful enough to expose this restriction.

All crates in the rust-windowing organizations have the same MSRV policy.

Platform-specific usage


Note that windows don't appear on Wayland until you draw/present to them.


To run the web example: cargo run-wasm --example web

Winit supports compiling to the wasm32-unknown-unknown target with web-sys.

On the web platform, a Winit window is backed by a <canvas> element. You can either provide Winit with a <canvas> element, or let Winit create a <canvas> element which you can then retrieve and insert it into the DOM yourself.

For example code using Winit with WebAssembly, check out the web example. For information on using Rust on WebAssembly, check out the Rust and WebAssembly book.


The Android backend builds on (and exposes types from) the ndk crate.

Native Android applications need some form of "glue" crate that is responsible for defining the main entry point for your Rust application as well as tracking various life-cycle events and synchronizing with the main JVM thread.

Winit uses the android-activity as a glue crate (prior to 0.28 it used ndk-glue).

The version of the glue crate that your application depends on must match the version that Winit depends on because the glue crate is responsible for your application's main entrypoint. If Cargo resolves multiple versions they will clash.

winit glue compatibility table:

winit ndk-glue
0.29.1-beta android-activity = "0.5.0-beta.1"
0.28 android-activity = "0.4"
0.27 ndk-glue = "0.7"
0.26 ndk-glue = "0.5"
0.25 ndk-glue = "0.3"
0.24 ndk-glue = "0.2"

The recommended way to avoid a conflict with the glue version is to avoid explicitly depending on the android-activity crate, and instead consume the API that is re-exported by Winit under winit::platform::android::activity::*

Running on an Android device needs a dynamic system library, add this to Cargo.toml:

name = "main"
crate-type = ["cdylib"]

All Android applications are based on an Activity subclass and the android-activity crate is designed to support different choices for this base class. Your application must specify the base class it needs via a feature flag:

Base Class Feature Flag Notes
NativeActivity android-native-activity Built-in to Android - it is possible to use without compiling any Java or Kotlin code. Java or Kotlin code may be needed to subclass NativeActivity to access some platform features. It does not derive from the AndroidAppCompat base class.
GameActivity android-game-activity Derives from AndroidAppCompat which is a defacto standard Activity base class that helps support a wider range of Android versions. Requires a build system that can compile Java or Kotlin and fetch Android dependencies from a Maven repository (or link with an embedded release of GameActivity)

For example, add this to Cargo.toml:

winit = { version = "0.29.1-beta", features = [ "android-native-activity" ] }

[target.'cfg(target_os = "android")'.dependencies]
android_logger = "0.11.0"

And, for example, define an entry point for your library like this:

#[cfg(target_os = "android")]
use winit::platform::android::activity::AndroidApp;

#[cfg(target_os = "android")]
fn android_main(app: AndroidApp) {
    use winit::platform::android::EventLoopBuilderExtAndroid;


    let event_loop = EventLoopBuilder::with_user_event()

For more details, refer to these android-activity example applications.

Converting from ndk-glue to android-activity

If your application is currently based on NativeActivity via the ndk-glue crate and building with cargo apk then the minimal changes would be:

  1. Remove ndk-glue from your Cargo.toml
  2. Enable the "android-native-activity" feature for Winit: winit = { version = "0.29.1-beta", features = [ "android-native-activity" ] }
  3. Add an android_main entrypoint (as above), instead of using the '[ndk_glue::main] proc macro from ndk-macros (optionally add a dependency on android_logger and initialize logging as above).
  4. Pass a clone of the AndroidApp that your application receives to Winit when building your event loop (as shown above).


A lot of functionality expects the application to be ready before you start doing anything; this includes creating windows, fetching monitors, drawing, and so on, see issues #2238, #2051 and #2087.

If you encounter problems, you should try doing your initialization inside Event::NewEvents(StartCause::Init).


Similar to macOS, iOS's main UIApplicationMain does some init work that's required by all UI related code, see issue #1705. You should consider creating your windows inside Event::NewEvents(StartCause::Init).

Redox OS

Redox OS has some functionality not present yet, that will be implemented when its orbital display server provides it.

Popular X11 Projects
Popular Wayland Projects
Popular User Interface Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.