How to Edit a YouTube Video in DaVinci Resolve 21.2

What you need before you start · Free or Studio: which edition this tutorial assumes · Set up the project: steps 1 to 3 · Cut the video: steps 4 to 6 · Add titles, audio and color: steps 7 to 9 · Make it run well: transitions, Fusion and proxies (step 10) · Export for YouTube: steps 11 and 12 · Complete working project: script the setup and the render · Common pitfalls that waste a first edit · Troubleshooting: 10 problems and their fixes · What changed in Resolve 21 and what older tutorials get wrong · Advanced tips once the first video is out · Common questions
DaVinci Resolve 21.2 is the newest confirmed release, and the free edition is enough to take a YouTube video from raw clips to a finished MP4. This DaVinci Resolve tutorial covers 12 steps, from checking your footage to verifying the exported file, and ends with a Python script that builds the project, the timeline and the render job for you.
Blackmagic’s support documentation names 21.2 as the current version for both the free app and Studio, and the readme is dated early November 2026. The scripting and SDK files used in the last section sit on Blackmagic’s developer and software page. Everything else in this guide uses only what the free edition ships with.
If you are still choosing an editor, our DaVinci Resolve vs Premiere Pro comparison covers price and workflow differences. This page assumes you already picked Resolve and want a clean first edit. The example is a talking-head video with B-roll, a title, music and a 1080p export.
What you need before you start
The table lists the software and files for this build. Resolve versions come from Blackmagic’s own support pages, checked on November 19, 2026. Where a version is not pinned, any current release works.
| Item | Version or spec | Why it matters |
|---|---|---|
| DaVinci Resolve (free) | 21.2 | Current confirmed release, same core editing, color, Fusion and Fairlight pages as Studio |
| DaVinci Resolve Studio (optional) | 21.2 | Adds Voice Isolation, noise reduction, multi-GPU and other paid tools |
| Operating system | Windows, macOS or Linux | Check Blackmagic’s tech specs page for the minimum build and RAM before installing |
| FFmpeg and ffprobe | A current release | Used in steps 1 and 12 to inspect footage and the final file |
| Python 3 | A current 3.x release Resolve can find | Only needed for the scripted project at the end |
| Source footage | 1080p or 4K, 24 to 60 fps | Shot on a camera, phone or screen recorder |
| Free disk space | At least 3 times the size of your clips | Cache, proxies and the export all live beside the originals |
Blackmagic lists the exact RAM, GPU and OS minimums on its tech specs page, and they change between 21.x builds. Read that page for your machine rather than trusting a number in a tutorial. If your computer meets the minimum but still stutters, step 10 on proxies fixes most of it.
Set up a folder layout before you open the app. A fixed structure stops the most common beginner failure, which is moving files after import and ending up with red Media Offline clips. Run this once in a terminal and keep every asset inside it.
mkdir -p ~/Videos/resolve-demo/{01_footage,02_music,03_graphics,04_proxies,05_exports}
ls ~/Videos/resolve-demo
# 01_footage 02_music 03_graphics 04_proxies 05_exports
On Windows, create the same five folders in File Explorer or run the equivalent mkdir calls in PowerShell. The script in the last section expects these exact names, so keep them as written.
Free or Studio: which edition this tutorial assumes
The free edition. Blackmagic’s documentation says it accepts media at any resolution but limits project mastering and output to Ultra HD or lower, and on Windows and Linux it uses one processing GPU. A 1080p or 3840×2160 YouTube upload fits inside that ceiling, so you give up nothing for this project.
| Capability | Free 21.2 | Studio 21.2 |
|---|---|---|
| Edit, Cut, Color, Fusion, Fairlight pages | Included | Included |
| Media import resolution | Unlimited | Unlimited |
| Mastering and output | Ultra HD or lower | Higher output supported |
| Processing GPUs (Windows, Linux) | One | Multiple |
| Voice Isolation | No | Yes |
| Temporal and spatial noise reduction | No | Yes |
| Camera Tracker, HDR tools, extra Resolve FX | No | Yes |
| Surround and immersive audio | No | Yes |
| Price | Free download | Paid, see Blackmagic’s Studio page |
Sources: Blackmagic’s support center and media pages, checked November 19, 2026. Studio features come from the documentation’s Studio-only list. Blackmagic’s 21.1 documentation reportedly describes Studio as a licence sale rather than a monthly subscription.
Prices moved recently. Blackmagic reportedly announced special pricing for Studio on October 20, 2026 and referenced a price increase, and one report put a 20% promotion ending November 20. Reports disagreed on the list price, so this guide gives no figure. Check the Studio product page on the day you buy.
One trap for beginners: using a Studio-only effect inside the free app. Resolve may add a watermark to the render or block it, depending on the tool. If a Studio feature is the only fix for a problem, such as noisy audio, try the free workarounds in step 8 first. Editors weighing Resolve against Apple’s app can read Final Cut Pro against Resolve for the cost trade-off.
Set up the project: steps 1 to 3
Step 1: Check your footage before importing
Run ffprobe on every clip. You want codec, resolution, frame rate and whether the frame rate is constant. Phone clips often record variable frame rate, which is the top cause of audio drifting out of sync on a timeline.
ffprobe -v error -select_streams v:0 \
-show_entries stream=codec_name,width,height,r_frame_rate,avg_frame_rate \
-of default=nw=1 ~/Videos/resolve-demo/01_footage/talking-head.mp4
Illustrative output from a phone clip:
codec_name=h264
width=1920
height=1080
r_frame_rate=30/1
avg_frame_rate=2997/100
When r_frame_rate and avg_frame_rate differ, as above, the clip is variable frame rate. Convert it to constant frame rate with FFmpeg before it reaches Resolve. The command re-encodes video and copies audio, so it takes a while on long clips.
ffmpeg -i talking-head.mp4 -fps_mode cfr -r 30 \
-c:v libx264 -crf 16 -preset slow -c:a copy talking-head-cfr.mp4
Keep the original in a separate archive folder and import only the converted copy. Camera files that report matching values need no conversion. Screen recordings from OBS are normally constant frame rate if you set a fixed value in the recorder.
Step 2: Create the project and match the timeline to your footage
Open Resolve, click New Project in the Project Manager, and name it. Then open File > Project Settings > Master Settings. Set Timeline resolution to 1920 x 1080 HD and Timeline frame rate to the value ffprobe reported, for this example 30. Set Playback frame rate to the same number.
Do this before you add a single clip. Resolve locks the timeline frame rate once the first clip lands on a timeline. If you forget, you can still create a second timeline and untick Use Project Settings in the new timeline dialog, but it is easier to get it right once.
Pick the frame rate from your main footage, not from the platform. YouTube accepts a range of frame rates, and a 30 fps clip placed on a 24 fps timeline produces dropped frames and judder. Mixed sources are fine. Resolve conforms the odd clip, though the result looks best when most clips match the timeline.
Step 3: Import media and sort it into bins
Go to the Media page. In the Media Storage panel, browse to your 01_footage folder, select the clips and drag them into the Media Pool. Repeat for music and graphics. Then create bins with a right-click in the Media Pool and New Bin: Footage, B-roll, Music, Graphics.
Bins cost ten seconds and save you hunting for a clip at hour two. Resolve also offers Smart Bins, which sort clips by metadata such as keyword or resolution. A Smart Bin that collects everything shorter than ten seconds gives you a ready-made B-roll list without manual tagging.
If Resolve asks to change the project frame rate to match a clip, decline when you already set it in step 2. Click through the clip properties once to confirm that each file shows the codec and frame rate you expect. Anything that shows a red icon or no audio waveform needs the checks in the troubleshooting table.
Cut the video: steps 4 to 6
Step 4: Build a rough cut on the Cut page
The Cut page is built for speed. Blackmagic designed it for fast assembly and trimming, with a source tape view that lets you scrub every clip like one long reel. Use it to find the good takes, mark In and Out points, and push clips onto the timeline in order.
Press I and O to mark the part of a take you want, then use the Smart Insert, Append or Ripple Overwrite buttons beneath the viewer to place it. For a talking-head video, drop in the best take of each section and ignore B-roll for now. You are building the spine of the story.
The Edit page is the main detailed workflow and works from the same timeline, so you can swap pages at any point. Many editors skip the Cut page and work only on Edit. Both routes are valid. Pick Cut when you have many short clips and want speed, and pick Edit when you already know the structure and need precise control.
Step 5: Trim and tighten on the Edit page
Switch to the Edit page. Cut dead air first, because pacing does more for a talking-head video than any effect. Learn these default shortcuts and your first edit gets much faster.
- Space: play or pause.
- J, K, L: play in reverse, stop, play forward. Tap L twice for faster playback.
- I and O: set In and Out points on a clip in the Source viewer.
- A: Selection mode. T: Trim Edit mode. B: Blade mode.
- Delete: remove a selected clip and leave a gap. Shift+Delete: ripple delete, which closes the gap.
- N: toggle snapping. M: add a marker.
- Ctrl/Cmd+Z: undo. Ctrl/Cmd+S: save the project.
Splitting a clip at the playhead has a different default key on each operating system. Open the Edit menu and read the shortcut next to Split Clip on your build instead of memorizing one. Shortcuts can change between versions and you can remap them under DaVinci Resolve > Keyboard Customization.
A reliable rhythm for talking-head edits: play at normal speed, split at each pause and false start, ripple delete the bad part, then move on. Leave a few frames of breathing room around cuts so speech does not sound clipped. If two clean takes are adjacent, an L-cut (audio from the next clip starting before the picture changes) hides the join.
Step 6: Layer B-roll and cutaways
Add a second video track by right-clicking the track header and choosing Add Track. Place B-roll on V2 above the talking head on V1. Drag a clip from the Media Pool onto V2 at the moment the speaker mentions the subject. The picture changes while the voice continues underneath.
Hold B-roll shots for a few seconds. Cut away every time the speaker makes a new point or when the framing has stayed the same for too long. Blade the cutaway to length with the Trim tool, then check playback to confirm that the speaker’s words still match the picture. Zoom the timeline with Shift+Z to see the whole project at once.
For picture-in-picture and simple moves, use the Inspector panel. Transform controls cover zoom, position and crop, and keyframes let you add a slow push-in. Keep movement small. A gentle zoom over the length of a shot reads as intentional, and a bigger move reads as a mistake.
Add titles, audio and color: steps 7 to 9
Step 7: Add titles and an intro
Open the Effects Library at the top left, expand Titles and drag Text+ or a Lower Third onto a track above your B-roll. Type the speaker’s name in the Inspector, then adjust font, size and position. Keep titles inside the safe area so platform interface elements do not cover them.
For a short intro, you can build a title card in Resolve or bring in a finished clip. If you want a ready-made animated opener, Vipid’s intro themes page lists the resolution, length and frame rate of each theme, so you can match it to the timeline you set in step 2. Place the intro clip at the head of V1 and push the rest of the edit right with a ripple insert.
Match the style of lower thirds across the whole video. One typeface, one color pair and one animation style looks professional, and three different styles look like a template library. Save your finished title as a Power Bin item so you can drag the same one into your next project.
Step 8: Balance dialogue and music
Drop a music track onto A2 or A3 under the dialogue. Open the Fairlight page for proper audio tools, or stay on Edit and drag the thin level line on each clip. Set dialogue so the loudest peaks sit comfortably below the maximum, then lower the music until speech is clear without effort.
To duck music under speech, add keyframes to the music clip’s level. Place a keyframe before the speaker starts, another just after to lower the volume, and a third where the pause begins to bring the music up again. Keep fades short, typically under a second, so the movement does not distract.
Noisy room tone is the most common audio problem. Voice Isolation is a Studio feature in Blackmagic’s documentation, so the free app cannot use it. The free route is a mix of the Fairlight equalizer (cut the low rumble below the voice), a light noise gate, and recording a few seconds of silence on set to help you judge the room. Fix the source whenever you can.
Pick one loudness target and use it on every upload so viewers do not reach for the volume control between your videos. Resolve’s loudness meter lives in the Fairlight page. Check YouTube’s current help pages for its guidance, because loudness handling on platforms changes and a number remembered from an older guide may be out of date.
Step 9: Fix exposure and color on the Color page
Open the Color page. Resolve’s Color page covers primary correction, shot matching, masks, tracking and node-based grading. For a first edit you need only three controls: the waveform scope, the primary wheels and one extra node for a look.
Start with exposure. On the waveform, the brightest parts of a normal shot should land near the top of the graph without flattening against it, and the darkest parts near the bottom. Drag the Gain wheel up or down for highlights, Lift for shadows, Gamma for midtones. Then fix white balance with the Temperature and Tint sliders until a neutral surface looks neutral.
Match shots before you style them. Right-click a good clip in the gallery or on the timeline thumbnail strip and use Shot Match, or copy a grade from one clip to the next with a middle-click on the target thumbnail. A consistent talking-head video needs every clip to share the same skin tone and brightness. Only then add a gentle contrast curve on a second serial node.
Make it run well: transitions, Fusion and proxies (step 10)
Step 10: Use transitions sparingly and turn on proxies if needed
Hard cuts are the default for talking-head videos. If you need a transition, drag Cross Dissolve from Effects Library > Video Transitions onto a cut between B-roll shots. Default length is short and adjustable by dragging the edges. Avoid wipes and spins unless the channel style calls for them.
The Fusion page is Resolve’s node-based compositor and motion graphics tool, and it exists inside the free app. Beginners can leave it alone. Use it when a title needs custom animation or when you need an effect that Edit page tools cannot handle. Blackmagic positions Fusion as part of the same app, so no export round trip is needed.
Now performance. If playback stutters, make proxies. Right-click clips in the Media Pool, choose Generate Proxy Media and pick a lower resolution and a light codec. Then enable Playback > Proxy Mode and set it to a smaller fraction. The installer also includes Blackmagic Proxy Generator, a separate tool that creates proxies in the background.
Switch proxy mode off before the final render. Resolve renders from the camera originals unless you tell it to use proxy media, but verify the setting on the Deliver page rather than assume. Mixed-camera projects benefit most from checking this, since clips in different formats are the ones that tend to stay linked to a proxy by mistake.
Render Cache is a second tool for heavy timelines. Under Playback > Render Cache, set it to Smart, and Resolve will pre-render sections that struggle in real time, such as stacked effects. Point the cache at a fast drive. Clearing it from the same menu frees space after the project is done.
Export for YouTube: steps 11 and 12
Step 11: Render on the Deliver page
Open the Deliver page. In the Render Settings panel, choose a YouTube preset such as the 1080p one. That fills in format, codec and a sensible bitrate. Then check each field against the table instead of trusting the preset blindly.
Render settings
| Setting | Value used in this tutorial | Note |
|---|---|---|
| Preset | YouTube, 1080p | Starting point, then confirm each field |
| Format | MP4 | Widest compatibility for upload |
| Codec | H.264 | H.265 is available on some systems, but H.264 is the safe default |
| Resolution | 1920 x 1080 | Same as the timeline, no scaling |
| Frame rate | 30 fps | Same as the timeline and the source clips |
| Quality | Automatic, or Restrict to a bitrate you choose | Higher bitrate means a larger file |
| Audio | AAC, stereo | Match the timeline’s audio setup |
| Use proxy media | Off | Render from camera originals |
| Output folder | 05_exports | Keep exports beside the project |
These values are choices for this project, not YouTube requirements. Resolve’s presets are a starting point and not a guarantee. Treat any YouTube bitrate or codec figure dated before September 2026 as unverified until you check YouTube’s own upload encoding page. According to YouTube’s blog post on the September 23, 2026 Made on YouTube event, the new viewer features were Custom Feeds and Ask YouTube. That post covers viewer features and does not point to a change in upload specs.
Pick Entire Timeline in the render range, set the file name and the output folder, then click Add to Render Queue. The job appears on the right. Click Render All and watch the progress bar. Rendering ties up the GPU, so leave other heavy apps closed. When Resolve finishes, the job shows a green tick and the file sits in your export folder.
Color tagging deserves a second look. In the Advanced Settings of the Deliver page, the color space and gamma tags tell players how to display the file. For standard web video, tag it as Rec.709. If colors look slightly different in your browser than in Resolve, the tag is the first suspect. Test in the player your audience uses.
Step 12: Verify the exported file before you upload
Do not upload blind. Play the file from start to end in a regular media player, not Resolve, and watch for audio sync, black frames and glitches at the cuts. Then run ffprobe to confirm that the numbers match the plan.
ffprobe -v error \
-show_entries stream=codec_type,codec_name,width,height,r_frame_rate,bit_rate:format=duration,size \
-of default=nw=1 ~/Videos/resolve-demo/05_exports/main-cut.mp4
Illustrative output from a finished render:
codec_name=h264
codec_type=video
width=1920
height=1080
r_frame_rate=30/1
bit_rate=16000000
codec_name=aac
codec_type=audio
r_frame_rate=0/0
bit_rate=320000
duration=612.400000
size=1233000000
Those numbers are an example, not a promise. What you check is the shape: video is H.264, size is 1920×1080, frame rate is 30/1, audio is AAC, and duration matches the timeline. If any field is off, fix it in the Deliver page and render again. Upload only after the file passes.
Complete working project: script the setup and the render
Everything above can be run by hand. This script automates the repetitive part: it creates a project, sets the timeline to 1920×1080 at 30 fps, imports your footage and music into bins, builds a timeline, puts the music on its own audio track, finds a YouTube 1080p render preset, and renders to 05_exports. It uses Resolve’s Python scripting API.
Where to run it matters. Resolve runs scripts from Workspace > Scripts in both editions. Scripting from outside the app is documented as a Studio feature in the versions we know of, so read the scripting readme that ships with your install before you try it from a terminal. Save the file as build_youtube_project.py in the Scripts folder for your system:
# Windows
%APPDATA%\Blackmagic Design\DaVinci Resolve\Support\Fusion\Scripts\Edit
# macOS
~/Library/Application Support/Blackmagic Design/DaVinci Resolve/Fusion/Scripts/Edit
# Linux
~/.local/share/DaVinciResolve/Fusion/Scripts/Edit
Restart Resolve, then look under Workspace > Scripts > Edit. If the entry is missing, the folder path is wrong or Resolve cannot find a Python 3 install. Part one of the script builds the project and the timeline:
import os
import time
try:
resolve # defined when launched from Workspace > Scripts
except NameError:
import DaVinciResolveScript as dvr
resolve = dvr.scriptapp("Resolve")
PROJECT_NAME = "yt-tutorial-demo"
TIMELINE_NAME = "main-cut"
ROOT = os.path.expanduser("~/Videos/resolve-demo")
FOOTAGE = os.path.join(ROOT, "01_footage")
MUSIC = os.path.join(ROOT, "02_music")
EXPORTS = os.path.join(ROOT, "05_exports")
WIDTH, HEIGHT, FPS = "1920", "1080", "30"
VIDEO_EXT = (".mp4", ".mov", ".mkv")
AUDIO_EXT = (".wav", ".mp3", ".flac")
def files_in(folder, exts):
if not os.path.isdir(folder):
return []
names = sorted(n for n in os.listdir(folder) if n.lower().endswith(exts))
return [os.path.join(folder, n) for n in names]
def build_timeline():
manager = resolve.GetProjectManager()
project = manager.LoadProject(PROJECT_NAME) or manager.CreateProject(PROJECT_NAME)
if project is None:
print("Could not create or load the project")
return None
project.SetSetting("timelineResolutionWidth", WIDTH)
project.SetSetting("timelineResolutionHeight", HEIGHT)
project.SetSetting("timelineFrameRate", FPS)
project.SetSetting("timelinePlaybackFrameRate", FPS)
pool = project.GetMediaPool()
root = pool.GetRootFolder()
footage_bin = pool.AddSubFolder(root, "Footage")
music_bin = pool.AddSubFolder(root, "Music")
pool.SetCurrentFolder(footage_bin)
clips = pool.ImportMedia(files_in(FOOTAGE, VIDEO_EXT))
pool.SetCurrentFolder(music_bin)
tracks = pool.ImportMedia(files_in(MUSIC, AUDIO_EXT))
if not clips:
print("No video clips found in " + FOOTAGE)
return None
timeline = pool.CreateTimelineFromClips(TIMELINE_NAME, clips)
project.SetCurrentTimeline(timeline)
if tracks:
timeline.AddTrack("audio", "stereo")
pool.AppendToTimeline([{
"mediaPoolItem": tracks[0],
"mediaType": 2,
"trackIndex": 2,
}])
manager.SaveProject()
return project
Part two picks the preset, queues the job, waits for it and prints the final status. Append it to the same file:
def pick_preset(project):
for name in project.GetRenderPresetList() or []:
lowered = name.lower()
if "youtube" in lowered and "1080" in lowered:
return name
return None
def render(project):
os.makedirs(EXPORTS, exist_ok=True)
preset = pick_preset(project)
if preset:
project.LoadRenderPreset(preset)
print("Preset: " + preset)
else:
print("No YouTube 1080p preset found, using current render settings")
project.SetRenderSettings({
"SelectAllFrames": True,
"TargetDir": EXPORTS,
"CustomName": TIMELINE_NAME,
})
job_id = project.AddRenderJob()
if not job_id:
print("Could not add a render job, check the timeline and settings")
return
project.StartRendering(job_id)
while project.IsRenderingInProgress():
status = project.GetRenderJobStatus(job_id)
print("Progress: " + str(status.get("CompletionPercentage", 0)) + " percent")
time.sleep(5)
print("Final status: " + str(project.GetRenderJobStatus(job_id)))
proj = build_timeline()
if proj is not None:
render(proj)
What a successful run looks like in the Console (Workspace > Console):
Preset: YouTube - 1080p
Progress: 0 percent
Progress: 38 percent
Progress: 77 percent
Final status: {'JobStatus': 'Complete', 'CompletionPercentage': 100}
That output is an example of the format. Your preset name may differ on your build, which is why the script searches the preset list instead of hard-coding it. Treat the first run as a dry run on a short test clip. Then open the project and check the music track, because API behavior around audio tracks has changed between Resolve versions. Finish by running the ffprobe check from step 12 on the output.
The script sets up a clean first cut. It does not trim, color or mix for you. Think of it as the boring ten minutes of every project, done identically every time. That is the point of scripting in Resolve for a small channel: same frame rate, same bins, same export folder, no clicks to forget.
Common pitfalls that waste a first edit
These six mistakes account for most beginner support threads. Each has a cheap prevention.
- Setting the frame rate after adding clips. Resolve locks the timeline frame rate with the first clip. Set it in Project Settings before importing, as in step 2.
- Importing variable frame rate phone footage. Audio drifts and cuts land late. Convert to constant frame rate first, as in step 1.
- Moving files after import. Resolve links to files on disk and does not copy them. Move a folder and every clip goes red. Keep the folder layout fixed.
- Rendering with proxy media on. The export looks soft and blocky. Switch proxy mode off and untick proxy use on the Deliver page.
- Using Studio-only effects in the free app. The render may carry a watermark or fail. Check the Resolve FX list and the Studio-only list before you build a look around a tool.
- Skipping the post-export check. A render can finish and still hold a glitch at hour one. Watch the whole file in a normal player before you upload.
A seventh trap is autosave. Resolve can keep project backups and timeline auto-saves, but they only help if you turned them on. Open Preferences > User > Project Save and Load, enable live save and project backups, and point backups at a drive other than the one holding the footage. A crash costs minutes instead of hours.
An eighth, less obvious one is editing on the wrong page. The Fusion page changes a clip for compositing and the Color page changes it for grading. Neither is the place to trim. Do trimming on Cut or Edit, and effects on Fusion only when needed. Mixing jobs across pages is how timelines grow tangled.
Troubleshooting: 10 problems and their fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Clip shows red Media Offline | File moved, renamed or on an unplugged drive | Reconnect the drive or right-click the clip and use Relink Selected Clips |
| Imported clip has video but no sound | Audio codec Resolve cannot decode on your system | Check Blackmagic’s supported codec list and transcode the audio to WAV or AAC with FFmpeg |
| Black frame or no picture for H.265 clips | The system lacks an HEVC decoder or GPU support | Install the operating system’s HEVC decoder or transcode to H.264 or an intermediate codec |
| Playback stutters or drops frames | Heavy codec, weak GPU or slow drive | Generate proxy media, set Render Cache to Smart, move cache to a fast drive |
| Audio drifts out of sync over time | Variable frame rate source | Convert to constant frame rate with FFmpeg and re-import |
| Black bars or cropped picture on export | Clip resolution differs from timeline and scaling mode does not suit | Open Project Settings > Image Scaling and choose scale to fit, fill or stretch, or set the clip’s Inspector zoom by hand |
| Export looks soft or blocky | Proxy media used for the render, or a low bitrate | Turn proxy mode off, untick proxy use on Deliver, raise the quality setting |
| Colors differ from Resolve in the browser | Color space or gamma tag mismatch | Set the tag to Rec.709 in Advanced Settings and compare in the player your viewers use |
| Render fails partway or stops | Full disk, GPU memory pressure or a corrupt clip | Free disk space, close other GPU apps, check the Console log, then render in chunks to find the bad clip |
| Script missing from Workspace > Scripts | Wrong folder, file not saved as .py or Python 3 not found | Match the path for your OS, restart Resolve, and install a current Python 3 |
When none of these fits, open Workspace > Console and read the last lines after reproducing the issue. Resolve logs the cause there for many import, render and script failures. Blackmagic’s support documentation lists where the log files live on each operating system, and attaching one makes a forum question much easier to answer.
If an update changed behavior, compare the version number on the About screen with the one in the support center. Blackmagic ships point releases often. Version 21.1.2, for example, reportedly touched trim selection, loudness meters, Quick Export and Magic Mask cache use, and 21.2 followed with its own set of fixes. Update on a gap between projects, never in the middle of one.
What changed in Resolve 21 and what older tutorials get wrong
Most video tutorials for Resolve were recorded on version 18, 19 or 20. The page structure, the Media, Cut, Edit, Fusion, Color, Fairlight and Deliver pages, is unchanged and the steps above still apply. What differs is the detail. Menu labels can shift between 21.x builds, and some panels moved.
Blackmagic describes the 21 generation as adding AI-assistant integration, expanded still-photography support and more than 100 tools and controls. The still-photography work shows up as a new Photo page in the page bar. For a YouTube edit you can ignore it. It matters if you cut thumbnails or photo montages in the same project and want to grade stills without leaving the app.
Point releases since 21 cover hardware and workflow details. According to Blackmagic’s readme, 21.2 reportedly added support for new Apple MacBook Pro XDR touch-screen models and Blackmagic Gen 6 LUTs. It also keeps source timecode for extracted audio, expands multicam and source timeline behavior, and reads PNG EXIF metadata. Most beginners will not notice any of it. Install it anyway, because the same release lists stability fixes for imports, rendering and audio.
Beware of version mix-ups when you search. Blackmagic’s older promotional pages still show 20.2 material, and some pages and reports mention 21.1 as the newest, while the support documentation names 21.2. Trust the support center and the About screen in your own install. If a tutorial title says Resolve 20, the workflow is fine but the screenshots will not match your window exactly.
One more recent change is branding noise. The free product and the paid product are both named DaVinci Resolve 21.2, with Studio as the paid edition. Blackmagic has not renamed, retired or merged either one, so a search for a separate cheaper tier will find nothing official. For a channel that only needs 1080p or Ultra HD output, the free app stays the right starting point.
Advanced tips once the first video is out
Build a template project. Save a finished timeline as a project template with your bins, title styles, music track layout and render preset already in place. Next video, you open the template, drop in the footage and skip the setup. The script from the last section does the same job in code and is easier to share with a second editor.
Make your own render preset. After you tune the Deliver page once, click the three-dot menu and choose Save as New Preset. It then appears next to the built-in YouTube presets, and the script can load it by name. A custom preset also protects you if Blackmagic renames its built-in ones in a later update.
Use Quick Export for drafts. Resolve’s Quick Export button on the Edit and Cut pages renders a file with a chosen preset in a couple of clicks, without touching the Deliver queue. It suits review copies for a client or a friend, while the full Deliver page remains the route for the master you upload.
Keep a motion-graphics habit. A short animated sting at the start, built once and reused, gives a channel a recognizable open. Vipid’s animated logo intro page shows one example of how a logo sting is specified. For related guides, browse the editing software guides.
Add a second pass for captions and loudness. Subtitles go on a dedicated track in Edit. Export an SRT from Resolve if you want to upload captions to YouTube separately. Then play the final export with the sound on a phone speaker, because most viewers listen on one. If the dialogue is clear there, it is clear almost everywhere.
Finally, back up before you delete. Export the project as a DRP file, archive the original footage, and keep the final MP4 and the project file together. A project archive from Resolve can bundle the media for a handoff. Disks fail, and a re-edit from backup beats a re-shoot every time.
Common questions
Is DaVinci Resolve free for YouTube videos?
Yes. The free edition includes the Cut, Edit, Fusion, Color and Fairlight pages, accepts media at any resolution and outputs up to Ultra HD. That covers 1080p and 3840×2160 uploads. Studio adds paid features such as Voice Isolation and noise reduction, which you can skip on a first channel.
Which version should I download in November 2026?
Download 21.2, the newest confirmed release for both the free app and Studio. Older pages still show 20.x material, so use Blackmagic’s support center and your install’s About screen to confirm the version.
Should I use the Cut page or the Edit page?
Either. The Cut page suits fast assembly from many clips, and the Edit page gives full control for trimming, titles and audio. Both work on the same timeline, so you can start on Cut and finish on Edit.
What export settings should I use for YouTube?
Start with a YouTube preset on the Deliver page, MP4 with H.264, a resolution and frame rate that match your timeline, and AAC audio. Then confirm the bitrate against YouTube’s current upload guidance, since older numbers online may be stale.
Why does my export look different from the timeline?
The usual causes are proxy media used in the render and a color space tag that differs from what your player assumes. Turn proxies off, set a Rec.709 tag in Advanced Settings and compare in the player your viewers use.
Can I script Resolve with the free version?
You can run scripts from Workspace > Scripts inside the app. Controlling Resolve from an outside terminal is documented as a Studio feature in the versions we know of, so check the scripting readme that ships with your install.
How long does a first edit take?
Plan an afternoon for a first ten-minute video. Most of that time goes on trimming and audio, not on learning the interface. The second video goes much faster once your project template and render preset exist.
More from the Vipid blog
- Lower Thirds Examples [2026]: 6 Styles, 5 Editors
- Adobe Premiere Pro to Resolve [2026]: CornerCut, $0 Beta
- Vipid intro themes resolution, length and frame rate per theme
- Promo themes product and channel promos
- Sample videos finished Vipid intros
- Vipid intro maker make a custom intro in the browser
Jonah Reyes
Jonah Reyes is the Editing & Export Editor at Vipid. He covers editing software, export settings and codecs, and the video specs of YouTube, Shorts, TikTok and Reels, plus OBS and screen recording. He builds Vipid’s spec tables from the platforms’ own documentation and re-checks them every 60 to 90 days, so the numbers in a guide match what the upload dialog actually accepts.

![Final Cut Pro 13 [2026]: MotionVFX Joins at $129/Yr](https://ivipid.com/blog/wp-content/uploads/2026/11/final-cut-pro-13-motionvfx-apple-creator-studio-2026-gen-800x450.webp)
![Adobe Premiere AI Color Match [2026]: 30 Credits a Pass](https://ivipid.com/blog/wp-content/uploads/2026/11/adobe-premiere-ai-assistant-color-matching-2026-gen-800x450.webp)