FVM

FVM is a Flutter SDK version manager for developers working across projects with different Flutter requirements. Its project-level pins and automation support make it a focused option for teams that want consistent SDK choices without a general environment-management layer.

Overview

Each project can use its own Flutter SDK version, recorded in `.fvmrc`. That lets developers move between projects without reinstalling Flutter and gives teammates a shared version reference. The file can also hold project-specific settings and flavors.

FVM is deliberately limited to Flutter SDK management, rather than managing a broad set of languages and tools. Its MIT license and open-source community model suit teams comfortable relying on community-driven software; documentation and GitHub feedback are the support routes.

Key features

Project pins and quick switching

FVM switches among installed SDK versions without downloading them again. This is useful when a developer maintains projects on different Flutter releases, while the `.fvmrc` pin can reduce version drift across a team. That consistency depends on developers and automation using the project’s FVM-managed SDK.

Cache cleanup and automation

FVM can show SDKs that no project references, preview cleanup candidates, and remove unused versions with fvm cleanup. This gives developers a way to reclaim space without guessing which cached SDKs are still needed. The project also describes its commands as suitable for CI/CD automation, making the same project configuration useful in build workflows.

IDE and developer-tool integration

FVM detects VS Code and updates `.vscode/settings.json` for the Dart Code extension to use the project’s managed SDK. Android Studio and IntelliJ need a separate SDK-path configuration, so teams using those IDEs should account for that setup rather than expect FVM to change their settings automatically. A Dart MCP server can also be pointed at `.fvm/flutter_sdk` so AI assistants use the pinned SDK.

Custom repositories and API

Custom Flutter repositories are supported through fork configuration. JSON API commands expose installed SDKs, releases, cleanup data, environment context, and project configuration, which can help when integrating FVM into scripts or tooling.

Pricing

FVM is free: the FVM plan costs nothing and covers open-source Flutter SDK version management on macOS, Linux, and Windows. There is no free trial because the free plan is the product’s offering. No seat or usage quota is part of the plan, so it fits individual developers and teams that need project-level version control without a paid tier.

Platforms

FVM supports macOS, Linux, and Windows, with standalone packages for macOS x64 and arm64, Linux x64, arm64, and riscv64, and Windows x64 and arm64. It can be installed through its shell script, Homebrew, Chocolatey, Pub, or standalone GitHub packages. Its platform support is useful across common development systems, though supported architectures vary.

For local project tracking, FVM stores known project-root paths in a machine-local `projects.json` file. It does not scan disks for projects, and those paths are absolute.

Who it's for

FVM is a strong fit for Flutter developers and teams juggling projects that require different SDK versions, especially when CI/CD should follow the same project pin. It is less compelling for developers seeking a general-purpose environment manager, or for teams unwilling to configure Android Studio or IntelliJ to use the FVM SDK path.

Pros and cons

• Project-specific Flutter versions: `.fvmrc` lets separate projects use different SDKs and gives teams a shared version reference.
• Quick switching without another download: moving among installed SDKs avoids repeating the download for each version change.
• Useful cleanup controls: previewing unused SDKs before removing them reduces the risk of deleting versions that projects still need.
• Automation and VS Code support: CI/CD commands and automatic VS Code configuration help carry the project pin into daily development and builds.
• IDE setup remains manual elsewhere: Android Studio and IntelliJ require users to configure the FVM SDK path themselves.
• Narrow scope: FVM manages Flutter versions, not a wider development environment.

Alternatives

For a broader category comparison, see Development Environment Managers.

• ActiveState Platform may suit teams looking beyond Flutter SDK version management; its free organization plan is limited to public projects, with a paid organization option using custom pricing.
• devenv is a free, MIT-licensed alternative for Linux, macOS, and WSL, but requires Nix; choose it when that broader Nix-based setup fits your environment.
• Flox offers a free Personal plan with its CLI, catalog access, unlimited public environments, and three private FloxHub environments; consider it when environment management beyond Flutter is the priority.
• frum is a free, MIT-licensed Ruby version manager for Linux, macOS, and Windows; choose it for Ruby rather than Flutter.
• Nix is a free, open-source package manager and is a better fit when package management, rather than Flutter SDK pinning, is the need.
• nvm is a free, open-source Node.js version manager; choose it for Node.js version control.
• PortBay has a free Community plan with project, sandbox-run, attachment, and Mac limits; consider it when those sandboxed-run features match the task.
• rustup is a free Rust toolchain installer and manager, so it is the relevant choice for Rust toolchains.

Verdict

Choose FVM if your work centers on Flutter and you want projects and CI/CD to share a pinned SDK version without repeated downloads. Its main trade-off is the narrow Flutter focus, plus manual SDK-path configuration in Android Studio and IntelliJ; developers who need broader environment management or automatic setup in those IDEs should look elsewhere.