Skip to Content

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

by

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

iphone fold text

iPhone Fold Crease Measurements Revealed as Device Hits Production

Wednesday February 25, 2026 5:37 am PST by
Apple has submitted production line orders for its upcoming foldable iPhone, effectively confirming that the device will launch this year, claims a Chinese leaker. According to the Weibo account "Fixed Focus Digital," assembly lines recently received the orders from Apple, which has apparently allowed the leaker to learn the crease measurements for the device's 7.8-inch inner display....
Read Full Article • 136 comments
Low Cost A18 Pro MacBook Feature Pink

Leaker Says Apple's Lower-Cost MacBook Will Have These 8 Limitations

Wednesday February 25, 2026 9:25 am PST by
Apple is expected to unveil its long-rumored lower-cost MacBook next week. Given it will be more affordable, this MacBook model will obviously have some reduced specs and compromises compared to the MacBook Air and MacBook Pro. While we are still waiting for Apple to announce the new MacBook, a leaker has shared eight alleged limitations to expect, based on an internal version of Apple's...
Read Full Article • 357 comments
m3 macbook pro blue

M5 Pro and M5 Max MacBook Pro: What to Expect

Wednesday February 25, 2026 3:02 pm PST by
Apple is working on a new MacBook Pro that could launch next week ahead of the "Special Experience" planned for March 4, so we thought we'd highlight all of the rumors about the device so far. Design There are no rumors of design changes, and we are expecting the upcoming M5 MacBook Pro models to look just like the M4 versions. Apple will continue to offer 14-inch and 16-inch size options,...
Read Full Article • 78 comments

Top Rated Comments

casperes1996 Avatar
casperes1996
106 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
zorinlynx
106 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
pgiguere1
106 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
keysofanxiety
106 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
Guy Clark
106 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)
A
arrowood
106 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)
Read All Comments