So you've landed on the SpliceKit repo, scrolled through a wall of technical docs, and thought "...what am I looking at?" Totally fair. This page is for you.
SpliceKit lets you control Final Cut Pro with text commands and AI instead of clicking buttons and dragging things around. It's also a plugin framework -- so you can build addons and plugins to do all kinds of awesome things that you couldn't normally do with FCP plugins.
Final Cut Pro is a powerful video editor, but everything in it is manual. You click, drag, scrub, hunt through menus. That's fine for some tasks, but painful for others:
- Removing silences from an hour-long interview? That's hundreds of manual cuts.
- Adding markers at every beat of a song? Click... click... click...
- Applying the same color grade to 50 clips? Hope you like copy-paste.
SpliceKit is really a collection of plugins that already adds a ton of quality-of-life features to FCP out of the box, plus an AI framework and plugin system that makes it easy to add even more.
Here's some of what's already built in:
- Silence Removal -- automatically detects and removes dead air from interviews and podcasts
- Transcript Editor -- transcribes your footage, shows you the words, and lets you edit your video by editing the text. Delete a sentence? The video gets cut too. Drag words around? The clips move to match.
- Command Palette (Cmd+Shift+P) -- search and run any editing command by typing, instead of hunting through menus
- Scene Detection -- automatically finds every cut/scene change in your footage
- Beat Detection -- finds beats in music so you can sync edits to the rhythm
- Batch Export -- export every clip on your timeline individually, with all effects baked in
- Social Media Captions -- auto-generate word-by-word animated captions (TikTok/Reels style)
- AI Editing -- describe what you want in plain English and let an AI assistant do the work
And because SpliceKit is a plugin framework, new features get added all the time. You can even create your own plugins with the help of AI -- describe what you want a plugin to do, and Claude can help you build it.
Here's the non-technical version:
-
SpliceKit patches your copy of Final Cut Pro. It makes a separate copy of FCP in your home folder and adds a small plugin (a "dylib") to it. Your original FCP stays untouched.
-
When you launch the patched FCP, SpliceKit wakes up inside it. It can now see and control everything FCP does -- the timeline, your clips, effects, playback, all of it.
-
You talk to SpliceKit through text. There are a few ways:
- A Command Palette inside FCP (press Cmd+Shift+P) where you type what you want
- A Transcript Panel for text-based editing
- An AI assistant (like Claude) that can run editing commands for you
- A Python scripting interface if you want to write your own automation
Think of it like this: FCP is a car with only a steering wheel and pedals. SpliceKit adds voice control and autopilot.
This is the question everyone asks, so let's break it down:
No. SpliceKit makes a copy of Final Cut Pro in ~/Applications/SpliceKit/ and patches the copy. Your original FCP from the App Store is never modified. Your libraries, projects, and media files are not changed by the patching process.
That said, SpliceKit does perform real edits when you ask it to. Just like any editing tool, you can undo (Cmd+Z) if something goes wrong, and you should keep backups of important projects.
No. SpliceKit runs entirely on your local machine. It doesn't modify Apple's servers, bypass DRM on content, or do anything online. It's the software equivalent of opening the hood of your own car and adding a turbocharger -- Apple doesn't monitor or restrict what you run locally.
Many popular Mac apps work the same way under the hood (BetterTouchTool, accessibility tools, etc.).
Yes. Reverse engineering for interoperability is explicitly protected under:
- DMCA Section 1201(f) (US law) -- you're allowed to reverse-engineer software to make it work with other programs
- EU Software Directive Article 6 -- same principle in Europe
SpliceKit is MIT licensed (open source, free to use and modify).
Being honest:
- Future FCP updates could break compatibility. When Apple updates FCP, SpliceKit may need to be re-patched. This is an inconvenience, not a danger.
- It uses internal FCP APIs that Apple doesn't document. This means some features might behave unexpectedly on edge cases. The undo button is your friend.
- It disables FCP's sandbox (the security boundary that limits what FCP can access on your system). This is required for the plugin to work. In practice, this just means the patched FCP has the same file access as any other app on your Mac.
Everyone who uses Final Cut Pro. Seriously. You don't need to be a programmer or a power user to benefit from SpliceKit. Most of the built-in features are things that every editor will appreciate:
- Casual editors -- silence removal, transcript editing, and the command palette make everyday editing faster and less tedious
- Professional editors -- batch export, scene detection, beat sync, and caption generation save hours on real projects
- Content creators -- auto-generate TikTok/Reels-style captions, quickly cut down long recordings, batch-process clips for social media
- People who want AI-assisted editing -- describe edits in plain English and let an AI handle the repetitive work for you
- Developers and tinkerers -- build your own plugins in Python, Lua, or with AI assistance. The plugin framework gives you access to everything inside FCP, so you can create tools that Apple's official plugin system doesn't support
The built-in plugins already handle the most common pain points. But if you ever think "I wish FCP could do X" -- SpliceKit probably makes it possible, and AI can help you build it even if you've never written a line of code.
- Download or clone the repo from GitHub
- Run the patcher -- the GUI patcher (
SpliceKitPatcher) is the easiest way. It handles everything in one click. - Launch the patched FCP from
~/Applications/SpliceKit/ - Try the Command Palette -- press Cmd+Shift+P and start typing
That's it. Your original FCP stays right where it is, completely unchanged.
- Check the main README for technical details
- Browse the docs folder for deep dives on specific features
- Open an issue on GitHub if something's unclear -- the community is friendly
You don't need to understand every ObjC class or JSON-RPC endpoint to use SpliceKit. Start with the Command Palette, try the Transcript Editor, and explore from there.