How to Install Flutter on Windows 11 for Android Development

Updated: September 2026

Installing Flutter on Windows 11 is only the first half of the setup.

If your goal is Android development, you also need a working Android toolchain, the correct SDK components, a compatible Java environment and a device or emulator that Flutter can detect.

This guide covers the full setup from a clean Windows machine to a working Flutter Android development environment.

What You Need

• Windows 11
• Git for Windows
• Flutter SDK
• Android SDK
• A compatible Java Development Kit
• VS Code, Android Studio or another supported editor
• An Android phone or emulator for testing

Flutter Installation vs Android Setup

These are related, but they are not the same thing.

Task	Purpose
Install Flutter	Provides the Flutter SDK and Dart tools
Configure PATH	Lets Windows run Flutter commands from any terminal
Install Android tools	Provides the SDK, platform tools and build components
Configure Java	Supports Android build tooling
Run flutter doctor	Checks whether the environment is correctly configured
Connect a device	Allows you to run and test Android apps

Step 1: Install Git for Windows

Flutter uses Git as part of its normal SDK and development workflow.

Install the latest version of Git for Windows from the official Git website.

After installation, open PowerShell or Command Prompt and run:

git --version

If Windows prints a Git version number, Git is available in your terminal.

Step 2: Install Flutter

Flutter supports more than one installation method.

The important part is to keep the SDK in a sensible location that does not require unnecessary administrator permissions.

A short path is usually easier to manage on Windows.

For example:

C:\Flutter

or:

C:\dev\flutter

Avoid Deep Installation Paths

Very long paths can create problems on Windows, especially when Git or package files produce deeply nested directories.

Flutter's own troubleshooting guidance recommends using a shorter SDK location if you encounter Windows filename-length errors.

For example, a path such as:

C:\Users\YourName\Documents\Development\Mobile\Flutter\flutter

is unnecessarily deep compared with:

C:\Flutter

Step 3: Add Flutter to PATH

Windows needs to know where the Flutter command-line tools are located.

The folder you add to PATH is the Flutter SDK's bin directory.

Example:

C:\Flutter\bin

How to Add Flutter to PATH

1. Open Windows Search.
2. Search for Environment Variables.
3. Open Edit the system environment variables.
4. Click Environment Variables.
5. Select the appropriate Path variable.
6. Click Edit.
7. Add your Flutter bin path.
8. Save the changes.

Close any terminal windows that were already open, then open a new terminal.

Run:

flutter --version

If Flutter displays its version information, PATH is working.

Step 4: Run flutter doctor

Now run:

flutter doctor -v

This is one of the most important Flutter setup commands.

It checks major parts of the development environment and reports problems that need attention.

You may see sections related to:

• Flutter
• Windows version
• Android toolchain
• Chrome
• Visual Studio
• Android Studio
• Connected devices

Not Every flutter doctor Warning Matters

If your only goal is Android development, a warning for a platform you do not intend to build for may not block your work.

For example, Windows desktop development has its own Visual Studio requirements that are separate from Flutter Android development.

Focus first on the sections relevant to your target platform.

Step 5: Install the Android SDK

To build Android applications, Flutter needs the Android SDK and related tools.

The simplest route for many users is to install Android Studio and use its SDK Manager.

Even if you prefer writing code in VS Code, Android Studio can still be useful for managing:

• Android SDK platforms
• SDK build tools
• Platform tools
• Command-line tools
• Android emulators

Step 6: Install the Required Android SDK Components

Open the Android SDK Manager and make sure the required components are installed.

Typical components include:

• Android SDK Platform
• Android SDK Build-Tools
• Android SDK Platform-Tools
• Android SDK Command-line Tools

The exact Android platform version required can change over time.

Use a supported and current Android SDK rather than blindly following an old tutorial that tells you to install one specific outdated API level.

Step 7: Check the Java Environment

Android builds rely on Java-based tooling.

Java compatibility matters because Flutter, Gradle and Android Gradle Plugin versions need to work together.

Check which Java Flutter is using with:

flutter doctor -v

You can also inspect Java from the terminal with:

java -version

Do Not Randomly Install Several JDK Versions

Having multiple Java installations without knowing which one the build system is actually using can make Gradle troubleshooting harder.

If a build reports a Java compatibility problem, identify the active Java installation before changing anything.

Step 8: Accept Android SDK Licenses

If Flutter reports Android license issues, run:

flutter doctor --android-licenses

Review the license prompts and accept them as appropriate.

Then run:

flutter doctor -v

again.

Step 9: Install an Editor

You can develop Flutter apps with several editors.

Common choices include:

• Visual Studio Code
• Android Studio
• IntelliJ-based IDEs

Flutter's current quick-install documentation specifically supports a Code OSS-based editor such as VS Code for setting up and trying Flutter. citeturn109599search1

VS Code

Install the Flutter extension. The Dart extension is normally installed as part of the Flutter tooling dependency.

Android Studio

Install the Flutter plugin if you want to use Android Studio as your primary Flutter IDE.

Step 10: Create a Test Project

Before setting up a large project, verify the environment with a simple Flutter application.

Run:

flutter create test_app

Then:

cd test_app

Check the project:

flutter analyze

If the project is clean, the next step is to run it on Android.

Step 11: Connect an Android Phone

On your Android phone:

1. Enable Developer Options.
2. Enable USB debugging.
3. Connect the phone to the PC.
4. Approve the USB debugging authorization prompt.

Then run:

flutter devices

Your phone should appear as an available Android device.

If it does, run:

flutter run

Step 12: Or Use an Android Emulator

If you do not have a physical Android phone available, create an Android Virtual Device through Android Studio.

An emulator is useful for development, but real-device testing is still important before release.

How to Know the Setup Is Actually Working

A healthy Flutter Android setup should be able to do all of these:

1. Run flutter --version.
2. Run flutter doctor.
3. Create a new Flutter project.
4. Detect an Android device or emulator.
5. Run the default Flutter app.
6. Build an Android debug application successfully.

If those steps work, the basic environment is ready.

Common Problem: 'flutter' Is Not Recognized

If Windows displays an error such as:

'flutter' is not recognized as an internal or external command

the most common issue is PATH.

Check These Items

• The Flutter SDK exists where you expect it.
• The PATH entry points to the bin folder.
• You opened a new terminal after changing PATH.
• There is no spelling error in the path.

Common Problem: Android Toolchain Is Missing

If flutter doctor cannot find the Android toolchain, confirm that the Android SDK is actually installed.

Then verify that Flutter can locate it.

If necessary, you can explicitly configure an SDK path with Flutter's configuration tools, but first make sure the SDK installation itself is valid.

Common Problem: Android Command-Line Tools Are Missing

This is a common setup issue.

The Android SDK can exist while the required command-line tools are missing.

Open Android Studio's SDK Manager and check that Android SDK Command-line Tools are installed.

Then rerun:

flutter doctor -v

Common Problem: Android Licenses Not Accepted

Run:

flutter doctor --android-licenses

Then rerun:

flutter doctor

If the license command itself fails, check the Android command-line tools and Java environment first.

Common Problem: Phone Is Not Detected

If Flutter does not list your Android phone, test the problem layer by layer.

1. Check the USB cable.
2. Try another USB port.
3. Make sure USB debugging is enabled.
4. Unlock the phone.
5. Accept the debugging authorization prompt.
6. Run adb devices.
7. Then run flutter devices.

If ADB itself cannot detect the phone, the problem is below Flutter.

Fix the USB or Android platform-tools connection first.

Common Problem: Gradle Fails on the First Project

If the default Flutter project creates successfully but Android build fails, identify the first meaningful Gradle error.

Common causes include:

• Incorrect Java version
• Missing Android SDK platform
• Broken SDK installation
• Network failure while downloading dependencies
• Gradle compatibility issues

Do not randomly upgrade and downgrade Java, Gradle and Flutter at the same time.

Common Problem: Windows Filename Too Long

Flutter's current Windows troubleshooting guidance documents errors caused by paths exceeding Windows' default filename-length behavior.

One simple fix is to keep Flutter in a short location such as:

C:\Flutter

rather than deeply nested folders.

Flutter also documents enabling long-path support in Git and Windows if needed. citeturn109599search7

Do You Need Visual Studio?

This is a common source of confusion.

Visual Studio and Visual Studio Code are different products.

Visual Studio with the Desktop development with C++ workload is required when you want to build Flutter Windows desktop applications.

Flutter's Windows setup documentation specifically lists that workload for Windows desktop development. citeturn109599search0

If your target is only Android, a Visual Studio desktop-toolchain warning is not necessarily an Android blocker.

Do You Need Android Studio?

Not necessarily as your code editor.

You can write Flutter code in VS Code or another supported editor.

However, Android Studio remains a convenient way to manage Android SDK packages and emulators.

Should You Use the Stable Flutter Channel?

For most developers building production apps, the stable channel is usually the safest default.

Experimental or preview releases may contain features you want, but they can also introduce compatibility changes that are unnecessary for a normal project.

Check your current Flutter setup with:

flutter channel

How to Update Flutter Later

When you intentionally want to upgrade Flutter, use:

flutter upgrade

Before upgrading an important production project, use version control and make sure you can return to a known working version if a dependency or build-tool compatibility issue appears.

Flutter Windows 11 Setup Diagnostic Table

Problem	Likely Area	Check First
flutter command not found	PATH	Flutter bin path
Android toolchain missing	Android SDK	SDK installation
cmdline-tools missing	Android SDK	SDK Manager
Licenses incomplete	Android SDK	flutter doctor --android-licenses
Phone missing	ADB / USB	adb devices
Gradle error	Build toolchain	First meaningful error
Java error	JDK compatibility	flutter doctor -v
Filename too long	Windows path	Move Flutter to a shorter path

Final Setup Checklist

Before Starting Your Real Flutter App

• Git works from the terminal.
• Flutter is installed in a sensible path.
• Flutter bin is in PATH.
• flutter doctor runs successfully.
• The Android SDK is installed.
• Android command-line tools are installed.
• Android licenses are handled.
• Java is compatible with the Android build toolchain.
• A device or emulator appears in flutter devices.
• A clean Flutter app runs successfully on Android.

Final Thoughts

A good Flutter installation is not defined by whether flutter --version works.

The real test is whether you can create a clean project, detect an Android device and successfully run the application.

Treat the environment as several separate layers:

Flutter → Android SDK → Java → ADB/device → Gradle build.

When something breaks, identify which layer is failing instead of reinstalling everything.

That approach makes Flutter setup and future troubleshooting much easier.

Continue the Flutter Android Series

• Flutter Android App Development Guide: From First Project to Play Store
• How to Connect an Android Phone to Flutter
• How to Fix Flutter Gradle Build Errors
• How to Prepare a Flutter App for Google Play Store

Official Sources & Further Reading

• Flutter — Set Up and Test Drive Flutter
• Flutter — Custom Installation
• Flutter — Upgrade Flutter
• Flutter — Windows Development Setup