Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-custom-post-order domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Release channels - Nextcloud
Deprecated: preg_split(): Passing null to parameter #2 ($subject) of type string is deprecated in /var/www/html/wp-includes/formatting.php on line 3479

Deprecated: preg_split(): Passing null to parameter #2 ($subject) of type string is deprecated in /var/www/html/wp-includes/formatting.php on line 3479

Tracking Nextcloud Releases

Choose your balance between stability and features

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. If you went via ‘beta’ to 14.0.0rc4 and stable is on 13.0.5, you have to wait until 14.0.0 or later is in stable until a new update will become available.

Where is my new stable release?
Nextcloud makes new versions incrementally available to user installations in the Stable channel. When a major new version comes out, we wait about one week and only when no problems are found we start the roll out in steps of about 20% of our user base per week. If you maintain several servers, this means some get it sooner than others. Sometimes, an issue is found that was not caught during our pre-release testing, so we delay the roll-out until the fix is available. As a result new release is typically only available in the stable channel after the first minor release. Sometimes it can take even a bit longer. Users can always upgrade sooner by choosing the beta channel, which typically tracks stable releases immediately after publishing.

After upgrading to the new major release from the Beta channel, you can switch back to stable where you will be notified of minor releases as usual.

If you are looking for our release- and maintenance schedule, you can find that in Github.

Note that, of course, we do not release unstable software. We spend a third of our development cycle on testing and only release Nextcloud if we and our paid and volunteer testers are unable to find any more issues. Unfortunately, Nextcloud is big and complicated software and with hundreds of apps users can install, Nextcloud can be used in thousands of different ways, on different platforms and with different configurations. We encourage users to join our testing efforts, trying out beta releases and release candidates so we can fix issues before release. Only testing YOUR use case can guarantee it will be perfect for you!

  Release channel   Use case   Get it here
Production This channel is used to deliver the Nextcloud Enterprise build to our customers.
Our customers have access to a special build of Nextcloud, giving them the reliable enterprise solution they need for the best possible experience.		 Learn more about our offering for customers.
Stable 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. We are very careful about new major releases, usually only making them available after the first minor bug fix release. To update sooner to the new version, use the Beta channel. Around big releases the Beta channel delivers the new major version.		 You can get the latest stable version from our installation page.
Install
Beta 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 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 will increase that percentage usually to 100% after the first bugfix release.Packages for the Release channels might be available in distributions, docker images, Snap and so on, this is up to the packagers and communities developing for those platforms.

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.0.5, upgrade 9.0.x to 9.0.6, then upgrade to 10.0.6, 11.0.7, then 12.0.5. We try to set up our updater to do this automatically for you whenever possible.

This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner.