Between 1 and 8 September 2026, all three major editing platforms shipped a major release. Avid Media Composer 2026.8 on the 1st. DaVinci Resolve 21.1 on the 7th. Adobe's generative media release for Premiere on the 8th. Then IBC opened in Amsterdam on the 11th and all three stood in the same hall explaining themselves.
Every one of them led with AI. That is where the similarity ends — and the differences between them are no longer cosmetic. They are three genuinely different bets on what the next five years of post-production looks like, and which one you choose now has consequences for your cost structure, your storage, and how much of your workflow you actually control.
I run all three in a normal month: Avid and Premiere in a broadcast environment, Resolve and Premiere on freelance client work. This is the comparison I would give a colleague who asked, not a spec sheet.
Three releases, eight days, one shared idea
Here is what each one actually shipped, in one line each. The full reviews go deeper.
The side-by-side
| DaVinci Resolve 21 | Media Composer 2026.8 | Adobe Premiere 26 | |
|---|---|---|---|
| The big idea | One app for everything, stills now included | Collaborative infrastructure, transcript-first AI | Generative AI native to the timeline |
| Headline feature | Photo page + MCP server | PhraseFindAI Multicam Auto Cut | Generative Media tool |
| AI approach | Local, unmetered, plus your own assistant | Assistive, transcript-first, Gemini panel | Cloud generative, five models, credit-based |
| Cost model | $295 once | Subscription, tiered | Subscription + credits |
| Free tier | Production-capable to 4K60 | Now uncapped (First) | None |
| Collaboration | Storage-agnostic | NEXIS, or Enterprise for 3rd-party Changed | Productions, storage-agnostic |
| Colour | Best in class | Functional | Improving; Color Mode in beta |
| Captions | Solid | Transcript-led | Single-word, native |
| Automation | MCP + Python (Studio) | MC API/SDK, OTIO 2.0 | Extensions, scripting |
| Strongest for | Grading, finishing, hybrid, solo to mid teams | Episodic TV, features, large teams | Social, ads, VSLs, Adobe ecosystem |
Who leads, category by category
“Which is leading” is the wrong question asked at the wrong resolution. Broken down, the answers are clear and they are not the same answer.
The three different bets on AI
Strip the feature lists away and each company is betting on a different answer to one question: who should own the AI in your edit?
Blackmagic's bet: AI is a local capability you buy once, and the assistant layer should be open. The MCP server in 21.1 is the clearest statement of this — they did not build a chatbot, they built a socket and let you plug in whatever you already pay for. No meter between you and your timeline.
Adobe's bet: AI is a service, generation becomes a normal part of editing, and you pay per use. The reference-frame conditioning shows this is thought through rather than bolted on — generated shots are grounded in your own footage. But it changes editing from a fixed cost to a variable one, and that is a real shift for anyone running a business on it.
Avid's bet: AI should do the mechanical work and stop. Transcript-driven multicam, content prep, an embedded assistant panel — and everything it produces stays editable. Kenna Hilburn's framing was keeping “editorial oversight and creative control firmly in editors' hands,” and the release is consistent with that. It is the most conservative bet and possibly the most defensible one.
Not “which has the best AI features” but “what happens to my cost per project in two years if this becomes how I work?” A one-time licence and local processing answers that differently from a subscription plus per-generation credits. Neither is wrong. But only one of them has an answer you can put on a rate card today.
Which one you should actually use
| If you are… | Use | Why |
|---|---|---|
| Freelance, mixed deliverables | DaVinci Resolve | Edit, grade, audio, VFX and stills in one app for $295 once. Your margin is the whole point. |
| Social, ads, VSLs, short-form volume | Adobe Premiere | Single-word captions and Object Mask are aimed directly at this work; generative fill is a bonus. |
| Broadcast, episodic, multi-editor | Media Composer | Still the standard — but price the Enterprise or NEXIS path before your next renewal. |
| A colourist or finisher | DaVinci Resolve | Not a close call, and 21.1 extends the lead on HDR deliverables. |
| Shooting photo and video together | DaVinci Resolve | The Photo page collapses two ecosystems into one grade. |
| Deep in After Effects and Frame.io | Adobe Premiere | The integration cost of leaving is higher than any feature gap. |
| Learning your first NLE | Resolve or MC First | Both are now genuinely free. Resolve for freelance and commercial, Avid if you want broadcast. |
| Building pipeline automation | DaVinci Resolve | The MCP server plus the Python API is the most programmable option on the market. Note Python now requires Studio. |
Here is Adobe's own demonstration of the generative timeline — the clearest example of how differently these three companies now think about what an NLE is for:
