Web FAQ

Not every web page makes sense in Flutter, but we think Flutter is particularly suited for app-centric experiences:

• Progressive Web Apps
• Single Page Apps
• Existing Flutter mobile apps

At this time, Flutter is not suitable for static websites with text-rich flow-based content. For example, blog articles benefit from the document-centric model that the web is built around, rather than the app-centric services that a UI framework like Flutter can deliver. However, you can use Flutter to embed interactive experiences into these websites.

For more information on how you can use Flutter on the web, see Web support for Flutter.

In general, Flutter is geared towards dynamic application experiences. Flutter's web support is no exception. Flutter web prioritizes performance, fidelity, and consistency. This means application output does not align with what search engines need to properly index. For web content that is static or document-like, we recommend using HTML—just like we do on flutter.dev, dart.dev, and pub.dev. You should also consider separating your primary application experience—created in Flutter—from your landing page, marketing content, and help content—created using search-engine optimized HTML.

That said, as mentioned in the roadmap, the Flutter team plans to investigate search engine indexability of Flutter web.

See building a web app with Flutter.

No, but you can use hot restart. Hot restart is a fast way of seeing your changes without having to relaunch your web app and wait for it to compile and load. This works similarly to the hot reload feature for Flutter mobile development. The only difference is that hot reload remembers your state and hot restart doesn't.

You can either use the browser's refresh button, or you can enter "R" in the console where "flutter run -d chrome" is running.

Flutter web apps can run on the following browsers:

• Chrome (mobile & desktop)
• Safari (mobile & desktop)
• Edge (mobile & desktop)
• Firefox (mobile & desktop)

During development, Chrome (on macOS, Windows, and Linux) and Edge (on Windows) are supported as the default browsers for debugging your app.

You can select Chrome or Edge as the target device in Android Studio/IntelliJ and VS Code.

The device pulldown should now include the Chrome (web) option for all channels.

See Creating responsive apps.

No. The file system is not accessible from the browser. For network functionality, use the http package. Note that security works somewhat differently because the browser (and not the app) controls the headers on an HTTP request.

Some plugins require platform-specific imports, particularly if they use the file system, which is not accessible from the browser. To use these plugins in your app, see the documentation for conditional imports on dart.dev.

Dart's concurrency support via isolates is not currently supported in Flutter web.

Flutter web apps can potentially work around this by using web workers, although no such support is built in.

See Embedding Flutter web.

See Web content in Flutter.

Use Flutter DevTools for the following tasks:

• Debugging
• Logging
• Running Flutter inspector

Use Chrome DevTools for the following tasks:

• Generating event timeline
• Analyzing performance—make sure to use a profile build

Use widget tests or integration tests. To learn more about running integration tests in a browser, see the Integration testing page.

See Preparing a web app for release.

Not currently.

Unless stated otherwise, the documentation on this site reflects the latest stable version of Flutter. Page last updated on 2024-10-01. View source or report an issue.