'How to use two version of flutter on same device for different projects?
I have a stable flutter channel SDK located at c:\flutter. which is set at the system environment variables to be the default path for Flutter.
And I'm using this path c:\flutter when creating new Flutter project in IntelliJ for our customers.
I also downloaded Flutter master channel at c:\flutter_master and I need to use this flutter SDK (master) for another project.
How I can correctly have two working flutter version on the same device for different projects without playing with the system environment variables each time?
Solution 1:[1]
Firstly you need to download all the flutter SDKs you would want to be able to switch locally and create aliases for it. This allows you to use multiple versions of the SDK through the command line or the terminal, Just like you use any flutter command, And Incase you want to use these different versions of your SDK in your IDE, you need to add the SDK paths to the settings of your IDE. Below you can find the steps to add the path to vscode. The below answer will help you setup the different versions of SDK regardless of whether you are on Windows, Linux, or mac.
Creating alias on Mac/Linux
This is how I have done it on an M1 mac,
I have different versions of flutter SDKs downloaded in a Documents folder located at $HOME/Documents
In order to access the appropriate version of flutter through the terminal, we need to create aliases. Think of aliases as a shortcut to accessing the SDK via the command line.
- To create an alias you need to create
.bash_aliasesfile inside your $HOME directory
you can do this via terminal by running
nano ~/.bash_aliases
Paste these aliases with the appropriate path in the file.
alias flutterd='~/Documents/flutter_dev/bin/flutter'
alias flutterm='~/Documents/flutter_master/bin/flutter'
alias flutterb='~/Documents/flutter_beta/bin/flutter'
Note that you can name the aliases as you like.
I have used the name
flutterdto point to flutter_devfluttermto point to flutter_masterflutterbto point to flutter_beta
that means when you type flutterd in the terminal then it will use the SDK located at ~/Documents/flutter_dev/bin/flutter and respectively for rest of the aliases.
(Hit ctrl + x and enter to save and exit)
- And lastly, you need to add this in your shell file
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
which is basically the rc file
$HOME/.bashrc if you are using bash
$HOME/.zshrc file if you are using zsh
if you are not sure then typing
echo $SHELLin your Terminal tells you which shell you’re using. This is the same file where you have added your flutter sdk's path when you first installed it. And if the file doesn't exist you may create it.
- Run
source $HOME/.<rc file>to refresh the current terminal window.
Now you can verify by typing your alias names in the terminal flutterm, flutterd etc and it will respond from the respective sdk.
you can verify this by running <alias name> doctor -v
e.g to verify flutterd is pointing to dev run flutterd doctor -v
Here is my output when I run the command
Creating alias on Windows
On windows, I have the flutter SDKs stored in C:/flutter_sdk
and then create an Alias folder and create batch files corresponding to each flutter SDK, where each batch file contains the path to flutter SDK
e.g flutterd.bat contains the path to dev sdk
@echo off
C:\flutter_sdk\dev\bin\flutter %*
Name your batch files wisely, because you will be using them from the command line. e.g I have a batch file named as
flutterb.batto point to the beta channel, so to access the beta SDK I will useflutterbin the command line and notflutter.
and finally, we need to add the alias folder to the environment variable in order to make it accessible throughout windows.
Go to environment variables => user variables => Path => edit=> new
Now you can verify if everything works fine by opening command prompt and enter flutterb doctor and it should show the SDK pointing to beta
Adding multiple SDK versions to VScode
Now to access the appropriate version of the SDK in vscode you need to add these SDK paths in settings.
- In your User settings (CMD+SHIFT+P) search for
sdk path - Under Flutter SDK paths add all the paths
Now when you open a flutter project you can choose your desired version by clicking on the flutter version at the bottom

And it will prompt you to choose the sdk to use
Note that if you are changing versions from vscode, you should also run flutter pub get from the right top icon in pubspec.yaml, so that the source code updates as per the choosen sdk. You may confirm this by looking at the class definition of the source code.
Solution 2:[2]
Flutter SDK can be specified per workspace if you use VSCode. You need to:
- Clone flutter repo to a new folder:
mkdir ~/flutter_dev
cd ~/flutter_dev
git clone https://github.com/flutter/flutter.git .
- Create
.vscode/settings.jsonwith the following content:
{
"dart.flutterSdkPath": "/Users/youruser/flutter_dev"
}
- Restart VSCode and you're good to go.
See more info in Dart Code - Quickly Switching Between SDK Versions
Solution 3:[3]
According to this issue on Flutter's repo iqbalmineraltown has the answer:
You might want to download multiple version as you need, because each Flutter SDK version is tightly coupled with specific Dart SDK.
You set the Flutter version for each project, and iqbalmineraltown highlights a way if you're using VS Code:
If you're using VSCode, you can download multiple version of flutter SDK into different path and quickly switch between them using Dart&Flutter Plugin You can set default SDK for each project by providing default SDK path for each workspace. So when you open a project, VSCode will use the version you specified for that project.
Solution 4:[4]
If you are using Android Studio, you can set difference version of Flutter for each project from menu File => Setting => Languages & Frameworks => Flutter:

And to run the flutter/dart from the command line for multiple flutter version, you can follow this article https://medium.com/@sarbagyastha/using-two-or-more-different-versions-of-flutter-in-single-machine-484293c2a7ff
Solution 5:[5]
Now you can use “FVM”, and it's Flutter Version Management, A simple CLI to manage Flutter SDK versions per project.
1 you can use it by this command
pub global activate fvm
2 after that you can install any versions you want like
fvm install stable
fvm install 'flutter version'
it will be installed at
/Users/'username'/fvm/versions/
3 to switch versions:
fvm use 'flutter version'
for more info, visit FVM.app
Solution 6:[6]
You can simply rename the folder without playing with the system environment variables each time.
Solution 7:[7]
I recommend using this tutorial over here, I made some changes for Mac:
For UNIX/Mac based OS users
Edit $HOME/.bashrc (for me it was $HOME/.bash_profile on Mac) file and add this line (if it doesn’t exist).
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
- Create and edit
$HOME/.bash_aliasesand add aliases as you want.
alias flutter2='~/development/sdks/flutter2/bin/flutter'
alias flutter='~/development/sdks/flutter/bin/flutter'
Using same technique I've kept flutter2 setup seprate from flutter1. Because in some projects I need two and in older projects the version 1.
Now open specific project in VSCode and open command palette (on Mac command was Command + Shift + P) and search for flutter sdk.

Now choose Auto-Detect, which will create a new file under root of your project .vscode/settings.json.

Open this file and place the path of flutter version you want to use like below:
{
"dart.flutterSdkPath": "/Users/imran/flutter2"
}
Do remember to run flutter2 --doctor, to resolve any issues
While setting up flutter2 I encountered an issue and fix for that is here I am getting error "cmdline-tools component is missing" after installing Flutter and Android Studio... I added the Android SDK. How can I solve them?.
Solution 8:[8]
You can use FVM to manage versions of flutter https://fvm.app
Solution 9:[9]
Having several versions of SDKs installed and adjusting project specific IDE SDK settings seem reasonable, but I prefer commandline tools and when you call flutter command, it always calls the one on the path. So I can't use this solution.
Alias solution mentioned in this post is preferable for me, but when used it, I often forgot to call with alias (such as flutterb), leading to calling wrong version of flutter. After accidentally doing this, I usually need to do a flutter clean as well.
What I use, inspired by alias solution, is that I added a flutter.bat file in the root folder of the project. It contains the following lines
@echo off
C:\SDK\flutter1\bin\flutter %*
As you may guess, this location belongs to the specific flutter installation for using with this project. It is not the version on the path, but since I call all flutter commands from the root folder of the project, my terminal session sees this flutter first and it uses this version, rather than the global one on the path. You can confirm this by calling flutter doctor for the first time.
- Note that this is for using constant versions for each project, rather than trying several versions on the same project. For that kind of use case, you can combine this with the alias solution.
- Also note that this is a Windows solution.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | |
| Solution 2 | |
| Solution 3 | flarkmarup |
| Solution 4 | I Made Mudita |
| Solution 5 | Mohamed Reda |
| Solution 6 | manoj reddy |
| Solution 7 | Jaumzera |
| Solution 8 | brianha289 |
| Solution 9 |









