简体中文
EnglishWhere to Start with WebAssembly on webassembly.org
Updated
Start with the Getting Started section of webassembly.org, then move to Specs and Docs for the standards and reference material, check Feature Status to see what is currently supported, and use MDN's WebAssembly pages as your day-to-day developer reference. This path suits beginners who want an official, standards-based introduction before writing any code.
What webassembly.org Is For
WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. It is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications. The site is the project's home base: it links to the overview, getting-started material, specifications, documentation, feature status, community channels, and news.
The site itself is a gateway, not a tutorial platform. Its value is pointing you to the authoritative sources rather than teaching syntax step by step.
A Practical Starting Path
1. Read the overview first
The homepage summary explains the four design goals you will keep running into:
- Efficient and fast — the binary format is size- and load-time-efficient, and Wasm aims to execute at native speed by using common hardware capabilities across platforms.
- Safe — Wasm describes a memory-safe, sandboxed execution environment; when embedded in the web it enforces the browser's same-origin and permissions security policies.
- Open and debuggable — modules are designed to be pretty-printed in a textual format for debugging, testing, experimenting, optimizing, learning, and teaching.
- Part of the open web platform — versionless, feature-tested, and backwards-compatible; modules can call into and out of JavaScript and access browser functionality through the same Web APIs available from JavaScript. Wasm also supports non-web embeddings.
Understanding these four points early makes the rest of the documentation easier to place.
2. Use Getting Started to pick your entry point
The Getting Started section is where you decide how you will produce Wasm. Because Wasm is a compilation target rather than a language you typically write by hand, your first decision is which source language and toolchain to use. The site's overview and linked material frame that choice; the detailed language-by-language guidance lives in the documentation it points to.
3. Consult Specs for the standard
The Specs section covers the open standards, which are developed in a W3C Community Group (including representatives from all major browsers) as well as a W3C Working Group. Go here when you need to know precisely what a instruction or module feature means, or when you are implementing a toolchain rather than just using one.
4. Check Feature Status before relying on a capability
Feature Status tells you what is currently supported. This matters because the web platform's versionless, feature-tested model means capabilities arrive incrementally. Check this page before designing around a specific feature, and re-check it when a tutorial you are following assumes something your target browser may not yet provide.
5. Keep MDN open while you build
The site explicitly points to MDN's WebAssembly pages as the developer reference documentation. That is where you go for API-level detail — the JavaScript interface for loading and running modules, the textual format, and related browser APIs — once you move from reading to building.
How the Sections Fit Together
| Section | Use it when you need to… |
|---|---|
| Overview (homepage) | Understand what Wasm is and its design goals |
| Getting Started | Choose a way to compile your source language to Wasm |
| Specs | Check the exact standard, including W3C process context |
| Docs | Find reference documentation, including the MDN pointer |
| Feature Status | Confirm whether a capability is currently supported |
| Community / News | Follow development and ask questions |
Common Sticking Points for Beginners
- Expecting to write Wasm by hand. Most developers compile to it. The textual format exists for debugging, testing, experimenting, optimizing, learning, teaching, and writing programs by hand — treat it as a reading and inspection tool first.
- Skipping Feature Status. Tutorials often assume recent features. Verify against the status page for your target environment.
- Confusing web and non-web use. Wasm supports non-web embeddings, so guidance aimed at browser deployment does not automatically apply to server or embedded runtimes.
- Looking for a full course on the site. webassembly.org orients you and links out; the hands-on reference is MDN, and language-specific toolchains are documented by their own projects.
What to Do Next
Read the homepage overview, open Getting Started to settle on a source language and toolchain, bookmark Specs and Feature Status for lookups, and keep MDN's WebAssembly pages open as your working reference. That sequence gives you the official framing first and the practical detail exactly when you need it.