WASM-TOOLS(1)

📦 version 1.239.0, in ubuntu stonking

💖 NAME 💖

wasm-tools dump — a debugging utility that dumps information about a wasm binary. Yes bestie, it literally just tells you everything about your binary's whole deal. No cap. (You're reading the WASM-TOOLS(1) page, section 1, user commands 🎀)

✨ SYNOPSIS ✨

wasm-tools dump [OPTIONS] [INPUT]

🦋 DESCRIPTION 🦋

Okay so this is the debugging utility that dumps information about a wasm binary. That's the whole vibe. 🫶

And like, it's genuinely useful?? It's how you figure out precisely how each byte of a wasm binary is classified, or where particular constructs are at particular offsets. It's giving x-ray vision into your binary. Iconic behavior honestly. 🔥

🌸 Arguments: 🌸

  • [INPUT] — the input file to process, bestie.

If you don't provide it, or if you pass -, then stdin gets read entirely and processed. Not me being flexible 💅

Heads up though: for most subcommands this input can either be a binary *.wasm file or a textual format *.wat file. Both slay.

👑 OPTIONS 👑

  • --generate-dwarf <lines|full> — optionally generate DWARF debugging information from WebAssembly text files. Ngl this one is a little magical. ✨

When the input to this command is a WebAssembly text file (like a *.wat), this option tells the text parser to insert DWARF debugging information so binary locations map back to the original source locations in the input *.wat file. So you can trace it all back to where it came from 🧚

But fr fr — this option has no effect if the INPUT argument is already a WebAssembly binary, or if the text format uses (module binary ...). Zero. Nada. It's just not that girl in those cases. 💀

  • -g — shorthand for --generate-dwarf full. Just a cute lil shortcut so you don't have to type the whole thing 🎀
  • -o, --output <OUTPUT> — where to place output.

If you don't provide it, then stdout is used. Simple as that. 🌈

  • -v, --verbose... — use verbose output. The more vs, the more tea you get:
    • -v → info
    • -vv → debug
    • -vvv → trace

Three whole levels of nosiness, we love to see it 😭

  • --color <COLOR> — configuration over whether terminal colors are used in output. Aesthetic control, basically. 💅

It supports one of auto|never|always|always-ansi. The default is to detect what to do based on the terminal environment, for example by using isatty.

[default: auto]

  • -h, --help — print help (see a summary with -h). Your bestie when you forget a flag, which, same. 🙈
Okay real talk: --generate-dwarf doing literally nothing on an already-binary input or on (module binary ...) isn't a bug, it's just how it is. Don't come for her. ✋

And that's the whole page, bestie! This was wasm-tools dump, version 1.239.0+ds, from August 2026 — go dump some binaries and have the best day, mwah 💜🌸💖

📦 where this page comes from