Robots Atlas>ROBOTS ATLAS
Standard

Wasm

2015ActivePublished: 18 November 2026Updated: 18 November 2026Published
Key innovation
A portable, sandboxed bytecode format that runs at near-native speed — the same compiled module runs in the browser and outside it, independent of source language and hardware architecture.
Category
Standard
Abstraction level
Standard
Operation level
ToolingAgent runtimeDeployment
Use cases
Running untrusted code in a sandbox (external sandbox)Isolating and executing code for AI agentsAI inference at the network edge and in the browserApplication plugin and extension systemsPortable server-side runtimes without system containersHigh-performance in-browser computation (games, multimedia, CAD)

How it works

Source code in languages such as C/C++, Rust or Go compiles to a .wasm module (binary format; a human-readable text format, WAT, also exists). Before execution the module is validated and type-checked. A runtime executes instructions on an implicit operand stack — as an interpreter, JIT or AOT. The module operates on an isolated linear memory and has no default access to system resources; it communicates with the outside world only through explicitly imported host functions: in the browser via JavaScript and Web APIs, and outside it via the WASI interface, which grants permissions under a capability-based model.

Problem solved

The web needed a fast, safe and portable compilation target for languages other than JavaScript without giving up the browser's security model. More broadly, Wasm solves running untrusted code in isolation at near-native speed — without the overhead of a full virtual machine or a system container.

Components

Binary instruction format (.wasm)Portable compilation target

A compact, fast-to-load bytecode format; it also has an equivalent text format (WAT) for debugging.

Stack-based virtual machineExecution model

A computational model where instructions operate on an implicit operand stack; hardware-independent.

Linear memoryMemory isolation

An isolated, contiguous memory region for the module — the foundation of the sandbox and memory safety.

Host imports and exportsInterface to the outside world

The module's explicit boundary: functions provided by the host (JS/Web APIs or WASI) and exported by the module.

WASI (WebAssembly System Interface)System interface outside the browser

A standardized, capability-based system interface that lets Wasm modules run outside the browser.

Runtime / execution engineModule execution

An interpreter, JIT or AOT engine that executes modules (e.g. Wasmtime, Wasmer, WasmEdge, wazero).

Evolution

Original paper · 2017 · PLDI 2017 · Andreas Haas
Bringing the Web Up to Speed with WebAssembly
Andreas Haas, Andreas Rossberg, Derek L. Schuff, Ben L. Titzer, Michael Holman, Dan Gohman, Luke Wagner, Alon Zakai, JF Bastien
2015
WebAssembly announced
Inflection point

Major browser vendors announce joint work on WebAssembly.

2017
MVP and support across all major browsers
Inflection point

The MVP design was finished in March 2017; by November 2017 Wasm was supported in all major browsers.

2019
W3C Recommendation
Inflection point

The WebAssembly Core Specification 1.0 became a W3C Recommendation on 5 December 2019.

2024
WASI 0.2

WASI 0.2 was released on 25 January 2024, alongside the Component Model.

Hardware requirements

Primary

Wasm is a portable, hardware-independent format; the same module runs across different CPU architectures.

Good fit

Modules are typically compiled (JIT/AOT) to native CPU code, reaching near-native performance.