CoreTrim

Everything a publication needs to write about or review CoreTrim. Take what you need; no permission or attribution request is attached to any of it.

What's in here

The one-paragraph version

CoreTrim is a Workflow Extension that exports a Final Cut Pro project with only the media the timeline actually uses, trimmed by stream copy with no re-encoding, and relinked so it imports back into Final Cut identically. Every source must prove it can be trimmed flawlessly before CoreTrim commits to a method, and the finished archive — media and project file alike — is verified again before it ships. Originals are never touched, anything that can't be proven safe is copied in full, and every export includes a report of exactly what was done. Multicam projects can keep all angles or be checkerboarded down to the shots in the cut.

Requesting a review copy

Email the press contact and you'll get a Mac App Store promo code, usually the same day. If you'd like a walkthrough, a specific workflow demonstrated, or an interview, just ask.

Reviewing it — what to try

CoreTrim installs as a Final Cut Pro extension, so there's no separate app to launch. Installing it registers the extension automatically; open Final Cut Pro and choose Window → Extensions → CoreTrim.

Then drag a project from the browser into the CoreTrim panel. Good things to put it through:

• A project with more media than it uses — the headline case. Watch the projected savings before you commit to anything.
• A multicam project — try it both ways: all angles preserved for future re-editing, or checkerboarded down to just the shots in the cut.
• A mixed-format timeline — ProRes, H.264/HEVC, MXF, stills, music. Note which files CoreTrim decides it can't trim safely and copies in full instead, and that it tells you why in plain English. CoreTrim-Supported-Formats.html lists exactly which formats trim and which are copied.
• The round trip — import the exported project back into Final Cut Pro and compare it against the original. Cuts, sync, effects, markers, speed changes and multicam angles should be indistinguishable.
• The report — every export writes an HTML report of what was trimmed, copied, or skipped, with per-file sizes and reasons.

Screenshots

Click any image for the full-resolution PNG, or use the download link under it. The app icon is here at 1024 × 1024 with transparency. All free to use, no attribution requested.

A note on the numbers: CoreTrim's panel shows a projected size and saving — the estimate you weigh before committing to an export, marked with a ~. The report states the actual result once the export has run. That's why the figure in the app screenshots (179.1 MB, 75%) differs slightly from the report (206.4 MB, 72%): they're the same project at two different moments, not two different claims.

Additional screenshots, higher resolutions, or a short screen recording are available on request.

The sample report

CoreTrim-Sample-Report.html is a genuine report from the project in the screenshots — not an excerpt or a mock-up. Every export writes one.

It's the most direct answer to the questions a reviewer tends to ask: what happens to files that can't be trimmed safely, and how would an editor know the project survived intact. The report lists every source with the decision CoreTrim made and the reason in plain English, the per-file sizes before and after, which Motion templates were copied into the export, and the counts that matter — segments created, rejected, failed. In this run: 54 files, 60 segments, 0 rejected, 0 failed, 736.8 MB down to 206.4 MB.

Facts you may need

Usage terms

The app name, icon, screenshots, boilerplate, and quote in this kit may be reproduced freely in coverage of CoreTrim, in print or online, without asking first. The only thing we ask is that screenshots aren't altered in ways that misrepresent what the app does.