Bindings for all Web APIs, a procedurally generated crate from WebIDL

71 releases

0.3.69 Mar 4, 2024
0.3.67 Jan 12, 2024
0.3.66 Nov 28, 2023
0.3.64 Jun 12, 2023
0.0.1 Jul 19, 2018

#1 in #web-api

Download history 678240/week @ 2024-01-03 718403/week @ 2024-01-10 752846/week @ 2024-01-17 717554/week @ 2024-01-24 761918/week @ 2024-01-31 774127/week @ 2024-02-07 758171/week @ 2024-02-14 802944/week @ 2024-02-21 790354/week @ 2024-02-28 802867/week @ 2024-03-06 757587/week @ 2024-03-13 796635/week @ 2024-03-20 754780/week @ 2024-03-27 796318/week @ 2024-04-03 801247/week @ 2024-04-10 658819/week @ 2024-04-17

3,161,905 downloads per month
Used in 22,835 crates (1,140 directly)


182K SLoC


Raw bindings to Web APIs for projects using wasm-bindgen.

Crate features

This crate by default contains very little when compiled as almost all of its exposed APIs are gated by Cargo features. The exhaustive list of features can be found in crates/web-sys/Cargo.toml, but the rule of thumb for web-sys is that each type has its own cargo feature (named after the type). Using an API requires enabling the features for all types used in the API, and APIs should mention in the documentation what features they require.

How to add an interface

If you don't see a particular web API in web-sys, here is how to add it.

  1. Copy the WebIDL specification of the API and place it in a new file in the webidls/unstable folder. You can often find the IDL by going to the MDN docs page for the API, scrolling to the bottom, clicking the "Specifications" link, and scrolling to the bottom of the specification page. For example, the bottom of the MDN docs on the MediaSession API takes you to the spec. The very bottom of that page is the IDL.
  2. Annotate the functions that can throw with [Throws]
  3. Run cargo run --release --package wasm-bindgen-webidl -- webidls src/features ./Cargo.toml
  4. Run git add . to add all the generated files into git.