5.5.0
Latest
OpenNavo editorial Added to Homebrew
Updated to version 5.5.0. The official release notes do not list specific changes.
Benjamin Fleischer and contributors · macOS runtime and APIs for separately installed user-space FUSE file systems, with kernel and FSKit backends and backend-specific setup requirements.
brew install --cask macfuseOpenNavo editorial Added to Homebrew
Updated to version 5.5.0. The official release notes do not list specific changes.
OpenNavo editorial Added to Homebrew
Improves FSKit operations and caching, hardens kernel protocol handling and fixes mount, read/write, rename and cleanup problems.
Improves FSKit operations and caching, hardens kernel protocol handling and fixes mount, read/write, rename and cleanup problems.
Official detailed release. The MFMount API may change in later releases, as noted by the publisher. Build SDK versions describe compilation and do not establish the minimum user OS.
OpenNavo editorial Added to Homebrew
Improves FSKit daemonization, interruptible mount channels, cancellation safety and library teardown.
Improves FSKit daemonization, interruptible mount channels, cancellation safety and library teardown.
Official detailed release. The MFMount API may change in later releases, as noted by the publisher. Build SDK versions describe compilation and do not establish the minimum user OS.
macFUSE 5.3.2
FSModule (FSKit Backend)Include Swift compatibility library
The file system extension requires libswiftCompatibilitySpan. on macOS 15.
MFMount.framework Include Swift compatibility library
The swift-collections package requires libswiftCompatibilitySpan. on macOS 15 and earlier. This addresses macfuse/macfuse#1176.
Update the swift-collections package from version 1.4.1 to 1.6.0
Please note that parts of the MFMount. API may still change in future releases.
macFUSE 5.3.1
Add initial support for macOS 27
Add initial support for Xcode 27
FSModule (FSKit Backend)Use the node identifier and generation as the authoritative handle for file system items instead of the inode number. Perform FUSE_LOOKUP to get authoritative handle of directory entries returned by FUSE_READDIR
Previous releases assumed that the node identifier and inode number were identical, as is the case when using the high level libfuse API without use_ino. This change removes that shortcut and resolves macfuse/macfuse#1166 and macfuse/macfuse#1167.
Improve stability by fixing a bug in open file handle management
Improve performance when preparing messages sent to the file system server
Improve performance when enumerating directories by using FUSE_BATCH_FORGET
Update the kernel extension version to 5.3.1
Remove the file system item from the name cache when handling FUSE_NOTIFY_INVAL_ENTRY
This ensures that the next lookup triggers a FUSE_LOOKUP request and resolves macfuse/macfuse#1160.
Address an incompatibility with the macOS 27 SDK included in Xcode 27.0 beta 1
MFMount.framework Turn MFChannelCreateWithDeviceFileDescriptor() into a weak import
This function will be removed once MFMount() supports mounting volumes using the kernel backend. Check that the symbol is available before calling it.
Please note that parts of the MFMount. API may still change in future releases.
libfuseVNOP_MONITOR. This adds the missing free_path() call in fuse_lib_monitor() and resolves macfuse/macfuse#1168.libfuse3VNOP_MONITOR. This adds the missing free_path() call in fuse_lib_monitor() and resolves macfuse/macfuse#1168.macFUSE 5.3.0
Update build process to use Xcode 26.5 (macOS 26.5 SDK)
Introduce a new channel API for exchanging FUSE messages with FUSE backends. The new API significantly improves I/O performance for volumes mounted using the FSKit backend.
FSModule (FSKit Backend)Add support for the new channel API provided by MFMount.
Add support for the new FUSE_INIT flags FUSE_DARWIN_REPLY_BUF and FUSE_DARWIN_PAYLOAD_BUF. The flags allow for zero-copy reads and writes.
Substantially improve I/O performance. Tests with the LoopbackFS reference file system show that reading files is up to 15 times faster than in previous releases.
Improve stability by addressing a race condition when accessing cached volume statistics that could cause the file system extension to crash.
MFMount.framework Introduce a new channel API for exchanging FUSE messages with the FSKit Backend and the Kernel Backend.
MFMount. is intended for developers porting FUSE user-space libraries to macOS, or adapting existing libraries to support mounting volumes using the FSKit backend. The framework handles the mount operation and provides a C API for communicating with the backend.
The new channel API exposes FUSE messages as borrowed buffers instead of requiring callers to copy each message into a single contiguous buffer. This allows for zero-copy reads and writes for large payloads when using the FSKit backend.
MFChannelRef for message-oriented communication with a backend. A channel is associated with a volume when the volume is mounted.MFMessageRef for inspecting received FUSE messagesPlease note that parts of the MFMount. API may still change in future releases.
libfuseMFMount.framework libfuse3MFMount.framework OpenNavo editorial Added to Homebrew
Introduces an XPC-based FSKit mounting API for sandboxed file systems and improves FSKit tools and libfuse3 compatibility.
Introduces an XPC-based FSKit mounting API for sandboxed file systems and improves FSKit tools and libfuse3 compatibility.
Official detailed release. The MFMount API may change in later releases, as noted by the publisher. Build SDK versions describe compilation and do not establish the minimum user OS.
GitHub Release Added to Homebrew
Update kernel extension to version 5.1.3
Add special handling for the O_EXEC open flag to prevent a kernel panic. Internally, O_EXEC is treated as O_RDONLY, meaning a readable file descriptor will be requested from the file system server. For details, see macfuse/macfuse#1130.
FSModule (FSKit Backend)libfuse3setxattr handler always being an empty string. On macOS, FUSE_COMPAT_SETXATTR_IN_SIZE needs to account for the additional position field and its associated padding. For details, see macfuse/macfuse#1134.GitHub Release Added to Homebrew
FSModule (FSKit Backend)Improve automatic file system extension registration
The file system extensions are registered automatically before mounting a volume and can be registered manually using the install subcommand. The --force flag removes any duplicate extensions before registering the current set.
/Library/Filesystems/macfuse.fs/Contents/Resources/macfuse.app/Contents/MacOS/macfuse install --force
Add support for streaming logs using the log subcommand
/Library/Filesystems/macfuse.fs/Contents/Resources/macfuse.app/Contents/MacOS/macfuse log stream
Resolve compatibility issues with legacy versions of macOS
Previous releases installed the io. launch service on unsupported versions of macOS, which could result in the service crashing and the installer hanging. This release removes the service on unsupported versions of macOS.
GitHub Release Added to Homebrew
Update kernel extension to version 5.1.1
Disable VNOP_MONITOR support on macOS 15. VNOP_MONITOR was introduced in macOS 15.4. Disable the feature on macOS 15 to maintain compatibility with macOS versions before 15.4.
macFUSE 5.1.0
Update build process to use Xcode 26.1 (macOS 26.1 SDK)
Update demo file systems
LoopbackFS demo file systems and add a libfuse3 variant (LoopbackFS-libfuse3-C)HelloFS demo file system (HelloFS-Framework-Swift). It serves as a minimal "Hello World" example — in just 40 lines of code.Update kernel extension to version 5.1.0
Add support for the VNOP_MONITOR file system callback
The VNOP_MONITOR callback is available since macOS 15 and notifies file systems when the number of watchers for a file system item changes. This allows distributed file systems to subscribe only to events for items that are actively being watched, improving efficiency and reducing unnecessary event handling.
VNOP_MONITOR callback is invoked, the kernel extension sends a FUSE_MONITOR message (struct fuse_monitor_in) to the file system server running in user spaceFUSE_MONITOR_BEGIN flag is set when a new watcher starts monitoring the itemFUSE_MONITOR_END flag is set when a watcher stops monitoring the itemFix a bug in VNOP_LINK that can cause a deadlock in case a file system uses the same nodeid to represent both the original file system item and its link. In this case, trying to lock the link in VNOP_LINK resulted in a deadlock. For more information, see macfuse/macfuse#1120.
Fix a bug in VNOP_MNOMAP that can cause a deadlock. The VNOP_WRITE callback might end up calling the VNOP_MNOMAP callback. Attempting to lock the already locked file system item in the VNOP_MNOMAP callback caused the deadlock.
Fix f_mntfromname (fsname mount option) being truncated at 90 bytes. f_mntfromname supports names of up to 1024 bytes (including the terminating \0 character). For more information, see macfuse/macfuse#1123.
FSModule (FSKit Backend)Add support for mounting "non-local" volumes (typically distributed file systems) on macOS 26. Mounting "local" volumes (typically physically attached storage) is supported on macOS 15.4 and later macOS versions.
Add support for mount option local. macOS is more aggressive in dealing with "local" volumes. Treat this option as experimental.
Add support for mount option volname=, where NAME is a string. You can use the volname option to specify a name for the volume being mounted.
libfusemonitor callback handler and implement support for the new FUSE_MONITOR message. For more information, see "Kernel Extension".libfuse3Add support for mounting file systems using the FSKit backend. By default, the kernel backend is used to mount volumes. When specifying the mount option -o backend=, libfuse3 will use the FSKit backend to mount the file system. For more information, see FUSE Backends.
Add new monitor callback handler and implement support for the new FUSE_MONITOR message. For more information, see "Kernel Extension".
Add utimens API extension for macOS. When FUSE_DARWIN_ENABLE_EXTENSIONS is set to 1 , the utimens handler is called with three time stamps — the file's access, modification, and backup time stamps. By default, the handler is called with the file's access and modification time stamps.
Fix a bug in the statfs API extension for macOS and add missing fuse_lib_statfs$DARWIN() handler
Fix a bug in the threadid module that prevented several file system callback handlers from being invoked when using the module
Adapt fuse_clone_chan_fd_default() for macOS. On macOS, there is no need to associate new FUSE device file descriptors with the original ones.
Rename crtime (creation time) btime (birth time). This change does not affect ABI stability, but it requires code updates when compiling a file system with this release and the macOS API extensions being enabled.
Improve Swift support
GM type name prefix in SwiftUserFileSystem.MoveOptions more idiomatic for SwiftFileAttributeKey extension defining additional framework-specific attribute keysTurn NSObject categories UserFileSystemLifecycle, UserFileSystemOperations, and UserFileSystemResourceForks into actual protocols
Remove unsupported exchangedata() callback handler. exchangedata() has been superseded by renamex_np() and has been unsupported since macOS 11. This change deprecates the corresponding delegate method.
- (BOOL)exchangeDataOfItemAtPath:(NSString *)path
withItemAtPath:(NSString *)otherPath
error:(NSError * _Nullable * _Nonnull)error
GitHub Release Added to Homebrew
Update build process to use Xcode 26.0.1 (macOS 26.0 SDK)
Update Installer package to use absolute paths when invoking command line tools in the postinstall script
Drop compatibility code for macOS 11 and earlier. macFUSE 5 supports macOS 12 through macOS 26.
Fix license file formatting. On macOS 26, QuickLook fails to render lists correctly if they are placed inside table cells in rich text documents.
Update kernel extension to version 5.0.7
Preserve a vnode's identity when marking it as dangling. Resetting the identity causes the fchmod(2) system call to fail. This addresses macfuse/macfuse#1112.
Resolve symbolic links in the kernel extension path before attempting to load the kernel extension
FSModule (FSKit Backend)Improve support for macOS 26. FSClient now provides information about installed third party file system extensions, enabling more reliable detection of whether a file system extension has been enabled by the user.
Add support for creating a mount point in / automatically when mounting a volume
Introduce foundational changes in preparation for new FSKit features in macFUSE 5.1
libfuse3typeof with the __typeof__ builtin in headers. The typeof keyword is part of the C23 ISO standard, but is not officially supported in older C ISO standards.GitHub Release Added to Homebrew
Use macOS 26.0 SDK instead of macOS 15.5 SDK to build macFUSE
Introduce foundational changes in preparation for new FSKit features in macFUSE 5.1
libfuse3libfuse3 to version 3.17.4macFUSE 5.0.5
macFUSE 5.0.4
Improve compatibility with macOS 26. macOS 26 reports itself as macOS 16 for binaries that were built using the macOS 15 SDK. This affected the updater.
Add support for updating the bundled Launch Services when mounting a volume.
Add --force option to re-install the bundled Launch Services even though they are already up to date.
Update kernel extension to version 5.0.4
Fix rare kernel panic when re-parenting "dangling" vnodes. Dangling vnodes were removed from the file hierarchy, but each retained a reference to its previous parent directory. This could trigger a kernel panic under certain conditions. For details, see macfuse/macfuse#1085.
macFUSE 5.0.3
Add support for macOS 26
Add support for Xcode 26
libfuseICU instead of iconv to normalize file names. The iconv release bundled with macOS lacks full Unicode coverage (e.g., emojis). For details, see macfuse/macfuse#1077.libfuse3ICU instead of iconv to normalize file names. The iconv release bundled with macOS lacks full Unicode coverage (e.g., emojis). For details, see macfuse/macfuse#1077.macFUSE 5.0.2
Use macOS 15.5 SDK instead of macOS 15.4 SDK to build macFUSE
Switch from App Services to Launch Services. This change streamlines the installation process and eliminates the need for users to authenticate as admin when using the FSKit backend for the first time.
Drop support for macOS 11. macOS 12 is the first macOS release that supports Swift Concurrency natively.
Update uninstaller to remove new Launch Services
libfuse3ino64_t type may be unavailable when _POSIX_C_SOURCE is defined. For more information, see macfuse/macfuse#1080.macFUSE 5.0.1
Update uninstaller for macFUSE 5
Update build script and add target build options --no-default and --no-inherit
FSModule (FSKit Backend)Fix an issue that could cause a crash of the file system process on failed mount attempts
When mounting a volume, the file system process expects to receive a socket handle for exchanging FUSE messages. Sending the mount status code without sending a socket handle first, can result in a crash. This issue only affected the FSKit backend. For details, see macfuse/macfuse#1071.
Address an issue that could result in the file system extension not being listed in System Settings
In some cases PluginKit fails to discover the file system extension automatically. As a workaround we register the extension explicitly. This issue only affected the FSKit backend. For details, see macfuse/macfuse#1071.
Optimize the service that is responsible for brokering connections between the file system extension and file system server processes
libfuse3libfuse3 to version 3.17.2macFUSE 5.0.0
Add experimental support for FSKit on macOS 15.4 and newer releases of macOS
macFUSE supports two backends for mounting file systems. By default, the kernel backend (based on the legacy VFS kernel API) is used to mount volumes. When specifying the mount-time option -o backend=, macFUSE will use FSKit to mount the volume. For more information, see FUSE Backends.
Drop support for macOS 10.9 to 10.15. macFUSE 5 supports macOS 11 and later versions of macOS.
Update reference file systems for macFUSE 5. For more information, see the demo repository.
Optimize build script
Make framework swift-friendlier by adding generics and nullability annotations
Add new delegate method for listing directories. The new delegate method supports returning directory entries including the name and the requested attributes of each entry. This is the first step in implementing support for FUSE_READDIRPLUS.
- (nullable NSArray<GMDirectoryEntry *> *)
contentsOfDirectoryAtPath:(NSString *)path
includingAttributesForKeys:(NSArray<NSString *> *)keys
error:(NSError * _Nullable * _Nonnull)error
GitHub Release Added to Homebrew
Invalidate a vnode's identity in case the corresponding file is removed.
When performing a remove operation, the file might not actually be removed by the user space code. libfuse renames open files, hides them and defers removing them until all open file handles have been closed (unless hard_remove is enabled). This means we might come across the vnode again, e.g. while performing a readdir(3) operation. We need to invalidate the vnode's current identity to make sure Finder does not display any outdated information.
Optimize build script
GitHub Release Added to Homebrew
Update libfuse3 to version 3.17.1
Some macOS specific features require FUSE API extensions that break compatibility with the vanilla FUSE API. Setting the compile-time flag FUSE_DARWIN_ENABLE_EXTENSIONS to 0, when building a file system, disables those API extensions. By default, the macOS specific API extensions are enabled.
Please note:
libfuse3 API extensions might not be stable, yet. This means that libfuse3 file systems that are built for macFUSE 4.10.1 might need to be updated to work with future macFUSE releases.Add support for arbitrary file system block sizes
The macOS kernel imposes no restrictions on the block size of a file system, neither should we. macFUSE supports file system block sizes between 128 B and 1 MB. The specified I/O size (-oiosize=) is rounded down to the next multiple of the file system block size, if necessary.
The device block size (-oblocksize=) needs to be a power of two and may not exceed 4 KB on Intel Macs and 16 KB Apple Silicon Macs.
Address code signing issue. The bundled download helper ksurl needs to be code signed individually to make its origin transparent. In previous releases, ksurl was only code signed indirectly as component of the update tool. For details, see macfuse/macfuse#1062.
Declare the maximum size of extended attributes. pathconf(. returns the number of bits that are required to store the maximum extended attribute size in bytes, in our case 25, which equals a maximum extended attribute size of 33,554,431 bytes (~ 32 MB).
macFUSE 4.10.0
Add experimental support for libfuse3
Some macOS specific features require FUSE API extensions that break compatibility with the vanilla FUSE API. Setting the compile-time flag FUSE_DARWIN_ENABLE_EXTENSIONS to 0, when building a file system, disables those API extensions. By default, the macOS specific API extensions are enabled.
Please note:
libfuse 2.9.9 and libfuse3 3.17.1 RC1.libfuse3 API might not be stable, yet. This means that libfuse3 file systems that are built for macFUSE 4.10.0 might need to be updated to work with future macFUSE releases.Use iconv() instead of CFStringNormalize() to normalize file names in the high level FUSE API. Calling CFStringNormalize() after daemonizing the file system process results in a crash. See File Names (Unicode Normalization Forms) for details on file name normalization.
Work around a limitation preventing a single process from mounting multiple GMUserFileSystems (macFUSE.) at the same time. Even though a single process can mount multiple GMUserFileSystems, it is recommended to use a separate process per virtual volume. For details, see macfuse/macfuse#1059.
Do not delete intermediate Xcode build files after building a target
Fix a build script logging bug when cleaning a build target
GitHub Release Added to Homebrew
Improve support for FUSE_NOTIFY_INVAL_ENTRY notifications and trigger Finder refresh.
A FUSE_NOTIFY_INVAL_ENTRY notification is fired to inform the kernel that the specified file has a new identity, possibly due to having been renamed remotely. As a result, the vnode is removed from the name cache, a VNODE_EVENT_RENAME event is fired and the vnode's identity is updated on its next lookup.
For details, see macfuse/macfuse#960 and macfuse/macfuse#470.
Improve fault tolerance when looking up vnodes.
In case a vnode type change is detected during a VNOP_LOOKUP call, the original (now outdated) vnode is revoked and a new node is created automatically without returning an error. The error condition will be logged.
For details, see macfuse/macfuse#894.
Optimize build script
macFUSE 4.9.0
This release lays foundational groundwork for macFUSE 5.0
Decouple kernel extension version from release version. In future macFUSE releases, the kernel extension will only be updated in case there have been code changes of the macFUSE kernel code. This avoids prompting users to allow loading a new kernel extension build.
Address a race condition in the libfuse mount process. On macOS, the mount process is asynchronous. This means mount(2) will not have returned when fuse_mount() returns, but we are interested in the mount(2) return code. Therefore, we spin up a separate thread that waits for mount(2) to return.
Use dispatch source to handle signals in libfuse. Mounted volumes are unmounted on SIGHUP, SIGINT and SIGTERM. We should not assume that unmounting a volume is async-signal safe. This means we should not rely on sigaction(2) handlers to perform the unmount operation.
Add support for using Grand Central Dispatch to process file system requests in libfuse. See fuse_loop_dispatch() for details. This reduces the number of threads being created and destroyed and cuts down on resource usage. fuse_session_loop_dispatch() is a drop-in replacement for fuse_session_loop_mt().
Add high-level libfuse mount-time option loop. The loop option can be used to select the file system request processing loop implementation. Supported values are:
single_threaded: Process requests seriallymulti_threaded: Process requests in parallel on worker threads managed by libfusedispatch: Process requests in parallel using Grand Central DispatchThe default implementation is multi_threaded. When mount option -s (single threaded) is present, option loop is ignored.
Use dispatch semaphores as fallback for unnamed POSIX semaphores in libfuse. Unnamed POSIX semaphores are not supported by macOS. Therefore, we have been using a custom fallback implementation based on POSIX threads, which is now replaced by dispatch semaphores.
Silence pthread_setugid_np() deprecation warnings in libfuse
Modernize build script
Clean up code and improve readability
Archive loader and mounter debug symbols
Update links in release disk image
Complete move of all project resources from the osxfuse organization to the macfuse organization. See History for details.