Roadmap

In November 2017, WebAssembly CG members representing four browsers, Chrome, Edge, Firefox, and WebKit, reached consensus that the design of the initial (MVP) WebAssembly API and binary format is complete to the extent that no further design work is possible without implementation experience and significant usage.

After the initial release, WebAssembly has been gaining new features through the standardization process. For the complete list of current proposals and their respective stages, check out the WebAssembly/proposals repo.

The table below aims to track implemented features in popular engines:

  1. Requires flag chrome://flags/#enable-webassembly-garbage-collection
  2. Requires flag chrome://flags/#enable-experimental-webassembly-features
  3. Enabled in Nightly, unavailable in Beta/Release
  4. Supported in desktop Safari since 14.1 and iOS Safari since 14.5
  5. Requires flag --wasm-features=memory64
  6. Requires flag --wasm-features=multi-memory
  7. Requires flag --experimental-wasm-extended-const
  8. Requires flag --experimental-wasm-memory64
  9. Requires flag --experimental-wasm-relaxed-simd
  10. Requires flag --experimental-wasm-return-call
  11. Requires flag --experimental-wasm-type-reflection
  12. Requires flag --v8-flags=--experimental-wasm-extended-const
  13. Requires flag --v8-flags=--experimental-wasm-memory64
  14. Requires flag --v8-flags=--experimental-wasm-relaxed-simd
  15. Requires flag --v8-flags=--experimental-wasm-return-call
  16. Requires corresponding v8 flag (--v8-flags="...")
  17. Requires flag --enable-exceptions
  18. Requires flag --enable-memory64
  19. Requires flag --enable-multi-memory

To detect supported features at runtime from JavaScript, check out the wasm-feature-detect library, which powers the “Your browser” column above.