Standards & Learning
15 entriesThe specification, WASI and where to learn.
Runtimes
9 entriesEngines that run Wasm modules and components outside the browser.
Compilers & Toolchains
19 entriesTurn your code into Wasm and inspect the result.
Serverless, Edge & Cloud-Native
9 entriesPlatforms that run Wasm as functions or services.
Plugins & Extensibility
6 entriesUse Wasm as a safe plugin format.
Browser, Data & AI Applications
6 entriesWasm powering applications.
Related Pages
8 entriesNeighbouring pages on this site.
Frequently Asked Questions
What is WebAssembly?
WebAssembly (Wasm) is a compact binary instruction format that runs in a sandbox at near-native speed. It was designed for browsers and now also runs on servers, at the edge and on embedded devices through runtimes.
What is WASI?
The WebAssembly System Interface gives Wasm modules a standard way to use files, clocks, networking and other system features outside the browser, without tying them to one operating system.
What is the Component Model?
A proposal for composing Wasm components written in different languages through typed interfaces, so they can be linked without custom glue code. Check the Component Model docs for current status.
Which runtime should I choose?
It depends on the workload. Wasmtime emphasizes standards support, WasmEdge targets cloud-native and AI workloads, Wasmer offers a package ecosystem, wazero suits Go hosts, and WAMR and wasm3 suit small devices. Test your own modules.
Does Wasm replace containers?
Not in general. Wasm modules start quickly and are sandboxed, but ecosystem support differs from containers, so many teams run both, for example through containerd shims or Kubernetes projects such as SpinKube.
How current is this page?
Links and project activity were checked in October 2026. WebAssembly standards, runtimes and hosted platforms change quickly, so confirm details in each project's own documentation. Sites that block automated checks are kept and may need a manual click.