# Nextcloud-desktop parallel versions

**URL:** <https://help.nextcloud.com/t/nextcloud-desktop-parallel-versions/251948>\
**Category:** 💻 Desktop\
**Tags:** update\_problems\
**Created:** [November 12, 2026, 7:44am UTC](https://help.nextcloud.com/t/nextcloud-desktop-parallel-versions/251948 "2026-11-12T07:44:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![esprit-libre](https://help.nextcloud.com/user_avatar/help.nextcloud.com/esprit-libre/32/48680_2.png) [@esprit-libre](https://help.nextcloud.com/u/esprit-libre)\
**Post date:** [November 12, 2026, 7:44am UTC](https://help.nextcloud.com/t/nextcloud-desktop-parallel-versions/251948/1 "2026-11-12T07:44:14Z")

</div>

Since a while appeared a new versioning for desktop app, similar to server versioning.

This could makes sense to make desktop version following server version. For example, as long as I use a Nextcloud server version 34, users are advised to follow desktop version 34. But what if I connect to multiple servers with different versions?

Regarding [milestones](https://github.com/nextcloud/desktop/milestones) we can notice that multiple versions are updated regularly (v33, v34, v35 and now the new v36).

But [Download and install Nextcloud](https://nextcloud.com/install) does not propose to download any except latest. Furthermore, autoupdate of installed versions only propose latest. So why keep updating oldest versions? What is the goal behind that?

And more generally, is there an interest to follow oldest branch of desktop version? If so, how make desktop installations to follow a specific branch?

Thanks for any clarification!

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [November 16, 2026, 8:14am UTC](https://help.nextcloud.com/t/nextcloud-desktop-parallel-versions/251948/2 "2026-11-16T08:14:43Z")

</div>

In general, you should just use the latest desktop version available.

There is no hard dependency, in general the clients are compatible with all older versions of Nextcloud (they might cut support at some point, but that should be long before the server versions fall [out of support](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule)).

One day there might be the new Nextcloud server version 36 with a fancy new feature, this new feature then probably requires a Nextcloud desktop client 36 or newer. But even in this case, I’d expect the older clients still running and just ignoring the new feature.

Older version are not of great interest, there are some legacy versions for older macOS versions:

> <https://github.com/nextcloud/desktop/issues/7555>
>
> In this post, we provide the current status of the recent releases of the deskto…p client.
> 
> | Client Release | Covered By |
> |-|-|
> | 35.\\\*.\\\* | 🟢 Community support |
> | 34.0.5 | 🟢 Enterprise support |
> 
> Enterprise customers are put on the enterprise channel for client updates, unless changed by the admin.
> 
> \## Highlights in Version 35
> \- virtual files for Linux
> \- mass deployment support
> \- new unified sharing
> \- new unified search
> \- full Nextcloud Assistant integration
> 
> \## Highlights in Version 34
> 
> \- reduction of client size by more than 50% (due to removal of obsolete libraries)
> \- new native tray menus for quick status overview and notification reactions
> \- previous tray window was separated into own dedicated dialogs for activity, search, assistant, status
> \- migration dialog for moving from classic sync to file provider on macOS
> \- various performance and stability hardening
> 
> \## macOS Compatibility
> 
> | macOS Release | Latest Supported Client Release |
> |-|-|
> | 11 Big Sur | 3.13.4 |
> | 12 Monterey | 4.\\\*.\\\* |
> | 13 Ventura and later | 34.\\\*.\\\* \[^1\] |
> 
> \## Frequently Asked Questions
> 
> \### Why are older major versions still getting maintenance releases?
> 
> Like many mature software projects — think Firefox ESR, Windows 10 alongside Windows 11, macOS receiving security updates across multiple generations, or Microsoft Office suites being supported in parallel — we maintain more than one major release at a time. Active bug fixes and security patches are backported to older stable branches as long as they are supported. So seeing (in example) a 4.0.10 appear after 33.0.2 is completely expected. People on the older branch receive bug fixes and smaller improvements as well.
> 
> \### Why did the version jump from 4 to 33?
> 
> For clarity (to the most part). Starting with version 33, the desktop client’s major version number is aligned with the Nextcloud server release. From here on, the major version will just increment by one as usual. Major releases bring features while point releases bring fixes. It also is a step in the establishment of a more predictable and transparent release cycle while conveying currency.
> 
> \> \[!IMPORTANT\]
> \> There neither was nor is a dependency between these client and server releases! Older clients will work with newer servers, too, and vice versa.
> 
> \### Which version should I use?
> 
> Use whatever is offered by default on the \[Nextcloud download page\](https://nextcloud.com/install/#desktop-files) unless you need to work on older operating systems no longer supported by it or have an enterprise environment which still operates with a previous release.
> 
> \[^1\]: The file provider feature requires at least macOS 14 Sonoma. See #9927 for further details.

(but they should then also work with newer server versions).

---

<div class="post-metadata">

**Author:** ![esprit-libre](https://help.nextcloud.com/user_avatar/help.nextcloud.com/esprit-libre/32/48680_2.png) [@esprit-libre](https://help.nextcloud.com/u/esprit-libre)\
**Post date:** [November 16, 2026, 10:49am UTC](https://help.nextcloud.com/t/nextcloud-desktop-parallel-versions/251948/3 "2026-11-16T10:49:15Z")

</div>

Ok, I also see that difference between v34 and v35 is the support:

- v34 has Enterprise Support
- v35 has Community Support

Thanks for this link that also answers to my questions 👍

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [November 16, 2026, 1:54pm UTC](https://help.nextcloud.com/t/nextcloud-desktop-parallel-versions/251948/4 "2026-11-16T13:54:46Z")

</div>

What some do with new version, if there is the very first release of a new version, e.g. the 35.0.0, they still stay on the 34-branch and just switch to the 35 branch after the first point release. Or if this is due to a specific bug they wait for it to be fixed.  
And for 34 branch, there are still releases: [Releases · nextcloud/desktop · GitHub](https://github.com/nextcloud/desktop/releases)

(I suppose, if you wanted to stay on the 34-branch, you probably have to ignore the updates to the 35 versions, and then yourself check when new versions on the 34 branch appear). I’d do that just if I have a specific problem with a new version.

As a company, you have more support to know how it works in your environment, have your own deployment, branding, …
