FilmCraft vs Premiere Pro: An Open-Source Video Editor With Its Own Codecs

FilmCraft vs Premiere Pro compares a free non-linear editor built from scratch in Rust against the editor many professionals already use. FilmCraft's pitch is unusually specific: the same panels, workspaces, tools and shortcuts as Premiere, on top of video and audio codecs the team wrote themselves. Its maintainers also publish a frank estimate of how far along it is, and that estimate frames the whole comparison.

The short version

Premiere Pro is the working choice when you need broad codec support, plug-ins, hardware-accelerated performance on large footage and a team that already knows it. FilmCraft is worth testing on small projects if you want a Premiere-style editor with a permissive licence and no subscription. The README gives two numbers, both self-assessed: about 87 percent of Premiere's menu items, effects, transitions and formats exist, and the team's honest estimate of readiness for real work is about 50 to 60 percent.

What FilmCraft includes

FilmCraft is a Cargo workspace written in Rust. It runs natively on macOS, Windows and Linux, and in the browser through WebAssembly. The licence is MIT or Apache-2.0 at your option.

Editing. Source and Program monitors, bins, a multi-track timeline with patch and target buttons, sync locks and linked selection. Three-point editing with insert and overwrite, lift and extract, and the trim set: ripple, roll, slip, slide, rate stretch and razor. Time is computed on integer ticks, so 23.976, 29.97 drop-frame and 59.94 are exact.

Workspaces and keys. Editing, Assembly, Color, Effects and Audio workspaces, dockable panels, and a keyboard-shortcut editor with presets that mimic FilmCraft, Premiere Pro, Final Cut Pro and Avid layouts.

Colour. A Lumetri-style panel with basic correction, creative looks, RGB curves plus hue and saturation curves, shadow, midtone and highlight wheels, HSL secondary keying and a vignette.

Effects and motion. The README lists Premiere's full Video Effects bin and about thirty transitions, motion and opacity on every clip, 26 blend modes and Bezier keyframes with value and velocity graphs, composited on the GPU through wgpu in linear light.

Audio. Loudness meters to the ITU-R BS.1770 and EBU R128 standards, a track mixer and clip mixer, five insert slots per track, sends, submixes and automation modes (Read, Latch, Touch and Write), plus parametric EQ, dynamics, a limiter, reverb, DeNoise and DeHummer.

Titles and captions. A text engine with OpenType shaping and bidirectional text, shape and pen tools, caption tracks in several formats and import and export for SRT, WebVTT and SCC.

The codec decision

The most unusual claim is that FilmCraft contains no FFmpeg. Its H.264, HEVC and ProRes decoders, its AAC and Opus audio, and its container code are written in Rust from the public ITU-T, ISO and IETF specifications. The README says they are tested frame by frame against FFmpeg used as an outside reference.

That is a legitimate engineering choice, and it also explains the gaps. Camera RAW is not supported yet, HEVC and AV1 export are not available, E-AC-3 is missing, and the README says phone and camera files from the real world are less tested than conformance streams. If your footage comes from many cameras, that is the first thing to test.

Interchange with other editors

FilmCraft reads and writes Final Cut Pro 7 XML, which Premiere and DaVinci Resolve also exchange, FCPXML and OpenTimelineIO. That is useful for moving an edit into Resolve for grading or sending a timeline to a collaborator. It does not mean Premiere project files open directly.

Reliability and workflow details

Editors are judged on what happens at 2 a.m. before a deadline, and the README gives several concrete details here. Saves are atomic, auto-save keeps a rolling set of versions, and a crash-recovery journal written about a second after each edit restores unsaved changes after a crash or power cut. History is unlimited, with a History panel, and keyboard shortcuts can be remapped, including presets that imitate Final Cut Pro and Avid.

The README also describes render previews: a render bar marks segments green, yellow or red, previews are cached by content, and an edit only invalidates the segments it touches, so undo brings the green back. Export runs as a background job with progress and cancel, which lets you keep cutting while a render finishes.

How the project is built

FilmCraft is a layered Cargo workspace, with the lower layers handling time, media and codecs and the upper layers handling the editor and interface. The same engine runs on the desktop and in the browser, and there is a web package attached to each release. A CPU path renders the same frames as the GPU path and the two are tested against each other, which gives the project a built-in way to catch rendering regressions.

The README links a roadmap file with milestones and an honest assessment dated 5 October 2026, and an AGENTS file that sets rules for contributors about assets, clean-room practice and licences. It also states that FilmCraft contains no Adobe code, icons, presets or LUTs and no GPL or LGPL code, and that every icon is drawn in code. For a company thinking about adopting open-source software, that licence hygiene is a point in its favour.

A practical test plan

A fair trial of FilmCraft takes an afternoon and uses your own material:

1. Import a representative clip from each camera you use, and note which ones fail to decode or look wrong.
2. Cut a two-minute sequence using your normal moves, including trims, speed changes, a title and a caption track.
3. Grade the sequence with the Lumetri-style panel and compare it with your usual result.
4. Export H.264 and check the file in the player your audience uses.
5. Move the timeline to another editor through Final Cut Pro XML or OpenTimelineIO and see what survives.
6. Save, force-quit the app and reopen to confirm that recovery works for you.

If steps 1 and 4 pass on your hardware, FilmCraft is worth following more closely. If step 1 fails because your camera format is not yet supported, wait for a later release.

Comparison table

The table pairs the two with the established open-source editors and with DaVinci Resolve, whose pricing model differs from Premiere's.

Where FilmCraft still falls short

The README lists its biggest gaps in its own words, and they are the practical limits to plan around:

• Speed on big footage. Hardware decoding works on macOS and Windows but not yet on Linux. Colour work, keys and export rendering still run on the CPU.
• No plug-ins. VST3, Audio Units and OpenFX are not hosted.
• Delivery codecs. H.264 only.
• Platform testing. Windows and Linux get far less testing than macOS.
• AI features. Few so far, with speech to text optional and off by default.

Premiere Pro answers most of these with a mature plug-in market, wide codec support and hardware paths on common systems. It is also a subscription product with no self-hosted edition, which matters if ownership of the tool is the reason you are looking.

Who should try which

Try FilmCraft if you cut on macOS, edit short projects, value an open licence, or want to contribute bug reports with real footage, which the maintainers say is the most useful thing they can receive.

Stay with Premiere Pro for client work, mixed-camera projects and anything that depends on third-party effects.

Consider Kdenlive or Shotcut if you want an open-source editor that is dependable now, and look at EffectCraft, from the same team, if motion graphics are the goal. The full family is covered in the ArtCraft Crafting Apps guide, and the video editing category lists more tools.