macOS High Sierra 10.13.4 Displays Warnings When Opening 32-Bit Apps as Part of Apple's Phase Out Plan - MacRumorsOpen MenuShow RoundupsShow Forums menuVisit ForumsOpen Sidebar
Skip to Content

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

iphone 18 pro blue%402x

iPhone 18 Pro: Dark Cherry, Light Blue, and Dark Gray Chassis Leaked [Update]

Thursday June 4, 2026 5:18 am PDT by
Update: Since publication, new information has come to light suggesting the images have been AI-manipulated and are not in fact iPhone 18 Pro chassis parts. The original article follows. The color options Apple is reportedly planning for the upcoming iPhone 18 Pro and ‌iPhone 18 Pro‌ Max have appeared online today in the form of images of chassis parts of unknown authenticity....
Aston Martin CarPlay Ultra Screen

Apple Says CarPlay Ultra is Coming to These Vehicle Brands

Thursday May 21, 2026 11:53 am PDT by
Last year, Apple launched CarPlay Ultra, the long-awaited next-generation version of its CarPlay software system for vehicles. Nearly a year later, CarPlay Ultra is still limited to Aston Martin's latest luxury vehicles, but that should change fairly soon. In May 2025, Apple said many other vehicle brands planned to offer CarPlay Ultra, including Hyundai, Kia, and Genesis. CarPlay Ultra...
iOS 27 All the New App Features

iOS 27: All the Rumored App Features

Wednesday June 3, 2026 3:48 pm PDT by
Siri is getting a major overhaul in iOS 27, but Apple also has some big updates planned for apps like Camera, Photos, and Wallet. There are multiple new AI features in the works, plus some non-AI upgrades. Camera Apple is moving Visual Intelligence from the Camera Control button to the Camera app in iOS 27, according to Bloomberg. There will be a Siri mode that will be available alongside...

Top Rated Comments

casperes1996 Avatar
109 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
109 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
109 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)
Guy Clark Avatar
109 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)
keysofanxiety Avatar
109 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)
109 months ago
MacRumors content image

;-) 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)