You Dragged an MP4 Onto the Timeline and Now You’re Confused
You opened DaVinci Resolve, dragged an MP4 onto the timeline, and got “media offline.” Maybe a generic import error. Maybe nothing happened at all. You Googled it, found a Reddit thread from 2021, and now you’re reading about transcoding pipelines at 11 PM when you just wanted to cut together a homelab tour video.
Welcome to video editing on Linux.
Here’s the good news: you actually have two serious options, and one of them won’t do this to you. The bad news is figuring out which one that is — because both Kdenlive and DaVinci Resolve are legitimately powerful, both are technically free, and the internet is full of people who love whichever one they picked first and will defend it emotionally.
Let’s skip the fanboyism. You need to edit video on Linux. Here’s how to pick the right tool without wasting a weekend on the wrong one.
The Field Is Smaller Than You Think
Before we get into it: yes, there are other Linux video editors. Shotcut exists. OpenShot exists. Olive has been “almost ready” for several years. Pitivi is there if you want something that respects your freedom more than your time.
None of them are the answer for serious work. Shotcut and OpenShot are fine for cutting a holiday video together, but they hit walls fast — missing features, quirky behavior, limited export options. Olive is genuinely promising but not production-stable yet. Pitivi is… fine. For very specific things.
The real choice, for anyone who edits more than occasionally, is Kdenlive or DaVinci Resolve. Full stop. Everything else is a detour.
DaVinci Resolve on Linux: The Asterisks
Resolve is a genuinely world-class editor. Hollywood uses it. Colorists love it. The Fusion compositing environment is deep enough to lose months in. Fairlight audio is a full post-production suite. None of that is marketing copy — it’s real.
But Resolve on Linux, especially the free version, comes with a stack of asterisks that Blackmagic doesn’t put in the headline.
Asterisk One: No MP4. No AAC. No, Really.
This is the one that gets everyone. DaVinci Resolve Free on Linux does not support H.264 or H.265 video, and will not encode or import AAC audio. This isn’t a Linux-specific bug — it’s intentional. Blackmagic licenses those codecs for the Studio version and strips them from the free tier.
What this means in practice: every MP4 you shoot on your phone, every screen recording from OBS, every clip off your camera — none of it imports cleanly into Resolve Free. You have to transcode it first. The standard workaround is ffmpeg:
ffmpeg -i input.mp4 -c:v dnxhd -profile:v dnxhr_hq -c:a pcm_s16le output.movDNxHD/HR is a professional intermediate codec that Resolve loves. It also produces files that are roughly 10x the size of your H.264 original. That 4GB MP4 from your camera becomes a 40GB MOV before you’ve cut a single frame. You’ll want a big drive.
ProRes is the other common option if you’re in a Mac-adjacent workflow. Either way, the point is: transcoding is now a mandatory step in your workflow if you use Resolve Free. For some people that’s a one-time setup cost they accept. For most homelab creators who just want to ship a video, it’s an immediate deal-breaker.
Asterisk Two: The Linux Installer Is a Journey
Blackmagic ships Resolve for Linux as a .run script. On Rocky Linux 9 or the specific Ubuntu LTS versions they actively test against, it installs reasonably cleanly. On anything else — Arch, Fedora, Debian, newer Ubuntu — you are on your own.
The problems vary: missing libfusion.so, wrong libstdc++ version, CUDA runtime mismatches, missing libOpenCL, the installer silently failing and Resolve launching as a gray window. Community scripts like MakeResolveDeb (for Debian/Ubuntu) and the davinci-resolve AUR package (for Arch) exist specifically because the official installer fights non-targeted distros.
If you’re on a stable Ubuntu LTS or Rocky Linux and you have an NVIDIA card, you’ll probably be fine with some patience. If you’re on Arch with an AMD GPU, you’re about to spend a Saturday reading forum threads.
Asterisk Three: It Really Wants NVIDIA
Hardware acceleration in Resolve on Linux is CUDA-first. NVIDIA GPUs work best, and even then you need to match driver versions carefully — Resolve has specific CUDA requirements that don’t always align with whatever your distro’s NVIDIA package ships.
AMD GPU users can get OpenCL working, and ROCm support exists in theory. In practice it’s inconsistent, slower than CUDA, and requires enough configuration that “works” is generous. Intel Arc/iGPU users are largely out of luck for hardware-accelerated processing.
This isn’t a dealbreaker if you have the right hardware. But if you’re running a Ryzen mini PC, a ThinkStation with an AMD workstation GPU, or anything with integrated graphics, Resolve’s performance story falls apart quickly.
Asterisk Four: The Real Price
DaVinci Resolve Studio is $295 USD, one-time, no subscription. That’s genuinely reasonable for what you get. But that number matters because the free version’s limitations — particularly the codec restrictions — push a lot of users toward it.
If you edit regularly, shoot in anything other than RAW/ProRes, and want a workflow that doesn’t require a transcoding step before every project, Resolve Studio is basically required. Budget for it from the start if Resolve is your path.
Kdenlive: The Honest Trade-offs
Kdenlive isn’t the flashy choice. It doesn’t have Resolve’s color grading nodes, doesn’t have Fusion compositing, doesn’t have Fairlight’s multi-track mixing depth. If you go in expecting Hollywood post-production tools, you’ll be disappointed.
What Kdenlive has is: it works. On Linux. With your actual files.
Where Kdenlive Falls Short
Color grading in Kdenlive is competent for basic corrections. You get a color wheel, curves, levels, some scopes. It’s fine for “fix the white balance and make it look less gray.” It is not a replacement for Resolve’s node-based color pipeline if you’re grading LOG footage or doing anything more than basic correction. There’s no serious argument here — Resolve wins this category by a wide margin.
Audio mixing is functional but shallow. You get tracks, effects, per-clip volume, basic ducking. If you need multi-track dialogue editing, ADR workflow, or anything approaching professional audio post, Kdenlive will leave you reaching for a dedicated DAW.
The plugin ecosystem is Frei0r effects and MLT filters. These cover a lot of ground for common use — blur, color effects, motion, chroma key — but there’s no OFX ecosystem and nothing like Fusion for compositing. What you see is what you get.
Project file stability has gotten much better over the past few releases. That said, Kdenlive’s project files are XML on disk (which is actually nice — you can grep them, diff them, version them with git), and a hard crash on a corrupted save can still ruin your afternoon. Save versions manually. Use Save As aggressively. It’s not 2018 anymore but the ghost is still there.
Where Kdenlive Wins
Kdenlive is a native Linux application. It installs from your package manager. On Debian/Ubuntu: apt install kdenlive. On Arch: pacman -S kdenlive. On Fedora: dnf install kdenlive. No .run script fighting your libraries. No CUDA dependency. VAAPI hardware acceleration works on Intel, AMD, and NVIDIA via VA-API or NVENC. It just works.
MP4, MKV, MOV, AVI, WebM — drag it to the timeline. It renders. No transcoding step. No intermediate codec dance. Your OBS recordings, your phone footage, your GoPro clips, your YouTube downloads — all of it imports. This sounds like a low bar, but compared to Resolve Free, it’s actually the defining difference for most workflows.
The render dialog exposes ffmpeg directly. You can set CRF values, pick hardware encoders (h264_vaapi, hevc_nvenc), write custom encoder strings. It’s not a pretty GUI, but it gives you real control over the output in a way that Resolve’s free tier export dialog doesn’t.
Hardware floor is low. Kdenlive edits 1080p footage acceptably on a mini PC with an iGPU. 4K gets choppy without hardware acceleration, but you can proxy clip it. Resolve Free needs a beefier machine to feel smooth, and even then you’re dependent on the NVIDIA tax for the good performance path.
It’s KDE. It’s open source. The project is actively developed. The community is responsive. If something breaks, there’s a bug tracker and people who fix things.
The Decision Matrix
Stop overthinking it. Here’s where you probably land:
Pick Kdenlive if:
- You’re making tutorial videos, screencasts, YouTube content, or homelab demos
- Your footage comes from phones, cameras, OBS, or anything that outputs MP4
- You have an AMD or Intel GPU (or integrated graphics)
- You’re on Arch, Fedora, or any non-Ubuntu distro
- You’re learning video editing for the first time on Linux
- Your deliverable is “1080p MP4 uploaded to YouTube”
- You want to install it in 30 seconds and start cutting
Pick DaVinci Resolve (Studio) if:
- Color grading is a core part of your work — you shoot LOG/RAW and need real node-based grading with proper scopes
- You need Fairlight-level audio post: ADR, multi-track dialogue, professional mixing
- You use Fusion for compositing or motion graphics
- You have an NVIDIA GPU and you’re on Ubuntu LTS or Rocky Linux
- You’re working on a film, short, or production where the output quality justifies the workflow complexity
- You shot it on a Blackmagic Pocket Cinema Camera — you already own this problem, might as well lean in
- You’re buying Studio anyway — the free version restrictions aren’t your concern
Genuinely don’t bother with Resolve Free if:
- Your footage is MP4 and you don’t want to transcode it
- Your GPU is AMD or Intel
- You’re not on a Blackmagic-friendly distro
- You just want to cut and export without fighting the tooling
The Honest Take
Resolve is the more powerful editor. That’s not debatable. The color science, the audio tools, the compositing, the professional workflow integration — it’s genuinely impressive and the $295 Studio license is fair pricing for what you get.
But “more powerful” only matters if you need that power. Resolve is a Ferrari that demands premium fuel, a specific track, and an NVIDIA mechanic on call. Kdenlive is a Civic that runs on whatever’s at the pump, starts every time, and gets you where you’re going without drama.
For 90% of Linux users in the homelab/tech-creator space, Kdenlive is the right answer. Not because it’s a better editor in absolute terms — it’s not — but because it’s enough, and it doesn’t fight you. The time you’d spend transcoding codecs, wrestling the Resolve installer, and managing CUDA driver versions is time you could spend actually editing.
If you grow out of Kdenlive’s color grading or genuinely need Fusion-level compositing, you’ll know. At that point, buy Resolve Studio, make sure you have NVIDIA, use Ubuntu LTS, and commit to the workflow. It’s worth it when you need it.
Until then: apt install kdenlive, drag your MP4 to the timeline, and get to work.
One More Thing: The “Free” Math
Both editors advertise as free. Let’s be precise about what that means.
Kdenlive is free as in open source, free as in beer, free as in “installs from your package manager and doesn’t ask for anything.” There is no paid tier, no Studio version, no codec you have to buy. It’s just free.
DaVinci Resolve Free is free as in “the base application doesn’t cost money, but the codec you need costs $295 and the GPU that makes it work costs several hundred more.” That’s not a scam — the Studio license is genuinely good value. But it’s worth being clear-eyed: Resolve Free on Linux is a demo of what Resolve can do if you have the right hardware, the right distro, and a willingness to either pay for Studio or transcode everything you touch.
Neither answer is wrong. Just know what you’re signing up for before you spend a Saturday fighting it.
