> ## Content Index
> Fetch the complete content index at: https://davinciresolveclub.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# DaVinci Resolve Scene Cut Detection: Split a Finished Video into Shots
- URL: https://davinciresolveclub.com/davinci-resolve-scene-cut-detection/
- Published: 2026-10-23T05:40:00.000Z
- Updated: 2026-10-23T05:39:59.000Z
- Description: Choose Media Storage before import or Studio timeline detection, then review the shot boundaries before you start grading.
- Author: Jason Miller
- Tags: Tutorials, Beginner Guides, #learn

To split a finished video into shots, open Resolve’s **Media** page, find the file in **Media Storage**, right-click it, and choose **Scene Cut Detection**. Run **Auto Scene Detect**, review the boundaries, then choose **Add Cuts to Media Pool**. In **DaVinci Resolve Studio**, you can also select a clip on an Edit or Cut timeline and choose **Timeline > Detect Scene Cuts**.

I’d choose the Media route when a long export needs careful inspection before grading. The Studio timeline route is handier when the video already sits in an edit or only one section needs splitting. Both find likely shot changes, and neither recreates the original editing project from a rendered file.

[Download](https://streamly.surf/c/2ebmf2MxAg6s?ref=davinciresolveclub.com)

## Choose the route before you start

The two commands work at different stages, and that matters more than whether you call the feature “scene detection” or “auto cut.”

- **Free or Studio, before import:** use the Media Storage browser on the Media page. Its Scene Detect window gives you a confidence threshold, three frame views, and an editable Cut List before you add the shot ranges to the Media Pool.
- **Studio, on a timeline:** use Timeline > Detect Scene Cuts on the Edit or Cut page. Resolve’s Neural Engine adds through edits to the video on the timeline. A through edit is a boundary between consecutive portions of the same source clip.
- **Only a few boundaries, or a cut you already know:** a [manual clip split](https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/) is often the more direct choice. Scene detection is useful when you need to locate many existing edits inside one file.

Blackmagic’s [Resolve 21.1 scene-detection instructions](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com#page=533) separate the Media-page workflow from the Studio-only timeline workflow, and this guide follows those desktop paths. A Studio-only timeline command doesn’t mean the older Media Storage method has gone away.

## Prepare a working copy and check the timebase

Keep the original rendered video available. To analyze an existing timeline, select it in the Media Pool and choose **Edit > Duplicate Timeline**. Give the copy a recognizable name and open it before adding cuts, so you still have an uncut assembly to compare against.

For the Media route, create or select a destination bin before detection so the shot ranges stay easy to find. I’d give the finished video its own bin, so its detected shots don’t get mixed into a bin of camera originals.

Check the source frame rate and whether it uses drop-frame timecode, then match the project’s **Timeline frame rate** and applicable **Use drop frame timecode** setting to that source workflow. The [manual’s ingest checklist](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com#page=539) warns that these settings aren’t set automatically from the file when the Media Pool already contains media. Fix any mismatch before you build an assembly around the detected cuts.

## Detect shots before adding the file to the Media Pool

1. Open the **Media** page. In the **Media Storage** browser, navigate to the finished video on disk.
2. Right-click the file there and choose **Scene Cut Detection**. For this route, start from Media Storage, before importing the file into the Media Pool. A right-click on an already imported Media Pool item is a different context.
3. In the Scene Detect window, click **Auto Scene Detect**. Let the analysis finish; its duration depends on the media, so there is no useful universal completion time.
4. Inspect the candidate boundaries with the viewers, graph and Cut List. Correct the list as described below before committing it to the pool.
5. When the list is accurate, click **Add Cuts to Media Pool**. If the **Conform Settings** dialog appears, verify that it agrees with the source settings before accepting it.
6. Close the Scene Detect window. The detected shot ranges are now available as individual clips in the Media Pool, ready to assemble in order on a timeline.

![The Media Storage browser selects Market_edit.mov with Scene Cut Detection in its context menu; a separate Media Pool bin waits below.](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/10/scene-cut-detection-storage.webp)

Launch detection from the file in Media Storage. The Media Pool receives the shot ranges after you review them.

Make your corrections in Scene Detect while you still have its full Cut List. It’s also where you save the analysis for later: the window’s Options menu provides **Save Scene Cut** for an **.sc** file and **Save EDL** for a CMX-style edit list. To resume an .sc analysis, open the same media in Scene Detect first, then use **Load Scene Cut**.

## Check the cut, not just the green line

A high line means a confident candidate, but it doesn’t guarantee a cut. In the Scene Detect viewer, the small left view shows the last outgoing frame, the main view shows the first incoming frame, and the small right view shows the second incoming frame. At a normal hard cut, the left image changes substantially while the center and right images belong to the same new shot.

Click a Cut List entry, inspect those three views, then press **N** or the **Down Arrow** for the next entry; **P** or the **Up Arrow** goes back. Check the whole list, then scrub or play through the video too. A list of accepted cuts can’t show you every cut the analysis missed.

![Scene Detect shows a wide market view before a cut and two similar close views after it, above green candidate lines and a magenta threshold.](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/10/scene-cut-detection-review.webp)

Confirm the change between the left and center frames, then check that the center and right frames continue the incoming shot.

### Remove false cuts and restore missed ones

The **magenta confidence bar** decides which candidate lines enter the Cut List. Raise it to reject shorter, lower-confidence candidates, and those lines turn gray; lower it to include more. No threshold is right for every video, and raising it can throw out genuine subtle changes along with the noise.

- **A false cut:** select its position and use **Delete** beneath the graph.
- **A missed cut:** step to the exact first frame of the incoming shot and use **Add**. Similar color and lighting across adjacent shots can hide a genuine edit from the analysis.
- **A dense cluster around a transition:** use the Scene Detect **In** and **Out** controls to isolate it, then use **Prune**. It removes neighboring candidates within one frame of another, retaining the highest-probability cut in the group. It does not simply erase every cut in the marked interval.

Blackmagic documents [fast motion and abrupt changes in color or lighting](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com#page=536) as things that can fool the detector, so a camera flash or whip pan deserves a closer look even when its line is tall. Review again after changing the threshold or pruning. A cleaner graph on its own isn’t a finished Cut List.

## Split an existing timeline in Studio

On your working timeline copy, select the finished video clip or clips you want to analyze and choose **Timeline > Detect Scene Cuts**. When processing finishes, the detected boundaries show up as through edits you can work with independently.

Keep the analysis focused. Set timeline **In** and **Out** points to limit it to part of a clip. With several video tracks present, lock the tracks you want excluded, since the [documented timeline procedure](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com#page=533) specifically supports that track restriction. A clean temporary timeline holding only the intended video also keeps unrelated layers out of the analysis.

![Studio Timeline menu highlights Detect Scene Cuts; In and Out points bracket part of a video while the upper title track is locked, with a second detail showing cuts inside the range.](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/10/scene-cut-detection-timeline.webp)

This example limits detection to the marked range while the title track stays locked. Inspect the new boundaries before grading.

Use the Up and Down Arrow keys to step through the resulting edits. To remove a false boundary, **select the through-edit line itself** and press **Delete**; selecting and deleting an entire clip is a different action. To add a missing boundary, park on the first frame of the next shot and choose **Timeline > Split Clips**. I’d use the menu commands here because they don’t assume your keyboard uses Resolve’s default mapping.

Keep the source audio available and compare it with the original after detection. A rendered soundtrack is still a mix, and finding picture cuts won’t recover the original dialogue, music and effects tracks.

## What scene detection cannot recover

**A dissolve is not a hidden hard cut.** The Media-page detector doesn’t automatically identify dissolves and other transitions as editable transition effects. Blackmagic notes that a dissolve often shows up as a triangular cluster of graph lines. Pruning that cluster can simplify the list, but the blended frames stay in the exported video.

For independent control of both pictures through a dissolve, ask for the source clips with handles or the original timeline and its media. Splitting a flattened transition doesn’t separate its two original layers. Burned-in titles, composites and grades hit the same limit: detection gives you boundaries in the rendered picture, not the components used to make it.

**Clips in the project are not new video files on disk.** Add Cuts to Media Pool creates usable shot ranges in Resolve, and timeline detection creates edit points. Neither command is a batch render. An .sc file stores the detection information, and an EDL stores edit decisions. If you need standalone video files, render them in a separate delivery step.

## If the command is missing or the result looks wrong

- **No Scene Cut Detection in the right-click menu:** return to the Media page and select the file in **Media Storage**, not the Media Pool or an arbitrary timeline clip.
- **No usable Timeline > Detect Scene Cuts in Free:** use the Media Storage workflow. The Neural Engine timeline route requires Studio.
- **Many one-frame-looking pieces:** inspect the Cut List before import. Recheck the threshold and prune only the clusters you have identified. Don’t accept a large cut count as evidence of accuracy.
- **A real shot change is missing:** inspect the boundary directly and add it manually. Look especially carefully where adjacent shots have similar contrast and color.
- **A false boundary was already imported:** distinguish Media-stage clip ranges from timeline through edits. For the Media route, return to the detection list and correct it before rebuilding the assembly; the Studio through-edit removal instruction applies to boundaries created on the timeline.

Before grading, compare the assembled result with the uncut video: first and last frames, shot order, boundary positions, duration and audio continuity. Check the frame and timecode at several boundaries instead of relying on clip names alone. Keep those comparisons in the source export’s timebase, because scene detection can’t infer the original camera timecode from pictures.

Once the boundaries are right, move on to [matching the shots for color and contrast](https://davinciresolveclub.com/davinci-resolve-shot-matching/). I’d finish the cut review first: a correction that spans two different shots is a more expensive problem to discover halfway through grading. The [Resolve learning path](https://davinciresolveclub.com/davinci-resolve-tutorial/) covers the surrounding editing and color workflow when you need a broader next step.