FilmCraft: what it does and what to check first
Putting two clips together sounds simple until the title disappears too quickly, a cut leaves a black gap or the sound arrives late.
Last updated
Menus and supported features can change. Compare the source-check date below with your current app version.

Putting two clips together sounds simple until the title disappears too quickly, a cut leaves a black gap or the sound arrives late. FilmCraft is a timeline video editor. For a first exercise, I would use two short clips and one title rather than transfer a large Premiere project. The useful question is whether the source footage, edit and exported video all agree.
The checked material describes alpha / in development. I have read the public documentation; I have not installed and run this app for a hands-on review.
A look at the screen
| Where to look | What it does |
|---|---|
| Source and Program monitors | Distinguish the selected source range from the final sequence. |
| Timeline | Adjust clip order, length and audio position. |
| Export | Check resolution, frame rate, range and audio output. |
What the documentation describes
- Use a Source monitor for the original media and a Program monitor for the edited sequence, with a multitrack timeline.
- The documented workflow includes trimming, colour adjustments, keyframes, titles, captions and audio mixing.
- Export H.264 video and explore the documented command-based control paths.
What interests me beside Premiere
The documentation describes FCP7 XML, AAF and OTIO exchange routes. These carry editing information between tools; they are not the same as opening a Premiere .prproj directly. I would evaluate a new edit and an imported edit separately, because titles and effects can be lost even when the cuts and tracks transfer.
The developer describes free, open-source, local work. Open source means the code is available to inspect. I have not measured a speed or total-cost advantage. For Premiere, check the official product and plan information for the terms that apply in your region.
The limitation I would check first
The README says .prproj files cannot be opened directly and VST3, Audio Units and OpenFX plug-in hosting is absent. Some rendering work runs on the CPU, and the range of real camera and phone media tested is limited. I have not measured performance on my computer. Codec handling and audio/video sync matter more here than the length of the feature list.
A small first task
For the first exercise, let’s edit two clips into a 15-second promotional video. Prepare: Two short MP4 clips you have permission to use, a short title and optional audio. Use the same original clips when comparing editors.
Check the official app page and release downloads for a build matching your operating system and CPU. If there is no suitable installer or the app does not start, read Get started/Quick start and known issues in the official README. Record the app version and OS when you try the task.
The separate tutorial gives the menu sequence and an expected result. It is a documentation-based exercise, not a claim that I completed it. AI-assisted development, an app’s built-in AI features and an agent operating existing functions need to be distinguished when judging an automation claim.
Keep the working file and the delivery file
Keep the editing project together with its original video and audio, and save the delivered MP4 separately. An MP4 is the finished playback result, not an editable timeline. Reopen the project and change a cut or title, then compare the resulting duration with the first export. A preview that plays correctly does not guarantee that the encoded file has the same timing.
If the result differs
If a phone clip previews or exports incorrectly, first play the original outside the editor. Record the codec, frame rate and FilmCraft version. Check whether the issue affects one clip or every clip. Inspect sequence and export start/end points and change one setting at a time; a replacement clip is a new input, not proof that the original worked.
What I would verify before a bigger job
- Compare cut positions, duration and voice sync using the same two clips.
- Record import, preview and export times plus errors on the same PC.
- Inspect missing titles and effects in actual XML/AAF/OTIO interchange.
A new short video is a sensible first task. A project built around .prproj files or third-party effects is a different migration problem. A 15-second export also says nothing by itself about long edits, every phone codec or the speed of CPU rendering.
Judge the edit’s communication as well as its length: the first scene needs reading time, the second needs a clear continuation, and music needs an intentional starting point. For a fair performance comparison, record importing, previewing and exporting on the same PC, including crashes and repair time.
Introduction · Task tutorial · Comparison: documented differences
Sources & further reading
- https://getartcraft.com/apps/filmcraft
- https://github.com/storytold/filmcraft/blob/main/README.md
- https://www.adobe.com/products/premiere.html
- https://github.com/storytold/filmcraft/blob/cee1feb185e675a108f78067f71ad86a640ace3d/README.md
- https://github.com/storytold/filmcraft/blob/cee1feb185e675a108f78067f71ad86a640ace3d/crates/ui-egui/src/menus.rs
- https://github.com/storytold/filmcraft/blob/cee1feb185e675a108f78067f71ad86a640ace3d/docs/keyboard.md