Tiny Online Tools logoTiny Online ToolssearchSearch tools…grid_viewAll Tools
Homechevron_rightReverse Engineering Toolschevron_rightWASM Import/Export VisualizerWASM Import/Export Visualizer

WASM Import/Export Visualizer

See what a WebAssembly module needs from its host and what it offers back, grouped by module namespace, side by side.

upload_file

Click to browse or drag & drop files here

Drop a .wasm file to visualize its imports and exports

Accepted: .wasm

Similar Tools

WASM Binary Explorer

WASM Binary Explorer

Browse a WebAssembly module's sections, functions, imports, exports, memories, tables and globals with exact byte offsets and sizes.

WASM Size Analyzer

WASM Size Analyzer

Find out which functions and data segments dominate a WebAssembly module's size, with an exact sorted breakdown and a visual treemap.

WASM Decompiler

WASM Decompiler

Turn a WebAssembly binary into readable WAT text, with a per-function call graph, control-flow shape, and a best-effort toolchain guess.

WASM Demangler

WASM Demangler

Demangle Rust and C++ symbol names found in a WebAssembly binary, one at a time or in bulk across a whole file.

Split PDF

Split PDF

Split a PDF file into individual pages or page ranges.

Embroidery File Converter

Embroidery File Converter

Convert an embroidery file to DST or EXP — the only two formats this tool can write correctly. Reads DST, EXP, JEF, PES and PEC.

Mach-O Inspector

Mach-O Inspector

Inspect macOS and iOS Mach-O binaries: architecture, load commands, segments, sections and linked libraries, right in your browser.

apps

More Tools

Browse our full collection of free online tools.

Every WebAssembly module has a boundary: things it imports from its host environment, and things it exports back for the host to call. That boundary is where the interesting questions live — what does this module actually need to run, and what does it expose? The WASM Import/Export Visualizer lays that boundary out clearly, entirely in your browser.

Drop in a .wasm file and the tool parses its import and export sections with the same byte-accurate parser used across our WebAssembly tools, then:

  • Groups imports by module namespace (env, wasi_snapshot_preview1, a JS glue namespace, and so on), resolving each imported function's real parameter/result signature from the module's type section.
  • Groups exports by kind (function, memory, table, global), resolving function-export signatures the same way, correctly accounting for the fact that imported functions occupy the lowest function indices.
  • Shows both side by side, imports on the left and exports on the right, so you can see the whole host/module contract at a glance.

Where the import namespace and field names give a real, checkable signal, the tool adds a modest, evidence-based note — for example recognizing wasi_snapshot_preview1 as likely a WASI-targeted build, or a cluster of emscripten_*/__cxa_* imports as likely Emscripten's C/C++ runtime glue. These notes always show the actual matching import names that produced them and are phrased as "likely", never as certainty — this tool reads real binary data, it doesn't guess at what it can't see.

Use it to understand what a third-party .wasm file actually depends on before running it, to compare the host surface of two builds, to spot an unexpectedly large import surface, or simply to learn how a WebAssembly module talks to its environment.