Apple has begun notifying developers that universal macOS apps distributed through the Mac App Store can now drop support for Intel-based Macs as long as the apps require macOS 13 or later. The notification, sent to registered developers, marks a notable shift from the long-standing requirement that new and updated apps submitted to the Mac App Store include support for both Apple silicon and Intel processors. It adds another signal that Apple is moving its software ecosystem firmly to its own chip designs.
According to Apple’s message, developers with apps that have a deployment target of macOS 13 Ventura or later no longer need to ship an x86_64 binary slice for Intel Macs. Apple explained that removing Intel support will let developers simplify their development process and optimize download and on-device size. To make the change, developers need to update the app’s build settings to “arm64” only, then rebuild and submit the app to the Mac App Store.
The transition marks an important milestone. When Apple introduced its first Apple silicon Macs in 2020, it required developers to provide universal binaries with native code for both architectures. That made it easier for customers to move to the new platform without worrying whether their software would work. Today, a large share of Macs sold are powered by Apple silicon, and many apps are primarily developed for that platform. Allowing Intel support to be dropped for apps that require recent macOS versions follows the reality that the Intel Mac install base is shrinking.
What Apple told developers
Apple reportedly sent the email on Tuesday, September 1, 2026. The message said in part, “We’re reaching out to let you know that universal macOS apps on the Mac App Store that require macOS 13 or later can now remove support for Intel-based Mac computers.” It also noted that removing Intel support “can simplify your development and optimize your download and on-device size.” Apple then provided the straightforward technical instruction: “To remove Intel support, update your app build settings to ‘arm64’ only. Then rebuild and submit your app to the Mac App Store.”
Until now, developers who offered a universal binary or had previously submitted an Intel-compatible build were generally expected to maintain both architectures for the Mac App Store. While developers could design their projects in many ways, Apple’s requirement to support Intel made it difficult to take full advantage of Apple silicon-specific features or to reduce binary size by cutting out legacy code.
What matters to Mac App Store users
For users on Intel-based Macs, the change means they may stop receiving new features or updates for certain apps once developers choose to go arm64 only. Apple’s policy has long ensured that users can download the last compatible version of an app even if the developer has moved on. Intel users still running a version of macOS that is compatible with their machine will be able to access the previous build. However, they should not expect subsequent releases, unless a developer makes a special exception or offers an older version.
Developers who select an arm64-only build will still need to decide whether their app really can require macOS 13 or later. Some Intel Macs support macOS 13, including MacBook Pro and iMac models from 2017 and later, MacBook Air models from 2018 and later, and Mac mini, iMac Pro, and Mac Pro models introduced in 2018 and later. For those machines, a universal app with a macOS 13 target could still run until the developer stops building the x86_64 slice. The ability to remove the Intel slice means that those Intel users will be cut off from future updates, even if their Macs are capable of running the new version’s operating system. That may be acceptable to developers who believe the overhead of maintaining Intel code outweighs the benefit of reaching a small and shrinking set of customers.
Why Apple is making this change now
The move fits with Apple’s long-term plan to end support for Intel hardware. The company first announced its transition from Intel to Apple silicon in June 2020. It promised a two-year transition, but the shift has continued for several years since then because of the installed base of Intel Macs. As Apple has introduced new macOS versions, Intel Macs have gradually fallen off the supported list. macOS 27 Golden Gate, named after the Golden Gate Bridge, reportedly drops support for Intel Macs completely. After that, all Macs that run the newest operating system will have Apple silicon processors.
Apple also previously said that Rosetta 2, its translation layer that lets Apple silicon Macs run Intel-based apps, will be discontinued after macOS 27. Rosetta 2 has been important for many users because it allowed older software to work on Apple silicon Macs when developers had not yet shipped native versions. The company said there would be some exceptions for certain games, but for ordinary applications, Rosetta 2 will no longer be a guaranteed bridge into the future. This makes the Mac App Store announcement a natural companion: new apps intended for future macOS versions will be expected to generate native Apple silicon code, while Intel-era software becomes increasingly tied to older versions of macOS.
What developers should do
Developers who want to take advantage of today’s change should first confirm that their app’s minimum deployment target is macOS 13 or later. If it is, they can open Xcode, locate the architecture setting in their build settings, and set the active architecture to arm64. The process removes the x86_64 slice from the final build, which reduces the binary size. The Mac App Store submission process will accept the app as long as it is a proper arm64 build and meets all other App Store guidelines.
For developers using Xcode, the setting is often found under Build Settings, then Architectures. A project that previously used the standard architectures setting, including both arm64 and x86_64 for Mac, should be changed to include only arm64. Some developers may need to review their code for Intel-specific assumptions, such as inline assembly, endian handling, or use of third-party libraries that still ship with x86_64 object files. Apple silicon-only builds can also use modern frameworks and technologies that are not available on Intel. Since the app already requires macOS 13 or later, developers can assume a certain base level of system capabilities.
One important caveat is that the new policy applies only to apps distributed through the Mac App Store. Developers who distribute outside the store can use similar compiler settings, but they have always had more flexibility. Those developers need to think about the hardware requirements imposed by their own licensing, customer expectations, and support obligations. The Mac App Store change reduces friction for developers who prefer to distribute through Apple’s store while still serving Intel users with downloaded older versions.
Effects on the Mac ecosystem
Eliminating Intel support from Mac App Store apps will eventually make the app library reflect the reality of the hardware Apple sells. Apple silicon Macs have been on the market for several years, and they now account for the overwhelming majority of new Macs. With macOS 27 dropping Intel, new Mac software will increasingly be designed around the assumption that users have Apple silicon. That will unlock features that depend on the unified memory architecture, advanced GPU capabilities, and Neural Engine.
Independent developers are likely to appreciate the smaller binary size. Removing an x86_64 slice from a universal app can shave tens of megabytes from the download and installed size, depending on the app. Many apps contain native code, frameworks, and resources that are duplicated for each architecture. An arm64-only build can also speed up compile times, reduce complexity in continuous integration pipelines, and make it easier to adopt new system frameworks that are optimized for Apple silicon only. Larger apps that serve many functionalities, such as video editors, audio workstations, and graphics design tools, may benefit most from the reduced size.
In addition, developers no longer need to test on Intel hardware or account for performance differences between Intel and Apple silicon Macs. Apple silicon features like memory compression, fast input/output, and tighter integration with iOS apps are not part of the Intel experience. When an app does not need to run on Intel, the development team can spend less time working around architecture-specific issues and more time improving the product.
An evolving App Store strategy
Apple has used the Mac App Store as a way to guide developers toward architectural changes before. When the company transitioned from PowerPC to Intel in 2006, software companies had to rebuild their applications for x86, and Apple eventually phased out the Classic environment for PowerPC applications. A similar transition happened with the move from 32-bit to 64-bit apps on both macOS and iOS. Apple required developers to submit 64-bit builds long before 32-bit hardware disappeared. By making support policies clear in advance, Apple gave developers time to plan.
The same pattern appears to be happening now. Apple has been preparing developers for the end of Intel support for several years. Xcode has gradually made Apple silicon the default target for development, and many App Store submissions are already arm64 only. Apple’s decision to allow Mac App Store apps with a macOS 13 minimum to drop Intel support removes the last major red-tape requirement for developers who have been waiting to offer an arm64-only experience.
There may also be a policy component connected to the upcoming release schedule. If macOS 27 Golden Gate does not support any Intel Macs, an app that runs only on Apple silicon will still be able to run on any Mac that can install macOS 27. An app that requires macOS 13 or later could still run on certain Intel Macs, but only if the developer included the Intel slice. By making the Intel slice optional for apps targeting macOS 13 and later, Apple ensures that future macOS releases are not burdened by compatibility requirements that the hardware no longer receives.
The decision to continue allowing Intel users to download the last compatible version is an important consumer protection. App Store users frequently return to previously purchased apps after they are removed from sale or stop being updated. Apple’s policy means that a customer on an Intel Mac will not completely lose access to an app they purchased just because the developer later releases an arm64-only version. Instead, the version they download will be the latest one that still included Intel support. That policy helps developers minimize support costs while acknowledging that older hardware still has value to some customers.
Apple’s guidance also raises a practical question for developers who are not ready to cut off Intel users. If an app’s deployment target remains earlier than macOS 13, the Mac App Store will still accept a universal build that includes both architectures. Developers who want to maintain Intel compatibility should keep their Xcode project configured to build universal binaries. They can still take advantage of the standard distribution process and let the Mac App Store manage compatibility for each user. It is only when they decide to require macOS 13 or later and set the architecture to arm64 only that Intel support disappears for future updates.
For many product teams, the decision will come down to analytics. Developers can look at their crash reports, App Store sales data, and user demographics to see how many active customers are still on Intel. If the number is low, the cost of supporting a separate architecture may no longer be justified. If the number is high, perhaps because the app is used by organizations that have older Macs, continuing to ship universal binaries can protect that revenue stream. Apple’s change does not force a particular path; it simply removes the mandatory requirement for developers whose audience has already moved on.
Users should also understand that an Intel Mac will continue to run software that was installed before Apple’s policy change. Applications that have been fully updated to arm64-only versions are not necessarily removed from an Intel Mac if they were downloaded earlier; the Mac App Store will, however, prevent new downloads for incompatible versions on Intel hardware. Apple’s notice tells developers that Intel users can continue using the last version of the app compatible with their machine, which implies that the store remains aware of each user’s hardware and download history.
The wider implication is that the Mac App Store is slowly becoming an Apple silicon-only marketplace for new development. Third-party apps that are updated in the future will progressively abandon Intel, matching the direction of macOS itself. By the time macOS 27 arrives, most users opening the Mac App Store will have an Apple silicon Mac, and developers who want to reach them will be able to do so with leaner, faster builds.
Given the email’s wording, Apple is likely to update its public documentation and developer guidelines in the coming weeks. Developers should check the Mac App Store review guidelines, Xcode release notes, and Apple’s own developer news for official changes. The short version, though, is straightforward: if an app requires macOS 13 or later, it can now be built and submitted to the Mac App Store with only Apple silicon support. That is a clear next step in the industry’s long journey away from Intel, and it will shape the future of Mac software for years to come.
Source:9to5Mac News