Skip to content

Building a web application with Flutter

Jonah Williams edited this page Jun 21, 2019 · 6 revisions

Current Status

Flutter now has early experimental support for running flutter web applications. There are still many missing features and known performance issues, so it isn't recommended for production use. This requires the latest flutter master from at least commit 4c0145.

IMPORTANT: The unforked flutter web workflow is still missing several features currently present in flutter_web. Work is ongoing to upstream these changes in Flutter proper.


Only the flutter gallery and hello_world have been configured to work with flutter for web. The additional configuration can be generated with the command flutter create --web ..


The web workflow is still gated behind the environment variable FLUTTER_WEB, which must be set to true in the shell in question. (The env check will be removed for the command line shortly lands and in IDE's much later). If this is setup correctly, then flutter devices will output a device named web. flutter doctor will also check for a locatable chrome executable which is required for development mode and tests. If one cannot be found, try setting the CHROME_EXECUTABLE environment variable to the path to your Chrome executable.

$ flutter devices
> 1 connected device:
> Chrome • chrome • web-javascript • Google Chrome 75.0.3770.80 
$ flutter doctor
> Doctor summary (to see all details, run flutter doctor -v):
> [✓] Flutter (Channel unknown, v1.7.3-pre.52, on Mac OS X 10.14.5 18F132, locale en-US)
> [✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
> [✓] Xcode - develop for iOS and macOS (Xcode 10.0)
> [✓] iOS tools - develop for iOS devices
> [✓] Chrome - develop for the web
>     ! CHROME_EXECUTABLE not set
> [!] Android Studio (version 3.3)
>     ✗ Flutter plugin not installed; this adds Flutter specific functionality.
>     ✗ Dart plugin not installed; this adds Dart specific functionality.
> [✓] IntelliJ IDEA Community Edition (version 2018.3.4)
> [✓] VS Code (version 1.35.0)
> [✓] Connected device (1 available)

flutter run will launch the application using the development compiler in a Chrome browser. The name of the web "device" is currently "chrome", but this doesn't need to be specified if there are no other devices attached.

$ flutter run -d chrome
> Running "flutter pub get" in hello_world...                         0.4s
> Compiling lib/main.dart for the Web...                              1.0s
> 🔥  To hot restart (and rebuild state), press "R".
> For a more detailed help message, press "h". To quit, press "q".

To see additional build output, you can run with -v. If there are issues with changes not propagating or compilation errors that can't be resolved, run flutter clean and then file a bug describing what you changed.

This includes a basic hot restart functionality: though IDEs do support hot reload on save, this functionality does not exist yet for flutter web. While flutter web intends to support modern browsers for shipped applications, for development we require the use of a chrome browser to make use of Chrome devtools.


Plugins are not currently supported in flutter web.

Engine development

Development on the web engine requires the same setup as the normal engine workflow. Follow the setup in the engine contributing guide at Setting-up-the-Engine-development-environment.

To build the web engine:

./flutter/tools/gn --unopt --full-dart-sdk
ninja -C out/host_debug_unopt

And then to run with a locally built web engine:

flutter run -d chrome --local-engine=host_debug_unopt

The web implementation of dart:ui is located at and the rules to build the sdk are located at

Subsequent changes to the dart sdk in the engine will require another run of ninja -C out/host_debug_unopt and a restart or browser refresh. Currently the web compilers do not recompile the web engine, and instead it works because the dart sdk is loaded as a separate javascript bundle in the browser during development mode.

Release builds

A release build uses dart2js instead of the development compiler to produce a single JavaScript file. This can be run with the release flag or built using flutter build web. This will output files at build/web, including the assets, which need to be served together. There is no support for "building" a debug build, since they consist of potentially thousands of small files.


Unit tests can be run on the web with the argument --platform=chrome. This will compile the tests to JavaScript and run them in a headless Chrome browser. Note that there are still compatibility issues with many flutter tests and bugs with the test bootstrap itself that will need to be resolved.

$ flutter test --platform=chrome
> Downloading Web SDK...                                              1.1s
> Running "flutter pub get" in flutter...                             0.4s
> Compiling test/scheduler/debug_test.dart for the Web...   

There is no current support for driver tests.

Flutter Wiki


Framework repo

Engine repo


Experimental features

Release Notes

Clone this wiki locally
You can’t perform that action at this time.