# Flutter SDK archive
> All current Flutter SDK releases: stable, beta, and main.
:::note Developing in China
If you want to use Flutter in China,
check out [using Flutter in China][].
If you're not developing in China, ignore this notice
and follow the other instructions on this page.
如果你正在中国的网络环境下配置 Flutter，
请参考 [在中国网络环境下使用 Flutter][] 文档.
:::
[using Flutter in China]: /community/china
[在中国网络环境下使用 Flutter]: https://docs.flutter.cn/community/china/
## Overview
The Flutter SDK archive is a collection of all previous versions of the
Flutter SDK. This archive is useful for developers who need to use an older
version of Flutter for compatibility reasons or to investigate bugs.
The archive includes Flutter SDKs for Windows, macOS, and Linux on the
following [channels][]:
* **Stable channel**: This channel contains the most stable Flutter builds.
Roughly every third beta version is promoted to the stable version.
The stable channel is the recommended channel for
new users and for production app releases.
* **Beta channel**: This channel is the most recent version of Flutter that is
available, but it is not yet stable. The beta branch is usually released
on the first Wednesday of the month. A fix will typically end up in the
beta channel about two weeks after it lands in the main channel.
Releases are distributed as [installation bundles][].
* **Main channel**: This channel has the newest features, but it hasn't been fully
tested and might have some bugs. We don't recommend using it unless you're
contributing to Flutter itself.
The following information is available for each Flutter release in the
SDK archive:
* **Flutter version**: The version number of the Flutter SDK
(for example, 3.35.0, 2.10.5) follows a modified
[calendar versioning][] scheme called _CalVer_.
For more information, visit the [Flutter SDK versioning][] page.
* **Architecture**: The processor architecture the SDK is built for
(for example, x64, arm64). This specifies the type of processor the SDK is
compatible with.
* **Ref**: The git commit hash that uniquely identifies the specific codebase
used for that release.
* **Release Date**: The date when that particular Flutter version was
officially released.
* **Dart version**: The corresponding version of the Dart SDK included in the
Flutter SDK release.
* **Provenance**: Provides details about the build process and origin of the
SDK, potentially including information about security attestations or
build systems used. Results are returned as JSON.
[calendar versioning]: https://calver.org/
[Flutter SDK versioning]: https://github.com/flutter/flutter/blob/main/docs/releases/Release-versioning.md
## Install from an archive
After downloading a Flutter SDK archive from this page,
use the following steps to install:
1. Extract the downloaded archive to a desired location on your system.
2. Add the Flutter `bin` directory to your system's `PATH`. For more information,
see [Add Flutter to PATH](/install/add-to-path).
3. Run the following command to verify the installation:
```bash id="yfl9s6"
flutter doctor
```
The `flutter doctor` command checks your environment
and reports on the status of your installation.
For detailed platform-specific setup instructions,
refer to the main [Flutter installation guide](../install).
## Public release windows
Predictability is key to landing complex features safely.
We use public release windows to provide the community with
the visibility needed to plan ahead.
By explicitly calling out branch cutoff dates and release targets,
we enable everyone to align their development cycles and
coordinate feature landing effectively.
### What is a branch cutoff date?
This date is the deadline for pull requests to
land in the default branches (`main` for Dart and `master` for Flutter) to
guarantee inclusion in the next stable release.
* **Before cutoff:** Your PR will ship in the next stable version.
* **After cutoff:** Your PR will wait for the following cycle.
### 2026 schedule
| Flutter version | Release target | Branch cutoff date |
|-----------------|----------------|--------------------|
| Flutter 3.41 | February, 2026 | 2026-01-06 |
| Flutter 3.44 | May, 2026 | 2026-04-07 |
| Flutter 3.47 | August, 2026 | 2026-07-07 |
| Flutter 3.50 | November, 2026 | 2026-10-06 |
{:.table}
---
## Stable channel
## Beta channel
:::tip
To see what's changed in a beta release, compare the version tags on GitHub.
1. Find the version number (tag) you want to see (for example, `3.38.0-0.2.pre`).
2. Find the previous version number (for example, `3.38.0-0.1.pre`).
3. Go to the [GitHub compare page](https://github.com/flutter/flutter/compare).
4. Select the older tag for the `base` field and the newer tag for the `compare` field.
For example: [`flutter/flutter@3.38.0-0.1.pre...3.38.0-0.2.pre`](https://github.com/flutter/flutter/compare/3.38.0-0.1.pre...3.38.0-0.2.pre)
:::
## Main channel
[Installation bundles][] are not available for the `main` channel
(which was previously known as the `master` channel).
However, you can get the SDK directly from
[GitHub repo][] by cloning the `main` channel and then
triggering a download of the SDK dependencies:
```console
$ git clone -b main https://github.com/flutter/flutter.git
$ ./flutter/bin/flutter --version
```
## More information
To learn what's new in the major Flutter builds, check out the
[release notes][] page.
For details on how our installation bundles are structured,
see [Installation bundles][].
[channels]: https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-build-release-channels.md
[release notes]: /release/release-notes
[GitHub repo]: https://github.com/flutter/flutter
[Installation bundles]: https://github.com/flutter/flutter/blob/main/docs/infra/Flutter-Installation-Bundles.md