Apple Drops 40-Year-Old AFP Protocol in macOS 27, Urges Migration to SMB3
- 60% of MD5 Password Hashes Can Be Cracked in Under an Hour with a Single GPU
- Dirty Frag: Root Access on Every Major Linux Distribution — No Patch, No Warning
- Ubuntu 26.04 LTS (Resolute Raccoon): The Most Ambitious Ubuntu LTS in a Decade
- Proton Mail: Data Transferred to FBI Again!
- How Close Are Quantum Computers to Breaking RSA-2048?
- How to Prevent Ransomware Infection Risks?
- What is the best alternative to Microsoft Office?
Breaking News — June 12, 2026
Apple Drops 40-Year-Old AFP Protocol in macOS 27, Urges Migration to SMB3
Published June 12, 2026 | macOS · Networking · File Sharing
Apple’s long-standing Apple Filing Protocol is finally gone. With macOS 27, AFP client support has been officially removed — closing the chapter on a proprietary networking standard that Apple first introduced alongside AppleTalk in 1985.
After decades of quiet coexistence with modern protocols, the Apple Filing Protocol (AFP) has reached its end of the line. Apple confirmed in macOS 27 that AFP client support has been fully removed, rendering legacy hardware such as Apple Time Capsules — which rely on AFP and the outdated SMB1 — effectively incompatible with the latest macOS unless users retain an older system version.
The move was not entirely unexpected. Apple had telegraphed the end of AFP through successive deprecation warnings. Most explicitly, macOS Sequoia 15.5 (released in May 2025) updated the mount_afp man page with a clear notice that the AFP client was deprecated and would be removed in a future macOS release. Users were urged to explore alternatives and migrate their workflows before that version arrived. That version turned out to be macOS 27.
The Origin and Development History of AFP
AFP’s story begins in 1985, when Apple released its AppleTalk networking suite — a proprietary protocol stack designed to give every Macintosh automatic, zero-configuration networking on local area networks. AFP was the file-sharing layer of that stack, enabling Macs to discover and access each other’s files without any manual IP configuration. It was a genuinely forward-thinking idea for its time, predating the widespread adoption of TCP/IP by nearly a decade.
Apple developed AFP in part to handle Mac-specific features that generic protocols of the era simply could not support — most notably resource forks, the dual-stream file structure that classic Mac OS used to store application data and metadata side by side. Early AFP implementations were bundled into System 6 in 1988 and later into AppleShare and AppleShare IP server products throughout the early 1990s, making AFP the backbone of Mac networking in schools and small offices across the world.
Why AFP Could Not Survive the Modern Era
Apple’s decision to cut AFP is easy to understand in hindsight. The protocol was designed for small, homogeneous networks of Macintosh computers communicating over AppleTalk — a world that has long ceased to exist. In a TCP/IP landscape populated by a mix of Windows, Linux, and Mac machines, AFP’s proprietary nature became a liability rather than an advantage.
Security has been an increasingly glaring problem. AFP’s authentication mechanisms have not kept pace with modern standards, and Apple’s silence on the protocol — no meaningful updates since AFP 3.4 in 2012 — made clear that it had no intention of investing engineering resources to bring it up to date. Carrying the maintenance burden of a protocol that serves a shrinking minority of use cases, while it accumulates unaddressed security obligations, is exactly the kind of technical debt Apple has a consistent history of cutting loose.
Switching to SMB3: What Users Need to Know
Apple’s recommended replacement is SMB3 — the current version of the Server Message Block protocol, originally developed by Microsoft and now maintained as an open industry standard. SMB3 has become the de facto universal file-sharing protocol, with robust support across Windows, Linux, and macOS, as well as virtually every modern NAS device on the market.
For Time Machine users, the migration path is straightforward. Most modern NAS devices from manufacturers such as Synology and QNAP support SMB3 natively. Pointing Time Machine at an SMB3-capable NAS share requires no AFP configuration whatsoever, and users gain better encryption, improved performance, and ongoing security support in the bargain.
Those who cannot immediately replace AFP-dependent hardware — most commonly users still running original Time Capsule units — are advised to either defer their upgrade to macOS 27, or explore the TimeCapsuleSMB community project as a transitional solution while they plan a longer-term replacement.
