Commentary#Video editing#Coding agent
FilmCraft tested: the free Premiere Pro alternative, ready for a real cut?
FilmCraft is a free, open-source Premiere Pro alternative in Rust, self-rated about 56% ready for real work at v0.6.0. Tested against Kdenlive and Shotcut.
FilmCraft is an open-source Premiere Pro alternative rebuilt from scratch in Rust by the ArtCraft team, with panels, workspaces, tools and shortcuts laid out where Premiere puts them, running on macOS, Windows, Linux and in the browser. What sets it apart is the bottom of the stack: the H.264, HEVC, ProRes and AAC codecs are the project’s own Rust code, written from the public specifications — there is no FFmpeg in the repository. As of October 12, 2026 it has 10,814 GitHub stars (3,253 when we published the seven-app comparison on October 8), and the latest release, v0.6.0, shipped on October 11. This article checks its self-rated completeness, its codec engineering and its delivery gaps to answer one concrete question: can you cut a real project with it today?
Key points
- Self-rated 86% breadth, 56% readiness. The README (re-measured 2026-10-10 against Premiere Pro 26.5.2) reports about 86% feature breadth — menus at 92%, effects at 100% under measured criteria — and about 56% “ready for real work.” Editing, trimming, multicam, color, keyframes, effects, titles, captions, mixing, codecs and export all work today.
- Time is integer, so edits never drift. Every edit is computed on 254,016,000,000 ticks per second, a base divisible by every common frame and sample rate, which makes 23.976, 29.97 drop-frame and 59.94 exact rather than approximate — a hard advantage over most open-source editors.
- Delivery formats are the ceiling. H.264 is the only software-encoded delivery format; H.265 export exists only through hardware encoders; AV1 export does not exist at all; and there is no VST3 or OpenFX plugin hosting. Projects on a deadline should not switch yet.
86% breadth, 56% readiness
The status section (re-measured 2026-10-10 against Premiere Pro 26.5.2) keeps two numbers. Feature breadth is about 86% — the share of Premiere’s menu items, effects, transitions, panels and formats that exist in FilmCraft, with menus at 92% and effects at 100% under measured criteria. “Ready for real work” is about 56%, which the project calls its honest estimate of how close FilmCraft is to replacing Premiere on real projects.
Ten days ago, in the seven-app comparison, those figures read “feature checklist about 87%; ready for real work about 50–60%.” The midpoint of the range has moved up a notch; the version marched from v0.2.1 to v0.6.0 in five days, four releases in total, and stars tripled. The same reading rule applies: these are self-assessments, the method is documented in docs/target-app-parity.md, and no third party has tested the claim systematically.
The most informative part of the status section is the project’s own list of biggest gaps, and the first one is speed on big footage. Hardware decoding works on macOS and Windows, and for H.264 and HEVC on Linux (VA-API, or NVDEC with NVIDIA’s driver); VP9 and AV1 decode in software there. Blend modes and the most common effects run on the GPU, but Lumetri, keying and export rendering still run on the CPU. Translated to experience: on a 4K timeline, preview and export waits will be longer than Premiere’s, and how much longer depends on your footage and your GPU.
The cutting room is familiar
The editing surface is designed for zero migration cost. Source and Program monitors, bins with thumbnails, a multi-track timeline with patch and target buttons, sync locks and linked selection — plus the Editing, Assembly, Color, Effects and Audio workspaces, every panel dockable wherever you want it.
Three-point editing is complete: mark In and Out in the Source monitor, then insert (,) or overwrite (.) onto the patched tracks, with Lift (;) and Extract (') taking ranges back out. The trim family is all here — ripple, roll, slip, slide, rate stretch and razor — and Trim mode selects edit points as ripple, roll or trim, nudges them a frame at a time (⌥← ⌥→, ×5 with ⇧), toggles the trim type with ⌃T, extends to the playhead with E, and ripple-trims with Q and W. The Trim Monitor shows both sides of an edit, and dynamic trimming trims live during playback: L forward, J back, K to stop and commit as a single undo step.
The time base deserves its own paragraph. Every edit is computed on integer ticks — 254,016,000,000 per second, divisible by every common frame rate and sample rate — so 23.976, 29.97 drop-frame and 59.94 are exact. Drift from mismatched frame rates on a long timeline, a classic failure mode in editors that store time as floating point, is designed out at the root.
The details professionals rely on are present: markers with colors, names and durations, exportable as review notes via Markers ▸ Export Markers as CSV; add edit (⌘K) on one or all tracks; nesting; copy, paste and paste insert; ripple delete and close gap; snapping; unlimited undo with a History panel. The Keyboard Shortcuts editor (⌥⌘K) ships a drawn keyboard, panel-specific shortcuts, conflict warnings and presets for FilmCraft, Premiere Pro, Final Cut Pro and Avid layouts. Saves are atomic, auto-save keeps a rolling set of versions, and a crash-recovery journal written about a second after each edit brings unsaved changes back after a crash or power cut.
Its own decoders
This is where FilmCraft differs from every other open-source editor. There is no FFmpeg inside: the video codecs, AAC, Opus and the containers are the project’s own Rust code, implemented from the public ITU-T, ISO and IETF specifications and tested frame by frame against ffmpeg as an external oracle. The README’s claim is bit-exactness:
| Codec | Decode | Encode | Self-reported basis |
|---|---|---|---|
| H.264 / AVC | yes | yes | decoder bit-exact on 37+ streams, 500–600 fps at 1080p; encoder with High/Main/Baseline, CABAC, B-frames, CRF/CBR/VBR/2-pass |
| HEVC / H.265 | yes | no | Main and Main 10, bit-exact on 41 streams (tiles, WPP, PCM, long-term refs), about 225 fps at 1080p |
| Apple ProRes | yes | yes | decodes 422 Proxy through 4444 XQ; export writes 422 HQ |
| VP9 | yes | no | profiles 0–3, 8/10/12-bit, 4:2:0 to 4:4:4, bit-exact on 50+ streams |
| AV1 | yes | no | Main profile, 8/10-bit 4:2:0 and monochrome, every coding tool incl. film grain, superres, spatial layers |
| DNxHD / DNxHR | yes | yes | all SMPTE ST 2019-1 CIDs (LB to 444, 8/10/12-bit) |
| AAC-LC / Opus / VP8 | yes | AAC yes | Opus range-exact on every RFC 8251 conformance vector |
| MP3 / FLAC / ALAC / Vorbis | yes | no | via the symphonia crate (MPL-2.0) for now, to be replaced |
| MP4 / MOV | yes | yes | fragmented MP4, edit lists, timecode tracks |
Also imported: MPEG-2/MPEG-1, AC-3, MP2, MXF (OP1a/OP-Atom), MPEG transport and program streams (AVCHD, broadcast, DVD), Ogg and image sequences. Not yet: AV1 export, camera RAW, E-AC-3. Hardware decoding covers macOS (VideoToolbox), Windows (Media Foundation) and H.264/HEVC on Linux (VA-API); H.264 export can opt into NVIDIA’s encoder on Windows and Linux, and H.265 export goes through NVENC (Windows) or VideoToolbox (macOS).
Bit-exactness here is measured against conformance test vectors, and the README is upfront about the gap that leaves: real-world camera and phone files are far less tested, and Windows and Linux get far less testing than macOS. On Hacker News, commenters praised how fast FilmCraft launches and, in the same threads, noted it cannot encode H.265 or AV1 — both true, and the difference between them is whether you are reading about decode or encode.
Color, effects and sound
The color workspace is a complete Lumetri-style panel in the order a colorist works: Basic Correction (temperature, tint, exposure, contrast, highlights, shadows, whites, blacks, saturation); Creative (eight built-in looks with intensity, plus faded film, sharpen and vibrance — the looks are color transforms written in code, not LUT files); Curves (an RGB editor with monotone-cubic interpolation that does not overshoot, plus hue-saturation, hue-hue, hue-luma, luma-saturation and saturation-saturation); Color Wheels for shadow, midtone and highlight, each with its own lightness control; HSL Secondary with matte viewing; and Vignette. The waveform and vectorscope are computed from the graded frame, and all grading happens in linear light at 32-bit float.
The effects side covers Premiere 26’s full Video Effects bin — 93 effects in 16 folders — plus the Legacy bin, the obsolete effects old projects use, and about 30 transitions: blurs, keys (Ultra Key, Track Matte), distortions (Corner Pin, Turbulent Displace, Warp Stabilizer), lights and glows, immersive VR effects on equirectangular footage, Posterize Time, Echo and more, from cross dissolves and dips through wipes, irises, pushes, slides, zooms, page peel and cube spin. Motion and opacity apply to every clip, with 26 blend modes. Keyframes come in linear, Bezier, auto and continuous Bezier, hold, and ease in/out; Effect Controls gives every parameter a keyframe lane under a time ruler, and animated parameters expand into value and velocity graphs with draggable influence handles, sharing a keyframe navigator with the Properties panel.
Audio is built to broadcast standards. Momentary, short-term and integrated loudness plus true peak follow ITU-R BS.1770 and EBU R128, and the project says its integrated reading matches ffmpeg’s ebur128 filter to a tenth of an LU. Clip effects run on the project’s own DSP library — parametric EQ, high/low/band-pass filters, dynamics, a true-peak limiter, delay, reverb, DeNoise, DeHummer, invert and pitch shift — all keyframable, continuous across scrubbing, playback and export with latency compensated. The Audio Track Mixer and Audio Clip Mixer provide faders, pan, mute, solo, five insert slots per track (pre- or post-fader), sends, submixes and a Mix track, all sample-accurate; 24 tracks with three effects each mix about six times faster than real time on one core. Automation offers Read, Latch, Touch and Write, recorded live from the mixer during playback. Playback runs on the audio clock, so picture follows sound and never the reverse.
Titles and captions use a real text engine: OpenType shaping with kerning and ligatures, bidirectional text, line breaking, tracking and leading, drawn in linear light and sharp at any scale or rotation. The Type, Shape and Pen tools work on the Program monitor; graphic clips hold text and shape layers with fill, strokes, background and shadow, all keyframable. Caption tracks support Subtitle, CEA-608, CEA-708 and Teletext, with frame-exact SRT, WebVTT and SCC import/export, editing in the Text panel and burn-in on export.
Export, and where delivery stops
Export mode presets cover Media File, YouTube, Vimeo, TikTok, Instagram and FTP. The software-encoded delivery format is H.264 MP4 with AAC — the project’s own test render of a 6-second 960×540 clip takes 1.3 seconds and decodes in ffmpeg without a single warning under strict error detection. Beyond that: Apple ProRes 422 HQ and Motion JPEG in QuickTime, MXF OP1a and Avid-style OP-Atom (DNxHR, ProRes or H.264 with PCM and start timecode), PNG sequences, animated GIF and WAV. Background jobs carry progress and cancel, so you keep editing while it renders; rendered previews cache by content, so an edit only invalidates what it touches and undo brings the green back.
Put that next to the gap list and the sweet spot is obvious. H.264-delivered web content, social video, sizzle reels and trailers are what it cuts well today; projects that need HEVC or AV1 delivery, VST3 plugins, or .prproj opening do not pass through it yet. The project’s own phrasing on platform reliability — Windows and Linux get far less testing than macOS — makes the priority order clear.
FilmCraft vs Kdenlive vs Shotcut
The free editing seat on the 2026 desktop, with facts checked on 2026-10-12:
| Dimension | FilmCraft v0.6.0 | Kdenlive | Shotcut v26.9.27 | Premiere Pro |
|---|---|---|---|---|
| License | MIT / Apache-2.0 | GPL-3.0 | GPL-3.0 | subscription, $22.99/month |
| Stack | pure Rust, own codecs | C++/MLT | C++/MLT | native |
| Interface | mirrors Premiere | its own logic | its own logic | — |
| Color | full Lumetri-style panel | scopes | basic | Lumetri |
| Loudness | BS.1770 / R128 meters | yes | yes | yes |
| Plugins | none (listed gap) | yes | yes | rich |
| Delivery formats | H.264 only (software) | broad | broad | everything |
.prproj | cannot open | cannot open | cannot open | — |
| Self-rated maturity | alpha, ~56% | years of stable releases | years of stable releases | commercial software |
Kdenlive’s reputation for crashing largely dates from older versions, as one 2026 review puts it, though large projects can still stumble; Shotcut v26.9.27 was the latest stable at our October 8 check-in, with 15,407 stars on GitHub. Both share the advantages of age and format coverage, and both put the interface on their own logic. One more option sits outside the table and belongs in any honest 2026 comparison: DaVinci Resolve’s free version, whose color grading is the class of the field, with a plugin ecosystem and delivery formats more complete than any open-source option — paid for in learning curve and memory footprint. FilmCraft’s differentiators are specific: Premiere muscle memory, the integer time base, and an engineering base that ships its own codecs.
Interchange and agents
FilmCraft takes “switching tools” seriously because it knows Premiere users live in collaboration. Its .fcproj files cannot open Premiere’s .prproj, but timelines move in both directions across six formats: Final Cut Pro 7 XML (xmeml — the format Premiere and DaVinci exchange — carrying nested sequences, transitions, generators, Motion, Opacity, Time Remap and audio levels with keyframes); FCPXML 1.9–1.11 with connected clips as lanes; OpenTimelineIO, the film industry’s open interchange format, round-tripping every FilmCraft detail through metadata.filmcraft; CMX 3600 EDL, the oldest format still in use, with drop-frame timecode, dissolves, wipes and M2 speed changes; AAF (Edit Protocol) for Avid Media Composer and Pro Tools; and OMF 2.0 for the audio-post handoff. Import merges the document’s bins, media and sequences as one undoable step and links every media file it finds on disk.
The agent door matches its siblings: every menu item, button, slider and drag is a command with an id, typed parameters and an enabled state — more than 650 engine commands in total, listed by filmcraft-cli commands. The UI, the CLI, a JSON control channel and an MCP server all dispatch the same commands, so an agent can cut, trim, grade, mix and export exactly the way a person does; the UI can also be driven at the level of mouse and keyboard, since every widget carries an automation id. The Apollo 11 documentary cut in the README screenshots — three minutes of NASA launch, landing and moonwalk footage with subtitles from the mission transcript — was built exactly that way, by an agent driving the running app. Batch rendering, scripted timeline edits and agent-cut rough cuts are capabilities you can use today. For the bitmap-side equivalent of this workflow, see our PhotoCraft test.
Installing and first run
Builds cover more platforms than most editors of this age. The FilmCraft page on getartcraft.com is the easy route; the GitHub release page lists every format with a SHA256SUMS.txt checksum list. macOS gets a universal DMG, signed and notarized, plus a signed CLI zip. Windows gets MSI and portable zips for x64, arm64 and x86, all code-signed. Linux gets an AppImage with .zsync self-update, a Flatpak, .deb, .rpm and a tarball whose installer places the app, its CLI and desktop entries under ~/.local without administrator rights (sudo ./install.sh --prefix /usr/local for all users). FreeBSD has a tarball, every release ships a WebAssembly build, and Gentoo users can install a community-maintained package from the ::snakebyte overlay.
One Windows quirk is worth copying down. The app initializes only Vulkan and DirectX 12 by default, not OpenGL, because letting wgpu also create an OpenGL instance can crash some drivers — AMD’s atio6axx.dll among them — before the window appears, so the app flashes in Task Manager and quits. When that happens, set WGPU_BACKEND=vulkan (or dx12) in PowerShell and relaunch. The macOS, Linux and web defaults are unchanged.
Project files are .fcproj, with documented schema migrations, auto-save and crash recovery. The architecture is a layered Cargo workspace — codecs and containers, foundations, editing and interchange, rendering and output, engine, front ends, test support — and nothing below the front ends depends on a UI toolkit or OS API, which is why the browser build and a future alternate interface are both possible rather than hypothetical.
Who should try it, who should wait
- Solo creators and small teams cutting H.264-delivered content: worth a trial. Zero migration cost on the interface, the full edit-trim-color-caption-mix chain, fast exports and crash recovery as a safety net. Re-cut one project you have already finished, and half a day answers the question.
- Projects that need HEVC/AV1 delivery or VST3 plugins: stay on your current tools. Both gaps are documented in the README with no workaround.
- Heavy Premiere collaborators: wait for
.prprojsupport and plugin hosting. Timeline interchange (XML/AAF/OTIO) covers part of the collaboration story, not all of it. - Developers and automation: usable now. 650+ commands plus MCP suit batch transcoding, scripted editing and agent rough cuts.
FilmCraft belongs to a bigger picture: our seven-app comparison weighs all of ArtCraft’s Adobe alternatives. The GitHub repository updates daily; downloads live at getartcraft.com/apps/filmcraft, with a signed and notarized macOS build, code-signed Windows installers, AppImage, Flatpak, deb, rpm and tarballs for Linux, a FreeBSD tarball, and a WebAssembly build you can self-host. If the Windows app does not open, the README’s fix is to switch backends with WGPU_BACKEND=vulkan or dx12.
One practical suggestion for the trial itself: keep a copy of your last delivered project, and re-cut it from the same footage rather than starting something new. Re-cutting exposes the gaps that matter — a transition that renders differently, a keyframe that lands a frame late, a H.264 export that a client platform refuses — while the story is already finished, so you are measuring the tool instead of the deadline. Take that saved project with you when you file a bug; real footage reports are what the project says it needs most.
FAQ
Is FilmCraft free for commercial use?
Yes. MIT or Apache-2.0 dual license, no fee, no telemetry. The repository contains no Adobe code, icons, presets or LUTs and no GPL/LGPL code; ffmpeg is used only as an external test oracle.
Can it open Premiere project files?
No. .prproj files cannot be opened; the project recommends bringing sequences over as FCP7 XML, AAF or OTIO. The same formats export, so timeline-level exchange with Premiere and DaVinci collaborators exists — project files and bin structures do not round-trip.
Is H.264 the only export format?
For software encoding, yes — H.264 MP4 is the only software delivery codec; H.265 exports only through hardware encoders (NVENC on Windows, VideoToolbox on macOS), and AV1 export does not exist yet. ProRes 422 HQ, Motion JPEG, MXF OP1a/OP-Atom, PNG sequences, GIF and WAV are also writable.