Install wabt with Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, scoop

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• spectest-interp
• wasm-decompile
• wasm-interp
• wasm-objdump
• wasm-stats
• wasm-strip
• wasm-validate
• wasm2c
• wasm2wat
• wast2json
• wat-desugar
• wat2wasm

Project history

The WABT repository was created in September 2015, during WebAssembly's early design period. It lives under the WebAssembly GitHub organization and describes itself as a suite of tools for WebAssembly rather than a compiler front end or runtime.

WABT grew alongside WebAssembly's standardization. The WebAssembly Community Group reached initial browser consensus in 2017, the W3C publication history records the first public working draft in February 2018, and WebAssembly Core 1.0 became a W3C Recommendation on 5 December 2019. WABT's job throughout that period was to provide practical tools around the binary and text formats that implementers, compiler authors, and curious low-level users needed.

Adoption history

The official WebAssembly advanced-tools page points low-level users toward tools for building and processing source files and generated binary content, especially compiler writers and people experimenting with the raw format. WABT became one of the default packages for that niche because it exposes the core format operations directly: text-to-binary, binary-to-text, validation, objdump-style inspection, interpretation, and test conversion.

How it is used

The most recognizable WABT commands are `wat2wasm` and `wasm2wat`, which translate between WebAssembly text format and binary format. The suite also includes `wasm-objdump`, `wasm-interp`, `wasm2c`, `wasm-strip`, `wasm-validate`, `wast2json`, `wasm-stats`, and `spectest-interp`, covering inspection, execution, C translation, section stripping, validation, and spec-test workflows.

In practice, WABT is used by people hand-writing WAT, debugging generated Wasm, checking whether a module validates, reducing binaries for test cases, converting spec tests into runnable artifacts, or inspecting compiler output without committing to a full browser or runtime.

Why package nerds care

WABT is significant because WebAssembly has a compact binary representation and a human-readable text representation, and developers constantly need to move between the two. For package nerds it is the binutils-like kit for Wasm: boring, sharp, scriptable tools that make the format observable.

Unlike the WebAssembly spec interpreter, which the WABT README characterizes as deliberately simple and specification-oriented, WABT is written in C/C++ and designed for easier integration into other systems. That makes it useful in build systems, tests, research tooling, and language-toolchain plumbing.

Timeline

• 2015: The WebAssembly/wabt repository was created.
• 2017: WebAssembly browser implementers reached consensus on the initial MVP API and binary format.
• 2018: WebAssembly Core 1.0 entered W3C First Public Working Draft status.
• 2019: WebAssembly Core 1.0 became a W3C Recommendation.
• 2020s: WABT continued tracking WebAssembly feature work through tool feature flags and releases.

Related projects

• WABT is adjacent to Emscripten, Binaryen, WebAssembly specifications, WASI, browser developer tools, and language compilers that emit Wasm. It is often used after a compiler has produced a module, or before a runtime consumes one.

Sources

• https://api.github.com/repos/WebAssembly/wabt
• https://github.com/WebAssembly/wabt
• https://webassembly.org/features/
• https://webassembly.org/getting-started/advanced-tools/
• https://webassembly.org/specs/
• https://www.w3.org/standards/history/wasm-core-1/