Adding the Flutter plugin to Android Studio comes down to one Marketplace search and a restart. That’s really the whole job. No separate installer, no extra download, nothing to configure by hand before the IDE picks it up.
Google’s Flutter team publishes the plugin through the JetBrains Marketplace, and Android Studio pulls in the required Dart plugin at the same time, without asking twice.
Flutter’s own tools documentation ties its current Android Studio guidance to Flutter 3.47, the version noted there as of the page’s most recent update in 2026 (Flutter documentation).
What Is the Flutter Plugin for Android Studio?
Android Studio on its own is a general purpose IDE built mainly for native development, and the Flutter plugin extends that base rather than replacing it. It runs inside the existing IDE instead of installing as a separate program, adding Dart language support and ready-made project templates, plus the run and debug tooling needed to build a Flutter app in the first place.
Once it’s active, a few things show up inside Android Studio that weren’t there before:
- A Flutter project type in the new project wizard
- Run and debug buttons wired to connected devices and emulators
- A widget inspector panel for reading the layout tree
- Hot reload for seeing UI changes without a full rebuild
The plugin doesn’t touch native Android development either. It just sits next to it. What actually sets Flutter apart is cross-platform app development, one Dart codebase compiling to both Android and iOS instead of two separate native projects.
Most Flutter developers don’t even reach for Android Studio to do that, though. Flutter’s own Q2 2026 developer survey found 40% of respondents use Android Studio as an editor, trailing VS Code at 66 percent (Flutter blog, 2026).
What Does the Flutter Plugin Require Before Installation?
Before any plugin gets involved, Android Studio itself has to clear a baseline spec, enough memory, enough disk space, and a supported operating system (Android Developers documentation). The minimums look like this:
- 8 GB RAM minimum
- 8 GB available disk space minimum
- 1280 x 800 minimum screen resolution
- 64-bit Windows, macOS, or Linux
That covers Android Studio by itself, nothing more. Once the Android SDK, emulator images, and an actual Flutter project land on the same drive, plan for more room than the bare minimum suggests.
The plugin also depends on the Flutter SDK, which is a separate download from the plugin itself and doesn’t come bundled with it.
Google recommends managing that SDK the way most teams already manage their own code, through Git version control.
Android Studio installs the Android SDK tools needed to compile and run an app once a device or emulator is connected, and it bundles its own JDK, so a separate Java installation usually isn’t necessary.
Which Android Studio Versions Support the Flutter Plugin?
Plugin builds tie to specific Android Studio versions rather than working identically across every release, since the Flutter plugin tracks Android Studio’s own release cycle rather than shipping on its own schedule.
Android Studio ships under codenamed releases such as Koala, Otter, and Quail, and the plugin publishes a matching build for each one it supports.
| Android Studio Release | Status | Flutter and Dart Plugin Note |
|---|---|---|
| Koala (2024.1.1) | Legacy release | Paired with Dart plugin 241.17502 and Flutter plugin 80.0.2 |
| Otter 3 Feature Drop | Oldest release with active cloud service support | Update required to keep Gemini and Crashlytics features working |
| Quail 4 (2026.1.4) | Current stable release | Newest plugin builds target this release first |
Android Developers documentation notes that cloud service integrations, including Gemini in Android Studio, stay active only on the latest stable channel and on major versions released within the past 10 months.
When an installed build falls outside that window, updating Android Studio clears up the mismatch before the plugin install even starts.
The Dart plugin version isn’t something anyone picks separately, by the way. It installs at whatever build the Flutter plugin specifies for that particular Android Studio release.
How Do You Install the Flutter Plugin in Android Studio?
The install itself is short. One restart at the end is the only real pause, and Android Studio handles most of the rest on its own.
- Open Android Studio and go to Settings, or Preferences on macOS
- Select Plugins from the left panel, then click the Marketplace tab
- Search for Flutter and select the official result published by the Flutter team
- Click Install, and accept the prompt to install the Dart plugin alongside it
- Restart Android Studio when prompted to activate both plugins
None of that changes by project type. The same steps apply whether the eventual app targets phones, tablets, or the web.
Installing on Windows
The path here runs through File, then Settings, then Plugins.
Windows Defender or a corporate antivirus tool occasionally flags the Marketplace download mid install. Whitelisting the Android Studio install directory usually clears it up.
Installing on macOS
The menu sits under Android Studio, then Preferences, instead of File and Settings, which trips up developers moving over from Windows.
- Gatekeeper may ask for permission the first time Android Studio restarts
- Apple Silicon and Intel Macs use the same plugin build
Installing on Linux
Menu location matches Windows: File, then Settings, then Plugins. Snap and tar.gz installs of Android Studio both land on the same Marketplace tab, so the installer format doesn’t really change anything here.
How Do You Set the Flutter SDK Path in Android Studio?
The plugin needs to know where the Flutter SDK actually lives on disk before any Flutter project will build.
If the SDK isn’t downloaded yet, grab it from Flutter’s official site and unzip it somewhere permanent. Not a temp folder, not Downloads.
Android Studio can be pointed at it directly, through Settings, then Languages and Frameworks, then Flutter, by pasting in the SDK folder path. Or the SDK’s bin folder can go on the system PATH environment variable instead, which lets both the IDE and the terminal find it without setting it twice.
The PATH route is worth doing anyway, since command line tools like flutter doctor rely on that same entry.
Path formatting differs by platform. Windows uses a drive letter and backslashes, while macOS and Linux use a forward slash path rooted at the home directory.
Should You Install the Flutter Plugin From the Marketplace or Manually?
Almost everyone installs through the Marketplace, and for good reason. It’s one click from inside Android Studio, no separate download involved, and new plugin builds just show up as updates on their own. The catch is that it needs outbound internet access from the IDE itself, and that’s the one thing that trips people up on a locked down machine.
A manual install exists for exactly that situation, a corporate proxy blocking things, or a fully air gapped machine. There, the plugin zip gets downloaded separately and installed from disk, and every future update has to be repeated by hand rather than appearing automatically.
JetBrains Marketplace listings show the Flutter plugin has passed 25 million downloads, with the Dart plugin close behind at nearly 29 million, both through the Marketplace alone (JetBrains Marketplace listings, checked September 2026). That volume is part of why the Marketplace route stays the default recommendation. Most installation problems reported online trace back to manual installs missing a dependency the Marketplace would have handled automatically.
How Do You Verify the Flutter Plugin Installed Correctly?
A couple of quick checks confirm the plugin actually took, before touching any project code.
Run flutter doctor from a terminal. A clean result shows checkmarks next to Flutter, the Android toolchain, and Android Studio itself.
A failing line under Android Studio usually means the Flutter or Dart plugin isn’t installed, even if the IDE opened without any errors.
- Open Settings, then Plugins, then Installed, and confirm both Flutter and Dart appear in the list
- Start a new project and check whether Flutter shows up as a project type in the wizard
Developers still learning their way around Android Studio can treat that wizard listing as the simplest proof the setup worked, since a missing plugin means Flutter never appears as an option at all.
No dialog, no error message either way. The wizard just quietly leaves Flutter off the list.
How Do You Create a New Flutter Project in Android Studio?
Once the plugin is active, creating a project takes a few clicks from the Welcome screen or the File menu.
Select New Project, then choose Flutter from the list of project types. Android Studio only shows this option when the plugin loaded correctly in the first place.
Before generating anything, it’s worth checking that the Flutter SDK path already shows the location set earlier, that the project name and Android package identifier look right, and which platforms are included, Android, iOS, web, or desktop.
Android Studio then generates the default counter app, a small template with one button and a number that increments on tap.
A Gradle sync runs automatically right after the files are created, since the Android side of a Flutter project still builds through Gradle underneath.
Run the template on a connected device or emulator to confirm it launches. A blank white screen for a few seconds usually just means the sync hasn’t finished. It’s not automatically broken.
How Do You Fix Common Flutter Plugin Installation Errors?
Most installation problems come back to the same handful of causes, and none of them require reinstalling anything.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Plugin missing from Marketplace search | Stale plugin cache or an outdated Android Studio build | Clear the plugin cache, update Android Studio, search again |
| SDK path rejected as invalid | Path points to a subfolder instead of the SDK root | Point to the folder that directly contains bin and packages |
| flutter doctor flags the Android SDK | Command line tools or licenses were never installed | Run flutter doctor –android-licenses and accept each prompt |
| Plugin shows installed but stays inactive | Android Studio was closed instead of restarted | Restart the IDE fully rather than dismissing the dialog |
The official Flutter repository documents the exact line developers see: “Android licenses not accepted. To resolve this, run: flutter doctor –android-licenses” (GitHub, flutter/flutter).
That message shows up whether the SDK was installed through Android Studio or downloaded separately, and accepting the licenses is the only real fix for it.
There’s a related quirk buried in the plugin’s own issue tracker that’s easy to lose an afternoon to. Android Studio reads the PATH environment variable only once at startup, so adding the Flutter SDK to PATH after the IDE is already open does nothing until it’s restarted (GitHub, flutter/flutter-intellij, issue #601).
When Does the Flutter Plugin Not Work in Android Studio?
A handful of situations break the plugin outright, or just keep it from applying in the first place.
Canary builds are one of them. flutter-intellij’s own setup notes state that Canary versions of Android Studio are generally not supported, since plugin builds target stable releases only. An Android Studio build old enough to sit outside the plugin’s supported range won’t list Flutter as an installable option at all, no matter how the search is phrased.
| Condition | Why It Fails | What Actually Works |
|---|---|---|
| Android Studio Canary or Beta build | Plugin builds target stable releases only | Switch to the latest stable Android Studio release |
| Flutter SDK far behind current | Old SDKs pair only with old plugin builds | Update the Flutter SDK, then reinstall or update the plugin |
| Command line only workflow | No IDE plugin is involved at any point | Use flutter create and flutter run directly from a terminal |
| Locked down corporate network | Marketplace domains are blocked at the firewall | Whitelist the JetBrains domains or install the plugin manually |
The plugin’s own compatibility record shows how far that drift can go. Flutter SDK builds up to v3.7.12 only ever worked with plugin version 83.0.4 and earlier, while v3.16.0 and everything after it needs a current plugin build (GitHub, flutter/flutter-intellij).
A project pinned to an old Flutter SDK for compatibility reasons will keep hitting plugin errors until one side or the other actually gets updated.
Command line only workflows are a legitimate case where the plugin simply doesn’t apply. flutter create, flutter run, and flutter build all handle basic software development tasks without Android Studio open at all.
Corporate and school networks are the other common blocker. JetBrains support documentation lists plugins.jetbrains.com, download.jetbrains.com, download-cf.jetbrains.com, and account.jetbrains.com as the domains that need outbound access over port 443 for the Marketplace to load (JetBrains, intellij-support.jetbrains.com).
When none of those domains are reachable, Settings shows a “Marketplace plugins are not loaded” message instead of search results, and a manual install becomes the only path forward.
FAQ on How To Add The Flutter Plugin In Android Studio
What Tools Does the Plugin Add to Android Studio Once Installed?
Beyond the new project type, the plugin adds a Dart analysis engine for real-time linting, a DevTools launcher for performance and network profiling, and a Flutter Outline panel for navigating the widget tree without scrolling through nested build methods.
Do You Need Xcode or Extra SDKs for iOS Builds Too?
Only if the target includes iOS. Android Studio and the Flutter plugin handle Android builds on their own; iOS builds still require Xcode and CocoaPods on macOS, installed and configured separately from anything the plugin sets up.
Does the JDK Version Affect Plugin Compatibility?
Indirectly. The plugin itself runs on Android Studio’s bundled JDK, but Gradle and the Android Gradle Plugin used to build the app enforce their own minimum Java version, and mismatches there surface as build failures, not plugin errors.
How Do You Update the Flutter Plugin to a Newer Version?
Open Settings, then Plugins, then Updates. Android Studio lists any pending Flutter or Dart plugin update there with a one click Update button, and applying it still requires the usual restart before the new build activates.
How Do You Uninstall or Reinstall the Flutter Plugin?
From Settings, then Plugins, then Installed, select Flutter, and click Uninstall. Reinstalling means repeating the Marketplace search and install steps from scratch, since Android Studio doesn’t keep a saved copy of a removed plugin locally.
Does Installing the Plugin Require an Internet Connection Every Time?
No. Internet access only matters during installation and when checking for updates. Once installed, the Flutter plugin, the Dart plugin, and an already downloaded Flutter SDK all work offline for coding, running, and debugging a project.
Can Android Studio Run Flutter Projects Without the Dart Plugin Installed?
Not really. The Flutter plugin depends on the Dart plugin for language parsing and analysis, and the Marketplace installs both together automatically. Removing the Dart plugin afterward breaks Flutter support even if the Flutter plugin stays installed.
What Should You Fix First in How To Add The Flutter Plugin In Android Studio?
Check the Flutter SDK path first when the whole process stalls, ahead of plugin version, network access, or the Android Studio build itself.
A short sequence catches most stalls, worth going through in this order:
- SDK path points to the root folder
- Android Studio build matches the plugin’s supported release
- A full restart, not just closing the install dialog
A wrong path produces the same error as a version mismatch, so ruling it out first saves an unnecessary reinstall.
That oldest workable build isn’t fixed, either. Cloud service support rolls on a ten-month window, so the version excluded today shifts again once Android Studio ships past Quail 4, a boundary last confirmed in September 2026.
The next real step is getting Android Studio’s emulator running, since a working plugin only proves itself once a device exists to receive the build.
- How to Turn On Dark Mode in Notepad++ (Built-In, No Plugin) - October 3, 2026
- PostgreSQL Cheat Sheet - October 2, 2026
- How to Repair a Corrupt SQL Server Database Without Any Data Loss - October 2, 2026
