Published August 22, 2026

Try Flutter Web with WebAssembly Week: 2x to 5x Faster Performance

Google has launched Try Flutter Web with WebAssembly Week, a focused initiative running from August 17 to August 21 that invites developers to test their applications using WebAssembly compilation. The campaign calls on the Flutter community to opt into Wasm, measure the gains, and help resolve whatever blockers remain on the path to making WebAssembly the default compiler target for Flutter Web.

WebAssembly support in Flutter Web was stabilized back in version 3.22, pairing the Dart compiler with WebAssembly Garbage Collection, better known as WasmGC. Since then the technology has quietly proven itself in the real world. Dart DevTools, one of the most complex and interactive Flutter web applications in existence, has shipped with WebAssembly by default since late 2024. Today more than 97 percent of developers using DevTools run it on Wasm, enjoying smooth UI inspection, fast loading, and solid stability.

The Performance Numbers

According to Google's analysis, more than 58 percent of existing Flutter web apps already compile to WebAssembly with zero code changes. For those that do, the performance gains are substantial. Compiling to Wasm brings the benefit of both compiler acceleration through dart2wasm and multithreaded rendering through skwasm.

  • Up to two times faster frame times, sustaining 60 frames per second under churn that drops JavaScript to roughly 30 frames per second
  • Up to 2.5 times faster widget building and execution using native WasmGC structures
  • Multithreaded background rasterization via skwasm, keeping the main browser thread responsive
  • Over three times smoother frame consistency, cutting jitter from about 1.5 milliseconds down to about 0.5 milliseconds
  • A minimal bundle size change of no more than five percent larger compressed over the wire

The measurements were taken in Chrome on an Apple M4 Pro MacBook at a 60 Hz refresh cap under medium stress with hundreds of animated nodes. Google points to a live comparison demo that translates the headline gains into concrete terms: two times faster total frame times, 2.5 times faster widget build speeds, and three times lower jitter.

Why JavaScript Is Still the Default

If Wasm delivers better speed and stability, why does flutter build web still default to JavaScript? The answer comes down to a practical concern: some pub.dev packages still rely on legacy JavaScript interop through dart:html or dart:js, which needs to be updated for Wasm compatibility. This creates a chicken-and-egg dilemma. Google cannot make Wasm the default until more ecosystem packages update their interop code, and package authors are slow to prioritize those updates until developers opt in and request Wasm support.

That is exactly the friction WebAssembly Week is designed to break. By asking developers to test their apps, report blockers, and share wins over a single week, the initiative aims to give package maintainers the signal they need to invest in modern package:web and dart:js_interop migration. The supporting documentation has also been refreshed with guidance on WebAssembly on Flutter Web, migrating away from dart:html and dart:js, web building and deployment, and a Flutter web technical FAQ.

How to Participate

Getting involved requires three straightforward steps. First, upgrade to Flutter 3.47 with flutter upgrade to pick up the newest WasmGC optimizations and runtime fixes. Second, build with Wasm by running flutter build web --wasm in the project directory. Third, report any package or runtime issues through the official Wasm feedback form so engineers can help unblock migration. Developers who get clean builds and faster performance are encouraged to share metrics and framerate gains using the hashtag FlutterWasmWeek.

Throughout the week, Dart and Flutter engineers are triaging incoming issues in real time to help clear migration roadblocks, while the developer relations team surfaces success stories across community channels. For anyone building dashboards, internal tools, or full web applications with Flutter, the invitation is a low-cost way to see whether Wasm unlocks meaningful performance on their own hardware and codebase.

By testing apps and resolving package dependencies together this week, the community can pave the way toward making WebAssembly the default compiler for Flutter Web. The experiment requires nothing more than running flutter upgrade, trying flutter build web --wasm, and reporting what happens. The path from a JavaScript-by-default framework to a Wasm-by-default one is increasingly clear, and this week is about taking the first real step in that direction.

For Flutter developers, the practical takeaway is that WebAssembly is no longer a preview feature to watch from a distance. It is battle-tested in production tools, delivers measurable performance gains, and more than half of existing apps can adopt it without changing code. WebAssembly Week is a chance to close the loop and push the ecosystem past the last remaining interop hurdles toward a faster, smoother default for Flutter on the web.