How to Write to NTFS Drives on Mac
A practical guide to writing to NTFS drives on macOS, including free and paid options, safety checks, and how to avoid NTFS corruption.
macOS can read NTFS drives but cannot write to them with its built-in driver. To write, you need a third-party NTFS driver. On macOS 26 or later with an Apple Silicon Mac, Mountee provides free read/write access through Apple's FSKit framework and a bundled ntfs-3g engine, with no macFUSE or kernel extension.
If a Windows-formatted drive shows up on your Mac but every copy, edit, or delete fails, the drive is almost certainly NTFS. macOS reads NTFS fine. It refuses general-purpose writes.
This guide covers the working options, the safety checks that matter before you enable write access, and how to verify that a write actually reached the disk.
Why macOS cannot write to NTFS
Apple ships an NTFS read-only driver. It is enough to open files and copy them off the drive, but not to modify the volume. The limitation is in macOS, not in your drive or its permissions.
There are three ways people work around it:
- Use a third-party NTFS driver that adds write support.
- Reformat the drive to a filesystem macOS can write, such as exFAT. This erases the drive.
- Move files through another system, such as a Windows PC, a Linux virtual machine, or a network share.
A driver is the only option that keeps the drive NTFS and lets you write from your Mac directly.
Before you enable write access
Do these three things first. They take a minute and prevent most bad outcomes.
1. Back up anything important
Any new NTFS driver should be treated like new software that touches a filesystem. Copy irreplaceable files somewhere else before the first write test. This is standard advice for commercial drivers too, not a comment on Mountee specifically.
2. Confirm the filesystem
Open Terminal and list the disks:
diskutil listFind the partition that matches your drive’s size and name. Then inspect it:
diskutil info /dev/disk4s1Replace disk4s1 with your identifier. Look for:
- File System Personality: NTFS
- Read-Only Volume: Yes (this is normal for a cleanly unmounted NTFS volume on macOS)
If the filesystem is exFAT or FAT32, macOS can already write to it. The problem is something else; see Why your external drive is read-only on Mac.
3. Shut Windows down cleanly
If the drive was last used on a Windows PC, make sure Windows finished writing and closed the volume. A drive left in a hibernated or Fast Startup state is marked dirty, and a careful driver will refuse read/write access.
On Windows:
- Turn off Fast Startup in Control Panel → Power Options → Choose what the power buttons do.
- Shut down fully, or use Restart rather than a hybrid shutdown.
- If Windows offers to scan and repair the drive, let it finish.
Do not force write access to a dirty volume. That is how NTFS corruption happens.
Option 1: Mountee (free, macOS 26+, Apple Silicon)
Mountee is a free, open-source NTFS read/write utility built on Apple’s FSKit framework. It bundles the ntfs-3g engine, so there is no macFUSE install, no kernel extension, and no reboot.
It requires macOS 26 or later on an Apple Silicon Mac. The current 0.2.0 release is verified on macOS 26.6.2 and macOS 27.0.1. Intel Macs and older macOS versions are not supported.
Install and enable
- Download the DMG from mountee.app/download.
- Open it and drag MacNTFS.app to Applications. The 0.2.0 installer still uses the old name; it is the same project.
- Launch the app. It appears in the menu bar, not as a normal window.
- Press Enable File System Extension if the status is not Enabled.
- Connect the NTFS drive.
Mount read/write
- Open the Mountee menu bar window.
- Find your volume. It starts as not mounted.
- Choose Mount Read/Write. Read-only is the default; write access is an explicit action.
- The volume appears in Finder and under
/Volumes.
If the volume is dirty or hibernated, Mountee will mount it read-only and log the reason. Fix the Windows shutdown state before trying again.
Verify a write
Create a small test file, then unmount and remount the volume. If the file survives the remount, the write path is working. Do not start with a large important transfer.
Mountee’s safety model is documented in Security model, and its limits are listed in Known limitations.
Option 2: Mounty (free, older macOS)
Mounty is a long-running free menu bar utility. Version 2.x is a front end for macFUSE and ntfs-3g and requires macOS 11 or later. Version 1.x covers older macOS releases, and the official site lists support from macOS 10.9 through macOS 27 overall.
Installation is more involved because you install three pieces:
brew install --cask macfuse
brew install gromgit/fuse/ntfs-3g-mac
brew install --cask mountyMounty’s official instructions also describe the GUI path: install macFUSE, install ntfs-3g, then drag Mounty to Applications. On first launch you will need to trust macFUSE and the ntfs-3g driver in System Settings → Privacy & Security, and a restart is commonly required.
Mounty is a good fit if you are on an older macOS version or prefer its workflow. The trade-off is the extra dependency chain and the security approvals that macFUSE requires. See the Mounty comparison for the full list.
Option 3: A commercial driver
Paragon NTFS for Mac is a well-known commercial option. Its vendor lists support from macOS Catalina through macOS 27, and both Intel and Apple Silicon, with a 10-day trial before purchase. Installation requires a restart, and the product includes volume tools such as format and verify.
Commercial drivers are mature and support more macOS versions. They are closed source and paid. If you need Intel support or older macOS versions, they may be the practical choice. See the Paragon comparison.
Option 4: Avoid the driver entirely
If you only need to move files occasionally, you can skip NTFS write support:
- Copy files off the NTFS drive to your Mac. Reading works natively.
- Use exFAT for drives that must move between Windows and macOS. Reformatting erases the drive, so back up first.
- Use a Windows PC or Linux VM to write to the drive.
- Share a folder over the network from a Windows machine and copy through the network.
These options are free, but none of them lets you write to the NTFS volume directly from Finder.
Common errors and what they mean
| Error or symptom | Likely cause | What to do |
|---|---|---|
| “Read-only file system” after a read/write mount | Volume is dirty or hibernated; Mountee refused write access | Shut Windows down fully, disable Fast Startup, reconnect |
| Drive appears but cannot be mounted | Extension not enabled, or a stale app copy is registered | Enable the extension; see Troubleshooting |
| Copy starts then fails | Disk error, cable, or power problem | Stop, back up, check the drive on Windows |
| Files disappear after unplugging | Volume was removed before writes flushed | Eject first; do not unplug during writes |
| macOS asks for a password or security approval | A macFUSE-based tool is being installed | Follow that vendor’s instructions; Mountee does not need this |
A note on sudo mount commands
You may find old advice that remounts NTFS read/write with a sudo mount -t ntfs -o rw command. Modern macOS does not provide a supported general-purpose NTFS write path this way. At best it fails; at worst it encourages unsafe workarounds. Use a driver designed for the job.
Frequently asked questions
Does macOS ever write to NTFS?
The built-in driver is read-only for general use. Some old Boot Camp-era workarounds existed, but they are not a supported solution on current macOS and Apple Silicon.
Can I write to NTFS for free?
Yes, with limits. Mountee is free on macOS 26+ Apple Silicon. Mounty is free but requires macFUSE and ntfs-3g. See Free NTFS for Mac: available options.
Is it safe to write to NTFS from a Mac?
A careful driver plus backups and a clean Windows shutdown is the safe approach. Never force write access to a dirty volume, and test on non-critical data first.
Will formatting the drive to exFAT fix it?
Yes, but formatting erases the drive. Back up first, and remember exFAT has different metadata and permission behavior from NTFS.
