FVM
fvm.app
- Free plan
- Windows
- macOS
- Linux
- API
What FVM is
FVM is a free tool for managing Flutter SDK versions by project. A project’s `.fvmrc` file records its selected Flutter version, so teams can keep builds consistent while other projects use different versions. FVM switches between installed SDKs without downloading them again. It can identify unreferenced versions, preview cleanup candidates and remove unused SDKs with `fvm cleanup`. The tool supports macOS, Linux and Windows, with architecture support varying by system, and can be installed through a shell script, Homebrew, Chocolatey, Pub or standalone packages. Its documentation covers CI/CD automation and custom Flutter repositories. FVM detects VS Code and can update `.vscode/settings.json` for the Dart Code extension. Android Studio and IntelliJ settings must instead be configured to use the FVM SDK path. The tool also provides JSON API commands for SDK, release, cleanup, environment and project information. It stores known project-root paths in a machine-local file and says it does not scan disks for projects. The project uses the MIT License.
Who it suits
FVM suits Flutter developers and teams that need different SDK versions across projects or consistent versions within a team. Its automation commands may also suit CI/CD workflows.
Good to know, and what to watch
- Pins a Flutter SDK version per project in `.fvmrc`.
- Switches among installed SDKs without downloading them again.
- Cleanup can preview candidates before removing unused SDKs.
- Supports macOS, Linux and Windows.
- Android Studio and IntelliJ need separate SDK-path configuration.
- Supported architectures vary by operating system.
Plans
Every plan and priceFVM
Free plan
The verdict
FVM centralizes per-project Flutter version selection and can help teams keep builds aligned. Developers using Android Studio or IntelliJ should account for the separate IDE configuration.
What the maker publishes
- Automation
- The maker describes FVM as CI/CD friendly and provides commands for automation. source
- Cache management
- FVM can show unreferenced SDKs, preview cleanup candidates and remove unused versions with `fvm cleanup`. source
- Cache management
- FVM can show SDKs used by known projects and preview unused SDKs and patch upgrades before cleanup. source
- CI/CD
- The documentation describes FVM as CI/CD friendly with commands suitable for automation. source
- Custom forks
- FVM supports custom Flutter repositories through fork configuration. source
- Custom repositories
- FVM supports custom Flutter repositories. source
- Fast switching
- FVM changes SDK versions instantly without re-downloading them. source
- IDE limitation
- FVM does not change Android Studio or IntelliJ settings, which must be configured to use the FVM SDK path. source
- Install methods
- FVM can be installed with its shell script, Homebrew, Chocolatey, Pub or standalone GitHub packages. source
- JSON API
- FVM provides JSON API commands for listing installed SDKs, releases, cleanup data, environment context and project configuration. source
- JSON API
- FVM provides command-line JSON API commands for listing SDKs and releases, cleanup information, environment details, and project configuration. source
- License
- The project is licensed under the MIT License. source
- Local data handling
- FVM stores known project roots in a machine-local `projects.json` file, never scans disks and stores absolute paths. source
- Local project data
- FVM says it keeps known project-root paths in a machine-local file and does not scan disks for projects. source
- Maker
- The site footer credits Leo Farias; it does not state a headquarters or founding date. source
- MCP integration
- The Dart MCP server can be pointed at `.fvm/flutter_sdk` so AI assistants use the Flutter SDK pinned by FVM. source
- Other integrations
- The documentation covers Android Studio and IntelliJ configuration, Melos monorepos, and a Dart MCP server setup. source
- Per-project versions
- Each project can use a different Flutter SDK version through FVM configuration. source
- Project configuration
- The `.fvmrc` file stores a project's Flutter version and can include project-specific settings and flavors. source
- Purpose
- FVM manages Flutter SDK versions per project so teams can maintain consistent app builds and switch versions without reinstalling Flutter. source
- Purpose
- FVM manages multiple Flutter SDK versions and lets projects pin a version for consistent app builds. source
- Support and community
- The site points users to documentation and GitHub feedback, and describes the project as driven by open-source community contributors. source
- Supported platforms
- Standalone packages support macOS x64/arm64, Linux x64/arm64/riscv64 and Windows x64/arm64. source
- Supported systems
- The installation page lists support for macOS, Linux, and Windows, with architecture support varying by platform. source
Checked against the maker's pages on 2 Oct 2026.