Skip to main content
Contributor II
May 1, 2026
Answered

Sonos app on Mac

  • May 1, 2026
  • 43 replies
  • 4903 views

I’m getting a message on my MacBook that the Sonos app will soon need to be upgraded because support for apps built for the Intel processors are being phased out. I have Sonos app version 17.2 and MacOS 26.4.1. Is a newer version of the Sonos app available?

Best answer by AjTrek1

Prior to the upcoming MacOS release previous versions of MacOS used “Rosetta”

Here’s an AI Overview”

  • "Rosetta" most commonly refers to Apple's translation software enabling Intel-based apps to run on Apple silicon (M1/M2/M3 chips). It works by automatically translating code during installation, allowing for immediate, responsive performance. It is crucial for compatibility but will be phased out in future macOS versions. 

Sonos has decided not to recode the MacOS app to work with Apple silicon. Sonos actually started stripping the desktop app of functionality (i.e. setup and others functions) from MacOS and Windows several years ago. Eventually, the desktop app will be phased out on Windows as well. The Web-Based app is the eventual replacement.

Well this answer is no longer needed now that Sonos has reversed course on making the Desktop App work natively with Apple Silicon. 😂😂😂

43 replies

controlav
Lead Maestro
August 27, 2026

Based on device firmware versions:

S1: v57.x will never get to v58 (as that is already used for S2)

S2 “legacy”: v86.x with room to get to v89.x if desired

S2 “not-legacy”: v96.x and likely to increment way past that

The v96+ capable devices are really S3, getting new features and the like, but compatible with S2 legacy devices (unlike the S1/S2 split).

Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
Contributor I
August 27, 2026

I remember I’m here in this thread earlier on. I was having trouble with having my bedroom legacy Sonos speaker play my Mixcloud uploads, as well as also my newer cellar/office Sonos speaker. Both of which needed separate Mac desktop controllers to operate, or at least to set up queues. I had to get with support who managed set me up okay—after quite a bit of effort. Today maybe things might go easier.

It was later that I discovered I was able to add all my 5000+ hourlong Mixcloud uploads randomized onto both queues separately and have them play at the touch of a button. Something I don’t know how I could do with any other system.

All I’m saying now is I’m quite happy with how my older and newer Sonos devices are working okay.

kdowling
August 27, 2026

Here’s how I see it… There are only 2 controllers. S1 and S2. There are only two systems, S1 & S2. The S2 system now has older devices that are considered S2 Legacy with it’s own firmware branch.. The S2 legacy devices still use the S2 controllers and are S2 systems.

Those S2 legacy devices are not OLD S2, they got updated in the big May 2024 UPDATE. They are running the current S2 API etc. So they are S2.

AjTrek1
August 27, 2026

Simply put… It makes sense to me no matter the confusing (to some) the language may be about so called Legacy S2 products. As I said TMU they are still S2 products but due to hardware limitations they may not receive some features that the newer Sonos App (or S2 products if you want to make a distinction) will receive.

Things will probably come to ahead in a future update when those so- called “legacy S2” products have a functional gap vs other products that were designated as S2.

Granted For right now my system is unique in that none of my products are older than a Sonos Amp or Port. So my biggest worry is when those products get left behind. But then again they’re not critical to my system. 😂😂

Together Everyone Achieves More = T.E.A.M.
kdowling
August 27, 2026

As far as term “legacy” is concerned to my understanding it only refers to devices that cannot operate on the S2 (Sonos App) controller/Firmware.

You can see where the confusion comes from, correct? That statement is not true. The legacy devices do operate with the S2 controller/firmware. That was, and is, my point.

Things will probably come to ahead in a future update when those so- called “legacy S2” products have a functional gap vs other products that were designated as S2.

I agree, that will inevitably happen. We’ll have to see how Sonos handles that when the time comes.

Stanley_4
Grand Maestro
August 27, 2026

Please, don't let them switch to Roman  Numerals for version numbers, about the only more confusing option. :-)

AjTrek1
August 27, 2026

Let me try to better illustrate my point.

Fictionally speaking both Product A and Product B are considered as S2 and also operate under the renamed Sonos App since 2024 (which is used interchangeably in conversation).

Product A has 300 MB memory 

Product B has 256 MB memory which is the terminal point for S2 products. 

The next feature update requires 275 MB memory 

Theoretically both Product A and Product B are S2. However, the latest feature update requiring 275 MB memory essentially relegates Product B to S2 legacy. It still operates under the current S2/Sonos App but doesn’t support the new feature that Product A is capable of.

Thankfully, at that fictitious crossroads it wasn’t necessary to split the system as was the case with products formerly being designated as S1 and S2/Sonos App.

That my friends is my understanding until Sonos can provide an alternative explanation.

Together Everyone Achieves More = T.E.A.M.
kdowling
August 27, 2026

However, the latest feature update requiring 275 MB memory essentially relegates Product B to S2 legacy. It still operates under the current S2/Sonos App but doesn’t support the new feature that Product A is capable of.

Exactly. It (Product B - S2 Legacy) still operates under the current S2/Sonos App. I knew you could get there. :)

 

AjTrek1
August 27, 2026

However, the latest feature update requiring 275 MB memory essentially relegates Product B to S2 legacy. It still operates under the current S2/Sonos App but doesn’t support the new feature that Product A is capable of.

Exactly. It (Product B - S2 Legacy) still operates under the current S2/Sonos App. I knew you could get there. :)

 

What do you mean? I was already there I just had to break it down from the Einstein level 😂

Together Everyone Achieves More = T.E.A.M.
Contributor I
August 28, 2026

I remember I’m here in this thread earlier on. I was having trouble with having my bedroom legacy Sonos speaker play my Mixcloud uploads, as well as also my newer cellar/office Sonos speaker. Both of which needed separate Mac desktop controllers to operate, or at least to set up queues. I had to get with support who managed set me up okay—after quite a bit of effort. Today maybe things might go easier.

It was later that I discovered I was able to add all my 5000+ hourlong Mixcloud uploads randomized onto both queues separately and have them play at the touch of a button. Something I don’t know how I could do with any other system.

All I’m saying now is I’m quite happy with how my older and newer Sonos devices are working okay.

To append: I’m still successfully using the S1 Controller for Mac desktop with my Play:5 (Gen 1). I did not realize there’s a S2 Legacy issue vs. newer models. My Play:1 is working well with the regular Sonos app—although I should say that with latter, maybe my latest Queue restoration needed to be accomplished with my iPad. In any event I’m good with how I can randomly play 5000+ hourlong music assortments at the touch of a button. It’s a dream come true, in actuality. Plus the sound is great.

I’m totally ignorant when it comes to the question of how much memory my devices have, or of how much is used playing my music, which is coming basically from the cloud (Mixcloud) on demand. If I were exporting the actual music files directly from my hard drives to Sonos—I know that wouldn’t work!