windows-rs is a family of crates for Windows APIs, from raw bindings to declarative UI. This page lists the crates by task.

• Samples
• Releases

Most crates cover one area, such as strings, errors, registry access, or collections. The windows and windows-sys crates provide broad API coverage behind API-group features.

For most projects, prefer the focused crates below, and generate a minimal, project-specific binding with windows-bindgen for any additional APIs you need.

Start with what you are trying to do and add the smallest crate that covers it. Follow the link for usage and examples.

The full categorized index follows. Each crate has one page under crates/ covering both usage and internals - how the crate is built and maintained (the tool_bindings / tool_reactor / tool_package codegen pipeline, generated files, and conventions). Each crate's own readme.md is the user-facing introduction with a quick example, and the per-crate page links to it. Item-level API reference is the generated rustdoc on docs.rs, linked from every page.

The #[interface] and #[implement] macros are part of windows-core, split into the windows-interface and windows-implement crates only because Rust requires procedural macros to live in a dedicated proc-macro crate.

These crates package functionality that is part of other crates but must ship separately. windows-interface and windows-implement are part of windows-core (see above); Rust requires their proc macros to live in a dedicated proc-macro crate.

These crates project the entire Windows API surface. For new projects, prefer a focused binding generated with windows-bindgen, or compose the smaller crates above.

• Dependencies - every external SDK, header set, metadata file, and runtime the build and tooling depend on: what version is used, where it is set, how it is obtained, and how to update it.