macFUSE
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.
紹介
macFUSE is Benjamin Fleischer's file-system integration package for macOS. It enables separately installed user-space FUSE file systems to expose their content as mounted volumes. It is infrastructure for compatible storage applications and developers, not a standalone file manager or a bundled collection of file systems.
Features
- Bridge macOS file-system operations to a user-space file-system process.
- Support compatible third-party file systems backed by local files, remote storage, memory or other sources.
- Provide libfuse2/libfuse3-compatible APIs and macFUSE.framework for developers.
- Offer kernel and FSKit backends, with capability and OS differences.
- Provide runtime components, mounting tools and supporting frameworks.
- Enable use cases such as remote storage, encrypted views and app-specific virtual volumes when an appropriate separate file system is installed.
Installation and first use
Install brew install --cask macfuse, or open the official DMG and run its installer. The publisher recommends its own current download and notes that package-manager distributions are not maintained by the macFUSE developers. This cask runs the package installer rather than copying an ordinary GUI application. Install a compatible FUSE file system separately, then follow that product's mount instructions. macFUSE alone does not provide SSHFS, NTFS support, a cloud account or any other particular file system.
System requirements and backend selection
The official current download requires macOS12 or newer and supports Apple Silicon and Intel. No fixed RAM or disk-space minimum was confirmed in the retrieved requirements. Current5.4.0 DMG download size is16,512,456 bytes, separate from installed components and mounted data. macFUSE itself is macOS software; FUSE APIs have implementations on other systems, but that does not make this package a Linux or Windows installer.
The official Getting Started guide describes FSKit as available from macOS15.4; the homepage highlights supported user-space file systems on macOS26. A compatible FSKit workflow avoids loading a kernel extension and does not need Recovery-mode security changes. Backend feature/performance differences and file-system compatibility still matter. The kernel backend uses a kernel extension. On Apple Silicon, initial kernel-backend setup may require enabling third-party kernel extensions in Recovery and approving macFUSE in system security settings, followed by restart. Intel Macs also need applicable approval. Follow the official backend-specific guide rather than assuming every installation needs the same changes. The cask's older blanket kernel-extension caveat is not an accurate description of all current FSKit workflows.
Dependencies, conflicts and maintenance
The cask declares no extra formula dependency but explicitly conflicts with macfuse@dev. A third-party file-system program is required for an actual custom mount and can have its own server, credentials, network, license and permissions. Other installed versions or old FUSE components can affect dependent products; consult their compatibility requirements before changing the runtime. macFUSE installs system-level runtime and mount components, so updates can affect other applications that use them. Unmount active FUSE volumes and preserve their work before removal or maintenance. Homebrew uninstall uses package receipts and launch-service handling; optional zap also removes the preference pane and related user caches. Do not treat uninstalling a shared runtime as equivalent to deleting a self-contained app.
Accounts, costs and license
The official package is available without a core user account or subscription, and the project accepts sponsorship. Third-party file systems and storage services may charge separately. macFUSE uses its own BSD-style license with additional conditions, not unrestricted MIT licensing. In particular, binary redistribution bundled with commercial software, including automated download/installation in that commercial context, needs prior written permission. Incorporated components have their own notices. Review the complete official license for redistribution or product integration; ordinary installation does not grant unrestricted commercial bundling rights.
Official references
新バージョン 5.4.0の更新内容 10月7日 · OpenNavo編集部
- FSKitSupport macOS27 volume APIs and caller identities.
- KernelValidate ioctl replies to prevent potential kernel memory disclosure.
- MountingImprove failure reporting and mount-point ownership handling.
注意事項
macfuse requires a kernel extension to work. If the installation fails, retry after you enable it in: System Settings → Privacy & Security For more information, refer to vendor documentation or this Apple Technical Note: https://developer.apple.com/library/content/technotes/tn2459/_index.html