Final Cut Pro library won't update/copy, possible corruption?

I am running FCP 11.2 on a MacBook with an M2 processor. I keep my FCP libraries on external SSDs, so I can also open them on my iMac Pro.

This morning I opened, or tried to open, a library file I haven't used for three or four months.

But when I clicked 'OK' I got an error message saying FCP was unable to back up the library file. I presumed this was maybe because there was not enough space on the SSD for the backup? I therefore hit 'cancel"

But now, I can't even copy the library to a larger SSD, as when I do, I get an error message saying there is a problem reading the data on the .fcpbundle file.

Does this mean the file is irretrievably corrupted?

MacBook Air (M2, 2023)

Posted on Jan 1, 2026 2:57 PM

Reply
Question marked as Top-ranking reply

Posted on Jan 2, 2026 2:53 PM

If you get an error trying to copy the library via Finder to a larger SSD, that has nothing to do with FCP. That is a filesystem error that normally indicates the file is physically damaged. That could be the same underlying problem that kept FCP from backing up that library. If it can't read the library because files within the library are physically damaged, it can't back it up.


In such cases it's best to take a deep breath, slow down and don't make it worse. A good step would be search for all existing backups of that library, then copy those to a safe location. FCP automatically backs up libraries in a compressed format that doesn't include cache, analysis or media files. If you haven't used that library in 3-4 months, the may be several good backups that FCP automatically made back then.


The default library backup location is in ~/Movies/Final Cut Backups.localized. Each of those folders is a library name. Within each folder are often several backups of the library. Each of those backups is a copy of the library at a certain point in time. Each can be opened in FCP by File>Open Library>From Backups, or you can double click on the backup library in Finder.


Before doing that, as an extra safety step, I suggest copying all of the library backups to another "known good" drive. That preserves all the current backups in case problems get worse.


If you have any especially critical FCP or non-FCP content, you might consider manually copying that to a "known good" drive, just in case.


Once that's done you could run Disk Utility First Aid on the external drives where the library was. Look closely at the output. If there are any errors, I'd take a photo of that with your iPhone, just in case it's needed later.


First Aid does not do a read/write or sector scan of the media, it only checks for the filesystem structures. So it's possible First Aid could have no errors but the media itself could have bad blocks. Normally a failed read would be logged in the macOS System Log, but that is very verbose.


A simple test is running Blackmagic Disk Speed Test on each drive. One failure mode is the drive may show very slow write performance. Some SSD drives can enter a "Flash Translation Layer (FTL) failure state," in which writes become extremely slow. Both Samsung and SanDisk Extreme Portable and Extreme Pro drives have experienced this. I don't know about the PCIe versions.


Any media used with FCP should ideally be formatted APFS, both SSD and mechanical drives. The previous advice about APFS being only for SSD is out of date.

6 replies
Question marked as Top-ranking reply

Jan 2, 2026 2:53 PM in response to tontoe

If you get an error trying to copy the library via Finder to a larger SSD, that has nothing to do with FCP. That is a filesystem error that normally indicates the file is physically damaged. That could be the same underlying problem that kept FCP from backing up that library. If it can't read the library because files within the library are physically damaged, it can't back it up.


In such cases it's best to take a deep breath, slow down and don't make it worse. A good step would be search for all existing backups of that library, then copy those to a safe location. FCP automatically backs up libraries in a compressed format that doesn't include cache, analysis or media files. If you haven't used that library in 3-4 months, the may be several good backups that FCP automatically made back then.


The default library backup location is in ~/Movies/Final Cut Backups.localized. Each of those folders is a library name. Within each folder are often several backups of the library. Each of those backups is a copy of the library at a certain point in time. Each can be opened in FCP by File>Open Library>From Backups, or you can double click on the backup library in Finder.


Before doing that, as an extra safety step, I suggest copying all of the library backups to another "known good" drive. That preserves all the current backups in case problems get worse.


If you have any especially critical FCP or non-FCP content, you might consider manually copying that to a "known good" drive, just in case.


Once that's done you could run Disk Utility First Aid on the external drives where the library was. Look closely at the output. If there are any errors, I'd take a photo of that with your iPhone, just in case it's needed later.


First Aid does not do a read/write or sector scan of the media, it only checks for the filesystem structures. So it's possible First Aid could have no errors but the media itself could have bad blocks. Normally a failed read would be logged in the macOS System Log, but that is very verbose.


A simple test is running Blackmagic Disk Speed Test on each drive. One failure mode is the drive may show very slow write performance. Some SSD drives can enter a "Flash Translation Layer (FTL) failure state," in which writes become extremely slow. Both Samsung and SanDisk Extreme Portable and Extreme Pro drives have experienced this. I don't know about the PCIe versions.


Any media used with FCP should ideally be formatted APFS, both SSD and mechanical drives. The previous advice about APFS being only for SSD is out of date.

Jan 2, 2026 6:58 AM in response to Tom Wolsky

Thank you 🙏


The drives are [as I remember] Sandisk SSDs in UGreen enclosures; the one with the problem FCP project is 1TB, the destination one 4TB. I formatted them on my MacBook Air M2 [running the current version of Sequoia].


Main reason I wanted to open the project was to reduce its size by deleting generated files [which I realise would have been best to do after I finished editing/rendering when it was last open.


I'll double check exact model/capacity/free space and report back when I get home tonight.


Thanks so much for responding so promptly!

Final Cut Pro library won't update/copy, possible corruption?

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