With millions of Nextcloud users, there are a wide variety of needs and requirements for a private cloud server. Release Channels allow you to pick a versioning strategy that fits you.
You can choose a channel of your preference in the Administrator settings in your Nextcloud instance if you have installed Nextcloud from an archive. Learn more about the release channels below.
NOTE that you can only upgrade to a newer version. Skipping major versions when upgrading and downgrading to older versions is not supported by Nextcloud.
Nextcloud makes new versions incrementally available to user installations. When a major new version comes out, about 15% of the user base will receive an update notification in the first few hours. After some time and if no problems are found, the percentage is increased.
|Release channel||Use case||Get it here|
|This channel delivers the latest fully tested release of Nextcloud. That does not imply that these releases are bug free. The issues are known and can be worked around. The downside of this channel is that the releases are behind in terms of features and performance.||Older archives are available from our changelog page.|
|This channel delivers the latest feature releases ready for most users at minimal risk.|
Note that Nextcloud does staged rollouts, making releases incrementally available to the user base over time.
|You can get the latest stable version from our installation page.|
|Betas and release candidates are the versions of choice for testers in preparation for an Nextcloud release. They provide a short-term-stable point to report bugs against. Grab these to make sure the upcoming release works well on your infrastructure.||Automatically generated snapshot tarballs and betas track daily Nextcloud development. These are suitable to check if bugs are fixed but can break any time.|
|Daily builds are meant to reproduce bugs as well as to enable testers to follow the development of the next major version.|| Archive File (MD5)|
If you are looking to grab an archive of a specific version you can find links to them in our changelog.
Note that releases don't show up in the updater app right away. We usually stagger releases out to watch the impact and hold off in case very serious problems pop up. In practice, most bugfix releases are available within a week, major releases to a proportion of the users on release day in the Stable channel; we'll increase that percentage usually to 100% after the first bugfix release. We start the incremental rollout to the Production channel after the first bugfix release (for example, 12.0.1). Packages for the Release channels might be available in distributions, this is up to the packagers.
To upgrade in the safest way possible, always update to the latest minor release before upgrading to a new version. As an extreme example, to upgrade from 9 all the way to 12, upgrade 9.0.x to 9.0.6, then upgrade to 10.0.4, 11.0.3, then 12.0.1.