Extend native file handling in OS X (was OSXFUSE)

FUSE for macOS

Browse by Company

Adobe, Apowersoft, Autodesk, Avast, Corel, Cyberlink, Google, iMyFone, iTop, Movavi, PassFab, Passper, Tenorshare, Wargaming, Wondershare

FUSE 4.2.0

  -  5.7 MB  -  Open Source
Free Download

Security Status

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of FUSE 4.2.0.


For those interested in downloading the most recent release of FUSE for macOS or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

Download FUSE 4.2.0

  • FUSE 4.2.0 Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    FUSE 4.2.0 Screenshot 1
  • FUSE 4.2.0 Screenshot 2

What's new in this version:

- Add experimental support for macOS 12.
- Restore support for macOS 10.9 to 10.11. In Xcode 12.5, Apple fixed an issue that caused macOS 10.11 and earlier versions of macOS to reject packages signed in macOS 11 or later. With this fix, support for macOS 10.9 to 10.11 could be restored. This release supports macOS 10.9 to macOS 12.
- Add experimental support for Xcode 13
- Update build scripts to add support for newer macOS SDKs and use macOS 11.3 SDK instead of the macOS 11.1 SDK to build macFUSE.
- Add mount option norm_insensitive. When using the norm_insensitive option with a high-level file system, file names are normalized before performing a lookup. File names using different normalization forms will be treated as equal.
- Fix bug in libfuse when calling the filler function in the readdir callback with non-zero offsets. The bug occurred when a filesystem client read a directory until the end, seeked using seekdir() to some valid non-zero position and called readdir(). A valid directory entry is expected, but NULL was returned instead.

Top Downloads

More Popular Software »