For a transfer drive that current Mac and Windows computers both need to write, start with exFAT. Try your actual destination devices before moving the only copy of a file. For a recorder or a backup tool, check the destination's own format requirement before you choose.
Check the current format and available space before opening an erase dialog. If a Mac can read an NTFS drive but refuses to write a test file, check Apple's external drive troubleshooting steps. The documented causes include format, permissions and available space. You can copy the existing files to a verified second location before choosing whether to change the drive.
Match the format to the job
| Job | Starting choice | Verify before committing |
|---|---|---|
| Copy large video files between recent Macs and Windows PCs | exFAT | Both can create, edit and read the same disposable file |
| Exchange short files with a recorder or older embedded device | The format named by the device maker, sometimes FAT32 | Try the longest and largest file the device will actually use |
| Keep a Mac backup destination | A destination prepared by Time Machine | Watch for its setup requirements and test a restore |
| Store Windows data that depends on NTFS features | NTFS | The Mac's built-in write support does not cover this destination |
Disk Utility's format guide lists ExFAT and MS-DOS (FAT) among Windows-compatible options and describes APFS for Macs. Microsoft compares file size and filesystem features for NTFS, exFAT, FAT32 and UDF. A single file near 4 GiB can already cause trouble on FAT32. In an example collection, five 1 GiB clips can fit where one 5 GiB clip cannot, even when the drive has plenty of room.
If your use case is automated recovery, follow Time Machine's destination setup separately from the decision about shared file transfer. A partition that both computers can browse offers no evidence that your backup app accepts it.
Test both directions with a spare file
Reformatting erases the contents of the selected volume. Read a file from your extra copy before considering an erase, and check the target drive by model or capacity when the computer lists several disks. Begin by testing the existing format if both computers already mount it.
On the Mac, copy in a sample at least as large as the largest file you expect to exchange. Eject the drive and open that file on Windows. Write a separate test file from Windows, eject, then open it and edit a copy on the Mac. Record which computer created each sample and which computer could open and modify it. If a camera or recorder also needs the drive, repeat the write test on that device before transferring anything you cannot reproduce.
Check whether the current drive already does the job
Plug the drive into the Mac and open the disk information to see the current filesystem. Repeat on the Windows computer before opening any format dialog. Write down which hosts can open existing files, which can create a new one, and how the media is meant to travel. A drive used for delivery between two computers can have a different format from the archive that protects your only original.
Suppose a production team has to exchange a single 7 GiB recording. Test with a copy of that size before using the drive for a real delivery. A filesystem can have ample total space while the requested file can still exceed its limit for one file. Leave enough room for the extra test files and make sure the receiving program will open the sample after the copy. If you also need an older camera to read the drive, use the camera's supported requirements and test it separately. Compatibility with two desktop systems does not establish what a third device needs.
If reading succeeds on the Mac but writing fails, check the drive's filesystem and available space. Then inspect whether the folder and volume are actually writable under the account you use. For NTFS, Apple's support article describes the built-in write limitation. An authorised third-party driver, a network share, or a transfer through another appropriately formatted disk may be part of a specific approved workflow. A format change is useful only after the storage and compatibility requirements are clear.
Rehearse with the largest file and a deep path
Copy a harmless data file from one computer and safely eject the drive. On the other computer, check its size and open it with the app that matters. Copy a second disposable file back in the opposite direction. Add a nested folder if you will move structured projects. If permissions, filenames, or the destination application are part of the job, check those in the sample. Use the deep-path transfer test before a Mac folder with many nested names is copied to Windows.
Keep a log of failures with the direction, file size and action. If a small file moves both ways and a much larger one fails, look at space, filesystem limits and the message the destination gives. If every write fails on just one computer, inspect its mounted permissions or format support. If the drive goes missing during the copy itself, investigate the physical connection or power and keep the format unchanged during that diagnosis. Choose a different destination if the only usable copy would otherwise be put at risk.
Keep the backup destination distinct
For backup work, let the backup application verify its chosen destination. A generic cross-platform folder can store files without supporting the metadata or features the backup process expects. If you plan to share one physical drive between uses, review the vendor's volume guidance and the space actually available to each purpose. Keep an independent copy of important files before rearranging volumes. A folder for exchanging a video should not be the only available backup of that video.
After choosing a format, document which computer made the sample, which one read and wrote it, and the largest test file. Leave the new setup unchanged until you have opened a real delivery from the receiving side. Eject the drive in the ordinary way after each transfer. If the next job has a larger file or adds another device, try that combination while you still have the original file somewhere safe.


