macOS High Sierra 10.13.4 Displays Warnings When Opening 32-Bit Apps as Part of Apple's Phase Out Plan

Starting with macOS High Sierra 10.13.4, Apple is commencing with its plan to begin phasing out 32-bit apps on Macs. Apple has promised that macOS High Sierra will be the "last macOS release to support 32-bit apps without compromises."

After installing macOS High Sierra 10.13.4, which is now available in a beta testing capacity, when you open up an app that's a 32-bit app, you'll get a warning about its future incompatibility with the macOS operating system.

macoshighsierra
This is the first of many warnings Apple plans to provide as it works to put an end to 32-bit Mac apps, and this initial warning will only be shown one time for each app.

Apple's efforts to phase out 32-bit apps on Macs mirror the path it took when ending 32-bit app support on iOS devices. In iOS 10, Apple provided increasingly more insistent warnings to let users know that their apps wouldn't work with future versions of iOS before phasing out 32-bit support entirely in iOS 11.

As of January 2018, all new apps submitted to the Mac App Store must be 64-bit, and all apps and app updates submitted must be 64-bit by June of 2018. The next version of macOS after High Sierra will include "aggressive" warnings about 32-bit apps before they are phased out entirely.

Once 32-bit apps are phased out on Macs, they won't be able to be used at all, so users will need to find replacements for older 32-bit apps that aren't likely to be updated to 64-bit.

Related Forum: macOS High Sierra

Popular Stories

iOS 18 CarPlay Feature

iOS 18 Adds These 5 New Features to CarPlay

Thursday June 13, 2024 7:44 am PDT by
Apple did not mention CarPlay during its WWDC keynote this week, but iOS 18 includes a handful of new features for the in-car software. Overall, there is not a whole lot new for CarPlay on iOS 18, with changes seemingly limited to the Messages and Settings apps so far. Below, we recap everything new for CarPlay on iOS 18. New for CarPlay on iOS 18 1. Contact Photos in Messages App...
ios 18 button bulge

iOS 18 Adds Pop-Out Bezel Animation When Pressing iPhone Buttons

Tuesday June 11, 2024 10:40 am PDT by
iOS 18 includes a small but interesting change for the buttons on the iPhone, adding more of a visual element when changing volume, activating the Action button, or locking the screen. When you press an iPhone button in iOS 18, the display bezel bulges outward slightly. This feature is available for the volume buttons, Action button and the power button, and it will also likely be used for...
maxresdefault

First Look at Messages via Satellite in iOS 18

Thursday June 13, 2024 11:29 am PDT by
Apple has been gradually expanding its suite of satellite connectivity features for iPhone, and iOS 18 brings a significant new one in the form of Messages via satellite. The feature allows users to send and receive iMessages and SMS texts, including emoji and Tapbacks, while out of range of cellular and Wi-Fi networks. CNET met up with Apple's senior director of platform product marketing,...
iOS 18 Wallet Feature

Here's What's New in Apple Wallet on iOS 18 for Event Tickets and More

Friday June 14, 2024 7:32 am PDT by
iOS 18 includes a handful of enhancements to the Wallet app on the iPhone, with new features for Apple Pay, Apple Cash, event tickets, and more. Below, we outline everything new for the Wallet app on iOS 18, based on information from Apple's press release and a WWDC 2024 coding session. Redesigned Event Tickets Event tickets have an all-new design in the Wallet app on iOS 18, complete...

Top Rated Comments

casperes1996 Avatar
84 months ago
The CPU has NO PROBLEM executing 32-bit code, and there isn't even a performance hit in doing so. There's no real solid reason to discontinue 32-bit support. This is going to keep people who requires certain older apps from upgrading to the latest version of MacOS, and expose them to security vulnerabilities for no good reason at all.
Running 32-bit code, means that you need to keep a 32-bit version of all the libraries and frameworks those apps may rely on. That's both storage, and more crucially RAM consuming. And there is in fact a performance hit to having 32-bit and 64-bit apps running on the same system, as opposed to if both were 64-bit. If they are both 64-bits they can share certain conditions giving the processor an ability to preemtptively execute that code more quickly.

32-bit support isn't free either. You need to test against your 32-bit libraries and if you update a 64-bit library for a security reason, you'll also need to update and test the corresponding 32-bit library. And it may behave differently.

Nvidia has stopped supporting 32-bit systems because the testing burden just got too big. A lot of Linux distros are killing 32-bit variants as well.

It's not worth the effort anymore.

Edited slightly to fix a typo and improve readability
Score: 47 Votes (Like | Disagree)
zorinlynx Avatar
84 months ago
I wonder why Apple has such a fetish for phasing out 32-bit code.

The CPU has NO PROBLEM executing 32-bit code, and there isn't even a performance hit in doing so. There's no real solid reason to discontinue 32-bit support. This is going to keep people who requires certain older apps from upgrading to the latest version of MacOS, and expose them to security vulnerabilities for no good reason at all.
Score: 39 Votes (Like | Disagree)
pgiguere1 Avatar
84 months ago
I wonder why Apple has such a fetish for phasing out 32-bit code.

The CPU has NO PROBLEM executing 32-bit code, and there isn't even a performance hit in doing so. There's no real solid reason to discontinue 32-bit support. This is going to keep people who requires certain older apps from upgrading to the latest version of MacOS, and expose them to security vulnerabilities for no good reason at all.
The performance hit comes from the OS having to keep both a 32-bit and 64-bit version of shared libraries in RAM.
Score: 14 Votes (Like | Disagree)
keysofanxiety Avatar
84 months ago
I wonder why Apple has such a fetish for phasing out 32-bit code.

The CPU has NO PROBLEM executing 32-bit code, and there isn't even a performance hit in doing so. There's no real solid reason to discontinue 32-bit support. This is going to keep people who requires certain older apps from upgrading to the latest version of MacOS, and expose them to security vulnerabilities for no good reason at all.
People said the same thing when they went from 16 bit to 32 bit. Honestly, they did. Stubbornness for change is just slowing down progress. Just look at the cluster that is Windows which still rocks Program Files x86 for legacy purposes.

Apple have always been happy to drop older standards. 32 bit is only the latest in a long list. They did this in iOS and they’ve already dropped 32 bit support/plug-ins years ago for their Pro Apps (LPX), so this shouldn’t come as much surprise.
Score: 9 Votes (Like | Disagree)
Guy Clark Avatar
84 months ago
Thankfully Apple has kept 32-bit support for longer on MacOS so fewer apps are affected, but I can still see users refusing to update to the next MacOS because their useful older software is going to break.
Just keep using Snow Leopard complete 32-bit support and Rosetta for PPC apps plus pre iOS infestation.
Score: 9 Votes (Like | Disagree)
arrowood Avatar
84 months ago


;-) Ok, ok, yeah. I get it. 32-bit overhead, memory, libraries, etc. But, but, I can't live without Adobe Fireworks ;-)
Score: 8 Votes (Like | Disagree)