About
All stories
Editing

FilmCraft review roundup: a free Premiere Pro alternative?

A familiar workflow, successful small projects and some rough edges: what published reviews and Reddit users reveal about the open-source editor.

FilmCraft owl icon on a purple background

A free editor that looks familiar enough to use without relearning your working day is an attractive pitch. FilmCraft has brought that idea into the debate around Adobe alternatives. Published tests and Reddit discussions reveal why people want it to work, and why some editors are still reluctant to trust it with a deadline.

For this review roundup, we compared two authors’ hands-on reports with a discussion among FilmCraft users. The tests cover different October builds; their results should not be read as a benchmark of every subsequent release.

What FilmCraft actually offers

FilmCraft is the video editor in the ArtCraft family, rather than a replacement for the whole Adobe suite. Its official repository describes a free, open-source application written in Rust, available on Windows, macOS and Linux, with a browser version. The project uses MIT and Apache 2.0 licensing.

The same documentation calls it alpha software. It lists native Premiere project import among the gaps: a .prproj file cannot simply be opened, although sequence interchange through FCP7 XML, AAF or OTIO is offered. Third-party VST3, Audio Units and OpenFX plugin hosting is also absent. Those details matter more to a potential switch than a familiar arrangement of panels.

A familiar timeline, a slower export

Scott Simmons put FilmCraft through a corporate editing project for ProVideo Coalition. His October 23 review, updated to identify the tested version as 0.12.0, found that basic importing, editing, effects, text and output were possible. Bringing an existing edit across was less straightforward: XML and AAF produced a timeline, but relinking failed. Another interchange export brought the media across successfully.

His most concrete comparison was a 2-minute-30-second timeline exported as high-quality 1080p H.264. FilmCraft took 2 minutes 20 seconds; Premiere took 11 seconds. That is one reviewer’s project and setup, not a universal speed ratio. It does, however, show why an editor can welcome the interface and still hesitate over delivery.

An earlier build struggled with the basics

In an October 10 TechRadar review, Steve Paris tested FilmCraft 0.2.1. He liked the quick launch and familiar interface, and could create a project, import footage and assemble multiple layers. But dragging a clip edge to trim it did not work in his test, and playback of his footage produced static instead of usable audio.

Paris deliberately used an older Mac, while noting that Adobe’s applications performed better on that same machine. His experience documents a rough early build. It does not establish that the same faults remain in today’s download, or that every media format behaves the same way.

Reddit’s strongest argument is muscle memory

There are successful edits among the user reports. In “First film craft project completed” on r/ArtCraftAI, u/Surfella described spending about an hour on a Windows 10 project: importing video, editing it, separating and replacing audio, syncing the result and trying export settings. They were happy with the finished video, while explicitly describing the project as simple.

Another commenter, u/sandfrayed, questioned the need for FilmCraft when DaVinci Resolve already exists. Surfella’s answer was about familiarity:

“When you are used to the premiere workflow, it just makes sense.”

u/Surfella, r/ArtCraftAI

That exchange captures an appeal that a feature comparison can miss: people have invested years in an editing workflow. It is one small discussion, however, not evidence that most editors are switching.

The test is finishing your own project

Our reading of these accounts is that FilmCraft has earned a closer look, while the case for moving an established production workflow remains unproven. A successful short edit and a difficult interchange test can both be true. They ask different things of the software.

For a curious Premiere user, a useful trial would be a duplicate of a completed project: import the original media, rebuild a representative section, save and reopen it, then export the actual delivery format. That would answer the question the launch excitement cannot: whether FilmCraft can finish the kind of work you do.