| APFS | |
| Full Name: | Apple File System |
| Developer: | Apple Inc. |
| Introduction Os: | iOS 10.3, macOS 10.13 |
| Introduction Date: | March 27, 2017 (iOS), September 25, 2017 (macOS), |
| Preceded By: | HFS Plus |
| Partition Id: | 7C3457EF-0000-11AA-AA11-00306543ECAC (GPT) |
| Directory Struct: | B-tree[1] |
| Max Files No: | 9,223,372,036,854,775,808 |
| Max File Size: | 8 EB (9,223,372,036,854,775,808 bytes)[2] |
| Date Range: | – |
| Date Resolution: | 1 ns |
| Filename Character Set: | Unicode 9.0 encoded in UTF-8 |
| Dates Recorded: | access, attributes modified, contents modified, created |
| File System Permissions: | Unix permissions, NFSv4 ACLs |
| Compression: | Partial (decmpfs)[3] |
| Encryption: | Yes |
| Copy On Write: | Yes |
| Os: | macOS, iPadOS, iOS, tvOS, watchOS |
Apple File System (APFS) is a proprietary file system developed and deployed by Apple Inc. for macOS Sierra (10.12.4)[4] and later, iOS 10.3, tvOS 10.2,[5] watchOS 3.2, and all versions of iPadOS.[6] [7] It aims to fix core problems of HFS+ (also called Mac OS Extended), APFS's predecessor on these operating systems. APFS is optimized for solid-state drive storage and supports encryption, snapshots, and increased data integrity, among other capabilities.
Apple File System was announced at Apple's developers’ conference (WWDC) in June 2016 as a replacement for HFS+, which had been in use since 1998.[8] [9] APFS was released for 64-bit iOS devices on March 27, 2017, with the release of iOS 10.3, and for macOS devices on September 25, 2017, with the release of macOS 10.13.[10] [11]
Apple released a partial specification for APFS in September 2018 which supported read-only access to Apple File Systems on unencrypted, non-Fusion storage devices. The specification for software encryption was documented later.[12]
The file system can be used on devices with relatively small or large amounts of storage. It uses 64-bit inode numbers,[2] and allows for more secure storage by using a technology called Data Protection. The APFS code, like the HFS+ code, uses the TRIM command for better space management and performance. It may increase read-write speeds on iOS and macOS,[11] as well as space on iOS devices, due to the way APFS calculates available data.[13]
APFS uses the GPT partition scheme. Within the GPT scheme are one or more APFS containers (partition type GUID is). Within each container there are one or more APFS volumes, all of which share the allocated space of the container, and each volume may have APFS volume roles. macOS Catalina (macOS 10.15) introduced the APFS volume group, which are groups of volumes that Finder displays as one volume. APFS firmlinks lie between hard links and soft links and link between volumes.
In macOS Catalina the volume role (usually named "Macintosh HD") became read-only, and in macOS Big Sur (macOS 11) it became a signed system volume (SSV) and only volume snapshots are mounted. The volume role (usually named "Macintosh HD - Data") is used as an overlay or shadow of the volume, and both the and volumes are part of the same volume group and shown as one in Finder.
Clones allow the operating system to make efficient file copies on the same volume without occupying additional storage space. Changes to a cloned file are saved as delta extents, reducing storage space required for document revisions and copies.[7] There is, however, no interface to mark two copies of the same file as clones of the other, or for other types of data deduplication.
APFS volumes support snapshots for creating a point-in-time, read-only instance of the file system.[7]
Apple File System natively supports full disk encryption,[2] and file encryption with the following options:
APFS supports 64-bit inode numbers, supporting over 9 quintillion files (263) on a single volume.[2] [14]
Apple File System uses checksums to ensure data integrity for metadata but not for user data.[15]
Apple File System is designed to avoid metadata corruption caused by system crashes. Instead of overwriting existing metadata records in place, it writes entirely new records, points to the new ones and then releases the old ones, an approach known as redirect-on-write. This avoids corrupted records containing partial old and partial new data caused by a crash that occurs during an update. It also avoids having to write the change twice, as happens with an HFS+ journaled file system, where changes are written first to the journal and then to the catalog file.
APFS supports transparent compression on individual files using Deflate (Zlib), LZVN (libFastCompression), and LZFSE. All three are Lempel-Ziv-type algorithms. This feature is inherited from HFS+, and is implemented with the same AppleFSCompression / decmpfs system using resource forks or extended attributes. As with HFS+, the transparency is broken for tools that do not use decmpfs-wrapped routines.[16]
APFS adds the ability to have multiple logical drives (referred to as volumes) in the same container where free space is available to all volumes in that container (block device).[17]
While APFS includes numerous improvements relative to its predecessor, HFS+, a number of limitations have been noted.
APFS does not provide checksums for user data.[18] It also does not take advantage of byte-addressable non-volatile random-access memory.[19] [20]
Enumerating files, and any inode metadata in general, is much slower on APFS when it is located on a hard disk drive. This is because instead of storing metadata at a fixed location like HFS+ does, APFS stores them alongside the actual file data. This fragmentation of metadata means more seeks are performed when listing files, acceptable for SSDs but not HDDs.[21]
Unlike HFS+, APFS does not support hard links to directories.[22] [23] Since the version of the Time Machine backup software included in Mac OS X 10.5 (Leopard) through macOS 10.15 (Catalina) relied on hard links to directories, APFS was initially not a supported option for its backup volumes.[24] [23] This limitation was overcome starting in macOS 11 Big Sur, wherein APFS is now the default file system for new Time Machine backups (existing HFS+-formatted backup drives are also still supported).[25] macOS Big Sur's implementation of Time Machine in conjunction with APFS-formatted drives enables "faster, more compact, and more reliable backups" than were possible with HFS+-formatted backup drives.[26] [27]
An experimental version of APFS, with some limitations, is provided in macOS Sierra 10.12.4. It is available through the command line diskutil utility. Among these limitations, it does not perform Unicode normalization while HFS+ does,[33] leading to problems with languages other than English.[34] Drives formatted with Sierra’s version of APFS may also not be compatible with later versions of macOS or APFS, and the Sierra version of APFS cannot be used with Time Machine, FileVault volumes, or Fusion Drives.[35]
Since macOS 10.13 High Sierra, all devices with flash storage are automatically converted to APFS.[36] As of macOS 10.14 Mojave, Fusion Drives and hard disk drives are also upgraded on installation.[37] The primary user interface to upgrade does not present an option to opt out of this conversion, and devices formatted with the High Sierra version of APFS will not be readable in previous versions of macOS. Users can disable APFS conversion by using the installer's startosinstall utility on the command line and passing --converttoapfs NO.[38]
FileVault volumes are not converted to APFS as of macOS Big Sur 11.2.1. Instead macOS formats external FileVault drives as CoreStorage Logical Volumes formatted with Mac OS Extended (Journaled). FileVault drives can be optionally encrypted.
iOS 10.3, tvOS 10.2, and watchOS 3.2 convert the existing HFSX file system to APFS on compatible devices.[10] [11] [39]
Despite the ubiquity of APFS volumes in today's Macs and the format's 2016 introduction, third-party repair utilities continue to have notable limitations in supporting APFS volumes, due to Apple's delayed release of complete documentation. According to Alsoft, the maker of DiskWarrior, Apple's 2018 release of partial APFS format documentation has delayed the creation of a version of DiskWarrior that can safely rebuild APFS disks.[40] Competing products, including MicroMat's TechTool and Prosoft's Drive Genius, are expected to increase APFS support as well.
Paragon Software Group has published a software development kit under the 4-Clause BSD License that supports read-only access of APFS drives.[41] An independent read-only open source implementation by Joachim Metz, libfsapfs, is released under GNU Lesser General Public License v3. It has been packaged into Debian, Fedora Linux, Rocky Linux, Red Hat Enterprise Linux and Ubuntu software repositories.[42] [43] [44] Both are command-line tools that do not expose a normal filesystem driver interface. There is a Filesystem in Userspace (FUSE) driver for Linux called apfs-fuse with read-only access.[45] An "APFS for Linux" project is working to integrate APFS support into the Linux kernel.[46]
A commercial product, Paragon's APFS for Windows allows for read and write support to APFS volumes in all versions of Windows from Windows 7 through Windows 11 and Windows Server 2008 R2 through Windows Server 2022, but it is unable to format or verify APFS volumes, and it cannot read APFS volumes which are hardware-encrypted against the Apple T2 security chip.[47]