OSXFUSE

com.github.osxfuse.frameworks.OSXFUSE · System Extensions · v3.10.4
Native Version Spotted 204 devices
Native Version Spotted

Universal version latest seen at v3.11.2 · Reported by 20 Macs in the community.

All sighted native versions (8):

v3.11.2 ×1 v3.10.4 ×11 v3.8.3 ×3 v3.8.2 ×1 v3.10.5 ×1 v3.7.1 ×1 v3.6.3 ×1 v3.10.2 ×1

Sighting data is community-sourced — version availability and pricing should be verified with the developer.

About This App

OSXFUSE is a macOS kernel extension framework that extends the operating system's native file handling capabilities via third-party user-space file systems built on FUSE (Filesystem in Userspace). It allows developers to write custom file system implementations that appear and behave like native volumes to the OS and applications. Common use cases include mounting remote storage (via sshfs over SSH), in-memory file systems, cloud storage bridges, and specialized data repositories. OSXFUSE was renamed to macFUSE in 2017 as it transitioned to a community-maintained project. A native Apple Silicon build has been confirmed running on Macs in the Rosetta Check community.

Versions Seen 18 versions
v3.9.0 v3.8.3 v3.8.2 v3.7.1 v3.6.3 v3.5.8 v3.5.6 v3.5.5 v3.5.3 v3.5.2 v3.5.0 v3.4.2 v3.11.2 v3.11.0 v3.10.4 v3.10.3 v3.10.2 v3.0.5

AI Recommendation

1 suggestion
OSXFUSE AI
https://github.com/osxfuse/osxfuse/releases

A native Apple Silicon build of macFUSE (formerly OSXFUSE) is available and has been confirmed running on community Macs. Because macFUSE is a kernel extension, Rosetta 2 cannot translate it, so M-series Macs require the native build to use it at all. Download the latest installer directly from https://github.com/osxfuse/osxfuse/releases or from macfuse.io and run the standard installer package — it automatically detects your Mac's architecture and delivers the correct build. The installer includes both the runtime and development SDK. After installation completes, you will be prompted to allow the kernel extension in System Settings under Security & Privacy; click Allow and reboot to finalize the load. Any file systems you were using with the Intel version (such as sshfs mounts) will continue to work with the native build after the transition.