Final Cut Pro SSD full?

Final Cut stores generated media inside each Library bundle, next to the originals: render files, optimized media, proxy media and analysis files. A few short projects and a 1 TB MacBook SSD hits 90 percent, and a forum favourite is a 250 GB Library trimmed to around 44 GB just by deleting generated files. The quick win is to select the Library in the sidebar and choose File then Delete Generated Library Files, ticking render files plus optimized and proxy media, since those rebuild on demand. Then stop it coming back: turn off Background Render in Final Cut Pro, Settings, Playback, and leave the transcode options unchecked on import. If the Library still will not fit, Apple's own advice is to move it to an APFS drive, after a backup.

None of that moves the camera originals, though, and on a long-form project they are the real weight. You are back to a bloated Library and a Mac that cannot back up cleanly to Time Machine.

Sanbila keeps the originals out of the Library. On import your camera files upload to cloud storage with a redundant backup copy, the ProRes Proxy is encoded on the Sanbila cloud, and only the light proxy sits in a Virtual Folder that Final Cut reads as external media, outside the bundle. A 4 TB rush set becomes a couple of hundred gigabytes of proxy on disk, so the Library stays small and Time Machine backs it up quickly.

The local proxy cache has a size limit you set, from 5 GB to 500 GB, and least-recently-used eviction removes the oldest proxies first, never an original. Pin the project you are cutting so it is excluded, and unpin at delivery. For the finish, export an FCPXML and Smart Relink switches the timeline clips back to the full resolution originals streamed from the cloud via a local mount, and you set the View back to Original before sharing. A cleared proxy re-streams on demand, so nothing you free up is lost.