Why an NTFS Drive Mounts Read-Only on a Mac

Confirm the format before anything else

The pattern is consistent. The drive mounts, files open and copy off, but dropping a file onto it fails, new folders do nothing, and delete or rename show a crossed-out badge. Check the format in Disk Utility or through Get Info. If it says NTFS, the rest of this page applies.

A drive that does not appear at all is a different fault: cable, power, mount state or partition damage. Work through the drive-not-showing-up guide before assuming the format is the problem.

Apple ships a reader, not a writer

NTFS belongs to Microsoft. macOS includes read support and has never enabled write support, so every NTFS volume mounts read-only by default. That is the design, not a malfunction. Seagate and WD ship many drives formatted as NTFS, which is why a new disk can look broken the first time it is plugged into a Mac.

If reading is all you need, you already have it

Reading NTFS costs nothing on macOS, and the free tier of DiskBee adds permanent read-only access plus mount management with no time limit. A read-only mount is also the appropriate state for a drive you must not alter, such as one waiting for data recovery.

What the zero-cost write routes cost instead

• The experimental write switch hidden in the kernel. It is undocumented, unsupported by Apple, has a long record of corrupting volumes, and is being removed in recent releases. Not a candidate for data you care about;
• ntfs-3g with macFUSE and similar drivers. They are kernel extensions, so Apple Silicon needs SIP disabled and security lowered in Recovery Mode. Major macOS upgrades break the setup, as many users found after moving to Tahoe, and the cycle restarts with every release;
• Sideloaded "free" builds and cut-price activation codes. Unstable writes, a paywall that appears after the first successful transfer, and drivers that leave residue behind are the usual outcomes.

Four things to weigh in a paid driver

• Architecture. FSKit drivers run in user space, like DiskBee, so they need no kernel extension, no SIP change, no Recovery Mode and no restart. Legacy kext drivers need all four on Apple Silicon and break whenever Apple changes kernel rules;
• Write safety. Spec-compliant journaled NTFS writes, plus a pre-mount health check that warns before writing to a disk in trouble;
• Price shape. A one-time purchase of ¥98 or $13.99 with lifetime updates reads very differently from an annual subscription, which several rivals charge;
• Clean uninstall. One click should remove the driver and hand the volume back to macOS in its default read-only state.

Read-only can also come from the volume

A correctly installed driver will still mount read-only when the volume itself is in a protected state. An unsafe eject or a power cut leaves a dirty bit, and Windows Fast Startup leaves the volume hibernated. Eject properly on the Windows side, turn Fast Startup off there, then run a structure check; the free four-level check in DiskBee covers this. Once the journal replays and the dirty state clears, writable mounting returns.

So what is actually broken

Nothing. Read-only NTFS on a Mac is a gap in macOS, and copying files out has always been free. Writing needs a driver. Choose one built on FSKit and the SIP-lowering, breaks-after-every-upgrade cycle never starts, while the data already on the disk stays where it is.