Every render, every proxy, every old auto-backup builds up inside your Final Cut libraries — and Final Cut never cleans any of it. Vacuum finds the gigabytes you'll never use again, and never touches your original footage.
If you edit in Final Cut Pro, your disk fills up faster than your project does. Here's what most editors run into.
Every .fcpbundle is a hidden folder full of files Final Cut created for itself. Most of them you'll never need again.
No setup. No login. No "indexing your drives". Drag, see, decide.
Vacuum is paranoid about your footage on purpose. The rules below aren't suggestions — they're built into the app.
Generic disk cleaners don't understand the inside of an .fcpbundle. That's where most of the risk and most of the space actually lives.
Low on disk space — wondering where your GBs (or TBs) went?
It's almost certainly hiding inside your Final Cut Pro libraries. Every edit session quietly stacks up render files, optimized media, proxies, flow-analysis data and auto-backups — and none of it is cleaned up on its own. Use Vacuum to reclaim that space.
| Capability | Vacuum for FCP | Generic cleaners | Other FCP tools |
|---|---|---|---|
| Understands FCP bundle structure | ✓Per-category breakdown inside every .fcpbundle | ✗Opaque folders | ~Often unmaintained |
| Original Media protection | ✓Structurally excluded — two independent checks | ✗User judgement | ~Runtime check only |
| Multi-gate safety pipeline | ✓Refuses to touch when FCP is running, snapshot before any move, one-click recovery | ✗Single-step delete | ~No metadata snapshot |
| Non-destructive deletion | ✓Everything goes to the macOS Trash | ~Some hard-delete | ~Varies |
| Full undo history | ✓Every operation logged; restore in one click | ✗None | ✗Rarely offered |
| Auto-recovery after interrupted cleanup | ✓Snapshot detected on next launch | ✗None | ✗None |
| Duplicate detection | ✓Same name, same structure, optional content check | ~File-level only | ~Name-based |
| Orphan backup detection | ✓Matches by libraryID, tracks offline volumes | ✗N/A | ✗N/A |
| Native app, no telemetry | ✓SwiftUI, sandboxed, nothing leaves your Mac | ~Often phones home | ✓Usually local |
| Fully localized | ✓EN, NL, DE, FR, ES — app + Help Book | ~EN only common | ~EN only common |
| Guided first-run tour | ✓Interactive spotlight walkthrough | ✗None | ✗None |
Comparison reflects common behaviour in the category. Individual tools may differ.
Free up 100 GB and you've already saved more in cloud storage than the app costs. At 1 TB, you've saved the price of an external SSD.
No. Original Media is blacklisted at two independent levels in the code — Vacuum cannot delete it, by accident or otherwise. Your project files (the editorial decisions, timelines, events) are also untouched. Vacuum only removes files Final Cut generates: renders, proxies, optimized copies, analysis caches, old backups. These will be regenerated automatically by FCP when you reopen these libraries.
Files go to the macOS Trash, not into a void. Drag them back from the Trash, or use Vacuum's one-click Undo. As long as you haven't emptied the Trash, anything is recoverable.
Depends entirely on your projects, but most editors free hundreds of GBs on the first scan. Heavy ProRes or optimized-media workflows often see 1 TB or more across older libraries. Vacuum shows you the numbers per library before you delete anything.
Yes — with one rule: Final Cut Pro must be closed. Vacuum refuses to run otherwise. The render files and proxies you delete will simply be regenerated next time you need them. Your edit decisions are not affected.
Most of the older Final Cut library managers haven't been meaningfully updated in years and quietly break on modern macOS releases. Vacuum is actively maintained, fully sandboxed for the Mac App Store, localized in five languages, and built for current Final Cut workflows. You pay once — no subscription — and that's also what funds keeping it working on every macOS release.
macOS 14 (Sonoma) or later. Apple Silicon and Intel both supported, native Swift, no Rosetta. Sandboxed: you explicitly grant access to the drives or folders you want scanned, and nothing leaves your Mac.
No. Drag a folder, look at the breakdown, click "Trash". That's it. There's no command line, no settings to configure on first run, no opaque defaults to debate.