Drift: a free Qt 6 and FFmpeg desktop video editor for Reels, Shorts and game clips

What Drift is for, and who it is not for

Drift is a desktop video editor from CutWire Studios. The README frames the audience directly: Reels and Shorts, game clips, school projects, tutorials, product demos and memes. The pitch is that it runs on your machine rather than in a browser, with no subscription, no watermark and no account. That last point is the real differentiator. Most editors in this bracket ask you to sign in before you can export, and Drift's README treats the absence of that as the product.

The stated design goal is preview parity: what you see in the preview is what you export, because there is one compositor rather than separate preview and render paths. If that holds, it removes a common source of frustration in lightweight editors, where a filter looks one way on the timeline and another way in the file. It is a claim about architecture, not a benchmark, and the README does not publish measurements for it.

Who it is not for is just as clear from the feature list. There is no mention of multicam, no mention of proxy media, no mention of a scripting or headless render mode. If your work is long-form, multi-hour, or driven by a build pipeline, the feature set described here is not aimed at you.

How the editor is put together: Qt 6, FFmpeg, and one compositor

The repository is a C++ project built with CMake. The top level holds CMakeLists.txt, cmake/, src/, tests/, third_party/ and tools/, which is the layout you would expect from a Qt application that vendors some dependencies rather than pulling everything from a system package manager. Qt 6 supplies the window, the media bin, the preview, the inspector and the timeline; FFmpeg supplies decode, encode and the filter graph underneath.

The interesting structural claim is the single compositor. In editors that keep a fast preview renderer and a separate high-quality export renderer, the two drift apart and the user discovers the difference only after a long encode. Drift's README says there is one, and that the export dialog offers downscale presets plus advanced encoder settings on top of it. If the compositor is genuinely shared, changing an encoder setting changes the file, not the look.

Around the core sit several content directories: effects/, transitions/, effect-templates/, presets/, audio-effects/, resources/ and i18n/. Their presence tells you the effects browser, the transitions browser, the look templates and the audio chain are data-driven, loaded from files rather than hard-coded into the binary. That is good for contributors and for anyone who wants to understand what a preset actually does, and it also means a broken preset file is a plausible failure mode rather than a hypothetical one. The README does not document a validation step for those files.

Installing Drift on Linux from Flathub, and a first export

On Linux the README gives a Flathub install as the primary path. The application ID is org.cutwire.Drift, and the two commands below install it and then launch it. After the first command finishes, the app appears in your desktop launcher under the name Drift.

flatpak install flathub org.cutwire.Drift
flatpak run org.cutwire.Drift

If you are not on Flathub, the README points to the latest release page for platform builds: an AppImage for Linux, an installer and a portable zip for Windows, a .dmg for Apple Silicon macOS, and APKs for Android. The Android build is the unusual one here. The README says to take Drift-*-arm64-v8a.apk for a phone and to use the x86_64 build for emulators, and it gives the adb form of the install:

adb install Drift-*-arm64-v8a.apk

Once the editor is open, the workflow the screenshots describe is: drop clips into the media bin on the left, drag them to the multi-track timeline below, stack overlays, titles and B-roll on additional tracks, then open the export dialog. The README describes that dialog as simple presets up front with extra control when you want it, and it shows downscale presets alongside advanced encoder settings. The README does not document a command-line export, so the export dialog is the path.

Subject cutout, captions and the audio chain in practice

Three features stand out because they are the ones lightweight editors usually skip. The first is subject cutout: the README shows a dialog where you click the subject and the isolated person or object is placed on its own clip. That is a rotoscoping-adjacent operation, and the README presents it as a click rather than a mask you draw by hand. It does not describe how the selection is computed or what happens on a clip where the subject leaves the frame, which is exactly where such tools tend to fall apart.

The second is captions. The README says captions are generated from the speech itself and then editable line by line, with the subtitle editor highlighting the line at the playhead. Generating a first pass and correcting it is a much better use of time than typing every line, so the design choice is sound. Accuracy is not stated anywhere, and the README does not say whether the speech recognition runs locally or needs a network call, which matters for anyone who picked Drift specifically to avoid an account.

The third is audio. The audio-effects directory and the screenshots list EQ, compressor, limiter, noise gate, de-esser and a voice leveler. That is a small but sensible chain for spoken-word content, and it is the part of the app most likely to make a phone recording sound deliberate. The README does not give default values or describe the processing order.

Where Drift will disappoint you

The README is silent on several things an editor needs to know before trusting it with a project. There is no mention of autosave, crash recovery or a project file format. If the app closes unexpectedly, the documentation gives you no reason to expect your timeline back. Until that is documented, save often and keep the source clips, because a project file you cannot reopen is not a backup.

There is also no documented proxy workflow. Decoding 4K footage on a laptop while compositing several tracks is the classic case where a small editor stalls, and Drift's README does not describe a lower-resolution editing mode. It does offer downscale presets at export, which is a different thing: that reduces output size, not the cost of scrubbing the timeline.

The platform list is broader than the documentation behind it. Linux, Windows, macOS and Android are all named, but the macOS build is Apple Silicon only, and the README says nothing about Intel Macs. Android is presented as an APK you sideload, not a store listing, and there is no description of how a touch interface handles a multi-track timeline. Treat the mobile build as an experiment rather than a second supported platform.

Finally, the naming. Searching for "drift" returns a game, a chat product, a car air freshener and a fishing technique. The README does not address this, and it is a real cost: issues, tutorials and forum answers about this editor are hard to find by name alone.

Drift against Kdenlive and Shotcut

The obvious comparison is with Kdenlive and Shotcut, both GPL desktop editors that also sit on FFmpeg. The difference is scope. Kdenlive and Shotcut are general-purpose NLEs: multiple project profiles, configurable tracks, effect stacks you build yourself, and documentation that covers project files and recovery. Drift is narrower by design. It ships a fixed set of effects, transitions and look templates that are previewed on a real frame, and it organizes the app around a single window with media, preview, inspector and timeline visible at once.

That narrowing is the trade. In Drift you get a curated set of looks and a shorter path from import to export, and you give up the ability to assemble an arbitrary effect chain or to configure the project in detail. The README's audio list is a good illustration: EQ, compressor, gate, de-esser and voice leveler are exactly the tools a talking-head clip needs, and they are presented as a finished chain rather than as modules you wire together.

The other difference is distribution. Drift ships a Flathub package and an Android APK, which is unusual for this category. If you want the same editor on a phone and a laptop, that is a reason to look at Drift specifically. If you want a mature project format and a long tail of third-party tutorials, Kdenlive and Shotcut have the advantage, and the README does not claim otherwise.

Licence, releases and what upgrading costs you

Drift is GPL-3.0. For anyone editing their own footage, that is a non-issue: you can use the binary, keep your videos, and publish them however you like. The obligation attaches to distribution of the software or of a modified version, not to the videos you cut with it. If you plan to bundle Drift inside a product, ship a modified build, or link it into a proprietary application, read the licence text in LICENSE and get proper advice, because the GPL's requirements around source distribution are not something to infer from a summary.

The release cadence visible here is fast. v0.5.0 and v0.5.1 landed a day apart at the end of August 2026, and v0.6.0 followed on 2026-09-13. The repository's last push was on 2026-09-15. That pattern suggests a project still settling its feature set, which cuts both ways: fixes arrive quickly, and behaviour can change between minor versions. The CHANGELOG.md at the repository root is where the differences are recorded, and it is the file to read before upgrading a project you have already cut.

There is no migration tooling mentioned, and the README does not describe a project file format, so the practical upgrade cost is unknown from the documentation alone. The safe sequence is to finish and export anything in progress before moving to a new release.

Editorial conclusion

Adopt Drift if you cut short-form video on a desktop and want a single-window editor that runs from a Flathub install or a release binary without an account, and if GPL-3.0 fits how you distribute your work. Do not adopt it if you need a documented headless or scripted render pipeline, or if you are editing long-form material where a missing autosave or proxy workflow would cost you a session. Before committing, install v0.6.0, open the export dialog and confirm the downscale presets and advanced encoder settings cover your delivery format, then check the CHANGELOG for what changed between v0.5.0 and v0.6.0.

Frequently asked questions

Official sources

1. CutWire-Studios/Drift on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases