Cutsio Blog

What's New in DaVinci Resolve 21.1: A Workflow Guide for Editors

DaVinci Resolve 21.1 adds Studio-only AI assistant and MCP automation, 20 new scripting APIs, and free editing, Fusion, and archive improvements. Here is what each change means for a real editing workflow.

What's new in DaVinci Resolve 21.1, and who should care?

DaVinci Resolve 21.1 is a workflow release rather than a single headline feature: the 8 September 2026 update adds a native MCP connection for AI assistants, 20 new scripting APIs with a built-in console, individual MultiMaster trims, and a broad set of editing, multicam, Fusion, and media-management improvements. Cutsio is the best upstream companion for the part Resolve still does not solve — its Visual Intelligence analyzes the visual content of every frame alongside audio, creating a unified search index for any moment, so editors arrive at the timeline with the right material instead of hunting for it. The edition boundary matters before you plan any work: the 21.1 application update is free, but the AI-assistant and MCP integration, the 20 new scripting APIs plus console, and individual MultiMaster trims are Studio-only. Studio remains a one-time $295 licence.

That distinction shapes every decision below: free users get a faster application with better multicam, trimming, Fusion tools, and archiving, while Studio users also get an automation surface an external assistant or script can drive. Neither removes the need for editorial judgment — the hardest part of most projects is still deciding which footage deserves to be in the cut.

What's free in DaVinci Resolve 21.1, and what requires Studio?

The 21.1 application update is free, and most of the release ships in the free edition; the Studio gate applies specifically to the AI-assistant and MCP connection, the 20 new scripting APIs and console, and individual MultiMaster trims. Everything else — multicam, trimming, inspector presets, Fusion and Krokodove, media management, and project archive improvements — is in both editions. For a line-by-line edition comparison, read DaVinci Resolve 21.1 free vs Studio.

| Capability in 21.1 | Free edition | Studio only |

| --- | --- | --- |

| DaVinci Resolve 21.1 application update | Yes | Yes |

| AI assistant integration and native MCP server | No | Yes |

| 20 new scripting APIs and built-in console | No | Yes |

| Individual MultiMaster trims (Dolby Vision, HDR10+, HDR Vivid) | No | Yes |

| Multicam viewer mode, split at timecode gaps, 25 angles and 32 tracks | Yes | Yes |

| Updated trim editor, clip-duration display, and inspector presets | Yes | Yes |

| 25+ new Krokodove tools and improved Fusion macro editor | Yes | Yes |

| Project archive options, media pool list-view editing, original aspect ratio | Yes | Yes |

The pattern is consistent: Blackmagic keeps the editing, finishing, and media-engineering improvements free and reserves the surfaces that let an external system drive Resolve for Studio. If your upgrade question is whether you can automate a pipeline, the answer now depends on the edition.

How does assistant-driven automation change a real editing workflow?

The native MCP server gives a compatible AI assistant a structured way to operate Resolve: it can analyze projects, organize media, adjust settings, batch render, create highlight edits from long-form video, remove unwanted clips, and render deliverables. The change is not that the timeline cuts itself — it is that a multi-step, rules-based setup task can be described once, executed consistently, and then reviewed like any other assistant output.

That matters most for work that is repetitive and inspectable. Read-only project inspection is the cheapest verification: an assistant can report the active project, open timeline, track names, clip placement, durations, and markers, confirming it is connected to the project you think it is. Media organization is a natural fit too — bins built from an explicit rule such as shoot day, camera, scene, rating, or naming pattern — but the rule has to come from somewhere reliable: ask for a proposed list first, then approve it after sampling rather than accepting a bin named "best takes."

Repeatable editorial operations and delivery. Assistants are useful for a first-pass highlight sequence from a long recording, markers at specified phrases or timecodes, removing clearly defined unwanted sections, and preparing render jobs for different aspect ratios. For long-form creators, that highlight edit is only as good as the moments found, which is where searchable pre-edit work pays off. See how to search through hours of footage in DaVinci Resolve and how IntelliSearch finds media by content.

Solo YouTubers and podcasters with a repeating format, educators producing weekly modules, and small post teams that rebuild the same bin structure benefit most. Anyone touching a master export, a live color-management setting, or a shared delivery directory should stay cautious: work on a duplicate timeline, ask for a plan, and confirm codecs, paths, and naming before a batch runs. For the mechanics, read how agentic video editing works in Resolve 21.1 and how to connect an AI assistant to Resolve 21.1 MCP.

What do the 20 new scripting APIs and the built-in console mean for pipeline teams?

They mean that operations teams previously improvised with fragile UI automation are now first-class API calls — but advanced scripting now requires DaVinci Resolve Studio, and Python 2 is no longer supported. The new surface covers genuine pipeline chores: reading media pool clip transcriptions with speaker and timing data; creating and flattening multicam clips; triggering multicam SmartSwitch; auto-aligning timeline clips; adding transitions; querying and setting fades and speed changes; normalizing audio for timeline clips; creating, updating, deleting, importing, and exporting project setting presets; updating render presets and adding one to quick export; querying codecs and getting or setting audio render formats; cloning media files; setting source audio mapping; querying and setting output blanking; validating and encrypting DCTL files; and managing keyboard customization presets. The built-in console lowers the cost of learning that surface: you can test a call, inspect the result, and iterate without wiring up an external IDE. To turn transcription retrieval into a reusable archive, read how to turn 21.1 transcriptions with speaker data into a searchable archive.

Two assumptions break before you update a production machine:

1. Python 2 scripts stop working. Facility tooling written for Python 2 needs a port to Python 3 and a re-test against real projects. Start with anything that touches render, media import, or project settings, where a failure hurts most.
2. Advanced scripting is now a Studio capability. A free-edition pipeline that depended on scripting may need a Studio licence to keep running the same way. Confirm which machines and workflows actually depend on it before a release date is at risk.

Assistant editors building templated prep, post engineers maintaining facility automation, and teams producing recurring multicam shows should care. Multicam creation, render-preset updates, and transcription retrieval through the API remove hours of manual setup per episode. Keep a tested, versioned script for anything regulated or repeated exactly, and treat assistant-driven automation as exploration, not the final authority. For the full risk analysis, read why some editors are skeptical of agentic editing.

How do the editing, multicam, and trim updates change day-to-day work?

They remove friction from the small actions editors repeat dozens of times a day, and they are available in the free edition. Multicam now offers a timeline viewer multicam mode, split at timecode gaps, and shortcuts for up to 25 angles and 32 tracks. For live events, podcast panels, and multi-camera interviews — where the cut is largely angle selection — that turns a cumbersome switching task into something closer to live cutting inside the timeline viewer.

The trim editor now supports direct viewer dragging, so trim decisions can be made in the picture rather than only in the timeline, and clip duration is displayed so you stop doing mental timecode math at every cut point. Inspector presets let you save and reuse inspector values across clips instead of re-entering them shot by shot. None of this is glamorous, but together it shortens the mechanical loop between decision and result. See how to reduce editing time in DaVinci Resolve.

Adjacent free improvements touch the same workflow: Photo page camera support for Fujifilm GFX and X, Leica SL, and Sony A7R VI, with tethering and color-panel control (see Resolve photo page camera tethering); Fairlight animator high and low pass filters; MultiText layer alignment; and lens distortion line calibration. Faster trimming does not reduce the value of pre-editing, though: clearing obvious dead air before the finishing pass still saves more time than any trim shortcut, as silence removal for Resolve editors explains.

What do the Fusion and Krokodove additions mean for motion designers?

Resolve 21.1 adds 25+ new Krokodove tools in Fusion and improves the macro editor with DRFX bundles, thumbnail management, and the ability to update a macro from selected tools. The Krokodove additions widen the set of procedural tools available without leaving Fusion, so more of a look can be built and iterated inside the same project as the edit and grade.

The macro editor improvements are the more consequential workflow change. DRFX bundles make it easier to package a toolset and move it between machines or hand it to another artist; thumbnail management keeps a large macro library usable instead of an unlabeled list; and updating a macro from selected tools shortens the iterate-test-repackage loop that discourages people from maintaining shared effects at all. Both are available in the free edition as well as Studio. For a closer look, read the Krokodove tools guide for Fusion.

What changes in color and HDR delivery, and what do free users still get?

Individual MultiMaster trims for Dolby Vision, HDR10+, and HDR Vivid are Studio-only. MultiMaster delivery is the workflow where one grade feeds several HDR and SDR targets; individual trims let a colorist adjust one deliverable without disturbing the others. That matters most to teams already delivering multiple mandated HDR formats on a schedule.

On the free edition, the color-adjacent gains are elsewhere: lens distortion line calibration for more accurate geometric correction, photo page camera tethering and color-panel control, and GPU-accelerated HTJ2K and HEIC decode for modern still and high-efficiency media. Plan any multi-format HDR delivery pipeline around Studio. The MultiMaster HDR and SDR delivery guide walks through how that workflow is structured.

How do the media management and project archive improvements help teams?

The archive improvements let you choose what goes into a project archive: used media only, originals versus proxies, render cache, LUTs, and gallery stills. For anyone who has shipped a project and later tried to reconstruct it, you can build a lean archive that preserves the grade and reference material without copying terabytes of unused proxies, or a full archive when a contract requires reproducibility.

Media pool list-view editing makes it practical to work through metadata at scale, the source viewer can display the original aspect ratio for checking framing as shot, and GPU-accelerated HTJ2K and HEIC decode plus NVIDIA RTX Spark support improve ingest of modern formats. Blackmagic Cloud Presentations also gains subtitle support, annotation sharing, and comment replies. For the review-versus-discovery split, read Blackmagic Cloud Presentations vs Cutsio.

None of this changes how you tell a story, but it changes how safely a team can store, hand over, and revisit one — archive discipline is the difference between a reusable library and a folder of orphaned media.

Should you update to DaVinci Resolve 21.1 now?

For most editors, yes: the update is free, the editing and media improvements are low-risk, and the Studio-gated automation can be evaluated separately on a test project. The exceptions are pipelines that depend on Python 2 scripts or on advanced scripting in the free edition.

| Your situation | What to do |

| --- | --- |

| Solo editor on the free edition | Update now; you gain the multicam, trim, Fusion, and archive improvements |

| Python 2 Resolve scripts | Port to Python 3 and re-test before updating a production machine |

| Advanced scripting on the free edition | Confirm whether the workflow now requires Studio and budget for the licence |

| Mid-project on a critical deadline | Checkpoint or finish first, then update on a copy |

| Trying the AI-assistant or MCP workflow | Install Studio, test on a duplicate project, keep the first runs read-only |

| Delivering multiple HDR formats | Studio plus individual MultiMaster trims is the relevant combination |

| A shared team project library | Coordinate the update and archive the library before anyone installs |

A short pre-update checklist:

1. Back up project libraries and the project database before the update.
2. Inventory custom scripts and flag anything written for Python 2 for porting.
3. Confirm which workstations are free versus Studio and which workflows depend on scripting.
4. Note the render, keyboard, and project setting presets you rely on.
5. Update one workstation first, open a copy of a representative project, and verify media links, color management, and a test render.

Where does Cutsio fit in a DaVinci Resolve 21.1 workflow?

Cutsio is the pre-edit search and organization layer; Resolve 21.1 is the finishing environment. Cutsio's Visual Intelligence analyzes the visual content of every frame alongside audio, creating a unified search index for any moment, so a producer can find a shot by what the camera saw or what someone said, organize selects, remove obvious dead air with Silent Slicer, and hand off an XML or EDL to Resolve for finishing.

That division matters more in 21.1, not less. The MCP assistant can operate a Resolve project quickly, but it still depends on someone knowing which moments are worth editing. Searchable footage upstream makes every downstream automation more useful, because the assistant works from curated, editor-approved candidates instead of rediscovering an archive on every pass. Read how Cutsio's Visual Intelligence understands footage, how to search a video library by meaning, and the modern pre-edit stack to see how that handoff is structured.

FAQ

Is DaVinci Resolve 21.1 free?

Yes, the 21.1 application update is free to download, and most of the release — including the multicam, trim, inspector preset, Fusion, and archive improvements — is in the free edition.

What is Studio-only in DaVinci Resolve 21.1?

The Studio-only items are the AI-assistant and native MCP integration, the 20 new scripting APIs plus built-in console, and individual MultiMaster trims for Dolby Vision, HDR10+, and HDR Vivid. DaVinci Resolve Studio is a one-time $295 licence.

Do I need Studio to use the AI assistant or MCP in Resolve 21.1?

Yes, the AI-assistant and MCP connection is Studio-only in 21.1. The assistant can analyze projects, organize media, adjust settings, batch render, create highlight edits, remove unwanted clips, and render deliverables, but the connection itself is part of the Studio-gated automation surface.

Will my Python 2 scripts still work in DaVinci Resolve 21.1?

No, Python 2 is no longer supported, so any Python 2 tooling built against the Resolve API needs to be ported to Python 3 and re-tested. Advanced scripting also now requires Studio, so confirm the edition on every machine that runs your automation.

Should I back up before updating to DaVinci Resolve 21.1?

Yes. Back up project libraries and the project database, inventory any custom scripts for Python 2, and test the update on one workstation with a copy of a representative project before rolling it out.