WASM
Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.
WebAssembly Preview.
At a glance
| Purpose | A WebAssembly binary module: typed sections of imports, functions, memory, exports, code and data. |
| Extensions | .wasm |
| Poka parser | poka-wasm |
| Viewer | poka-tree-viewer |
| Depth tier | Parser with a shared viewer (see Depth tiers) |
| Breadth tier | B3 Core (see Breadth tiers) |
How much Poka reads
B3 Core. Only the main content type or types are decoded (for example geometry but not materials, layers or annotations, or only one version family). The list of gaps is substantial.
Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-wasm/src/main.rs (504 lines) and plugin.json. No unit tests or tests/samples.rs; the corpus has poka-ini.wasm, read by no test. Covers .wasm. The tree shows one node per section with imports and exports (and their kinds), entry counts, memory limits, the start index and the custom-section names. Judgement: B3: the module's interface is decoded, but function bodies, types and data are not.
What Poka does not read
- Function bodies are not disassembled
- Function signatures (the type section) are counted, not listed
- The name section is named, not decoded, so internal function names are not shown (judgement from the code)
- Data and element segments are not shown
- Component-model binaries are not read (judgement from the code)
Libraries
Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.
- wasmparser (candidate; Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT; Rust; https://github.com/bytecodealliance/wasm-tools/tree/main/crates/wasmparser) — official wasmtime parser
Sources
- parsers/poka-wasm/src/main.rs
- parsers/poka-wasm/plugin.json