Intel, Universal 1 or 2 apps

If I read things correctly with the introduction of MacOS 27 it will be the end of Intel apps. (Some sites say MacOS 28).

My understanding is that if the app is designated “Universal” it will work in MacOS 27 and beyond.

Again my understanding is that “Universal 1” was for PowerPC & Intel and “Universal 2” is for Intel & ARM.

As my M1 is running Rosetta 2 ( I presume) the “Universal” and Intel designated apps are working.

When Rosetta 2 is dropped in MacOS 27 will these ‘Universal” apps still work if they are designated just “Universal” or will they need to show “Universal 2” or ????

iMac 24″, macOS 15.5

Posted on May 2, 2026 2:48 AM

Top-ranking reply

MrHoffman

Level 10

161,545 points

Posted on May 30, 2026 7:51 AM

Globet wrote:

So I'm a bit confused on the Intel/silicon issue. I see recommendations that installing Rosetta 2 will enable the use of Intel-based apps, but elsewhere I see that Rosetta support is to be dropped when a future version of MacOS is launched.

Universal 1 and Rosetta 1 is roughly twenty years back, and no longer relevant.

Universal 2 is current, shows as Universal, and is relevant for old app versions and for effectively if not actually unmaintained apps.

Support for Intel x86-64 apps is going away in macOS 27, except for a few specifically unmaintained games.

So far I'm not seeing much evidence of even majors (Amazon, for example in their desktop Music app, Intel only, offering a silicon-compatible version? Can anyone clarify? I already have several notifications popping up reporting that some of my apps will need to be updated...

Which apps, and do those apps have newer versions?

If Amazon’s desktop music app is not updated for instance, don’t update to macOS 27 when that arrives, and then check with Amazon for updates or alternatives for macOS 27.

Some of the printer vendors haven’t updated their apps in some years, and some of those apps might even be unnecessary for AirPrint / TWAIN / ICA printers and scanners.

These macOS 26.5 app notifications are presumably all trying to warn people about their old apps before the macOS 27 betas arrive, and break the old things.

Also probably to encourage the vendors to update their apps for Apple silicon Macs, that having first been released back in 2020.

Or to not rush a macOS update when some critical app hasn’t been updated or replaced.

View in context

41 replies

Owl-53

Level 10

113,749 points

May 31, 2026 12:57 PM in response to MrHoffman

MrHoffman wrote:

Owl-53 wrote:

Need_help_give_help wrote:

Hi Globet et al

I return to my original post and subsequent discussion above.

PPC and x86-32 apps do not run on macOS 26. That support was removed long ago; last with 10.6 and with 10.14, respectively.

Yes, we are only too aware of all this, unless this aspect, is truly intended towards the Author of the question ?

Jun 2, 2026 1:01 AM in response to Owl-53

Owl-53 referring to your post 0923 31/5/26

I note your advice: “Proceed with an abundance of caution using an unknown Terminal Commands” I most certainly will heed it. I won’t be using the Lipo command which requires a download of Xcode especially as Mr Hoffman has hopefully given an alternative.

Jun 2, 2026 1:25 AM in response to MrHoffman

Mr Hoffman

Thanks for your advice re FILE command. I have had a bit of an experiment but it is not giving the answers I expect. I will continue to work on it to ensure that I am doing it correctly and hopefully I’ll be able tease out UNIVERSAL to Universal 1 or Universal 2 applications.

Globet

Level 1

36 points

Jun 2, 2026 1:32 AM in response to MrHoffman

Shouldn't Apple take some sort of a lead on this? Comms are confusing (for example - go to the Apple store for updated apps for silicon" seems only to apply to current Apple's own apps). Apple must be aware of (or can check) which apps sold on the store are of Kind Intel, Universal 1, or Universal 2. Maybe a flag on the store to indicate an app as "silicon compatible"? Vast majority of users don't become aware of this type of issue until it bites them...

Owl-53

Level 10

113,749 points

Jun 2, 2026 2:13 AM in response to Need_help_give_help

Need_help_give_help wrote:

Owl-53 referring to your post 0923 31/5/26

I note your advice: “Proceed with an abundance of caution using an unknown Terminal Commands” I most certainly will heed it. I won’t be using the Lipo command which requires a download of Xcode especially as Mr Hoffman has hopefully given an alternative.

When Mr.Hoffman said, “The file command will tell you that too, and with no Xcode installed,” he wasn't saying that Xcode should not be installed. He was simply pointing out an alternative method that, in theory, would provide the same information without requiring Xcode.

The problem is that the user ( you ) had already tried that route and reported “Thanks for your advice re file command. I have had a bit of an experiment but it is not giving the answers I expect.”

So we're no longer discussing a hypothetical alternative—we're discussing one that has already been tested and has not produced a satisfactory answer.

Given that, suggesting Xcode as the next step is not contradicting Mr. Hoffman's advice. It's a recognition that the proposed alternative has not resolved the issue.

If the objective is to obtain a more definitive answer rather than continue experimenting with a method that isn't yielding clear results, then installing Xcode becomes a reasonable and arguably more practical option.

At some point the discussion has to move beyond "you could try this instead" and focus on "what is most likely to answer the question." Based on the information provided so far, the Xcode route appears to be the more reliable way to do that.

Jun 2, 2026 4:29 AM in response to Globet

Globet

Yes wouldn’t it be nice if Apple would help so we can identify applications we have so know in advance whether they will work or not.

You will be told by others that this forum is not Apple but a bunch of users helping each other, I’m sure that’s true. I am 99% sure though that Apple does read these posts and does participate.

That said I have passed on feedback to Apple at Product Feedback - Apple but haven’t received any acknowledgement. I invite you to have a try.

Jun 2, 2026 4:33 AM in response to Owl-53

Owl-53

You have misunderstood what I said as I obviously wasn’t clear enough.

Although, as I said, I have experimented with Mr Hoffman suggestion of using the “File” command I am also

not confident yet that I am doing it right. It is true Mr Hoffman might not have been saying ‘don’t install Xcode’ but I’m not putting words in his mouth.

As to your method it might work perfectly but at this stage I am not going to try it out for the very reason you give: “Proceed with an abundance of caution using an unknown Terminal Commands”