You found PlumePack, you installed the free version, you pointed it at your project, and it stopped you at sixty gigabytes. If your project is over an hour of any modern camera codec, you were always going to hit that wall. The free tier is a tasting menu. It's the right move on PlumePack's end and a frustrating moment on yours.
Before you reach for the credit card, though, the more useful question is: which problem are you actually trying to solve? The answer changes the right next step.
What 60 GB actually means
To put the cap in perspective: a single hour of ProRes 422 HQ at UHD is around 600 GB. An hour of BRAW Q5 is around 100 GB. An hour of compressed H.264 from a mirrorless camera is more like 25-30 GB. So PlumePack's free tier comfortably handles short-form social cuts and B-roll trims. Anything that resembles a real corporate, wedding, doc, or commercial project will overshoot the cap on day one of the shoot.
That isn't a knock on PlumePack. The 60 GB limit lets the free tier prove the engine works on your media before you pay $79 for the PRO unlock. It's the upgrade trigger built into the product.
Step one: figure out which job you're doing
Editors hit PlumePack for one of two reasons. The right next step depends on which one is yours.
Job A — "I want to bundle this finished project for archive or handoff"
You're about to ship the project to a colorist, an audio post house, or cold storage. You want one self-contained folder containing only the media that the timeline used, ideally with handles, ideally without re-encoding. PlumePack was built for this. The 60 GB limit isn't a flaw — it's the sample size before the real engine.
Right next step: upgrade to PlumePack PRO ($79). The lossless trim engine across ProRes, BRAW, R3D, H.264/265, DNxHD, and ARRIRAW is genuinely good. There isn't a free tool that matches it. Buy the unlock and ship your project.
Job B — "My drive is full and I want to clean it up"
This is the more common case, and the one PlumePack is the wrong tool for. If you reached for it because you saw "consolidate" or "remove unused" and figured it would tell you what was safe to delete from your drive, the 60 GB limit isn't even your real problem.
PlumePack works on one project at a time. It can't tell you whether a clip in this project is reused in another project on the same drive. Run it on twelve projects in turn and you're still missing every shared B-roll asset, every recurring-client asset, every stock plate that lives in a shared folder. The cross-project problem is the shape of the actual job, and per-project consolidation is structurally blind to it.
Right next step: a drive-wide audit. Clip Sweeper indexes every Premiere project on a drive at once and only flags media that no timeline anywhere depends on. It's a one-time App Store purchase with no per-project size limit, which is the relevant cap when "the drive" is the unit of work and not "this one project."
How to tell which job you're doing
If you're not sure which bucket you're in, the question to ask yourself is: "Am I trying to get one project out of my way, or am I trying to make my whole drive smaller?"
- One project out of the way — wedding, commercial, episode, deliverable that has shipped — that's a PlumePack job. Buy the unlock or use the free tier if it fits.
- Whole drive smaller — recurring backlog, "I should have cleaned this up six months ago," budget pressure to not buy another 20 TB drive — that's not a PlumePack job. PlumePack one project at a time will quietly produce wrong answers because it can't see what other projects share.
The both-tools answer
Most working editors will end up using both. Clip Sweeper on a regular cadence — monthly, end of quarter, before a fresh shoot — to keep the drive lean and to find projects that are safe to fully archive. Then PlumePack at the moment of archive, to bundle that project into a clean self-contained folder for cold storage, vendor handoff, or final delivery.
If you want the two-tool comparison side-by-side with no marketing varnish, the PlumePack vs Clip Sweeper page is the honest version.
What not to do
Don't run PlumePack twelve times on twelve projects and assume the leftover files are deletable. They probably aren't, because PlumePack only knows what each project used in isolation. The math on shared assets is wrong by definition at that scope.
Don't manually right-click "Remove Unused" in each project either. Same blind spot, with worse safeguards.
Don't buy a bigger drive without doing the audit first. Most editors find 30-60% reclaimable on a working drive that feels full. That's a $400 drive purchase deferred for a few clicks of audit work.
The summary
PlumePack's 60 GB free tier is a real wall, and it's also a useful filter. It tells you whether the tool fits the job you're doing. If you're archiving one project, $79 is well-spent. If you're trying to fix a drive that's filling up, the cap is a hint that you're on the wrong page — and the right tool is one that sees across all your projects at once.