H.264 workflow in Final Cut Pro
H.264 is the codec almost every prosumer camera writes by default. Sony A7S III, Canon R5, DJI Mavic, GoPro Hero, iPhone 17 Pro: they all ship H.264 or HEVC variants. Final Cut Pro reads H.264 natively on Apple Silicon, but a long-form documentary cut from 40 hours of source still puts pressure on the SSD. Sanbila stores the H.264 originals on Cloudflare R2 and uses Final Cut's optimized media or a Sanbila ProRes Proxy on the local SSD to keep the magnetic timeline responsive.
Why H.264 punishes long-form Final Cut edits
H.264 is small on disk per minute, around 30 to 60 GB per hour at 4K, which sounds friendly until you remember that documentary editors collect hundreds of hours. Forty hours of A7S III footage land at about two terabytes. Final Cut Pro decodes H.264 with hardware acceleration on Apple Silicon, but it still benchmarks slower than ProRes for scrubbing, J-K-L navigation and skimmer responsiveness. The Final Cut answer is "create optimized media", which transcodes everything to ProRes 422 and roughly triples the footprint. On a 1 TB MacBook Pro you run out of disk before the rough cut is done.
Originals in R2, ProRes Proxy locally for Final Cut
Sanbila uploads the H.264 files straight from the SD card, the CFexpress reader or the drone download. The Sanbila virtual folder mounts inside the Final Cut Pro library through symlinks that Final Cut reads as native clips. The Sanbila preset for Final Cut is 1080p ProRes Proxy, which is the codec Final Cut was designed around: skimmer is instant, magnetic timeline edits stay responsive, and the ProRes proxy plays back full rate on a base M3 MacBook. Final Cut's built-in proxy mode toggles cleanly, and the H.264 originals stay on R2 until you need them for export.
H.264 (.mp4, .mov) · Final Cut Pro
For H.264 in Final Cut Pro, the recommended Sanbila preset is 1080p ProRes Proxy in .mov. Final Cut treats ProRes as a first-class citizen, so skimmer, scrub and trim are instant. The proxy sits around 30 GB per hour, which fits comfortably on a 1 TB MacBook for a documentary cut. For a YouTube creator working on a shorter piece, the 720p ProRes Proxy variant cuts the footprint in half and stays smooth on an entry-level M3.
Export to ProRes 422 master from the H.264 source
Final Cut Pro exports an FCPXML at any point. Sanbila reads the FCPXML and identifies every clip that lives on the timeline. Smart Relink switches those clips to stream mode, the WebDAV volume mounts on macOS as a Sanbila-{projectId} volume, and Final Cut shifts from the local ProRes proxy to the H.264 originals served over WebDAV. The export to a ProRes 422 master reads the H.264 source bytes from R2 on demand, decodes through the Apple Silicon hardware path, and writes the final ProRes file locally. No giant H.264 cache ever lands on the SSD.
Five steps from the SD card to ProRes delivery
- 1
Connect the SD card, the CFexpress reader or the drone offload drive. Sanbila scans, hashes every .mp4 or .mov, and uploads to R2 in parallel with multipart upload above 100 MB.
- 2
Open the Sanbila virtual folder for the project. The 1080p ProRes Proxy files are linked through symlinks that Final Cut Pro treats as clips in a regular event.
- 3
Cut, fine-cut and lock in Final Cut Pro. The magnetic timeline stays responsive on a MacBook Pro M3 even with 100 plus clips per minute of finished cut.
- 4
Export an FCPXML and run Sanbila Smart Relink. Used clips switch to stream mode, the WebDAV volume mounts as Sanbila-{projectId} on macOS, and Final Cut sees the H.264 originals at full resolution.
- 5
Export to ProRes 422 from Final Cut. The export decodes H.264 from R2 over WebDAV on Apple Silicon hardware and writes the master locally. Original H.264 never lands permanently on the SSD.
Sanbila by the numbers
Real specs from the live Sanbila product, not marketing claims.
Common questions about H.264 in Final Cut Pro
Does Final Cut Pro see the Sanbila symlinks as importable clips?
Yes. Final Cut Pro reads symlinks as regular files inside the event. The Sanbila virtual folder generates symlinks pointing at the local ProRes Proxy by default, and the import is identical to importing a folder of clips from any drive.
How does Sanbila handle HEVC variants like Apple ProRes HEVC from iPhone 17 Pro?
HEVC files upload to R2 in the same flow as H.264. Apple Silicon decodes HEVC in hardware just like H.264. The Sanbila 1080p ProRes Proxy stays the recommended local format because it sidesteps the heavier HEVC decoding on the timeline.
Can two Final Cut Pro editors share a Sanbila project?
Yes on the Studio plan. Both editors log into Sanbila on their own Mac and open the same virtual folder. Each generates their own ProRes Proxy locally. Final Cut libraries stay per-editor because Final Cut does not support shared libraries with concurrent writes, but the media is shared through Sanbila.
Does the ProRes 422 master export match what Final Cut would produce from local H.264?
Yes. Final Cut decodes the same H.264 bytes from R2 over WebDAV that it would decode locally. The export to ProRes 422 is bit-for-bit identical to a master produced from a local copy of the H.264, plus the network read time absorbed by the block-level cache.
How big is the WebDAV mount for a 40-hour documentary edit?
The WebDAV mount only exposes the clips that ended up on the locked timeline, identified through the FCPXML. A finished cut that uses 200 unique clips from a 40-hour project ends up mounting roughly 30 to 60 GB of source H.264, which streams cleanly from R2 on a standard broadband connection.
Related workflows
ProRes 422 workflow in Premiere Pro
ProRes 422 is the codec broadcast and corporate teams pick when they need a clean intermediate without going RAW. A Sony FX6 in UHD at 25p writes around 250 GB per hour at ProRes 422 HQ. Premiere Pro reads ProRes natively on macOS and Windows, but the disk fills fast. Sanbila stores the originals on Cloudflare R2, generates a lighter proxy on your machine and lets Premiere stream the ProRes back for the final export.
Blackmagic RAW workflow in DaVinci Resolve
BRAW is the codec DaVinci Resolve grew up with. Decoding is fast, debayer is clean, and the metadata roundtrip is the most mature in the industry. The catch is the disk. A URSA Mini Pro 12K at 8:1 still writes around 250 GB per hour, and the Pocket 6K stack on a documentary shoot fills a 2 TB drive in a week. Sanbila keeps the BRAW originals on Cloudflare R2 and serves a 1080p ProRes Proxy on your machine so Resolve plays back instantly, then streams the BRAW over WebDAV when you grade.
RED RAW (R3D) editing workflow in DaVinci Resolve
RED Komodo, V-Raptor and V-Raptor XL produce R3D files at 300 to 700 GB per hour in 6K and 8K. DaVinci Resolve handles R3D natively, but the bandwidth still bottlenecks at the disk. Sanbila keeps the originals in cloud storage and lets Resolve open lightweight proxies during the offline cut, then switches each clip back to the original through a WebDAV mount when the colorist needs the raw debayer.