ExFAT on HDD for FCP editing?

All my external drives are formatted appropriately but I have one HDD (that for reasons I will not go into) I wish to use as ExFAT.


It will not be used primarily with FCP but I have tested a small project and it appears to behave normally.


What if any problems might there be? Is it less reliable than FAT 32?


I have numerous SSDs/NVMes formatted APFS and HDDs formatted Mac OS Extended so please don't tell me not to use ExFAT. 😳

Mac mini, macOS 15.5

Posted on May 17, 2025 7:28 AM

Reply
Question marked as Top-ranking reply

Posted on May 17, 2025 7:56 AM

Don’t put the library on the ExFAT drive. The format doesn’t understand bundles/packages and doesn’t work well with them especially copying or moving them. Using media stored on the drive I don’t think should be a problem.

Similar questions

10 replies

May 18, 2025 6:19 AM in response to Ian R. Brown

Ian R. Brown wrote:

Sometimes when plugging in a FAT32 drive with loads of space I have been unable to add a video as my Mac thinks the drive is full and has zero free space

When sharing files between a Mac and Windows I have used exFAT. But once a problem was that a 128 GB flash drive formatted as exFAT (GUID) on Big Sur was seen only AFAIR 100 MB on Windows 10 while exFAT (Master Boot Record) showed all capacity.


https://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-when-partitioning-a-drive/


On the other hand, formatting a drive with exFAT using Windows may use a file allocation size for the file system which macOS doesn't understand. It seems 128 kB Allocation Unit Size should be used if exFAT is used on a Mac.


https://www.partitionwizard.com/partitionmagic/allocation-unit-size-exfat.html


So usually it is best to use Disk Utility to erase the drive if you are going to format it with exFAT.


And Sequoia might have teething problems with FAT or exFAT:


"The implementations of the exfat and msdos file systems on macOS have changed; these file systems are now provided by services running in user-space instead of by kernel extensions. If the application has explicit checks or support for either the exfat or msdos file systems, validate the applications with those file systems and report any issues. (110421802)"


macOS Sonoma 14 Release Notes | Apple Developer Documentation


May 18, 2025 5:59 AM in response to Ian R. Brown

Whilst on the subject of FAT32 here is something you may not know.


Sometimes when plugging in a FAT32 drive with loads of space I have been unable to add a video as my Mac thinks the drive is full and has zero free space


This is a problem that has occurred sporadically for several years with several Macs involving several HDDs and memory sticks.




As mentioned, this has puzzled me for years and also a number of other Mac users. However, I discovered the reason yesterday.


It is because I and the other sufferers have got DriveDX open in the background.


Switch it off and the drive behaves normally, switch it on and the drive thinks it is full.


There may be other apps that cause this phenomenon. FreeSpace is one.


I am glad I found the reason because for years I have been worried that my drives or computers might be failing!


May 17, 2025 2:54 PM in response to Ian R. Brown

You said you're using an HDD formatted ExFAT in a primarily non-FCP application, and you want to know if ExFAT would cause problems in that application. That's difficult to say.


My team uses RED cameras that record to SSD storage formatted as FAT-32. When recording they automatically split the file into approx. 4.16 GB segments. That process is reliable and is handled by FCP provided the RED workflow software is installed. The file segments are presented as a single clip. All other utility software must understand that format to present the RED .R3D file segments as a single logical clip. So that's an example of automatic file segmentation with a well-documented procedure that works well -- at least among utilities that understand the segmentation format.


If you're asking about file management used by some model of Samsung TV recording to some type of FAT 32 portable drive, you'll probably get a better answer from a support source familar with that specific model of TV.


However, I think some TVs also use automatic file segmentation where they split the file to multiple 4 GB segments. I think some TVs will play that back seamlessly, but others might require selecting each file segment. That would probably also require a specific filename convention, such as MOVIE_001.MP4, MOVIE_002.MP4, etc.


You said this was primarily a non-FCP application scenario, but if you're discussing editing or creating a series of file segments with FCP for playback on the Samsung TV, that would require specific technical information from the TV manufacturer.

May 18, 2025 12:24 AM in response to joema

My oldish DJI P3P does not perfectly segment footage by dropping a few frames at the split point.


I always let the device format the SD card and P3P uses FAT as a default with its max 4GB file size limit. exFAT would allow larger files but unfortunately the P3P then still splits the 60 Mb/s videos at 4GB or about each 9 minute.


So I must remember to take care that the split does not occur in an important spot by starting capture at a certain point of the max 20 minute fly.


Once I had to add 2+2 frames at clip breakpoint to make the split point seem not so jerky.

May 18, 2025 1:06 AM in response to joema

Thanks for the information.


Unfortunately the info given by TV manufacturers appears to be useless.


The TV manual says that recording may or may not be available depending on location or model but it doesn't say whether my model can or can't!


So I am guessing it can't. AI is no help as some searches say it can whilst others disagree and the manufacturer's website contains nothing useful.


So it looks as though I will continue using a FAT32 HDD to play my FCP created movies on TV and forget about recording.

May 18, 2025 6:35 AM in response to Matti Haveri

I always use Disk Utility and the problem has covered several computers, drives and operating systems.


The problem is simply that if DriveDX has not been shut down when the FAT32 drive is plugged in it will register that drive as having zero bytes.


I have tested it numerous times now and it is infallibly the same . . . DriveDX causes some form of conflict.


I don't know whether DriveDX would cause the same conflict with ExFAT as I have not tested it.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

ExFAT on HDD for FCP editing?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.