Support Center

macOS ships an NTFS reader but no writer. Microsoft never licensed NTFS writing to Apple, so an NTFS volume mounts read-only by design. New Seagate and WD drives often arrive pre-formatted as NTFS, which is why they look locked the moment you plug them in. A failing drive shows different symptoms: it disappears, clicks, or drops off mid-copy. DiskBee registers an FSKit file system and the same volume mounts writable, with existing files untouched.

macOS reads and writes APFS, Mac OS Extended, FAT32 and exFAT, and reads NTFS only. APFS and HFS+ are Mac-only: Windows cannot open them at all. FAT32 works on both systems but caps any single file at 4GB. exFAT has no journal, so an unplug without ejecting can damage the directory. NTFS is journaled and native to Windows; on a Mac it needs a driver before you can write.

Yes. The minimum is macOS 15.4, which covers macOS 26 Tahoe and macOS 27. One universal installer runs on Apple Silicon (M1 through M6) and Intel alike. The file system runs on FSKit, Apple's user-space framework, so there is no kernel extension to approve and no Recovery Mode step.

Boot Camp partitions are usually NTFS, which macOS mounts read-only on its own. With DiskBee installed, a standard NTFS partition including BOOTCAMP mounts writable. You do not have to reboot into Windows to drop a file in.

Yes. DiskBee ships a BitLocker engine: enter the volume password or the 48-digit recovery key and the volume unlocks in place. "Remember in Keychain" makes later plug-ins automatic. Supported: NTFS BitLocker volumes created on Windows 7 or later, in XTS-AES 128/256 or AES-CBC compatibility mode. Not supported: BitLocker To Go sticks (FAT32/exFAT), volumes paused mid-encryption or mid-decryption, and TPM-only volumes with no password or recovery key.

Read and write both work. After unlocking, the volume mounts read-write and data is encrypted to the BitLocker standard before it reaches the disk, so Windows sees the same content when the drive goes back. Choose "Mount as read-only" if you only need to copy files out. Power-loss behaviour matches Windows: the NTFS journal repairs metadata, and at most the file being written is incomplete.

FSKit is the framework the app is built on, and Apple shipped it in macOS 15.4. It lets NTFS read-write run in user space, which is what removes the kernel extension, the SIP change, the Recovery Mode detour and the restart after install. Before 15.4 every NTFS writer had to use the deprecated kext route. On a Mac that cannot reach 15.4, reading and copying files out still work for free, because macOS reads NTFS natively. Writing then means either a kernel-extension product, with the security trade-offs that implies, or a Windows PC.

Disk Utility offers NTFS nowhere because macOS cannot create NTFS volumes. Once DiskBee is installed, an NTFS personality is registered: the website edition erases a drive to NTFS in one click from the Pro toolbox, while the App Store edition routes the job through Disk Utility or diskutil to the same extension. A Windows PC via Disk Management also works. Formatting erases the drive, and NTFS is the only target format offered.

Choose NTFS when the data matters. It is journaled, native to Windows, and writable on Mac with DiskBee. exFAT is fine for moving small files between machines with zero setup, but the missing journal means an unplug without ejecting can take the directory with it. FAT32 exists for legacy hardware and stops at 4GB per file.

The risk is real, though it does not happen on every unplug. exFAT keeps no journal, so a power cut mid-copy, a pulled cable or a failing cable can leave the allocation table inconsistent. In bad cases the partition shows up as RAW. Keep the only copy of footage or backups on another drive, and eject before disconnecting.

You cannot, because the limit is part of the FAT32 specification. When a large video or disk image fails with "file too large", back the drive up and reformat it as exFAT or NTFS. exFAT keeps Windows and Mac compatibility; NTFS adds journaling.

Formatting erases the volume, and there is no in-place conversion between NTFS, exFAT and FAT32. The reliable order is copy everything elsewhere, format, then copy back. If the drive is already NTFS and the data is awkward to move, installing an NTFS driver on the Mac avoids the round trip entirely.

That depends on how strictly the driver follows the NTFS specification. DiskBee writes through Apple's FSKit framework, follows the journaling rules, runs a structure check before each mount, and refuses to write to a disk whose check fails. Critical actions such as ejecting ask for confirmation. Keep a backup of anything irreplaceable, as you would with any file system.

Error -36 is Finder's generic read/write failure. Three causes cover most cases: a damaged source file, an unstable link between Mac and drive, or file-system errors on the target. Start with a known-good cable plugged straight into the Mac, run a structure check on the target drive, then copy in smaller batches.

Disconnects do not always mean the drive is failing. Cables, enclosure controllers and underpowered 2.5-inch drives account for most of them. Whatever the cause, stop writing, copy important data out read-only, then swap cables and run a disk check. Repeated disconnects across several computers, or a clicking noise, point at hardware.

Yes. macOS caches writes, and pulling the cable before they flush can leave the directory inconsistent. exFAT is the most exposed, which is why portable drives formatted that way account for a large share of corruption cases. Use "Safely Remove Hardware" on Windows for the same reason.

First Aid in Disk Utility handles APFS, HFS+, FAT32 and exFAT, and skips NTFS. DiskBee runs a four-level read-only check instead: MFT walk, allocation geometry, $Bitmap reconciliation and index verification, reported as a graded summary. Problems it can prove safe, such as lost clusters or a stale dirty bit, are repaired after you confirm the plan. Deeper damage is referred to Windows chkdsk /f, which remains the authoritative NTFS repair.

Try a cable you know carries data, plugged directly into the Mac rather than through a hub. Confirm the drive spins up or its light comes on. Open Disk Utility and see whether it appears; a greyed-out entry can be mounted by hand. Then check DiskBee's disk list, and restart the Mac. If several computers fail to detect it and it clicks, treat it as a hardware problem.

Some mechanical drives and enclosure chips behave poorly with Apple Silicon, which users have reported for years. Use a short, good-quality cable with no hub, give 2.5-inch drives enough power, and move large copies off the system's read-only mount. Pull important data out before you experiment further.

Products built on kernel extensions, macFUSE or ntfs-3g tend to break with major macOS releases, because kernel rules change and the driver stops loading. Some users end up lowering security again after each upgrade. DiskBee runs in user space through FSKit, so the kernel is not involved.

Neither. It is a user-space file system on FSKit, Apple's framework for exactly this job. SIP stays on, Recovery Mode is not needed, and installation does not ask for a restart.

Reading, viewing, copying files out, mount management and the speed test are in the free tier, and the website edition adds the four-level structure check. If you only pull data off drives, you may never need Pro. Writing, editing, deleting, renaming and renaming volumes need Pro, which is a one-time purchase.

Three differences matter. Architecture: most alternatives still ship kernel extensions, which on Apple Silicon means Recovery Mode and a restart; this one is FSKit user space. Price: ¥98 / $13.99 once, updates included, against monthly or yearly billing elsewhere. Behaviour: spec-compliant writes, a pre-mount check, and an uninstall that leaves no driver behind.

Usually not. Bargain codes tend to come from pirated builds or fake resellers. Typical symptoms are unstable writes that damage a drive, drivers left behind after uninstall, breakage after a system update, and no support. The drive holds your data, so buy from the official channel.

The website edition is one payment: ¥98 in China, $13.99 internationally, lifetime license, updates included. The App Store edition offers both one-time and yearly options. A license covers one Mac, tied to a device fingerprint. Moving to a new Mac is self-service: unbind on the old machine under Settings → License, or choose "Transfer with order number" if it is lost or broken, for up to 5 transfers.

No. macOS reads NTFS on its own, and the free tier adds mount management and copy-out. Payment only starts when you need to write.

The license covers later versions, so a macOS upgrade does not trigger a second payment. User-space code on FSKit is also less exposed to the kernel changes that break extension-based drivers.

No. The website edition checks for updates in the background and installs them with one click, and "Check for Updates…" sits in the app menu. The App Store edition updates through the App Store. Either way the license covers every later version.

Check the things that can be verified. The app is signed with an Apple Developer ID and notarized. It uses Apple's FSKit rather than a home-grown kernel extension. Privacy, terms and refund policies are published, naming the operating entity and contact details, and overseas payments run through Paddle as merchant of record. A small team usually means faster replies and no bundled promotions.

For a fixed job like reading and writing NTFS, a one-time license is usually cheaper to own. ¥98 or $13.99 buys the current version plus updates, with no renewal to track and no cancellation friction. A subscription makes sense when you need ongoing enterprise support and a feature set that keeps growing. Try the free tier first and decide from your own use.