# DaVinci Resolve Club: Tutorials, Fixes & Workflow Guides > Hands-on DaVinci Resolve tutorials: editing, color grading, Fusion, Fairlight audio and export settings, tested in both the free version and Studio. Public Ghost content for AI and LLM tooling. This file includes a bounded export of public pages first, then recent public posts. Append `.md` to any post or page URL to get the content in Markdown (for example, `/example-post.md`). ## Pages ### About Jason Miller URL: https://davinciresolveclub.com/about/ Last updated: 2026-09-08T21:13:59.000Z DaVinci Resolve Club is an independent publication for people editing video in Resolve. The guides cover editing, color, Fusion, Fairlight, export and the problems that interrupt a project. The aim is simple: help you choose the next step and know what to check afterward. ## The editorial byline Guides are published under the [Jason Miller byline](https://davinciresolveclub.com/author/jason/). That profile collects the articles; this page explains the editorial standard behind them. The site is not Blackmagic Design's official documentation or support service. ## Evidence, not a testing badge Our editorial standard separates a documented product fact from a hands-on result. Release notes, manuals and [Blackmagic Design's support material](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) are the reference for version changes, controls and edition limits. A hands-on claim needs a recorded test, including the version, platform and conditions. Reading a manual is not the same as running that test. Community reports can help identify a possible failure pattern. They are not proof that every machine has the same fault. Likewise, a newer update date does not mean every workflow was retested on Windows, Mac, Linux, Free and Studio. Guide images should help you locate a control or understand a decision. An illustration or annotated interface is not evidence of a measured performance result. Instructions and limitations still need to be clear in the text. ## Report a correction Found a wrong step? Email [hello@davinciresolveclub.com](mailto:hello@davinciresolveclub.com) with the article URL, Resolve version, operating system, Free or Studio edition, and the exact error or menu label. A short description of how to reproduce the problem helps. Do not send license keys, passwords, client footage or private project files. The correction standard is to fix the passage and check any FAQ answer, structured data or related guide that repeats it. For software support rather than an article correction, follow the guidance on the [contact page](https://davinciresolveclub.com/contact/). ## Commercial disclosures Some links may earn the site a commission if you buy through them. Our editorial rule is that paid placements, affiliate relationships and supplied products must be disclosed where they affect a recommendation. Payment is not a reason to conceal a limitation or leave a factual error uncorrected. ## Find a guide Making your first edit? Start with the [learning path](https://davinciresolveclub.com/davinci-resolve-tutorial/). If something has stopped working, the [troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/) sorts guides by the problem you see. ### Privacy URL: https://davinciresolveclub.com/privacy/ Last updated: 2026-09-08T21:25:55.000Z This policy covers davinciresolveclub.com. The site uses Ghost hosting, Google Analytics and a third-party search script. Reading a public guide does not require an account, but visiting a page still sends technical information to the services that deliver and measure it. ## Hosting and search Ghost hosts the site and its images. Requests can include your IP address, browser information and the requested URL. See [Ghost's privacy policy](https://ghost.org/privacy/?ref=davinciresolveclub.com) for its handling of technical data. The search interface loads code from jsDelivr, so your browser also connects to that provider. Its [privacy policy](https://www.jsdelivr.com/terms/privacy-policy?ref=davinciresolveclub.com) applies to those requests. ## Google Analytics Google Analytics 4 is connected to measure visits and interactions. It can receive page addresses, referring pages, browser and device information, and identifiers used to distinguish visits. The Google tag currently loads when a page opens; this site does not currently provide an on-page analytics consent selector. In a fresh-browser check, the site set `_ga` and `_ga_VRN3WGP3WC` cookies. Google's [GA4 cookie documentation](https://support.google.com/analytics/answer/11397207?hl=en&ref=davinciresolveclub.com) explains their user and session purposes. Cookie expiry and server-side data retention are different settings; browser limits can also shorten a cookie's lifetime. This policy does not promise a fixed deletion date for all analytics data. Google explains its processing and available controls in [how it uses information from partner sites](https://policies.google.com/technologies/partner-sites?ref=davinciresolveclub.com). Ghost's separate native web analytics is described by Ghost as cookie-free; that does not make the additional Google Analytics integration cookie-free. ## Your browser controls You can clear or block cookies in your browser and use tracking protection. Blocking cookies alone does not necessarily stop analytics requests. Google's [Analytics opt-out add-on](https://tools.google.com/dlpage/gaoptout/?ref=davinciresolveclub.com) is another option for supported desktop browsers; it does not block every other service. Private browsing is not a guarantee that a website receives no data. ## Email and external links If you email the site, the address and information you provide are part of that correspondence. Do not send passwords, license keys, private footage or confidential project files. Following an external or affiliate link takes you to another provider whose privacy practices apply there. ## Privacy requests For questions about your data, or a request to access, correct or delete information you have sent us, contact [hello@davinciresolveclub.com](mailto:hello@davinciresolveclub.com). Describe the request without attaching identity documents or other sensitive records. Updated September 9, 2026. ### Contact URL: https://davinciresolveclub.com/contact/ Last updated: 2026-09-08T21:40:30.000Z For corrections, guide requests or questions about a source, email [hello@davinciresolveclub.com](mailto:hello@davinciresolveclub.com). DaVinci Resolve Club is an independent publication, not Blackmagic Design support. ## Report an error Include the article URL, your Resolve version, operating system, Free or Studio edition, and the exact step or claim that looks wrong. Tell us what you expected and what happened instead. If the issue depends on footage, include its format, codec, bit depth and frame rate if known. Remove private file paths and personal details from any diagnostic text. A short sequence that reproduces the problem is more useful than a large project archive. ## Request a guide or source Describe the task you want to finish and where you got stuck. For a source question, quote the relevant sentence and include the page URL. Our [editorial standards](https://davinciresolveclub.com/about/) explain the difference between a documented product fact and a hands-on test. ## Software support This inbox is for the publication. It is not a project-recovery or remote-support service. For activation, crashes or other software faults, use [Blackmagic Design's Support Center](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) to find the current support and forum routes. Do not rely on an editorial email for an urgent production problem. ## Protect private information Do not send passwords, license keys, client footage, confidential files or identity documents. For questions about information you have shared with the site, see the [privacy policy](https://davinciresolveclub.com/privacy/). ### DaVinci Resolve Color Grading: Where to Start URL: https://davinciresolveclub.com/davinci-resolve-color-grading/ Last updated: 2026-09-15T10:51:36.000Z Build a dependable grade ## Set the pipeline, then shape the image Start by identifying the footage and the intended output. Choose your color-management path before balancing shots or adding a look. The first six guides cover the foundations; open the groups below when you need to reuse a grade, work with stills or isolate part of a shot. Choose the task ## Learn the tools in a useful order Follow the beginner walkthrough, or go straight to the part of the grade that needs attention. [ ![How to color grade in DaVinci Resolve, a beginner's complete walkthrough](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/How-to-Color-Grade-in-DaVinci-Resolve--Beginner-Tutorial.jpeg) 11 min read How to Color Grade in DaVinci Resolve: Beginner Tutorial Set up the color pipeline, balance the image and match the sequence before building a look. Work through a small node tree and review selective corrections in motion. ](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/)[ ![DaVinci Resolve RCM and CST color pipelines mapping camera log through a wide-gamut grade to Rec.709](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-color-management-cover.webp) 9 min read DaVinci Resolve Color Management: RCM vs CST & LUT Order Compare project-based Resolve Color Management with Color Space Transform nodes. Follow input, working and output spaces, then diagnose double transforms and misplaced LUTs. ](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/)[ ![DaVinci Resolve Scopes Explained: How to Read Every Scope](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/DaVinci-Resolve-Scopes-Explained--How-to-Read-Every-Scope.jpeg) 13 min read DaVinci Resolve Scopes Explained: How to Read Every Scope Choose a scope for the question: exposure, channel balance, saturation or gamut. Read the image alongside the measurements instead of chasing a universal target. ](https://davinciresolveclub.com/davinci-resolve-scopes-explained/)[ ![DaVinci Resolve Color page node graph showing order, parallel branches and a labeled grading workflow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/nodes-explained-cover-v2.webp) 12 min read DaVinci Resolve Nodes Explained Follow image and key connections through serial nodes and mixers. Keep the tree readable and find the operation that changed the result. ](https://davinciresolveclub.com/davinci-resolve-nodes-explained/)[ ![How to install and use LUTs in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/How-to-Use-LUTs-in-DaVinci-Resolve.jpeg) 10 min read How to Use LUTs in DaVinci Resolve Install and apply a LUT, check its expected input and output, and place it deliberately. Diagnose missing LUTs, excessive contrast and unwanted double transforms. ](https://davinciresolveclub.com/how-to-use-luts-in-davinci-resolve/)[ ![DaVinci Resolve Auto Color A button with before and after frame and RGB parade](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-auto-color-guide.webp) 10 min read DaVinci Resolve Auto Color: How It Works, When It Fails Compare automatic balancing with the original frame and the scopes. Decide when a white-balance reference, Shot Match or Color Match better fits the problem. ](https://davinciresolveclub.com/davinci-resolve-auto-color/) Match shots, reuse grades and work with stills3 guides [ ![How to copy a color grade between clips and projects in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/How-to-Copy-a-Color-Grade-in-DaVinci-Resolve.jpeg) 13 min read How to Copy a Color Grade in DaVinci Resolve Choose between replacing a whole grade, appending saved nodes or sharing a correction. Check what the destination clip already contains before pasting. ](https://davinciresolveclub.com/copy-color-grade-davinci-resolve/)[ ![DaVinci Resolve 21 Shot Matching between reference and target clips with scopes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-shot-matching-cover.webp) 10 min read DaVinci Resolve Shot Matching: Match Clips Correctly Choose a useful reference and bring clips into comparable image states. Evaluate the match with split screen and scopes instead of assuming copied settings will match shots. ](https://davinciresolveclub.com/davinci-resolve-shot-matching/)[ ![DaVinci Resolve 21 Photo Page: Full Walkthrough](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/06/DaVinci-Resolve-21-Photo-Page--Full-Walkthrough.jpeg) 11 min read DaVinci Resolve 21 Photo Page: Full Walkthrough Organize stills in albums, compare grade versions and move between Photo and Color tools. Check the separate Studio and tethered-capture requirements for your workflow. ](https://davinciresolveclub.com/davinci-resolve-21-photo-page/) Isolate a subject or repair part of the frame3 guides [ ![DaVinci Resolve 21 Magic Mask 2 isolating a subject with click tracking and Better-mode Smart Refine](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-magic-mask--feature-v2.webp) 10 min read DaVinci Resolve Magic Mask: Resolve 21 Guide Use Studio’s Magic Mask to isolate a subject. Track through the shot, repair missed frames and inspect difficult edges before grading inside or outside the selection. ](https://davinciresolveclub.com/davinci-resolve-magic-mask/)[ ![Tracked face blur and background blur in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/blur-face-background-davinci-resolve--feature-v1.webp) 9 min read How to Blur a Face or Background in Resolve Track a face blur or separate a subject from the background. Check drift, occlusion and recognizability across the complete output, not just a paused frame. ](https://davinciresolveclub.com/blur-face-background-davinci-resolve/)[ ![DaVinci Resolve Object Removal workflow replacing a tracked unwanted object](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/remove-objects-davinci-resolve.webp) 9 min read Remove Objects in DaVinci Resolve: Object Removal Guide Assess the available background before using Studio’s Object Removal. Compare a generated fill, a patch and a manual clean plate, then inspect flicker and visible seams. ](https://davinciresolveclub.com/remove-objects-davinci-resolve/) Before you start ## Get the foundations straight ### Should I decide color management before grading? Yes. Identify the source footage, working color space and intended output before building the grade. That gives you a clear place for technical conversions and helps you avoid applying the same conversion twice. ### Do I need Studio to start color grading? No. Resolve Free includes the core tools needed to learn color correction. Advanced features such as Magic Mask and Object Removal require Studio; check the feature requirements before following one of those workflows. Blackmagic’s [Color page overview](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com) explains the tools, and its [Studio feature list](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) helps separate edition-specific effects. For structured practice, the [official Colorist Guide](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com) includes lesson files. The currently listed book is for Resolve 20; check newer controls against your installed version. ### DaVinci Resolve Export Settings: The Complete Hub URL: https://davinciresolveclub.com/davinci-resolve-export-settings/ Last updated: 2026-09-13T10:45:54.000Z Plan the delivery ## What needs to leave the timeline? A YouTube upload, client master, audio mix and transparent overlay need different checks. Start with the file the recipient needs, then choose a guide. A familiar preset is a starting point, not proof that the job is ready. Choose the task ## Export the right file Start with the full walkthrough or pick a specific delivery. The last two guides help when the render fails or the picture changes. [ ![How to Export Video in DaVinci Resolve 21](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/06/How-to-Export-Video-in-DaVinci-Resolve.jpeg) 10 min read How to Export Video in DaVinci Resolve 21 Choose Quick Export or work through the Deliver page. Set the output, range and file location, then check the queued job and the finished video. ](https://davinciresolveclub.com/export-video-davinci-resolve/)[ ![DaVinci Resolve YouTube Export Settings](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/cover-corrected-3.webp) 9 min read DaVinci Resolve YouTube Export Settings Use the SDR bitrate guidance for your resolution and frame rate. Check audio, color tags and upload processing without applying SDR settings to an HDR delivery. ](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/)[ ![Audio-only export settings on the DaVinci Resolve Deliver page](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/export-audio-davinci-resolve--feature-v1.webp) 9 min read How to Export Audio Only in DaVinci Resolve Export one finished mix or plan separate stems. Check the output bus, channel layout and range before deciding which audio format the recipient needs. ](https://davinciresolveclub.com/export-audio-davinci-resolve/)[ ![DaVinci Resolve subtitle track with timed caption cues and three delivery options](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-subtitles-cover.webp) 10 min read DaVinci Resolve Subtitles: Create, Style, Import & Export Create or import captions, adjust timing and choose the delivery: a separate SRT, supported embedded captions or text burned into the picture. ](https://davinciresolveclub.com/davinci-resolve-subtitles-captions/)[ ![DaVinci Resolve transparent video export with a checkerboard alpha background and RGBA output file](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-transparent-alpha-cover.webp) 9 min read Export Transparent Video in DaVinci Resolve (Alpha) Confirm real transparency, choose an alpha-capable output and check the result over another background. Diagnose missing alpha, black playback and edge artifacts. ](https://davinciresolveclub.com/davinci-resolve-export-transparent-background/)[ ![DaVinci Resolve timeline reframed for landscape, vertical and square video](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/change-aspect-ratio-davinci-resolve--feature-v1.webp) 9 min read Change Resolution and Aspect Ratio in DaVinci Resolve Separate timeline size, output size and clip reframing. Prepare a vertical, square or widescreen version without overlooking cropped subjects, titles or captions. ](https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/)[ ![DaVinci Resolve Render Failed](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/DaVinci-Resolve-Render-Failed.jpeg) 10 min read DaVinci Resolve Render Failed Match the actual error or stalled job to a focused diagnostic. Isolate the failing section and check the relevant media, Fusion, GPU or storage problem. ](https://davinciresolveclub.com/davinci-resolve-render-failed/)[ ![DaVinci Resolve viewer compared with a washed-out rendered file and waveform scopes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/washed-out-export-cover.webp) 9 min read DaVinci Resolve Export Looks Washed Out: Fix Color & Gamma Compare the reimported file with the timeline, then check the player or upload. Separate color management, data levels and tags before changing the grade. ](https://davinciresolveclub.com/davinci-resolve-export-looks-washed-out/) Before you render ## Check the job, then the file ### Is MP4 the best format for every export? No. An upload, client master and VFX handoff can have different format, codec, audio and transparency requirements. Follow the destination guidance or written delivery specification rather than treating one preset as universal. ### Can the preflight checker inspect my Resolve project? No. It compares settings you enter and records checks you confirm. It cannot inspect the project, media or rendered file. Review the queued job yourself, then play and check the actual output after rendering. Use the [manual export preflight checker](https://davinciresolveclub.com/davinci-resolve-export-preflight-checker/) to review your settings before starting. Blackmagic’s [delivery overview](https://www.blackmagicdesign.com/products/davinciresolve/media?ref=davinciresolveclub.com) explains Quick Export and the Render Queue; YouTube’s [encoding recommendations](https://support.google.com/youtube/answer/1722171?hl=en&ref=davinciresolveclub.com) separate SDR and HDR uploads. ### DaVinci Resolve Fusion: Nodes Without the Pain URL: https://davinciresolveclub.com/davinci-resolve-fusion/ Last updated: 2026-09-15T16:59:29.000Z Build the shot ## Start with one small composite Need text to follow a wall, a background replaced or two takes combined? Choose that result first. Fusion connects effects through nodes; the beginner guide walks through three small projects. A simple title or crop may be easier to finish on the Edit page. Choose the task ## Learn nodes, then solve the shot Start with the basics or choose the effect you need. Open the groups below for masks, delivery and reusable templates. [ ![DaVinci Resolve Fusion beginner tutorial with a tracked wall title and Text+ to Planar Transform node workflow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/fusion-cover-ports-v2.webp) 10 min read DaVinci Resolve Fusion Tutorial for Beginners Follow MediaIn, Merge and MediaOut through a tracked title, green-screen composite and animated lower third. Find where an invisible result stops reaching the timeline. ](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/)[ ![DaVinci Resolve 21 Delta Keyer settings with accurate Fusion Inspector and node graph](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/cover-corrected-6.webp) 12 min read DaVinci Resolve Delta Keyer: Complete Settings Guide Work from screen selection to the matte, edge detail and spill. Judge the key over the replacement background, not just against the checkerboard. ](https://davinciresolveclub.com/davinci-resolve-delta-keyer/)[ ![Planar tracking grid attaching a graphic to a concrete wall in Fusion](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/fusion-tracking-davinci-resolve--feature-v1.webp) 10 min read DaVinci Resolve Fusion Tracking: Point, Planar & 3D Match the tracker to the shot: a 2D feature, a plane or a camera move. Check drift, occlusion and how the insert follows the recorded motion. ](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/)[ ![Multiple Fusion roto shapes isolating a running subject and producing a clean matte](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/rotoscoping-davinci-resolve-fusion--feature-v1.webp) 11 min read DaVinci Resolve Rotoscoping: Polygon, B-Spline & MultiPoly Break a moving subject into manageable shapes. Adjust key poses where the outline changes, then review the matte and the finished composite in motion. ](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/)[ ![DaVinci Resolve 21 clone effect with locked camera, stacked V1 V2 takes and Inspector Cropping](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/cover-corrected-2.webp) 11 min read How to Clone Yourself in DaVinci Resolve (Clone Effect) Plan separate takes and combine them without an obvious seam. Compare a locked-camera crop with masking, overlapping actions and a moving-camera composite. ](https://davinciresolveclub.com/clone-yourself-davinci-resolve/)[ ![DaVinci Resolve stabilization guide comparing Translation, Similarity and Perspective modes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/09/davinci-resolve-stabilization-cover-corrected.png) 9 min read Stabilize Video in DaVinci Resolve: Edit, Color & Fusion Compare the Edit and Color stabilizer with targeted Fusion tracking. Watch the crop, edge movement and image distortion before accepting the result. ](https://davinciresolveclub.com/davinci-resolve-stabilize-video/) Isolate a subject or shape the frame3 guides [ ![Magic Mask isolating a moving subject in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/feature-magic-mask-1.png) 10 min read DaVinci Resolve Magic Mask: Resolve 21 Guide Use Studio’s subject-isolation tools when manual shapes are not a good fit. Check missed limbs, difficult edges and frames where the selection changes. ](https://davinciresolveclub.com/davinci-resolve-magic-mask/)[ ![Tracked face blur and background blur in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/feature-blur.png) 9 min read How to Blur a Face or Background in Resolve Track a face or separate a subject from the background. Check the entire output; adding a blur effect does not by itself guarantee anonymity. ](https://davinciresolveclub.com/blur-face-background-davinci-resolve/)[ ![Video frame changing from square to rounded corners in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/round-corners-davinci-resolve--feature-v1.webp) 9 min read How to Round Corners in DaVinci Resolve Build a rounded frame and keep its corners consistent while resizing. Check the mask connection, borders and whether the final output needs transparency. ](https://davinciresolveclub.com/round-corners-davinci-resolve/) Export, compare and reuse your work3 guides [ ![DaVinci Resolve transparent video export with a checkerboard alpha background and RGBA output file](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-transparent-alpha-cover.webp) 9 min read Export Transparent Video in DaVinci Resolve (Alpha) Check for real alpha and a compatible output format. Reimport the render over another background to distinguish transparency from a player showing black. ](https://davinciresolveclub.com/davinci-resolve-export-transparent-background/)[ ![Fusion node graph versus After Effects layer timeline comparison](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/fusion-vs-after-effects-cover.webp) 10 min read Fusion vs After Effects in 2026 Compare shot compositing, motion design, templates and handoff requirements. Choose by the work you need to deliver, not an assumed winner on speed. ](https://davinciresolveclub.com/fusion-vs-after-effects/)[ ![DaVinci Resolve 21 Fusion node tree converted into a reusable macro with custom controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-fusion-macros-cover.webp) 9 min read DaVinci Resolve Fusion Macros and Templates: Build, Save, Install Choose a macro, group or Edit-page template. Expose useful controls, save to the intended destination and diagnose a template that does not appear. ](https://davinciresolveclub.com/davinci-resolve-fusion-macros-templates/) Before you start ## Which Fusion are you using? ### Is the Fusion page a separate app? No. The Fusion page is built into DaVinci Resolve. Fusion Studio is a separate application. The guides here focus on working inside Resolve unless they explicitly compare the two. ### Do I need Studio before learning nodes? No. You can start learning node-based compositing in Resolve Free. Some advanced tools require Studio, so check the feature requirements before following a particular effect workflow. Blackmagic’s [Fusion overview](https://www.blackmagicdesign.com/products/davinciresolve/fusion?ref=davinciresolveclub.com) explains the built-in tools. If you prefer a longer course with practice material, use the [official visual-effects training](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com). The listed visual-effects books are for Resolve 20; check newer controls against your installed version. ### Fairlight Audio in DaVinci Resolve URL: https://davinciresolveclub.com/davinci-resolve-fairlight-audio/ Last updated: 2026-09-15T15:29:26.000Z Make the dialogue work ## Start with what you can hear Balance the voices before chasing a loudness number. If the problem is noise, buried dialogue or silence, choose that task below. You do not need to add every processor to every recording. Choose the task ## Build and check your mix Start with levels, routing or the sound you want to improve. Open the groups below for more audio tasks. [ ![Fairlight loudness meters showing peaks and LUFS on a finished mix](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-audio-levels-lufs--feature-v1.webp) 8 min read Audio Levels and LUFS in DaVinci Resolve Balance the mix, distinguish peaks from loudness and measure the correct delivery range. Choose targets from the job, not a universal preset. ](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/)[ ![Dialogue, music, effects and Foley tracks routed through matching Fairlight buses to the Main bus](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/fairlight-bus-routing-feature-v2.webp) 9 min read Fairlight Bus Routing Explained Trace dialogue, music and effects through tracks, submixes and the final bus. Check extra routes before exporting a mix or stems. ](https://davinciresolveclub.com/fairlight-bus-routing/)[ ![Editorial cover for natural dialogue compression in Fairlight without presenting unverified control values](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/fairlight-compressor-dialogue--feature-v1.webp) 8 min read Fairlight Compressor Settings for Dialogue Control uneven dialogue without flattening every syllable. Set threshold and timing from the recording, then listen for pumping and raised room noise. ](https://davinciresolveclub.com/fairlight-compressor-dialogue/)[ ![Editorial cover for cleaning dialogue with Fairlight EQ without prescribing fixed frequencies or gain values](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/fairlight-eq-dialogue--feature-v1.webp) 8 min read Fairlight EQ: Clean Dialogue in DaVinci Resolve Choose clip or track EQ and make changes you can hear in context. Reduce rumble or harshness without copying a curve onto every voice. ](https://davinciresolveclub.com/fairlight-eq-dialogue/)[ ![DaVinci Resolve dialogue waveform automatically lowering a music track beneath speech](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-audio-ducking-cover.webp) 9 min read DaVinci Resolve Audio Ducking: Ducker, AI & Sidechain Keep speech clear over music. Compare Ducker, sidechain compression and AI-assisted mixing, then check transitions and exceptions by ear. ](https://davinciresolveclub.com/davinci-resolve-audio-ducking/)[ ![DaVinci Resolve 21 Fairlight Noise Reduction controls and background-noise diagnostic choices](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/cover-corrected-7.webp) 9 min read How to Remove Background Noise in DaVinci Resolve Separate steady noise, hum and gaps between words before choosing a processor. Reduce distraction without trading it for watery or muffled speech. ](https://davinciresolveclub.com/remove-background-noise-davinci-resolve/) Edit, clean up and troubleshoot clips4 guides [ ![Dialogue waveform with silent pauses removed on a DaVinci Resolve timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/remove-silence-davinci-resolve--feature-v1.webp) 9 min read How to Remove Silence in DaVinci Resolve Compare silence removal with ripple edits that shorten the timeline. Protect quiet words, sync, music and captions, then review the joins. ](https://davinciresolveclub.com/remove-silence-davinci-resolve/)[ ![Voice Isolation and Dialogue Leveler compared on dialogue waveforms](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/voice-isolation-vs-dialogue-leveler--feature-v1.webp) 11 min read Voice Isolation vs Dialogue Leveler in DaVinci Resolve Choose between reducing competing sound and evening out dialogue levels. Check edition requirements and compare the result at matched loudness. ](https://davinciresolveclub.com/voice-isolation-vs-dialogue-leveler/)[ ![DaVinci Resolve No Audio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/DaVinci-Resolve-No-Audio.jpeg) 8 min read DaVinci Resolve No Audio Follow the signal from clip and track meters through buses, monitoring and the output device. Find where audible playback stops. ](https://davinciresolveclub.com/davinci-resolve-no-audio/)[ ![How to Mute and Split Audio in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/06/How-to-Mute-and-Split-Audio-in-DaVinci-Resolve.jpeg) 8 min read How to Mute and Split Audio in DaVinci Resolve Mute a clip, track or short section without losing sync. Distinguish unlinking audio and video from extracting a separate audio file. ](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/) Record, transcribe and deliver3 guides [ ![How to Transcribe Audio in DaVinci Resolve 21](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/06/How-to-Transcribe-Audio-in-DaVinci-Resolve-21.jpeg) 9 min read How to Transcribe Audio in DaVinci Resolve 21 Choose clip transcripts or timeline subtitles, correct the generated text and check the export format. Find the relevant controls and edition requirements. ](https://davinciresolveclub.com/transcribe-audio-davinci-resolve/)[ ![Audio-only export settings on the DaVinci Resolve Deliver page](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/export-audio-davinci-resolve--feature-v1.webp) 9 min read How to Export Audio Only in DaVinci Resolve Choose one finished mix or separate stems, confirm the source bus and render range, then listen to the exported file. ](https://davinciresolveclub.com/export-audio-davinci-resolve/)[ ![DaVinci Resolve 21 Voiceover panel recording a microphone waveform to a VO timeline track](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/voiceover-cover.webp) 9 min read How to Record Voiceover in DaVinci Resolve 21 Choose a simple voiceover recording route or explicit Fairlight patching. Check the microphone signal, monitoring, channel mapping and the recorded take. ](https://davinciresolveclub.com/record-voiceover-davinci-resolve/) Before you add another effect ## Two useful starting checks ### Do I need Studio to start mixing in Fairlight? No. Resolve Free includes core audio editing and mixing tools. Studio adds features such as Voice Isolation. Check the edition requirements in the guide before choosing an AI workflow. ### Is there one correct loudness or compressor setting? No. The recording, the mix and the delivery requirements determine the settings. Listen for clear speech, check peaks and measure the finished program. A louder result is not automatically a better result. Before buying for a specific feature, check Blackmagic’s [Studio feature overview](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com). New to audio? The [official Fairlight lessons](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com) cover editing, mixing and recording. The listed Fairlight book is for Resolve 20; some controls differ in newer releases. ### Fix DaVinci Resolve: Troubleshooting Hub URL: https://davinciresolveclub.com/fix-davinci-resolve/ Last updated: 2026-09-15T14:13:54.000Z Diagnose before changing settings ## Start with the symptom, not a reinstall A missing clip, a choppy timeline and a silent output need different checks. Save your work, make a test copy where possible and change one thing at a time. Choose the task ## Choose the problem you can see or hear Pick the closest match, then test whether each change actually affects the failure. [ ![Media Offline in DaVinci Resolve: How to Fix It](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/05/Media-Offline-in-DaVinci-Resolve--How-to-Fix-It.jpeg) 10 min read Media Offline in DaVinci Resolve: How to Fix It Check whether Resolve lost the source path or cannot decode the clip. Separate original-media, proxy and cache problems before relinking. ](https://davinciresolveclub.com/media-offline-davinci-resolve/) [ ![DaVinci Resolve Slow Playback](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/DaVinci-Resolve-Slow-Playback.jpeg) 12 min read DaVinci Resolve Slow Playback Identify whether source decoding, timeline effects, GPU load or storage limits playback. Compare the available proxy and cache approaches. ](https://davinciresolveclub.com/davinci-resolve-slow-playback/) [ ![Resolve 21 Memory and GPU, Proxy Handling, bypass, and Render in Place controls for fixing allocation errors](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/gpu-memory-feature-v2.webp) 9 min read Fix GPU Memory Full in DaVinci Resolve Protect the project, find a repeatable failing frame and isolate demanding processing. Test a copy before changing the working setup. ](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/) [ ![DaVinci Resolve Render Failed](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/DaVinci-Resolve-Render-Failed.jpeg) 10 min read DaVinci Resolve Render Failed Use the error message and failing timecode to separate clip, decode, GPU and storage problems. Check the result with a short render. ](https://davinciresolveclub.com/davinci-resolve-render-failed/) [ ![DaVinci Resolve No Audio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/DaVinci-Resolve-No-Audio.jpeg) 10 min read DaVinci Resolve No Audio Compare clip playback, track and bus meters, monitoring and the output device. Follow the signal to find where sound stops. ](https://davinciresolveclub.com/davinci-resolve-no-audio/) [ ![DaVinci Resolve project library, DRP, DRA, media and cache storage map](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/where-davinci-resolve-projects-saved--feature-v1.webp) 11 min read Where DaVinci Resolve Projects Are Saved Confirm the active Project Library before assuming work is lost. Distinguish project exports, archives and backups, then choose a recovery route. ](https://davinciresolveclub.com/where-davinci-resolve-projects-saved/) [ ![DaVinci Resolve MP4 import fix for an audio-only video file](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-mp4-import-fix.webp) 9 min read DaVinci Resolve Won't Import MP4? Fix Audio-Only Clips Inspect the video and audio streams inside the MP4\. Check format support and source patching before converting or replacing media. ](https://davinciresolveclub.com/davinci-resolve-wont-import-mp4/)[ ![DaVinci Resolve crash diagnosis with a repeatable trigger and recovery path](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-keeps-crashing.webp) 8 min read DaVinci Resolve Keeps Crashing? Find the Exact Trigger Record a repeatable trigger, protect the project and isolate media, plug-ins or system changes. Avoid changing several variables together. ](https://davinciresolveclub.com/davinci-resolve-keeps-crashing/)[ ![DaVinci Resolve Media Pool and Deliver page with MP4, HEVC, AAC and operating system codec checks](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/supported-codecs-cover.webp) 9 min read DaVinci Resolve Supported Codecs and Formats Guide Compare the actual container and streams with platform and edition support. Check importing and exporting separately before choosing an intermediate format. ](https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/) Before you troubleshoot ## Keep the next step safe ### Should I reinstall Resolve before trying these guides? Not as the first response to every error. Check whether the problem affects one clip, one project or even a new test project. Reinstalling is not a substitute for recovering missing media or restoring the right project backup. Protect the existing work before changing the installation. ### What should I record before asking for help? Note the exact Resolve build and Free or Studio edition, operating system, GPU and driver, error message and steps that reproduce it. Include the failing timecode when there is one. Remove private client details before sharing diagnostics; do not post confidential project or media files publicly. Before an installation or driver change, compare your setup with the requirements and changes in Blackmagic’s [Resolve 21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com). ### Learn DaVinci Resolve: Start Here URL: https://davinciresolveclub.com/davinci-resolve-tutorials/ Last updated: 2026-09-08T21:56:08.000Z One current route ## Continue in the maintained Learn Resolve hub The previous roadmap has been consolidated so readers do not have to choose between two overlapping learning pages. The current hub groups beginner setup, editing, audio, color, Fusion and export guides by the job you need to complete. [Open the Learn Resolve hub](https://davinciresolveclub.com/davinci-resolve-tutorial/) ### DaVinci Resolve Comparisons URL: https://davinciresolveclub.com/davinci-resolve-comparisons/ Last updated: 2026-09-12T13:22:26.000Z Choose the task ## Which choice are you making? Already using Resolve? Compare editions or costs first. Choosing a different editor? Pick the comparison for your timeline, team and delivery needs. [ ![DaVinci Resolve vs DaVinci Resolve Studio: Which Do You Need?](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/05/DaVinci-Resolve-vs-DaVinci-Resolve-Studio--Which-Do-You-Need-.jpeg) 10 min read DaVinci Resolve vs DaVinci Resolve Studio: Which Do You Need? Decide whether a specific Studio feature justifies upgrading. Compare output limits, noise reduction, AI tools and codec support against the work you actually need to deliver. ](https://davinciresolveclub.com/davinci-resolve-vs-studio/) [ ![DaVinci Resolve Free Version Features: What You Lose Without Studio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/05/DaVinci-Resolve-Free-Version-Features--What-You-Lose-Without-Studio.jpeg) 12 min read DaVinci Resolve Free Version Features: What You Lose Without Studio Check what the no-cost edition includes, which features need Studio and where format or export limits matter. A feature inventory for planning a real project, not just deciding whether to upgrade. ](https://davinciresolveclub.com/davinci-resolve-free-version-features/) [ ![How Much Does DaVinci Resolve Cost?](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/05/How-Much-Does-DaVinci-Resolve-Cost-.jpeg) 9 min read How Much Does DaVinci Resolve Cost? Separate the free editor, desktop Studio license, Cloud rental and iPad purchase. Check regional prices, taxes, bundles and renewal terms before paying. ](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) [ ![DaVinci Resolve 21 vs Adobe Premiere Pro 2026 comparison of price workflow color AI and audio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/resolve-vs-premiere-2026-cover.webp) 12 min read DaVinci Resolve vs Premiere Pro (2026) Compare Resolve’s integrated finishing workflow with Premiere’s Adobe connections and team handoffs. Check subscription costs, effects, audio and project migration before moving a client job. ](https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/) [ ![DaVinci Resolve versus Final Cut Pro editing workflow comparison](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-vs-final-cut-pro-cover.webp) 10 min read DaVinci Resolve vs Final Cut Pro in 2026 Compare Final Cut’s Magnetic Timeline with Resolve’s editing and finishing workflow on desktop. Look at Mac requirements, media organization, collaboration and the cost of switching. ](https://davinciresolveclub.com/davinci-resolve-vs-final-cut-pro/) [ ![DaVinci Resolve versus CapCut video editing workflow comparison](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-vs-capcut-cover.webp) 10 min read DaVinci Resolve vs CapCut in 2026 Compare captions, templates and social publishing with color, audio and longer-project finishing. Check paid assets, AI limits and the work needed to move between the two editors. ](https://davinciresolveclub.com/davinci-resolve-vs-capcut/) [ ![Fusion node graph versus After Effects layer timeline comparison](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/fusion-vs-after-effects-cover.webp) 10 min read Fusion vs After Effects in 2026 Compare node-based compositing in Fusion with After Effects motion design and Premiere templates. Choose around the shot, animation and revision process, not a blanket speed ranking. ](https://davinciresolveclub.com/fusion-vs-after-effects/) [ ![DaVinci Resolve 21 and Filmora 15 editing interfaces compared side by side](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/resolve-vs-filmora-cover.webp) 10 min read DaVinci Resolve vs Filmora in 2026 Compare Filmora’s editing tools and templates with Resolve’s dedicated finishing workspaces. Check export restrictions, paid plans, AI allowances and what survives a project handoff. ](https://davinciresolveclub.com/davinci-resolve-vs-filmora/)[ ![DaVinci Resolve 21 and VEGAS Pro 2026 editing interfaces compared side by side](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/resolve-vs-vegas-pro-cover.webp) 11 min read DaVinci Resolve vs VEGAS Pro in 2026 Compare timeline editing in VEGAS with Resolve’s dedicated workspaces. Check platform support, license tiers, included effects and migration limits before switching. ](https://davinciresolveclub.com/davinci-resolve-vs-vegas-pro/) Before you switch ## Make the comparison useful ### Should I compare Free with Studio or with another editor? Use Free vs Studio when a Resolve feature or export limit is blocking your work. Compare another editor when the timeline, team workflow, platform or delivery process is the problem. The pricing guide answers a different question: what each purchase or rental actually covers. ### Is After Effects a replacement for the whole Resolve workflow? Not by itself. After Effects focuses on motion graphics and visual effects. Resolve combines editing, color, Fusion and Fairlight in one application. Compare Fusion with After Effects for compositing or animation; compare Resolve with Premiere for the broader editing workflow. See how Adobe describes [After Effects motion graphics and visual effects](https://www.adobe.com/products/aftereffects.html?ref=davinciresolveclub.com), alongside Blackmagic’s [Fusion node-based workflow](https://www.blackmagicdesign.com/products/davinciresolve/fusion?ref=davinciresolveclub.com). ### How can I test a switch without risking a project? Use a copy of a short, representative edit. Include your camera media, titles, effects, captions and audio. Export the required deliverable and try the intended handoff. Keep the original project and media until you have checked the result. ### DaVinci Resolve Tutorial: The Learning Path URL: https://davinciresolveclub.com/davinci-resolve-tutorial/ Last updated: 2026-09-15T16:16:01.000Z Start small ## Finish one video, then add a skill Use a few clips from one project. Make a cut you can watch from beginning to end, check the sound and export it. The first six guides cover that route; open another section when a particular task gets in the way. First project · 6 guides ## Your first finished video Start with the complete beginner tutorial, or open the step you need. [ ![DaVinci Resolve Tutorial for Beginners](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/05/DaVinci-Resolve-Tutorial-for-Beginners.jpeg) 10 min read DaVinci Resolve Tutorial for Beginners Finish a short video: import clips, make a rough cut, add a title, balance audio and review the export. ](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/)[ ![How to Split a Video in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/06/How-to-Split-a-Video-in-DaVinci-Resolve.jpeg) 9 min read How to Split a Video in DaVinci Resolve Split at the playhead or use Blade mode. Check track selection before cutting video and audio separately. ](https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/)[ ![How to Save Work in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/06/How-to-Save-Work-in-DaVinci-Resolve.jpeg) 8 min read How to Save Work in DaVinci Resolve Understand project libraries, Live Save, backups and exported project files. Choose what to save before relying on recovery. ](https://davinciresolveclub.com/how-to-save-work-davinci-resolve/)[ ![How to Mute and Split Audio in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/06/How-to-Mute-and-Split-Audio-in-DaVinci-Resolve.jpeg) 8 min read How to Mute and Split Audio in DaVinci Resolve Mute a clip or track, split an audio section and keep picture and sound aligned when separating them. ](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/)[ ![How to Color Grade in DaVinci Resolve: Beginner Tutorial](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/How-to-Color-Grade-in-DaVinci-Resolve--Beginner-Tutorial.jpeg) 11 min read How to Color Grade in DaVinci Resolve: Beginner Tutorial Start with color management, exposure and balance. Match shots before building a look, then check a test export. ](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/)[ ![How to Export Video in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/06/How-to-Export-Video-in-DaVinci-Resolve.jpeg) 9 min read How to Export Video in DaVinci Resolve 21 Choose Quick Export or the Deliver page. Check format, range and audio, then play the finished file. ](https://davinciresolveclub.com/export-video-davinci-resolve/) Set up the project4 guides [ ![DaVinci Resolve System Requirements (2026)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/05/DaVinci-Resolve-System-Requirements--2026-.jpeg) 10 min read DaVinci Resolve System Requirements (2026) Check operating system, memory, GPU and storage requirements for the version and edition you intend to install. ](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/)[ ![DaVinci Resolve timeline frame rate choices for mixed source footage](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-frame-rate-guide.webp) 9 min read DaVinci Resolve Frame Rate: Set Timeline FPS Correctly Choose timeline cadence before importing. Understand mixed frame rates, slow motion and options when timeline FPS is locked. ](https://davinciresolveclub.com/davinci-resolve-frame-rate/)[ ![DaVinci Resolve timeline reframed for landscape, vertical and square video](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/change-aspect-ratio-davinci-resolve--feature-v1.webp) 9 min read Change Resolution and Aspect Ratio in DaVinci Resolve Set a landscape, vertical or square timeline. Reframe the subject and check titles before exporting another aspect ratio. ](https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/)[ ![DaVinci Resolve Proxy Workflow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-proxy-workflow--feature-v1.webp) 13 min read DaVinci Resolve Proxy Workflow: Create, Link & Export Choose between proxies, optimized media and render cache. Create and relink proxies, then check the source used for export. ](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) Edit, arrange and add titles9 guides [ ![DaVinci Resolve keyboard shortcut map for selection, blade, trim, and split at playhead](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-keyboard-shortcuts-guide--feature-v2.webp) 15 min read DaVinci Resolve Keyboard Shortcuts That Save Time Find editing shortcuts, check the active keyboard preset and diagnose commands that affect the wrong track or panel. ](https://davinciresolveclub.com/davinci-resolve-keyboard-shortcuts-guide/)[ ![DaVinci Resolve 21 Inspector tabs and core Transform controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-inspector--feature-v2.webp) 10 min read DaVinci Resolve Inspector: Core Controls Explained Find transform, crop, audio and effect controls. Check the selected clip before copying, animating or resetting a setting. ](https://davinciresolveclub.com/davinci-resolve-inspector/)[ ![Three ways to duplicate a clip in DaVinci Resolve: modifier drag, paste and Media Pool duplicate](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/09/cover-repair-v2.webp) 7 min readHow to Duplicate a Clip in DaVinci Resolve (Fast Ways)Compare drag-copy, copy-and-paste and paste-insert methods. Check destination tracks and whether a nested copy is independent. ](https://davinciresolveclub.com/duplicate-clip-davinci-resolve/)[ ![Illustrated DaVinci Resolve title over video with Text and Text+ tools](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/05/How-to-Add-Text-in-DaVinci-Resolve.jpeg) 9 min readHow to Add Text in DaVinci ResolveChoose basic Text, Text+ or a title preset. Set the wording and position without confusing titles with subtitle tracks. ](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/)[ ![DaVinci Resolve transition between two clips with visible trim handles](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-transitions-guide.webp) 9 min read DaVinci Resolve Transitions: Add, Trim and Fix Them Add a transition, choose its duration and check available handles. Diagnose a dissolve that will not fit the cut. ](https://davinciresolveclub.com/davinci-resolve-transitions/)[ ![One Adjustment Clip applying a shared effect across multiple timeline shots](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/adjustment-clips-davinci-resolve--feature-v1.webp) 9 min readAdjustment Clips in DaVinci ResolveApply a shared transform or effect over a defined range. Check which clips and titles sit underneath it. ](https://davinciresolveclub.com/adjustment-clips-davinci-resolve/)[ ![DaVinci Resolve speed controls with retime curve and speed points](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/How-to-Change-Clip-Speed-in-DaVinci-Resolve.jpeg) 12 min readHow to Change Clip Speed in DaVinci ResolveUse a fixed speed, a ramp or a freeze frame. Check interpolation, audio and the space around the edit. ](https://davinciresolveclub.com/change-clip-speed-davinci-resolve/)[ ![DaVinci Resolve compound clip containing layered video, titles and audio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-compound-clips.webp) 9 min read Compound Clips in DaVinci Resolve: Create, Edit and Undo Group an edit inside a compound clip. Open its contents, make an independent copy and check before decomposing it. ](https://davinciresolveclub.com/davinci-resolve-compound-clips/)[ ![DaVinci Resolve 21 Edit page with a selected picture-in-picture facecam over a landscape timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/picture-in-picture-cover.webp) 9 min read DaVinci Resolve Picture in Picture: Resolve 21 Guide Build an inset video, adjust its crop and position, then add a border or animation where the composition needs it. ](https://davinciresolveclub.com/davinci-resolve-picture-in-picture/) Build a specific skill4 guides [ ![DaVinci Resolve subtitle track with timed caption cues and three delivery options](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-subtitles-cover.webp) 10 min read DaVinci Resolve Subtitles: Create, Style, Import & Export Create or import captions, check timing and choose between a subtitle file, embedded captions and burned-in text. ](https://davinciresolveclub.com/davinci-resolve-subtitles-captions/)[ ![DaVinci Resolve multicam edit with three camera angles and an active timeline cut](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/multicam-editing-cover.webp) 10 min read DaVinci Resolve Multicam Editing: Sync to SmartSwitch Sync camera angles, keep the chosen audio and review the camera cuts. Explore SmartSwitch when your edition supports it. ](https://davinciresolveclub.com/davinci-resolve-multicam-editing/)[ ![DaVinci Resolve 21 Curve Editor with cyan easing curve and orange Transform keyframes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/keyframes-curve-editor-cover.webp) 9 min read DaVinci Resolve Keyframes and Curve Editor Guide Animate a parameter, shape its timing with curves and troubleshoot missing keyframes. Check the motion in playback. ](https://davinciresolveclub.com/davinci-resolve-keyframes-curve-editor/)[ ![DaVinci Resolve Fusion Tutorial for Beginners](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/07/DaVinci-Resolve-Fusion-Tutorial-for-Beginners.jpeg) 9 min read DaVinci Resolve Fusion Tutorial for Beginners Learn nodes through a tracked title, a green-screen key and a lower third. Troubleshoot a composition that appears blank. ](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) Check features and updates4 guides [ ![DaVinci Resolve 21 Slate Finder identifying a clapperboard and metadata](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/davinci-resolve-slate-finder-slate-id--feature-v2.webp) 10 min readDaVinci Resolve 21 AI Slate ID and Slate FinderDistinguish finding a slate from reading its metadata. Review detected fields before saving them to the clips. ](https://davinciresolveclub.com/davinci-resolve-slate-finder-slate-id/)[ ![DaVinci Resolve 21 AI tools cover with IntelliSearch, Speech Generator, CineFocus and Slate ID interfaces](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/resolve-21-ai-tools-cover-v2.webp) 10 min readDaVinci Resolve 21 AI Tools: Free vs Studio BreakdownCompare AI tools by task, edition and hardware needs. Check model downloads and review the result before using it. ](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/)[ ![DaVinci Resolve 21 What's New cover with Photo, IntelliSearch, keyframe and Color interfaces](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/resolve-21-whats-new-cover-v2.webp) 9 min readDaVinci Resolve 21: What's New, AI Tools, Photo Page and Upgrade NotesReview the Photo page, editing changes and upgrade notes. Check the release notes for the exact build you install. ](https://davinciresolveclub.com/davinci-resolve-21-whats-new/)[ ![Safe DaVinci Resolve update checklist with project and library backups](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/update-davinci-resolve-safely--feature-v1.webp) 12 min readHow to Update DaVinci Resolve SafelyBack up projects, libraries and media before upgrading. Keep a rollback plan and test a copy of an active project. ](https://davinciresolveclub.com/update-davinci-resolve-safely/) Before you start ## A few beginner questions ### Do I need Studio to follow the beginner path? Start with Free for a basic edit, title, color correction and export. Specific AI tools, formats and finishing features can require Studio or particular hardware. Check the feature you need before buying an upgrade. ### Do I need to learn Fusion before editing a video? No. Make a straightforward edit first. Open the Fusion guide when you need a tracked title, a key or another compositing task. You can learn it alongside a project instead of completing a whole effects course before you begin. ### Where can I get footage and structured lessons to practice? Blackmagic Design provides free training videos, books and lesson files. Check the version named on each course: the training page currently lists Resolve 20 books, while the current desktop release notes cover 21.1\. Menus and available features can differ. Get the [official training and lesson files](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com), and check Blackmagic’s [Resolve 21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) before following a version-specific step. [Browse the full tutorial library](https://davinciresolveclub.com/tag/tutorials/) ### DaVinci Resolve Proxy Workflow: Create, Link & Export URL: https://davinciresolveclub.com/davinci-resolve-proxy-workflow/ Last updated: 2026-09-08T23:08:56.000Z Proxy Media is the right Resolve workflow when your camera originals are too heavy for smooth editing and you want lightweight files that can be moved, shared, inspected, and relinked. Set the proxy resolution and codec in Project Settings, generate the files from the Media Pool, choose **Prefer Proxies** while editing, then switch back to camera originals before the final quality check. That's different from Timeline Proxy Resolution, Optimized Media, and Render Cache. Those tools can all improve playback, but they solve different bottlenecks. This guide gives you one repeatable workflow for a single workstation, a laptop handoff, or a remote edit without turning your final export into a guessing game. ## Choose the right playback tool first Don't generate hundreds of gigabytes of proxy files until you know that Proxy Media is the tool your project needs. Start with the smallest intervention that matches the symptom. Workflow selector ### Which playback tool should you use? Pick the symptom you can reproduce. The selector recommends the smallest useful intervention; you can combine tools later if the project has more than one bottleneck. What slows down first? **The whole timeline is only a little slow**I need an instant, reversible playback test. **Source clips are hard to decode**H.264, H.265, RAW, 6K, or 8K footage struggles before heavy effects. **A few processed clips become slow**Fusion, noise reduction, grades, retimes, or effects cause the drop. **The edit moves between people or systems**I need lightweight files I can copy, inspect, and relink. Do the generated files need to move outside this workstation? **Yes, I need portable files**Another editor, machine, drive, or service needs them. **No, Resolve can manage them here**The project stays in this setup and I only need easier source playback. Start with #### [](#) Start again Test one clip before generating a full set. Proxies reduce source-media demands; Render Cache stores processed results. Neither replaces a backup of your originals. Blackmagic makes the same distinction in the [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com): Proxy Media is independent and portable, Timeline Proxy Resolution changes processing resolution without creating media, Optimized Media is managed internally, and Render Cache targets effect-heavy results. ![DaVinci Resolve Proxy Handling menu with Disable, Prefer Proxies, and Prefer Camera Originals](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/davinci-resolve-proxy-handling-menu-v2.webp) Proxy Handling switches the preferred playback media without relinking clips. ## Set resolution, codec, and location before generating files Open **File > Project Settings > Master Settings**. In Optimized Media and Render Cache, choose Proxy Media Resolution and Proxy Media Format. Under Working Folders, confirm the Proxy generation location. Then check **Preferences > System > Media Storage**: its Proxy Generation Location preference can override that project folder. The Proxy Media Path column will tell you where each linked file actually lives. For resolution, **Choose Automatically** is a safe first test because Resolve reduces sources that exceed the timeline resolution. Use Half or Quarter when you need a predictable size reduction. Eighth and Sixteenth are transport choices for unusually large originals or constrained remote workflows; they can make focus, key edges, fine text, and compression artifacts too difficult to judge. Proxies can reduce decoding and storage demands, but they are not a way around the [system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). Check [hardware and driver compatibility](https://davinciresolveclub.com/davinci-resolve-hardware-compatibility/) separately; effects can still exhaust GPU memory with proxies enabled. For codec, prioritize decoding speed on the editing machine rather than the smallest possible number on disk. ProRes Proxy or ProRes LT is a common macOS choice. DNxHR LB or SQ is a practical cross-platform choice. The exact list depends on the operating system and Resolve build. H.264 or H.265 can make compact handoff files, but highly compressed long-GOP media may move work back onto the decoder you were trying to relieve. Test one representative clip before generating the whole card. Put proxies on a fast SSD with enough free space and a stable path. Avoid a temporary download folder, a drive letter that changes between workstations, or a cloud-sync directory that may evict files. If the project will move, design the folder structure before generation so the same proxy root can travel with the project. ## Generate Proxy Media from the Media Pool 1. Select one representative clip in the Media Pool. 2. Right-click it and choose **Generate Proxy Media**. 3. Wait for generation to finish and test playback, scrubbing, audio sync, and a short color or Fusion section. 4. If the test is clean, select the remaining source clips and generate the full set. Resolve uses the proxy resolution and format already stored in Project Settings. Changing those settings after generation does not silently rebuild old files. Generate a new proxy if you want a different resolution, codec, or RAW interpretation. When separately recorded audio is synced to a source clip in the Media Pool, Blackmagic notes that generated proxy media includes the synced audio inside the proxy video file. Verify sync on a slate or a hard consonant before handing the project to another editor. ![DaVinci Resolve Media page with bins and source clips in the Media Pool](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/davinci-resolve-media-pool.webp) Select source clips in the Media Pool before generating, linking, or checking proxy media. ## Verify that Resolve is actually using the proxies Generating files isn't the same as playing them. In the Cut or Edit viewer, open Proxy Handling and choose **Prefer Proxies**. Resolve will use a linked proxy when it exists and fall back to the camera original when it doesn't. That fallback is convenient, but it can hide a partial proxy set: one section plays smoothly while another still decodes the original. Use List view in the Media Pool and enable the **Proxy** and **Proxy Media Path** columns. The status should show a resolution rather than None or Offline. Check several clips from different camera folders. The first item in the bin is not enough. - **None** means no proxy is linked. - **Offline** means Resolve has proxy metadata but can't find the expected file. - **A resolution** means linked proxy media is online. The viewer and clip badges also show whether Resolve prefers proxy media, prefers camera originals, has only proxy media available, or has disabled the proxy workflow. Use those indicators during handoff checks instead of trusting memory. ## Proxy Media vs Optimized Media Both make source footage easier to play, but ownership is different. Proxy Media creates normal, independent files that you can copy, inspect, archive, and relink. Optimized Media is controlled internally by Resolve and is designed to stay with the project environment that created it. Choose Proxy Media when the edit moves between systems, another editor needs compact files, or you need an explicit file path and status. Choose Optimized Media when Resolve can manage the substitute media inside the current setup. Resolve 21 can reuse Optimized Media across projects in the same project library, but it isn't included in Media Management or Project Archive operations, so don't treat it as portable handoff media. ## Proxy Media vs Timeline Proxy Resolution Timeline Proxy Resolution doesn't transcode your source clips. It asks Resolve to process the timeline at a lower working resolution. That makes it an excellent first move when playback is close to real time and the bottleneck is general processing rather than source decoding. Choose **Playback > Timeline Proxy Resolution** and test Half or Quarter. Restore full processing resolution when judging fine detail. Proxy Media and Timeline Proxy Resolution are independent, so you can edit with proxy files and still reduce timeline processing for a heavy grade. If playback is already smooth after one change, stop there. ## Proxy Media vs Render Cache Proxies reduce source-media demands; they do not pre-render your effects. A proxy may make an H.265 interview play cleanly, yet a Fusion composition, temporal noise reduction or a chain of Resolve FX can still drop frames. Use [Render Cache for the processed result](https://davinciresolveclub.com/davinci-resolve-render-cache/) when that is the bottleneck, rather than assuming that another proxy set will solve it. A [GPU Memory Full error](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/) can survive a proxy change when the real pressure comes from timeline resolution, Fusion, temporal effects, or the grade. Reduce the expensive processing or cache that result instead of generating another proxy set. Render Cache is project-managed and not a portable replacement for the original camera media. Don't copy a CacheClip folder to another workstation and call it a handoff. Use a proxy-aware archive or copy the proxy root deliberately. ## Automate watch folders with Blackmagic Proxy Generator Use the separate [Blackmagic Proxy Generator](https://www.blackmagicdesign.com/products/davinciresolve/collaboration?ref=davinciresolveclub.com) when new camera files arrive in one or more watch folders and you want proxy creation to continue outside the Resolve interface. Choose the proxy format, add the watched folders, and let the application place generated media in **Proxy** subfolders beside the originals. When those originals are imported into the Media Pool, Resolve can link the matching proxies automatically. If you need a separate handoff folder, **Extract Proxies** copies the generated proxy files to a destination you choose; it doesn't replace the camera originals. ![Blackmagic Proxy Generator processing watch folders and creating proxy files](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/blackmagic-proxy-generator.webp) Proxy Generator can monitor watch folders while DaVinci Resolve remains available for editing. In Proxy Generator, click **Start** after selecting the watch folders and proxy format. When you need **Extract Proxies**, stop processing first so that control is available. Check the copied files on the destination before handing over the project. ## Move, link, and relink proxy files If proxies were generated outside Resolve or moved, select the source clips in the Media Pool and choose **Link Proxy Media**. External proxies need identical source timecode, the same base filename, the same frame rate and a supported codec. A timecode number burned into the picture is not a substitute for matching file metadata. Check duration and audio sync after linking, too. After linking, verify the Proxy and Proxy Media Path columns. If a moved drive produces Offline status, relink to the directory containing the matching files. Don't relink camera originals through the proxy command; original relinking and proxy relinking are separate operations. If the originals are also missing, separate proxy relinking from the broader [Media Offline diagnosis](https://davinciresolveclub.com/media-offline-davinci-resolve/) so Resolve is pointed at the correct file type in each step. **Unlink Proxy Media** removes the metadata relationship but doesn't delete the file from disk. That is useful when testing a link, but it also means old proxy generations can accumulate. Record the active proxy root before cleanup. ## Switch back to camera originals before finishing For a reliable original-media check, choose **Disable All Proxies**. Unlike Prefer Camera Originals, it cannot silently fall back to a proxy when an original is missing. Also turn off **Playback > Use Optimized Media if Available** and disable caching under **Playback > Render Cache** for this check. Inspect focus, noise, key edges, stabilization and texture; restore your working playback options afterward if needed. A purple timeline line warns that camera originals are missing in the proxy workflow. With proxies disabled, missing originals appear as Media Offline instead. Confirm the originals are online before a master export; selecting Prefer Camera Originals alone does not prove they are available. ## Export without accidentally using proxies In the Deliver page’s advanced video settings, leave **Use proxy media** off for an original-media master. Also check the independent **Use optimized media** and **Use render cached images** options: turn both off when you want Resolve to process the originals afresh. High-quality optimized media or cache can be a deliberate delivery choice, but only after you verify their format and quality—not simply because proxy delivery is disabled. Choose the final codec, container, resolution, and audio layout from the [DaVinci Resolve export settings hub](https://davinciresolveclub.com/davinci-resolve-export-settings/); proxy choice shouldn't silently become the delivery specification. Before adding the final render job, run this short gate: 1. Disable All Proxies, and confirm the original clips are online. 2. For the visual check, disable optimized-media playback and render caching. 3. Open several clips at 100% and inspect focus, grain, keys, and noise reduction. 4. For a fresh original-media render, turn off Use proxy media, Use optimized media and Use render cached images. 5. Render a short difficult section and inspect the exported file outside Resolve. If the master still stops or fails after originals are restored, follow the [render-failure isolation workflow](https://davinciresolveclub.com/davinci-resolve-render-failed/) before turning proxy media back on. For a quick daily or a proxy-only remote review, you can deliberately enable **Use proxy media**. Label that output as a proxy review. Do not present it as an original-quality master just because the render completed. Playback preferences and Deliver-page media choices are separate checks. ## Does the proxy workflow work in Free and Studio? Blackmagic presents robust proxy editing as part of the main Resolve workflow, and the [current DaVinci Resolve product page](https://www.blackmagicdesign.com/products/davinciresolve?ref=davinciresolveclub.com) places the Free download alongside those editing features. Studio adds separate AI, effects, codec, resolution, and performance capabilities, but you do not need Studio merely to create and use a normal proxy workflow. Codec availability and hardware acceleration still vary by operating system, source format, bit depth, GPU, and Resolve edition. If an option is absent on your system, choose a proxy codec that the current installation can generate and decode reliably rather than copying a setting from another platform. ## Common proxy workflow failures ### Proxy generation is slow or makes huge files Test a lower resolution or a lighter proxy codec on one clip. High-quality intermediate codecs trade storage for easy decoding. Highly compressed codecs save space but can take longer to encode and may be less responsive on weak hardware. Confirm that the proxy destination isn't a slow network volume. ### Proxy status says Offline Show the Proxy Media Path column, mount the expected drive, and use Link Proxy Media if the files moved. If the folder was renamed or a Windows drive letter changed, fix that path before regenerating anything. ### Playback is still slow with proxies enabled First verify that Resolve is using proxies rather than originals. If it is, the bottleneck may be Fusion, grading, noise reduction, an OFX plug-in, audio processing, storage or timeline resolution. Use the [slow playback diagnosis](https://davinciresolveclub.com/davinci-resolve-slow-playback/) instead of generating a second proxy set blindly. ### The final export looks soft Make the camera originals available. Turn off Use proxy media, Use optimized media and Use render cached images for a fresh original-media test, then render a short section again. If it remains soft, check timeline resolution, scaling, source resolution and the delivery codec. Turning off proxy delivery alone does not rule out a low-quality optimized file or cache. ### Unlinking did not free disk space That's expected. Unlinking removes the relationship inside Resolve; it doesn't delete the proxy files. Confirm the active Proxy Media Path, close the project, and remove only the old proxy generation you have positively identified. Keep a backup if the project is still active. ## The proxy workflow checklist - Test one representative clip before generating the full set. - Choose a codec for easy decoding on the actual edit machine. - Store proxies on a fast, stable path with enough free space. - Verify Proxy and Proxy Media Path columns after generation. - Use Prefer Proxies while editing and camera originals while finishing. - Relink moved proxies; don't regenerate until the path is ruled out. - Check all three Deliver media options before an original-media master. - Document and remove old proxy generations deliberately. When playback is stable, use the [DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/) to place proxy setup back in the larger import, edit, color, audio, and export sequence. ## Proxy workflow questions ### Where does DaVinci Resolve save proxy media? Project Settings > Master Settings > Working Folders sets the Proxy generation location. Preferences > System > Media Storage can override it. Check the Proxy Media Path column for the exact file expected by a clip. ### Should I use Proxy Media or Optimized Media? Use Proxy Media for portable files that you can inspect, copy and relink. Optimized Media is managed internally and can be reused across projects in the same project library. It is not included in Media Management or Project Archive operations, so do not rely on it as your handoff package. ### Does Timeline Proxy Resolution create proxy files? No. It lowers the timeline processing resolution on the fly. Proxy Media creates actual files on disk and links them to the camera originals. ### Will Resolve export from the original files? By default, delivery uses originals rather than proxy files. For a fresh original-media render, verify the originals are online and turn off Use proxy media, Use optimized media and Use render cached images. High-quality optimized media or cache can be used deliberately after checking their format and quality. ### Does Unlink Proxy Media delete the files? No. It removes the metadata link. The proxy file remains on disk until you delete it deliberately. ### Why are my proxies offline after moving the project? The recorded Proxy Media Path no longer matches the mounted drive or folder. Restore the path or select the source clips and use Link Proxy Media to point Resolve to the moved files. ### Can My Computer Run DaVinci Resolve 21? URL: https://davinciresolveclub.com/davinci-resolve-pc-checker/ Last updated: 2026-09-08T15:00:29.000Z Build-specific compatibility check ## Check your computer Choose your platform and edition, then enter only the hardware facts you know. These rules were checked against Resolve 21.1 on September 8, 2026. No scan, diagnostic upload or speed test. The form does not save your answers in a URL or browser storage. 1\. Choose your platform Windows x86 macOS Windows ARM Linux Resolve editionDaVinci Resolve (Free)DaVinci Resolve Studio 2\. Choose the heaviest regular workload **1080p editing**Cuts, titles and simple grades **4K editing**Check the platform’s 4K memory rule **Fusion work**Compositing, not a blanket AI check Also using these Studio features? Select both if needed. Advanced AI toolsBackground rendering 3\. Enter the hardware facts you know 64-bit Windows 10 Creators Update or later? Yes Not sure No Supported processor? Yes Not sure No System or unified memory Not sure4 GB8 GB12 GB16 GB24 GB32 GB48 GB64 GB96 GB128 GB or more Discrete GPU installed? Yes Not sure No GPU memory (VRAM), not RAM + VRAM Not sure Less than 2 GB / none 2 GB 4 GB 6 GB 8 GB 12 GB 16 GB 24 GB or more OpenCL 1.2 or CUDA 12.8 support? Yes Not sure No Official AMD/Intel driver or NVIDIA Studio 581.57+? Yes Not sure No Check my setup Reset Ready to check ### Enter the facts you know, then check the setup. Unknown facts remain unresolved. A result is not a benchmark. ## What the result means **Listed checks met** means your answers satisfy the requirements evaluated by this form. It does not mean the computer has been scanned or that a project will play smoothly. **More facts need checking** means something essential is unknown or outside this rule set. A failed memory or GPU condition tells you what to verify first—not which expensive replacement to buy. Choose **Not sure** instead of guessing. A processor label such as “i7” does not establish decoding performance, and system RAM cannot simply be added to a GPU’s VRAM. On a Mac, enter unified memory once; the checker does not ask you to split it into invented RAM and VRAM pools. Changing any answer clears the old report. Changing platform also resets the hardware answers, so a Windows confirmation cannot silently become a Mac confirmation. [![PC checker fields with unknown hardware values, separate RAM and VRAM, and driver confirmation](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/checker-hardware-annotated-v2.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/checker-hardware-annotated-v2.webp?ref=davinciresolveclub.com) Annotated view of this checker: leave an unknown characteristic as Not sure. The form evaluates your answers; it does not detect your hardware. Tap the image to enlarge. Before buying hardware, test representative media and your actual effects. A benchmark can help compare systems, but its entry requirements are not a guarantee for every timeline. For example, [Puget Bench publishes requirements for running its own tests](https://www.pugetsystems.com/pugetbench/creators/davinci-resolve/?ref=davinciresolveclub.com); those should not be repackaged as universal comfortable 4K specifications. ## Resolve 21.1 platform checks The table summarizes the desktop baseline in Blackmagic’s [Resolve 21.1 release readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com), dated September 8, 2026\. Studio’s extra feature conditions follow below. Use the readme for the exact build you intend to install rather than applying this table to every historical release. | Platform | Listed OS / processor | System memory | Graphics check | | ----------- | ---------------------------------------------------------------------- | ----------------------------- | ---------------------------------------------------------------- | | Mac | Apple Silicon; macOS 15 or newer | 8 GB; 16 GB for Fusion | Apple Silicon graphics; no separate VRAM entry here | | Windows x86 | 64-bit Windows; Windows 10 Creators Update is the listed release floor | 16 GB; 32 GB for Fusion | Integrated or discrete GPU, 4 GB VRAM, qualifying API and driver | | Windows Arm | Windows 11 for Arm; generic matrix names Snapdragon X Elite | 16 GB; 32 GB for 4K or Fusion | No separate VRAM floor in this readme’s Arm section | | Linux | Rocky Linux 8.6 | 32 GB | Discrete GPU, 4 GB VRAM, qualifying API and driver | Blackmagic’s Windows x86 label means the [64-bit Windows build, not a 32-bit edition](https://forum.blackmagicdesign.com/viewtopic.php?p=1092546&t=210617&ref=davinciresolveclub.com). Choose that platform for an Intel/AMD PC with a 64-bit operating system; Windows Arm is a separate build. A 64-bit processor with 32-bit Windows installed is not the same thing. For Windows x86 and Linux, confirm an **OpenCL 1.2 or CUDA 12.8** path for the exact GPU and driver. Windows lists official AMD/Intel drivers or NVIDIA Studio **581.57+**; Linux lists official AMD drivers or NVIDIA Studio **580.119.02+**. The two NVIDIA numbers are platform-specific, not interchangeable. An integrated Windows GPU is not automatically disqualified, but an advertised shared-memory maximum alone does not prove the whole graphics requirement. Other Linux distributions and Arm processors receive an unresolved result here. That means the form cannot confirm them from its baseline, not that Resolve can never run on them. For Blackmagic video-hardware monitoring, the readmes also specify **Desktop Video 12.9 or later**; monitoring hardware is outside this form’s checks. [![Resolve 21.1 PC checker explaining why an Intel Mac misses the Apple Silicon requirement](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/checker-mac-annotated-v1.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/checker-mac-annotated-v1.webp?ref=davinciresolveclub.com) Example result with Apple Silicon set to No. This checks the 21.1 baseline, not whether an older Resolve build could run on that Mac. Tap the image to enlarge. ## Studio AI and background rendering need separate checks The [Studio 21.1 readme](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) adds conditions beyond the base application. On Mac, advanced AI calls for at least **16 GB memory**; background rendering and analysis call for **32 GB**. On Windows x86 and Linux, advanced AI calls for **16 GB VRAM**; background rendering calls for **32 GB RAM plus 12 GB VRAM**. Select both feature boxes when both apply: the checker uses the higher applicable floor, not an average. An 8 GB GPU can meet the base graphics line yet miss the listed advanced-AI requirement. Fusion and AI are therefore separate choices. The Arm section does not publish equivalent feature-specific memory lines, so those Studio checks remain unresolved on Arm rather than borrowing the x86 VRAM rules. [![PC checker result comparing 8 GB selected VRAM with the 16 GB Studio advanced AI requirement](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/checker-ai-annotated-v1.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/checker-ai-annotated-v1.webp?ref=davinciresolveclub.com) Windows Studio example with Advanced AI selected: the 8 GB answer misses the listed 16 GB VRAM condition. No playback or render speed was measured. Tap the image to enlarge. ## What to try next For a wider explanation of hardware choices, use the [system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/), while keeping this tool’s dated build scope in mind. If the machine meets the listed checks but the Edit page struggles, test a [proxy workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/). A specific memory error needs the [GPU memory troubleshooting guide](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/), not another green compatibility badge. Other browser utilities are in [Tools and calculators](https://davinciresolveclub.com/tools/). This form does not inspect CPU generation, codec licensing, plugins, sustained storage speed, temperatures or laptop power limits. It also does not identify third-party monitoring hardware. Check those against the project you actually need to finish; a memory total alone cannot settle the purchase. ## DaVinci Resolve PC checker FAQ ### Does this checker scan my computer? No. It evaluates the answers you select in this page. It does not inspect hardware, request a diagnostic file, run a benchmark or save the form answers in a URL or browser storage. That is not a claim that the rest of the website has no analytics. ### Does passing the checker guarantee smooth 4K playback? No. Listed checks met means the selected answers satisfy this form’s rules. CPU, media, codec support, effects, plugins, storage and power limits remain untested. Try a representative project before relying on a machine for delivery. ### Can DaVinci Resolve 21.1 run on an Intel Mac? The 21.1 Mac readme requires Apple Silicon and macOS 15 or newer. An Intel Mac does not meet that listed baseline. Check the readme of an older compatible build separately; this checker does not certify older releases. ### Can DaVinci Resolve use integrated graphics? The Windows x86 readme permits integrated or discrete graphics when the memory, API and driver conditions are met. Linux requires a discrete GPU. Do not add system RAM to VRAM or treat a shared-memory maximum as proof of complete GPU compatibility. ### Why does the checker ask about GPU drivers and API support? VRAM is only one condition. Windows x86 and Linux also need the listed OpenCL or CUDA path and manufacturer driver. Not sure leaves that condition unresolved instead of inventing a pass. ### What if the checks pass but playback is slow? A listed minimum is not a performance measurement. Test the actual codec and effects, try proxies for editing, inspect the specific error if one appears, and compare representative benchmarks before deciding which component needs an upgrade. ### Do Studio AI tools have higher requirements? Yes. The 21.1 Studio readme lists 16 GB memory for advanced AI on Mac and 16 GB VRAM on Windows x86 and Linux. Background work has separate requirements. The checker applies the higher relevant floor when both are selected; the Arm-specific feature checks remain unresolved. ### Why did my result disappear after I changed a setting? A result belongs to the answers used to create it. Editing any value clears the previous verdict; run the check again. Changing platform resets hardware answers to Not sure, and Reset restores the starting form without a verdict. ### DaVinci Resolve Hardware & Compatibility URL: https://davinciresolveclub.com/davinci-resolve-hardware-compatibility/ Last updated: 2026-09-09T01:21:22.000Z Choose the task ## Find your next check Checking a computer before buying? Start with the PC checker. Already editing? Choose the symptom below before spending money on an upgrade. [ ![Desktop and laptop hardware compatibility check for DaVinci Resolve 21](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/davinci-resolve-pc-checker-cover-v1.webp) Interactive checkerCan My Computer Run DaVinci Resolve 21?Check the listed Resolve 21.1 requirements for your platform, Free or Studio edition, and workload. Unknown hardware stays unresolved. Passing the checks does not predict playback speed. ](https://davinciresolveclub.com/davinci-resolve-pc-checker/) [ ![DaVinci Resolve system requirements workstation with graphics card RAM and NVMe storage](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/system-requirements-cover-v2.webp) 11 min readDaVinci Resolve System Requirements (2026)Check Resolve 21.1 operating-system, RAM, GPU and storage requirements, including the separate Studio limits for advanced AI and background rendering. ](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) [ ![Mac and Windows creator laptops for DaVinci Resolve editing](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/best-laptops-davinci-resolve-cover-v1.webp) 14 min readBest Laptops for DaVinci Resolve in 2026Compare Mac and Windows laptop configurations, cooling and upgrade limits. Match the exact model to your footage and effects; advanced Studio AI needs a separate requirements check. ](https://davinciresolveclub.com/best-laptop-for-davinci-resolve/) [ ![Fixing slow playback in DaVinci Resolve, from proxies to timeline settings](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/07/DaVinci-Resolve-Slow-Playback.jpeg) 11 min readDaVinci Resolve Slow PlaybackIsolate decoding, timeline resolution, effects, storage and GPU load with one repeatable playback test. Find the bottleneck before replacing the computer. ](https://davinciresolveclub.com/davinci-resolve-slow-playback/) [ ![Resolve 21 Memory and GPU, Proxy Handling, bypass, and Render in Place controls for fixing allocation errors](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/gpu-memory-feature-v2.webp) 9 min readFix GPU Memory Full in DaVinci ResolveLocate the failing frame or effect, protect the project, and test which processing exceeds available GPU memory. Do not treat every error as a reason to buy a new card. ](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/) [ ![DaVinci Resolve Proxy Workflow cover with camera originals, proxy files and an editing timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/davinci-resolve-proxy-workflow--feature-v1.webp) 14 min readDaVinci Resolve Proxy Workflow: Create, Link & ExportCreate and verify Proxy Media, relink moved files and switch back to camera originals for finishing. Compare proxies with optimized media and timeline resolution changes. ](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) [ ![DaVinci Resolve Render Cache guide comparing Smart and User modes with red and blue timeline cache bars](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/size/w600/format/webp/2026/08/render-cache-cover.webp) 10 min readDaVinci Resolve Render Cache: Smart vs User GuideChoose Smart or User cache, understand red and blue cache bars, and check the cache location. Troubleshoot unfinished cache renders without deleting camera originals. ](https://davinciresolveclub.com/davinci-resolve-render-cache/) [ ![DaVinci Resolve Media Pool and Deliver page with MP4, HEVC, AAC and operating system codec checks](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/supported-codecs-cover.webp) 9 min readDaVinci Resolve Supported Codecs and Formats GuideCheck the actual video and audio streams, not just the file extension. Match the codec, profile, operating system and Resolve edition to the decode or encode task. ](https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/) [ ![Fixing media offline errors in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/05/Media-Offline-in-DaVinci-Resolve--How-to-Fix-It.jpeg) 9 min readMedia Offline in DaVinci Resolve: How to Fix ItCheck whether Resolve lost the source path or cannot decode the file. Relink the correct media and investigate clips that remain offline even when the files exist. ](https://davinciresolveclub.com/media-offline-davinci-resolve/) Before you upgrade ## Compatibility questions ### Does meeting the minimum mean smooth 4K playback? No. Minimum requirements are an entry check, not a playback benchmark. The codec, frame rate, effects and storage path also matter. Test a representative part of your project before deciding what to upgrade. ### Do Free and Studio need the same hardware? Not for every feature. Resolve Studio 21.1 lists separate requirements for advanced AI and background rendering. Check the requirements for your platform and the features you will use; a general GPU minimum is not enough. ### Should I upgrade if a clip says Media Offline? Not until you know why it is offline. A moved source file needs its path repaired; an unsupported codec needs a different investigation. More RAM or a faster GPU will not restore a missing file path. For the current feature-specific minimums, check Blackmagic’s [Resolve Studio 21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com). ### Video Bitrate & File Size Calculator URL: https://davinciresolveclub.com/video-bitrate-file-size-calculator/ Last updated: 2026-09-08T14:12:34.000Z Enter the values you already know. This calculator can estimate a finished video file size, find the video bitrate that fits a target size, or show how long a storage card can record. It includes the audio stream, reports both decimal and binary units, and does all calculations in your browser. No video is uploaded. **Choose a mode:** File size needs video rate, combined audio rate and duration. Target bitrate works backwards from your size cap. Recording time uses the free space you can actually record into—not necessarily the number printed on a card. Enter 0 for audio when there is none. If a camera specification already gives the **total** recording data rate including audio, put that total in the video-rate field and leave audio at 0\. Otherwise, enter video and the combined rate of all audio streams separately. Do not count the audio twice. Three calculations, one tool ## Video bitrate and file size calculator Choose what you need to find. Rates use bits per second; storage uses bytes. File size Target bitrate Recording time Optional reference preset Custom values YouTube 1080p, 24/25/30 fps YouTube 1080p, 48/50/60 fps YouTube 1440p, 24/25/30 fps YouTube 1440p, 48/50/60 fps YouTube 4K, 24/25/30 fps, low end YouTube 4K, 24/25/30 fps, high end YouTube 4K, 48/50/60 fps, low end YouTube 4K, 48/50/60 fps, high end Vimeo 1080p, low end Vimeo 1080p, high end Vimeo 4K, low end Vimeo 4K, high end Platform reference rates checked September 8, 2026\. These are not measured rates or guaranteed file sizes. Video bitrate kbpsMbpsGbps Audio bitrate kbpsMbps Duration Hours Minutes Seconds Planning allowance % Optional. Leave at 0% unless you want extra headroom. Calculate file sizeReset Target file size MBGBMiBGiBTB Audio bitrate kbpsMbps Duration Hours Minutes Seconds Planning allowance % Calculate video bitrateReset Available storage MBGBMiBGiBTBTiB Video bitrate kbpsMbpsGbps Audio bitrate kbpsMbps Planning allowance % Calculate recording timeReset Ready Enter your values, then calculate. Copy resultCopy share link No video is uploaded. Calculations run in this page. Shared links contain settings in the URL; opening one can put those values in browser history, server logs or analytics. ## Where the calculator fits in DaVinci Resolve Start on the Deliver page and choose **Custom Export** when you need direct control instead of a destination preset. After you select the format, codec and encoder, inspect the **Quality** controls. A rate field may appear as **Restrict to** with a value in Kb/s. Availability and wording can vary by codec, operating system and hardware encoder, so don't expect every render preset to expose the same field. If you need the surrounding controls, use the [full Deliver-page walkthrough](https://davinciresolveclub.com/export-video-davinci-resolve/). ![DaVinci Resolve 21 Custom Export menu and Single Clip render mode](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/custom-export-resolve21.webp) Choose Custom Export for direct access to codec-specific controls. Single Clip is the normal choice for one finished video. ## The file-size calculation A [byte contains eight bits](https://csrc.nist.gov/glossary/term/byte?ref=davinciresolveclub.com), so the core conversion is simple: add the video and audio bitrates, multiply by duration in seconds, then divide by eight. The reverse calculation works from a target number of bytes back to bits per second. The calculator uses the unrounded numerical result for its next step and rounds the display. It uses ordinary browser floating-point arithmetic, not byte-exact inspection of a file. ![Video file-size calculator with video and audio rates, duration, MB and MiB results annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/calculator-size-annotated-v2.webp) Annotated website calculator: 8 Mbps video plus 384 kbps audio over ten minutes gives 628.8 MB before allowance. The per-minute estimate is 62.88 MB. For example, 8 Mbps of video plus 384 kbps of audio for ten minutes gives 628.8 MB before allowance: 62.88 MB per minute. A 500 MB target over ten minutes with 192 kbps audio leaves about 6.475 Mbps for video before allowance. If exactly 128 GB of decimal storage is available at a total 100 Mbps, the mathematical recording time is 2 hours, 50 minutes and 40 seconds. Formatting, existing files, camera limits and fluctuating data rates can reduce usable time. ### Estimate recording capacity, not card speed ![Recording-time calculator with 128 GB available storage and a 100 Mbps total rate annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/calculator-time-annotated-v2.webp) Annotated website calculator: exactly 128 GB available at a total 100 Mbps gives 2 hr 50 min 40 sec before allowance. This checks capacity, not card speed or camera limits. ## MB and GB are not the same as MiB and GiB This page reports both systems because apps and storage vendors don't always label them consistently. Decimal units use powers of 1,000: 1 MB is 1,000,000 bytes and 1 GB is 1,000,000,000 bytes. Binary units use powers of 1,024: 1 MiB is 1,048,576 bytes and 1 GiB is 1,073,741,824 bytes. These prefixes follow the distinction described by the [National Institute of Standards and Technology](https://www.nist.gov/pml/special-publication-330/sp-330-section-3?ref=davinciresolveclub.com). ## Current YouTube and Vimeo reference rates The presets are shortcuts for planning, not secret best-quality settings. YouTube's upload guidance, checked September 8, 2026, recommends H.264 with variable bitrate and lists SDR reference rates of 8 Mbps for 1080p at standard frame rates, 12 Mbps for high frame rates, 35 to 45 Mbps for 4K at standard frame rates, and 53 to 68 Mbps for 4K at high frame rates. Its stereo audio recommendation is 384 kbps. Check the [official YouTube upload encoding settings](https://support.google.com/youtube/answer/1722171?hl=en-GB&ref=davinciresolveclub.com) before a critical delivery because platform guidance can change. Vimeo's compression guidance, checked September 8, 2026, recommends variable bitrate where available and gives broader ranges: 10 to 20 Mbps for 1080p and 30 to 60 Mbps for 4K, with AAC-LC audio at 320 kb/s. The presets keep the low and high ends separate. They are planning examples for compressed web uploads, not ProRes or DNxHR targets. Vimeo explicitly tells ProRes users to follow their editor’s standard presets. If your encoder is in a quality-based mode, use a measured representative average or a documented format rate; a quality slider is not a Mbps value. See [Vimeo's video and audio compression guidelines](https://help.vimeo.com/hc/en-us/articles/12426043233169-Video-and-audio-compression-guidelines?ref=davinciresolveclub.com) for the full table. ## Why the rendered file can differ The underlying rate-times-duration relationship gives the media payload for the actual average total data rate. A real export may differ because variable bitrate changes with scene complexity, a requested target or maximum is not necessarily the achieved average, and the container adds metadata and indexing data. Extra audio tracks, embedded captions and other streams also consume space. Vimeo likewise identifies bitrate as the main driver while noting compression settings, metadata and other video properties as additional factors in its [storage estimate explanation](https://help.vimeo.com/hc/en-us/articles/26238598856465-How-do-I-estimate-the-amount-of-storage-my-video-file-will-use-up-on-my-Vimeo-account?ref=davinciresolveclub.com). There is no trustworthy universal container-overhead percentage for every format and workflow. That's why the allowance starts at zero and remains under your control. A 10% allowance multiplies the estimated payload by 1.10; target-bitrate and recording-time modes divide the available byte budget by 1.10 first. It is not an assertion that every file has 10% overhead, nor the same as reserving 10% of the whole card. For a hard upload cap, budget below the limit, test a representative section, and inspect the complete output before uploading. A short sample cannot guarantee the size of the full film. ## Use the result for the next export decision A target bitrate is a planning constraint, not a quality score. Resolution, frame rate, codec, encoder, motion, grain and source quality all affect how well a given rate holds up. If your destination is YouTube, pair the calculation with our [DaVinci Resolve YouTube export settings](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/). For broader format choices and export troubleshooting, start from the [DaVinci Resolve export hub](https://davinciresolveclub.com/davinci-resolve-export-settings/). Need to check the queued job as well as its estimated size? Use the [export preflight checklist](https://davinciresolveclub.com/davinci-resolve-export-preflight-checker/). Find the other planning utilities in [Tools and calculators](https://davinciresolveclub.com/tools/). ## Video bitrate calculator FAQ ### Does resolution determine video file size? Not by itself. At a fixed total bitrate and duration, a 1080p and 4K file calculate to the same size. The 4K version usually needs more bitrate to preserve comparable detail, which is why platform recommendations rise with resolution and frame rate. ### Why is my rendered file different from the estimate? Variable bitrate, encoder behavior, container metadata, extra streams and rounding can move the final result. Use an actual average total rate for payload math; a preset or requested encoder target is only a planning estimate. Container data can still add bytes. ### Where do I find bitrate in DaVinci Resolve? Open the Deliver page and inspect the Quality controls for your chosen format and codec. A rate field may appear as Restrict to in Kb/s, but availability depends on the codec, encoder, operating system and hardware. ### What is the difference between MB and MiB? MB is decimal and contains 1,000,000 bytes. MiB is binary and contains 1,048,576 bytes. The calculator shows both so you can compare its result with whichever convention another app uses. ### Can a bitrate calculation guarantee an exact upload size? No. It can solve the mathematical target, but variable-rate encoding and container data can shift the finished file. Leave margin below a hard cap and verify the rendered output. ### Does this calculator upload my video or inputs? No video file is requested or uploaded. The calculation runs in this page. A shared link includes settings in its URL; opening it can expose those values to browser history, server logs or analytics. Do not treat the link as private storage. ### Does recording time prove my card is fast enough? No. It estimates capacity from available bytes and total data rate. It does not test sustained write speed, certify a memory card, detect free space or bypass camera recording limits. ### What happens after I edit a value or switch modes? The previous result is cleared. Calculate again before copying a result or a share link. Reset restores that mode’s starting values and removes the settings query from the address bar. ### DaVinci Resolve Export Preflight Checker URL: https://davinciresolveclub.com/davinci-resolve-export-preflight-checker/ Last updated: 2026-09-08T13:28:10.000Z Use this free checklist beside Resolve’s Deliver page. Enter the planned settings, confirm what you have checked in the project, then review the report before starting a long render. It cannot inspect your project or prove that the finished file is correct. **Start here:** choose a destination, open the video and audio sections, then complete the manual checks. Reference values are examples—not measurements of your timeline. Check before Start Render ## DaVinci Resolve export preflight Compare entered settings with a limited SDR reference. Check the rendered file separately after export. ### 1\. Choose the delivery target Selecting a profile doesn't change your fields until you press **Load reference values**. Delivery target YouTube SDR Vimeo SDR Custom or client specification Load reference values 2 Enter the planned export settings Copy settings from Resolve’s Render Settings panel. Container or formatMP4QuickTime / MOVMXFOther Video codecH.264H.265ProRes 422 HQDNxHROther Resolution1280 x 7201920 x 10802560 x 14403840 x 2160 / 4K UHDCustom Frame rate23.976 fps24 fps25 fps29.97 fps30 fps48 fps50 fps59.94 fps60 fpsOther / outside this reference Bitrate modeVBR targetCBR targetAuto / qualityOther Video bitrate, MbpsNo numeric rate is compared for this mode or codec. Frame rate matches the source or approved delivery spec Progressive scan is intentional 3 Check the audio export A clean picture doesn't prove the correct bus, channel layout or sample rate is being rendered. Export Audio is enabled Audio codecAACLinear PCMOther Sample rate44.1 kHz48 kHz96 kHzOther Channel layoutMonoStereo5.1 surroundOther Audio bitrate, kbpsNo AAC bitrate comparison applies with audio off or another audio codec. 4 Confirm the manual checks in Resolve Confirm each applicable item in Resolve. The audio-bus item is skipped when audio is off. Final-file playback happens after rendering, not here. **Render range is intentional**Entire Timeline, In/Out Range or the selected clips cover exactly what should be delivered. **Single Clip or Individual Clips is intentional**One finished program and a source handoff are different jobs. **Filename and destination folder are final**The output won't overwrite the wrong version or disappear into a temporary folder. **No offline-media warning is being ignored**Relink missing media before rendering unless the missing item is intentionally excluded. **Output track or bus is verified**The selected Main or Submix is the signal you monitored. **Caption delivery is decided**Burn-in, embedded captions, sidecar file or no captions matches the destination. **Proxy, optimized-media and cache use is intentional**Decide whether the final render may use those sources for this job. **Color-space and gamma tags are checked**The tags match the managed workflow and destination instead of a remembered preset. **Render Queue job details are reviewed**Name, path, range and expected output still match after the job is added. Run export preflightReset Waiting for your checks ### Check the planned export. Your report appears here after you run the check. Copy reportCopy share link No project or media upload. Calculations run in this page. Shared links contain settings in the URL; those values can appear in browser history, server logs or analytics when the link is opened. Manual confirmations reset for the recipient. **After rendering:** play the exported file outside Resolve before delivery. A completed browser checklist is not file QC, a codec-support check, or an upload guarantee. ## What this preflight checks—and what it cannot The report compares selected fields with a small set of YouTube SDR or Vimeo recommendations and lists manual items you have not confirmed. It does not read Resolve, detect offline clips or validate every codec/container combination. HDR metadata, bit depth, chroma subsampling, encoder support, loudness, disk space and actual file size still need separate checks. There are two stages: **before rendering**, review settings and the queued job; **after rendering**, inspect the output. Changing a field invalidates the previous report. Loading a reference or opening a shared link resets confirmations so another person’s ticks cannot certify your project. ![DaVinci Resolve Club export checker with reference values, settings and manual-check sections annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/preflight-tool-annotated-v2.webp) Annotated view of this website’s checker. Copy actual settings, complete the manual checks, then run the report. This is not the Resolve application. ## Inspect the Render Queue before Start Render DaVinci Resolve's Deliver page lets you queue more than one job, so check the job you are about to start. The controls you edited a minute earlier may belong to a different queued job. Confirm the output name and location, intended range and clip mode. Resolve can queue audio-only, video-only and combined outputs, which is useful but also makes the queue a place where a wrong job can look plausible. If you need the surrounding controls, follow the [complete Deliver-page export walkthrough](https://davinciresolveclub.com/export-video-davinci-resolve/). ![DaVinci Resolve 21 Render Queue with output path and offline-media warning checks](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-queue-preflight-resolve21.webp) Annotated Render Queue example: review the queued job before Start Render. The shown job names and paths are examples. ## Audio needs its own preflight For a video that needs sound, turning on Export Audio is only the first check. The selected output track or bus must carry the signal you monitored, and the requested channel layout must match the delivery. For a finished stereo mix, that's often the Stereo Main bus; stems and handoffs need a different plan. The separate [DaVinci Resolve audio export guide](https://davinciresolveclub.com/export-audio-davinci-resolve/) covers finished mixes, buses, stems and timeline tracks without pretending they are interchangeable. **Silent video is a valid choice.** Turn audio off deliberately; the tool skips the audio-bus check and asks you to review the silent output. This form needs a numeric bitrate for its AAC comparison. Linear PCM does not use that AAC target field—follow the required sample rate, bit depth and channel layout in Resolve. ![DaVinci Resolve 21 Audio export panel with Export Audio and output bus controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/export-audio-panel.webp) Annotated Audio controls. WAVE/PCM is an audio-only example, not the YouTube video preset; choose the format, sample rate and output bus required by your delivery. ## How the YouTube and Vimeo reference profiles work The built-in examples are 1080p SDR references checked September 8, 2026\. They do not cover HDR delivery or every codec. YouTube recommends MP4, H.264, progressive scan, the source frame rate, variable bitrate and 48 kHz audio. The AAC-LC example is not its only audio option: the guidance also lists Opus and Eclipsa Audio. Its SDR table lists 8 Mbps for 1080p at 24, 25 or 30 fps and 12 Mbps at 48, 50 or 60 fps. For 4K, the ranges are 35–45 and 53–68 Mbps respectively; this tool warns below the lower end, not above a supposed upload ceiling. Stereo audio is listed at 384 kbps. The checker compares your values with the [official YouTube encoding settings](https://support.google.com/youtube/answer/1722171?hl=en-GB&ref=davinciresolveclub.com) and reports differences as review notes, not proof that a file cannot upload. YouTube does not require a bitrate limit. If Resolve uses automatic or quality-based encoding, select that mode instead of inventing a Mbps value. ProRes and DNxHR also skip the numeric comparison. Vimeo explicitly points ProRes users to their editor’s standard presets. A custom resolution or unlisted frame rate produces a review note rather than a guessed bitrate verdict. Vimeo's current compression guidance accepts several codecs, recommends a constant native frame rate, progressive scan and variable bitrate where possible, and publishes broader target ranges. Its 1080p range is 10 to 20 Mbps and its 4K range is 30 to 60 Mbps; AAC-LC audio is listed at 320 kb/s and 48 kHz. Vimeo also says that MP4 and MOV are preferred containers even though many formats are accepted. The checker uses the [Vimeo compression table](https://help.vimeo.com/hc/en-us/articles/12426043233169-Video-and-audio-compression-guidelines?ref=davinciresolveclub.com) together with its [file-preparation guidance](https://help.vimeo.com/hc/en-us/articles/12426058107409-About-preparing-video-file-for-upload?ref=davinciresolveclub.com). For a full platform workflow rather than a preflight, use the [DaVinci Resolve YouTube export settings guide](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/). ## The delivery specification wins A broadcaster, client, festival, archive or VFX handoff may require MOV, MXF, ProRes, DNxHR, PCM audio, a particular channel layout or exact naming rules. In that case, choose **Custom or client specification**. The checker stops applying platform preferences and marks the result for review because it cannot read the client specification. Missing applicable values and unfinished confirmations remain visible. Don't change a written delivery requirement merely to make a generic platform profile look cleaner. Some controls vary with Resolve edition, operating system, codec, encoder and hardware. The current Resolve product page notes that Quick Export offers destination presets and common master, H.264, H.265 and audio-only options, while the Deliver page exposes the Render Queue for batch output. It doesn't make one setting universal for every codec. Check the [official Blackmagic Media page](https://www.blackmagicdesign.com/products/davinciresolve/media?ref=davinciresolveclub.com) for an overview of those delivery workflows; verify exact controls in the documentation for your installed version. ## After the render, check the file that will leave your machine Open the rendered file outside Resolve. Watch the first and last frames, then sample a few cuts, transitions, graphics and sections with heavy motion. Listen for sync, missing channels, clipping or unexpected silence. Confirm captions in the form you promised. If the picture changes in another player, use the [washed-out export diagnostic](https://davinciresolveclub.com/davinci-resolve-export-looks-washed-out/). If the job stops or fails, match the actual message against the [render-failed troubleshooting guide](https://davinciresolveclub.com/davinci-resolve-render-failed/) instead of changing random settings. For formats and delivery problems, use the [DaVinci Resolve export hub](https://davinciresolveclub.com/davinci-resolve-export-settings/). For related planning utilities, return to the [free tools and calculators](https://davinciresolveclub.com/tools/). ## DaVinci Resolve export preflight FAQ ### Does the checker inspect my DaVinci Resolve project? No. It checks only the settings you enter and the items you confirm. It cannot read your timeline, Render Settings, Render Queue, media state or final file. It also does not verify all codec/container combinations or platform and Studio support. ### Does the checker upload my project or media? No file is requested or uploaded. The comparison runs in this page. A shared link contains settings in its URL, which can appear in browser history, server logs or analytics when opened. Do not treat the share link as a private record. ### Does a YouTube or Vimeo warning mean my file will fail to upload? No. A review note can mean a difference from a recommendation or an input outside this tool’s coverage. Check the destination guidance and actual output; this report is not an upload guarantee. ### Should I use Single Clip or Individual Clips? Use Single Clip for one finished program. Use Individual Clips when the delivery requires separate clips or a handoff. Confirm the actual queued job against the delivery specification. ### Do I have to play the final file before running preflight? No. Run preflight before rendering. Once the render finishes, play the exported file outside Resolve and check picture, sound, sync, captions and the first and last frames. A ticked checklist cannot replace that inspection. ### Can I check a silent video or an automatic-bitrate export? Yes. Turn audio off intentionally to skip audio fields and the bus check. Select Auto / quality when no numeric video bitrate is set. ProRes and DNxHR also skip numeric bitrate comparison; their presets and finished output still need review. ### What happens when I change settings or open a shared link? Changing a field invalidates the previous report, so run the check again. A shared link restores settings but resets all manual, frame-rate and scan-type confirmations. The recipient must check their own project. ### What should I do when a client specification differs from a platform profile? Choose Custom or client specification and follow the written requirements. The tool does not validate that document and keeps the result marked for review. Platform reference values are not universal export rules. ### Free DaVinci Resolve Tools & Calculators URL: https://davinciresolveclub.com/tools/ Last updated: 2026-09-08T15:22:06.000Z Choose one job ## What do you need to check? Open a tool, enter the facts you know, and review the result. No installation, account or file upload is needed. [ ![Desktop and laptop hardware compatibility check for DaVinci Resolve 21](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/davinci-resolve-pc-checker-cover-v1.webp) Interactive compatibility checkerCan My Computer Run DaVinci Resolve 21?Compare your computer with Resolve 21.1’s listed requirements. Select Free or Studio and the features you use. Unknown hardware stays unresolved; meeting the checks is not a promise of smooth playback. ](https://davinciresolveclub.com/davinci-resolve-pc-checker/) [ ![Video bitrate calculator showing 8 Mbps over ten minutes equals 600 MB](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/video-bitrate-file-size-calculator-cover-v1.webp) Three-way video calculatorVideo Bitrate & File Size CalculatorEstimate file size from bitrate and duration, find a bitrate for a target size, or calculate recording time. Include audio and choose decimal or binary storage units. The result is an estimate, not a rendered-file measurement. ](https://davinciresolveclub.com/video-bitrate-file-size-calculator/) [ ![DaVinci Resolve export preflight from timeline and settings to queue and file QC](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/davinci-resolve-export-preflight-cover-v1.webp) Interactive export preflightDaVinci Resolve Export Preflight CheckerReview planned export settings before a long render. Check the range, video and audio choices, then work through the reminders. Inspect the finished file after rendering; the tool cannot inspect it for you. ](https://davinciresolveclub.com/davinci-resolve-export-preflight-checker/) Before you rely on a result ## Use the result to plan your next check A compatibility checklist cannot measure playback speed. A size estimate cannot guarantee a variable-bitrate export. And an export checklist cannot watch the finished video. Test representative media and follow the delivery specification for your actual job. For help choosing hardware or diagnosing playback, use the [Hardware & Compatibility hub](https://davinciresolveclub.com/davinci-resolve-hardware-compatibility/). For format choices, platform settings and render problems, use the [Export guides](https://davinciresolveclub.com/davinci-resolve-export-settings/). Quick questions ## Using these browser tools ### Do these tools run inside DaVinci Resolve? No. They run on this website in your browser. They are not Resolve plug-ins, do not change project settings and do not scan your hardware or media. ### Can I use them with the Free edition? Yes. These website tools are free to use. In the PC checker, choose the Resolve edition and workload you actually use; Studio AI and background-rendering requirements are checked separately. ### Can I share a result? The bitrate calculator and export preflight provide share links containing the settings entered in those tools. Anyone with the link can read those values. The PC checker does not save answers in a share URL. No project or media file is uploaded. ### DaVinci Resolve Download: Official Free & Studio URL: https://davinciresolveclub.com/davinci-resolve-download/ Last updated: 2026-09-08T12:20:59.000Z Official download routes ## Choose Free or Studio, then your computer Get DaVinci Resolve from Blackmagic Design. These links open the vendor’s pages, not an installer hosted here. Desktop release checked September 8, 2026**DaVinci Resolve 21.1**App Store releases can differ. No Studio license? ### DaVinci Resolve Free Start with the free editor. It is not a timed Studio trial. [Get Free from Blackmagic](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com) Already licensed? ### DaVinci Resolve Studio Use the separate Studio installer for your activation key, dongle or assigned Cloud license. Mac App Store purchases use the Store edition. [Find Studio in Blackmagic Support](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) **Windows:** choose **Windows x86** for Intel or AMD x64 PCs. Choose **Windows ARM** only for supported ARM hardware; the 21.1 readme lists Snapdragon X Elite and Windows 11 for ARM. Mac users choose **Mac OS X**; Linux users choose **Linux**. Check the version’s requirements before installing. One deeper guide per decision ## Download and install guides Choose your operating system, settle the Windows processor question, or find an older release. Each card opens one focused guide. [ ![DaVinci Resolve for Windows download and installation guide on a Windows editing workstation](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-for-windows-cover-v1.webp) 9 min readDaVinci Resolve for WindowsDownload from Blackmagic. Intel and AMD PCs need 64-bit Windows and the Windows x86 package; supported Snapdragon PCs use Windows ARM. Back up before updating. ](https://davinciresolveclub.com/davinci-resolve-for-windows/) [ ![DaVinci Resolve for Mac download and installation guide on an Apple silicon editing workstation](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-for-mac-cover-v1.webp) 9 min readDaVinci Resolve for MacChoose Blackmagic’s download or its official Mac App Store edition. Check your Mac’s compatibility and Studio license channel, then protect projects before installing. ](https://davinciresolveclub.com/davinci-resolve-for-mac/) [ ![DaVinci Resolve Windows x86 versus ARM build choice for Intel AMD and Snapdragon computers](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-windows-x86-vs-arm-cover-v1.webp) 9 min readWindows x86 vs ARMFor an Intel or AMD x64 PC, choose Windows x86\. For a supported Windows ARM PC, choose ARM. Check System type first, then verify drivers and plugins before moving a working project. ](https://davinciresolveclub.com/davinci-resolve-windows-x86-vs-arm/) [ ![DaVinci Resolve old versions with official archive and project backup workflow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-old-versions-cover-v1.webp) 9 min readDaVinci Resolve Old VersionsGet older Resolve installers from Blackmagic’s Support Center under Latest Downloads. Match the release, Free or Studio edition and platform; keep a compatible project backup before replacing the app. ](https://davinciresolveclub.com/davinci-resolve-old-versions/) [ ![DaVinci Resolve Studio 21 official download with activation key dongle and Blackmagic Cloud license paths](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-studio-download-cover-v1.webp) 9 min readDaVinci Resolve Studio DownloadDownload the separate Studio installer from Blackmagic’s Support Center. Use your existing activation key, dongle or assigned Cloud rental; a Mac App Store purchase needs the Store edition. ](https://davinciresolveclub.com/davinci-resolve-studio-download/) [ ![DaVinci Resolve for Linux download and installation guide on a professional editing workstation](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-for-linux-cover-v1.webp) 9 min readDaVinci Resolve for LinuxGet the official Linux ZIP, check the Rocky Linux and GPU requirements, then test your real media. Ubuntu and Debian need a separately maintained installation route. ](https://davinciresolveclub.com/davinci-resolve-for-linux/) No standard desktop installer? ### Mobile, ChromeOS and failed installations Use these guides when the device has a different Resolve route, no supported native editor, or the correct desktop package refuses to install. [ ![DaVinci Resolve for iPad download and setup guide with a professional tablet editing workflow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-for-ipad-cover-v1.webp) 9 min readDaVinci Resolve for iPadGet the official free iPad app, check your model and storage, then test a short edit and export. Studio is a separate iPad purchase; desktop project transfers need a version and media check. ](https://davinciresolveclub.com/davinci-resolve-for-ipad/) [ ![DaVinci Resolve Android and iPhone availability guide with two smartphones and a safe download check](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-android-iphone-cover-v1.webp) 7 min readResolve for Android & iPhone?No official Resolve editor runs on Android phones or iPhone. Check the genuine Camera app, avoid fake APKs, and choose between transferring footage to Resolve and editing on the phone. ](https://davinciresolveclub.com/davinci-resolve-for-android-iphone/) [ ![DaVinci Resolve on Chromebook: remote Resolve, browser editing and a separate compatible editor](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/chromebook-cover-corrected-v2.webp) 9 min readDaVinci Resolve for ChromebookNo official Resolve build supports ChromeOS. Choose remote access to a suitable Resolve computer, or use Clipchamp or a compatible local editor to finish the video on your Chromebook. ](https://davinciresolveclub.com/davinci-resolve-for-chromebook/) [ ![DaVinci Resolve installation error guide with Windows macOS and Linux repair paths](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-resolve-installation-errors-cover-v1.webp) 10 min readFix Resolve Installation ErrorsMatch the exact installation error before changing anything: check the official package, protect projects, and follow the right Windows, Mac or Linux recovery path. ](https://davinciresolveclub.com/davinci-resolve-installation-errors/) At the vendor’s download window ## Edition first. Platform second. The Free and Studio packages are separate. Still deciding? Use our [Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) and [license pricing guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/). On Windows, open **Settings > System > About** and read **System type**. Blackmagic’s x86 label does not mean a 32-bit installer. For hardware and operating-system checks, see the dated [system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). If a registration form appears, follow the current official form. A free download is not a promise of a permanent registration bypass. ![Blackmagic Design download picker with Free, Studio, Mac OS X, Linux, Windows x86 and Windows ARM choices](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-official-download-screen.webp) Official Blackmagic download picker captured September 2, 2026\. Choose the edition above the platform buttons; consult the live page for the current point release. Protect the working project ## Back up before opening it in 21.1 Blackmagic’s [21.1 Free readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) and [Studio readme](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) recommend a full project-library backup and individual project backups. They say projects opened or created in 21.1 cannot be opened in 20.3.2, even though the library remains compatible. Keep a working installer and test a disposable project before moving active work. Follow the [safe update workflow](https://davinciresolveclub.com/update-davinci-resolve-safely/) for rollback preparation. Choose the right purchase channel ## Mac App Store is a separate license Blackmagic’s [official Mac App Store listing](https://apps.apple.com/us/app/davinci-resolve/id571213070?mt=12&ref=davinciresolveclub.com) is legitimate. Studio purchases there are not interchangeable with activation keys, dongles or Cloud licenses for the direct download. If your team assigns a Cloud rental, follow Blackmagic’s [Studio sign-in instructions](https://help.cloud.blackmagicdesign.com/license-manager/logging-in-to-davinci-resolve/?ref=davinciresolveclub.com). A Cloud account by itself is not an assigned Studio license. Before you download ## DaVinci Resolve download FAQ ### Is DaVinci Resolve free to download? Yes. Choose the Free edition if you do not have a Studio license. It is not a timed Studio trial. Studio is a separate installer with its own license requirements. ### Should I download Windows x86 or Windows ARM? Choose Windows x86 for an Intel or AMD x64 Windows PC. Choose Windows ARM only for supported ARM hardware; the 21.1 readme lists Windows 11 for ARM and Snapdragon X Elite. Both branches are 64-bit. ### Where is the safest place to download DaVinci Resolve? Use Blackmagic Design’s product or Support Center pages, or its official Mac App Store listing. Avoid repackaged installers, cracks and unofficial APKs. This website does not host Resolve installers. ### What is the latest DaVinci Resolve version? Blackmagic listed DaVinci Resolve and Studio 21.1 for desktop on September 8, 2026, when this hub was checked. Mac App Store and iPad releases can differ. Check the vendor’s current listing before downloading. ### Can I download an older DaVinci Resolve version? Yes. Blackmagic keeps older releases in its Support Center. Match the edition, version and platform, and keep compatible project backups. Installing an older app does not make a newer project backward-compatible. ### Does DaVinci Resolve need an activation key? The Free edition does not need a Studio activation key. The direct Studio edition supports an activation key, license dongle or assigned Blackmagic Cloud license. Mac App Store Studio purchases use a separate Store license. ### Can I install DaVinci Resolve on both Mac and Windows? Blackmagic provides separate Mac and Windows packages. Each computer must meet its version’s requirements. For Studio, check the license channel and activation limits; a Mac App Store purchase is not a Windows Studio license. Test media paths, plug-ins and project compatibility before moving work. ## Posts ### DaVinci Resolve for Chromebook: What Actually Works URL: https://davinciresolveclub.com/davinci-resolve-for-chromebook/ Last updated: 2026-09-08T11:49:26.000Z **Quick answer:** there is **no supported native DaVinci Resolve installation for Chromebook** as of September 8, 2026\. Blackmagic offers desktop packages for Mac, Windows and Linux, but no ChromeOS installer, browser-native editor or Chromebook APK. To use Resolve from a Chromebook, run it on a suitable remote computer. To finish a video locally or in Chrome, choose a different editor. The Linux download is not a hidden ChromeOS version. ChromeOS’s Linux environment and Blackmagic’s supported Linux setup differ in operating system, graphics access and drivers. An installer window opening does not establish that the editor can import, play or export your footage. **Need the real installer?** Start at the [DaVinci Resolve Download & Install hub](https://davinciresolveclub.com/davinci-resolve-download/). This page is the ChromeOS decision guide: when to use a browser editor, when to remote into a Resolve computer and when the Chromebook is simply the wrong machine. ## Choose the Job Before You Choose the Workaround A Chromebook can still help you make video. The useful question is not “Can I force the Resolve installer to open?” It is “Which part of this project must happen on the Chromebook?” | Your actual need | Best route | What to expect | | ---------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------- | | Learn Resolve menus and edit a real Resolve project | Remote access to an already working Resolve computer | Test the remote session, including GPU access, picture and sound | | Cut a short school, social or YouTube video | Use a supported browser editor such as Clipchamp | No native install, but simpler projects can be completed in Chrome | | Edit locally with multiple tracks and touch controls | Check LumaFusion in Google Play | Paid separate editor; check device compatibility and feature requirements | | Grade, composite or finish demanding 4K work | Use a supported Resolve computer | A Chromebook is a companion, not the render workstation | If you only need to submit a two-minute class video, building a remote workstation may be unnecessary. If you must learn Resolve for a course or deliver a Resolve project archive, switching to a different editor may create a different problem. Decide which constraint is real before spending money or changing the Chromebook. For learning before you have a Resolve computer, you can watch [Blackmagic’s training videos](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com) on the Chromebook. That helps with terminology and editing decisions; doing the exercises still needs access to Resolve. The [beginner tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) provides a route once that access is ready. ## Why the Linux Installer Does Not Make Resolve a Chromebook App Google’s [Chromebook Linux setup guide](https://support.google.com/chromebook/answer/9145439?hl=en&ref=davinciresolveclub.com) describes a Debian development environment inside ChromeOS. The [Resolve 21.1 readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) instead lists Rocky Linux 8.6, 32 GB RAM and a discrete GPU with at least 4 GB VRAM, plus OpenCL 1.2 or CUDA 12.8 and supported drivers. Those requirements apply to the computer running Resolve, not the Chromebook displaying a remote session. ![Official Blackmagic Design picker with Windows x86 and Windows ARM DaVinci Resolve downloads](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-windows-installer-picker.webp) Blackmagic’s official download picker offers desktop platform choices, not a ChromeOS installation. The Linux button is not a Chromebook compatibility setting. There is a graphics distinction that many Chromebook installation guides miss: 1. Google’s general Linux help lists GPU and video-decode acceleration as unsupported. That should not be stretched into “Linux apps on every Chromebook have no graphics acceleration.” 2. Google’s ChromeOS engineers have documented [accelerated OpenGL through VirGL](https://chromeos.dev/en/posts/improving-vulkan-availability-with-venus?ref=davinciresolveclub.com) for Linux apps in a virtual machine. Their 2022 article describes graphics architecture, not a current Resolve compatibility list. 3. Virtualized OpenGL is not proof of the supported OpenCL/CUDA compute and driver stack Resolve requires. Neither a Linux flag nor a Chromebook Plus badge supplies Blackmagic support. You may find scripts or videos that reach an installer window. Treat those as experiments, not a dependable way to finish a project. Before trusting any such result, you would need evidence of the exact device, OS, drivers, media formats, playback, audio and export. For a separate supported Linux machine, use the [Linux installation guide](https://davinciresolveclub.com/davinci-resolve-for-linux/); do not transplant its commands into Crostini. Do not disable security or replace the operating system just to follow an undated tutorial. Protect local files and respect school or employer policies. Changing the OS can put data at risk and still leave the hardware unsuitable for Resolve. ## Option 1: Run Resolve on Another Computer and Control It from Chromebook Remote access keeps the real Resolve project and tools available: the host computer runs the editor, while the Chromebook sends your input and receives a streamed view. Start with a host on which Resolve already works locally. A remote connection does not repair an unsupported GPU or broken installation. For an existing Mac or Windows host, follow Google’s [Chrome Remote Desktop setup instructions](https://support.google.com/chromebook/answer/1649523?hl=en&ref=davinciresolveclub.com) while you can still reach the computer locally. Install the host component, complete the security prompts and set a private access PIN. Do not leave the machine unattended until you have tested Resolve through the remote session. **Linux host caveat:** Google’s Linux instructions use a 64-bit Debian package and a virtual desktop session. Do not assume they apply unchanged to Blackmagic’s Rocky Linux setup or expose the GPU Resolve needs. Use a remote solution appropriate to that host and verify Resolve inside the actual session. 1. Open [Chrome Remote Desktop Access](https://remotedesktop.google.com/access?ref=davinciresolveclub.com) on the host and complete Set up remote access. Resolve must already open and play representative media locally. 2. Keep the working project and camera files accessible to the host. If its own timeline struggles with difficult source footage, consider [proxy media on the Resolve host](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/). Proxies reduce decoding work; they do not remove network delay. 3. On the Chromebook, open the same Access page, sign in with the intended Google account, select your configured computer and enter its PIN. This is your remote-access setup, not a public support code to share. 4. Test the actual session: Resolve’s GPU access, picture, audio, keyboard shortcuts, pointer control and a short export. Permission prompts or organizational policies may require help from the administrator. 5. Render on the host, then copy the finished file or review version to the destination where you need it. Play that copy outside Resolve before delivery. Use the remote session for organizing media, rough cuts, review changes and exports. Do not rely on a compressed remote view for final color or critical audio decisions. Check those through a trusted display and audio path at the editing workstation. The host must stay awake, online and connected to its media. Test what happens after a restart before depending on unattended access. If you rent a cloud computer instead, check the GPU, remote-session support, Resolve license requirements, storage, transfer costs and data policy before paying. A cloud-PC subscription is not automatically a Studio license. ## Option 2: Edit in the Browser with Clipchamp Microsoft documents [Clipchamp on Chromebook](https://support.microsoft.com/en-us/clipchamp/using-the-clipchamp-video-editor-on-a-chromebook?ref=davinciresolveclub.com) for both personal and work or school accounts. It uses Chrome and requires an internet connection, even when you work with local files. Do not assume that “browser editor” means a remote server removes every load from your Chromebook. ![Clipchamp Import media menu with pointers to the button and local or cloud file sources](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/clipchamp-import-annotated-v1.webp) Annotated [Microsoft personal-account interface example](https://clipchamp.com/en/blog/google-drive/?ref=davinciresolveclub.com). Use Browse files for local footage; cloud options depend on your account. This is Clipchamp, not Resolve in a browser. For a personal account, open [Clipchamp](https://app.clipchamp.com/?ref=davinciresolveclub.com); work or school accounts use their OneDrive or SharePoint route. Choose **Import media > Browse files** for local clips, drag them onto the timeline, make a short edit, then use **Export** and save the result to your computer. Check the downloaded file’s picture and sound. Cloud import choices can differ by account. Microsoft warns that some Chromebooks can struggle with projects longer than ten minutes or very large 4K files. This is not a hard ten-minute limit. Start with representative footage, complete a short edit and export it before importing an entire shoot; your hardware, source files and effects determine whether the workflow is practical. A browser editor is not “DaVinci Resolve online.” Project files, effects, shortcuts, color tools and collaboration models are different. Use this route when the deliverable matters more than keeping a Resolve project. ## Option 3: Check a Local ChromeOS or Android Editor Google supports [Android apps on compatible Chromebooks](https://support.google.com/chromebook/answer/7021273?hl=en&ref=davinciresolveclub.com), not every model. Its [Play compatibility guidance](https://support.google.com/googleplay/answer/2851648?hl=en&ref=davinciresolveclub.com) explains that device, Android version, screen and region can affect availability. Check the app listing on your exact Chromebook rather than trusting an editor roundup. [LumaFusion for Android and ChromeOS](https://luma-touch.com/lumafusion-for-android/?ref=davinciresolveclub.com) is a separate paid multitrack editor. LumaTouch lists Android 10 or later and at least 3 GB RAM; those are requirements, not a promise of smooth 4K editing. Check its [live Google Play listing](https://play.google.com/store/apps/details?hl=en&id=com.luma%5Ftouch.lumafusion&ref=davinciresolveclub.com) for your device’s compatibility, current purchase terms and optional paid features. A school or employer may block Play Store installs. ![LumaFusion media library, preview and multitrack timeline identified in the Android interface](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/lumafusion-annotated-v1.webp) Annotated [LumaTouch Android interface example](https://luma-touch.com/lumafusion-for-android/?ref=davinciresolveclub.com): media library, preview and timeline. Check compatibility and the layout on your Chromebook; this is a different editor, not a Resolve port. Before buying, check compatibility, required features and purchase terms. Once you have legitimate access to the editor, test the parts that decide whether it can deliver your project: - Can it import the camera's actual video and audio codecs? - Does a five-minute timeline remain responsive with your effects? - Can it export the required resolution, frame rate and file format? - Is there a watermark, storage cap or paid feature blocking delivery? - Can you back up or move the project itself, as well as export the video? ## What a Chromebook Plus Changes A stronger Chromebook can make a browser or compatible Android editor more useful. The **Chromebook Plus** name does not add a ChromeOS build of Resolve, however. Do not buy one expecting the Linux button to turn it into a supported Resolve workstation. If Resolve is non-negotiable, compare access to a suitable host with the cost of a computer that runs it directly. Use our [Resolve system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) to evaluate that machine. CPU branding alone does not settle GPU, memory, codec or storage needs. ## What About ChromeOS Flex? ChromeOS Flex is not a supported Resolve platform either. Google’s [Flex differences page](https://support.google.com/chromeosflex/answer/11542901?hl=en&ref=davinciresolveclub.com) says Linux development support depends on the model and describes only a narrow Android VPN-app exception. That is not ordinary Google Play editor support: do not assume the LumaFusion route above applies to Flex. Consider browser editing or access to a suitable remote host instead. ## Avoid Fake Chromebook Downloads [Blackmagic's own Resolve download page](https://www.blackmagicdesign.com/event/davinciresolvedownload?ref=davinciresolveclub.com) is the identity check. If a page claims to provide a ChromeOS installer, browser extension, cracked web edition or “DaVinci Resolve APK for Chromebook,” it is not an official Resolve distribution. For Blackmagic’s genuine phone apps and their limits, see the [Android and iPhone compatibility guide](https://davinciresolveclub.com/davinci-resolve-for-android-iphone/). A familiar logo on a download page does not make an unofficial installer authentic. Do not enable unknown sources, paste terminal commands you have not inspected or upload a project archive to a site just because its page uses the Resolve logo. A converter or remote service may be legitimate, but it should describe its own product honestly. It should not pretend to be a Blackmagic installer. ## Chromebook Resolve Troubleshooting | What you see | What it means | Best next move | | -------------------------------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | No ChromeOS option on Blackmagic's download page | There is no native Chromebook package | Choose remote Resolve or a Chromebook editor | | The Linux installer extracts but Resolve will not launch | Package extraction did not solve the OS, GPU or driver boundary | Stop treating Crostini as a supported workstation | | Google Play says an editor is incompatible | The app or device does not meet the current compatibility rules | Use a browser editor or another supported device | | Remote Resolve feels delayed | The host, network or stream is the bottleneck | Compare local host playback with remote playback; use proxies for host decoding, and troubleshoot the network separately | | Browser export fails on a long project | A resource, source-media or export problem needs investigation | Keep the error; test representative shorter sections and available storage before retrying the full job | The key test is a finished round trip. Import representative media, edit long enough to expose performance problems, export the intended format and play the result outside the editor. Opening a timeline is not proof that the workflow can deliver. ## Frequently Asked Questions ### Can I download DaVinci Resolve on a Chromebook? No official native ChromeOS version is available as of September 8, 2026\. Blackmagic’s desktop packages are for Mac, Windows and Linux. A Chromebook can display and control Resolve on a suitable remote computer, but that is not a local Resolve installation. ### Can I install the Linux version of Resolve on ChromeOS? Crostini is not a supported Resolve configuration. Its Debian environment and virtualized graphics are not equivalent to the Rocky Linux and discrete GPU compute/driver stack listed for Resolve 21.1\. Some Linux apps can use accelerated graphics on ChromeOS; that does not establish Resolve compatibility. ### Does DaVinci Resolve work on Chromebook Plus? There is no native Resolve build for Chromebook Plus. Better hardware may help compatible browser and Android editors, but it does not change Blackmagic’s supported operating systems. Use a suitable remote Resolve host or a different editor. ### Is there a DaVinci Resolve APK for Chromebook? There is no official Resolve APK or ChromeOS installer. Verify downloads through Blackmagic’s website and official app stores. Blackmagic Camera on a compatible Android device is a capture app, not the Resolve editor. ### Can I use DaVinci Resolve through a web browser? Blackmagic does not offer a browser-native Resolve editor. A browser can connect to a separate computer running Resolve through a suitable remote-access service. Chrome Remote Desktop is one route for an already working Mac or Windows host, subject to permissions and an actual session test. ### What is the best Resolve alternative for Chromebook? For a short browser edit, Clipchamp has official Chromebook instructions. For a local multitrack editor, check LumaFusion’s requirements and Play compatibility on your device. If you need the Resolve project and tools themselves, use a suitable remote Resolve workstation instead. ### Can a Chromebook edit 4K video? It depends on the editor, device and footage. Microsoft specifically warns that some Chromebooks struggle with large 4K files in Clipchamp. Test representative clips, effects and a full export before committing. Native Resolve finishing still requires a supported editing computer. ### DaVinci Resolve Installation Errors: Fix the Installer URL: https://davinciresolveclub.com/davinci-resolve-installation-errors/ Last updated: 2026-09-08T10:09:01.000Z **Quick answer:** match the DaVinci Resolve installer’s exact message before deleting or reinstalling anything. Start with a fully extracted official package for your operating system and processor. If Windows reports an existing version, check the installed Resolve entry; if macOS blocks the file, read the warning before considering an exception. Keep project backups separate from installer cleanup. Do not start by deleting Blackmagic folders or registry keys. First protect the project library, record the error word for word, confirm whether the download is Resolve or Resolve Studio, and confirm the operating system and architecture. A repair for “ResExt.cab is corrupt” is not the repair for “a newer version is already installed.” **Still choosing the package?** Use the [Download & Install hub](https://davinciresolveclub.com/davinci-resolve-download/) first. This page starts when the official package will not extract, install, update or complete normally. ## Before You Change Anything If Resolve opens, back up the project library and export critical projects before changing versions. Keep the source media separately too. The [Resolve 21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) warn that projects created or opened in 21.1 cannot be opened in 20.3.2, even though the library can remain accessible. Reinstalling an older editor does not reverse that change. Follow the [safe-update backup steps](https://davinciresolveclub.com/update-davinci-resolve-safely/) before proceeding. If Resolve cannot open, preserve its existing library and media locations; do not delete them to make setup run. 1. Photograph or copy the complete error, including its numeric code. 2. Write down the current Resolve version and whether it is Free or Studio. 3. Record the OS version and, on Windows, whether the computer is x64 or ARM64. 4. Keep a known-good previous installer if you may need to roll back; do not keep using a damaged or security-flagged download. 5. Restart once before retrying so a pending update or installer process is not holding files. Identify the last successful stage: download, extraction, setup or first launch. If the installed editor opens and then hangs, the launch message becomes the useful clue. That does not prove every installed file is healthy, but it is different from a ZIP that never extracted. ## Match the Symptom to the First Safe Fix | Message or symptom | What to check | First safe action | | -------------------------------------------------------------- | -------------------------------------------------------------- | ----------------------------------------------------------------------------------- | | “Failed to open, extract all files before executing” | Incomplete extraction or failure opening the installer payload | Extract the entire official ZIP to a new local folder | | “A newer version of Resolve is already installed” | Existing version, downgrade or stale Windows installer data | Check Settings > Apps > Installed apps before deeper recovery | | “ResExt.cab … is corrupt” | Package or file-reading failure | Delete that extracted copy, download again and extract again | | Setup completes, but Resolve is missing | Wrong component, installer reopened or app search confusion | Check Installed apps and the Resolve component selection | | macOS cannot verify or open the package | Gatekeeper, damaged file or wrong package | Verify source and warning type before any override | | Linux permission or unsupported GPU message | Executable permission, distro or driver stack | Compare the system with the current Resolve readme | | “Network resource unavailable” or missing ResolveInstaller.msi | Windows needs installation data it cannot find | Record the exact requested file and version; use the matching Windows recovery path | | Error 2755 | Unexpected package-install error; the nested error matters | Keep the full message and package path before attempting a fix | ## Start with a Fresh Official Package Get a fresh package from the [Blackmagic Design Support Center](https://www.blackmagicdesign.com/support/?ref=davinciresolveclub.com), not a mirror or repacked installer. Check both the edition and the operating-system button. DaVinci Resolve and DaVinci Resolve Studio are separate downloads; choosing Studio is not an installer repair for the free edition. ![Official Blackmagic Design picker with Windows x86 and Windows ARM DaVinci Resolve downloads](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-windows-installer-picker.webp) Blackmagic’s download picker separates the edition and platform. Choose the intended Resolve or Studio column, then the correct operating system and Windows architecture; this is not a compatibility test. On an Intel or AMD x64 Windows PC, choose **Windows x86** in Blackmagic’s picker. On an ARM-based PC, check the supported hardware before choosing Windows ARM: the 21.1 readme lists Windows 11 for ARM and Snapdragon X Elite. In Windows, open Settings > System > About and read **System type**. The [x86 versus ARM guide](https://davinciresolveclub.com/davinci-resolve-windows-x86-vs-arm/) explains the labels and compatibility limits. ![Windows 11 System type showing a 64-bit operating system and x64-based processor for the Resolve Windows x86 download](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/windows-system-type-v2.webp) Annotated Windows Settings example: the System type row identifies an x64-based processor. The other example specifications are not a Resolve recommendation. Read the same field on your own PC before changing installer packages. Download to local storage with room for both the archive and extracted files. On Windows, right-click the ZIP and choose [Extract All](https://support.microsoft.com/en-us/windows/experience/storage-filemanagement/zip-and-unzip-files?ref=davinciresolveclub.com). Wait for extraction to finish, then open the installer from the new folder. Keep everything extracted together; do not reuse a partly extracted folder from a failed attempt. ## Fix Windows Extraction and Corrupt Cabinet Errors For “Failed to open, extract all files before executing,” close setup and extract the entire ZIP to a fresh local folder. The message is a reason to check extraction, not proof that you forgot to unzip it. If it returns after a complete extraction, record that fact and move to a fresh official download rather than repeating the same attempt. A **ResExt.cab** corruption message means setup could not use a required cabinet payload. Microsoft’s [Windows Installer error reference](https://learn.microsoft.com/en-us/windows/win32/msi/windows-installer-error-messages?ref=davinciresolveclub.com) describes this as error 1335; the package or the way it is being read can be involved. Remove only the failed extracted installer copy, download again and retry locally. If it repeats, record the full message, check available system-drive space and report any other file-reading errors to support. Do not delete a Windows Installer cache folder. Do not start by opening the installer’s internal DAT file and running a discovered MSI. Blackmagic’s documented route is to run its installer and follow the prompts. If a complete fresh package still fails, retain the filename, exact message and any log setup offers so support can identify the failing component. ## Fix “A Newer Version of Resolve Is Already Installed” This message can be accurate. In a [Windows reinstall discussion](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=176119&ref=davinciresolveclub.com), Blackmagic support explains that newer versions can install over the current one, while same-version installs and downgrades require removing the existing Resolve entry. The example is a Free-to-Studio change at the same version. Treat that as a reason to inspect what is installed, not a reason to erase every Blackmagic folder. 1. Open Settings > Apps > Installed apps. 2. Look specifically for DaVinci Resolve. Do not remove Blackmagic RAW, Fairlight or hardware drivers merely because they share the vendor name. 3. If Resolve is listed and you intentionally need a same-version reinstall, downgrade or Free/Studio swap, back up projects and uninstall that Resolve entry. 4. Restart Windows. 5. Run the fresh extracted package that matches the intended edition and architecture. If removal fails, follow Microsoft’s [recovery instructions for your Windows version](https://support.microsoft.com/en-us/windows/deployment/install-upgrade/fix-problems-that-block-programs-from-being-installed-or-removed?ref=davinciresolveclub.com). Its Windows 11 section starts with restart, supported app-repair options and uninstalling from Settings; not every desktop app has Repair or Reset. The downloadable Program Install and Uninstall troubleshooter is described under Windows 10\. Do not assume an old video’s screens or tool apply unchanged to Windows 11\. If Windows offers troubleshooting when removal fails, keep its exact result for support. Do not delete a vendor-wide registry branch or use a sweeping “cleaner.” If the normal Resolve uninstall entry is broken, ask Blackmagic support for a repair matched to that version and message. Keep your backups and the failed setup evidence intact. ### Missing MSI, “Network Resource Unavailable” or Error 2755 If uninstall asks for **ResolveInstaller.msi** or an unavailable network resource, save the exact filename, requested location and installed version. It does not necessarily mean your internet connection failed. Do not browse to an arbitrary MSI from a different release or download a loose installer file from a mirror. Use the Windows recovery route above and ask Blackmagic for the matching package if the original source is required. **Error 2755** is not a diagnosis of one missing folder. Microsoft defines it as an unexpected server error while installing a package, with a second error value and package name. Capture those details. A fresh official package on accessible local storage is a reasonable first check; recreating Windows system directories, changing their permissions or disabling security is not a general fix for this number. ## When Setup Finishes but You Cannot Find Resolve The downloaded installer and the installed Resolve application are different files. Reopening the installer starts extraction again; it does not launch the editor. On Windows, search the Start menu for **DaVinci Resolve** and check Settings > Apps > Installed apps. If only control-panel software appears, rerun the official package and confirm that the DaVinci Resolve application component is selected. On macOS, look in Applications. On Linux, verify the application entry and installation output rather than reopening the .run package. If the installed Resolve application closes, hangs or reports a GPU error, switch to [startup-crash troubleshooting](https://davinciresolveclub.com/davinci-resolve-keeps-crashing/). A partial installation is still possible, but repeatedly reopening the ZIP will not distinguish missing files from GPU drivers, plugins or preferences. Keep the launch message separate from any setup error. ## Fix macOS Package and Security Messages Apple’s [Gatekeeper guidance](https://support.apple.com/en-gb/102445?ref=davinciresolveclub.com) distinguishes a routine first-open confirmation from an unverified developer, damaged software or a malware warning. macOS checks developer signatures and notarization for software downloaded outside the App Store. These warnings do not all justify the same response. ![macOS Privacy and Security Open Anyway example with editorial cautions about source and malware warnings](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/macos-open-anyway-apple-framed.webp) Apple’s Privacy & Security example with added editorial cautions. “Example App” is a generic illustration, not a reproduced Resolve failure. Only consider Open Anyway after verifying the source and warning; never use it to bypass a malware alert. - **Downloaded from the Internet:** this is the normal first-open confirmation for an identified developer. Confirm Blackmagic as the source, then continue. - **Apple cannot check it or the developer cannot be verified:** first delete the copy and download the current package directly from Blackmagic. Use Open Anyway only if the source and package are trusted. - **Will damage your computer or contains malware:** do not override the warning. Delete the file and contact Blackmagic if a fresh official copy receives the same alert. - **App is damaged:** treat the copy as corrupted or altered. Download again instead of disabling Gatekeeper globally. For a generic installer failure, check the package’s requirements first. Resolve 21.1 lists **macOS 15 Sequoia or later and Apple Silicon**; a security exception cannot make an Intel Mac compatible. Check free startup-disk space and whether you have the required administrator access. If a managed Mac hides the security option, contact its administrator. Use the [Mac installation guide](https://davinciresolveclub.com/davinci-resolve-for-mac/) for the correct package and platform route; do not rename or remove Application Support folders as an opening move. ## Fix Linux Installer Failures Without Hiding a Platform Mismatch The [Resolve 21.1 readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) lists Rocky Linux 8.6, 32 GB of system memory and a discrete GPU with at least 4 GB VRAM as the basic Linux requirements. It also specifies OpenCL 1.2 or CUDA 12.8 and the required driver versions. These are not universal Studio workload recommendations: the [Studio 21.1 notes](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) list higher memory requirements for advanced AI and background rendering. Identify a permission failure separately from a missing library or unsupported GPU. 1. Confirm that the package is the current Linux download from Blackmagic. 2. Extract it completely and review the included release notes. 3. If the .run file is not executable, add execute permission to that exact downloaded file, then run it from a terminal so the message remains visible. 4. Compare the OS, RAM, GPU, VRAM and driver requirement with the current readme. 5. If using Ubuntu, Debian, Fedora or Arch, separate third-party packaging problems from official Rocky Linux support. If the terminal names a missing library, preserve the exact name and OS version before installing packages. Do not assume a dependency command written for Ubuntu 22.04 is right for another distribution or release. Continue with the [Linux installation and compatibility guide](https://davinciresolveclub.com/davinci-resolve-for-linux/) for distro-specific routes. Community repackaging is not the same as Blackmagic support, and bypassing a dependency check does not install the dependency. ## Prove the Repair Launch the installed editor, confirm its version, and test with a disposable project and representative media. Check picture and sound, then play a short export outside Resolve. This is a useful check of your own setup, not a guarantee that every plugin, codec or long render will work. Before opening valuable projects, confirm the intended version and backup location; if you are downgrading, use the [older-version compatibility checks](https://davinciresolveclub.com/davinci-resolve-old-versions/) first. If setup still fails, send support the installer filename, edition, OS build, processor architecture, complete error, failed stage and available system-drive space. Include any log or log location offered by setup; if none is shown, ask which installer log they need. A launch diagnostic is not automatically an installer log. Review logs for account names, local paths and other private information before posting them publicly. ## Frequently Asked Questions ### Why does DaVinci Resolve say “extract all files before executing”? The message asks you to check extraction, but it can appear even after unzipping. Extract the entire official ZIP into a fresh local folder, keep its files together and run setup there. If it repeats, retry a fresh official download and preserve the complete error. ### How do I fix “a newer version of Resolve is already installed”? Check the existing DaVinci Resolve entry in Windows Installed apps. Same-version installs, downgrades and a Free/Studio swap may require uninstalling that entry first. Back up projects, use the normal uninstall route, and follow Microsoft’s instructions for your Windows version if removal fails. Do not delete registry branches blindly. ### What does a corrupt ResExt.cab error mean? Setup cannot use a required cabinet payload; a damaged package or a file-reading problem can be involved. Remove only the failed extracted installer copy and retry a fresh official download on local storage. If the same message returns, keep the full error and any installer log, check available disk space and contact support. ### Why did installation finish but DaVinci Resolve is missing? You may be reopening the downloaded installer, may have installed only an optional component or may be looking outside the installed-app list. Search for DaVinci Resolve in Start or Applications and confirm the Resolve component was selected in setup. ### Should I disable antivirus or Gatekeeper to install Resolve? Do not disable system security globally. Read the exact warning and verify the official download. Do not override a malware alert or an organization’s security policy. On macOS, Apple allows a per-app exception for certain verification warnings only when you are sure the app is trustworthy and untampered; a malware warning is different. ### Do I need to uninstall Resolve before updating? On Windows, a newer Resolve release can usually be installed over the current version. A same-version reinstall, downgrade or Free/Studio swap may require uninstalling first. Back up projects before changing versions: installing an older editor does not reverse changes made when a newer version opened a project. ### Why does Resolve still fail after it installed successfully? You now have a first-launch failure to investigate. GPU drivers, unsupported hardware, plugins, preferences or incomplete installation files can be involved. Keep the launch message and use startup troubleshooting rather than assuming that repeating the installer will identify the cause. ### DaVinci Resolve for Android & iPhone: Is It Available? URL: https://davinciresolveclub.com/davinci-resolve-for-android-iphone/ Last updated: 2026-09-08T09:22:21.000Z **Quick answer:** there is **no official DaVinci Resolve editor for Android phones or iPhone** as of September 8, 2026\. Blackmagic offers the desktop editor for Mac, Windows and Linux, plus [DaVinci Resolve for iPad](https://apps.apple.com/us/app/davinci-resolve-for-ipad/id1581363826?ref=davinciresolveclub.com). For capture on compatible phones, use Blackmagic Camera. It records and manages footage; it does not put the Resolve timeline, Color page, Fusion or Fairlight on your phone. If a site offers a “DaVinci Resolve APK,” do not install it. There is no Blackmagic Resolve package on Google Play to match that claim. The useful phone workflow is to capture with Blackmagic Camera or another trusted camera app, then edit on an iPad or supported computer. **Looking for a real installer?** Use the [Download & Install hub](https://davinciresolveclub.com/davinci-resolve-download/) for Windows, macOS, Linux, Studio and the official iPad route. This page is specifically about phone availability and the safest way to move phone footage into Resolve. ## What Blackmagic Actually Offers on Each Device The product names matter here. Search results often use “DaVinci mobile” for anything connected to Blackmagic, but the apps do different jobs. Blackmagic's current [Resolve product page](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com) lists the full editing software for Mac, Windows and Linux. Apple's editor listing is explicitly named DaVinci Resolve for iPad. Neither source presents a Resolve editor for Android phones or iPhone. | Device | Official Blackmagic option | What it does | | ------------------------------ | -------------------------------------- | ----------------------------------------------------- | | Android phone or tablet | Blackmagic Camera on supported devices | Capture, monitor, manage and upload footage | | iPhone | Blackmagic Camera and Remote Monitor | Capture or monitor, not full Resolve editing | | iPad | DaVinci Resolve for iPad | Dedicated touch editor with hardware-dependent limits | | Mac, Windows or Linux computer | DaVinci Resolve or Resolve Studio | Full desktop post-production application | Blackmagic Camera records footage; [Blackmagic Remote Monitor](https://apps.apple.com/us/app/blackmagic-remote-monitor/id6446672513?ref=davinciresolveclub.com) receives a viewing stream from supported Blackmagic products, including Resolve Studio. Seeing that stream on an iPhone is not the same as running the editor or controlling its timeline. Neither app is an iPhone version of Resolve. ## How to Verify an Official Mobile App Do not judge an app by its icon, screenshots or use of the word “DaVinci.” Check the store identity before installing: 1. Open Google Play or Apple's App Store yourself rather than following an APK button. 2. Confirm the developer is **Blackmagic Design Inc**. 3. On the official Android listing, check the package ID in the page address: `com.blackmagicdesign.android.blackmagiccam`. A copied name or package string on a different website is not proof of authenticity. 4. Read the store's compatibility result for the exact device. 5. Reject any page claiming that enabling “unknown sources” is required for DaVinci Resolve. An unrelated developer can publish an editing guide, wallpaper app or simple video maker with a similar name. That does not make it a Blackmagic product. Even a clean malware scan would not turn the wrong app into Resolve. ## Use Blackmagic Camera on iPhone For recording on an iPhone, use [Blackmagic Camera from Apple’s App Store](https://apps.apple.com/us/app/blackmagic-camera/id6449580241?ref=davinciresolveclub.com). The US listing checked on September 8, 2026 names Blackmagic Design Inc, offers the app free and reports **version 3.4.1**. It requires **iOS 17.0 or later and an A12 Bionic chip or newer**. Check the compatibility panel on your own device before planning a shoot around it. ![Blackmagic Camera iPhone recording controls with frame rate, shutter, white balance and audio meters](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-camera-iphone-app-store.webp) Blackmagic Camera recording-interface example. Check the capture settings and sound before a take; this is not a Resolve editing timeline. Layouts can differ by device and app version. The app exposes camera controls such as frame rate, shutter angle, white balance, ISO, audio meters and monitoring aids. On supported Apple hardware, recording options can include ProRes as well as H.264 and H.265\. Available formats, frame rates and lenses still depend on the exact iPhone, storage path and current app version. Start with a short clip using the intended resolution and frame rate. Record picture and sound, stop, then open the clip in Media. If the file is missing or playback is wrong here, sort that out before adding a transfer or Cloud sync to the problem. ## Use Blackmagic Camera on Android Open [Blackmagic Camera on Google Play](https://play.google.com/store/apps/details?id=com.blackmagicdesign.android.blackmagiccam&hl=en%5FUS&ref=davinciresolveclub.com). The listing checked on September 8, 2026 names Blackmagic Design Inc, shows an update date of **September 3, 2026** and identifies **3.4.3 in What’s new**. Use the live listing for your device’s install eligibility; the version number alone does not mean that every Android phone supports the same recording features. ![Blackmagic Camera Android capture interface alongside an explanation that it is not the Resolve editor](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-camera-android-google-play.webp) Camera-interface example with editorial labels: recording controls on the left, the app’s role on the right. Check Google Play on your own phone for compatibility. Blackmagic’s [Camera product page](https://www.blackmagicdesign.com/products/blackmagiccamera?ref=davinciresolveclub.com) describes compatible Android phones and tablets, while Google Play warns that some features are device-dependent. Camera access, codecs, lenses, storage and sustained recording can differ between models. If Play says your device is incompatible, an APK mirror does not establish that those functions will work. For a long take, check more than whether the app opens. Test the required duration, sound synchronization and storage destination on that phone. Keep the working app version and settings with your shoot notes so you can repeat the setup. ## Move Phone Footage into Resolve Blackmagic documents three Camera workflows: record locally and move the clips, upload selected media, or record into a Blackmagic Cloud project. Choose by connection speed, file size and who needs the footage. Open Media to review clips and check the intended destination before uploading; a thumbnail alone does not confirm delivery. ![Blackmagic Camera Media view with numbered pointers to Media, All Clips and Cloud Folders](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-camera-media-transfer-annotated-v1.webp) Annotated [Blackmagic Camera Media example](https://www.blackmagicdesign.com/products/blackmagiccamera?ref=davinciresolveclub.com): 1 opens Media, 2 selects All Clips, and 3 identifies Cloud Folders. The example says “No project selected”; do not treat visible thumbnails as proof that originals reached the editor. ### Local transfer Record to device storage or a supported external drive, then copy the files to the computer or project drive. Verify the copy before deleting anything from the phone. A local transfer avoids waiting for a mobile upload when the connection is slow or the camera originals are large. ### Selected upload Record locally and upload only the clips the editor needs first. This can reduce mobile data and keep rejected takes off the transfer queue. Preserve the originals until the editor confirms receipt and playback. ### Blackmagic Cloud workflow The [official Blackmagic Camera workflow](https://www.blackmagicdesign.com/products/blackmagiccamera?ref=davinciresolveclub.com) can sync media into a Resolve project, including proxy-first workflows on supported setups. A free Blackmagic ID is not the same thing as unlimited free Cloud Storage. Check the current storage plan, project assignment and upload state before relying on it. Whichever route you choose, preserve the original filename and avoid messaging apps that silently recompress video. In Resolve, check frame rate, color interpretation, audio channels and timecode before cutting. For a multicamera job, test synchronization before the event rather than after every phone has recorded hours of footage. ### Run one end-to-end test before the real shoot Use the exact phone, recording format, storage destination and transfer method planned for the job. Record sound and movement for long enough to represent the take you need. A brief successful test cannot establish that an hour-long recording will be reliable. On the editing device, import the copy into a disposable Resolve project. Confirm picture and sound, the reported frame rate and color interpretation, then play a short export outside Resolve. If a proxy arrives first, verify that the camera original has also arrived and is correctly linked before judging final image quality or deleting phone media. ## When You Need to Edit on the Phone Need to finish the video on the phone? For straightforward cuts, titles and music on iPhone, [Apple’s free iMovie](https://apps.apple.com/us/app/imovie/id377298193?ref=davinciresolveclub.com) is a genuine mobile editor. On Android, [KineMaster](https://www.kinemaster.com/?ref=davinciresolveclub.com) is one option with a timeline and layered editing. These are alternatives for editing phone footage, not Resolve downloads. Before committing, check the current store listing for device support, paid features and watermark rules, then export a short sample. If you specifically want Resolve on a portable device, check the [iPad app’s requirements and feature limits](https://davinciresolveclub.com/davinci-resolve-for-ipad/). For the full desktop application, use a supported Mac, Windows or Linux machine. A large Android tablet still runs the Camera capture app, not the Resolve editor. ## If the Store Says the App Is Incompatible | Symptom | What to check | | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | No DaVinci Resolve result on a phone | That is expected; the official editor is not offered for Android phones or iPhone. | | Blackmagic Camera cannot be installed | Check the OS version and exact device against the live store compatibility panel. | | A website offers a Resolve APK | Do not sideload it; no official Resolve Android package exists. | | The app records but Resolve rejects the clip | Identify the video and audio codec, copy one short original locally and test it before transcoding. | | Cloud media does not reach the editor | Check the Blackmagic ID, project selection, storage plan, upload status and network. | | A long recording stops or disappears | Preserve logs and remaining files, then test storage, heat, power and the current app update before recording again. | Do not delete the only local copy while troubleshooting a transfer. Confirm the receiving file's size and play it outside the camera app before clearing phone storage. ## Frequently Asked Questions ### Can I download DaVinci Resolve on Android? No official DaVinci Resolve editor is available for Android phones or tablets as of September 8, 2026\. Blackmagic Camera is available for compatible Android devices, but it captures and uploads footage rather than providing the Resolve editing application. ### Is there an official DaVinci Resolve APK? No. Blackmagic does not publish a Resolve APK or a Resolve editor listing on Google Play. Avoid downloads that borrow the name, ask you to enable unknown sources or use a developer other than Blackmagic Design Inc. ### Can I install DaVinci Resolve on an iPhone? No official Resolve editor is offered for iPhone. Apple's Blackmagic portfolio includes Blackmagic Camera and Remote Monitor for iPhone, while the editing app is explicitly DaVinci Resolve for iPad. ### Is Blackmagic Camera the same as DaVinci Resolve? No. Blackmagic Camera records and manages footage. DaVinci Resolve is the editing and post-production application for supported computers; the dedicated iPad app has its own feature limits. Installing Camera on a phone does not add Resolve’s editing pages. ### Can Blackmagic Camera send footage to DaVinci Resolve? Yes. You can transfer files locally, upload selected clips or use supported Blackmagic Cloud workflows. Protect the camera originals and verify picture, audio, frame rate and color in Resolve before deleting phone media. ### Why does Google Play say Blackmagic Camera is incompatible? Android camera access and recording features depend on the phone, OS and hardware. Trust the current Google Play compatibility result for the exact device. Sideloading the package does not guarantee that unsupported camera, codec or storage functions will work. ### What is the closest official way to edit Resolve projects on mobile? Use DaVinci Resolve for iPad on a compatible iPad. For the full desktop application, use macOS, Windows or Linux. An Android phone or iPhone can capture, upload or monitor parts of the workflow, but it does not run the Resolve editor. ### DaVinci Resolve for iPad: Download & Setup URL: https://davinciresolveclub.com/davinci-resolve-for-ipad/ Last updated: 2026-09-08T08:42:55.000Z **Quick answer:** install [DaVinci Resolve for iPad from Apple’s App Store](https://apps.apple.com/us/app/davinci-resolve-for-ipad/id1581363826?ref=davinciresolveclub.com). The US listing checked on September 8, 2026 offers **21.0.4 as a free download**. Apple requires iPadOS 18.0 or later and an A12 Bionic chip or newer. Blackmagic separately recommends an **iPad Pro with M1 or newer and at least 8GB of RAM**. Being allowed to install the app is not a promise that your footage will edit smoothly. Before buying an iPad or moving a desktop project, test three things that the store badge cannot answer: whether your source files play with audio, whether the device has enough working storage, and whether the project opens on the desktop Resolve version you plan to use. A tablet can be compatible with the app and still be the wrong machine for a heavy camera format or a long-form timeline. This page covers the dedicated iPad app. For Windows, macOS, Linux, Studio and older builds, start at the [Download & Install hub](https://davinciresolveclub.com/davinci-resolve-download/). An iPhone or Android phone is a different availability question; the iPad listing is not an installer for those devices. ## Use the Real App Store Listing The legitimate app is named **DaVinci Resolve for iPad** and the developer is **Blackmagic Design Inc**. It is not an APK, a configuration profile, a remote-control wrapper or a “mobile Resolve” download from a file site. If the developer name does not match, stop. ![Official DaVinci Resolve for iPad Cut page shown in the Apple App Store listing](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/ipad-cut-page-app-store.webp) Official [App Store Cut-page example](https://apps.apple.com/us/app/davinci-resolve-for-ipad/id1581363826?ref=davinciresolveclub.com): source clips on the left, a viewer on the right and the editing timeline below. This is interface orientation, not a verified 21.0.4 device test. 1. Open the App Store on the iPad. 2. Search for **DaVinci Resolve for iPad**. 3. Confirm the developer is Blackmagic Design Inc. 4. Read the current Compatibility section before tapping Get. 5. Install the free app first; make a Studio decision after the real workflow test. The September 8 listing reports an app size of about **3.8GB**. That is Apple’s listed app size, not the storage budget for an editing project. Source clips, working files, backups and finished exports need additional space. Check the free space on the device rather than assuming that 3.8GB spare is enough. ## Compatible Does Not Mean Comfortable Apple's current installation floor is iPadOS 18.0 and an A12 Bionic chip or later. Blackmagic's own description recommends an iPad Pro with M1 or newer and at least 8GB of RAM. It also warns that earlier models may be limited to HD and that memory limits can disable or restrict features. | Question | What the current listing says | How to use it | | ----------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------ | | Can the app install? | iPadOS 18.0+ and A12 Bionic+ | Hard compatibility gate from Apple | | What does Blackmagic recommend? | iPad Pro with M1 or newer and at least 8GB RAM | Better floor for buying specifically for Resolve | | Will an older iPad behave like a desktop? | Earlier models may be HD-limited or lose features under memory pressure | Test before committing a project | | Is the listed app size enough free space? | No; it describes the app, not working media | Budget for sources, cache and exports | If you already own the iPad, install Free and run the acceptance test below. If you are shopping for hardware, buy for the heaviest footage and timeline you expect, not the lightest demo that launches. Our [Resolve system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) explains the difference between a minimum and a comfortable editing target, although its desktop GPU advice does not map directly to iPad silicon. ## Plan Storage Before You Import Media Keep enough room for the originals you store locally, any working files the project creates, and the finished export. A drive with space for the source clips alone may still fill during the job. Before importing a large folder, decide where those files and the backup will live. - Keep the original media on a known volume with a backup. - Use a fast external SSD when the project size makes internal storage impractical. - In Files, open Browse and look under Locations for the external drive; then confirm Resolve can access its media. - Leave room for cache and the final export at the same time. - Disconnect the drive only after imports, playback and exports using it have finished. Apple’s [external-storage requirements for iPad](https://support.apple.com/guide/ipad/external-storage-devices-ipad75b7b23f/ipados?ref=davinciresolveclub.com) specify a single data partition and a supported format, such as APFS, exFAT or FAT32\. Some drives need external power. If a drive does not appear in Files, check its format, cable, adapter and power before blaming Resolve. **Do not erase or reformat the only copy of your media.** A drive appearing in Files is only the first check; test playback and export with that same connection. An external SSD can make a small internal drive more workable, but keep the media folders identifiable and backed up. Moving originals between folders after import can leave clips offline. Confirm the project still opens with its media before you leave for a shoot or hand it to another editor. ## Import a Real Clip and Learn the iPad Interface Blackmagic advertises H.264, H.265, Apple ProRes and Blackmagic RAW support in the current listing. That is not a promise that every profile, bit depth, frame rate, audio track and storage path behaves identically on every iPad. Import one file from the actual camera or phone you use. 1. Create a disposable project. 2. Import a representative clip from internal or external storage. 3. Confirm picture and audio both appear. 4. Scrub, trim and play the clip at the timeline frame rate you expect to use. 5. Add one title or transition and one basic color correction. 6. Export a short section and play it outside Resolve. The current listing says the app supports Apple Pencil and Magic Keyboard. Both can improve control, but neither fixes a codec, memory or storage bottleneck. Buy accessories for the workflow you have already tested. ## Color Tools Are Real, but Feature Parity Is Not Automatic Start with one clip on the Color page. The viewer, color wheels, scopes and node graph let you inspect the correction without judging the whole timeline at once. In the first Color example below, the selected clip is highlighted in the filmstrip and its node graph appears at the upper right. Check the clip selection before changing a grade. ![DaVinci Resolve for iPad Color page with selected clip, node graph, color wheels and RGB parade scopes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/ipad-media-and-timeline.webp) Official [iPad Color-page example](https://apps.apple.com/us/app/davinci-resolve-for-ipad/id1581363826?ref=davinciresolveclub.com). Check the highlighted clip first, then its node graph, wheels and scopes. The filmstrip here is not the Cut-page editing timeline. Older tutorials describe only Cut and Color, but that is no longer a complete account of the app. The [iPad release history](https://apps.apple.com/us/app/davinci-resolve-for-ipad/id1581363826?ref=davinciresolveclub.com) records Deliver-page support in 20.1 and the Photo page in 21\. Use the supported pages in your installed release; a keyboard trick that exposes another page is not evidence of full desktop feature support. The official store images here illustrate the controls, not every page in the current version. Blackmagic’s [Resolve 20 Studio and iPad feature matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5FStudio%5F20%5FFeatures.pdf?ref=davinciresolveclub.com) is a historical reference, not a verified feature list for 21.0.4\. Use the current iPad release notes and inspect the feature you need on your model before buying Studio for it. Do not infer that a desktop effect is available just because a shared project contains it. ## Free or Studio on iPad Install Free first. The US App Store listing shows a **$94.99 DaVinci Resolve Studio in-app purchase** as of September 8, 2026\. Prices can vary by country and change over time; check the amount on the Apple Account that will buy the upgrade. The iPad upgrade is a separate Apple in-app purchase, not a desktop Studio activation-key entry. Blackmagic’s [licensing explanation](https://forum.blackmagicdesign.com/viewtopic.php?p=1042078&t=200521&ref=davinciresolveclub.com) distinguishes it from desktop licences. Owning Studio for Windows, Linux or a direct Mac installation does not by itself unlock the iPad upgrade. Already paid on this Apple Account? Look for the app’s restore-purchases option before paying again. Apple’s [purchase-restoration guidance](https://support.apple.com/en-gb/108096?ref=davinciresolveclub.com) says to use the same account and allow in-app purchases. If restoration still fails, restart the device and contact the developer or Apple with the purchase record. Our [Free versus Studio guide](https://davinciresolveclub.com/davinci-resolve-vs-studio/) covers the broader feature decision, while the [Resolve cost guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) separates the purchase channels. For this iPad, buy only when the feature you need is both Studio-only and supported on the device—not simply because the desktop edition offers it. ## Move Projects Between iPad and Desktop Safely Record the versions on both devices before moving work. On September 8, the iPad listing still offers 21.0.4 while desktop 21.1 is available; you cannot assume both platforms update together. The store description also still names Resolve 20 for desktop project exchange. That wording does not establish a guaranteed round trip between every newer build. Test a duplicate before either application changes your only working project. A `.drp` is a project export, not a backup of all source footage. A `.dra` is a project archive; verify what media it includes before relying on it. Keep the originals separately backed up. The [safe-update guide](https://davinciresolveclub.com/update-davinci-resolve-safely/) explains why reinstalling an older app is not the same as recovering a compatible project. 1. Record the Resolve version on both devices. 2. Export a separate project or project archive backup. 3. Move a duplicate project first. 4. Verify that all media paths relink on the destination. 5. Check titles, effects, fonts, audio routing and color before continuing work. 6. Do not overwrite the only known-good copy until the round trip has succeeded. A Blackmagic Cloud project library can reduce manual project-file transfers, but still verify the media on the destination. If you use media syncing, check what has actually finished syncing; if you move files on a drive, check those paths instead. Opening the project is not proof that every source clip, font or effect is available. In the Color example below, inspect the named nodes as well as the image when checking a handoff. ![DaVinci Resolve for iPad Color page with named Balance, Curves, Vignette, Sharpen and LUT nodes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/ipad-color-page-app-store.webp) Official [iPad Color-page example](https://apps.apple.com/us/app/davinci-resolve-for-ipad/id1581363826?ref=davinciresolveclub.com) with named nodes. When transferring a project, check the grade and each needed effect on the destination; a node label alone does not prove feature compatibility. ## If the App Will Not Install or a Project Will Not Open | Symptom | First check | | --------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | The App Store says the iPad is incompatible | Check iPadOS version and exact iPad model; do not sideload an imitation app. | | The download stalls | Check free internal storage, network stability and App Store account status. | | The clip has no picture or no audio | Identify the video and audio codecs, then test a short native file copied to internal storage. | | An external drive appears in Files but media goes offline | Confirm the same volume and folder remain mounted and accessible to Resolve. | | A desktop project warns about its version | Stop and preserve the original. Record both versions and test a duplicate; do not let either device upgrade the only copy. | | The interface or effect differs from desktop | Check current iPad release notes and the exact feature on your model; the Resolve 20 matrix is historical. | Do not erase the project, uninstall the app or delete cache as a first response. Preserve the error, note the app and iPadOS versions, and test with a disposable project. That keeps a storage issue from becoming a data-loss issue. ## Frequently Asked Questions ### Is DaVinci Resolve free on iPad? Yes. Blackmagic Design publishes DaVinci Resolve for iPad as a free App Store download. Optional Studio features are sold through a separate in-app purchase. Start with Free and test the actual media, timeline and export workflow before deciding to upgrade. ### Which iPads can install DaVinci Resolve? The Apple listing checked on September 8, 2026 requires iPadOS 18.0 or later and an A12 Bionic chip or newer. Blackmagic separately recommends an iPad Pro with M1 or newer and at least 8GB of RAM. An older eligible iPad may still face HD, memory or feature limits. ### How much storage does DaVinci Resolve need on iPad? The US App Store lists about 3.8GB for the app as of September 8, 2026\. Source media, working files, backups and exports need additional space. Check the footprint of your actual project; the listed app size is not a free-space recommendation. ### Does DaVinci Resolve for iPad work with an external SSD? Yes, with compatible storage and media. Apple requires a single data partition and a supported file system, and some drives need external power. Check the drive in Files, then test the exact cable, power connection and clips in Resolve. Back up the media before changing the drive’s format. ### Can iPad Resolve projects open on desktop? Project exchange is supported, but verify the two app versions and test a duplicate with its media before moving real work. On September 8, 2026, the iPad listing offers 21.0.4 while desktop 21.1 is available; the store description still names Resolve 20 interchange. None of that proves every newer-version round trip is safe. ### Does a desktop Studio license unlock Studio on iPad? No. Studio on iPad is a separate Apple in-app purchase, not a desktop activation-key unlock. If you previously bought the iPad upgrade, use the same Apple Account and try restoring that purchase before buying again. ### Is DaVinci Resolve available on iPhone? This App Store listing is for the iPad editor, not an iPhone version. Other Blackmagic mobile apps have different jobs and are not substitutes for the Resolve editing app. Avoid third-party downloads that imitate the name. ### DaVinci Resolve for Linux: Download & Install URL: https://davinciresolveclub.com/davinci-resolve-for-linux/ Last updated: 2026-09-08T07:59:02.000Z **Quick answer:** DaVinci Resolve has an official native Linux build. Download the Free or Studio Linux ZIP from [Blackmagic Design](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com), extract it and follow the included installer instructions. Before installing, check the distro and GPU: the Resolve 21.1 readmes checked on September 8, 2026 name **Rocky Linux 8.6, 32GB of RAM and a discrete GPU with at least 4GB of VRAM**. Ubuntu and other distributions need a separately maintained compatibility route; they are not the baseline named in those readmes. Do not move a working project to Linux just because the installer opens. First check the camera codec, audio codec, GPU driver and delivery format you use. A system that reaches the Project Manager can still fail to import a phone clip, play its audio or render the format your client needs. Keep the working setup until a small test project completes those jobs. Need a different platform or edition? Start with the [Download & Install hub](https://davinciresolveclub.com/davinci-resolve-download/). For a whole-workstation comparison, see the [Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). This page covers the Linux package, installation choices and the checks to make before moving your work. ## Download the Linux Package From Blackmagic Start with Blackmagic’s own Linux ZIP, not a mirror or an unexplained prebuilt `.deb`. Community packaging can help with a distro mismatch, but it should use the official source package. Keep that original archive so you can identify exactly what was installed. ![Official Blackmagic Design download picker with the DaVinci Resolve Linux option](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-linux-download-picker.webp) Choose Linux inside Blackmagic Design's own download picker. Select Free or Studio first; the Studio installer still needs a valid license. 1. Open the official [DaVinci Resolve product page](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com). 2. Choose the Free edition if you want the no-cost application. If you have a Studio activation key, dongle or assigned Cloud rental, choose the separate Studio Linux download; our [Studio installer and licence guide](https://davinciresolveclub.com/davinci-resolve-studio-download/) explains the licence routes. 3. Select the **Linux** package. 4. Complete Blackmagic's registration form if it appears. 5. Save the ZIP to a local drive with room for both the archive and its extracted contents. **Checked September 8, 2026:** Blackmagic’s catalogue lists Free and Studio 21.1 Linux packages, and both release readmes are dated September 8\. Check the live release card again before downloading. A newer package can change requirements; an old tutorial’s version number is not a reason to download an old installer. ## Decide Whether You Want a Supported or Compatibility Install Rocky Linux 8.6 is the operating system named in both 21.1 readmes. That is a vendor baseline, not proof that every other distro fails or that you should downgrade an existing workstation to match a number. If you need Ubuntu, Debian, Fedora or Arch, budget time to check the specific distro release, GPU driver and installer method together. | Path | What it means | Who should choose it | | -------------------------------------------- | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | Rocky Linux 8.6 | Matches the operating system named in the current Blackmagic readme | A facility or editor who values a reproducible, supportable workstation | | Ubuntu or Pop!\_OS | Popular compatibility path, often using extra libraries or third-party repackaging | An experienced Linux user willing to own updates and rollback | | Debian, Fedora, Arch or derivatives | Community-maintained route whose working steps can change with the distro | A user comfortable reading scripts, logs and package dependencies | | Wine, Proton or a container as the main plan | Adds another unsupported layer around a GPU-heavy native application | Experimentation, not a deadline-critical workstation | System76’s [Pop!\_OS and Ubuntu installation guide](https://support.system76.com/support/install-davinci-resolve/?ref=davinciresolveclub.com) describes an **NVIDIA-specific** route using MakeResolveDeb. Do not apply its driver advice to an AMD machine. It is a compatibility installation, not an expansion of Blackmagic’s Rocky Linux support baseline. ## Run the Resolve 21 Linux Preflight The [Free 21.1 readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) lists these Linux minimums. They are not a guarantee of smooth 4K noise reduction, large Fusion compositions or multicam playback: - **Rocky Linux 8.6** - **32GB of system memory** - A **discrete GPU with at least 4GB of VRAM** - A GPU supporting **OpenCL 1.2 or CUDA 12.8** - Official AMD drivers from the GPU manufacturer, or **NVIDIA Studio driver 580.119.02 or newer** - Blackmagic Desktop Video 12.9 or later when using supported Blackmagic monitoring hardware The [Studio 21.1 requirements](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) add workload-specific figures: **at least 16GB of VRAM for advanced AI tools**, and **32GB of RAM plus 12GB of VRAM for background rendering**. Do not buy a 4GB card expecting that baseline to cover every Studio feature. Check the driver version and the GPU’s compute support before troubleshooting Resolve itself. A working desktop does not prove that the required OpenCL or CUDA path is available to the application. Follow the GPU vendor and distro instructions for that exact machine; avoid installing a driver version copied from an unrelated tutorial. Our [Resolve PC checker](https://davinciresolveclub.com/davinci-resolve-pc-checker/) can help organize the CPU, memory, GPU and storage questions, but it cannot inspect your Linux machine or validate a driver. Treat it as a pre-purchase checklist, not a hardware scanner. ## Check Your Media Before You Change Operating Systems A filename does not tell you which codecs are inside. MP4 and MOV containers can hold different video and audio formats. Blackmagic’s [Resolve 20 codec matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com) lists H.264/H.265 decoding as Studio-only in its Rocky Linux table, with NVIDIA acceleration; encoding requires Studio and NVIDIA graphics. Its audio table has no AAC decode or encode support. **That is a Resolve 20 document, not a verified 21.1 matrix.** Use it as a warning to check your files, not a promise about the new version. Consult Blackmagic’s current support documents and test the exact media before migrating. Open a representative clip in [MediaInfo](https://mediaarea.net/en/MediaInfo/Screenshots?ref=davinciresolveclub.com) and inspect the General, Video and Audio sections separately. Note the container, video codec, profile, bit depth, chroma subsampling and audio codec. The example below uses MXF, MPEG Video and PCM; your footage may be different. Those values describe a file, not whether Resolve on your machine can decode it. ![MediaInfo fields identifying container, video codec, bit depth, chroma subsampling and audio codec before Linux migration](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/linux-media-codec-preflight-annotated-v2.webp) Annotated [official MediaInfo Windows example](https://mediaarea.net/en/MediaInfo/Screenshots?ref=davinciresolveclub.com). MXF, MPEG Video, 8-bit 4:2:2 and PCM are this sample’s values, not recommended settings or a Resolve compatibility result. Before installing, collect three small files: 1. A representative camera or phone clip with its original audio. 2. A clip from the heaviest production format you expect to grade. 3. A short delivery reference matching the format your client or platform requires. Those files are more useful than a synthetic sample. If your normal work is 10-bit HEVC with AAC audio, a friendly DNxHR clip proving that the Media Pool works tells you almost nothing about the actual migration. ## Extract and Run the Official Linux Installer The official Linux ZIP contains the installer and accompanying instructions. Extract the complete archive into its own folder first, rather than trying to launch a file inside the archive viewer. Read the instructions included with your downloaded release before making system changes. 1. Extract the whole downloaded ZIP into a new folder. 2. Open the included Linux installation instructions and read the notes shipped with that exact release. 3. If needed, enable executable permission for the exact `.run` installer. In GNOME Files, [file permissions](https://help.gnome.org/gnome-help/nautilus-file-properties-permissions.html?ref=davinciresolveclub.com) are under Properties → Permissions; the control is called Executable as Program. Other desktops may use a different label. 4. Launch the installer as directed by its included instructions and respond to its authentication prompt. Do not make your entire Downloads folder executable or change project-folder permissions. 5. Do not copy commands from an old tutorial until you have confirmed that its distro and Resolve release match yours. 6. Reboot when the GPU driver or workstation policy requires it, then launch Resolve normally. For a Debian-based setup, review the current [MakeResolveDeb maintainer instructions](https://www.danieltufvesson.com/makeresolvedeb?ref=davinciresolveclub.com). It repackages your official installer; it is not a Blackmagic product. The maintainer documents **two generated packages for Resolve 21, both required**. Use the filenames actually generated on your machine, not versioned examples pasted from another release. We have not verified a 21.1 installation with this tool, so keep a rollback path and test before production use. ## Free or Studio on Linux The Free Linux build is a separate no-cost application. The 21.1 Free readme limits mastering and output to Ultra HD or below and supports one processing GPU on Windows and Linux. Studio adds licensed capabilities, but downloading its package does not supply a licence. An assigned Cloud rental is one supported Studio activation route; an ordinary Cloud account on its own is not. For the purchase decision, use our [Free versus Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) and [current cost guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/). For Linux specifically, make the codec matrix part of that decision. A Studio license may remove an important H.264/H.265 limitation, but it does not mean every audio codec, container and GPU combination becomes interchangeable with Windows. ## Run a First-Project Acceptance Test Do this before copying a project library or calling the migration finished. You are testing the whole path. Seeing the Project Manager is only one checkpoint. ![DaVinci Resolve Edit page with Media Pool, video timeline, audio tracks and mixer](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/linux-first-project-test-v1.webp) Official [Blackmagic Edit-page interface example](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com), not a Linux test result. Use your own short project to check import, picture, audio and export. 1. Confirm Resolve reaches the Project Manager without an unsupported GPU message. 2. Create a disposable test project rather than opening the only copy of active work. 3. Import each representative file and check picture plus audio. 4. Play and scrub the clip, add one basic color correction and confirm that GPU processing stays stable. 5. Render a short section to the delivery format you actually use. 6. Play the exported file outside Resolve and verify audio, color and duration. Before an update, back up the project library and export critical projects separately. Preserve the source media too; a plain project export is not a footage backup. Both 21.1 readmes warn that projects created or opened in 21.1 cannot be opened in 20.3.2 even though the library can remain accessible. Our [safe update workflow](https://davinciresolveclub.com/update-davinci-resolve-safely/) explains why reinstalling an older application is not the same as restoring a compatible project. ## Fix Linux Install and Launch Problems by Symptom | Symptom | First useful check | | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | The .run file does nothing | Confirm the full ZIP was extracted and the installer has executable permission. | | The installer reports missing packages | Check whether the instructions target your distro; do not assume a Rocky package name maps directly to Ubuntu or Arch. | | Resolve shows “Unsupported GPU Processing Mode” | Verify the discrete GPU, vendor driver, OpenCL/CUDA support and current driver floor outside Resolve first. | | An MP4 is invisible or imports without usable audio | Identify the video and audio codecs, then compare them with Blackmagic's Linux codec table and your Free/Studio edition. | | The app opens only from a terminal | Read the terminal error before changing libraries; it often names the missing dependency or driver component. | | An update breaks a working compatibility install | Restore the recorded package/driver state and follow the current maintainer instructions for that distro rather than repeating old commands. | Change one reversible layer at a time. A mass library replacement can turn one missing dependency into a damaged desktop. Preserve the downloaded installer, the exact Resolve version, the GPU driver version and any community script revision used. Those four details make a failure reproducible. ## How to Uninstall DaVinci Resolve on Linux For a native Blackmagic installation, the 21.1 readme says to run the installer and select its uninstall option. For a MakeResolveDeb installation, use the package-manager removal route described by its maintainer instead. Do not mix the two removal methods or replace them with commands that delete directories. Uninstalling the application should not be treated as permission to delete project libraries, source media, cache or gallery stills. Back up the project library first, identify each storage location, remove the application through the same installation path and only clean cache after you have confirmed that the source media is safe. ## Frequently Asked Questions ### Is DaVinci Resolve available for Linux? Yes. Blackmagic provides official native Linux installers for Free and Studio. The 21.1 readmes checked on September 8, 2026 name Rocky Linux 8.6 as the operating-system baseline. ### Does DaVinci Resolve work on Ubuntu? Ubuntu installations are possible through community compatibility methods, but Ubuntu is not the baseline named in Blackmagic’s 21.1 readmes. Check the exact distro release and GPU route. System76’s documented Pop!\_OS/Ubuntu method is NVIDIA-specific, not a general AMD installation recipe. ### How much RAM does DaVinci Resolve need on Linux? Both Resolve 21.1 readmes list 32GB of system memory for Linux. Studio additionally lists 16GB of VRAM for advanced AI tools and 32GB of RAM with 12GB of VRAM for background rendering. These are requirements, not measured performance promises. ### Why does DaVinci Resolve say unsupported GPU processing mode on Linux? Treat it as a GPU-compute configuration problem to investigate, not proof of one specific fault. Check the discrete GPU, driver version and required OpenCL or CUDA support, then read the actual error and logs before changing libraries or application preferences. ### Does DaVinci Resolve Free on Linux support H.264 and H.265? Do not assume the Windows or macOS rules apply. Blackmagic’s Resolve 20 Rocky Linux matrix lists H.264/H.265 decoding as Studio-only with NVIDIA acceleration, and encoding as Studio plus NVIDIA. It also lists no AAC decode or encode support. That document does not verify 21.1 behavior: check the current vendor documentation and test your exact video and audio before moving work. ### Should I use MakeResolveDeb to install Resolve? It is an option for a deliberately chosen Debian-based compatibility installation, not an official Blackmagic installer. Review the maintainer instructions, keep the original ZIP and record the tool version. The documented Resolve 21 conversion produces two packages and requires both; this article does not certify a tested 21.1 setup. ### Where should I download DaVinci Resolve for Linux? Download it from Blackmagic Design's official DaVinci Resolve product or support page. Avoid mirrors, repackaged installers and search ads that imitate the product name. This site links to the vendor package and does not host the installer. ### DaVinci Resolve Studio Download: Official Guide URL: https://davinciresolveclub.com/davinci-resolve-studio-download/ Last updated: 2026-09-08T06:18:10.000Z **Quick answer:** download DaVinci Resolve Studio from [Blackmagic Design's official Resolve and Fusion support page](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com). In Latest Downloads, choose the card titled **DaVinci Resolve Studio**, not the separate Free card, then select Mac OS, Linux, Windows x86 or Windows ARM as offered. The installer is available to download, but Studio is not free to use. The current Studio 21.0.4 card requires a licence dongle, Blackmagic Cloud licence or software activation code. If you already own a valid key or dongle, use the support-page download; you do not need to buy the same licence again just to get the installer. Otherwise, start with Resolve Free or buy Studio through an official channel. **Checked September 8, 2026:** Blackmagic’s catalogue lists DaVinci Resolve Studio 21.0.4, released August 5, 2026\. Check the live release card before downloading; the version, available platforms and requirements can change. ## Download the Correct Studio Package On the support page, Free and Studio appear as separate software updates. The Free card says DaVinci Resolve. The paid card includes the word **Studio** in both the heading and downloaded package name. If you are still deciding between editions or operating systems, use the [Resolve download hub](https://davinciresolveclub.com/davinci-resolve-download/) first. This page is for the point where Studio is already the intended edition. ![Official Blackmagic Support Center card for DaVinci Resolve Studio 21.0.4 download](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-studio-download-card.webp) The current Studio 21.0.4 archive card identifies the edition, date, licence requirement and available platform buttons. This real page capture was checked on September 2, 2026. 1. Open the official Blackmagic Resolve and Fusion support family page. 2. Wait for the Latest Downloads column to load. 3. Find **DaVinci Resolve Studio 21.0.4 Update** or the newer current Studio card if Blackmagic has released one. 4. Read the release note and confirm that the heading includes Studio. 5. Select the platform that matches the computer. 6. Complete the requested download details or use the download-only route if the current dialog offers it. 7. Save the official package and let it finish before opening or extracting it. This site does not host the installer. Avoid torrents, “pre-activated” copies, key generators and repacks. A modified Studio package can compromise the workstation and does not create a legitimate licence. ## Choose Mac, Linux, Windows x86 or Windows ARM | Platform button | Choose it for | | --------------- | ----------------------------------------------------------------------------------------------------------------------------- | | Mac OS | A Mac that meets the current Studio release requirements. Resolve 21.0.4 currently names macOS 15 or later and Apple silicon. | | Windows x86 | A normal Intel or AMD 64-bit Windows PC. Blackmagic uses x86 as the family label for this current 64-bit package. | | Windows ARM | A supported Windows-on-ARM computer. The current 21.0.4 baseline names Windows 11 for ARM and Snapdragon X Elite series. | | Linux | A Linux workstation that matches Blackmagic's current distribution, memory and GPU requirements. | Architecture and licence are separate. A Studio activation code does not make the Windows x86 installer suitable for ARM, and a dongle does not make an unsupported Mac compatible. Check the [current Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) before downloading a large package for an old or unusual system. For a normal Intel or AMD PC, the [Windows installation guide](https://davinciresolveclub.com/davinci-resolve-for-windows/) covers the platform steps. Apple users can follow the [Mac download guide](https://davinciresolveclub.com/davinci-resolve-for-mac/). If Windows reports an ARM-based processor, check the [Windows x86 versus ARM guide](https://davinciresolveclub.com/davinci-resolve-windows-x86-vs-arm/) before choosing a package. ## The Download Does Not Create a Studio Licence For the installer downloaded from Blackmagic, the three licence routes are: - **Software activation code:** choose Use License Key and enter your Studio key when prompted. Registration on the download page is not this activation step. - **USB licence dongle:** connect the legitimate Studio dongle before launch and keep it connected while using Studio. - **Blackmagic Cloud rental:** choose Use Blackmagic Cloud ID and sign in to the profile with an assigned Studio licence. Merely having a Cloud account is not enough. ![Official DaVinci Resolve Studio 21 activation screen with License Key and Blackmagic Cloud ID choices](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/resolve-studio-license-choice.webp) The current Blackmagic Cloud guide shows the real Studio 21 activation screen. Use License Key and Use Blackmagic Cloud ID are explicit choices; a USB dongle is detected as its own licence path. Blackmagic’s [Studio Cloud sign-in guide](https://help.cloud.blackmagicdesign.com/license-manager/logging-in-to-davinci-resolve/?ref=davinciresolveclub.com) documents the screen above. Choose **Use Blackmagic Cloud ID**, click **Continue** and sign in. Then select **Personal** for your personal rental or the organization that assigned your licence. Click **Log In** and confirm the activation. These are alternative profiles: select the one that owns the licence, not every profile in the list. ![Studio Cloud profile selector with Personal rental, organization licence and Log In marked](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/resolve-studio-cloud-profile-v2.webp) Annotated illustration based on Blackmagic’s Studio 21 profile selector. Personal and organization are alternative choices; the names are examples from the official guide, not an account activated for this article. A Cloud rental activates **one computer at a time**. To move it, use **License Details** in the Cloud License Manager to deactivate the old computer, then sign in on the new one. Blackmagic’s [rental-licence management instructions](https://help.cloud.blackmagicdesign.com/license-manager/managing-licenses/?ref=davinciresolveclub.com) distinguish this from unassigning the licence from a person. You do not need to unassign it from yourself just to change computers. Keep activation codes private. Do not put them in public screenshots, send them to strangers or enter them into unofficial activators. ### Bought Studio in the Mac App Store? If you bought [Studio in the Mac App Store](https://apps.apple.com/us/app/davinci-resolve-studio/id900392332?mt=12&ref=davinciresolveclub.com), download that Store edition with the Apple account used for the purchase. It does not supply a key for Blackmagic’s direct installer; a direct key, dongle or Cloud rental does not activate the Store edition either. Blackmagic’s [explanation of the separate licence channels](https://forum.blackmagicdesign.com/viewtopic.php?p=1042078&t=200521&ref=davinciresolveclub.com) covers this distinction. Do not buy again before checking which edition you already own. ## Is DaVinci Resolve Studio Free or a Trial? DaVinci Resolve Free is a separate edition. Studio is paid. On September 8, 2026, [Blackmagic’s US Studio page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) listed Studio 21 at **$295**. That is the direct purchase price, not a Cloud rental or Mac App Store quote. Regional price, tax and bundles can differ; check the [Resolve price and licence guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) before buying. The official product and support pages checked on September 8 did not offer a time-limited Studio trial. They offered Resolve Free and paid Studio. Free is useful for learning and an initial compatibility check, but it cannot validate a Studio-only effect or codec before purchase. Downloading Studio alone does not unlock those features. Use our [Free versus Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) when the unresolved question is features. Buy Studio for a specific capability or workflow, not because an unofficial page calls it “full version.” ## Back Up Before Moving From Free or Updating Studio Free and Studio use the same Resolve project ecosystem, but changing the application version can still change a project. Protect the rollback path before installing: 1. Back up the project library using the controls for its local, network or Cloud library type. 2. Export active or irreplaceable projects separately as .drp snapshots. Preserve the source media and required dependencies too; a plain project export is not a footage backup. 3. Record the current Resolve edition and complete build number. 4. Record critical OpenFX, VST, GPU driver, panel and media dependencies. 5. Keep the backup away from the cache and working-media drive. 6. Close Resolve before running the Studio installer. The [Studio 21.0.4 readme](https://www.blackmagicdesign.com/support/content/readme/5e8ed1f827564634984496004809d558?ref=davinciresolveclub.com) gives a precise compatibility warning: its project libraries can remain accessible to 20.3.2, but individual projects created or opened in 21.0.4 cannot be opened in 20.3.2\. Reinstalling an old Studio application is not a complete downgrade plan. Keep a compatible pre-update backup. Use the [safe Resolve update workflow](https://davinciresolveclub.com/update-davinci-resolve-safely/) before moving a production library to a newer Studio build. ## Install Studio on the Computer After the official package has finished downloading: 1. Confirm that the filename and package are Studio, not Free. 2. Extract the archive if the platform download is compressed. 3. Run the included installer and read each component choice. 4. If the platform installer asks to replace or remove the Free application, continue only after the project backups are complete. 5. Use the component information in the Studio readme. Desktop Video is for Blackmagic monitoring hardware; do not treat it as a requirement for an ordinary computer display. 6. Restart only if the installer or operating system asks. 7. Launch DaVinci Resolve Studio and choose the correct licence path. If you need to remove an existing direct installation, follow Blackmagic’s platform instructions: use **Uninstall Resolve** on Mac, **Programs and Features** on Windows, or the installer’s uninstall option on Linux. Do not manually delete a project-library folder while removing the app. For an installer failure, follow the [Resolve installation-error guide](https://davinciresolveclub.com/davinci-resolve-installation-errors/) before trying a second package. ## Prove the First Studio Launch A successful activation is not the end of installation. Open a duplicate project and verify the workflow you bought Studio for: - confirm that the title or About screen identifies Studio; - check the expected project library and storage locations; - import a clip from the real camera, phone or screen recorder; - test the Studio-only effect, codec or output that justified the licence; - check audio, OpenFX, VST, LUTs, fonts and external panels; - export a short representative section and play it outside Resolve. A lightweight H.264 sample cannot validate a job built around RAW, 10-bit HEVC, noise reduction, multicam, Fusion or immersive audio. The acceptance test should resemble the production timeline. ## Update an Existing Studio Installation Use the newest current Studio card only when the project and dependencies are ready for that version. An old activation key or dongle is not a reason to download an unknown mirror. The official archive keeps previous Studio packages alongside the current one, and the [old versions and rollback guide](https://davinciresolveclub.com/davinci-resolve-old-versions/) explains how to choose one without sacrificing the working project. Before updating, note the working build, back up projects and check plugin, operating-system and GPU-driver compatibility. After updating, open a duplicate project first. If a regression appears, preserve the newer environment and restore a tested pre-update backup with the matching official old version rather than trying to force a newer project backward. ## If Studio Will Not Activate or Projects Are Missing | Symptom | First check | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Resolve asks for a key unexpectedly | Identify the licence you intend to use. Choose the key or Cloud route, or check that the dongle is connected. A Cloud login does not replace an activation key you already own. | | Activation key is rejected | Check exact characters, internet access and purchase source. Unofficial activation tools are not a recovery path. | | Dongle is not detected | Connect the legitimate dongle before launch, test a direct USB port and confirm that the Studio build is installed. | | Cloud ID has no licence | Check that a rental has been assigned and select the correct Personal or organization profile. If it is active on another computer, deactivate that computer through License Details first. | | Resolve launches but says Free | Check the downloaded package and application name. The Free and Studio installers are separate. | | Project Manager looks empty | Leave the old path untouched. Identify the original local, network or Cloud library and reconnect it through the documented workflow. | If licensing remains blocked, contact Blackmagic or the authorised seller with the purchase channel, order evidence, exact Studio version, platform and complete error text. Never include the full activation code in a public forum post. ## Frequently Asked Questions ### Where is the official DaVinci Resolve Studio download? Use Blackmagic Design's Resolve and Fusion support page. In Latest Downloads, choose the DaVinci Resolve Studio card, verify the current version and select the Mac, Linux, Windows x86 or Windows ARM button shown for that release. ### Can I download DaVinci Resolve Studio for free? You can obtain the installer from Blackmagic, but the download does not create a Studio entitlement. Studio requires a supported licence dongle, Blackmagic Cloud licence or software activation code. DaVinci Resolve Free is the separate no-cost edition. ### Does DaVinci Resolve Studio have a free trial? The official product and support pages checked on September 8, 2026 did not offer a time-limited Studio trial. Resolve Free is a separate no-cost edition, but it cannot test every Studio-only capability. Downloading the Studio installer does not activate a trial. ### Do I need an activation key for DaVinci Resolve Studio? Not always. The direct Blackmagic installer supports an activation key, a licence dongle or an assigned Cloud rental. The Mac App Store edition uses its separate Store purchase, not those direct-install licences. ### Can I install Studio after using DaVinci Resolve Free? Yes. Back up the library using the controls for its local, network or Cloud type, export critical projects separately and preserve the media. Download the separate Studio installer, close Resolve, follow the platform instructions and confirm the expected projects before production work. ### Which Studio download should an Intel or AMD Windows PC use? Choose Windows x86\. Blackmagic uses that label for the current 64-bit Intel and AMD package. Choose Windows ARM only for a supported Windows-on-ARM computer that meets the current processor and operating-system requirements. ### Can I download an older DaVinci Resolve Studio version? Yes. The official Blackmagic support archive includes previous Studio releases. Match the exact edition, platform and project backup, and remember that a project opened in a newer Resolve version may not open in the older build. ### DaVinci Resolve Old Versions: Official Downloads URL: https://davinciresolveclub.com/davinci-resolve-old-versions/ Last updated: 2026-09-07T21:41:16.000Z **Quick answer:** get old DaVinci Resolve versions from [Blackmagic Design's official Resolve and Fusion support archive](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com). Let the long page finish loading, find the exact release under Latest Downloads, then match the Free or Studio edition and the platform buttons shown on that card. For now, leave the working version installed. An old installer changes the application, not the project history. A project created or opened in a newer Resolve release may not open in an older one. Back up the full project library, export active projects separately and prove that the backup works before treating rollback as possible. **Archive checked September 7, 2026:** Blackmagic’s official catalogue lists separate Free and Studio entries for the releases below. These are available archive entries, not a promise that an old release is still maintained or compatible with your computer. ## Use the Official Blackmagic Archive The support archive is long because it mixes DaVinci Resolve Free, DaVinci Resolve Studio, Fusion Studio, Project Server, manuals and support notes. That is inconvenient, but it preserves the publisher and release context that a mirror strips away. If you have not yet decided whether you need Windows, Mac, Free or Studio, start with the [Resolve download hub](https://davinciresolveclub.com/davinci-resolve-download/). This guide begins after the current release is no longer the right fit. ![Blackmagic Design Support Center showing an official old DaVinci Resolve 19.1.4 download card](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-old-versions-archive.webp) Blackmagic's live archive shows the date, edition, release note and available platform buttons on the same card. This real page capture was checked on September 2, 2026. 1. Open Blackmagic's Resolve and Fusion support family page. 2. Wait for the Latest Downloads column to populate. 3. Scroll to the required version. Browser Find can help after the list has loaded. 4. Distinguish **DaVinci Resolve** from **DaVinci Resolve Studio**. 5. Read the card's date and release note before choosing the platform. 6. Select only a platform button that the exact card exposes. 7. Save the installer with the version and platform visible in its filename or surrounding archive record. __Older Free and Studio releases listed in the official archive on September 7, 2026__ | Release to find | Archive date | Listed platform categories | | --------------- | ----------------- | -------------------------------- | | 20.3.3 | May 13, 2026 | Mac, Windows, Linux, Windows ARM | | 19.1.4 | March 21, 2025 | Mac, Windows, Linux, Windows ARM | | 18.6.6 | March 20, 2024 | Mac, Windows, Linux | | 17.4.6 | March 29, 2022 | Mac, Windows, Linux | | 16.2.8 | November 25, 2020 | Mac, Windows, Linux | | 15.3.1 | April 5, 2019 | Mac, Windows, Linux | Search for the version number in **Latest Downloads**, then choose the edition and platform on that card. A listed installer is not a hardware recommendation. The readme supplies the operating-system and processor requirements for that release. Skip software mirrors, torrents, shared drives and “portable” repacks. A convincing filename does not preserve the publisher trail, and the package may be modified, incomplete or wrongly labelled. This site does not host old Resolve installers. ## Choose the Old Version From the Reason You Need It “Older” is not a technical requirement. The correct release is the one that matches a known constraint: | Why you need an old version | What should determine the release | | ---------------------------------------- | --------------------------------------------------------------------------------------- | | Open a pre-existing backup | Match the Resolve version that created or last safely opened that backup. | | Recover from a bad update or regression | Use the last build you personally tested with the same project, media and driver stack. | | Run Resolve on an older OS or computer | Match the archived release notes and system requirements to that exact OS, CPU and GPU. | | Keep a critical plugin or device working | Match the plugin or hardware vendor's supported Resolve, OS and driver versions. | | Join another editor or shared library | Match the agreed Resolve and Project Server workflow across the team. | | Use an existing Studio licence | Choose the Studio entry for the required release and a supported licence channel. | Start with the release that last worked with the project, plugins and hardware you need. A later patch in the same branch may fix your problem, but read its notes before choosing it. A facility or plugin vendor may require a specific point release; a tidier version number is not a reason to ignore that requirement. Older does not automatically mean faster. Test the candidate with the same footage and export settings before committing. For today’s release, use the [current Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/); for an archived build, read **that build’s own requirements**, not the current version’s minimums. ## Back Up Before You Replace Resolve A rollback plan needs two different backups: - **Full project-library backup:** protects the database or library that contains the projects. - **Individual project exports:** give critical projects a separate portable copy. A project backup is not a copy of the entire editing workstation. Keep source media and required fonts, LUTs, plugins, license tools and scripts available separately. Export options differ, so check what the chosen backup includes. Do not assume a plain project export contains the footage. 1. Identify the library type first. For a local library, use its library-backup control in Project Manager; for a shared network library, coordinate the backup with its Project Server administrator. Cloud libraries use the separate web controls described below. 2. Export each critical project as a separate .drp file. In Project Manager, right-click its thumbnail and choose Export Project. Keep that dated export as a snapshot; later edits are not automatically written into it. 3. Copy project backups away from the cache and working-media drive. 4. Record Resolve Free or Studio, the complete build number, OS version, GPU driver and Project Server version if used. 5. List required OpenFX and VST plugins, fonts, LUTs, panels and capture devices. 6. Test a copy of the backup in a separate library or test environment, using the version that created it. Do not test by replacing the only working library. Our [safe Resolve update workflow](https://davinciresolveclub.com/update-davinci-resolve-safely/) covers the same protection from the forward-update side. If you need to identify where local projects and libraries live, use the [Resolve project storage guide](https://davinciresolveclub.com/where-davinci-resolve-projects-saved/). Leave the library files themselves alone. ### If Your Library Is in Blackmagic Cloud For a **Blackmagic Cloud** library, open its Project Server page, select the library and open **Backups**. Click **Create Backup**, then confirm the completed entry and its timestamp. Blackmagic’s [Cloud backup instructions](https://help.cloud.blackmagicdesign.com/project-server/managing-project-libraries/?ref=davinciresolveclub.com) describe these web controls; they are not the local Project Manager interface. ![Blackmagic Cloud Backups tab with Create Backup and the completed backup timestamp marked](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/old-resolve-cloud-backup-v2.webp) Annotated illustration based on Blackmagic’s Cloud interface. Applies to Cloud libraries only; dates are source examples, not a backup performed for this guide. ## A Newer Project May Not Open in an Older Resolve Backward compatibility is release-specific. There is no safe shortcut such as “minor versions are fine” or “the previous major always opens it.” Read the release notes for the two exact versions. [Blackmagic's current Resolve 21.0.4 readme](https://www.blackmagicdesign.com/support/content/readme/f1b3986a11634684b538ff3d1d4b55d6?ref=davinciresolveclub.com) provides a concrete example. Blackmagic says it made an effort to keep 21.0.4 project libraries compatible with 20.3.2, but projects created or opened in 21.0.4 are no longer accessible in 20.3.2\. The same note tells users to make a full project-library backup and individual project backups before opening projects in 21.0.4. That statement is about those named releases. It should not be stretched into a promise for Resolve 18, 19, 20.3.3 or a future build. The safe assumption is narrower: once a newer Resolve changes a project, an older Resolve may reject it or lose newer features. ## Decide Whether Rollback Is Still Possible ### If You Have a Tested Pre-Update Backup 1. Confirm the old Resolve edition, version and platform that match the backup. 2. When available, preserve the current system by using a second test machine, boot volume or rollback image. 3. Install the official archived package in the controlled test environment. 4. Restore a copy of the pre-update backup, not the only original. 5. Relink representative media and check critical plugins, fonts and LUTs. 6. Play the hardest normal timeline and create a short test export. 7. Move production only after the old environment passes. For a **Cloud backup**, select its dated entry and choose **Restore**. Confirm the backup, give the restored copy a distinct name, select its server and region, then restore it. This creates a new cloud library without overwriting the current one. It does **not** convert newer projects for an older Resolve release; verify the required Resolve version before relying on it for rollback. ![Blackmagic Cloud restore dialog with backup date, restored library name, server, region and Restore marked](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/old-resolve-cloud-restore-v2.webp) Annotated Cloud restore dialog. Restore a separate library copy; this does not make its projects compatible with an older Resolve version. ### If You Do Not Have a Compatible Backup A newer Resolve that still opens the project is an asset, so keep that installation intact. Preserve the current system first. Then export what you would need to finish or reconstruct the job: project backups, rendered masters, audio stems, graphics, subtitles and supported interchange files where the receiving workflow is known. An XML, AAF or EDL is not a full Resolve project downgrade. Complex grades, Fusion work, Fairlight routing, plugins and newer features may not survive. Treat interchange as a reconstruction aid, then verify it in the destination version before removing the source environment. When the project no longer opens even in the current version, stop changing the library. Contact Blackmagic support or the forum with the exact Resolve version, OS, library type, error text and backup history. ### Preserve the Evidence Before Troubleshooting Save the current installer if you still have it, record the full Resolve build number and capture the exact error before changing the system. Preserve the library, individual exports, source media and any existing system backup. Do not delete preferences, caches, plugin folders and the library together: you would lose both the recovery options and a useful comparison. Write down each change and test after it. For a problem that began with one Resolve update, first compare the release note, GPU driver, plugin versions and one duplicate project. A rollback should answer a specific failure, not become a second uncontrolled migration. ## Match Free, Studio, Platform and Architecture Every archive choice has several dimensions: - **Edition:** Resolve Free or Resolve Studio. - **Platform:** Mac, Windows or Linux when offered on that release card. - **Architecture:** Windows x86 or Windows ARM only where the card provides that choice. - **Licence:** Studio still needs a valid supported licence path. The 18.6.6 archive entries listed above do not offer a Windows ARM package; 19.1.4 and 20.3.3 do. If the Windows labels are confusing, use the [x86 versus ARM download guide](https://davinciresolveclub.com/davinci-resolve-windows-x86-vs-arm/). A Mac button alone does not establish Intel compatibility. Check the exact archived readme, operating system and hardware before installing. If you are not sure whether the project needs Studio, compare the features in our [DaVinci Resolve Free versus Studio guide](https://davinciresolveclub.com/davinci-resolve-vs-studio/) before downloading. Installing the wrong edition adds a licence problem to the rollback. ## Test the Old Version With the Real Job A successful launch proves almost nothing. Use a duplicate project and check: - one clip from every important camera or screen-capture source; - timeline frame rate, resolution and color-management settings; - OpenFX, VST, fonts, LUTs and Fusion compositions; - audio device, video I/O, control panel and shared storage; - rendered output in the exact required codec, resolution and audio layout; - the exported file in a separate player or quality-control tool. Leave the original backup untouched. A failed test should cost only the duplicate and the test environment, not the production library. ## Frequently Asked Questions ### Where can I download old DaVinci Resolve versions? Use Blackmagic Design's official Resolve and Fusion support archive. Scroll through Latest Downloads, find the exact release, distinguish Free from Studio and select only a platform button shown on that release card. ### Can I download DaVinci Resolve 20, 19, 18 or 17 from Blackmagic? Yes. On September 7, 2026, Blackmagic’s official catalogue listed 20.3.3, 19.1.4, 18.6.6 and 17.4.6 in separate Free and Studio entries. Platform availability differs; use the exact release card and its readme rather than an old direct download link. ### Can an older Resolve version open a newer project? Not safely by default. Compatibility is version-specific, and a project created or opened in a newer release may be inaccessible in an older one. Use a tested pre-update project or library backup that matches the old version. ### How do I downgrade DaVinci Resolve without losing projects? Before replacing Resolve, back up the library using the controls appropriate to its local, network or Cloud type, and export critical projects separately. Preserve the working setup. Test a copy of a compatible pre-update backup with the matching official old release before moving production work. ### Is an older DaVinci Resolve version faster? Not universally. Performance depends on the OS, GPU driver, codec, hardware acceleration, plugins, effects and project. Test the same representative timeline and export preset rather than assuming an older version will run better. ### Can I use a third-party site for an old Resolve installer? Use Blackmagic's archive instead. A mirror removes dependable publisher provenance and may provide a modified, incomplete or wrongly labelled package. The official archive also shows the edition, date, release note and platform choices together. ### Do I need the old Free or Studio installer? Match the edition used by the project and licence workflow. Free and Studio are separate archive entries. Studio still requires a valid supported licence, and downloading a Studio package does not create an entitlement. ### DaVinci Resolve Windows x86 vs ARM: Which Build? URL: https://davinciresolveclub.com/davinci-resolve-windows-x86-vs-arm/ Last updated: 2026-09-07T21:06:00.000Z **Quick answer:** if Windows says **64-bit operating system, x64-based processor**, download **Windows x86** from Blackmagic Design. Despite the name, this is the normal 64-bit Resolve build for modern Intel and AMD PCs. Choose **Windows ARM** only when System Type identifies an ARM-based processor and the computer meets Blackmagic's current Windows ARM requirements. The label catches people out because x86 often means 32-bit software elsewhere. In Blackmagic’s picker, it identifies the Intel and AMD family. Blackmagic staff [confirmed that both Windows downloads are 64-bit](https://forum.blackmagicdesign.com/viewtopic.php?p=1092546&t=210617&ref=davinciresolveclub.com). There is no current 32-bit Resolve package hiding behind the x86 button. **Requirements checked September 7, 2026:** the figures below come from Blackmagic’s **Resolve 21.0.4** readme, updated August 4\. Read the notes for the version you are downloading; an older tutorial or a laptop’s marketing page cannot establish support for a newer release. ## Choose the Build in 30 Seconds | What Windows reports | Resolve download | Typical hardware | | -------------------------------------------- | -------------------------------------------------------------- | ----------------------------------------------------------------------------- | | 64-bit operating system, x64-based processor | **Windows x86** | Intel Core, Intel Core Ultra, AMD Ryzen and AMD Threadripper PCs | | 64-bit operating system, ARM-based processor | **Windows ARM**, after checking the current supported baseline | Supported Windows-on-ARM PCs that meet the listed Snapdragon X Elite baseline | | 32-bit operating system | Neither current build | Unsupported operating-system architecture for current Resolve | ![Windows System type x64-based processor mapped to the Resolve Windows x86 download](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/windows-system-type-v2-1.webp) Annotated illustration based on [Pureinfotech’s Windows About interface example](https://pureinfotech.com/check-if-processor-arm64-x64-64bit-windows-11/?ref=davinciresolveclub.com). The processor wording—not “64-bit” alone—decides which Windows download to choose. The words “64-bit” alone do not settle the choice because both families are 64-bit. What matters is the processor architecture: **x64-based** versus **ARM-based**. A product name such as Surface, Galaxy Book or Copilot+ PC is not enough either; those families can span different processors and generations. ## How to Check x64 or ARM in Windows 1. Open **Settings**. 2. Select **System**, then **About**. 3. Find **System type** under Device specifications. 4. Match the exact result to the table above. Microsoft’s [System type instructions](https://support.microsoft.com/en-us/windows/experience/compatibility/32-bit-and-64-bit-windows-frequently-asked-questions?ref=davinciresolveclub.com) distinguish the operating-system type from the processor type. Read the processor part of that line. Depending on your Settings version, the section may be called **Device specifications** or **Device info**, as in the annotated example above. Do not infer the processor from a **Program Files (x86)** folder: Microsoft documents that folder on Windows ARM too. Before buying a computer, check its exact processor on the manufacturer’s specification page. “Windows 11, 64-bit” alone does not tell you which Resolve package it needs. If the machine is a conventional Intel or AMD PC and you want the complete installation path, continue with the [Windows download and installation guide](https://davinciresolveclub.com/davinci-resolve-for-windows/). For the other operating-system routes, the [Resolve download hub](https://davinciresolveclub.com/davinci-resolve-download/) keeps the official Windows, Mac, Studio and older-version choices in one place. ## Why Does Blackmagic Call the Intel and AMD Build x86? x86 names the processor family that grew from Intel's earlier x86 instruction set. Modern Intel and AMD Windows PCs normally use the 64-bit extension called x86-64, x64 or AMD64\. Software download pages do not all label that family the same way. Blackmagic’s [support explanation of the download buttons](https://forum.blackmagicdesign.com/viewtopic.php?p=1100291&t=212186&ref=davinciresolveclub.com) maps Windows x86 to standard Intel and AMD PCs. Windows ARM is the separate ARM64 package. Choose by the operating system and processor together: - Intel or AMD Windows PC: Windows x86. - Supported ARM-based Windows PC: Windows ARM. - Mac with Apple silicon: Mac OS, not Windows ARM. ![Official Blackmagic Design picker with Windows x86 and Windows ARM DaVinci Resolve downloads](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-windows-build-picker.webp) Blackmagic exposes separate current download buttons for the two Windows processor families. The Free and Studio rows each repeat the same architecture choice. Use [Blackmagic Design's official Resolve page](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com) or its [support center](https://www.blackmagicdesign.com/support/?ref=davinciresolveclub.com). This site does not host or repackage either installer. ## Current Resolve 21 Windows Requirements The current minimums are not identical. The values below combine [Blackmagic's Resolve 21.0.4 readme](https://www.blackmagicdesign.com/support/content/readme/f1b3986a11634684b538ff3d1d4b55d6?ref=davinciresolveclub.com) with Blackmagic support's x86-for-Intel-and-AMD build distinction: | Requirement | Windows x86 | Windows ARM | | ------------------ | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Operating system | Windows 10 Creators Update (the readme’s listed minimum) | Windows 11 for ARM | | Processor baseline | Intel or AMD x64 family | Qualcomm Snapdragon X Elite series | | System memory | 16GB; 32GB when using Fusion | 16GB; 32GB with 4K or Fusion | | Graphics | Integrated or discrete GPU with at least 4GB VRAM; OpenCL 1.2 or CUDA 12.8 | No separate GPU or VRAM minimum is stated in the ARM section; use the supported platform and its required drivers. | | Driver requirement | Official AMD/Intel GPU drivers; NVIDIA Studio 581.57 or newer when using NVIDIA | Check the PC and peripheral vendors for Windows ARM support; the ARM readme does not list an NVIDIA driver floor. | Blackmagic’s Windows 10 compatibility floor is not a recommendation to run an unmaintained OS. [Standard Windows 10 support ended October 14, 2025](https://support.microsoft.com/en-us/windows/experience/compatibility/32-bit-and-64-bit-windows-frequently-asked-questions?ref=davinciresolveclub.com); check your update coverage separately. The x86 readme also calls for Desktop Video 12.9 or later **when using Blackmagic monitoring hardware**, not for every laptop installation. These are compatibility floors, not promises of smooth playback. For GPU choices and memory planning, use the [complete Resolve system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). Our [PC compatibility checker](https://davinciresolveclub.com/davinci-resolve-pc-checker/) is a first filter based on the details you enter—not a hardware scan or a substitute for testing your footage. “Snapdragon X Elite series” does not mean every Snapdragon or every Copilot+ PC. Blackmagic's current readme names a specific ARM baseline. If a newer processor or another ARM vendor is absent from that document, check the latest readme and Blackmagic support material before treating it as supported. ## Why Use the Native ARM Build Instead of x86 Emulation? [Microsoft's Windows on Arm FAQ](https://learn.microsoft.com/en-us/windows/arm/faq?ref=davinciresolveclub.com) explains that Windows 11 ARM can run many x86 and x64 applications through emulation. That does not make the x86 Resolve installer the best default when Blackmagic supplies a native ARM build for the supported machine. A native package avoids translating the application's processor instructions at runtime. Microsoft says native ARM apps generally provide the best performance, responsiveness and battery behavior on ARM devices. That is a platform principle, not proof that every Resolve operation will be faster on every ARM laptop. Resolve performance still depends on the source codec, GPU path, memory capacity, thermal limits, effects, plugins and export format. Compare a real timeline, not two architecture labels. A controlled test should use the same media, timeline, effects, playback settings and output preset. ## The Real ARM Risk Is the Dependency Chain The application can be native while one critical part of the editing system is not. Before moving paid work to Windows ARM, inventory everything that touches the project: - OpenFX video plugins and their licensing managers. - VST audio plugins used on tracks, buses or the Fairlight page. - Control surfaces, capture devices, card readers and video I/O hardware. - Camera utilities, codec components and media-management tools. - Shared-storage, backup and cloud-sync clients. - Font managers, subtitle tools and delivery quality-control software. Microsoft's [current emulation documentation](https://learn.microsoft.com/en-ca/windows/arm/apps-on-arm-x86-emulation?ref=davinciresolveclub.com) states that emulation supports user-mode code but not drivers. Kernel-mode components must be built for ARM64\. Its platform FAQ also warns that an x86 or x64 setup program cannot install an ARM64 driver. That distinction matters for audio interfaces, video I/O, dongles and other peripherals. The control application may launch under emulation while the device still fails because the required driver is not available for ARM64. Check the exact plugin version and its license helper, not a blanket claim that all plugins work or none do. Look for explicit **Windows ARM or ARM64** support from the vendor. “Windows 11,” “64-bit,” or support for Apple silicon on macOS does not establish compatibility with Resolve on Windows ARM. ## Free, Studio and Architecture Are Separate Choices First choose the edition: DaVinci Resolve Free or DaVinci Resolve Studio. Then choose the architecture: Windows x86 or Windows ARM. A Studio licence does not convert one installer architecture into the other, and downloading the Studio package does not create a paid entitlement. If you are deciding between editions, use the [Free versus Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/). If you already own Studio, download the Studio row that matches the same System Type rule. Keep the licence or activation details available before replacing a working production installation. ## Move a Resolve Project Between x86 and ARM Safely A Resolve project can move between computers, but its project file is not a copy of the whole workstation. Media paths, plugins, fonts, LUTs, audio tools and hardware may still need attention. Use the **same Resolve version** on both machines for the first transfer test, with the required edition and supported dependencies. Keep a pre-update backup. Blackmagic’s 21.0.4 readme warns that an individual project created or opened in 21.0.4 will no longer open in 20.3.2, even though the library can remain accessible. Installing the older app does not undo that project change. Follow the [safe update and backup workflow](https://davinciresolveclub.com/update-davinci-resolve-safely/) before combining a computer move with a Resolve upgrade. ![Resolve Media Pool, title track, Effects library and audio meters to check after moving a project to Windows ARM](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/windows-arm-project-check-v2.webp) Annotated illustration based on [Blackmagic’s official Studio 21 Edit interface](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com). Use your own project to check media, titles, required plugins and sound; this is not a claimed ARM compatibility test. 1. Back up the project library and export the important project separately. 2. Duplicate the project so the first ARM test is disposable. 3. Record every required plugin, font, LUT, control surface and media utility. 4. Install only versions that their vendors support on Windows ARM. 5. Relink media and check clips from every camera or capture source. 6. Open Fusion compositions and Fairlight buses that depend on external tools. 7. Render a representative section and compare the output outside Resolve. A lightweight H.264 sample proves very little when the production project uses 10-bit HEVC, RAW, multicam, noise reduction or Fusion. Test the hardest normal section of the real job. If a source format behaves differently, compare it with the [Resolve codec and format guide](https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/) before blaming the CPU architecture. ## If You Downloaded the Wrong Build Recheck System type and return to Blackmagic’s official picker before changing drivers or deleting preferences. If the download is incomplete, discard only that installer file and obtain the correct package. If Resolve is already installed, back up active projects before uninstalling or replacing it. Keep project libraries and source media intact. Keep diagnosis narrow: - **Installer will not run:** verify the package architecture and current OS requirement. - **Resolve opens but a device is absent:** verify the device's ARM64 driver as well as its control app. - **A plugin is missing:** verify its exact Windows ARM build and licensing component. - **Media is offline or slow:** separate file paths, codec support, storage and GPU behavior from the installer choice. - **A project changes appearance:** compare fonts, LUTs, plugins and color-management settings on both systems. Make one reversible change at a time. Deleting several settings folders at once makes it harder to tell what caused the fault. If the correct package still will not install, use the [installation-errors guide](https://davinciresolveclub.com/davinci-resolve-installation-errors/) with the exact message and your processor details. ## Frequently Asked Questions ### Should a 64-bit x64 PC download DaVinci Resolve Windows x86? Yes. If Windows reports a 64-bit operating system and an x64-based processor, choose Blackmagic's Windows x86 download. That is the current standard package for modern Intel and AMD Windows PCs. ### Is the DaVinci Resolve Windows x86 download 32-bit? No. Blackmagic support has confirmed that the current Windows x86 and Windows ARM Resolve packages are both 64-bit. The x86 label identifies the Intel and AMD processor family in Blackmagic's picker; it does not mean that Resolve is a 32-bit application. ### Can I install the Windows x86 build on a Snapdragon PC? Windows 11 ARM can emulate many x86 and x64 user applications, but Blackmagic supplies a native Windows ARM build for its supported ARM baseline. Use the native ARM package when the machine meets the current requirement, then verify plugins, drivers, media and export behavior. ### Does DaVinci Resolve ARM work on every Snapdragon processor? Do not assume that it does. Blackmagic’s Resolve 21.0.4 readme names Windows 11 for ARM and the Snapdragon X Elite series. Another Snapdragon model is not established as supported by that baseline; check its current release notes and Blackmagic support before relying on it. ### Will my Resolve plugins work on Windows ARM? Compatibility depends on each plugin and its licensing components. Check the vendor's current page for the exact version and explicit Windows ARM or ARM64 support. “Windows 11” or “64-bit” alone does not prove native ARM compatibility. ### Do x86 device drivers work through Windows ARM emulation? No. Microsoft says emulation covers user-mode application code, not kernel-mode drivers. Hardware that needs a driver requires an architecture-compatible ARM64 driver, even when its companion application can run under emulation. ### Can the same Resolve project open on x86 and ARM computers? A project can move, but use matching Resolve versions for the initial test and check the required edition. Back up and duplicate it, then verify media, codecs, fonts, LUTs, plugins, audio and a representative export. A project opened in a newer Resolve release may not reopen in an older one; the 21.0.4 readme specifically warns about 20.3.2. ### DaVinci Resolve for Mac: Official Download & Install URL: https://davinciresolveclub.com/davinci-resolve-for-mac/ Last updated: 2026-09-07T20:24:57.000Z Start at [Blackmagic Design’s official Resolve page](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com), then check your Mac before selecting a download. If you are updating an existing installation, back up the project library and export important projects before the new version opens them. An Intel Mac needs a separate compatibility check. If About This Mac shows **Processor** followed by an Intel model, do not assume the current installer supports it. Intel is outside Blackmagic’s listed 21.0.4 baseline. That is not proof that every Intel Mac is technically unable to launch it; it means you should use the [official older-version download route](https://davinciresolveclub.com/davinci-resolve-old-versions/) and match the release to both your hardware and macOS. I checked Blackmagic’s download catalog on **September 7, 2026**: the latest listed Free and Studio Mac packages were **DaVinci Resolve 21.0.4**, dated August 5\. The requirements below apply to that release. If the official download changes, read its new release notes first. The [Download & Install hub](https://davinciresolveclub.com/davinci-resolve-download/) covers the other platforms and download choices. ## Check the Mac Before You Download Start with the Apple menu, then **About This Mac**. [Apple's current identification guide](https://support.apple.com/en-us/116943?ref=davinciresolveclub.com) says an Apple silicon model shows **Chip**, while an Intel model shows **Processor**. The same window gives you the installed macOS version and memory. ![About This Mac Chip and Memory fields used to check an Apple silicon Mac before downloading Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/mac-chip-check-v2.webp) Annotated illustration based on [Apple’s About This Mac example](https://support.apple.com/en-us/116943?ref=davinciresolveclub.com). The example shows M2 Pro and 16GB; its macOS version is not shown. Check your own OS version against the current Resolve requirements. | Current Resolve 21.0.4 Mac minimum | What it means | | ------------------------------------------ | -------------------------------------------------------------------------- | | macOS 15 Sequoia or later | An older macOS release is outside the current minimum. | | Apple silicon computer | About This Mac should show Chip, not an Intel Processor field. | | 8GB system memory | This is a compatibility floor, not a comfortable target for every project. | | 16GB when using Fusion | Fusion raises Blackmagic's stated memory minimum. | | Desktop Video 12.9 or later for monitoring | Relevant when the workflow uses supported Blackmagic video I/O hardware. | These values come from [Blackmagic's Resolve 21.0.4 readme](https://www.blackmagicdesign.com/support/content/readme/f1b3986a11634684b538ff3d1d4b55d6?ref=davinciresolveclub.com). They describe a compatibility floor, not smooth playback with every camera format, noise-reduction stack or Fusion composition. The [complete system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) handles the broader hardware question. Apple silicon includes families such as M1, M2, M3, M4 and M5\. Sharing that processor class does not make every Mac equally capable. Memory, the exact chip, cooling, source codec and effects determine how demanding the job will be. If you are buying rather than installing on a Mac you already own, compare configurations in our [Resolve laptop guide](https://davinciresolveclub.com/best-laptop-for-davinci-resolve/). ## Blackmagic Website or Mac App Store? Both routes are official, but they solve different problems. The [current Mac App Store listing](https://apps.apple.com/us/app/davinci-resolve/id571213070?mt=12&ref=davinciresolveclub.com), written by Blackmagic, says its build does not support some external control panels and may not work with every third-party OpenFX or VST plugin. It sends users who need those integrations to Blackmagic's support website. | Your situation | Download route to check | | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | | You rely on a control panel or third-party OpenFX/VST plugins | Start with the direct Blackmagic build; check the specific integration’s requirements. | | You prefer App Store installation and its stated limitations do not affect your work | The official Mac App Store listing is a valid option. | | You already own a Studio activation code, dongle or Blackmagic Cloud license | Use the direct Studio build for that license, not the separately purchased App Store edition. | | You bought Studio through the Mac App Store | Use that App Store purchase; do not expect it to activate the direct Studio installer. | For a working edit station, I would start with the direct Blackmagic build unless there is a specific reason to use the Store. The reason is integration and licensing—not a claim that one build renders faster. Check the panel or plugin you actually need rather than assuming every third-party tool behaves the same way. ## Free or Studio on Mac? Free does not require a paid Studio license. For direct Studio downloads, Blackmagic’s [current release listing](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) accepts a **software activation code, license dongle or Blackmagic Cloud license**. Downloading the Studio installer does not supply that entitlement. The Mac App Store is a separate license channel. Blackmagic’s [Studio licensing table](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5FStudio%5F20%5FFeatures.pdf?ref=davinciresolveclub.com) identifies its Store purchase as noninterchangeable with other desktop or Cloud licenses. A Store purchase will not activate the direct Studio installer, and a direct activation code is not a Store purchase. For feature limits, see [Free versus Studio](https://davinciresolveclub.com/davinci-resolve-vs-studio/); the [cost and license guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) covers buying choices. ## Download the Direct Mac Installer From Blackmagic ![Official Blackmagic Design download picker with Mac OS X options for DaVinci Resolve Free and Studio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-mac-download-picker.webp) Blackmagic's current picker still labels the button Mac OS X. The 21.0.4 readme gives the actual current minimum as macOS 15 or later on Apple silicon. 1. Go to the official Blackmagic Resolve product page. 2. Pick the Free download or the Studio route that matches your license. 3. Select **Mac OS X** in Blackmagic's download picker. 4. Complete the requested registration information if the Free download asks for it. 5. Save the file locally and let the download finish completely. 6. If the browser saved a compressed archive, expand it before running the installer. We link to the developer instead of hosting or repackaging the installer. Start from Blackmagic’s product or [support page](https://www.blackmagicdesign.com/support/?ref=davinciresolveclub.com), and check the exact version you selected. A file size or checksum copied from a different release does not validate your download. ## Back Up an Existing Project Library Before Updating Installing for the first time? Skip to the next section. Updating a working system? Protect the downgrade path before the new version opens a production project. Blackmagic says it made an effort to keep the 21.0.4 project library compatible with 20.3.2\. It also says that individual projects created or opened in 21.0.4 are no longer accessible in 20.3.2\. Reinstalling the old application is therefore not a complete rollback plan. 1. Create a full project-library backup. 2. Export separate backups of active or irreplaceable projects. 3. Record the current Resolve version and any critical plugin versions. 4. Keep the backups away from the same cache or working-media location. 5. Open a duplicate test project in the new version before production work. Our [safe Resolve update workflow](https://davinciresolveclub.com/update-davinci-resolve-safely/) explains the backup and rollback steps. Keeping the old application is useful, but it cannot undo a project-format change; the pre-update backup protects that project. ## Install the Blackmagic Build on macOS Blackmagic’s readme says to double-click the DaVinci Resolve Installer icon and follow the onscreen steps. On a Mac, first open the downloaded disk image to reach that installer. This follows Apple’s [disk-image and package installation instructions](https://support.apple.com/en-gb/guide/mac-help/-mh35835/mac?ref=davinciresolveclub.com). 1. Find the completed download. If it arrived as a ZIP archive, expand it first. 2. Open the **.dmg disk image**, then double-click the **DaVinci Resolve Installer** inside it; the name may include the version. 3. Check that this is the package from the official download you requested. Read the installer’s prompts before approving them. 4. Follow the installation steps, providing administrator credentials only if requested. Use the normal Applications location. 5. Close the installer when it finishes. Restart if requested, then open Resolve from Applications. Read the exact macOS warning before deciding what to do. Apple’s [safe-app guidance](https://support.apple.com/en-au/102445?ref=davinciresolveclub.com) distinguishes an app it cannot verify from an app reported as damaged, malicious or revoked. An official-looking filename alone is not enough reason to override a warning. For an eligible unverified-developer or notarization warning, Apple describes a specific **System Settings > Privacy & Security > Open Anyway** exception. Consider it only when you trust the source and are confident the app has not been altered. If you cannot establish that, stop and obtain a fresh official copy or ask the developer about the alert. **Do not use that exception for a malware, damaged-app or revoked-authorization alert.** Resolve the warning rather than forcing the package to run. Do not disable Gatekeeper globally or paste Terminal bypass commands from an install tutorial. On a managed Mac, your organization may restrict installation or exceptions. ## Install From the Mac App Store Open the official Free or Studio listing in the Mac App Store and check that the developer is **Blackmagic Design Inc**. Use the intended Apple Account, especially for a Studio purchase. Both current listings specify **macOS 15 or later, Apple silicon, 8GB memory or 16GB with Fusion, and a 1440×900 display**. The display figure is from the Store listings; it is not an extra line quoted from the direct-build readme. Before switching from the Store edition to the website edition, back up your projects and confirm your license channel. Do not erase libraries or preferences merely to change distribution. Install and test the intended build before removing anything you might need for recovery. ## Prove the First Launch With Real Media ![Resolve 21 Media Pool, timeline viewer and audio meters for checking media after Mac installation](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/mac-first-launch-v2.webp) Annotated illustration based on Blackmagic Design’s [official Studio 21 Edit interface](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com). Check picture and sound using your own media; this is not a benchmark or a claimed test of your Mac. 1. Launch Resolve and confirm that it reaches the Project Manager. 2. If this is an update, use a test library or duplicate project first. 3. Check media, cache and gallery locations before generating large files. 4. Import one clip from the camera, phone or screen recorder you actually use. 5. Play and scrub it, apply a simple correction and confirm audio output. 6. Export a short section and play the result outside Resolve. A sample clip cannot validate every 10-bit HEVC, RAW, multicam or Fusion workload. Test footage from the camera, phone or screen recorder you normally use, with an effect representative of your work. If Resolve launches but playback is poor, follow the [slow-playback diagnosis](https://davinciresolveclub.com/davinci-resolve-slow-playback/) before reinstalling. ## If Resolve Will Not Install or Open on Mac | Symptom | First check | | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The current installer will not run on an Intel Mac | Intel is outside the current 21.0.4 listed minimum. Use Blackmagic's archive and match an older Resolve release to the Mac and macOS version. | | macOS says the package cannot be opened | Read the exact alert. Only an eligible unverified-app warning has a limited exception path; do not override malware, damaged-app or revoked-authorization warnings. | | Resolve opens but a panel or plugin is missing | Check whether this is the Mac App Store build and compare the device or plugin with the App Store limitations. | | Resolve opens but media is slow or offline | Separate source-codec, storage, permission and performance problems from the installation itself. | | An older Resolve version will not open an updated project | Restore the library or individual-project backup made before 21.0.4 opened it. | Make one reversible change at a time. Keep the exact error, install source, Mac chip and macOS version together; they help distinguish incompatible hardware, permissions, licensing and failed setup. If these checks do not identify the problem, use the [installation-errors guide](https://davinciresolveclub.com/davinci-resolve-installation-errors/). Do not delete preferences, libraries and cache together to see what happens. ## How to Uninstall Resolve on Mac For the direct Blackmagic build, the 21.0.4 readme specifies the **Uninstall Resolve** icon. For a Store installation, follow Apple’s app-removal instructions for that copy. Neither is an instruction to manually delete project libraries, source footage, galleries or exports. Back up projects before removing anything. For a clean reinstall, identify the install source, license channel and exact problem first. A destructive “clean up everything” pass is rarely the safest first repair. ## Frequently Asked Questions ### Is DaVinci Resolve free on Mac? Yes. The Free edition is available for Mac from Blackmagic Design and through the Mac App Store. Studio is a separate paid edition. Pick the distribution and license path deliberately, especially if you use external panels or third-party plugins. ### Does DaVinci Resolve 21 work on Intel Macs? Blackmagic’s Resolve 21.0.4 Mac minimum lists an Apple silicon computer, not Intel. Treat an Intel Mac as outside that supported baseline and match an archived release to its hardware and macOS version. This is not a claim that every Intel Mac is technically incapable of launching the app. ### Does DaVinci Resolve work on M1, M2, M3, M4 and M5 Macs? These are Apple silicon families and satisfy the processor class named in the 21.0.4 minimum. You must also meet the macOS and memory requirements. Chip tier, memory, cooling, codec and effects still affect performance; the chip name alone does not guarantee smooth editing. ### Should I download Resolve from Blackmagic or the Mac App Store? Use the Blackmagic website when you need external control panels or third-party OpenFX or VST plugins. Blackmagic's current App Store listing says some panels are unsupported and some plugins may be incompatible. The App Store is still an official route when those limitations do not affect you. ### How much memory does DaVinci Resolve need on Mac? Blackmagic's current Resolve 21.0.4 minimum is 8GB of system memory or 16GB when using Fusion. That is a compatibility minimum. Larger projects, Fusion, noise reduction and multitasking can justify substantially more memory. ### Why will DaVinci Resolve not open on my Mac? Check the exact alert, Mac chip, macOS version and download source first. An unsupported configuration, a security warning, missing plugin and updated project that will not open in an older release are different problems. Do not bypass a malware or damaged-app warning, or delete project data as a first repair. ### Can I update Resolve on Mac without backing up? You can install an update, but opening a production project without a backup removes a safe downgrade path. Blackmagic says projects created or opened in 21.0.4 cannot then be opened in 20.3.2\. Back up the full library and export important projects first. ### DaVinci Resolve for Windows: Download & Install URL: https://davinciresolveclub.com/davinci-resolve-for-windows/ Last updated: 2026-09-07T18:35:51.000Z Download from [Blackmagic Design’s official Resolve page](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com). Before choosing a Windows button, check both the processor type and whether Windows is 64-bit. If you are updating an existing installation, back up the project library and export the projects you cannot afford to lose before the new version opens them. I checked Blackmagic’s current download catalog on **September 7, 2026**: the latest listed Free and Studio packages were **DaVinci Resolve 21.0.4**, dated August 5\. If the official picker shows a newer release when you visit, read that release’s notes before installing it; the requirements and rollback warning below are specifically for 21.0.4. Need a different platform or an older release? The [Download & Install hub](https://davinciresolveclub.com/davinci-resolve-download/) covers those choices. For this Windows setup, start with the correct package, check the [current system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/), then test a clip before moving real work. ## Get the Windows Installer From Blackmagic, Not a Mirror Blackmagic offers Free and Studio in its download picker. Choose the edition first, then the Windows architecture. The free download asks for registration details; the Studio support download offers a separate route for existing license holders. Use the labels shown by Blackmagic, not a Windows logo on an advertisement. ![Official Blackmagic Design picker with Windows x86 and Windows ARM DaVinci Resolve downloads](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/blackmagic-windows-installer-picker.webp) Use the Windows choice inside Blackmagic Design's own download picker. The architecture label matters more than the Windows logo. 1. Open the [official DaVinci Resolve product page](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com). 2. Select **Free Download Now** or the Studio download option. 3. Pick the edition you actually intend to run: Free or Studio. 4. Match **Windows x86** or **Windows ARM** to the system type. 5. Save the ZIP archive somewhere with enough free space to download and extract it. We link to the developer rather than hosting or repackaging the installer. Check the destination before downloading: a page calling itself “latest” may still offer an older release. A fixed file-size or checksum copied from another site is not a substitute for matching the exact official package. ## Windows x86 or ARM: Check System Type First “Windows 11” identifies the operating system, not the processor architecture. On Intel and AMD PCs, Blackmagic labels its **64-bit x86 build “Windows x86.”** That button does not mean a 32-bit Windows edition is supported. Snapdragon-based Windows machines use the separate ARM package only when they meet Blackmagic’s ARM requirements. ![Windows 11 System type showing a 64-bit operating system and x64-based processor for the Resolve Windows x86 download](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/windows-system-type-v2.webp) Annotated illustration based on a real [Windows Settings example by Pureinfotech](https://pureinfotech.com/check-if-processor-arm64-x64-64bit-windows-11/?ref=davinciresolveclub.com). Device identifiers are hidden. This illustrates the architecture field, not hardware suitable for Resolve; Settings labels can vary by Windows build. 1. Open **Settings**. 2. Go to **System**, then **About**. 3. Find **System type** in the device-information section. Microsoft calls this **Device specifications**; some Settings layouts show **Device info**. 4. **64-bit operating system, x64-based processor** means the **Windows x86** package. Check both parts of the line. 5. An **ARM-based processor** sends you to the ARM requirements below before the download. Blackmagic's [Resolve 21.0.4 readme](https://www.blackmagicdesign.com/support/content/readme/f1b3986a11634684b538ff3d1d4b55d6?ref=davinciresolveclub.com) is narrower than “any ARM-based Windows PC.” It lists Windows 11 for ARM and a Snapdragon X Elite series processor, with 16GB of memory or 32GB for 4K or Fusion work. Another ARM processor is not automatically covered just because Windows itself runs on it. Microsoft’s [Windows architecture guide](https://support.microsoft.com/en-us/windows/experience/compatibility/32-bit-and-64-bit-windows-frequently-asked-questions?ref=davinciresolveclub.com) explains how System type separates the operating system from the processor. If it says **32-bit operating system**, a different Resolve download button will not fix that limitation. Windows 11 itself is 64-bit only. For a buying or migration decision, our [Windows x86 versus ARM guide](https://davinciresolveclub.com/davinci-resolve-windows-x86-vs-arm/) covers the broader compatibility trade-offs. ## Check the Current Windows Requirements The table combines Blackmagic’s [Resolve 21.0.4 minimum requirements](https://www.blackmagicdesign.com/support/content/readme/f1b3986a11634684b538ff3d1d4b55d6?ref=davinciresolveclub.com) with the architecture check above. Where the ARM readme does not specify a separate GPU or driver floor, that is stated explicitly—not filled in with an invented minimum. | Check | Windows x86 | Windows ARM | | ------------------ | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | | Operating system | Windows 10 Creators Update or a supported newer Windows release; 64-bit installation | Windows 11 for ARM | | Processor platform | x64-based Intel or AMD PC | Qualcomm Snapdragon X Elite series | | System memory | 16GB; 32GB when using Fusion | 16GB; 32GB for 4K or Fusion | | Graphics | Integrated or discrete GPU with at least 4GB VRAM; OpenCL 1.2 or CUDA 12.8 | The ARM readme lists the processor platform rather than a separate discrete-GPU specification | | Graphics driver | Official AMD/Intel GPU drivers; NVIDIA Studio Driver 581.57 or newer | Use the supported software for the actual ARM device; do not apply an x86 NVIDIA requirement to every ARM laptop | **Windows 10 compatibility is not the same as Windows support.** Microsoft ended ordinary Windows 10 support on [October 14, 2025](https://support.microsoft.com/en-us/windows/deployment/updates-lifecycle/windows-10-support-has-ended-on-october-14-2025?ref=davinciresolveclub.com). For a new setup, I would use a supported Windows 11 installation. If you must keep Windows 10, check the support lifecycle and any Extended Security Updates eligibility for your exact edition separately. **Using Blackmagic video hardware for external monitoring?** The Windows readme also requires **Desktop Video 12.9 or later** for that workflow. It is not a requirement to install Desktop Video merely to use an ordinary computer display. These are compatibility checks, not a promise of smooth editing. Codec, resolution, bit depth, effects, multicam and Fusion can change the workload considerably. Before buying hardware, compare your project with the full requirements guide and our [Resolve PC checker](https://davinciresolveclub.com/davinci-resolve-pc-checker/). A 4GB VRAM minimum is not a recommendation to buy a 4GB GPU for demanding work. ## Free Is the Default; Studio Needs a License Start with Free if you do not have a Studio license. Blackmagic’s [current Studio download listing](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) accepts a license dongle, a software activation code or a Blackmagic Cloud license. If Studio came with hardware you bought, check the included license details. Downloading the Studio installer alone does not activate it. Choose the edition around the work you need to do. See [what the free version includes](https://davinciresolveclub.com/davinci-resolve-free-version-features/) and the [Free versus Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) for feature limits. The [cost guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) covers pricing and license choices. ## Protect an Existing Resolve Installation Before Updating First installation? Skip to the install steps. Updating a working machine? Pause before 21.0.4 touches a production project. Blackmagic says 21.0.4 makes an effort to keep the project library compatible with 20.3.2\. It also warns that an individual project created or opened in 21.0.4 is no longer accessible in 20.3.2\. That means uninstalling the new application does not by itself create a safe rollback. 1. Create a **full project library backup**. 2. Export separate backups of active, irreplaceable projects. 3. Record the current Resolve version and the GPU driver version. 4. Keep installation media and backups off the same working drive where practical. 5. Only then install the new release and open a copy of a representative project. Our [safe Resolve update workflow](https://davinciresolveclub.com/update-davinci-resolve-safely/) explains the backup and rollback steps. Keep the old installer if you may need it, but remember that it cannot reverse a project-format change; the pre-update backup is what protects that project. ## Extract the ZIP and Install Resolve Extract the complete ZIP before running setup. In File Explorer, right-click it and choose **Extract All**, following [Microsoft’s extraction instructions](https://support.microsoft.com/en-us/windows/experience/storage-filemanagement/zip-and-unzip-files?ref=davinciresolveclub.com). Run the installer from the resulting folder rather than from a ZIP preview. 1. Right-click the downloaded ZIP and choose **Extract All**. 2. Open the extracted folder after Windows finishes. 3. Run the DaVinci Resolve installer. 4. Review the publisher and file origin shown by Windows before approving User Account Control. 5. Follow the onscreen installer prompts. 6. Restart Windows if setup or a driver update asks for it. The readme says the package also installs **Blackmagic RAW Player**, **Blackmagic Proxy Generator** and utilities for hardware control panels. Those names alone do not mean the download is wrong. Review the installer’s component descriptions before changing selections; do not install an unrelated offer simply because it appears beside a download button. ## Verify the First Launch Before Moving Real Work Reaching “Finished” tells you setup completed. A short test with footage you actually use checks something more useful: whether Resolve can open, find the media, play picture and sound, and produce an export on this computer. ![Resolve 21 Media Pool, timeline viewer and timeline to check a clip after Windows installation](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/resolve-first-launch-v2.webp) Annotated illustration based on Blackmagic Design’s [official Resolve 21 Edit interface](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com). Use your own representative clip for the test; this example is not a benchmark or evidence that we tested your PC. 1. Launch Resolve and confirm it reaches the Project Manager without a GPU initialization warning. 2. If this was an update, create a test library or open a duplicate project first. 3. Check that media, cache and gallery locations point to drives you actually intend to use. 4. Import a clip from your real camera, phone or screen recorder. 5. Play it, scrub it, add a simple correction and confirm audio output. 6. Export a short section using a normal delivery preset and play the rendered file outside Resolve. Test the footage you expect to edit. A friendly H.264 sample does not validate a project built around 10-bit HEVC, RAW, mixed frame rates or heavy Fusion. The test only counts when it touches the codec and storage path you expect to use. ## If Resolve Will Not Install or Open | Symptom | First check | | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The installer will not start | Confirm the ZIP was fully downloaded and extracted, then run setup from the extracted folder. | | Windows says the app cannot run on this PC | Check both OS and processor architecture: 64-bit Windows plus the matching x86 or supported ARM package. | | Resolve reports an unsupported GPU or fails at launch | Install the current supported driver from NVIDIA, AMD or Intel and compare it with Blackmagic's current readme. | | The official file was quarantined | Verify that it came directly from Blackmagic and review the exact security alert. Do not disable protection globally. | | Resolve opens but playback is unusable | Test a simple supported clip, then separate codec, driver, storage and effects problems using the [slow playback guide](https://davinciresolveclub.com/davinci-resolve-slow-playback/). | | An older Resolve version will not open an updated project | Restore the separate project or library backup made before the new version opened it. | Change one reversible thing at a time, keeping the exact error message. Do not delete project libraries, reset everything or turn off Windows protection to see what happens. If the basic checks do not identify the problem, the [installation-errors guide](https://davinciresolveclub.com/davinci-resolve-installation-errors/) separates failed setup from failed first launch. ## How to Uninstall DaVinci Resolve on Windows Blackmagic's current readme sends Windows users to Programs and Features, then DaVinci Resolve, then Uninstall. Current Windows settings also expose installed apps. Whichever route you use, removing the application is not the same operation as deleting project libraries, source media, cache or exports. A reinstall does not require erasing project data. Back it up, uninstall Resolve, restart if needed, then reinstall the correct official build. Delete cache only when you understand which cache location belongs to the affected project and have confirmed that source media is safe. ## Frequently Asked Questions ### Is DaVinci Resolve free on Windows? Yes. Blackmagic Design offers a free Windows edition. Studio is separate and requires a valid activation code, license dongle or Blackmagic Cloud license. Downloading the Studio package alone does not activate it. ### Should I download Windows x86 or Windows ARM? Choose Windows x86 when System type shows a 64-bit operating system and an x64-based processor. Choose Windows ARM for an ARM-based computer that meets Blackmagic’s current ARM requirements, including the supported Snapdragon processor family. The Windows x86 label does not mean 32-bit Windows is supported. ### Does DaVinci Resolve work on Windows 11? Yes, Resolve 21.0.4 works on supported Windows 11 systems. The computer must also meet the memory, GPU, driver and processor requirements. Windows 11 by itself does not prove that a machine is suitable for Resolve or identify whether it needs the x86 or ARM installer. ### How much RAM does DaVinci Resolve need on Windows? Blackmagic's Resolve 21.0.4 minimum for Windows x86 is 16GB of system memory, or 32GB when using Fusion. Its Windows ARM minimum is 16GB, or 32GB for 4K or Fusion. These are compatibility minimums, not guaranteed smooth-performance targets. ### Can I install DaVinci Resolve without uninstalling the old version? An in-place update may work, but protect the project library first. Blackmagic warns that projects created or opened in 21.0.4 cannot then be opened in 20.3.2\. Make a full library backup and export important individual projects before opening them in the new version. ### Why does DaVinci Resolve not open after installation? Check the exact error, the downloaded architecture, complete ZIP extraction, GPU support and graphics driver. Also compare the PC with the current minimum requirements. These are diagnostic starting points, not proof of one cause; avoid deleting project data or disabling Windows security. ### Where should I download DaVinci Resolve for Windows? Use Blackmagic Design's official DaVinci Resolve product or support page. It provides the current Free and Studio installers for Windows x86 and Windows ARM. This guide links to that official source and does not host, mirror or repackage the installation file. ### Best Laptops for DaVinci Resolve in 2026 URL: https://davinciresolveclub.com/best-laptop-for-davinci-resolve/ Last updated: 2026-09-09T01:08:37.000Z **Quick answer:** my first shortlist pick for mixed DaVinci Resolve work is the **16-inch MacBook Pro with M5 Pro, 48GB memory and a 1TB SSD**. For Windows editing, compare the ASUS ProArt P16 and Lenovo Legion Pro 7i with an RTX 5070 Ti Laptop GPU, 12GB of VRAM and at least 32GB of system memory. Those Windows configurations fall below Studio 21.1's 16GB VRAM requirement for advanced AI tools; choose a higher-capacity GPU if that is part of your job. That answer changes if your work is mostly travel edits, proxy media or straightforward 4K timelines. A 24GB MacBook Air M5 can make sense there, and an RTX 5060 Windows laptop with 32GB of RAM is a reasonable lower-cost starting point. Buying more machine than your projects use wastes money; buying from a vague product-family name can leave you with the wrong GPU, memory or SSD. On a small screen, swipe the table sideways to see every column. With a keyboard, focus the table and use the arrow keys. | Best for | Configuration to look for | Main compromise | | ------------------------------ | ------------------------------------------------------------ | --------------------------------------------------------------------- | | My first pick for mixed work | 16-inch MacBook Pro, M5 Pro, 48GB, 1TB | High entry cost and no later memory upgrade | | Portable professional work | 14-inch MacBook Pro, M5 Pro, 24GB or 48GB, 1TB | 24GB is below the Studio background-task memory minimum | | Creator-first Windows laptop | ASUS ProArt P16, RTX 5070 Ti 12GB, 64GB, 2TB where available | 12GB VRAM is below the Studio advanced-AI minimum; check regional SKU | | Desk-first Windows GPU work | Lenovo Legion Pro 7i Gen 10, RTX 5070 Ti 12GB, 32GB or 64GB | 12GB VRAM is below the Studio advanced-AI minimum; heavy to carry | | Lower-cost Windows shortlist | Lenovo Legion 5i Gen 10, RTX 5060 8GB, 32GB, 1TB | 8GB VRAM is below both Studio feature thresholds described below | | Quiet travel and proxy editing | MacBook Air M5, 24GB, 512GB or 1TB | Fanless; 24GB is below the Studio background-task memory minimum | I checked the specifications, supporting reviews and Resolve 21.1 requirements on **September 9, 2026**. Prices and stocked configurations vary by country. These are editorial shortlist choices, not a live price ranking or a claim that one machine wins every test. Match the complete manufacturer part number before paying. ## Start With the Resolve Workload, Not “4K Capable” Resolution alone is a poor laptop filter. One 4K timeline may contain easy-to-decode camera media and a simple grade. Another may combine 10-bit long-GOP footage, multicam streams, noise reduction, Magic Mask, optical flow and a Fusion composition. Both are “4K,” but they don't ask the same thing from the CPU, GPU, memory or media engines. Before comparing laptops, inspect a representative camera clip in MediaInfo. Note its format, resolution, frame rate, bit depth and chroma subsampling. The example below is 8-bit 4:2:0 footage; a recommendation based on it should not be treated as proof for your different 10-bit source. ![MediaInfo resolution, frame rate, chroma subsampling and bit depth for checking laptop editing needs](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/laptop-source-properties.webp) Annotated illustration based on a real [Puget Systems MediaInfo example](https://www.pugetsystems.com/labs/articles/what-h-264-and-h-265-hardware-decoding-is-supported-in-davinci-resolve-studio-2122/?ref=davinciresolveclub.com). These are properties of one sample file, not recommended recording settings or a Resolve 21 compatibility result. [PugetBench for DaVinci Resolve](https://www.pugetsystems.com/pugetbench/creators/davinci-resolve/?ref=davinciresolveclub.com) separates encoding, processing, real-world timelines, Fusion, GPU effects and AI workloads. It runs tests in Resolve, but most of its measurements use export or render time. A high score is useful evidence; it is not a guarantee that scrubbing your camera footage will feel equally fast. Use three practical workload bands: - **Light and proxy:** short-form edits, one or two camera streams, basic correction, titles and optimized or proxy media. Memory and storage still matter, but a high-end GPU is usually unnecessary. - **Balanced 4K:** native 4K editing, several nodes, moderate effects, multicam and regular H.264, HEVC or ProRes delivery. This is where M5 Pro or an RTX 5060/5070-class configuration becomes sensible. - **Fusion and GPU effects:** temporal noise reduction, optical flow, AI tools, heavy Fusion compositions, high-resolution RAW or many simultaneous effects. Prioritize sustained cooling, memory headroom and more VRAM. If a lower-powered laptop otherwise fits your life, a planned [DaVinci Resolve proxy workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) can be a better investment than carrying a much heavier machine every day. Proxies improve the editing path; they don't turn a light laptop into a fast Fusion or noise-reduction workstation. ## How These Laptops Were Chosen This is an evidence-led buying guide, not a claim that I personally owned and benchmarked all six laptops. I checked Blackmagic's requirements, the exact manufacturer configurations and reviews that identify their test hardware. The M5 Pro benchmark cited below used **Resolve 20.3 Studio, not Resolve 21**. Manufacturer specifications establish what a laptop contains; only a relevant test can establish how quickly it completes a job. [Blackmagic's Resolve 21.1 readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) lists 8GB of system memory on Mac, or 16GB when using Fusion. On Windows it lists 16GB, or 32GB with Fusion, plus a GPU with at least 4GB of VRAM. Those are compatibility floors, not comfortable buying targets for every project. The [current Resolve system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) covers the full OS and driver matrix. ### Studio 21.1: Check the Feature, Not Just the App The [Studio 21.1 requirements](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) add these memory conditions. They are minimums for the named features, not proof of fast playback or a blanket ban on every AI-assisted feature below them. **Windows Intel/AMD laptops:** advanced AI tools require at least 16GB VRAM. Background rendering requires at least 32GB system RAM *and* 12GB VRAM. A 12GB RTX 5070 Ti configuration can meet the background-rendering memory condition while falling short of the advanced-AI condition. **Apple Silicon laptops:** advanced AI tools require at least 16GB system memory; background rendering and analysis require at least 32GB. The 24GB MacBook Air and 24GB MacBook Pro choices below are editing options, not configurations for those background features. Choose at least 32GB on the Air or 48GB on the shortlisted M5 Pro if you need that memory capacity, while still considering cooling and your project. For a new Windows laptop, 32GB of system memory is the sensible starting point. For a new Mac, 24GB is a workable starting configuration for balanced editing, while 48GB gives M5 Pro buyers more room for Fusion, multitasking and longer ownership. Unified memory and Windows RAM plus dedicated VRAM are different architectures, so there is no honest one-number conversion between them. ## 1\. MacBook Pro 16 with M5 Pro: My First Pick for Mixed Work **Buy:** M5 Pro with 20-core GPU, 48GB unified memory and 1TB SSD. I would start here for a mix of editing, grading and delivery when a large working display and mobility both matter. Apple's [MacBook Pro specifications](https://www.apple.com/macbook-pro/specs/?ref=davinciresolveclub.com) list media hardware for H.264, HEVC, ProRes and ProRes RAW, plus AV1 decode. Those are chip capabilities, not a promise that every format is supported or accelerated in every Resolve edition. Keep your actual camera codec in the comparison. The 16-inch M5 Pro has an 18-core CPU, a 20-core GPU and 307GB/s memory bandwidth. [Notebookcheck's review](https://www.notebookcheck.com/Apple-MacBook-Pro-16-2026-Test-M5-Pro-macht-eines-der-besten-Multimedia-Notebooks-noch-besser.1246158.0.html?ref=davinciresolveclub.com) tested a different memory/storage configuration: **64GB and 4TB**. Its PugetBench 2.0.0 results in Resolve 20.3 Studio were close to the RTX 5090 ProArt P16 in that comparison, though the P16 scored higher in both Resolve presets. That supports putting M5 Pro on the shortlist—not promising the same result from a 48GB/1TB machine in Resolve 21. **Choose it if:** you want one mobile machine for a broad mix of editing, color and delivery, and its size fits your bag. Treat manufacturer web-browsing battery figures as a different workload from rendering in Resolve; they are not editing-runtime estimates. **Skip or step up if:** your work is dominated by demanding Fusion, temporal effects or high-resolution RAW and every saved render minute has measurable value. Compare an M5 Max configuration or a larger-VRAM Windows system, but do it against your own project files before spending the premium. ## 2\. MacBook Pro 14 with M5 Pro: Best Portable Pro Choice **Buy:** M5 Pro, 24GB for mainstream editing or 48GB for heavier Fusion and multitasking, with a 1TB SSD. The 14-inch Pro is the more portable of these two recommendations: Apple lists the M5 Pro models at 1.60kg for 14-inch and 2.14kg for 16-inch, before the charger. You give up screen area for Resolve's dense interface. Also check the chip: the 14-inch M5 Pro is offered with **16-core or 20-core GPUs**, so two listings that both say “M5 Pro” need not contain the same processor configuration. Leave room in the budget for storage. Source media, proxies, optimized media, cache and exports add up quickly. I would choose 1TB for a primary editing laptop when possible, even if active media lives on an external SSD. That is a practical buying preference, not a Resolve installation requirement. ## 3\. ASUS ProArt P16: Best Creator-First Windows Option **Configuration to compare:** RTX 5070 Ti Laptop GPU with 12GB VRAM, 64GB system memory and a 2TB SSD. One verified regional example is [ASUS H7606WR-SE022X](https://estore.asus.com/se/90nb17d1-m00310-proart-p16-h7606-copilot-pc.html?ref=davinciresolveclub.com). It has all four of those specifications; another P16 listing may not. The ProArt P16 is worth comparing when you want Windows and NVIDIA hardware in a creator-focused chassis. [ASUS's regional specification table](https://www.asus.com/pl/laptops/for-creators/proart/proart-p16-h7606/techspec/?ref=davinciresolveclub.com) shows why the part number matters: the H7606 family spans several GPUs and memory configurations. Its onboard system memory is not a later RAM upgrade opportunity. Do not assume every RTX 5070 Laptop GPU has 8GB of VRAM. NVIDIA introduced a 12GB variant in April 2026, and [XMG's manufacturer explanation](https://www.xmg.gg/en/news-roadmap-2026-q2-xmg-roadmap/?ref=davinciresolveclub.com) explicitly distinguishes the 8GB and 12GB versions from the RTX 5070 Ti. The P16 H7606WP in the ASUS table has 8GB; the H7606WR example above has a 12GB 5070 Ti. Verify the actual laptop, not just “5070” in the title. Equal memory capacity also does not make two GPUs equally fast. ![ASUS ProArt P16 H7606WR-SE022X with RTX 5070 Ti 12GB, 64GB onboard memory and 2TB SSD](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/proart-exact-sku.webp) Editorial annotation of the [manufacturer's H7606WR-SE022X product photo and specifications](https://estore.asus.com/se/90nb17d1-m00310-proart-p16-h7606-copilot-pc.html?ref=davinciresolveclub.com). This is one regional configuration, not a store capture or proof of current local stock. Be careful with reviews of the same family. [Notebookcheck's May 2025 P16 review](https://www.notebookcheck.net/4K-OLED-is-replaced-by-120-Hz-2-8K-OLED-Asus-ProArt-P16-with-RTX-5070-Laptop-review.1026301.0.html?ref=davinciresolveclub.com) tested the H7606WP with an RTX 5070, 64GB RAM and 2TB SSD. Its limited generational performance gain was not a test of the 5070 Ti model recommended here, nor a Resolve 21 benchmark. Use that review for the configuration it actually measured. ## 4\. Lenovo Legion Pro 7i Gen 10: A Desk-First Windows Option **Buy:** RTX 5070 Ti 12GB with 32GB or 64GB of system memory and at least 1TB of SSD storage. Look for the **16IAX10H** platform. Lenovo's [official Pro 7 specifications](https://psref.lenovo.com/syspool/Sys/PDF/Legion/Legion%5FPro%5F7%5F16IAX10H/Legion%5FPro%5F7%5F16IAX10H%5FSpec.PDF?ref=davinciresolveclub.com) list the RTX 5070 Ti Laptop GPU with 12GB GDDR7 and a 140W TGP, plus memory offerings up to 64GB through two CSODIMM slots. Those specifications explain why it belongs in the comparison; they are not a measured Resolve advantage over the ProArt or MacBook. The trade-off is mobility. Lenovo lists a starting weight of 2.57kg, and the power adapter adds to what you carry. There is no built-in card reader on this platform. I would compare it for a mostly plugged-in workstation role, then check a representative Fusion or effects-heavy project before paying more for the GPU. If most of your work is cuts and basic grades away from a desk, the extra size may solve the wrong problem. ## 5\. Lenovo Legion 5i Gen 10: A Lower-Cost Windows Shortlist **Buy:** RTX 5060 8GB, 32GB system memory and 1TB SSD. The specific platform here is **Legion 5 15IAX10**. Lenovo's [15IAX10 specifications](https://psref.lenovo.com/syspool/Sys/PDF/Legion/Legion%5F5%5F15IAX10/Legion%5F5%5F15IAX10%5FSpec.pdf?ref=davinciresolveclub.com) list an RTX 5060 Laptop GPU with 8GB VRAM, memory offerings up to 32GB and a 1TB SSD option. Compare an actual 32GB/1TB listing with newer and discounted alternatives in your country. Gen 10 is not automatically the cheapest or best-value purchase just because it is on this shortlist. Eight gigabytes of VRAM can serve balanced 4K editing, especially when you manage proxies, cache and effects. It provides less room for high-resolution textures, demanding temporal processing and larger Fusion compositions than a 12GB configuration. If Resolve already reports [GPU memory full errors](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/) in your normal projects, don't treat another 8GB GPU as a durable upgrade without testing. ## 6\. MacBook Air M5 with 24GB: Best for Quiet Travel Edits **Buy:** 24GB unified memory with a 512GB or 1TB SSD. The MacBook Air M5 belongs on this list with a narrow job description. Apple's [current Air specifications](https://www.apple.com/macbook-air/specs/?ref=davinciresolveclub.com) include H.264, HEVC, ProRes and ProRes RAW media engines, and the machine can be configured above its 16GB base memory. It's silent, light and well suited to selects, proxy editing, short-form delivery and travel work. It is fanless. [RTINGS' public M5 Air review](https://www.rtings.com/laptop/reviews/apple/macbook-air-13-m5-2026?ref=davinciresolveclub.com) reports performance dropping during long, demanding workloads. Its test unit was the base 13-inch model with 16GB RAM, a 512GB SSD and an 8-core GPU—not the 24GB buying configuration above. More memory does not add a fan. For repeated long exports or substantial Fusion work, I would compare a cooled MacBook Pro instead. ## Mac or Windows for DaVinci Resolve? Mac is worth prioritizing when the balance of mobility, supported media hardware and the macOS applications you already use matters most. The M5 Pro shortlist is an editorial choice for mixed work, not a blanket claim that Mac is faster, quieter or longer-lasting on battery for every Resolve task. Windows gives you a wider range of NVIDIA laptop GPUs and chassis designs, with replaceable RAM or storage on selected models. Check that upgradeability on the actual platform: the ProArt P16 has onboard RAM, while the two Lenovo platforms above have memory slots. Dedicated VRAM figures and Apple unified-memory capacities are not interchangeable performance scores. Neither platform wins every codec. Before buying, check the exact camera format, bit depth and chroma subsampling against our [Resolve codec and format guide](https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/). Free and Studio editions can also differ in hardware-acceleration behavior, so a laptop recommendation cannot be separated from the software edition and source media. ## How Much Memory, Storage and VRAM Should You Buy? ### System memory For Windows, start at 32GB for a new Resolve machine. Move to 64GB if you regularly build substantial Fusion comps, run several creative applications together or keep machines for many years. For Apple Silicon, 24GB is a practical starting point for balanced work, while 48GB is the safer M5 Pro configuration for heavier projects. These are buying recommendations, not reworded official minimums. ### VRAM On Windows, 8GB is an entry point for controlled editing, and 12GB leaves more room for effects and higher-resolution media. Neither meets Studio 21.1's stated 16GB VRAM requirement for advanced AI tools. For that work, compare a configuration with at least 16GB VRAM, such as the RTX 5080 option in the Legion Pro 7 platform above. Capacity still isn't a speed score: power limits and cooling also affect sustained performance. ### Storage Choose at least 1TB for a primary editing laptop when possible. A 512GB model can work for a travel machine if projects and cache live on fast external storage, but it needs active space management. Keep source media, cache and backups planned as separate responsibilities. One large internal SSD is not a backup. ### Display and ports A wide-gamut, accurate internal display is valuable for editing and client review. It isn't automatically a controlled reference-monitoring path. Color-critical delivery still needs a calibrated workflow and, where the work demands it, dedicated video output hardware and an appropriate display. Check for the ports your storage, monitoring and power setup actually use rather than assuming a dongle will solve every path. ![MacBook Pro 16-inch MagSafe, three Thunderbolt 5 ports, headphones, SDXC reader and HDMI](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/macbook-pro-ports.webp) Annotated illustration based on [Apple's real 16-inch MacBook Pro port photos](https://www.apple.com/macbook-pro/specs/?ref=davinciresolveclub.com). Map your SSD, display, card reader and charging needs to the exact model before buying. ## Verify the Exact SKU Before Checkout 1. **Exact GPU:** confirm the full laptop GPU name, not “RTX 50 series.” 2. **VRAM:** verify capacity separately. RTX 5070 Laptop GPUs have both 8GB and 12GB variants; the name alone is not enough. 3. **System or unified memory:** check whether it's upgradeable. Apple memory and the ProArt P16's onboard memory can't be expanded later. 4. **SSD:** confirm capacity and whether a second drive slot exists if that matters to your media plan. 5. **Ports:** map external SSDs, displays, card readers, audio devices and power before choosing a chassis. 6. **Display:** confirm the actual panel in that part number. Resolution, refresh rate, gamut and brightness can vary within a family. If a retailer won't show the manufacturer part number or the exact GPU and memory configuration, buy elsewhere. The same family name can describe machines that belong in different workload tiers. For a used or refurbished laptop, add condition, battery health, warranty, return terms and required accessories to the comparison. A discounted older machine can be sensible if its exact hardware still meets the current software requirements and passes your project test. An old premium model is not automatically a better buy than a new midrange one. ## What Should You Buy at Each Performance Tier? **Lower-cost Windows target:** start the comparison around an RTX 5060 Laptop GPU with 8GB VRAM, 32GB RAM and a 1TB SSD. It is one useful configuration to price, not the cheapest machine that can run Resolve. Plan proxies and cache for difficult sources, and do not expect every temporal effect to play in real time. **Mainstream professional tier:** M5 Pro MacBook Pro with 24GB or 48GB, or an RTX 5070 Ti Windows laptop with 32GB or 64GB. This is the useful comparison for editors who earn money in Resolve and need broader workload coverage. **Heavy GPU tier:** if Studio 21.1's advanced AI tools are part of your Windows workflow, filter for at least 16GB VRAM before comparing performance. Larger-VRAM Windows GPUs or higher-memory M5 Max configurations may also make sense when repeated Fusion, noise-reduction or RAW jobs cost you time. Test a representative project first; extra hardware won't fix an unsuitable codec or workflow by itself. If your current machine feels slow, run through the causes in our [slow playback troubleshooting guide](https://davinciresolveclub.com/davinci-resolve-slow-playback/) before replacing it. Decode limitations, render cache, storage and project settings can imitate a hardware shortage. The [Hardware & Compatibility hub](https://davinciresolveclub.com/davinci-resolve-hardware-compatibility/) connects that diagnosis with the requirements, GPU and codec guides. Use it to establish what is limiting your current setup before deciding which component needs an upgrade. ## Test the Laptop Before the Return Window Closes Use a copy of a real project: play a difficult section with your usual grade, scrub the timeline, open a representative Fusion comp and export a short section in your actual delivery format. Record the Resolve version and Free or Studio edition, driver, power mode, whether the laptop is plugged in, and whether proxies or cache are active. Compare both laptops under the same conditions. If you also run PugetBench, match the **application version, benchmark version and preset**. Basic can run in Resolve Free; Standard and Extended require Studio. Puget's [benchmark guide](https://www.pugetsystems.com/pugetbench/creators/user-guide/?ref=davinciresolveclub.com) warns that mismatched versions and power profiles can explain different scores. A controlled benchmark and your own project answer different parts of the buying question. ## Frequently Asked Questions ### What is the best laptop for DaVinci Resolve in 2026? My first pick for mixed editing, color and delivery work is a 16-inch MacBook Pro with M5 Pro, 48GB memory and a 1TB SSD. For Windows editing, compare a ProArt P16 or Legion Pro 7i with an RTX 5070 Ti Laptop GPU, 12GB VRAM and at least 32GB RAM. If you need Studio 21.1 advanced AI tools on Windows, choose at least 16GB VRAM instead. The best fit still depends on your footage, effects, portability needs and local price. ### How much RAM does a DaVinci Resolve laptop need? For a new Windows laptop, 32GB is a sensible starting point; 64GB gives more room for substantial Fusion work or multitasking. On Apple Silicon, 24GB is a practical editing configuration and 48GB gives an M5 Pro more headroom. Studio 21.1 requires at least 32GB on Mac for background rendering and analysis. On Windows, background rendering requires both 32GB system RAM and 12GB VRAM; system RAM cannot replace dedicated VRAM. ### Is a MacBook Air good enough for DaVinci Resolve? A MacBook Air M5 with 24GB of memory can suit light editing, proxies, short-form projects and travel work. That configuration falls below Studio 21.1's 32GB Mac requirement for background rendering and analysis. Its fanless design is also a compromise for long exports or substantial Fusion work. More memory does not add cooling; compare a MacBook Pro for sustained heavy use. ### Is an RTX 5060 laptop enough for DaVinci Resolve? An RTX 5060 Laptop GPU with 8GB VRAM and 32GB system memory is a configuration to compare for controlled 4K editing, not a guarantee for every format or effects stack. Its 8GB VRAM falls below Studio 21.1's Windows requirements for advanced AI tools and background rendering. Proxies and cache can help editing, but they do not change those published hardware requirements. ### Is Mac or Windows better for DaVinci Resolve? Neither is better for every Resolve project. Compare a Mac's media-engine support and portability with the GPU, cooling and upgrade options in the exact Windows laptop. Check your source codecs, Free or Studio edition and required features. Apple unified memory is not directly interchangeable with a Windows laptop's system RAM plus dedicated VRAM. ### Can I use a laptop screen for professional color grading? A good laptop display is useful for editing and review, but its gamut or HDR badge doesn't make it a controlled reference path. Color-critical delivery requires a calibrated workflow and may require dedicated video output hardware plus an appropriate reference display. ### Can an older laptop run DaVinci Resolve 21? It may run Resolve 21.1 if it meets the current OS, memory, GPU and driver requirements. The Mac readme requires Apple Silicon and macOS 15 or later, so an older Intel Mac is not on that supported baseline. Meeting minimums does not guarantee smooth playback; test your actual codecs and effects before buying a used laptop. ### DaVinci Resolve vs VEGAS Pro in 2026 URL: https://davinciresolveclub.com/davinci-resolve-vs-vegas-pro/ Last updated: 2026-09-07T16:18:50.000Z **Quick answer:** choose **VEGAS Pro 2026** if you work on Windows 11 and prefer trimming, effects and audio close to one flexible timeline. Choose **DaVinci Resolve 21** if you want a free editor without a trial deadline, native Mac or Linux support, or dedicated color, Fusion and Fairlight workspaces. The deciding test is a representative project with a revision, not the length of either feature list. Comparing an old copy of Sony VEGAS with today's Resolve misses a major change: Boris FX acquired VEGAS from MAGIX in March 2026 and released VEGAS Pro 2026\. The account system, bundles and hardware requirements have changed. Advice for VEGAS 22 or 23 may still help an existing owner, but it should not decide a new 2026 purchase. I checked the developers' current documentation on **September 7, 2026**. The recommendations below are editorial judgments about workflow, not a timed head-to-head benchmark. Use the same footage, title, audio repair, color correction and export in both apps before buying. The VEGAS price table is explicitly dated launch pricing because I could not confirm a selected current offer in the public store. ## DaVinci Resolve vs VEGAS Pro at a glance | Decision | Practical difference | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Best first fit** | **VEGAS Pro 2026:** solo Windows editing with event-level control.**Resolve 21:** end-to-end post-production that can grow into a team workflow. | | **Free option** | **VEGAS:** full-featured 15-day trial, not a free edition without a trial deadline.**Resolve:** capable Free edition with no normal export watermark within its limits. | | **Paid model** | **VEGAS:** monthly, annual and selected perpetual tiers.**Resolve:** Studio is a one-time purchase. | | **Operating systems** | **VEGAS:** current official requirement is Windows 11.**Resolve:** Windows, macOS and Linux. | | **Editing model** | **VEGAS:** most work stays close to one customizable timeline.**Resolve:** Cut/Edit, Fusion, Color, Fairlight and Deliver have distinct jobs. | | **Color, VFX and audio** | **VEGAS:** useful timeline-integrated tools and OFX expansion.**Resolve:** deeper dedicated finishing environments. | | **Existing project move** | **VEGAS:** export documented Resolve XML and archive the media.**Resolve:** conform the XML, rebuild unsupported work and compare a reference export. | This is not a beginner-versus-professional split. VEGAS has multicam editing, planar tracking, compositing, color controls, audio buses and third-party OFX support. Resolve also has a conventional Edit page; you do not have to learn every workspace to make a first cut. The useful comparison is how each app organizes the work you actually need. Still deciding which editors belong on your shortlist? The [DaVinci Resolve comparisons hub](https://davinciresolveclub.com/davinci-resolve-comparisons/) covers Premiere Pro, Final Cut Pro, CapCut and other alternatives, alongside the separate Free-versus-Studio decision. ## What changed from Sony VEGAS to VEGAS Pro 2026? The name persists in searches because Sony sold the software years ago and many editors learned on those versions. The current ownership change is newer and more important: the [Boris FX acquisition announcement](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro?ref=davinciresolveclub.com) is dated March 30, 2026 and covers VEGAS Pro, Sound Forge and Acid Pro. VEGAS Pro 23 and earlier remain legacy MAGIX products; VEGAS Pro 2026 is the first Boris FX release. That distinction matters when you compare screenshots, license advice or troubleshooting. An old activation-key guide, MAGIX Hub tutorial or VEGAS 22 price doesn't describe the current Boris FX account flow and 2026 editions. Search with the exact version before applying a fix. ## Price: Resolve starts free; VEGAS now has three tiers Blackmagic's [Resolve product page](https://www.blackmagicdesign.com/products/davinciresolve?ref=davinciresolveclub.com) offers a Free edition for Windows, macOS and Linux. Normal exports do not carry a built-in watermark, but Studio-only effects and unsupported formats can still interrupt a free workflow. Free output is limited to **Ultra HD 3840 × 2160 at up to 60 fps**. The [Resolve cost guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) explains when paying for Studio makes sense. The US [Resolve Studio page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) showed **$295** when checked. That is a desktop software purchase, not a monthly editor subscription. Studio adds tools such as advanced noise reduction, Magic Mask and additional Resolve FX. Blackmagic Cloud hosting or storage can carry separate charges; buying the editor does not mean every associated service is free. VEGAS offers three editions. The [current plan comparison](https://www.vegascreativesoftware.com/vegas-pro/plans-pricing/?ref=davinciresolveclub.com) identifies their included tools, while Boris FX's March 30 launch announcement provides the US list prices below. These are **historical launch prices, not a verified September checkout quote**. Check the selected edition, billing period, renewal total, tax and upgrade eligibility before paying. | Plan | US launch list — March 30, 2026 | | ---------------------- | ----------------------------------------------------------------------- | | **VEGAS Pro** | $99.95/year or $219.95 for a perpetual license. | | **VEGAS Pro Plus** | $149.95/year or $299.95 for a perpetual license. | | **VEGAS Pro Ultimate** | $199.95/year; no perpetual option in the launch table. | | **VEGAS trial** | Current trial: 15 days of Ultimate on Windows; no credit card required. | The tier differences matter more than an introductory discount. The current feature table puts Mocha VEGAS, Particle Illusion, Sound Forge and CrumplePop VST tools in Plus. Ultimate adds Mocha Pro, Optics and Continuum VFX for VEGAS, among other tools. The launch licensing table offers perpetual Pro and Plus, but Ultimate as a subscription. Confirm those choices in the actual offer; do not assume a VEGAS plug-in bundle also licenses every other host. If you only need an editor, Resolve Free has the lower entry cost. Paying for VEGAS can still make sense if its controls fit your established workflow or its bundle replaces tools you would otherwise buy. The [15-day Ultimate trial](https://vfx.borisfx.com/vegas-pro-free-trial?ref=davinciresolveclub.com) lets you test that fit without a credit card. Remember that testing Ultimate does not mean every feature will remain available if you buy Pro. ## Editing workflow: timeline events versus dedicated pages VEGAS is tactile. Drop media on the timeline, trim an event, overlap two events for a crossfade, apply an effect at event or track level, adjust audio and keep moving. Its windows are customizable, and the interface doesn't force the edit through a formal page sequence. The [VEGAS feature guide](https://www.vegascreativesoftware.com/vegas-pro/features/?ref=davinciresolveclub.com) documents event editing, track compositing, OFX keyframes, 3D plane positioning, planar tracking, multicam editing and input buses. If you already work comfortably with its fades, envelopes and shortcuts, that familiarity is a reason to test carefully before switching—not evidence that another editor is inherently slower. ![VEGAS timeline clip events, GL Transition and audio waveform identified](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/vegas-timeline-events-reference.webp) Annotated illustration based on the [VEGAS developer interface reference](https://www.vegascreativesoftware.com/vegas-pro/features/?ref=davinciresolveclub.com). The markers identify existing timeline regions; this is not our timed test or an exact-build capture. Resolve gives different jobs their own workspaces: Cut and Edit for editing, Fusion for node-based compositing, Color for grading, Fairlight for audio and Deliver for output. You can start on Edit and open the specialist pages as needed. There is no requirement to push every simple video through all of them. Neither layout wins by itself. During your trial, revise a title, replace a shot, change the mix and adjust a grade after the first export. Which changes are straightforward, and which send you hunting for a control? That is a more useful answer than assuming VEGAS is always easier or Resolve always takes longer to learn. If Resolve feels slow only because the keys are unfamiliar, start with the [Resolve keyboard shortcuts guide](https://davinciresolveclub.com/davinci-resolve-keyboard-shortcuts-guide/). Rebuild the five VEGAS commands you use most before judging the whole interface. ## Color, effects and audio: convenience versus finishing depth VEGAS can grade within the editing environment using curves, wheels, LUTs and scopes. Its **Camera LUT** and **Look LUT** sections separate the input transform from a creative look. Match the camera transform to the actual footage; the example strengths in the illustration are not recommended settings. VEGAS also supports OFX animation, planar tracking, track compositing and audio mixing with buses. ![VEGAS Camera LUT and Look LUT controls separate an input transform from a creative look](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/vegas-camera-look-lut-reference.webp) Annotated [developer LUT reference](https://www.vegascreativesoftware.com/vegas-pro/features/?ref=davinciresolveclub.com). The selected LUTs and strength values are examples, not settings to copy to every camera clip. Resolve's advantage is not an automatic “better image” button. Its Color page provides node-based corrections, tracked Power Windows and color-management tools; Fusion provides a dedicated node compositor. Fairlight gives audio its own workspace for detailed editing and mixing. Those separate environments are useful when a grade, composite or mix needs more organization than your first rough cut. A careful VEGAS grade can look better than a careless Resolve grade. Choose the controls you need to diagnose a problem and repeat a result across shots. If VEGAS already gives you those controls, a switch needs a practical benefit beyond the reputation of Resolve's Color page. ## AI and bundles: check which features require a subscription The [VEGAS Pro 2026 release page](https://www.vegascreativesoftware.com/vegas-pro/whats-new/?ref=davinciresolveclub.com) lists the Continuum Title Pack, improved AI Z-Depth and NVIDIA Blackwell acceleration for AVC and HEVC 4:2:2 media. That acceleration depends on compatible hardware and footage; it is not a claim that every render becomes faster. Boris FX also confirms [ProRes RAW support in its 2026 launch announcement](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro?ref=davinciresolveclub.com). Fully offline speech-to-text and text-to-speech are **subscription-only** in VEGAS Pro 2026; Storyblocks access also requires a subscription. The release describes the two offline speech functions as unlimited, not cloud-credit operations. Do not extend that promise to every AI tool, or assume that buying a perpetual editor includes the subscription services. For captions, VEGAS can generate titles on the timeline or export a separate SRT file—choose the delivery format you actually need. ![VEGAS Generate Titles and Export SRT controls for two caption delivery options](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/vegas-captions-srt-reference.webp) Annotated illustration based on the [Boris FX VEGAS Pro 2026 press interface](https://borisfx.com/company/press-and-media/?ref=davinciresolveclub.com). Generate Titles creates timeline titles; Export SRT creates a separate caption file. Offline speech-to-text requires a subscription. Resolve 21 also uses AI across editing, transcription, masking, audio and analysis, with important tools reserved for Studio. Compare the repeated operation, not the number of AI labels. Write down the three actions you perform every month, then verify edition, local/cloud processing and renewal cost for each. ## Hardware: current VEGAS is Windows 11 only The current [VEGAS requirements table](https://www.vegascreativesoftware.com/vegas-pro/system-requirements/?ref=davinciresolveclub.com) lists Windows 11, 16 GB RAM and 8 GB VRAM in its minimum column. Its 4K column recommends 32 GB RAM and 8 GB VRAM; its AI column recommends 32 GB RAM and 16 GB VRAM. These are published requirements, not a guarantee for every GPU with that memory capacity. They also do not support the assumption that current VEGAS is a lightweight answer for any old PC. Resolve runs on Windows, macOS and Linux, but its behavior also depends on edition, codec, GPU, VRAM, effects and operating system. The [Resolve 21 system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) explains those interactions. A Mac or Linux requirement decides this comparison immediately; on Windows, the footage must decide. ### Test real editing performance before paying or switching 1. Use a real camera or screen-recording file with the codec and frame rate you deliver every week. 2. Build the same 60-second timeline, title, transition, speed change, color correction and dialogue cleanup. 3. Scrub, trim and revise for ten minutes before creating proxies. 4. Add one effect or title from the package you expect to use, not a synthetic benchmark. 5. Export the same delivery codec and record dropped frames, render time, errors and visible differences. Record the software build, GPU driver, source codec, proxy/cache settings and export settings alongside the result. That makes the comparison interpretable. A render time from someone else's different footage, GPU or effect stack is not a reliable prediction for your project. ## Which editor should you choose? ### Choose VEGAS Pro when the Windows timeline is the advantage VEGAS is worth considering if you prefer event-level Windows editing and want video, fades, effects and audio close together. That can suit YouTube, event videos, music videos, courses and corporate work. The advantage is a layout and toolset that fit your habits—not a promise that these genres always finish faster in VEGAS. The Boris FX ownership also makes Plus and Ultimate more interesting for editors who need Mocha, Continuum, Optics, Particle Illusion, CrumplePop or Sound Forge. Price the actual bundle against the actual tools. Don't buy an edition because the word “Ultimate” sounds safer. ### Choose Resolve when the project must cross departments or platforms I would lean toward Resolve when dedicated color work, Fusion compositing, audio post or cross-platform collaboration is central to the job. Free already includes multi-user collaboration; Studio is not required simply because another editor joins. Check any hosted-project or storage charges separately. Both the free entry point and the desktop Studio purchase are useful when budgeting, but neither removes hardware, training or service costs. If your decision is really about a professional NLE ecosystem, compare [Resolve vs Premiere Pro](https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/). If the machine is a Mac and you prefer a one-time editor, use [Resolve vs Final Cut Pro](https://davinciresolveclub.com/davinci-resolve-vs-final-cut-pro/). VEGAS is a Windows-only branch. ### Finish a revision before committing Install Resolve Free and the 15-day VEGAS Ultimate trial. Finish the same small project, then make a client-style revision: swap a shot, retime a clip, change a title, repair a noisy line, match a new camera angle and export again. The second pass exposes friction that a first-impression review misses. If Resolve wins the test but feels foreign, the [Resolve beginner tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) provides a complete first-project route. Familiarity is a real production advantage, but it shouldn't be confused with a permanent product limit. ## Move a VEGAS project to DaVinci Resolve without pretending it is native A `.veg` file doesn't open in Resolve. The documented interchange starting point is **Final Cut Pro 7/DaVinci Resolve XML**, which the current VEGAS supported-formats table lists for export. That is better than flattening the entire job, but it's still a conform, not a native project conversion. 1. Duplicate the VEGAS project and use the documented [Vegas Project Archive](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/3-projects/archivingprojects.htm?ref=davinciresolveclub.com) with the required media. Include nested projects, proxies or BRAW companion files when the job depends on them. 2. Export a high-quality reference movie with matching resolution, frame rate and visible timecode if practical. 3. Export Final Cut Pro 7/DaVinci Resolve XML from VEGAS. 4. Create the Resolve project at the correct frame rate, import the XML and relink original media. 5. Compare every cut, dissolve, speed change, crop and audio event against the reference. 6. Rebuild VEGAS generators, OFX, track compositing, envelopes, titles and audio routing unless a test proves they transferred correctly. Don't use the VEGAS text EDL as a full-fidelity shortcut. The [current VEGAS EDL documentation](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/3-projects/edl.htm?ref=davinciresolveclub.com) says its EDL isn't intended for project interchange, can place converted events on one track and replaces transitions with crossfades. Use it only when that simplification is acceptable. Keep VEGAS, the archive and the reference export until the Resolve master passes a shot-by-shot and audio comparison. Deleting the source environment before conform approval turns a manageable migration into archaeology. ## DaVinci Resolve vs VEGAS Pro FAQ ### Is DaVinci Resolve better than VEGAS Pro? Resolve is the stronger fit if you need a free edition without a trial deadline, native Mac or Linux support, or dedicated color, Fusion and Fairlight workspaces. VEGAS may fit a Windows editor who prefers event-level controls and its Boris FX bundles. Finish a representative project and a revision before choosing; neither wins every task. ### Is VEGAS Pro still Sony VEGAS? No. The historical name remains common in searches, but Boris FX acquired VEGAS Pro from MAGIX on March 30, 2026\. VEGAS Pro 23 and earlier remain legacy MAGIX products; VEGAS Pro 2026 is the current Boris FX release. ### Is VEGAS Pro free like DaVinci Resolve? No. VEGAS offers a full-featured 15-day Ultimate trial, not an ongoing free edition. Resolve Free can complete projects without a normal export watermark when its format and feature limits fit the job. Free output supports up to Ultra HD 3840 × 2160 at 60 fps; Studio-only effects can still require an upgrade. ### Does VEGAS Pro work on Mac or Linux? The current VEGAS Pro 2026 system page lists Windows 11\. It does not list macOS or Linux. DaVinci Resolve supports Windows, macOS and Linux, so a current Mac/Linux requirement ends this comparison in Resolve's favor. ### Which is easier for beginners, VEGAS Pro or DaVinci Resolve? VEGAS may feel more familiar if you want event-level controls near one Windows timeline. Resolve has more specialist workspaces, but a beginner can start on Edit and learn the others as needed. Neither layout guarantees a faster first edit. Try the same project and a revision in both. ### Can a VEGAS project open in DaVinci Resolve? A native `.veg` file doesn't open in Resolve. VEGAS Pro 2026 documents Final Cut Pro 7/DaVinci Resolve XML export. Archive the project and media, export a reference, import the XML into Resolve and rebuild anything that doesn't survive the conform. ### Is VEGAS Pro 2026 a one-time purchase? Boris FX's launch table offers perpetual licenses for VEGAS Pro and Pro Plus, alongside subscriptions; Ultimate is subscription-only in that table. Current licensing support confirms subscription and perpetual options remain available, but verify the selected tier and offer before purchase. Offline speech-to-text, text-to-speech and Storyblocks are subscription-only features. My choice would come down to the next project: VEGAS if its Windows event controls and included tools already match the work; Resolve if the free edition, cross-platform projects or specialist finishing workspaces solve a concrete need. Keep your existing editor and project archive until the replacement has passed a complete picture-and-audio check. ### DaVinci Resolve vs Filmora in 2026 URL: https://davinciresolveclub.com/davinci-resolve-vs-filmora/ Last updated: 2026-09-07T15:12:07.000Z **Quick answer:** choose **Filmora 15** if ready-made titles, templates and guided creator tools fit the videos you publish. Choose **DaVinci Resolve 21** if you need normal watermark-free exports from a free editor, deeper color and audio work, Fusion compositing or a project that can move into professional finishing. Try your own footage before paying for either. The cheapest editor and the easiest first edit are different decisions. Filmora lets you edit for free, but its free exports carry a watermark. Resolve Free can produce a finished video without that watermark, provided your footage and effects fit its limits. You do not have to learn every Resolve page to cut a short video. This desktop comparison checks the developers' documentation and displayed US plans on **September 7, 2026**. The recommendations are editorial judgments about workflow, not results from a timed head-to-head benchmark. Prices vary by platform, region and checkout offer; use a representative project to make the final choice. ## DaVinci Resolve vs Filmora at a glance | Decision | Practical difference | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Best first fit** | **Filmora 15:** template-led creator edits, stock assets and guided tools.**Resolve 21:** editing that can grow into color, VFX, audio, collaboration and finishing. | | **Free export** | **Filmora 15:** available, but carries a Filmora watermark.**Resolve 21:** no built-in watermark for normal exports within Free-edition limits. | | **Paid model** | **Filmora 15:** subscription or perpetual license tied to a major version.**Resolve 21:** Studio is a one-time purchase. | | **Learning curve** | **Filmora 15:** integrated creator controls beside a conventional timeline.**Resolve 21:** specialist workspaces to learn as the project needs them. | | **Templates and stock** | **Filmora 15:** central part of the workflow.**Resolve 21:** available, but not the core reason to choose Resolve. | | **Color, VFX and audio** | **Filmora 15:** useful integrated creator tools.**Resolve 21:** dedicated Color, Fusion and Fairlight environments. | | **Desktop platforms** | **Filmora 15:** Windows and macOS.**Resolve 21:** Windows, macOS and Linux. | | **Project handoff** | **Filmora 15:** best inside Filmora's own project system.**Resolve 21:** built for broader post-production and interchange workflows. | ![Filmora timeline selection and Color menu leading to Color Wheels](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/filmora-color-controls-reference.webp) Annotated [Wondershare interface reference](https://filmora.wondershare.com/guide/color-wheels.html?ref=davinciresolveclub.com): clip controls sit beside the timeline. The source does not identify an exact build; this is not our timed comparison. That table is a starting point, not a ranking. Filmora has moved beyond basic trimming: version 15 adds source and timeline preview, dual timelines, imported subprojects, a Pen tool and new AI features. Resolve has quick workflows too, but its advantage appears when the same project needs a serious grade, a complex composite, a controlled mix or a reliable handoff. The [DaVinci Resolve comparisons hub](https://davinciresolveclub.com/davinci-resolve-comparisons/) connects this decision to CapCut, Premiere Pro, Final Cut Pro and Resolve Free versus Studio. Use this page only for the Filmora decision. ## Price: free, subscription and “perpetual” mean different things Blackmagic's [current Resolve product page](https://www.blackmagicdesign.com/products/davinciresolve?ref=davinciresolveclub.com) lists DaVinci Resolve Free at $0\. It works with virtually all 8-bit formats up to Ultra HD 3840 × 2160 at 60 fps, subject to the documented format and platform limits. Normal exports don't receive a Resolve watermark. The separate [Free vs Studio guide](https://davinciresolveclub.com/davinci-resolve-free-version-features/) maps the features that are actually locked. On the observed US page, [DaVinci Resolve Studio](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) was $295 as a one-time purchase. Studio raises the format and resolution ceiling and adds the DaVinci AI Neural Engine, extra Resolve FX, advanced noise reduction, Magic Mask and other professional tools. The [Resolve cost guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) covers license details and the checkout traps that a headline price misses. The Windows offer on Filmora's [official pricing page](https://filmora.wondershare.com/shop/buy/buy-video-editor.html?ref=davinciresolveclub.com) showed **Basic at US$49.99/year**, **Advanced at US$59.99/year** and **Perpetual at US$79.99 once**. Basic matters if you mainly want paid export rights rather than Advanced's monthly AI allowance. These are observed offer prices, not a quote for every Mac license or a guaranteed renewal rate. Check your operating system, renewal total, tax and optional Creative Assets subscription in the final cart. ### Before you pay for Filmora First, Filmora Free is usable for editing, but its exported video carries a watermark. Resolve Free is the stronger zero-dollar option when its codec, resolution and feature limits fit the project. Second, Filmora Perpetual means continued use of the purchased major version, not free upgrades forever. The current page says the plan receives Filmora 15 updates only. Subscription plans include future version upgrades while the subscription remains active. Advanced showed **1,000 AI credits per month**; Perpetual showed **1,000 one-time credits**. The subscription allocation resets every 30 days, and unused credits from the previous period are reclaimed. Basic does not include the same monthly allowance. Do not assume all AI tools become unlimited after buying the editor: the pricing FAQ's normal-speed entitlement refers to eligible legacy users, not every new plan. Treat the Creative Assets trial as a separate checkout decision: the observed offer included a seven-day trial that renews as an add-on. Check whether each selected stock item or effect needs that subscription, and whether its license covers your intended use. Paying for the editor does not automatically grant every asset or a team-wide license. ## Editing workflow: integrated controls or specialist workspaces? Filmora keeps media, titles, effects and many clip controls close to a conventional timeline. That layout may be easier to approach if you mainly want to arrange clips, add a title, clean dialogue and publish. Version 15 also has source/timeline previews and dual-timeline editing; it is not limited to a single simplified preview window. A ready-made title helps when it already matches the result you need. Include a revision in your trial: change the aspect ratio, match two camera shots, adjust dialogue and replace the title. That tells you more about the workflow than getting one preset onto the timeline. Resolve gives editing, compositing, color, audio and delivery their own workspaces. Start on Edit; move to Color, Fusion or Fairlight when the job needs them. The tradeoff is more systems to learn as your work expands, rather than a requirement to master them all before the first export. If the Resolve interface is the only thing stopping you, use the [Resolve beginner tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) to finish one short video before deciding. Twenty minutes of clicking around isn't a fair comparison with an editor you already know. ## Filmora 15 is not a toy, but Resolve has the deeper finishing path Wondershare's [Filmora 15 feature guide](https://filmora.wondershare.com/guide/latest-versions-and-features.html?ref=davinciresolveclub.com) documents dual-timeline editing, imported subprojects, source/timeline preview, animated charts and a Pen tool. Its wider [Filmora guide](https://filmora.wondershare.com/guide/?ref=davinciresolveclub.com) includes multicamera editing, compound clips, proxies, keyframes, masks, color controls, scopes, a mixer, EQ, denoise and ducking. Its [LUT documentation](https://filmora.wondershare.com/3d-lut.html?ref=davinciresolveclub.com) also confirms export of compatible color adjustments as a `.cube` file. A LUT transfers a color transform, not the timeline or every effect. That is enough for a large amount of YouTube, course, product and social work. A beginner doesn't outgrow Filmora merely because they learn keyframes or start using scopes. ![Resolve Color node tree separates primary and secondary corrections from effects](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/resolve-color-nodes-reference.webp) Annotated [Blackmagic Design Color example](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com). The preserved node graph illustrates separate corrections and effects, not a measured quality advantage over Filmora. ### Where Resolve separates itself Resolve's Color page combines node trees, tracked Power Windows, groups, versions, galleries, color management and professional monitoring. Those tools help keep corrections consistent across a sequence and separate a shared look from shot-specific fixes. Filmora has capable color controls too; Resolve's advantage here is how much of the finishing workflow you can organize in one dedicated workspace. Fusion gives Resolve a node-based compositor inside the same project. Fairlight supplies buses, automation, routing, meters, plug-ins and delivery tools for mixes that go beyond balancing a voiceover against music. Filmora's integrated tools are easier to reach; Resolve's architecture handles more demanding revisions. This distinction doesn't guarantee a prettier export. A bad color pipeline in Resolve can look worse than a careful Filmora grade. The advantage is control, diagnosis and repeatability, not magic image quality. ## AI: compare the repeated task, not the feature count Filmora packages many AI actions around creator output: short-form extraction, generation, enhancement, text and speech tools, removal and translation. That can be the shorter route when the weekly task is “turn this talking-head video into several social cuts.” Some of those actions consume credits or use different processing tiers, so the workflow has an operating cost even when the editor license is paid. Resolve 21 also has AI-assisted editing, audio, masking and analysis, with important features reserved for Studio. Its strength is how those tools feed the rest of the post pipeline. A mask can continue into a grade or composite; dialogue work can continue inside Fairlight; transcription can drive an edit. Write down the three AI operations you'll repeat every month. Then check whether each is included, credit-metered, local, cloud-processed or Studio-only. “More AI” isn't a decision until the recurring task and recurring cost are named. ## Performance: test your codec and effect stack Filmora is often recommended for modest computers and Resolve is often called demanding. Both statements can be directionally useful and still fail on your footage. H.265 10-bit camera files, screen recordings with variable frame rate, noise reduction, generated media, multicam and third-party effects stress different parts of a system. Use the same 60-second sample in both editors: 1. Import the camera file you actually use, not a downloaded demo. 2. Build the same timeline resolution and frame rate. 3. Add one title, one speed change, one color correction and the audio cleanup you expect. 4. Scrub, play and edit for ten minutes before generating proxies. 5. Export the same H.264 or H.265 delivery file and record time, failures and visible differences. The [Resolve 21 system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) explains why operating system, codec, GPU memory and edition matter together. Don't buy an editor because somebody else's gaming PC exported one sample faster. ## Which editor should you choose? ### Choose Filmora when publishing speed is the product Filmora is the practical choice when you want a guided timeline, ready-made titles, stock assets and AI-assisted social output in one creator-focused environment. It fits solo YouTube channels, course videos, family edits and small marketing jobs where the template or preset is already close to the approved result. If your shortlist also includes a phone-first social workflow, read [DaVinci Resolve vs CapCut](https://davinciresolveclub.com/davinci-resolve-vs-capcut/). This comparison concerns Filmora desktop; do not assume a desktop license, mobile app and cloud service have identical features or entitlements. ### Choose Resolve when the project must grow Resolve is the better long-term choice when you expect camera-format variety, controlled color, motion graphics, complex audio, multi-user work or professional delivery. Its Free edition makes that path unusually accessible, provided the footage and hardware fit its limits. Resolve Free already supports multi-user collaboration. Studio is not required merely because another editor joins the project; hosted project libraries, storage and other services may have their own charges. Choose the software edition and the shared-project service separately. If your real alternative is an established professional subscription workflow, the more useful next comparison is [DaVinci Resolve vs Premiere Pro](https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/). Filmora and Premiere solve different collaboration, ecosystem and interchange problems. ### Choose neither until one controlled test is complete Install both, finish the same short project and count the actions that mattered: media organization, rough cut, captions, title, audio cleanup, color match, revision and export. Keep the editor that removes friction from the tasks you actually repeat. A long feature list can't tell you which interface makes you miss a deadline. ## Switch from Filmora to DaVinci Resolve without losing the project Wondershare's [project guide](https://filmora.wondershare.com/guide/create-a-project.html?ref=davinciresolveclub.com) says an ordinary `.wfp` stores editing decisions and references to source media; it is recognized and opened by Filmora. The checked project and export documentation does not establish a direct Resolve timeline-transfer route. Archiving is a backup step, not a conversion. Keep Filmora and the original project until the replacement has been checked. 1. Duplicate the Filmora project, then follow [File > Archive Project](https://filmora.wondershare.com/guide/move-projects.html?ref=davinciresolveclub.com) to package it with its referenced source files. Open the archive in Filmora to confirm it is usable. 2. Export a high-quality reference movie with the original timeline's resolution and frame rate. Keep it separate from the source media. 3. Preserve the original video, audio and permitted graphics. Export useful isolated audio where your setup allows it; plan to rebuild titles or effects that cannot be transferred. Do not assume transparent-title export is available in every configuration. 4. Create a Resolve project and set the intended timeline frame rate before importing media. 5. Rebuild from original media when future revisions matter. Compare every cut, crop, speed change, title and mix decision with the reference movie. 6. Keep the Filmora archive until the Resolve export passes your visual and audio comparison. A matching picture alone does not confirm the mix or the underlying editable media. ![Filmora File menu with Archive Project for preserving the project and source media](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/filmora-archive-project-reference.webp) Annotated [Wondershare archive reference](https://filmora.wondershare.com/guide/move-projects.html?ref=davinciresolveclub.com). Archive Project keeps a Filmora project with its sources; it does not create a Resolve timeline. For a simple locked edit, a high-quality master may be enough for color or delivery. For an edit that will keep changing, rebuilding from source media is slower but safer than cutting a compressed master into pieces and pretending the original timeline transferred. ## DaVinci Resolve vs Filmora FAQ ### Is DaVinci Resolve better than Filmora? Resolve is the stronger fit for dedicated color work, Fusion compositing, Fairlight mixing and post-production handoff. Filmora may fit better when its templates, stock assets and integrated creator controls already match the job. Choose by completing a representative project, not by assuming either editor wins every task. ### Which is easier for beginners, Filmora or DaVinci Resolve? Filmora may be easier to approach if its templates and integrated clip controls match the job. Resolve has more specialist workspaces, but beginners can start on Edit and learn Color, Fusion or Fairlight as needed. Finish the same short project in both; neither interface guarantees a faster first edit for everyone. ### Is DaVinci Resolve Free better than Filmora Free? Resolve Free is the stronger choice when you need a finished export without a built-in watermark and its codec, resolution and feature limits fit the job. Filmora Free allows editing and export, but the official plan page says exported videos carry a Filmora watermark. ### Is Filmora 15 good enough for YouTube? Yes, for many channels. Filmora 15 provides a multitrack timeline, titles, templates, stock assets, color and audio controls, captions and creator-focused AI tools. Resolve becomes more attractive when the channel needs deeper grading, compositing, mixing, collaboration or demanding delivery formats. ### Does Filmora have color grading? Yes. Filmora documents HSL, curves, color wheels and scopes, plus export of compatible adjustments as a .cube LUT. Resolve offers a deeper dedicated architecture for nodes, shot matching, color management and finishing. A Filmora LUT is not a transfer of its complete edit or every effect. ### Can Filmora projects open in DaVinci Resolve? No direct opening route is documented in the official guides checked for this comparison. Wondershare says `.wfp` files can only be recognized by Filmora. Archive the Filmora project and sources, export a reference, then rebuild or conform the work in Resolve without assuming effects and titles will translate. ### Is Filmora a one-time purchase? Filmora offers a Perpetual plan as well as subscriptions. The official plan page says Perpetual covers continued use and updates within the purchased major version, currently Filmora 15, but not future major-version upgrades. Prices and bundled trials can change, so verify the checkout terms. My choice would be Filmora for a template-led creator workflow that already fits the brief, and Resolve for projects that need more control over color, compositing, audio or handoff. If both fit, use the free editions to test the same edit before buying a license. Filmora's free watermark and Resolve's edition limits belong in that test, not as surprises at delivery. ### DaVinci Resolve Fusion Macros and Templates: Build, Save, Install URL: https://davinciresolveclub.com/davinci-resolve-fusion-macros-templates/ Last updated: 2026-09-05T21:38:36.000Z **Quick answer:** build and test the node tree, select the nodes that belong in the reusable item, then right-click one and choose **Macro > Create Macro**. In Resolve 21, choose the controls to expose, keep the necessary image connections, and arrange the live Inspector Preview. Test with **Copy Macro**, then save as a Macro, Group or Edit Template. The right save choice depends on whether you need a Fusion node, editable internals or an item in the Cut/Edit Effects Library. A saved file and an installed template are not the same thing. A custom Fusion macro will not automatically appear under Edit-page titles. If a valid `.setting` file seems to vanish, check its destination before rebuilding the effect. ## Choose Macro, Group or Edit Template before you build | Save choice | Best use and limit | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Macro** | Use one custom node inside Fusion with a restricted set of controls. The internal node tree is intentionally hidden behind that tool. | | **Group** | Collapse a reusable setup while keeping its individual nodes expandable. Choose this when another compositor may need to repair or redesign the internals. | | **Edit Template** | Drag a reusable Title, Generator, Effect, or Transition from the Cut/Edit Effects Library. It exposes selected controls in the Inspector instead of asking the editor to work in Fusion. | If you're still learning what each node does, start with the [Fusion beginner workflow](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/). The macro process assumes the comp already works. Packaging a broken comp only makes the failure easier to repeat. ## Build a clean source comp Make the smallest node tree that produces the finished result. Name the important nodes, remove abandoned branches, and test different clips, frame sizes, durations, and aspect ratios when those inputs can change. A reusable lower third shouldn't be approved after one name at one duration. A reusable effect should survive a different source clip without relying on a hidden mask or a fixed frame number. The nodes you include depend on the template category. In Blackmagic's title example, select the creative nodes but exclude **MediaIn and MediaOut**. Its transition example includes both MediaIn nodes and MediaOut; its generator example includes MediaOut; its simple effect example includes MediaIn and MediaOut. Do not apply the title rule to every template. Start from an existing working template of the category you need when the boundary is unclear. For a normal custom Fusion tool, check its image input and output before packaging. Keep the source comp as an editable reference. If the new macro has no usable image connection or produces a blank frame, compare it with that source before changing the design. ## Create a Fusion macro in Resolve 21 1. Open the clip or Fusion Composition on the **Fusion** page. 2. Build the complete effect and confirm the final branch reaches MediaOut. 3. Select only the nodes that belong inside the reusable item. 4. Right-click one selected node. 5. Choose **Macro > Create Macro**. 6. Give the macro a short, searchable name that will still make sense in six months. ![Fusion node context menu identifying Macro and Create Macro after selecting nodes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/fusion-macro-create-menu.webp) Annotated [Resolve 17 menu reference by Hitsugi Yukana](https://assets.st-note.com/img/1660472638558-qMM8DtLpcx.png?width=1200&ref=davinciresolveclub.com). The same command is documented in Resolve 21; the selected nodes still depend on the template category. Blackmagic's [Resolve 21 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) documents the redesigned Macro Editor and its live Inspector Preview. That preview is more than decoration: it lets you judge what an editor will actually see while you're still choosing and organizing parameters. ## Expose fewer controls than the node tree contains The **Export** column includes parameters and input connections. Do not uncheck everything indiscriminately: the macro still needs the image inputs and output appropriate to its job. Beyond those connections, expose only the controls the next editor needs. For a lower third, that might be Styled Text, font, size, text color, background opacity and position. A title does not need every Text+ setting in its Inspector. Rename controls for the person using the template. **Background Opacity** is clearer than an internal channel name; **Title Position** distinguishes a title transform from other transforms in the comp. Set defaults and ranges for that specific parameter. A narrow opacity range can make sense, but do not constrain a position control so tightly that the title cannot reach the edge of the frame. ![Resolve 21 Macro Editor Inspector Preview with Add Page, text input and size controls annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/fusion-macro-preview21.webp) Annotated [Blackmagic Design Resolve 21 interface reference](https://www.blackmagicdesign.com/products/davinciresolve/whatsnew?ref=davinciresolveclub.com). This is the preview side of the editor, not the Export column or a measured result from our own test. ## Organize the live Inspector Preview In Resolve 21's preview, drag controls into the order you want, move them between pages, or add and rename pages. Separator, Spacer and Nest organize the Inspector without editing a settings file by hand. A Nest is a collapsible section; use it for settings people rarely touch. - Keep the first page for the settings changed on almost every use. - Put related controls together: text, layout, color, timing, or advanced repair. - Use one separator when two groups would otherwise run together. - Use a nest for genuinely optional detail, not for the core controls the editor needs immediately. - Leave a new page for a real second task, not because the first page looks busy. For title templates, test the same Inspector with a short name, a long name, and a two-line name. If you need the full Text+ workflow before packaging it, use the [Resolve text and Text+ guide](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/). ## Test the macro before saving it Open the Macro Editor's three-dot menu and choose **Copy Macro**. Paste the work-in-progress item into the Fusion node tree and test the exposed controls there. Blackmagic added this loop so you don't have to save and import a new file for every small change. Check four things before you commit the file: 1. The output matches the original comp at the default values. 2. Every visible control changes what its label promises. 3. No essential input, mask, image, or text control was hidden. 4. Minimum and maximum values don't trap the editor or break the design. Paste the test into a fresh comp and connect the inputs it requires. Compare its default output with the original, then try the exposed controls. This catches problems that can stay hidden when the macro sits beside the source nodes and still depends on them. Also test a shorter and longer timeline duration. A finished animation will not necessarily adapt just because you packaged it. **Anim Curves** can scale animation with the duration; **Keyframe Stretcher** can preserve the entrance and exit while stretching the hold between them. Choose the behavior your template needs and check both ends after trimming. ## Save to the destination you actually need The current three-dot menu separates the destinations: - **Save As Macro:** creates one custom node with the controls you exposed. - **Save As Group:** stores an expandable container of the individual nodes. - **Save to Edit Template:** places the result in the Cut/Edit Effects Library as a Title, Generator, Effect, or Transition. - **Choose Thumbnail:** adds a recognizable thumbnail. - **Show in Folder:** opens the saved location instead of making you guess it. To reuse a saved custom tool in Fusion, right-click in the Node Editor and choose **Add Tool > Macros**, then select it. Keep its `.setting` file in the active Macros location shown by your save dialog; **Show in Folder** confirms where it went. The Macros folder is not the same as `Templates/Edit/Titles`. For an Edit Template, choose its category when saving, then add a fresh instance from that category to the timeline and check the Inspector. For an ordinary timeline transition, use the [transitions guide](https://davinciresolveclub.com/davinci-resolve-transitions/) to solve handles, duration, alignment, and playback. A Fusion Transition template is a different task: it builds the reusable effect that later appears in that library. ## Install .setting and .drfx templates correctly Install a loose `.setting` file in its intended category. For a valid `.drfx` bundle, double-click the file in your operating system *or* drag it into the Fusion page, then confirm Resolve's installation dialog. These are alternative routes. Renaming an arbitrary downloaded file to `.drfx` does not turn it into a valid bundle. The Macro Editor's **Show in Folder** locates a macro you have already saved. To find a template category instead, open the Fusion page Effects Library, expand **Templates > Edit**, right-click the category and choose **Show Folder**. That is safer than guessing an installation-specific path. The user-level Edit template roots in the [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) are: - **macOS:** `~/Library/Application Support/Blackmagic Design/DaVinci Resolve/Fusion/Templates/Edit/` - **Windows:** `%AppData%\Blackmagic Design\DaVinci Resolve\Support\Fusion\Templates\Edit\` - **Linux:** `~/.local/share/DaVinciResolve/Fusion/Templates/Edit/` Append `Titles`, `Generators`, `Effects` or `Transitions`. Create a missing category folder only inside the verified template root. Quit and reopen Resolve after manual placement, then look in the corresponding Effects Library section. If your installation uses a different location, follow **Show Folder**; do not modify the application package just because an older tutorial suggests it. ## Package a .drfx without losing its assets A bundle is useful when you want to distribute several templates together. Follow the documented structure rather than renaming a single settings file: 1. Create an `Edit` folder with the category subfolders you need, such as `Titles` and `Transitions`. 2. Put each `.setting` file in its matching category. Include the permitted icons and associated assets it needs. 3. ZIP that directory structure, then change the archive extension from `.zip` to `.drfx`. 4. Install the bundle in a test setup and check a fresh instance. Bundling a file does not fix a hard-coded media path or install a required third-party plugin. Resolve keeps the installed bundle together; it does not unpack it into loose templates. Removing the installed `.drfx` removes the templates inside it. Keep your editable source files separately, and distribute fonts, plugins or other assets only when their licenses allow it. ## Fix a Fusion template that is not showing ![Fusion Effects Library Templates Edit category and Show Folder command for locating installed templates](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/fusion-template-show-folder.webp) Annotated [Storyblocks interface reference](https://sb-wp-assets.storyblocks.com/resources/wp-content/uploads/2026/04/21093216/02a-Show-Folder-1024x482.png?ref=davinciresolveclub.com). The shown category is Transitions. Use the category your template belongs to; this is not a new Resolve 21 capture. 1. **Confirm the destination.** A Fusion Macro belongs in Fusion's macro list; an Edit Template belongs in the Cut/Edit Effects Library. 2. **Confirm the category.** A title in `Effects` will not appear under Fusion Titles. Move it to the folder that matches its construction. 3. **Confirm the extension.** Check that the file didn't become `.setting.txt` or an invalid bundle after download or extraction. 4. **Confirm the folder level.** The file belongs inside the category folder, not beside `Edit` and not inside an extra duplicate `Edit/Edit` tree. 5. **Restart Resolve.** Manual additions are indexed when the application starts. 6. **Search the correct library.** Look under Titles, Generators, Effects, or Video Transitions according to what you saved. 7. **Test the underlying requirements.** A template can load but still fail if it depends on missing fonts, media, third-party plugins, or Studio-only tools. Do not copy a missing item into several system and user folders at once. Keep one known file and change one thing per test. The correct extension is `.setting`, singular—not `.settings`. If the item appears but renders incorrectly, installation has succeeded; investigate its image connections, fonts, assets and required tools instead. ## Update a reusable template without breaking working edits Keep a known-good copy before replacing a working template. Save a material redesign under a new name such as **Lower Third v2**, add a fresh instance to a test timeline, and compare it with the old one. Replacing a file is not a promise that every existing timeline instance will update safely. Use the Macro Editor's **Open** command to load an existing macro for revision, or its Node Editor Macro submenu entry. Check the new version on a different clip and a different duration. If it uses fonts, external media, plugins, or Studio-only nodes, document those requirements where the template is distributed. A macro wrapper doesn't remove the licensing or installation requirements of the tools inside it. ## Frequently Asked Questions ### What is a Fusion macro in DaVinci Resolve? A Fusion macro packages one or more selected nodes as one custom node and exposes only the parameters you choose. It's useful when the internal setup should be reused without presenting the whole node tree every time. ### What is the difference between a Fusion macro and a group? A macro behaves as one custom node with selected controls. A group is a container whose individual nodes can be expanded and edited later. Use a group when future access to the internal construction matters. ### How do I make a Fusion template appear on the Edit page? In Resolve 21's Macro Editor, choose Save to Edit Template and select Title, Generator, Effect, or Transition. For manual files, place the .setting file in the matching Templates/Edit category folder, quit Resolve, reopen it, and search that Effects Library category. ### Why is my Fusion template not showing in DaVinci Resolve? Check the destination, category folder, extra folder levels, file extension and whether Resolve was restarted after manual placement. Use Show Folder in the Fusion Effects Library to locate the category, or Show in Folder in the Macro Editor for an already saved macro. Test one known file instead of copying it into several locations. ### Where is the Fusion Templates folder on Windows? The current user-level Edit template root is %AppData%\\Blackmagic Design\\DaVinci Resolve\\Support\\Fusion\\Templates\\Edit\\. Add Titles, Generators, Effects, or Transitions according to the template type. ### Can I edit a Fusion macro after saving it? Yes. The Resolve 21 manual says an existing macro can be opened from the Node Editor's Macro submenu and re-edited in the Macro Editor. Save a backup or a versioned copy before changing a tool used in real projects. ### Do Fusion macros and templates work in DaVinci Resolve Free? The macro and template workflow is part of Fusion, but the wrapper doesn't make every node, plugin, font, or asset universally available. A template that depends on a Studio-only tool or third-party plugin still carries that requirement. Use the [Fusion task hub](https://davinciresolveclub.com/davinci-resolve-fusion/) for the next compositing job. Keep this guide for the handoff: turning a working comp into a reusable tool with controls someone else can understand. ### DaVinci Resolve Shot Matching: Match Clips Correctly URL: https://davinciresolveclub.com/davinci-resolve-shot-matching/ Last updated: 2026-09-05T20:47:45.000Z **Quick answer:** on the Color page, select the clip you want to change. Then right-click the reference clip and choose **Shot Match to This Clip**. Resolve moves the target toward the reference in color and contrast. Normalize the footage consistently, isolate the test on a dedicated node, and check the result across the cut. Expand to several clips only after that first match works. The direction is easy to reverse. You don't right-click the bad clip and ask it to match itself. Select the targets first, then right-click the reference. If the automatic result is useful, refine it. If it isn't, remove the dedicated Shot Match node and match the shot manually. ## What Shot Match changes, and what it cannot repair Shot matching means making scene angles feel consistent in exposure, color balance, contrast and saturation. Blackmagic's [Color page overview](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com) describes the automatic command as matching color, contrast and brightness. It cannot reconstruct detail that was never recorded. Clipping caused by your grade or output transform is a different problem: inspect the source before assuming that detail is lost. The [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) is more precise about the limit. Shot Match tries to bring clips closer without stretching a weak image until it falls apart. Ask it to make an underexposed interior equal a noon exterior and it may split the difference. That restraint is useful, but it also means the command cannot force unrelated lighting into a convincing match. The automatic correction is designed as a neutral starting point, not a finished creative grade. Build the scene look after the shots agree, not inside the reference clip you're using to calculate the match. ## Choose a reference shot that makes sense A good reference represents the scene you want the audience to believe. Look for a clip with stable exposure, a useful view of skin or neutral objects, no large temporary color wash and enough tonal detail to judge. The prettiest frame isn't always the best reference. A heavily stylized close-up can be a poor target for a wide shot with different lighting and background colors. For an automatic match, keep the reference simple. Blackmagic recommends basic Lift, Gamma and Gain adjustments; complex curves, qualifiers and secondaries can make the comparison less reliable. Keep normalization, the test adjustment and the creative look separate so you can inspect each. Their exact node placement depends on your color-management pipeline. For the reference-balancing steps, use the [beginner color grading workflow](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/). Pick a reference the other shots can reasonably approach. If matching to it destroys shadow or highlight detail in weaker footage, soften the reference rather than pushing those clips harder. ## Normalize log and mixed-camera footage before matching Shot Match works best when the target and reference live in a common normalized space. The current manual says the control was developed around Rec.709 gamma 2.4 and recommends Resolve Color Management as a way to normalize media first. That doesn't mean every project must be converted manually to Rec.709\. It means the algorithm should compare equivalent image states. Don't ask Shot Match to compare unnormalized LogC with unnormalized RED Log3G10, or a normalized clip with a flat log clip. Those signals encode tone and color differently. Resolve may produce a change, but the comparison isn't a sound basis for the scene. Use a consistent managed pipeline or verified transforms first. The [RCM and CST guide](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/) explains how to avoid missing or double transforms. Protect an existing grade before experimenting. Avoid stacking the test over a complicated creative look or secondary corrections. Keep the input normalization that your pipeline needs; “start clean” is not an instruction to delete every CST or disable project color management. Should you use Auto Color first? Blackmagic's Resolve 21 manual gives conflicting guidance: its introduction recommends the A button on both target and reference, while the following guidelines call for ungraded targets. The [official Resolve 20 Colorist Guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf?ref=davinciresolveclub.com) also demonstrates Shot Match after a Balance node. Treat Auto Color on both clips as a separate test, not a compulsory step or a guaranteed improvement. Preserve your original grade, compare the simple normalized baseline with that test, and keep the better result. ## How to use Shot Match to This Clip 1. Open the **Color** page and show the thumbnail timeline. 2. Select one target clip that needs to change. Leave multi-clip selection until that first test works. 3. In the Node Editor, right-click a node and choose **Add Node > Add Serial**. Label the new node Shot Match and leave it selected. Keep required normalization intact. 4. Right-click the good reference clip. The reference may be outside the target selection. 5. Choose **Shot Match to This Clip**. 6. After applying the command, select the target and reference for comparison. Enable **Split Screen > Selected Clips**, then play across the cut. ![Shot Match context menu with instructions to select the target then right-click a different reference clip](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/shot-match-direction-v2.webp) Annotated [Resolve 20 command-menu reference by Larry Jordan](https://wpmedia-lj.s3.amazonaws.com/wp-content/uploads/2025/11/Match%5F14.jpg?ref=davinciresolveclub.com). Select the target first, then open this menu on a different reference clip. The menu route is also documented for Resolve 21; this is not a new capture. For a contiguous batch, select the first target and Shift-click the last. Start with one camera angle, not a mixture of wides, close-ups, interiors and exteriors. Before applying the match, check that each target has an isolated test node selected. If you cannot keep the adjustment separate from work you need to preserve, match those clips individually instead. ## Why the color wheels do not move after Shot Match Shot Match doesn't write a visible set of Lift, Gamma, Gain or curve values that you can inspect. The Resolve 21 manual says the generated image adjustment is applied invisibly as the final adjustment in the selected node, similar to a LUT. The image changes while the familiar primary controls may appear untouched. A dedicated node gives you a simple before/after switch. Select it and press **Command-D on macOS or Ctrl-D on Windows** with the default shortcuts. That bypasses the selected node; Shift-D bypasses the whole node tree. To remove the isolated test, right-click its node and choose **Reset Node Grade**, or delete that node. Resetting also clears other adjustments and keyframes in that node, so do not use a node that contains work you need to keep. ![Reset Node Grade in a Resolve node menu, with a warning that it clears other work in that node](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/shot-match-reset-node.webp) Annotated [Resolve 20 node-menu reference by Larry Jordan](https://wpmedia-lj.s3.amazonaws.com/wp-content/uploads/2025/11/Match%5F16.jpg?ref=davinciresolveclub.com). The screenshot identifies the command, not proof that node 01 contains only Shot Match. Isolate your own test before resetting it. This also explains why copying the visible wheel numbers cannot reproduce a Shot Match result. If you need an editable correction, use the automatic result as a visual hint, then rebuild the match with normal primary controls on a fresh node. The [node guide](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) covers serial order, isolation and safe bypassing in more detail. ## Match multiple clips without creating an undo trap Each timeline clip has its own undo history. Blackmagic warns that a Shot Match applied to several clips cannot be undone across all of them with one global action. Revisit each affected clip and either undo the operation or remove its isolated test adjustment. Do not use Reset All Grades and Nodes just to remove one match. 1. Group the scene mentally by camera angle and lighting setup. 2. Pick one target from Angle B and match it to the chosen reference from Angle C. 3. Inspect that cut in split screen, scopes and normal playback. 4. If the test holds, select the other Angle B clips and repeat the same reference match. 5. Test one clip from the next angle before expanding the selection again. Don't run the command on shots that already match. A small automatic change can make a stable angle less consistent. Lightbox is useful after the first pass because it makes a mismatched clip easier to spot across a full scene. ## Refine the match with waveform, RGB parade and vectorscope A match should survive the cut, not merely produce similar scope shapes. After matching, select both the reference and target, enable Split Screen and choose **Selected Clips** from its mode menu. The comparison illustration below shows where that mode appears; its four images demonstrate grading versions, not a tested camera match. 1. **Waveform:** compare corresponding black, midtone and highlight regions. Adjust exposure and contrast with primary controls. Don't force unrelated backgrounds to the same level. 2. **RGB parade:** inspect neutral objects and shadows for channel imbalance. Correct the cast while protecting intentional colored light. 3. **Vectorscope:** compare hue and saturation, then check skin-tone direction when skin is present. The traces don't need to become identical. 4. **Playback:** loop the edit. A technically close still can still flash warmer, darker or more saturated during the cut. ![Resolve Split Screen menu identifying Selected Clips for reference-and-target comparison](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/shot-match-compare-clips.webp) Annotated [Blackmagic Design comparison-interface reference](https://images.blackmagicdesign.com/images/products/davinciresolve/color/compare/compare-md.jpg?%5Fv=1601272719&ref=davinciresolveclub.com). The shown desert frames are grading versions. Select Selected Clips for your own shot comparison; this is not a measured before/after result. The [Resolve scopes guide](https://davinciresolveclub.com/davinci-resolve-scopes-explained/) explains what each display measures and where skin, clipping and channel imbalance appear. Shot Match is faster when the scopes tell you what remains wrong instead of inviting random wheel movement. For a manual comparison against a fixed frame, park on the reference, right-click the Viewer and choose **Grab Still**. Switch to the target, select that still in the Gallery and enable **Image Wipe** in the Viewer toolbar. Drag inside the Viewer to move the dividing line, then adjust the target with normal primary controls. You are comparing the still, not choosing Apply Grade or copying its node tree. ## Why Shot Match is not working or gives a bad result ### The reference and target are reversed Select the clip that should change, then right-click the different clip it should resemble. If the command is missing, first check that you have not right-clicked the active target itself. If the wrong image changes, undo on that clip or reset its isolated test node before repeating the selection. ### The clips are in different image states A normalized reference and flat log target aren't comparable. Check input color spaces, color management, CST placement and whether one clip has a display transform that the other lacks. ### The targets already contain corrections A complicated target grade can interfere with the comparison. Protect it and test a simpler version while retaining necessary normalization. The manual's Auto Color advice and its ungraded-target warning are not consistent, so do not assume that all preliminary balance is forbidden—or that adding Auto Color always fixes a poor match. ### The shots do not share enough scene information A frame dominated by a purple wall can distort the comparison with an angle dominated by green foliage. Large unmatched color areas are a documented failure case. Try a more representative reference, match by angle, or switch to manual scopes work. ### The images are too far apart Severe exposure differences, mixed lighting or missing source detail may be beyond an automatic match. Try a more representative reference or balance the target manually. If you test Auto Color before another match, apply that experiment to both clips on protected versions and compare it with the baseline. Do not keep stacking failed automatic adjustments. ## Shot Match vs Auto Color, Color Match and copying a grade | Tool | Best use and limit | | ---------------- | ----------------------------------------------------------------------------------------------------------------------- | | **Auto Color** | Move one current frame toward a neutral starting point. It does not compare that clip with a separate reference. | | **Shot Match** | Move scene clips toward a chosen reference. It does not expose editable wheel values or guarantee a final match. | | **Color Match** | Use a supported color chart recorded in the shot. It is not the same as matching one ordinary image to another. | | **Copy grade** | Apply the same existing node correction to genuinely similar clips. It does not analyze differences between shots. | | **Manual match** | Use visible controls when lighting, cameras or backgrounds differ. It takes longer but keeps every correction editable. | The [Auto Color guide](https://davinciresolveclub.com/davinci-resolve-auto-color/) explains one-frame automatic balancing. If clips already share the same setup and need the same correction, use the [copy-grade methods](https://davinciresolveclub.com/copy-color-grade-davinci-resolve/) instead. Copying a grade and calculating a match solve different problems. ## A repeatable scene-matching order 1. Normalize every camera into a consistent working pipeline. 2. Choose one honest reference per lighting setup. 3. Balance that reference with simple primaries. 4. Test Shot Match on one clip from one angle. 5. Refine the target with waveform, parade and vectorscope. 6. Expand to the rest of that angle only after the test works. 7. Review the scene in Lightbox and loop every cut. 8. Add the creative look after the scene is internally consistent. Keep the test small enough to reverse: one clip, then one angle. For a manual creative workflow, matching to a developed hero look is also possible. The simple-reference advice here is specifically about giving the automatic Shot Match command a useful starting point. ## DaVinci Resolve Shot Matching FAQ ### Where is Shot Match to This Clip in DaVinci Resolve? Open the Color page, select the target clip or clips in the thumbnail timeline, then right-click the reference clip. Choose Shot Match to This Clip from that reference clip's context menu. ### Which clip should I select first for Shot Match? Select the clip or clips that need to change first. Then right-click the good reference clip. The targets receive the adjustment; the reference supplies the color and contrast direction. ### Why did Shot Match change the image without moving the color wheels? Resolve applies Shot Match as an invisible final adjustment in the selected node, similar to a LUT. It doesn't move the normal user-editable primary controls, so use a dedicated node that you can bypass or remove. ### Can I Shot Match multiple clips at once? Yes. Select multiple target clips, then right-click the reference and run Shot Match. Test one clip from each camera angle first because each clip has its own undo history and a bulk match can't be undone in one global action. ### How do I undo or remove Shot Match? If it was the last action on the current clip, use Undo. For several clips, revisit them individually. If Shot Match is isolated on its own node, delete that node or right-click it and choose Reset Node Grade. Reset also removes other adjustments and keyframes in that node; do not confuse it with resetting every grade and node. ### Does Shot Match work with log footage and different cameras? It can work with log footage, but the manual says normalized clips produce more reliable results. Do not match different unnormalized log encodings or mix normalized and unnormalized clips. Put both cameras into a consistent color-managed or verified transform pipeline first. ### Why does Shot Match look wrong? Check the reference choice, complicated target corrections, mismatched normalization, exposure or lighting differences, and large background colors that appear in only one angle. Test a simpler protected version or another reference. Auto Color before matching is an optional comparison, not a guaranteed fix; finish manually when the automatic result remains worse. Shot Match is one route inside the [DaVinci Resolve Color Grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/). Use it when the reference is meaningful and the inputs are comparable. When either condition fails, a visible manual correction is safer than forcing the automatic result. ### DaVinci Resolve Smart Bins and Power Bins Guide URL: https://davinciresolveclub.com/davinci-resolve-smart-bins-power-bins/ Last updated: 2026-09-05T18:45:49.000Z **Quick answer:** use a **Smart Bin** when you want Resolve to keep finding clips that match metadata rules inside a project. Use a **Power Bin** when you want to place reusable assets manually and reach them from other projects in the current Project Library. Use a regular Bin when the material belongs to one project and you want to file it yourself. That distinction matters because the three bin types solve different problems. A Smart Bin is a saved query, not a folder full of copied clips. A Power Bin is a shared Media Pool area, not a search rule and not a backup of the files on disk. Blackmagic's [Media page overview](https://www.blackmagicdesign.com/products/davinciresolve/media?ref=davinciresolveclub.com) makes the same distinction. The steps here cover the desktop version of Resolve 21; the iPad interface is different. New to the Media Pool? Start with the importing steps in the [Resolve beginner guide](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/). Otherwise, choose the bin type below and build one small, useful example before organizing the whole project. ## Smart Bins vs Power Bins vs regular Bins | Bin type | How clips get there | Scope | Best use | | --------------- | -------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | **Regular Bin** | You drag or import items manually | Current project | Camera days, interviews, audio, timelines and project-specific graphics | | **Smart Bin** | Resolve evaluates metadata rules dynamically | Current project's matching media; the rule can be shown in all projects | Good takes, one codec, one frame rate, interview keywords, offline clips or timelines | | **Power Bin** | You add reusable items manually | Projects in the current Project Library, with user limits in multi-user installations | Logos, slates, music beds, sound effects, title generators and recurring graphics | The useful test is simple. If the membership should change when metadata changes, choose Smart. If the same asset should be available when you open a different project, choose Power. If neither is true, a regular Bin is usually clearer. ## Show Smart Bins and Power Bins in Resolve 21 1. Open the Media Pool on the Media or Edit page. 2. Open the Media Pool options menu, the three-dot control in the panel. 3. Enable **Show Smart Bins** and **Show Power Bins**. 4. Expand the new sections in the Bin list. ![Resolve Media Pool menu with Show Smart Bins and Show Power Bins highlighted](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/bins-show-sections.webp) Annotated [Resolve 20 interface reference by giantmoa](https://note.com/giantmoa/n/n434b4fa9121b?hl=en-US&ref=davinciresolveclub.com). The panel-menu route is also documented for Resolve 21; this is not a new Resolve 21 capture. The [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) places these switches in the Media Pool options menu. Older tutorials use the top-level View menu; don't keep hunting there if your version has the panel menu instead. On the Cut page in Resolve 21, open the Media Bin dropdown at the upper left of the Media Pool to view Smart Bins. Its plus button creates a new one. The Media or Edit page is a simpler starting point when you want to see regular Bins, Power Bins and Smart Bins together. ## Create a Smart Bin that proves the rules work A good first test uses a property you can verify on one clip. Frame rate, codec and resolution come from the media. **Good Take is different: it is a checkbox, not an automatic quality judgment.** Select a clip in the Media Pool, open Inspector > File and enable Good Take before building the example below. 1. Show the Smart Bins section. 2. Right-click its background and choose **Add Smart Bin**. 3. Name the rule by its result, such as **Good Takes**. 4. Choose **Media Pool Properties > Good Take > is true**. 5. Click **Create Smart Bin**. Confirm that the clip you marked appears. To test resolution instead, choose Resolution and enter the width and height of a known source clip—not the timeline resolution. The reference below uses 1920 × 1080 as an example, not a required project setting. ![Edit Smart Bin dialog highlighting Resolution, 1920 by 1080 values and Match All](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/smart-bin-field-value.webp) Annotated Resolve 17 dialog from TutKit's lesson. This shows an existing resolution rule, not the Good Take example above. The field/value and All/Any logic is documented in Resolve 21; the dialog is not a fresh capture. ### Match All, Match Any and nested criteria **Match All** narrows the result because every enabled row must be true. For example, `Keywords contains interview` plus `Good Take is true` returns only selected interviews. **Match Any** widens the result because one matching row is enough. It can collect `Keywords contains drone` or `Keywords contains aerial`. The **plus button** adds a criterion. Option-click on macOS or Alt-click on Windows to add a nested match group. Use that when you need all of one group and any of another; otherwise, two simple Smart Bins are easier to troubleshoot. ### Automatic Smart Categories are different Resolve can create automatic categories for Timelines, Photo Albums, Keywords, Collections, People, Shot, Scene and Offline Clips. The controls live under **Preferences > User > Editing > Automatic Smart Bins**. Keyword, Shot and Scene categories have a useful shortcut: drag selected clips onto an existing automatic Smart Bin to assign that bin's property to the clips. The current manual explicitly limits this behavior to those three categories. Dropping clips onto an arbitrary custom Smart Bin doesn't file them or rewrite their metadata. If you need to add scene and take labels first, the [Slate ID and Slate Finder guide](https://davinciresolveclub.com/davinci-resolve-slate-finder-slate-id/) covers that separate workflow. Check the labels before relying on a Smart Bin to select your footage. ## What “Show in all projects” actually shares The checkbox makes the **Smart Bin definition** persistent. Resolve places that rule in the User Smart Bins folder inside every project in the current Project Library. It doesn't merge the projects' Media Pools or make one project's clips visible inside another. For example, a persistent Good Takes rule can appear in two projects but return different clips. An empty result in the second project is correct when none of its clips has Good Take enabled. ## Build a Power Bin for reusable assets 1. Show the Power Bins section from the Media Pool options menu. 2. Right-click inside the section and choose **Add Bin**. 3. Create a small structure such as Brand, Audio and Titles. 4. Import or drag only assets you genuinely reuse. 5. Open another project in the same Project Library and verify the Power Bin there. ![Power Bins Master with Clips and Audio folders, distinguished from project bins and Smart Bins](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/power-bins-scope.webp) Annotated crop from [TutKit's Resolve 17 lesson](https://www.tutkit.com/en/text-tutorials/1778-efficient-use-of-power-bins-and-smart-bins-in-davinci-resolve?ref=davinciresolveclub.com), illustrating the separate Power Bins area. Folder names are examples; current-library scope and source-file dependence also apply in Resolve 21. Keep this small: an approved logo, a slate, a title generator, useful sound effects and music licensed for your work. Put camera cards and one-off project footage in regular Bins so the shared collection stays easy to scan. The boundary is the current Project Library, not your entire account. A different library can have different Power Bins. In a multi-user installation, the manual also limits visibility to the particular user's projects. ### Power Bins do not replace source storage Power Bins reference source files; they do not copy them into a protected media archive. Keep those files in a stable, backed-up folder. If a disk is disconnected or a file moves, follow the [Media Offline relink steps](https://davinciresolveclub.com/media-offline-davinci-resolve/). Need to carry an editable sequence between projects? Use a timeline transfer, rather than treating Power Bins as a universal container for timelines, compound clips or multicam edits. If an item will not drop into a Power Bin, identify its clip type first. A Fusion Composition and a Fusion Clip are not interchangeable names; a `.drfx` file is a template package, not an ordinary Media Pool clip. ## Export and back up Power Bins without false security To export a Power Bin, select it, right-click and choose **Export Bin**, then save the `.drb` file. In the destination Project Library, show Power Bins, select the destination area, right-click and choose **Import Bin**, then select that file. Check the imported bin and relink any offline assets before depending on it. The `.drb` file stores the bin information, not the linked logos, music or video on disk. Back up those source files separately. For whole-project backups and transfers, use the [Resolve save and archive guide](https://davinciresolveclub.com/how-to-save-work-davinci-resolve/). The [project location guide](https://davinciresolveclub.com/where-davinci-resolve-projects-saved/) explains why the library, project export and media folders are separate. ## Fix Smart Bins or Power Bins that look missing or broken ### The section is not visible On the Media or Edit page, make sure the Media Pool is open, then enable the missing section in its three-dot menu. Expand the Bin list and the section itself. If space is tight, widen the Media Pool; do not assume the saved bins have been deleted just because the sidebar is hidden. ### A Smart Bin is empty Double-click the Smart Bin to edit it. Disable criteria one at a time and inspect the same field on a known clip. Match All excludes that clip if even one enabled row is false. Keywords, Scene and Description may be blank; Good Take may simply be unchecked. Save the corrected rule with OK. ### The rule appears in another project but the clips do not That's expected when **Show in all projects** is enabled. The saved rule travels; clip contents don't. Add or tag media in the second project and let the rule evaluate that project's Media Pool. ### Power Bins disappeared after switching projects Confirm that the new project belongs to the same Project Library and user context, then re-enable Show Power Bins in the Media Pool options. If you moved to another library or computer, import the exported `.drb` and restore the source-media paths as needed. ### A Power Bin item is offline Find the actual source file before reorganizing bins. Relink or replace that file reference. Recreating the Power Bin doesn't restore deleted media. ## Smart Bins and Power Bins FAQ ### What is the difference between Smart Bins and Power Bins? Smart Bins dynamically show clips that match metadata rules in the current project. Power Bins are manually populated reusable assets available across projects in the current Project Library. ### Why can’t I see Smart Bins or Power Bins? On the Media or Edit page, open the Media Pool options menu and enable Show Smart Bins or Show Power Bins. Expand the Bin list and the section; widen the Media Pool if space is tight. ### Do Smart Bins and Power Bins work in DaVinci Resolve Free? Yes, basic Smart Bins and Power Bins are desktop organization features available in Free as well as Studio. That does not make every AI tool used to create metadata free. This guide does not describe the iPad interface. ### Does “Show in all projects” share Smart Bin clips? No. It shares the Smart Bin rule through the User Smart Bins folder. Each project shows only its own media that matches that rule. ### Can I back up Power Bins? You can export and import Power Bins as `.drb` files. Back up the referenced source media separately because the bin file isn't a copy of the logos, audio, titles or clips on disk. ### Why is my Smart Bin empty? Check for empty metadata, an unchecked Good Take field, the wrong value or a Match All rule that excludes the clip. Test one known property, then add criteria one at a time. ### Does deleting a Smart Bin delete my clips? No. The current Resolve manual states that deleting a Smart Bin removes the saved filter, not the gathered media associated with it. Keep regular Bins for the current project, Smart Bins for searches you repeat, and Power Bins for assets you reuse. For the next job—syncing, proxies or smoother playback—choose a guide in the [Resolve workflow hub](https://davinciresolveclub.com/tag/workflow/). ### DaVinci Resolve Supported Codecs and Formats Guide URL: https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/ Last updated: 2026-09-05T16:59:08.000Z **Quick answer:** DaVinci Resolve supports many common codecs, but a file extension is not enough to check a clip. Identify its container, video and audio codecs, profile and bit depth. Then check the row for your operating system, Free or Studio edition and hardware. Use **Decode** for import and **Encode** for export. MP4 is the container, not the video inside it. For a compatibility check, read the file with MediaInfo and compare the result with the official matrix. Don't rely on the extension, the camera brand, or a list that combines macOS, Windows and Linux into one yes/no answer. **Checked September 5, 2026:** the latest codec matrix found in Blackmagic's support listing is [DaVinci Resolve 20 Supported Formats and Codecs](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com), dated July 2025\. The platform table below summarizes that document; it is not a newly issued Resolve 21 matrix. Check your installed build and a representative file before relying on an older row for a new camera profile or GPU. If a particular MP4 already fails, the [MP4 import repair guide](https://davinciresolveclub.com/davinci-resolve-wont-import-mp4/) walks through that problem. For the steps around importing and editing, the [Resolve workflow hub](https://davinciresolveclub.com/tag/workflow/) brings together media, proxy and playback guides. ## The six checks behind “supported” | Check | Example | Why it changes the answer | | --------------------- | --------------------------------------- | ----------------------------------------------------------------- | | Container | MP4, MOV, MKV, MXF | Defines the package, not every stream it may contain | | Video codec | H.264, H.265/HEVC, AV1, ProRes, DNxHR | Resolve must be able to decode or encode that stream | | Profile and bit depth | Main 10, 10-bit, 4:2:2 | Support can differ inside one codec family | | Audio codec | AAC, PCM, MP3, FLAC | Video and audio support are independent | | Platform and edition | Windows Free, macOS Studio, Rocky Linux | The official rows differ by OS and license | | Hardware | Supported GPU decoder/encoder | GPU-accelerated rows still depend on the actual device and driver | The official matrix adds two more distinctions: alpha export and codec passthrough. Those matter for transparency and finishing, but they aren't substitutes for Decode and Encode. A codec can be readable without being available as a Deliver output. ![Resolve Metadata panel distinguishing a MOV container, H.264 video codec and the example's No Audio status](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/codecs-metadata-reference.webp) Annotated crop of [Blackmagic Design's Media Pool interface reference](https://www.blackmagicdesign.com/products/davinciresolve/media?ref=davinciresolveclub.com). The displayed No Audio belongs to this example; it is not a diagnosis of your file. Use MediaInfo for the fuller stream details. ## Read the actual streams with MediaInfo Open the source file in [MediaInfo](https://mediaarea.net/en/MediaInfo?ref=davinciresolveclub.com) and choose Tree or Text view. Note these fields before changing anything in Resolve: 1. **General Format:** the container, such as MPEG-4. 2. **Video Format:** the codec, such as AVC/H.264 or HEVC/H.265. 3. **Format profile and Bit depth:** record both; support can differ within one codec family. 4. **Chroma subsampling:** commonly 4:2:0 or 4:2:2, another profile detail worth recording. 5. **Frame rate mode:** Constant or Variable. If a readable phone or screen recording drifts out of sync, variable frame rate is worth checking; it does not automatically make the codec unsupported. 6. **Audio Format:** AAC, PCM, MP3, FLAC or another independent stream. ![MediaInfo frame-rate mode, 4:2:0 chroma subsampling and 8-bit depth with field-by-field annotations](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/codecs-mediainfo-fields.webp) Annotated MediaInfo reference from [Puget Systems' hardware-decoding research](https://www.pugetsystems.com/labs/articles/What-H-264-and-H-265-Hardware-Decoding-is-Supported-in-DaVinci-Resolve-Studio-2122/?ref=davinciresolveclub.com). These are the source example's values, not settings to copy into Resolve. The example above has 8-bit, 4:2:0 video at a constant frame rate. Your file may have different values even when its extension is the same. Renaming `clip.mkv` to `clip.mp4` does not change those streams. Remuxing moves compatible streams into a different container without re-encoding them; transcoding creates new encoded streams. For an OBS recording, a remux can help when the container is the obstacle and its streams are already compatible. It cannot turn an unsupported AV1, HEVC or audio stream into a supported one. The [OBS formats guide](https://obsproject.com/kb/audio-video-formats-guide?ref=davinciresolveclub.com) explains the distinction; check video and audio after remuxing instead of assuming a new extension fixes both. ## Common codec support by desktop platform This is a quick reference to the **July 2025 Resolve 20 matrix**, using its exact platform headings. It is not a complete format list or a guarantee for every current computer. Camera RAW variants, image sequences, IMF/DCP, alpha and professional profiles still need their individual rows. | Platform | H.264 / H.265 | AV1 | AAC audio | | -------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------- | | macOS | Decode and encode listed as GPU accelerated for MOV, MKV and MP4 | Decode Yes; Encode not listed | Decode and encode listed | | Windows 10 | H.264: 8-bit OS-supported profiles. H.265: 8/10-bit OS-supported profiles. Studio adds more profiles and GPU acceleration | Decode and encode listed as GPU accelerated | Decode and encode listed | | Rocky Linux 8.6 CUDA | Decode: Studio-only; Nvidia GPU acceleration is noted separately. Encode: Studio and Nvidia graphics | Decode and encode listed with Nvidia GPU acceleration | Not listed for decode or encode | On Windows, the matrix lists 8-bit OS-supported H.264 profiles and 8/10-bit OS-supported H.265 profiles, with additional profiles and GPU acceleration in Studio. That is not the same as saying every 10-bit HEVC file needs Studio. Check its exact profile and chroma subsampling: two 10-bit camera files need not use the same decoding path. For Linux, keep two conditions separate: H.264/H.265 **decode is marked Studio-only**, with Nvidia acceleration noted in parentheses; **encode explicitly calls for Studio and Nvidia graphics**. The decode note does not establish that all software decoding needs Nvidia. These are Rocky Linux 8.6 CUDA rows, not a promise for every distribution or GPU. Check the [Resolve 21 system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) separately when choosing a supported installation. ## Audio, alpha and passthrough need their own checks Audio needs its own row. The macOS and Windows sections list AAC, constant-bit-rate MP3, FLAC and OPUS decode, with encoding availability shown separately. The Linux section lists MP3 and FLAC but leaves built-in AAC decode and encode blank. A container can therefore contain usable video and unusable audio. Do not assume that buying Studio alone fixes Linux AAC. When a destination requires a specific audio format, read the Audio row and the container note together. For example, embedded audio choices depend on what the selected video container permits. Don't assume that an audio codec available as a standalone file is available inside every MOV, MP4 or MXF output. Alpha is another separate capability. The matrix has an **Alpha Exports** column because a codec that carries ordinary RGB/YUV video may not preserve transparency. Match the exact codec profile and container required by the receiving application. A file extension alone can't prove that an export contains an alpha channel. Codec Passthrough means Resolve may reuse source video instead of encoding it again. The [Resolve 21 Deliver documentation](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) also requires matching Format, Codec and Type for its source-reuse option; grades, effects, resizing and other changes can prevent reuse. It is not a universal lossless-export switch. A Yes in the passthrough column does not override the required output format or its limitations. ## ProRes, DNxHR, BRAW and editing intermediates The matrix lists Apple ProRes 422/4444-family and DNxHR decode and encode across macOS, Windows and Rocky Linux, subject to the container and profile rows. Advice that Resolve cannot export ProRes on Windows is outdated: Blackmagic added Windows and Linux ProRes encoding in [Resolve 19.1.4](https://www.blackmagicdesign.com/support/content/readme/0dc287e90d53499dbeb74c1e9ce09fcd?ref=davinciresolveclub.com). ProRes 422/4444 support is not evidence of ProRes RAW support. Blackmagic RAW is a separate codec family, listed for decode across the three desktop sections. ProRes or DNxHR can be useful working formats, but the profile matters. Choose one that preserves the source bit depth and intended quality, convert a short representative section, and inspect it before processing an entire card. Intermediate files are often much larger than H.264 or H.265\. Keep the camera originals and treat the transcode as a working copy. A supported codec can still be difficult to edit smoothly. Long-GOP H.264/H.265 may play correctly on its own yet stutter in multicam, high-frame-rate or effects-heavy timelines. That is not proof of an unsupported format. The [slow-playback guide](https://davinciresolveclub.com/davinci-resolve-slow-playback/) helps separate decoding pressure from cache, GPU and timeline problems. Hardware acceleration is a separate check from whether a codec is readable. In Preferences > System > Decode Options, inspect the available H.264/HEVC hardware-decoding controls. The devices shown depend on the installation. Puget's profile-by-profile testing also separates bit depth and chroma subsampling; the name H.265 alone does not tell you which GPU can accelerate a clip. ![Resolve Studio System Decode Options with H.264 and H.265 hardware-decoder controls annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/codecs-hardware-decode.webp) Older Studio interface reference from Puget Systems, with editorial annotations. Available devices and controls depend on the computer and edition; this is not a new Resolve 21 capture or an instruction to enable every checkbox. ## Decode and Encode are different promises **Decode** means reading a source stream for import and playback. **Encode** means creating an output stream. If video imports as audio only, inspect the video Decode row. If a codec is missing from Deliver, inspect Encode instead. The list of possible outputs is not a list of every format Resolve can read. The extension doesn't make both sides equivalent. You might import an AV1 file where AV1 encoding is unavailable, or decode a professional camera format that Resolve does not offer as the same Deliver output. Start the [Resolve export workflow](https://davinciresolveclub.com/export-video-davinci-resolve/) only after choosing a format and codec that match the destination rather than trying to mirror the source automatically. ## Free versus Studio without the usual oversimplification Blackmagic's [Resolve Studio 21 page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) describes expanded professional format support, advanced H.264 camera profiles, 10-bit encoding, IMF and DCP capabilities. The detailed matrix remains the better source for an individual row because the Free/Studio answer changes with OS, codec, profile and hardware. Examples show why a single rule fails: - Windows Free has listed OS-supported H.264 and H.265 profiles; Studio adds more profiles and GPU acceleration. - Rocky Linux H.264/H.265 decode is marked Studio-only; its encode rows explicitly require Studio and Nvidia graphics. - macOS H.264 and H.265 rows are listed as GPU accelerated without the same Linux Studio-only label. - Free can finish up to 60 fps at UHD 3840×2160\. That includes the resolution commonly called 4K for YouTube. Do not confuse it with a wider DCI 4K frame such as 4096×2160, which exceeds the Free UHD limit. Match the codec row to your platform before deciding whether an upgrade solves the problem. A license upgrade does not add a missing hardware decoder to a GPU or make every recording profile equivalent. ## The five-step codec diagnostic 1. **Read the streams.** Record container, video codec, profile, bit depth, chroma, frame-rate mode and audio codec. 2. **Choose the correct OS section.** Don't use a Windows row to diagnose Linux or macOS. 3. **Choose Decode or Encode.** Import and export are separate tests. 4. **Apply edition and hardware conditions.** Preserve every Studio, OS-supported profile, GPU and driver qualification. 5. **Test a short copy.** If the stream is unsupported, convert a representative sample to a listed intermediate and inspect it. If the source should be supported, check the file path and integrity, storage access and app build. For stuttering rather than a failed import, investigate decoding load and cache separately. If a previously linked clip turns red after moving a drive, start with the [Media Offline relink workflow](https://davinciresolveclub.com/media-offline-davinci-resolve/). Transcoding doesn't repair a missing path, and relinking does not add a missing decoder. ## DaVinci Resolve supported codecs FAQ ### Does DaVinci Resolve support MP4? Resolve supports many streams inside MP4, but MP4 alone isn't a compatibility answer. Check the video codec, audio codec, profile, bit depth, operating system, edition and Decode or Encode column. ### Does DaVinci Resolve Free support H.264? It depends on the platform and profile. The July 2025 matrix lists 8-bit OS-supported H.264 profiles on Windows and GPU-accelerated support on macOS. The Rocky Linux row marks decode Studio-only, with Nvidia acceleration noted separately. ### Does DaVinci Resolve Free support 10-bit H.265? The July 2025 Windows matrix lists 8/10-bit OS-supported H.265 profiles and says Studio adds more profiles and GPU acceleration. That does not guarantee every 10-bit or 4:2:2 file works. Check the exact MediaInfo profile and the separate row for your platform. ### Why does an MP4 import as audio only? The container and audio stream may be readable while the video codec or profile isn't. Read the file in MediaInfo, then compare the video stream with the correct OS and edition Decode row. ### Does DaVinci Resolve support AV1? The July 2025 matrix lists AV1 decode on macOS but no encode entry. Windows lists GPU-accelerated decode and encode; Rocky Linux 8.6 CUDA lists Nvidia-accelerated decode and encode. This is a Resolve 20 reference, so confirm the options on your installed build and GPU. ### What codecs should I transcode to for editing? DNxHR and ProRes are common intermediate candidates listed across the desktop platform sections. Match profile and bit depth to the source, test a short sample, and expect larger files than H.264 or H.265. ### Why can Resolve import a codec but not export it? Decode and Encode are separate capabilities. A codec can appear in the Decode column without an equivalent Encode option for that platform, edition or hardware. ### DaVinci Resolve Picture in Picture: Resolve 21 Guide URL: https://davinciresolveclub.com/davinci-resolve-picture-in-picture/ Last updated: 2026-09-05T14:24:58.000Z **Quick answer:** put the full-screen clip on V1 and the video you want as the smaller window directly above it on V2\. In DaVinci Resolve 21, select the V2 clip, open Effects, find **Resolve FX Transform > Picture in Picture**, and apply it. Use **Content** to reframe what appears inside the inset, **Position** to size and place the window, and **Style** for rounding, border and shadow. If Picture in Picture is missing, check the version before rebuilding the project. Blackmagic introduced the dedicated effect in the [Resolve 21 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com). Resolve 20 and earlier can make the same basic layout by scaling and positioning the V2 clip with Inspector Transform controls. The control names and two-track setup were checked on September 5, 2026 against the [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). This guide covers one inset window; the [Resolve learning hub](https://davinciresolveclub.com/davinci-resolve-tutorial/) can help with the editing steps around it. ## Choose the right Picture in Picture method | Method | Best use | Tradeoff | | -------------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------ | | Resolve 21 Picture in Picture FX | One facecam, reaction shot, product close-up or tutorial inset | Requires Resolve 21 | | Inspector Transform | Basic PiP in Resolve 20 or earlier, or a plain borderless inset | Framing, border and shadow take more manual work | | Video Collage | Several repeated tiles or a structured grid | More setup than one inset needs | | Fusion | Custom masks, tracked frames, complex reveals or reusable node templates | Steeper workflow and easier to overbuild | For one smaller window, start with the native Resolve 21 effect. Use a grid or Fusion when you need several coordinated frames or a custom mask. Switching between camera angles is a different job: the [multicam editing guide](https://davinciresolveclub.com/davinci-resolve-multicam-editing/) covers showing one synchronized angle at a time. ## Create picture in picture in Resolve 21 1. Open the Cut or Edit page and place the background video on V1. 2. Put the clip that should become the smaller window on V2, directly above the matching part of V1. 3. Trim or sync the two clips before styling the window. Moving the PiP clip later will also move its timing. 4. Select the V2 clip. Open **Effects**, search for **Picture in Picture**, and apply the Resolve FX Transform effect to that upper clip. 5. Open **Inspector > Effects > Open FX** and expand Picture in Picture. Its Content, Position and Style groups control different parts of the inset. 6. Choose **Open FX Overlay** below the Viewer if you want to drag and resize the inset on screen. 7. Play through the whole overlap. One representative frame is not enough. The speaker may lean out of a crop or cover text later in the shot. ![Resolve 21 Effects and Open FX tabs with Picture in Picture Content, Position and Style controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/pip-native-inspector-real.webp) Official [Blackmagic Design Resolve 21 interface](https://www.blackmagicdesign.com/products/davinciresolve/whatsnew?ref=davinciresolveclub.com), with an editorial checklist. The native effect lives under Effects > Open FX, separate from Video > Transform. With ordinary opaque clips, the upper track covers the lower one wherever they overlap. Before the effect is applied, V2 may fill the Viewer; that is expected. If V1 disappears from the timeline rather than just from the picture, check whether you placed both clips on the same track. Use the [Resolve Inspector guide](https://davinciresolveclub.com/davinci-resolve-inspector/) for a wider reference to Video, Audio and Effects controls. For this task, stay on the selected clip's Picture in Picture effect so that clip-level Transform and effect-level controls do not get mixed up. ## Content versus Position: the control that prevents bad crops The useful distinction is between the source inside the frame and the frame itself. Content changes what you see through the window; Position changes where that window sits. - **Content Zoom** enlarges or reduces the source inside the PiP frame. - **Content Pan** shifts that source horizontally. - **Content Tilt** shifts it vertically. - **Position X/Y** moves the whole window across the finished frame. - **Width and Height** change the outer window dimensions. If the face is too small but the inset already occupies the right amount of screen space, adjust Content Zoom rather than Width and Height. If the framing is good but the inset covers a subtitle or interface button, move Position X/Y. Keeping those jobs separate avoids the repeated resize-and-recrop loop common in older tutorials. Width and Height can also change the window's shape. Judge the result at the delivery aspect ratio. A corner layout designed at 16:9 can obscure important content after a vertical reframing; the [Resolve aspect-ratio guide](https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/) covers the timeline and output decisions that belong outside this effect. ## Make the inset readable without overdesigning it Open **Style** after the content and position are correct. Rounding moves from square corners at its minimum toward a circular window at its maximum. Rotation and Opacity affect the whole inset. Border, Fill and Drop Shadow each reveal their own controls when enabled. ### Create a circular picture in picture Center the face with Content Pan and Tilt, then raise Style Rounding to its maximum, 1\. Check the shape in the Viewer at your delivery aspect ratio. If it looks oval, adjust Width and Height until the visible window is circular. Do not assume matching numeric values guarantee a circle, and do not stretch the person to compensate for the frame. ### Add a border Enable Border, then set Border Width, Border Color and Border Opacity. The best width depends on timeline resolution, window size and background contrast, so there's no defensible universal number. Review at 100 percent Viewer scale and on a phone-sized preview before making the line heavier. ### Add a drop shadow Enable Drop Shadow and adjust Strength, Color, Drop Angle, Drop Distance, Expand and Blur. A shadow should separate similar tones, not look like a second graphic element. Test it over the brightest and darkest frames because one setting may disappear over black and look dirty over white. ### Use Fill only when the source needs it Fill draws a background behind transparent content inside the window. Fill Matches Border uses the border color. Neither is required for an ordinary full-frame video source, and adding Fill by habit can hide transparency you meant to preserve. ## Manual Picture in Picture in Resolve 20 or earlier The manual method is still useful for a plain inset and explains the underlying composite: 1. Place the background on V1 and the inset source on V2. 2. Select V2 and open **Inspector > Video > Transform**. 3. Keep Zoom X and Y linked, then reduce Zoom until the inset is the size you need. The useful value depends on the source and timeline dimensions. 4. Change Position X and Y to move it into a corner. 5. Use Cropping only when content outside the desired window must be removed. 6. Check Composite Opacity and track visibility if the result disappears. ![Manual picture-in-picture Transform controls with linked Zoom and Position keyframes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/pip-manual-transform-real.webp) Blackmagic Design's [manual picture-in-picture interface reference](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com), with an added checklist. These are example values from its illustration, not a preset to copy or a view of the native Resolve 21 effect. This route doesn't provide the Resolve 21 effect's separate Content and Position groups. Zoom changes the whole V2 image rather than zooming inside a fixed PiP boundary. A more complex fixed frame, tracked mask or reusable graphic belongs in the [Fusion beginner workflow](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/), but a basic corner inset doesn't require nodes. ## Animate the inset in and out For a simple fade, keyframe the native effect's **Style > Opacity**. This keeps the animation in Picture in Picture rather than mixing its window controls with clip-level Transform: 1. Select the V2 clip and open Inspector > Effects > Open FX > Picture in Picture. 2. At the first frame of the entrance, set Style Opacity to 0 and click its diamond to store a keyframe. 3. Move the playhead to the frame where the inset should be fully visible, then set the same Opacity parameter to 1\. Resolve adds the next keyframe. 4. For a fade-out, first store another Opacity keyframe at 1 where the exit begins, then move later within the clip and set it to 0\. That extra point holds the inset visible between the fades. 5. Play through the entrance, hold and exit. Use the Curve Editor to select the effect's Opacity curve and adjust the timing or easing if needed. For a slide, use the keyframe diamonds beside the native effect's Position controls; keep Content Zoom for reframing inside the window. With the older manual method, animate Video > Transform instead. The [keyframes and Curve Editor guide](https://davinciresolveclub.com/davinci-resolve-keyframes-curve-editor/) explains how to reveal the right curve and shape the move. A short entrance is usually enough; the frame should not compete with the speaker. ## Why Picture in Picture is missing or looks wrong ### The effect is not in search Check both the installed version and the Effects category. Search within **Resolve FX Transform**, not Video Transitions or Titles. The dedicated effect arrived in Resolve 21; on Resolve 20 or earlier, use the manual Transform method. You do not need to rebuild a project just because a search in the wrong category returns nothing. ### The background is not visible Check track order and timing first: background on V1, inset on V2, both covering the playhead. Confirm V1 is enabled, then check that Picture in Picture is applied to V2 and enabled in the Inspector. A full-size V2 image before applying the effect is normal. ### The Viewer handles move the wrong thing Select the V2 clip, open its effect in the Inspector and switch the Viewer to **Open FX Overlay**. Ordinary Transform controls edit the whole clip; the Open FX overlay edits the PiP window. ### The source moves but the window does not You're changing Content Pan or Tilt. Use Position X/Y to move the outer window. Use Width and Height to change its boundary. ### The Color-page version has a black background For the Color-page route, right-click the node graph, choose **Add Alpha Output**, and connect the Picture in Picture node's blue alpha output to that new graph output. Blackmagic documents this extra connection so the timeline receives transparency instead of a black background. The effect also has a **Use Alpha** checkbox for alpha compositing. If you are learning the effect, the Cut/Edit route avoids this extra node setup. ### The inset covers titles or phone UI Scrub the entire overlap and check the actual delivery frame. Move or resize the window, shorten its duration, or cut back to full screen when the background detail becomes more important. Safe placement is an editorial decision, not a permanent lower-right preset. ![Presenter inset covering an instruction compared with placement that leaves the instruction readable](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/pip-readable-placement.webp) Illustrative placement comparison using Blackmagic Design reference imagery, not an app capture. Keep instructions visible and check the whole shot before settling on a corner. ## Does Picture in Picture work in Resolve Free? Picture in Picture is available in Resolve 21 Free as well as Studio. Blackmagic's manual does not mark it Studio-only, and the release notes for its [free Mac edition](https://apps.apple.com/us/app/davinci-resolve/id571213070?mt=12&ref=davinciresolveclub.com) explicitly list the effect. If you cannot find it, check the installed version and Resolve FX category before assuming you need a paid license. PiP does not require special export settings. It becomes part of the composed timeline image. Use the normal [DaVinci Resolve export workflow](https://davinciresolveclub.com/export-video-davinci-resolve/), then review the rendered file to confirm the inset position, border and shadow survived at delivery resolution. ## DaVinci Resolve Picture in Picture FAQ ### How do I make picture in picture in DaVinci Resolve 21? Put the background on V1 and the smaller source on V2\. Apply Resolve FX Transform > Picture in Picture to V2, then adjust Content, Position and Style in the Inspector. ### Why can I not find Picture in Picture in DaVinci Resolve? The dedicated effect was added in Resolve 21\. Check the installed version and search the Resolve FX Transform category. In Resolve 20 or earlier, scale and position the upper clip with Inspector Transform controls. ### How do I make a circular picture in picture? Center the source with Content Pan and Tilt, set Style Rounding to 1, then adjust Width and Height until the window looks circular at the delivery aspect ratio. Matching numeric Width and Height values is not a reliable substitute for checking the visible shape. ### Can I add a border and shadow without Fusion? Yes in Resolve 21\. The native Picture in Picture Style controls include Border and Drop Shadow with their own width, color, opacity, distance and blur settings. ### How do I zoom inside the PiP without resizing its frame? Use Content Zoom, Pan and Tilt. Those controls reframe the source inside the window. Width, Height and Position X/Y change the outer window. ### How do I animate picture in picture? For a native Resolve 21 fade, keyframe Picture in Picture > Style > Opacity from 0 to 1\. Use its Position keyframes for a slide and the Curve Editor for timing. With the manual method, animate the clip's Transform controls instead. ### Is Picture in Picture available in DaVinci Resolve Free? Yes. The Resolve 21 manual does not mark Picture in Picture Studio-only, and Blackmagic lists it in the release notes for its free Mac edition. If it is missing, check the installed version and the Resolve FX Transform category. ### DaVinci Resolve Keyframes and Curve Editor Guide URL: https://davinciresolveclub.com/davinci-resolve-keyframes-curve-editor/ Last updated: 2026-09-05T13:23:53.000Z **Quick answer:** select the clip, park the playhead where the animation should begin, and click the gray diamond beside an Inspector parameter such as Position X or Zoom. Move the playhead, change that same value, and Resolve creates the second keyframe. Open **Show Keyframe Tray** to move the diamond markers in time, then switch to **Curves** when you need to change values, Ease In and Out, or shape Bezier handles. One keyframe stores a value. Set a second point at another time and change the value to create a simple move. The part that trips people up isn't setting the first diamond. It's choosing the right editor afterward. Keyframe lanes, value curves, the Viewer motion path and Fusion's Spline Editor all solve different pieces of animation. The menu names below were checked on September 5, 2026 against chapter 60 of the [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). This guide covers keyframing on the Cut and Edit pages. The [DaVinci Resolve tutorial hub](https://davinciresolveclub.com/davinci-resolve-tutorial/) can help you choose the next editing skill to learn. ## Choose the control that matches the job | Control | Use it for | What it does not replace | | ----------------------- | --------------------------------------------------------------- | --------------------------------------------------- | | Inspector diamond | Create, delete and jump between keyframes for one parameter | Detailed timing and curve shaping | | Keyframe Editor or Tray | See many parameter lanes, select points, retime, copy and paste | Changing a keyframe's numeric value by graph height | | Curve Editor | Change time and value, interpolation, easing and Bezier handles | Drawing the clip's spatial path in the Viewer | | Viewer motion path | Change the route Position X/Y follows across the frame | Inspecting the full numeric time-and-value graph | | Fusion Keyframes/Spline | Animate nodes inside a Fusion composition | Basic Edit-page Transform animation | If you only need a start and end value, the Inspector may be enough. Open the larger editors when you need to compare parameters, retime several points or remove the mechanical feel of linear motion. The [Resolve Inspector guide](https://davinciresolveclub.com/davinci-resolve-inspector/) explains the other Inspector groups; here, the focus is how to animate their values. ## Create your first two keyframes 1. Place a clip on the Cut or Edit timeline and select it. 2. Open **Inspector > Video** and expand **Transform**. 3. Move the playhead to the first frame where the state must be defined. 4. Set the starting Position, Zoom, Rotation Angle or other keyframable value. 5. Click the gray diamond beside that parameter. It turns orange because the playhead is now on a stored keyframe. 6. Move the playhead to the next moment and change the same value. Once a parameter has its first keyframe, that later change creates another one. 7. Play across the interval and check the actual result before adding more points. ![Resolve Inspector Transform controls with stored Zoom and Position keyframes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/keyframes-inspector-real.webp) The diamond stores a value at the playhead. This [Resolve 20 Inspector reference](https://wpmedia-lj.s3.amazonaws.com/wp-content/uploads/2025/10/Keyframes%5F00105.jpg?ref=davinciresolveclub.com) by Larry Jordan has Zoom and Position keys already set; the same core controls are documented in Resolve 21\. Annotations added for this guide. A gray diamond doesn't mean the parameter has no keyframes anywhere. It means the playhead isn't currently on one. The small previous and next controls beside the diamond move to stored points. Use them before overwriting a value that changes when you scrub. Clicking an orange diamond deletes the keyframe at the playhead. The reset control is broader: resetting a parameter removes all its keyframes. Resetting the whole Transform group can remove animation from several parameters at once, so treat reset as a destructive cleanup command. ## Open the Keyframe Tray, Editor and Curve view On both Cut and Edit, select the animated clip and click **Show Keyframe Tray** on the main timeline toolbar. The tray follows the currently selected clip. Expand the relevant parameter group, then choose the keyframe-lane or Curves view. For a larger panel, click Keyframes at the upper left of the Cut or Edit page. It exposes the same parameter hierarchy; the Curve icon at the upper left switches to the graph. On the Edit page, its Expand control opens the Keyframe and Curve Editor in a separate resizable window. That standalone window isn't available from Cut, so a missing pop-out on Cut is a page limitation, not a broken installation. If you want a keyboard shortcut, open **DaVinci Resolve > Keyboard Customization**, search for **Toggle Keyframe/Curve**, and assign the command for Cut, Edit or the Keyframe Editor. The manual documents customization rather than one universal default, so copying an unexplained shortcut from another editor's layout is unreliable. Use the Parameters menu to reduce clutter. **Display Parameters with Keyframes** hides empty tracks, while **Display Selected Parameters** lets you choose individual video, audio, Open FX or Resolve FX controls. Use the Toggle Curve Visibility icon beside a parameter to show its curve in the graph. This is separate from listing the parameter in the panel. If several curves are visible, click the dim curve you want to make active; Resolve displays several but edits one curve at a time. ## Keyframe Editor vs Curve Editor In keyframe lanes, dragging a diamond left or right changes when the stored value occurs without changing the value itself. Select several points to shift an entire beat or delete a bad section. To reuse a move, copy the selected points, place the playhead where the pasted sequence should begin, and paste with the Keyframe Editor focused. Keyframes can remain beyond a clip's visible extents after trimming; Resolve marks those hidden points with a directional indicator rather than silently deleting them. In the Curve Editor, horizontal movement retimes a point and vertical movement changes its value. Hold Shift while dragging when the correction must stay on one axis. Option-click a curve on macOS to add a point directly, or use the Add Keyframes tool. Standard Cut, Copy, Paste and Delete commands work on selected keyframes. Auto Zoom Graph Height is enabled by default and scales the visible graph around active values. That's a display aid, not an animation effect. Disable it when several parameters have very different ranges and you need manual control of graph height. Blackmagic's feature overview also calls this normalized zoom; Auto Zoom Graph Height is the menu label to look for. ## Make motion smooth with Ease In and Out Linear interpolation changes the parameter value at a constant rate between keyframes. That is correct for a progress bar or mechanical move, but it often feels abrupt when a title, photo or subject is supposed to start and stop naturally. 1. Open Curves and activate the parameter you want to shape. 2. Select the relevant start and end keyframes. 3. Choose **Ease In and Out** for a smooth start and finish, or use the directional Ease controls when only one side should change. 4. Enable Show Handles if necessary, then drag the Bezier handles to control how quickly the value leaves and approaches each keyframe. 5. Play the animation at speed. A pretty graph isn't evidence that the move reads well. ![Linear and eased value curves with identical start and end points](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/keyframes-linear-vs-eased.webp) Illustrative value-versus-time graphs, not an app capture or measured result. The endpoints stay the same; the shape between them changes the rate of movement. You can also right-click the orange Inspector diamond and choose Linear, Ease In, Ease Out or Ease In and Out. That's faster for a simple two-point move. The Curve Editor becomes useful when you need to see the entire change, compare neighboring segments or prevent a handle from creating an unwanted overshoot. ## Motion path shape is not the same as easing When Position X and Y are animated, enable Transform controls in the Viewer to expose the motion path. Right-click a path point and choose Smooth to add spatial Bezier handles. Moving the spatial handles changes the route through the image. The Viewer also has an acceleration handle on a Bezier stem, so it is not limited to reshaping the path. Dots along the path indicate relative speed: closer dots mean slower movement and wider spacing means faster movement. The Curve Editor answers a different question: how the parameter value changes over time. You can draw a curved path around a subject and still have a harsh linear start, or create a straight spatial path with smooth acceleration. Use the Viewer to judge the route in the picture and Curves to inspect how values change over time. For a simple title move, add and style the title first using the [DaVinci Resolve text guide](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/), then animate only the parameters that support the intended entrance. Don't keyframe every available control just because it has a diamond. ## Resolve 21 keyframe tools worth using Blackmagic's [Resolve 21 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) groups several additions that older tutorials can't show: - **Step In:** hold the previous keyframe's value, then jump at the next point. - **Step Out:** jump immediately to the next value and hold it until another point. - **Loop:** repeat the selected keyframe sequence through the clip. - **Ping Pong:** repeat forward, then reverse back and forth. - **Reverse Keyframes:** run the selected order and interpolation backward. - **Shape Box:** stretch or contract a selected group; Option-drag a corner on macOS to skew the selected points. - **Multi-clip editing:** selected stacked clips appear concurrently, while side-by-side selections appear sequentially. ![Resolve 21 Loop Type menu with Ping Pong selected and a repeating forward-reverse curve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/keyframes-ping-pong-real.webp) Select the keys, then choose Option Menu > Loop Type > Ping Pong to repeat the movement forward and backward. Official [Resolve 21 interface illustration](https://www.blackmagicdesign.com/products/davinciresolve/whatsnew?ref=davinciresolveclub.com) from Blackmagic Design, with annotations added. Retime Speed can now use the same Bezier easing family, but speed ramps have extra frame-blending and timing decisions. The [Resolve clip-speed guide](https://davinciresolveclub.com/change-clip-speed-davinci-resolve/) covers those retiming decisions in detail. Here, the key distinction is that Speed curves are not ordinary Position curves. Resolve 21 also lets Edit-page audio keyframes move with subframe, audio-sample accuracy when the timeline is zoomed in far enough. That helps precise clip-volume moves; it doesn't turn visual Transform keyframes into subframe video events. For automatic dialogue/music behavior, the [audio ducking guide](https://davinciresolveclub.com/davinci-resolve-audio-ducking/) explains Ducker, sidechain and AI Audio Assistant choices. ## Why keyframes or curves are not showing ### The wrong clip is selected The Tray follows the current timeline selection. Click the animated clip, not its linked audio, an adjustment clip above it or a neighboring title. ### The parameter is hidden Open Parameters and choose Display Parameters with Keyframes or enable the exact property under Display Selected Parameters. Then turn on its Toggle Curve Visibility icon. A listed parameter can still have its curve hidden. If points are visible but cannot be changed, check the keyframe lock beside the parameter. ### There is only one keyframe One point stores a value, but it does not define an interpolated interval. Add a second keyframe on the same parameter at another time. Two keys with the same value can form a flat line; change the value if you want a simple move, rather than assuming a flat graph is missing. ### The playhead is not on the point The Inspector diamond stays gray between keyframes. Use the previous and next controls or the lane instead of treating gray as proof that the animation vanished. ### The points are outside the trimmed clip Trimming can hide keyframes beyond the current clip edges. Look for the directional indicator, navigate to the point or extend the clip before deciding to rebuild the animation. ### You are looking for Fusion's Spline Editor Fusion effects, titles and generators exposed on Cut/Edit can appear in this Curve Editor. A normal Fusion clip or composition still uses Fusion's own Keyframes and Spline panels. The [Fusion beginner guide](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) explains that node-based workflow. ## Free vs Studio Blackmagic spells out the Cut/Edit Keyframe and Curve Editor workflow without a Studio-only marker, so the core tools apply to Resolve Free and Studio. The effect you animate can still have its own edition restriction. If a specific Resolve FX or AI control adds a Studio watermark or is unavailable, that does not make ordinary Transform, Crop, Composite or clip-audio keyframes paid features. ## DaVinci Resolve keyframes and Curve Editor FAQ ### How do I add keyframes in DaVinci Resolve 21? Select a clip, open the Inspector, place the playhead, and click the gray diamond beside a keyframable parameter. Move to another time and change the same value to create the next keyframe. ### What is the difference between the Keyframe Editor and Curve Editor? The Keyframe Editor exposes parameter lanes and is best for selecting, moving, copying and retiming points. The Curve Editor adds a value graph, interpolation controls and Bezier handles. ### How do I Ease In and Out in DaVinci Resolve? Select the start and end points in Curves and choose Ease In and Out, or right-click the orange Inspector diamond and choose an Ease option. Use handles when the preset shape needs refinement. ### Why are my keyframes not showing? Select the animated clip, show the correct parameter and enable its Toggle Curve Visibility icon. Check that keyframes exist at the times you expect. Two points at different times can form a flat line when their values match; different values are not required just to see a curve. ### Can I open the Keyframe and Curve Editor in a separate window? Yes on the Edit page: use Expand in the Keyframe Editor. Cut offers the panel and timeline Tray but not the separate resizable editor window documented for Edit. ### Does Resolve 21 support looping keyframes? Yes. Select a sequence and use Loop Type for Loop or Ping Pong. Loop repeats the sequence; Ping Pong alternates forward and reverse motion. ### Are keyframes available in DaVinci Resolve Free? The core Cut/Edit keyframe, Curve Editor, easing and loop workflow isn't marked Studio-only. Individual effects or AI controls animated inside it may still require Studio. ### How to Sync Audio and Video in DaVinci Resolve 21 URL: https://davinciresolveclub.com/sync-audio-video-davinci-resolve/ Last updated: 2026-09-05T09:50:26.000Z **Quick answer:** for a camera clip with scratch audio and a matching external WAV, select the pair, or their organized bins, in the Media Pool, right-click, and choose **Auto Sync Audio**. Set **Synchronize Using** to **Waveform**. Enable **Retain embedded audio** when you want the camera scratch track to remain beside the production recording, then click **Sync**. Inspect the associated audio channels, listen around the clap, and check the beginning, middle and end of a long take before editing it into a timeline. That last check matters. Auto Sync can find an initial match; it can't make two unsynchronized recorder clocks run at the same speed. A constant offset, a failed waveform match and drift that grows over time are three different problems. The menu names and sync behavior were checked on September 5, 2026 against the [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). For the surrounding editing steps, the [Resolve Workflow hub](https://davinciresolveclub.com/tag/workflow/) covers ingest, proxies, multicam and project organization. ## Choose the sync method from the reference you actually recorded | Reference available | Resolve method | Best use | | ---------------------------------------------------- | ----------------------------------- | --------------------------------------------------------------------------------- | | Camera and recorder share synchronized timecode | Auto Sync Audio > Timecode | Fast batch sync for organized production sound and Broadcast WAV files. | | Camera scratch audio matches the external recording | Auto Sync Audio > Waveform | Single-camera interviews, podcasts and location work without matching timecode. | | Both clips have a matching In, Out or Marker | Auto Sync Audio > In / Out / Marker | One pair at a time when there is a known clap or cue but waveform analysis fails. | | A visible clap and audio spike | Manual Media-page sync | Precise pair-by-pair control and difficult recordings. | | Clips are already placed on separate timeline tracks | Auto Align Clips | Move overlapping timeline items to the lowest-numbered selected reference track. | Multicam isn't required for one camera and one external recorder. Use the [Resolve multicam guide](https://davinciresolveclub.com/davinci-resolve-multicam-editing/) when the job is synchronizing several camera angles and switching between them; use this page when the primary job is attaching production audio to source video. ## Auto-sync by waveform in Resolve 21 1. Put only the matching camera and audio files in one bin, or multi-select the corresponding video and audio bins. Smaller day or scene groups reduce false candidates and analysis time. 2. Right-click the selected clips or bins and choose **Auto Sync Audio**. 3. Set **Synchronize Using** to **Waveform**. 4. Leave **Use channel number** on Auto for the first test. Choose Mix or the specific channel carrying the useful reference when other channels are silent or noisy. 5. Enable **Retain embedded audio** if you want camera scratch audio available after sync. 6. Enable **Retain Video Metadata** only when the camera's scene/take metadata must win over matching metadata in the audio file. 7. Click **Sync**, note any clips Resolve reports as unmatched, then verify a successful pair. ![Resolve Auto Sync Audio dialog with Waveform, reference-channel selection and retain-audio controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/sync-waveform-real-annotated.webp) Choose the reference channel and enable Retain embedded audio if you need the camera recording. Annotated [Auto Sync interface](https://videomontazher.com/en/lessons/davinci-20/audio-video-sync?ref=davinciresolveclub.com); source: VideoMontazher. The example has retention switched off. Waveform matching needs common recorded sound. A camera file with no usable reference audio cannot supply a match; a muted timeline track is not the same as a silent source file. Heavy clipping or noise can make matching less reliable. Re-recorded ADR won't reliably match the original performance just because the words are the same. ## Retain Embedded Audio vs the old “Append Tracks” wording Older Resolve tutorials often present two commands: replace the camera audio or choose “Based on Waveform and Append Tracks.” The current Resolve 21 dialog expresses that decision with **Retain embedded audio**. - **Retain off:** the newly synced production audio replaces the video clip's previous audio-channel result. - **Retain on:** Resolve adds the production channels while keeping the original camera audio available as additional channels/tracks when the clip is edited. ![Resolve Clip Attributes Audio tab with source channels mapped to the left and right stereo channels](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/sync-channel-check-real-annotated.webp) Clip Attributes is where you check the source-channel mapping. This camera-audio example is not a completed external-audio sync; verify the recorder channels in your own clip. Interface source: VideoMontazher, annotated for this guide. Neither choice deletes the camera source file or external WAV from disk. It changes the audio associated with the synced Media Pool clip. Right-click the synced clip, open **Clip Attributes > Audio**, and inspect the channel mapping instead of assuming a second timeline lane contains the right microphone. ## Batch-sync by timecode Use Timecode when camera and sound recorder were jam-synced or otherwise recorded matching code. Right-click the organized bins, choose Auto Sync Audio, select **Timecode**, decide whether to retain embedded audio and video metadata, then Sync. If several Broadcast WAV files overlap with matching code, Resolve can add each match; the preference **Limit media pool audio sync to first timecode match** in Preferences > User > Editing restricts that behavior when appropriate. Matching numbers do not prove the devices were actually synchronized on set. Spot-check the slate and lips. If the code is consistently wrong, switch to waveform or a marked clap rather than trusting metadata because it looks professional. ## Manually sync a clap in the Media page 1. On the Media page, set the Audio Panel to **Waveform** before selecting the source clips. 2. Select the camera clip and park the Viewer on the frame where the slate closes, a hand clap lands or another sharp visual cue occurs. 3. With the video Viewer parked there, select the matching WAV in the Media Pool. Its waveform opens in the Audio Panel. 4. Scrub the audio to the corresponding sharp spike. Listen to confirm the event; a nearby peak could be room noise rather than the clap. 5. Before linking, open the Audio > Waveform three-dot menu. Set **Retain embedded audio** and **Retain video metadata** according to what you want to keep. 6. Click **Link/Unlink Audio** in the Audio Panel to attach the aligned recording to the video clip. You can also mark matching In points, Out points or Markers on one video/audio pair, then choose **Audio Sync > Auto Sync Audio** and select that point type. Both clips need the same kind of point. This is still a manual identification step, but Resolve performs the final association consistently. ## Sync clips already on the timeline with Auto Align Media Pool Auto Sync changes the source clip's audio association for future edits. **Auto Align Clips** moves items already arranged on the timeline. Put one clip per track, make sure their timecode or waveforms overlap, select them, right-click, and choose **Auto Align Clips > Based on Timecode** or **Based on Waveform**. All selected clips align to the selected clip on the lowest-numbered video or audio track. Clips without overlapping timecode or matching waveforms stay where they are and appear in the warning. When waveform alignment prompts for a reference track, choose the recording whose waveform should be compared. Check the result before continuing to edit. ## Verify the sync before cutting 1. After Auto Sync finishes, note any clips reported as unmatched. 2. Open Clip Attributes and confirm the intended production channels are mapped. 3. Listen to the slate or first hard consonant with camera scratch and production audio both available. 4. Check lips, impacts or another clear event near the beginning. 5. Check identifiable events in the middle and near the end of a long take. An audio badge alone is not a sync check; confirm the recorder channels and listen. ### A fixed offset is not drift If the audio is early or late by the same amount at the beginning, middle and end, correct the fixed offset instead of stretching the recording. Resolve 21 provides **Trim > Slip Audio** commands for whole-frame moves and 1/10-frame subframe moves. Use a clear transient or consonant, make the smallest correction that solves the mismatch, then check all three points again. If a slate is hard to locate in a large shoot, the [Resolve 21 Slate Finder guide](https://davinciresolveclub.com/davinci-resolve-slate-finder-slate-id/) explains how to locate slates and use their metadata. Still listen to the matched result before you start cutting. ## Why Auto Sync fails ### No matching reference audio Waveform sync can't match silence, unrelated room tone or a different performance. Use timecode, matching markers/In-Out points or a manual visual/audio cue. ### The useful sound is on another channel Set Use channel number to the actual scratch channel, or try Mix when one channel contains long gaps. Don't analyze a noisy channel merely because it's channel 1. ### Too many unrelated files are selected Separate media by day, scene or known pair and rerun the failed clips in smaller batches. Resolve's completion warning identifies pairs that need another method; it isn't evidence that every file in the batch failed. ### The clip synced but plays no sound Inspect Clip Attributes, track mute/solo, bus routing and output. If unrelated timeline clips are silent too, leave the sync workflow and use the [Resolve no-audio diagnostic](https://davinciresolveclub.com/davinci-resolve-no-audio/). ## Audio starts in sync, then drifts If the clap matches at the start but lips are late at the end, one offset cannot fix both points. Check an event in the middle, too. A steadily growing gap suggests drift; a sudden jump calls for inspection around that point. Two endpoint checks alone do not tell you which problem you have. ![Camera and recorder waveforms aligned at the start with increasing separation at the middle and end](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/sync-drift-three-checkpoints.webp) Illustrative timing example, not a measured recording: compare several events to distinguish a growing gap from a sudden jump before changing duration. Independent device clocks can cause progressive drift even after a correct starting alignment. Sound Devices explains why [locking recording clocks prevents drift](https://support.sounddevices.com/hc/en-us/articles/44141193080987-Syncing-the-788T-with-External-Video-and-Audio?ref=davinciresolveclub.com). Irregular source timing or dropped/duplicated frames are other possibilities to investigate, not a diagnosis you can make from the file extension. Resolve defaults project audio to 48 kHz and automatically resamples imported audio with other sample rates to the timeline rate. A 44.1-versus-48 kHz difference alone does not establish the cause of drift. A variable-frame-rate phone or screen recording is worth checking when its timing appears irregular, but VFR alone is not proof of a fault. If source timing is implicated, preserve the original and test a constant-frame-rate copy. For a measured, steady rate mismatch, a controlled duration correction may be appropriate. Check several events afterward; one stretch will not repair every discontinuity. ### Only the rendered file is out of sync If the timeline stays aligned but the delivered file doesn't, don't repeat Media Pool Auto Sync. Re-import a short render into Resolve and compare a visible impact or spoken consonant against the source timeline. A correct re-import points toward the external player or delivery path. If the re-import is wrong too, investigate the rendered file and export settings. The [Resolve export hub](https://davinciresolveclub.com/davinci-resolve-export-settings/) helps you check codecs, export audio and delivery settings once the source pair is stable. Don't change the project timeline FPS to repair one drifting take. The [Resolve frame-rate guide](https://davinciresolveclub.com/davinci-resolve-frame-rate/) explains when to set timeline rates. For a single drifting take, investigate the source recordings first. ## Free vs Studio Media Pool Auto Sync, waveform/timecode methods, manual linking and timeline Auto Align are documented without a Studio-only marker. The core workflow therefore applies to Free and Studio. Hardware timecode, recorder accuracy and the quality of camera scratch audio affect the result more than the edition badge. After sync, the [Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) can help with cleanup, EQ, dynamics, buses and loudness. First confirm that the correct recording stays aligned for the whole take; then start mixing. ## DaVinci Resolve audio and video sync FAQ ### How do I auto-sync audio and video in DaVinci Resolve 21? Select the matching camera and audio clips or bins in Media Pool, choose Auto Sync Audio, select Waveform or Timecode, decide whether to retain embedded camera audio and video metadata, then click Sync and verify the result. ### Should I use Waveform or Timecode? Use Timecode when camera and recorder captured genuinely synchronized code. Use Waveform when both files contain the same reference sound. If neither exists, use matching markers/In-Out points or align a visible clap manually. ### What happened to “Based on Waveform and Append Tracks”? Current Resolve 21 presents that choice as Retain embedded audio in the Automatically Sync Audio dialog. Enable it to keep camera audio alongside newly synced production channels. ### How do I sync clips already on the timeline? Put one selected clip per track with overlapping timecode or audio, then choose Auto Align Clips based on Timecode or Waveform. Resolve aligns the selected items to the lowest-numbered selected track. Choose the waveform reference track if prompted, then verify the alignment. ### Why does waveform sync fail? The sources may lack matching sound, the useful reference may be on another channel, or the batch may contain unrelated files. Select the correct channel or Mix, reduce the batch, or use timecode, markers or manual clap sync. ### Why is audio synced at the start but not the end? Check events near the beginning, middle and end. A steadily growing offset suggests drift; a sudden jump may indicate a timing discontinuity. Investigate device clocks and source timing before applying a duration correction. One fixed offset cannot correct a changing gap. ### Does Auto Sync delete the original camera audio? No source media is deleted. Retain embedded audio controls whether the camera channels remain associated alongside the synced production audio. The original camera file and external WAV remain on disk. ### How to Record Voiceover in DaVinci Resolve 21 URL: https://davinciresolveclub.com/record-voiceover-davinci-resolve/ Last updated: 2026-09-05T08:09:30.000Z **Quick answer:** on the Cut page, open the microphone-shaped **Voiceover** tool under the Viewer. Choose the real microphone under **Audio Input**, leave **Record Track** on the new VO track or select your own mono track, and speak once before recording. If the input meter doesn't move, stop there and fix the device or permission; timeline volume can't repair a missing input. Wear headphones, place the playhead or an In point where the line should begin, then click **Record**. That route is enough for narration, scratch tracks and timed pickup lines. Resolve 21 also keeps a compact Voiceover palette on the Edit page, while Fairlight gives you explicit input patching, multiple armed tracks, layers and ADR. The controls below were rechecked on September 5, 2026 against the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com); Blackmagic's support center lists 21.0.4 as the current maintenance release at that check. If you're learning the wider audio path rather than solving this one recording task, the [DaVinci Resolve Fairlight hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) links to recording, cleanup, mixing and delivery guides. ## Choose the recording route before you set up the mic | What you need | Use this route | Why | | ----------------------------------------------------------------------- | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | One narration or scratch track, fast | Cut Voiceover | Current Resolve 21 palette includes input, destination track, monitoring, countdown, recording location and a prompter. | | A compact panel while editing | Edit page: Timeline > Record Voiceover | File name, input, track and Record stay in a small tool; extra options cover monitoring, countdown and stereo input. | | Explicit routing, multiple microphones or preserved layered takes | Fairlight track recording | You patch inputs to tracks, arm the exact tracks, and record from the transport. | | Cue lists, pre-roll, beeps, streamers and repeated dialogue replacement | Fairlight ADR | ADR is a session workflow, not merely another Record button. | Don't build the Fairlight route just because an old tutorial starts there. The simple tool removes several setup steps. Move to Fairlight when you need its control, not because recording a microphone is supposed to be complicated. ## Record a voiceover on the Cut page 1. Open an active timeline and switch to **Cut**. 2. Click the microphone-shaped **Voiceover** icon below the Viewer. 3. Under **Audio Input**, choose the microphone or audio-interface input you are actually using. 4. Under **Record Track**, use the VO track Resolve creates or choose another suitable audio track. 5. Speak at the level you'll use for the take. The miniature meter should respond before you press Record. 6. Choose a monitoring mode, put on headphones, and set a short countdown if you want one. 7. Place the playhead at the start, or set an In point when you want a repeatable cue. 8. Click **Record**, perform the line, then click **Stop**. These Voiceover settings control two different paths: Audio Input decides what Resolve records, while Monitoring decides what you hear during the take. A working headphone mix isn't proof that the selected microphone is reaching the recording track; the input meter is the faster check. The Cut palette offers **Timeline & Microphone**, **Timeline Audio Only**, **Microphone Audio Only** and **Mute Monitoring When Recording**. There's no universally correct choice. A narrator following music may need the timeline in headphones; a laptop user without headphones may need monitoring muted to avoid feedback. Use **No Countdown**, **3 Secs Countdown** or **5 Secs Countdown** based on the performer. The countdown is a visual preparation cue. It does not fix a late script start, room echo or input latency. ## Use the prompter and keep alternate takes The Cut Voiceover tool can load a plain-text `.txt` script and display it over the Viewer. Enable the Prompter Overlay, load the file, then adjust font size, line spacing, side margin and background opacity until the script is readable without covering the part of the frame you need to judge. Set In and Out points around the voiceover range when timing matters. Resolve uses that range to pace the scroll; without it, the script spans the timeline. The **Cue** button returns the playhead to the initial recording In point, so you can repeat a line without dragging the playhead back by eye. ![DaVinci Resolve 21 Cut Voiceover prompter with TXT script, In and Out points, Cue and Record controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/cut-prompter-workflow.webp) A .txt script, In/Out marks and Cue turn repeated narration takes into a controlled timing pass rather than a playhead hunt. After you stop, the playhead returns to the starting position for review. Recording a new take at the same location replaces the earlier clip on the timeline, but Resolve keeps the previous takes in the Media Pool. That is an editorial replacement, not deletion of the recorded media. Name the recording clearly and keep the destination bin selected so useful alternates are easy to find. ## Use the compact Edit-page Voiceover tool On the Edit page, choose Timeline > Record Voiceover or click the small microphone on the Timeline toolbar. Enter a useful File Name, choose the Audio Input, then choose a Record Track. Auto lets Resolve select a track from the current layout; selecting the VO track yourself is easier to verify in a crowded timeline. The three-dot menu adds **Input Monitoring**, a three-second visual countdown, **Mute Timeline Audio While Recording**, **Stereo Input** and **Hide Options**. Blackmagic notes that software input monitoring can have some lag. If the delay pulls your delivery off time, monitor directly through the audio interface when it supports that, or turn software monitoring off while keeping the picture or guide audio you actually need. **Stereo Input** is for a genuinely stereo microphone or stereo source. Most spoken-word microphones are mono. Selecting stereo by habit can create unnecessary channel confusion and is one reason to inspect the recorded clip when speech appears on only one side. ## Move to Fairlight when routing must be explicit Use Fairlight when the simplified palette cannot express the session: several microphones, separate performers, manual input assignments, overlapping takes or a controlled ADR pass. The [official Fairlight overview](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) treats track recording and ADR as full audio-post workflows rather than hidden voiceover preferences. 1. Create or select a suitable mono VO track. 2. Choose **Fairlight > Patch Input/Output**. 3. Set Source to the physical microphone input and Destination to the VO track input, then click **Patch**. 4. Click the track's red **R** button to arm it. An audio track can't be record-armed until an input is patched. 5. Place the playhead, click the transport **Record** button, and watch the waveform draw in real time. 6. Click Stop or press Spacebar, then disarm the track before ordinary playback. ![Fairlight Patch Input/Output with physical input tiles, destination tracks and the Patch button](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/patch-annotated-v2.webp) Select a physical input and a destination track before clicking Patch. Annotated [Patch Input/Output interface](https://videomontazher.com/en/fairlight/recording-adr?ref=davinciresolveclub.com); source: VideoMontazher. Fairlight can designate a default audio input that auto-patches when you arm a track. That's convenient on a stable workstation, but it doesn't replace checking the source shown in the Mixer. Recordings are written under **File > Project Settings > Master Settings > Working Folders > Project media location**, while the selected Media Pool bin determines where the new clips appear inside the project. For cue lists, pre-roll, post-roll, beeps and streamers, open the ADR interface instead of stretching a simple voiceover panel into an ADR session. AI Create ADR Cues is Studio-only. You can build a cue list manually and record ADR without that AI feature. ## DaVinci Resolve voiceover not working: find the first missing signal ![Edit-page Record Voiceover input meter, microphone selector and destination track in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/input-check-annotated-v2.webp) In the compact Edit-page tool, check the input meter, Audio Input and Record Track before recording. Then inspect the saved clip and test playback. ### No meter movement Don't press Record repeatedly. Confirm the microphone is powered and not physically muted, the operating system can see it, Resolve has microphone permission, and the Voiceover Audio Input points to that device rather than a laptop mic or stale interface. Reconnect or reselect the device, then speak again. A dead meter is an input problem; raising clip gain, a track fader or LUFS later in the chain can't create missing samples. ### The meter moves, but no clip appears Confirm an active timeline is open, choose a real Record Track instead of relying on an ambiguous Auto result, verify the recording location is writable and has free space, then perform a five-second test. In Fairlight, confirm the source is patched to the track input, the track is armed, and you pressed the transport Record control rather than only Record Arm. ### A clip exists, but playback is silent A clip exists, but it may contain silence. Inspect its waveform first. If there is no recorded signal, return to the input checks; if speech is visible in the waveform, check clip mute, track Mute/Solo state, track fader, bus assignment and output device. If other clips are silent too, move to the broader [Resolve no-audio diagnostic](https://davinciresolveclub.com/davinci-resolve-no-audio/). If only the VO track disappears between the Mixer and speakers, the [Fairlight bus-routing guide](https://davinciresolveclub.com/fairlight-bus-routing/) walks through that signal path. ## Fix echo, feedback and delayed monitoring Feedback happens when a live microphone hears its own monitored output through speakers and sends it back into the system. Use headphones, lower the monitor level, or choose a monitoring mode that doesn't return the mic to speakers. Muting the timeline isn't the same as muting microphone monitoring; decide which signal is causing the loop. A delayed copy of your voice is monitoring latency. The Edit tool explicitly warns that Input Monitoring can have lag. Reduce the audio buffer only if the system remains stable, use direct hardware monitoring when the interface provides it, or disable the software return. Don't drag a correctly recorded clip earlier just to compensate for a delay you heard only in headphones; compare the waveform with the picture first. ## Fix voiceover that plays in only one ear Start at the source format. A single spoken-word microphone normally belongs on a mono track. If a mono signal was recorded into only one side of a stereo clip, inspect Clip Attributes and map the active channel deliberately, or rerecord to a mono destination when practical. Do not duplicate the active channel until you have confirmed the file really contains one valid side rather than a damaged cable or wrong interface input. If the source channels are mapped correctly but playback still favors one side, check the track pan and bus format. “Only one ear” is a symptom shared by source mapping, track panning and output routing; the waveform and meters tell you which stage owns it. ## Fix a voiceover that is too quiet without clipping it Set the microphone or interface preamp so ordinary speech produces a healthy meter with room for louder words. There's no single record level that fits every voice, microphone and delivery specification. Avoid clipping at the input; lowering a clipped timeline clip can't restore the lost peaks. After recording, separate cleanup from loudness. Clip gain and the track fader set level, EQ changes tone, dynamics controls range, and the final loudness check belongs near delivery. Use the [Voice Isolation versus Dialogue Leveler guide](https://davinciresolveclub.com/voice-isolation-vs-dialogue-leveler/) only after you have a real recording; Voice Isolation is Studio-only and neither tool replaces microphone placement. Then use the [Resolve LUFS and audio-level guide](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/) for the destination measurement rather than chasing a generic recording number. ## DaVinci Resolve Free vs Studio for voiceover The base Cut/Edit Voiceover recording controls and Fairlight track-recording workflow are documented without a Studio-only marker, so the live-microphone task applies to Free and Studio. Studio adds AI capabilities around the recording workflow; Voice Isolation is explicitly Studio-only. AI Speech Generator creates speech from text; you don't need it to record your microphone. For a wider beginner route through the application, return to the [DaVinci Resolve tutorial hub](https://davinciresolveclub.com/davinci-resolve-tutorial/). For this task, the useful finish line is smaller: the correct microphone moves the meter, the take appears on the intended track, and the recorded waveform plays through the expected bus. ## DaVinci Resolve voiceover FAQ ### How do I record a voiceover in DaVinci Resolve 21? Open the Cut page Voiceover tool, choose the microphone under Audio Input, choose a VO track, confirm the meter moves, wear headphones, place the playhead or an In point, then press Record. The Edit page offers a compact version under Timeline > Record Voiceover. ### Why is DaVinci Resolve not recording my microphone? If the Voiceover meter doesn't move, check the physical mic, operating-system input, microphone permission and Audio Input selection. If the meter moves but no clip appears, check the destination track and recording location; in Fairlight, also verify input patching and Record Arm. ### Can I record voiceover in the free version of DaVinci Resolve? Yes. The base Voiceover and Fairlight recording workflows are documented without a Studio-only restriction. Some AI cleanup tools differ by edition; Voice Isolation is explicitly Studio-only. ### Why can I hear my voice with a delay while recording? That delayed return is monitoring latency. Use direct monitoring on the audio interface when available, reduce the buffer only if the system stays stable, or disable software Input Monitoring. Don't move the recorded clip until the waveform proves the recording itself is late. ### Why is my voiceover only in one ear? A mono microphone may have been recorded or interpreted as one side of a stereo clip. Check the source channels, Clip Attributes, track format and pan. Use a mono track for a normal single-microphone narration unless the source is genuinely stereo. ### Where does DaVinci Resolve save voiceover recordings? The Cut Voiceover palette has a Voiceover Recording File Location setting. Fairlight recordings use the Project media location under Project Settings > Master Settings > Working Folders, while the selected Media Pool bin controls where the new clips appear inside the project. ### Should I use Voiceover or ADR in Fairlight? Use Voiceover for narration, scratch tracks and simple timed pickups. Use Fairlight ADR when you need cue lists, pre-roll/post-roll, beeps, streamers, repeated performances and a controlled dialogue-replacement session. ### DaVinci Resolve Export Looks Washed Out: Fix Color & Gamma URL: https://davinciresolveclub.com/davinci-resolve-export-looks-washed-out/ Last updated: 2026-09-05T04:04:33.000Z **Quick answer:** don't add contrast or change every Rec.709 setting yet. Render ten seconds from a shot with clear blacks, midtones and highlights, re-import that file into Resolve, align it with the original, and compare the same frame on the waveform. If the re-imported render is also flatter or brighter, inspect the output transform and Data levels. If it matches inside Resolve but looks washed out only in QuickTime, Safari or another player, the encoded image may be fine and the difference may come from display color management or file tags. This distinction saves the grade. A player mismatch, a range mismatch and a missing output transform can all look like lifted blacks and lower saturation, but they aren't fixed by the same control. The menus and behavior below were rechecked on September 5, 2026 against the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). Blackmagic's [support center](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) lists Resolve 21.0.4 build 5 as the current maintenance release at that check. If you still need the full render sequence, format, codec, range, audio and queue, start with the [complete Resolve 21 export guide](https://davinciresolveclub.com/export-video-davinci-resolve/). The [DaVinci Resolve export hub](https://davinciresolveclub.com/davinci-resolve-export-settings/) then routes you to destination-specific settings and failure checks. This page owns one narrower job: proving why the finished image no longer looks like the timeline. ## The two-minute proof test 1. Choose a short section with a dark area, a face or neutral object, and a controlled highlight. Do not test only a title card or a fully black frame. 2. On the Deliver page, make a ten-second test using the same settings as the problem job. 3. Import the rendered file into the Media Pool and place it above the original in a duplicate timeline. Align the same frame before judging it. 4. Toggle between the original and re-import, then compare the waveform as well as the viewer. Compression can introduce small differences; you're looking for a material lift, crush or transform. 5. Play the same local file in the destination that looked wrong. Now you know whether the difference exists in the file, only in the player, or only after upload. ![DaVinci Resolve Color page comparing an original timeline frame with a re-imported render on the waveform](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/reimport-scope-test.webp) Render, re-import, align the same frame, then compare the waveform. If the re-import materially matches, test the playback path before changing the grade. A still captured from the Resolve viewer and a screenshot from QuickTime are weak evidence because each window can pass through a different display path. Re-importing the actual file brings the comparison back into one application. It does not prove that every metadata field is correct, but it separates a changed image from a changed interpretation. ## Use the failure location, not the visual adjective | What you observe | Most useful first check | Do not start with | | -------------------------------------------------------- | -------------------------------------------------------------------------------------- | --------------------------------- | | The re-import is also brighter, flatter or crushed | Output transform, Deliver Data levels, and the re-imported clip's level interpretation | QuickTime-only preferences | | The re-import matches, but QuickTime or Safari differs | macOS viewer color profile behavior and QuickTime-oriented file tags | Regrading the timeline | | The local file matches, but the processed upload differs | Platform processing status, embedded tags, SDR/HDR handoff and another playback path | Raising bitrate to repair gamma | | Only one source clip is wrong before and after export | That clip's input color space, camera transform and clip Data Levels | Changing the whole project output | | The job stops or reports an error | The exact error and failing frame | Color or gamma settings | ![Four-branch diagnostic for washed-out Resolve exports, QuickTime playback, uploads and individual clips](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/washed-out-diagnostic-map.webp) The same symptom can begin in four different places. Prove the branch before touching the grade. When the job fails to complete, leave this color diagnostic and use the [render-failed checklist](https://davinciresolveclub.com/davinci-resolve-render-failed/). A stopped job and a completed file with different color are separate intents. ## If the re-imported render is also washed out This is the encoded-file branch. Start with **Project Settings > Color Management**. In a color-managed project, the Output color space defines the destination mapping. In a manual CST workflow, the final output transform must be present exactly once. A missing transform can leave log footage flat; a second transform can push contrast and color the other way. Don't rebuild the project's color pipeline inside this troubleshooting page. The [RCM, CST and LUT-order guide](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/) owns that decision. Here, the test is smaller: bypass nothing, change nothing, and confirm whether the timeline already has one coherent input-to-output path. If the source looks wrong inside Resolve before export, the export is preserving a problem that began earlier. Next open **Deliver > Custom Export > Video > Advanced Settings**. Resolve documents **Data levels: Auto** as the normal starting point because Auto chooses the range associated with the selected codec. Video and Full are overrides, not quality levels. Full doesn't mean “more dynamic range,” and Video doesn't mean “lower quality.” They describe how the signal is mapped into the file. ![DaVinci Resolve 21 Deliver Advanced Settings with Data levels, Color Space Tag and Gamma Tag](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/deliver-advanced-settings.webp) Data levels changes the encoded range; Color Space Tag and Gamma Tag are metadata. Keep those jobs separate while testing. If the re-imported waveform shows lifted blacks or crushed highlights, render the same short section with Data levels set to Video, then Full. Change only that one control. Re-import both tests and label them clearly. Also inspect the re-imported clip under **Clip Attributes > Video > Data Levels**; do not override the export and the clip interpretation at the same time or the test stops telling you which side was wrong. For Deliver-page output, Resolve describes 10-bit Video-range luma as 64–940 and Full output as 4–1019\. Those numbers explain why a mismatch can lift blacks or crush extremes. They are not a reason to force Full for every computer file. ## Data levels and color tags are not the same fix **Data levels** controls how image values are written. **Color Space Tag** and **Gamma Tag** are metadata that compatible software can use to interpret the file. Changing a tag does not insert the missing creative grade or replace a CST. Changing Data levels isn't a way to tell QuickTime which display gamma you intended. For QuickTime renders, Resolve bases the tags on the Timeline Color Space when Resolve Color Management is disabled and on the Output Color Space when it's enabled. The Deliver controls default to **Same as Project**. That makes the project output setting the first thing to inspect when a file carries an unexpected tag. A safe comparison changes one layer at a time: 1. Keep Data levels at Auto and test the project-matched tags. 2. If the re-import matches but a target player differs, make a tag-only test for that destination. 3. If the re-import itself differs, return to the encoded range or output transform before touching display preferences. ## If only QuickTime or Safari looks washed out on a Mac Resolve 21 exposes three separate controls under **DaVinci Resolve > Preferences > System > General** on macOS: - **Use Mac Display Color Profile for viewers** lets Resolve viewers use the display profile selected in macOS through ColorSync. - **Viewers match QuickTime Player when using Rec.709 Scene** changes the Resolve viewer so its gamma characteristics match QuickTime Player for that case. - **Automatically Tag Rec.709 Scene Clips as Rec.709-A** changes tagging for Rec.709 QuickTime files; Blackmagic describes it as useful when the QuickTime result does not match Resolve and the destination is web rather than broadcast. ![DaVinci Resolve 21 macOS General preferences for display profiles, QuickTime matching and Rec.709-A tagging](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/mac-quicktime-preferences.webp) These controls affect different layers. Test one at a time; they are not a universal preset to enable as a group. The first two affect what you see in Resolve's viewer. The third affects how qualifying files are tagged. That's why enabling all three at once produces a useless test: the reference and the output interpretation move together. Rec.709-A is a destination-specific branch, not a synonym for “correct Rec.709.” If the master must work across televisions, Windows systems, review platforms and macOS applications, compare the same file in those real destinations before choosing a tag. Don't bake extra contrast into the grade merely to make one Mac player resemble the Resolve viewer; that contrast becomes part of the image everywhere else. ## If the local file matches but YouTube looks different First wait until the intended resolution has finished processing. Then compare the processed upload with the local file in more than one playback path. If the local file already differs in Resolve after re-import, YouTube isn't the first failure. If the local file matches and only the processed upload changes, inspect the embedded primaries, transfer and matrix tags and confirm that an SDR project wasn't delivered as an ambiguous HDR file. Bitrate can create blocking, banding and softness; it doesn't normally explain a global gamma lift. The [YouTube export settings guide](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/) owns the current codec, bitrate, audio and SDR/HDR upload details. Keep this page focused on the color handoff. ## Washed-out export on Windows The same re-import test still works. QuickTime-specific macOS preferences aren't the first branch, but output transforms, Data levels, file tags, HDR-to-SDR handling and player behavior still matter. Compare the file in Resolve and at least one other current player. If Resolve and the waveform match while one player differs, don't force Full range or rebuild the grade until another destination confirms the same shift. If only one camera or screen recording looks flat inside Resolve, inspect that source rather than the Deliver page. Mixed SDR and HDR captures, log media without an input transform, and clips interpreted at the wrong range can create a “washed-out export” that was visible before the render. Use the [waveform and RGB Parade guide](https://davinciresolveclub.com/davinci-resolve-scopes-explained/) to compare exposure and channels without trusting two differently managed windows. ## Check the SDR/HDR boundary An HDR timeline delivered as SDR needs an intentional output transform or tone-mapping path. An SDR timeline shouldn't acquire HDR tags by accident. Check the project output color space, the actual target specification, the codec's bit-depth support and the rendered file metadata together. Don't solve an HDR handoff by selecting a different Rec.709 gamma at random. When the source is phone, console or screen-capture media, verify whether it's SDR, PQ or HLG before grading. A file that looks washed out on import and stays washed out after export belongs to input and color-management diagnosis, not to an export-only tag fix. ## Five fixes that usually destroy the diagnosis - **Adding contrast before the re-import test.** This changes the image to compensate for an unproven display path. - **Forcing Full because it sounds higher quality.** A wrong range override can create the exact lift or crush you're trying to remove. - **Setting Rec.709-A everywhere.** It's a specific Mac/QuickTime/web branch, not a universal delivery standard. - **Changing project output, CST nodes, Data levels and tags in one render.** Even a good-looking result won't tell you which change mattered. - **Comparing screenshots from different applications.** Re-import the file and compare the same frame and scopes first. ## Free vs Studio The core test and the relevant project, Deliver and macOS viewer controls are available in the Resolve workflow documented without a Studio-only restriction. Codec and hardware-encoding choices still vary by operating system, edition and installed hardware, so make the short test with a codec your installation actually exposes. Studio doesn't remove the need to identify the output transform, range and playback destination. ## Washed-out DaVinci Resolve export FAQ ### Why does my DaVinci Resolve export look washed out? The common branches are a missing or duplicated output transform, a Video/Full data-level mismatch, player or display color management, incorrect color/gamma tags, or an SDR/HDR handoff problem. Re-import a short render and compare the same frame and waveform to identify the branch before changing the grade. ### Should I set DaVinci Resolve Data Levels to Auto, Video or Full? Start with Auto because Resolve normally selects the range appropriate to the codec. If the re-imported file shows lifted blacks or crushed highlights, test Video and Full separately on the same short range. Do not treat Full as a quality upgrade. ### Does Rec.709-A fix washed-out exports on a Mac? It can be useful in a Mac/QuickTime-oriented web workflow, but it isn't a universal Rec.709 fix. First prove that the re-imported image matches and that the difference appears only in the target playback path, then test the tag across the destinations that matter. ### Why does the export match in Resolve but not in QuickTime Player? The encoded image may match while QuickTime and Resolve use different display or gamma interpretation. Check Resolve's macOS display-profile and QuickTime-matching preferences separately from file tagging, and change only one layer per test. ### Why does my local export look correct but YouTube looks washed out? Confirm that processing has finished, compare more than one playback path, and inspect the file's SDR or HDR tags. A correct local re-import narrows the issue to metadata, platform processing or playback rather than the creative grade. ### Can I fix the problem by adding contrast before export? Only if the image itself is intentionally under-contrasted. Adding contrast to compensate for one player changes the encoded image for every destination. Run the re-import test first so a display difference doesn't become a permanent grading error. ### Why is only one clip washed out after export? If the same clip also looks wrong in Resolve, inspect its input color space, camera transform and Clip Attributes Data Levels. A one-clip problem rarely justifies changing the whole project's output color space or every render tag. ### DaVinci Resolve Render Cache: Smart vs User Guide URL: https://davinciresolveclub.com/davinci-resolve-render-cache/ Last updated: 2026-09-05T03:54:05.000Z **Quick answer:** choose **Playback > Render Cache > Smart** when you want Resolve to identify expensive clips and effects automatically. Choose **User** when you want deliberate control over the clips, Color nodes and effects that get cached. A red cache bar means the range is waiting to be cached; blue means the cached result is ready. Wait for blue, then replay the same range before deciding whether cache solved the problem. Render Cache creates temporary working media with processor-heavy operations already calculated. Resolve can play that media instead of rebuilding the live effect, grade or composition on every frame. It's useful for a difficult section of a timeline. It isn't a replacement for good source-media handling, and it doesn't prove that every playback problem is a cache problem. If the whole timeline is slow before you add effects, start with the [slow-playback diagnostic](https://davinciresolveclub.com/davinci-resolve-slow-playback/). If you need lightweight files that travel between workstations, use the [Proxy Media workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/). This guide stays on one job: controlling Resolve 21's render cache without turning the project into a pile of mystery files. ## The 60-second Render Cache setup 1. Open the timeline and mark a short range that fails consistently. 2. Choose **Playback > Render Cache > Smart**. 3. Play the range once, or stop working long enough for background caching to begin. 4. Watch the thin cache indicator along the bottom of the timeline ruler. 5. When the relevant red section turns blue, replay exactly the same range. That's a test, not a permanent configuration. If Smart caches far more than you need, or misses the one operation that's actually expensive, choose **Playback > Render Cache > User** and flag the relevant clip, node or filter yourself. On the Edit and Color pages, **Option-R** cycles through Off, Smart and User, but the menu is easier to verify when you are learning the system. ![DaVinci Resolve 21 Playback menu with Smart Render Cache and red and blue cache bars on the timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-cache-status.webp) Red is queued to cache; blue is ready. Judge the result only after replaying the same blue range. ## Smart vs User: choose by control, not by computer speed | Mode | What Resolve does | Best first use | Watch for | | --------- | ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | **Smart** | Automatically targets formats, grades and timeline operations Resolve considers expensive. Manual cache flags still work. | A quick test, a mixed timeline, or a machine that needs broad playback help. | It may cache more media than you expected, and it does not guarantee that every expensive operation will be the right target. | | **User** | Caches the clips, nodes and filters you flag. Project settings can still automate transitions, composites and Fusion effects. | A predictable workflow where most of the timeline is already real time and only specific operations need help. | “User” does not always mean “nothing automatic.” Inspect the User Mode automation checkboxes. | | **Off** | Disables Render Cache playback for the project. | A control test when cached playback is stale, corrupt or slower than the live result. | Turning cache off does not delete the stored files. | My practical rule is simple: start with Smart for one repeatable range. If the result is useful but the behavior is too broad, move to User and cache only the expensive boundary. Don't switch modes while comparing different ranges; you'll not know whether the mode or the content changed the result. In **File > Project Settings > Master Settings**, the Optimized Media and Render Cache group includes automatic User-mode options for transitions, composites and Fusion effects. The controls were rechecked on September 5, 2026 against the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) identifies automatic Fusion-effect caching as enabled by default. Check the actual boxes in your project instead of relying on a preset you remember from another timeline. ## The three cache levels Resolve manages The menu makes Render Cache look like one switch. Underneath, Resolve manages three different cache levels. Choosing the correct level matters because it determines which work is baked into the temporary media and which work remains live and editable. ![Diagram of DaVinci Resolve Fusion Output, Node and Sequence cache levels in the processing flow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-cache-three-levels.webp) Cache the expensive stage, not the entire project by reflex. Later stages can remain live when you cache at the right boundary. ### Fusion Output Cache: before the Color page Fusion Output Cache is the pre-Color cache. In Smart mode, Resolve can use it for processor-intensive source formats such as H.264, H.265 and supported camera-raw media, for speed effects, and for clips that contain Fusion work. In User mode, select one or more clips in the Edit timeline or Color-page thumbnail timeline, right-click, then choose **Render Cache Fusion Output > On**. Use this level when the expensive work happens before the grade. It's also the first manual target when a Fusion composition is the clear playback boundary. If the clip is still difficult after its Fusion Output cache is blue, the remaining cost may be in an Edit-page filter, the Color graph, a layer above it, storage, or another part of the playback chain. ### Node Cache and Color Output: inside the grade On the Color page, right-click a node and choose **Node Cache > On**. Resolve caches that node together with the upstream nodes feeding it. This is the precise choice for an expensive early operation such as temporal noise reduction: cache the costly foundation, then keep the downstream look adjustments live. **Render Cache Color Output** isn't a fourth independent level. It uses the Node Cache to store the whole Color-page output for a clip. Right-click the clip in the Edit timeline or Color thumbnail timeline and enable Render Cache Color Output. This is useful when the entire grade is finished enough to bake temporarily. Any change that affects the grade can require the whole result to be cached again. ### Sequence Cache: Edit-page timeline work Sequence Cache handles timeline operations such as transitions, opacity changes, adjustment layers, composite modes and speed or retime effects. You don't flag Sequence Cache clip by clip. Smart mode handles it automatically. In User mode, the project-level transition and composite checkboxes decide which categories can cache automatically; tracks that should stay live can be excluded from caching from the track-header context menu. Edit-page Resolve FX and OFX filters have their own manual control. Right-click the clip, open **Render Cache OFX Filter**, and select the expensive filter. That's more predictable than baking every operation on the clip when only one filter misses real time. ## What the red and blue cache bars actually tell you The thin indicator along the bottom of the timeline ruler is a status signal: - **Red:** this part of the timeline is marked to be cached. - **Blue:** Resolve has cached this part of the timeline. - **No bar:** the range may not be marked for cache at the current mode and item settings, or it doesn't need the type of caching you expected. Resolve can build cache while you play a red range. It can also begin after the project has been idle for the number of seconds set under Master Settings. The interval is configurable, so “wait five seconds” isn't a universal instruction. A blue bar isn't permanent. Change an upstream operation and the old cached result is no longer valid; Resolve turns the affected range back into work that must be calculated. That rebuild is normal. A cache that repeatedly invalidates without a relevant edit is a different problem and should be tested with one change at a time. ## Set cache format and location before a large project Open **File > Project Settings > Master Settings**. The two settings that matter most are separated on the page: - **Render Cache Format** is in the Optimized Media and Render Cache group. - **Cache files location** is in Working Folders. ![DaVinci Resolve 21 Project Settings showing Render Cache Format, background caching and Cache files location](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-cache-settings.webp) Format controls quality and throughput; the working folder controls where the generated cache occupies disk space. Choose a cache format that the editing machine can decode smoothly and the cache drive can sustain. The available codec list varies by operating system. ProRes and DNxHR families are common working choices; the correct tier depends on whether the cache is only for editorial playback or may be used in a finishing or delivery path. For HDR, alpha or out-of-bounds image data, a casually chosen lightweight format can be the wrong compromise. Blackmagic lists 16-bit float, ProRes 4444 or 4444 XQ, and DNxHR 444 among the formats appropriate when that signal must be preserved. Those are not automatic recommendations for every offline edit. They trade more storage and throughput for a higher-fidelity working result. The cache location defaults to the first scratch disk listed under Preferences > System > Media Storage. If no scratch disk is configured, Resolve can fall back to the system disk. Use a fast, consistently mounted volume with enough free space. A fast codec written to a full, sleeping or disconnected drive is still a broken cache workflow. If codec decode, GPU memory or storage throughput remains the bottleneck, use the [Hardware & Compatibility hub](https://davinciresolveclub.com/davinci-resolve-hardware-compatibility/) to isolate the machine-side constraint. ## Render Cache not working: test in this order Don't start by deleting every cache file. First prove which gate is failing. 1. **Verify the global mode.** Playback > Render Cache must be Smart or User, not Off. 2. **Verify the target.** In User mode, set the intended Fusion Output, node or OFX filter to On. For Sequence Cache behavior, inspect the project-level User Mode checkboxes. 3. **Trigger the cache.** Play the red range or leave Resolve idle long enough for the configured background interval. 4. **Watch the same range.** If no red bar appears, the item isn't being targeted the way you think. If red appears but never progresses, continue to storage and processing checks. 5. **Check the working folder.** Confirm that Cache files location exists, is writable, remains mounted and has free space. 6. **Run a scoped reset.** Select the problem clip and choose Playback > Delete Render Cache > Selected Clips. Let only that range rebuild. 7. **Compare cache Off.** If live playback is better, the chosen cache format, drive or target is adding overhead. Do not assume that more caching must be faster. 8. **Leave the cache topic when the evidence does.** A blue range that still cannot play smoothly points to another bottleneck. Return to the broader [playback test sequence](https://davinciresolveclub.com/davinci-resolve-slow-playback/) instead of rebuilding the same cache again. If a cache command is missing, greyed out or appears disabled, check the selection before changing preferences. Fusion Output and Color Output controls apply to clips selected in the Edit timeline or the Color-page thumbnail timeline; Node Cache applies to a selected Color node. Sequence Cache has no manual clip command because Resolve controls that level automatically. A Media Pool clip or an unrelated page won't expose the same context menu. ![Five-step DaVinci Resolve Render Cache troubleshooting path from mode and target to storage and selected-clip reset](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-cache-troubleshooting.webp) Change one variable, rebuild one range, then replay that same range. A full-project reset should not be the first move. If cached media appears offline, test the selected clip with cache Off, then clear and rebuild only that clip. If the original source is also offline, cache cleanup won't repair the media path; use the [Media Offline relinking checks](https://davinciresolveclub.com/media-offline-davinci-resolve/). If the problem occurs only in the Deliver queue with an error message, follow the [Render Failed diagnostic](https://davinciresolveclub.com/davinci-resolve-render-failed/) and keep the cache test scoped to the failing range. ## Clear cache without treating every file as disposable Render Cache is persistent. Closing the project does not remove it. Under **Playback > Delete Render Cache**, Resolve 21 offers three useful scopes: - **Selected Clips** rebuilds only the clips you have selected. Use it for one stale or suspect result. - **Unused** removes cache data that no longer corresponds to current timeline clips or effects. Use it for routine space recovery. - **All** resets the current project's entire render cache. Use it only when the scope really is the whole project or the other two choices can't isolate the problem. **Playback > Manage Render Cache** opens the Cache Manager for projects across accessible project libraries. The current manual warns that clearing selected cache there has no warning dialog or undo. Read the project and library columns twice before clicking the destructive button. For ongoing maintenance, **Preferences > User > Cache Management** can delete local cache older than a chosen number of days. That is useful on a constrained scratch drive, but it isn't a substitute for choosing the right working folder or keeping active project cache available. ## Should you use cached images for export? In the Deliver page's Video settings, **Use Render Cached Images** can write from cached media instead of calculating the effects again. This may save render time, but it also makes the cache format part of the output-quality chain. If the cache was created in a lightweight editorial format, contains stale frames or was never checked at delivery quality, leave the option off and render from the live source and effects. Use cached images only when you deliberately chose a suitable cache format, the complete delivery range is blue, and you have inspected the result. A successful timeline playback test is not automatically a mastering decision. ## Where Render Cache belongs in the workflow Render Cache is strongest when a timeline is already organized and one processing stage can't meet real time. It's project-managed, replaceable working media tied to the current computed result. Proxy Media is portable and tied to source clips. Optimized Media helps Resolve use easier-to-decode source media on the workstation. Timeline Proxy Resolution changes working resolution without generating those files. Those tools can work together, but they shouldn't be switched on as a ritual. Pick the tool that matches the boundary you can prove. The [DaVinci Resolve workflow hub](https://davinciresolveclub.com/tag/workflow/) organizes the next steps by job; the [Resolve troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/) is the better route when the symptom is wider than cache. ## DaVinci Resolve Render Cache FAQ ### Should I use Smart or User Render Cache? Use Smart for an automatic first test or when many different effects need help. Use User when most of the timeline already plays in real time and you want to cache specific clips, nodes or filters. Remember that project settings can still automate transitions, composites and Fusion effects in User mode. ### Why does the red cache bar never turn blue? Check that Render Cache is Smart or User, verify the item-level cache target, play the range or wait for the configured background interval, and confirm that the cache drive exists, is writable and has free space. Then delete cache for Selected Clips and rebuild one range. ### Why did a blue cache bar turn red again? Resolve invalidates cached media when an upstream operation changes. A grade, Fusion composition, filter, retime or timeline edit can require the affected result to be rebuilt. That's normal when the edit actually changed the cached processing path. ### Where does DaVinci Resolve store render cache files? The project uses the Cache files location under Project Settings > Master Settings > Working Folders. Its default comes from the first scratch disk in Preferences > System > Media Storage; without a configured scratch disk, Resolve can use the system disk. ### Can I safely delete Render Cache? Yes. Render Cache is generated working media, not the camera originals. Delete Selected Clips for a scoped rebuild, Unused for routine cleanup, or All for a complete current-project reset. Resolve must calculate deleted cache again when it is needed. ### Is Render Cache the same as Proxy Media? No. Render Cache stores computed timeline, Fusion and Color results for playback. Proxy Media creates linked, portable versions of source clips for easier editing and handoff. Use the dedicated proxy workflow when files need to move or be relinked. ### Does Render Cache change export quality? Ordinary cached playback does not force the Deliver page to use cache. If you enable Use Render Cached Images, the chosen cache format becomes part of the output path. Use a suitable high-quality format and inspect the cached range before relying on it for delivery. ### Remove Objects in DaVinci Resolve: Object Removal Guide URL: https://davinciresolveclub.com/remove-objects-davinci-resolve/ Last updated: 2026-09-05T03:39:33.000Z Object Removal works by searching neighboring frames for background that the masked subject hides. It is fast when a small object crosses a stable surface that becomes visible elsewhere. It is the wrong first choice when a person blocks unique scenery for the whole take, a moving reflection has to disappear too, or the repair crosses another foreground subject. If this repair belongs to a wider grade, the [Color task map](https://davinciresolveclub.com/davinci-resolve-color-grading/) keeps tracking, correction and cleanup in order. Object Removal is a DaVinci Resolve Studio feature. The simplest current Color-page workflow keeps a tracked Power Window and the Object Removal effect on the same Corrector node, then runs Scene Analysis. A separate matte node feeding a key input can be useful in an advanced node tree, but it's optional, not a required Blackmagic step. The controls below were rechecked on September 5, 2026 against the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com). ## Choose the removal method from the shot | Problem | Best first method | Why | | ---------------------------------------------------- | ---------------------------------------------------- | ----------------------------------------------------------------- | | Small object crosses a background revealed elsewhere | Object Removal in Studio | Temporal analysis can borrow clean background from nearby frames | | Fixed sensor spot, sign, or blemish | Patch Replacer in Studio | A controlled clone source may be cleaner than scene-wide analysis | | Face or license plate only needs privacy | Tracked blur or mosaic | No invented background is required | | Large foreground subject against a changing scene | Rotoscope plus a separate clean plate or replacement | The original may never reveal enough background | | Object touches the frame edge | Crop, reframe, cover, or manual paint | Temporal fill often lacks boundary information | | Complex parallax, reflection, or moving shadow | Segmented masks and Fusion cleanup | One automatic pass cannot model every interaction | ## Inspect the entire shot before drawing a mask Scrub from the first frame to the last and answer four questions: 1. Does every part of the hidden background appear clean in another frame? 2. Does the object cast a shadow, reflection, or color spill that also needs removal? 3. Does the background have parallax, water, smoke, crowds, foliage, or repeating motion? 4. Does the object cross another foreground subject that must remain? If the background is never visible, Scene Analysis has no authentic detail to recover. Use a separately photographed clean frame, a controlled neighboring patch, another take, a crop or a designed cover. For privacy, a tracked blur can be more honest and more stable than invented scenery. ![DaVinci Resolve Color page Power Window drawn closely around an unwanted person](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-power-window-object-mask-real-ui.webp) Real Resolve Studio 19 Color page captured by Envato. Keep the Window close to the unwanted subject, include motion blur and soften the edge just enough to avoid a hard cutout. ## Build a clean node structure Work on the Color page and duplicate the timeline or create a new grade version before changing the shot. For Blackmagic's simplest documented setup: 1. Create or choose one Corrector node for the repair. 2. Draw a close Power Window around the unwanted object and add only enough softness for its edge and motion blur. 3. Track or keyframe that Window through the whole shot, correcting slips manually. 4. Drag Object Removal from Resolve FX Revival onto that same Corrector node. 5. Run Scene Analysis, review the result, and run it again after any Analysis parameter changes. ![DaVinci Resolve Object Removal panel beside a tracked Power Window on the Color page](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-object-removal-tracked-window-real-ui.webp) Real Resolve Studio 19 Color page captured by Envato. For the simplest documented setup, the tracked Window and Object Removal effect live on the same Corrector node before Scene Analysis is run. That same-node arrangement removes needless routing from the beginner path. If an existing grade requires a dedicated Window node, its key output can feed a separate effect node, as some professional workflows show. Label that branch clearly and verify the key polarity rather than copying a node graph blindly. ## Draw the smallest stable window A huge window asks the effect to reconstruct more pixels and includes more background motion in the problem. A window that cuts through motion blur, shadow, or the object's changing silhouette leaves visible residue. Start tight, add enough softness for a natural edge, and expand only where the object or its contamination reaches. One Window isn't always enough. A person, shadow and reflection can move differently and may need separate treatment. Segment a long shot when the best mask shape or tracking model changes instead of forcing one oversized matte through every condition. If a moving subject needs isolation for a different treatment rather than removal, use the [Magic Mask guide](https://davinciresolveclub.com/davinci-resolve-magic-mask/) instead of forcing Object Removal to solve another job. ## Track, then correct the track manually Track forward and backward from a frame where the object and background are easy to read. Watch the window rather than the tracker graph alone. Correct slips where the subject is occluded, leaves frame, changes scale, or crosses a similar texture. Tracking the object is not always the same as tracking the surface that will replace it. For a sign on a wall during a camera move, planar motion of the wall can matter more than the sign's outline. The [Fusion tracking guide](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/) covers point, planar, and camera-tracking choices when the Color tracker isn't enough. ## Run Scene Analysis, then inspect the whole shot With the Window and effect in place, run Scene Analysis. Resolve searches across the clip for replacement detail. Turn on Assume No Motion only when the camera is locked and the object moves through the frame. Scene Mode changes what the analysis studies: Background excludes the object region, Boundary concentrates around it, and Object is intended for an unwanted feature that moves with the background, such as a sticker on a window. Play the analyzed result at normal speed, then step through entry, strongest motion, occlusions and exit. Gray fill or gray fringing isn't a finished patch: it's Resolve's warning that the current settings didn't find enough background detail. If you change Scene Mode, Analysis Boundary, Assume No Motion or another Analysis control, run Scene Analysis again before judging the revision. ## Adjust search range, blend mode, and clean plate Search Range controls how many frames around the current frame Resolve examines. Don't raise it automatically. Blackmagic recommends the smallest range that produces an acceptable result, because a wider search can introduce less relevant perspective, focus or lighting. Change it only when usable background exists farther away, then inspect the whole shot again. Linear is the default Blend Mode. Adaptive Blend can help when the filled patch meets background with different color or brightness, but it isn't universally better. Use Build Clean Plate when frames remain solid gray or the automatic fill is incomplete, not as a ritual final click. Internal asks Resolve to assemble a plate; External accepts a plate from another node. Show Clean Plate lets you inspect what is actually being used. ![DaVinci Resolve Object Removal controls for Scene Analysis Search Range Blend Mode and Build Clean Plate](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-object-removal-controls-real-ui.webp) Real Resolve Object Removal controls captured by EasyEdit. This example uses a separate matte node, an optional advanced layout. In the basic Blackmagic workflow the Window and effect can stay on the same Corrector node. ## Fix the artifacts one type at a time ### The object edge remains visible Expand or reshape the matte where motion blur, a shadow or edge spill extends beyond the object. Adjust softness carefully. Too much reveals original pixels; too little creates a cutout edge. Re-track after a shape change and re-run Scene Analysis when an analysis setting changes. ### The fill flickers or boils Split the shot where perspective, lighting or occlusion changes. Return Search Range to the smallest value that works, correct the track and use a more controlled clean plate. Add matching grain only after the underlying patch is stable. ### The patch slides against the background The plate motion doesn't match the surface. Track that surface in Fusion, transform or corner-pin a clean plate, then reveal it through a matte. A flat clone can't follow strong parallax just because the object mask is accurate. ### A shadow or reflection gives the object away Remove or rebuild the interaction separately. The object matte may not include a soft moving shadow, a mirror image, or colored light cast onto nearby surfaces. ### The result is soft compared with the shot Check whether the source plate came from a frame with different focus or motion blur. Match sharpness, blur direction, noise, grain, and exposure after the geometry is correct. ## Use Patch Replacer for a controlled clone Patch Replacer is a controlled clone. In Blackmagic's on-screen control, the patch behind the arrow is the source that samples clean texture; the patch in front is the target that covers the defect. Place the target over the unwanted mark, move the source to a convincing nearby region, then refine the shape and edge blend. Patch Replacer can track source and target motion with its FX tracker. Avoid sampling a recognizable repeated feature such as another window, cloud or face. Blackmagic spells out Patch Replacer as a Studio feature, so Free users shouldn't plan around it. ![DaVinci Resolve Patch Replacer source and target patches with FX tracker on the Color page](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-patch-replacer-real-ui.webp) Real Resolve Studio 19 Color page captured by film-tv-video.de in 2025\. The source patch samples clean texture; the target patch covers the defect, and the FX tracker can follow motion. ## Build a manual clean plate in Fusion when needed Fusion is the controlled route when the repair needs planar tracking, several masks, paint strokes, a photographed plate or foreground occlusion. Build a clean background branch, match it to the shot, and merge it through a tracked mask. This takes longer than the Color effect, but each failure can be inspected instead of hidden inside one automatic fill. Keep foreground objects on a separate branch when they cross the repair. A single patch over the composite will erase wanted foreground along with the unwanted subject. Match motion blur and grain only after plate geometry, color and occlusion are stable. Use the [Fusion rotoscoping workflow](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/) when the plate needs a controlled matte boundary. ![DaVinci Resolve Fusion node graph for a tracked manual clean plate object removal](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-fusion-clean-plate-real-ui.webp) Real Resolve Studio 19 Fusion composition captured by Creative Video Tips in 2025\. A manual plate, tracking, mask and color match provide control when automatic temporal fill cannot reconstruct the shot. ## Use blur when removal is unnecessary Privacy work does not require plausible invented scenery. A tracked blur, mosaic or cover is clearer and often more defensible for faces, addresses, account data and license plates. Follow the [tracked face and background blur guide](https://davinciresolveclub.com/blur-face-background-davinci-resolve/) when concealment is the actual requirement. Similarly, a logo, lower third, crop, or reframed shot can solve a corner obstruction without temporal artifacts. The best fix is the one the audience doesn't question, not the most computationally impressive effect. ## Quality-control the final removal - Watch at normal speed without staring only at the repair. - Step through entry, exit, occlusion, and the strongest camera move. - Check full resolution and the actual delivery transform. - Compare grain, texture, sharpness, exposure, and color. - Check shadows, reflections, and foreground crossings. - Render a short final-codec test and view it outside Resolve. Compression can hide a small flaw or make a soft patch pulse more visibly. Review both a high-quality master and the delivery encode. Keep the unaltered shot and a version with the node disabled for comparison. ## Cache the result only after the matte is approved Scene analysis and temporal reconstruction can be expensive to play in real time. A dropped frame during preview can look like a bad removal even when the rendered frame is correct. First inspect short ranges frame by frame, then cache the approved node or clip so you can judge temporal stability at normal speed. If a cached result becomes stale after changing the window, track, source trim, or clean plate, regenerate that cache before approving the shot. Keep analysis data, render cache, and original media conceptually separate. Deleting generated cache should never remove the only copy of the clean plate or source. For a long take, split the work into logical sections when perspective, lighting, or occlusion changes. Give each section its own reviewed matte and plate, then check the joins for a texture or grain jump. One enormous analysis isn't automatically more consistent than several controlled repairs. ## Frequently Asked Questions ### Is Object Removal available in DaVinci Resolve Free? No. Blackmagic lays out Object Removal and Patch Replacer as DaVinci Resolve Studio features. Free users can crop, cover or blur the problem, or build a manual Fusion paint and clean-plate repair with tools available in their exact version. ### Why does Object Removal leave a blurry or gray patch? Gray fill or fringing means the current analysis can't find usable background detail. A soft but filled patch can come from a mismatched source frame, focus, motion blur or lighting. Tighten the matte and track, use the smallest Search Range that works, compare Blend Mode, then build or supply a clean plate only if needed. ### Should I use Object Removal or Patch Replacer? Use Object Removal when other frames reveal the hidden background and temporal analysis can rebuild it. Use Patch Replacer for a small controlled clone from a clean nearby region. Both are Studio features. ### Can Object Removal erase a person from any video? No. A large person may hide unique background for the whole shot and create shadows, reflections or foreground crossings. Those cases may require a separate clean plate, rotoscoping, Fusion compositing, another take or a crop. ### Why does the removal work on one frame but flicker in motion? A still frame doesn't test temporal consistency. A slipping matte, changing source frames, parallax, grain or lighting can make the fill boil. Review every frame, segment the shot when conditions change and stabilize the plate before matching texture. ### Compound Clips in DaVinci Resolve: Create, Edit and Undo URL: https://davinciresolveclub.com/davinci-resolve-compound-clips/ Last updated: 2026-09-05T03:29:41.000Z A compound clip wraps selected timeline items into one editable object. Use it when a title, background, picture-in-picture and audio cue need to move, trim, transform or receive one parent effect together. Resolve does not render new media or erase the layers inside. Open the compound and the original construction is still there. If compound clips are one step in a first edit, the [Resolve tutorial map](https://davinciresolveclub.com/davinci-resolve-tutorial/) keeps the surrounding trim, audio and export work in sequence. The catch is identity. Copying and pasting a compound on the timeline creates another instance of the same Media Pool item, so an edit inside can update every use. Make an independent Media Pool duplicate before changing only one version. This guide was rechecked on September 5, 2026 against the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) for creation, Open in Timeline, the path control, Decompose in Place and parent-versus-internal processing. ## Choose a compound clip only when you need a container | Task | Best tool | Why | | -------------------------------------------------------------- | --------------------------------- | ---------------------------------------------------------------- | | Move a title, background, and picture-in-picture as one object | Compound clip | Keeps the layered construction editable inside one timeline clip | | Apply one effect across clips below without nesting them | Adjustment clip | Processes the visible stack beneath it over its duration | | Build node-based compositing between selected clips | Fusion clip or Fusion composition | Creates the Fusion-specific image pipeline | | Switch synchronized cameras | Multicam clip | Preserves angle and sync behavior | | Reuse a full scene or program section | Nested timeline | Keeps a named timeline as the reusable source | | Create a finished intermediate file | Render in Place or export | Produces actual media rather than another editable container | ## Create a compound clip from a timeline selection 1. Duplicate the timeline first when the structural change would be expensive to rebuild. 2. Select only the video, title, image and audio items that must behave as one object. 3. Right-click one selected item and choose New Compound Clip. 4. Give it a purpose-specific name and optional starting timecode instead of leaving Compound Clip 1. 5. Confirm that the new compound replaced the selection in the parent timeline and appeared in the currently selected Media Pool bin. 6. Play across its head, tail, audio, transitions, and any effects. ![DaVinci Resolve Edit page context menu with New Compound Clip selected for several timeline clips](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-new-compound-clip-real-ui.webp) Real Resolve Edit page captured by EasyEdit in 2024\. Select only the layers that belong together, then choose New Compound Clip. Resolve 21 retains this command and adds the new item to the selected Media Pool bin. The compound spans the time covered by the selected items. Internal gaps and track relationships become part of that nested result. Resolve also supports Convert In and Out to Compound Clip, but that marked-range method can include every track in the range, even when a track is disabled or Auto Select is off. Inspect the selection before creating it. ## Open and edit the clips inside Right-click the compound in the timeline and choose Open in Timeline. Resolve exposes the nested clips as an editable timeline. You can trim, move, replace, add or remove items inside while the enclosing timeline continues to see one compound result. Use the path control at the bottom-left of the timeline to return: double-click the enclosing timeline name. If the tracks suddenly look much simpler than the program, read that path before making a broad edit. You may still be inside the compound. ![DaVinci Resolve compound clip opened to show video audio and title layers with the parent timeline path](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-open-compound-path-real-ui.webp) Real Resolve compound opened in the timeline, captured by Quantrimang in 2023\. The bottom-left path identifies the enclosing timeline; Resolve 21 documents double-clicking that parent name to return. Changes inside update every timeline instance that points to that same Media Pool compound. That is useful for a repeated graphic package whose approved change should propagate. It is dangerous when two copies were expected to become different versions. ## Make an independent copy before changing one version Timeline copy and paste creates another reference, not a new independent compound. Rename the displayed timeline instance if you like, but a display name alone doesn't change the underlying Media Pool identity. 1. Find the compound item in the Media Pool, not merely its timeline instance. 2. Right-click and choose Duplicate Clip, then give the duplicate a clear versioned name. 3. Replace the timeline instance that must diverge with the new Media Pool duplicate. 4. Open that duplicate in its timeline and make the version-specific change. 5. Reopen the original instance and verify that its contents didn't change. ![DaVinci Resolve Media Pool context menu with Duplicate Clip available for a compound clip](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-duplicate-compound-media-pool-real-ui.webp) Real Resolve Media Pool context menu from a Blackmagic forum example. Duplicate the Media Pool compound, rename it, and replace the intended timeline instance before editing inside the new version. If Duplicate Clip is unavailable in the layout or the result is ambiguous, decompose the copied timeline instance and create a new compound from the restored clips. Either route must produce a separate Media Pool item. The [full Resolve duplication guide](https://davinciresolveclub.com/duplicate-clip-davinci-resolve/) covers ordinary source and timeline copies without collapsing these object types together. ## Extend a compound clip by adding duration inside In the parent timeline, a compound behaves like a source clip whose available head and tail are defined by the nested duration. You can't trim an edge outward when there's no more internal time to reveal. To add duration: 1. Open the compound in its timeline. 2. Extend the required video, title, generator, still or audio layers, or add new material. 3. Add intentional empty duration only when transparency or silence is the intended result. 4. Return through the bottom-left path control. 5. Trim the parent instance outward and inspect every internal layer at the new edge. Slowing the whole compound makes it longer by retiming the combined result. It also retimes internal motion, transitions, keyframes and audio, so it isn't equivalent to extending a title hold or adding clean source duration. ## Undo a compound with Decompose in Place If the compound was just created, normal Undo is the cleanest reversal. Later, duplicate the parent timeline, right-click the compound instance and choose Decompose in Place. Resolve replaces that instance with its internal clips at the same location. ![DaVinci Resolve timeline context menu showing Decompose in Place and Using Clips Only](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-decompose-compound-real-ui.webp) Real Resolve timeline captured by EasyEdit in 2024\. Decompose in Place restores the selected instance's internal clips; it does not delete the compound from the Media Pool or automatically preserve a parent-level grade. For an ordinary compound clip on the Edit page, the manual's base command is Decompose in Place. Resolve documents Using Clips Only and Preserve Audio Data separately for nested-timeline audio workflows in Fairlight and Edit. Those choices control how clips, tracks and audio data are restored; they do not promise to transfer a grade or effect applied to the parent compound onto every child. Compare the duplicate before and after decomposition. Decomposing one timeline instance doesn't delete the compound from the Media Pool and doesn't alter its other uses. It only replaces the selected instance with the underlying edit elements. ## Check grades before and after decomposition A compound can carry a grade or effect as one parent clip, while the internal source clips can have their own grades and effects. Those are separate processing levels. Before decomposition, identify whether the approved look lives on the parent compound, inside individual clips, in a group or at timeline level. Don't assume Decompose in Place will bake a parent grade into the restored clips. Capture a reference still or short render, decompose only a duplicate timeline, and compare scopes as well as the viewer. Rebuild or copy the parent operation deliberately when the decomposed version must match. ## Create handles before adding parent transitions A parent transition needs usable compound frames beyond the visible edit, just as an ordinary clip needs handles. If the compound begins or ends on the first or last internal frame, a centered transition has no extra nested material to reveal on that side. Open the compound, extend the required internal layers, then return and trim the parent instance so those extra frames remain hidden as handles. Inspect titles, generators, masks and audio at both edges. The [transition guide](https://davinciresolveclub.com/davinci-resolve-transitions/) explains the handle math and the insufficient-handles warning. ## Test delivery with the compound intact and decomposed Before export or handoff, render a short range containing the compound's first frame, last frame, strongest motion, transparency and any parent effect. If the next department requires source clips, compare that reference with a decomposed duplicate. This catches changes in scaling, alpha, retiming, color order and audio routing. Keep the approved reference movie beside the project transfer. XML or AAF interchange may not reproduce a Resolve compound as the receiving application expects. Preserve the editable compound timeline, then decompose and verify a separate handoff version only when the recipient needs source-level access. ## Control how source timelines and compounds edit into a timeline Edit > Decompose Compound Clips on Edit is a source-editing mode. When enabled, a compound or timeline loaded from the Media Pool or Source Viewer edits into the destination as underlying clips instead of one nested object. Resolve documents exceptions for Fit to Fill and Place on Top. This mode is not the same command as decomposing an instance already in the timeline. The mode is useful for selects timelines: enable it when chosen source clips should land individually in the program; disable it when the source timeline must remain a single nested object. Test the exact edit command and track destinations before using it across a long assembly. ## Understand processing order before adding effects An effect, transform or grade applied to the compound in the parent processes the combined result. Operations inside the compound process individual layers before that parent result. Moving an operation across this boundary can change scaling, masks, motion blur, alpha and which layers the effect sees. ![DaVinci Resolve parent timeline with one compound clip selected and Transform controls in the Inspector](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-compound-parent-inspector-real-ui.webp) Real Resolve parent timeline captured by Quantrimang in 2023\. Inspector changes at this level process the combined compound result; open the compound when only one internal layer should change. That's useful when one transform must move an entire picture-in-picture construction. It's less transparent when retiming or Optical Flow crosses several internal edits. Inspect the compound's head, tail and every internal cut for repeated or synthesized frames. If the goal is one look over visible clips while keeping them exposed in the parent timeline, compare the [adjustment-clip workflow](https://davinciresolveclub.com/adjustment-clips-davinci-resolve/). If playback is the problem, use proxies, optimized media, render cache or Render in Place through the [slow-playback checklist](https://davinciresolveclub.com/davinci-resolve-slow-playback/) instead of nesting for speed. ## Keep audio routing understandable A compound can contain several audio clips and tracks while presenting a simpler object in the parent. Before nesting dialogue, multichannel production audio or a premix, decide whether the mixer needs individual clips and automation at the parent level. Check channel mapping, fades, clip gain, Fairlight effects and sync after creation and again after decomposition. Preserve a pre-compound timeline. For a complex deliverable, follow the [Fairlight routing map](https://davinciresolveclub.com/fairlight-bus-routing/) before nesting hides the tracks the mixer must audit. ## Avoid compounds that hide the real workflow - Don't compound every finished scene only to make the timeline look tidy. - Don't substitute a compound for linked selection, groups, bins or track organization. - Don't expect nesting to reduce decode or effect processing like rendered media. - Don't retime a complex compound without checking every internal transition, title, generator and audio cue. - Don't send nested structures to another editor or colorist without confirming the turnover requirement. - Don't rename compounds generically when several versions share a project. ## Use a naming and version rule Name the Media Pool item by purpose and version, such as Lower Third - Guest - v03 or Phone Screen Composite - v02\. Keep shared instances when one edit should update every use. Duplicate the Media Pool item and increment the version before changing only one use. For handoff, preserve one timeline with the compounds intact and create a separate reviewed decomposition only when requested. Add a reference movie with burn-in so the receiving editor can detect a nesting, scaling, timing, grade or audio change. ## Frequently Asked Questions ### What is a compound clip in DaVinci Resolve? It's an editable nested container that represents selected timeline items as one clip in a parent timeline. Resolve doesn't render or merge the source files when the compound is created, and the internal clips remain editable through Open in Timeline. ### How do I undo a compound clip? Use normal Undo immediately after creation. Later, duplicate the timeline, right-click the compound instance and choose Decompose in Place. Compare the restored clips, audio routing, transitions and any grade or effect that had been applied to the parent compound. ### Why do both copied compound clips change together? Copying and pasting on the timeline creates another instance of the same Media Pool compound. Duplicate the compound in the Media Pool, rename it and replace the timeline instance that must become independent before editing its internal timeline. ### Why can’t I extend a compound clip? The internal timeline has no more duration available at that edge. Open the compound in its timeline, extend or add the required internal material, return to the parent and trim the compound outward. Leave extra internal frames hidden when a parent transition needs handles. ### Does a compound clip improve playback? Not by itself. It remains an editable nested construction and Resolve still processes its media and effects. Use proxy media, optimized media, render cache or Render in Place when playback performance is the actual problem. ### DaVinci Resolve Frame Rate: Set Timeline FPS Correctly URL: https://davinciresolveclub.com/davinci-resolve-frame-rate/ Last updated: 2026-09-05T03:18:48.000Z Choose the timeline frame rate from the delivery requirement, not from the largest number on a camera card. A 25 fps program can use 50 fps footage for half-speed shots; a 29.97 timeline can use 59.94 material the same way. The first decision is how the finished program must run. The second is what each source clip should do inside that timebase. If this is your first project, the [Resolve tutorial map](https://davinciresolveclub.com/davinci-resolve-tutorial/) keeps frame rate ahead of editing, audio and delivery. Resolve exposes several frame-rate controls because they solve different problems. Project Timeline frame rate sets the primary time grid. An individual timeline can use custom settings. Clip Attributes reinterprets source video and changes its duration. Retime Process decides how frames are mapped when rates or speeds differ. Deliver frame rate describes the rendered file. Treating all five as one generic FPS setting is how clean footage turns into judder or lost sync. These controls were rechecked on September 5, 2026 against the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com). ## Choose the outcome before the setting | What you want | Setting to use | What changes | | --------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------------------ | | A 25 fps broadcast or web master | 25 fps timeline before editing | The program time grid and normal delivery cadence | | 50 fps footage at normal speed in a 25 fps timeline | Leave clip interpretation at 50; edit normally | Resolve conforms frames while duration stays real time | | 50 fps footage as half-speed motion in 25 fps | Interpret at 25 fps or retime to 50% | All recorded frames play over twice the duration | | Replace a 60 fps timeline with 30 fps | Create a new custom 30 fps timeline and test-copy the edit | A new time grid that requires full review | | Fix a phone recording with irregular cadence | Inspect VFR and create a CFR intermediate when needed | The source file, not the timeline's intended cadence | ## Set the project frame rate before adding media 1. Create the project and open Project Settings > Master Settings. 2. Set Timeline frame rate to the exact delivery timebase, including 23.976 versus 24.000 or 29.97 versus 30. 3. Set Playback frame rate and monitoring for the actual display path. This doesn't replace the project timebase. 4. Save a project preset if the same delivery specification repeats. 5. Add representative media only after the rate is confirmed. The project Timeline frame rate locks once one or more files enter the Media Pool. ![DaVinci Resolve Project Settings with Timeline frame rate in Master Settings](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-project-timeline-frame-rate-real-ui.webp) Real Resolve Project Settings captured by TourBox in 2024\. Resolve 21 retains Timeline frame rate in Master Settings; choose the delivery timebase before adding media to the Media Pool. When the first imported media disagrees with the empty project, Resolve can offer Change Project Frame Rate. Choose Change only when that detected source rate is genuinely the required project rate. Choose Don't Change when the project was deliberately set for another delivery cadence, such as a 25 fps program receiving a 50 fps slow-motion source. This choice is about the project timebase, not whether Resolve can use the clip. ![DaVinci Resolve Change Project Frame Rate prompt with Don't Change and Change buttons](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-frame-rate-mismatch-dialog-real-ui.webp) Real Resolve mismatch prompt captured by TourBox in 2024\. Change adopts the detected source rate for the project; Don't Change preserves the timebase you already chose. Resolve 21 documents the same first-import decision. ## Pick the delivery cadence, not the “cinematic” label Start with the client, broadcaster, camera system or live pipeline requirement. Film workflows commonly distinguish 23.976 from 24.000\. PAL-derived television and many European workflows use 25 or 50; NTSC-derived work commonly uses 29.97 or 59.94\. Those labels aren't interchangeable, and a delivery specification beats a generic web recommendation. [YouTube's current encoding guidance](https://support.google.com/youtube/answer/1722171?hl=en&ref=davinciresolveclub.com) recommends uploading at the same frame rate in which the content was recorded and lists common rates including 24, 25, 30, 48, 50 and 60\. Don't convert 25 to 24 merely because a tutorial calls 24 cinematic. Conversion changes cadence and may require dropped, repeated, blended or synthesized frames. ## Keep high-frame-rate clips real time when that is the intent With mixed-frame-rate conforming enabled, placing a 50 fps source in a 25 fps timeline keeps its real-world duration unless you deliberately reinterpret or retime it. A one-second action remains one second; Resolve maps the available source frames onto the timeline grid. That behavior is appropriate for sports, screen recordings or camera footage captured at a higher cadence but intended to play in real time. The timeline can display only its own number of frames each second, so the selected Retime Process determines how the mismatch is represented. | Retime process | Method | Tradeoff | | -------------- | ------------------------------- | -------------------------------------------------------------- | | Nearest | Selects existing frames | Fast and sharp, but cadence can judder with awkward ratios | | Frame Blend | Blends neighboring frames | Smoother cadence can introduce ghosting | | Optical Flow | Estimates motion between frames | Can look smoother but costs more processing and can warp edges | Nearest uses the nearest source frame, dropping or repeating frames where necessary. Frame Blend dissolves adjacent frames. Optical Flow estimates motion and creates intermediate frames, which costs more processing and can break around crossing limbs, occlusion, water, particles, flashes or unpredictable camera movement. Test the motion-heavy section at full size; Optical Flow isn't automatically the best result. ![DaVinci Resolve Inspector Retime and Scaling panel with Nearest Frame Blend and Optical Flow choices](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-retime-process-inspector-real-ui.webp) Real Resolve Inspector captured by Filmmaking Elements in 2023\. Resolve 21 retains Nearest, Frame Blend and Optical Flow; inspect the shot because the most complex mode is not automatically the cleanest. ## Interpret high-frame-rate footage for slow motion If a camera recorded 50 progressive frames during one real second and you interpret that video at 25 fps, those 50 recorded frames occupy two timeline seconds. The picture becomes half speed without synthesizing intermediate frames. This is source interpretation, not normal mixed-rate playback. 1. In the Media Pool, right-click the original source and choose Clip Attributes. 2. On the Video tab, set Video Frame Rate to the intended interpretation rate. 3. Add the interpreted clip to a short test timeline and confirm the new duration. 4. Check picture timing and synchronization. Clip Attributes changes video, but it doesn't change the associated audio. 5. Don't reinterpret a source used elsewhere at normal speed unless every use should inherit that change. Interpreting 60 fps at 24 fps produces 40% speed because 24 divided by 60 is 0.4\. Interpreting 59.94 at 29.97 produces 50%. For a speed ramp or one selected slow section, use the [clip-speed and retime workflow](https://davinciresolveclub.com/change-clip-speed-davinci-resolve/) instead of changing the source interpretation for every use. ![DaVinci Resolve Clip Attributes Video tab with Video Frame Rate dropdown](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-clip-attributes-frame-rate-real-ui.webp) Real Resolve Clip Attributes captured by TourBox in 2024\. Video Frame Rate reinterprets the selected source video; Resolve 21 explicitly states that audio is unaffected. ## Be careful with audio when interpreting clips Some high-frame-rate camera modes record no usable production audio. More importantly, Resolve 21 states that changing Clip Attributes > Video Frame Rate affects video while audio is unaffected. The picture duration changes but the audio duration doesn't, so a synchronized clip can immediately fall out of step. That's a consequence to plan for, not a fault in the audio engine. For dialogue or double-system sound, leave normal-speed sources at their intended interpretation and retime only with an explicit audio plan. Never reinterpret a synced multicamera angle after synchronization without rebuilding or checking the group from beginning to end. The [multicam editing guide](https://davinciresolveclub.com/davinci-resolve-multicam-editing/) covers the synchronization stage separately. ## Recover when timeline frame rate is locked The project Timeline frame rate locks as soon as one or more files are added to the Media Pool. If the project-level control is greyed out, don't edit databases or preference files. A new custom timeline can use another timebase, but it doesn't change the locked project setting: 1. In the Media Pool, create a new timeline. 2. Disable Use Project Settings before confirming the new timeline. 3. Set the required Timeline Frame Rate in the custom Format settings. 4. Duplicate the original timeline before moving any edit content. 5. Copy the edit into the new timeline, then inspect timing, transitions, keyframes, speed effects, captions and audio sync. A different cadence changes the time grid. Copying clips is only the start of recovery. Frame-based keyframes, retimes, transitions, compound clips, captions and externally synced audio can land differently. Compare the first frame, last frame and several timing landmarks before replacing the original timeline. ![DaVinci Resolve Create New Timeline settings with Use Project Settings disabled and Timeline Frame Rate](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-custom-timeline-frame-rate-real-ui.webp) Real Resolve custom-timeline settings captured by TourBox in 2024\. Disabling Use Project Settings lets this timeline use its own format; it does not unlock or rewrite the project-level frame rate. ## Handle mixed 23.976, 24, 25, 29.97 and 30 sources Mixed frame rates are normal in documentary and creator projects. Choose one master timeline from delivery, keep mixed-frame-rate conforming enabled for normal-speed sources, and inspect clips whose cadence doesn't divide cleanly into the timeline. A mathematically valid conversion can still look uneven on a pan or scrolling screen. Check pans, scrolling interfaces, LED walls, stage lighting, motion blur and shutter cadence. Converting 24 to 25 presents a different pattern from 60 to 30\. If exact running time and sync matter, don't reinterpret a clip just to make its metadata match the timeline. ## Do not change timeline FPS to fix slow playback If the viewer manages only 18 frames per second on a 25 fps timeline, changing the timeline to 18 isn't a performance fix. The timeline defines the finished program; real-time playback depends on decoding, effects, storage, GPU work and the current render cache. Test the same range with effects bypassed. If the source codec is expensive to decode, use proxies or optimized media. If Fusion, noise reduction, retiming or scaling causes the miss, cache that operation or lower preview load. Work through the [slow-playback checklist](https://davinciresolveclub.com/davinci-resolve-slow-playback/) without changing the approved cadence. ## Check exchange timelines and external audio at exact rates An XML, AAF, DRT or imported timeline can carry a timebase that differs from the receiving project. Read the import dialog. Then compare the first and last frame, clip durations, transitions, speed changes and markers against the source edit instead of assuming a successful import means a timing match. Audio has no video frame rate, but clips, timecode and synchronization live on a timeline grid. Confusing 23.976 with 24.000 can create cumulative timing or timecode disagreement in a long program. Verify the exact rate at ingest, interchange and delivery rather than fixing the end by eye. For multicamera material, lock the program rate before synchronization and inspect a point near the end of a long take. If sync progressively drifts, investigate source timestamps, recorder clock, variable frame rate and interpretation. Repeatedly nudging later clips hides the cause and makes the next conform harder. ## Convert variable-frame-rate media before blaming FPS Phones, screen recorders, meeting tools and browsers can produce variable-frame-rate media. A file may report a nominal 30 fps while the time between encoded frames varies. Such media can be associated with uneven seeking, drift or inconsistent frame-accurate edits, but VFR isn't proof of the cause by itself. Use MediaInfo or another reliable inspector to check Frame rate mode and timestamps. [HandBrake's current frame-rate documentation](https://handbrake.fr/docs/en/latest/technical/frame-rates.html?ref=davinciresolveclub.com) distinguishes a variable source from a Constant Frame Rate output. If a controlled test implicates VFR, preserve the original and transcode a separate constant-frame-rate copy at the intended cadence. Recheck start-to-end sync before relinking. Changing only the Resolve timeline rate doesn't normalize source timestamps. ## Match export to the approved timeline The Deliver page defaults to the Timeline Frame Rate. Keep the approved cadence unless the specification requires a different master and you have reviewed the conversion. A higher output number doesn't recover motion samples the camera never recorded. Some Individual Source Clips renders can retain source rates, while a Single Clip render is conformed to the timeline. Use the [export task map](https://davinciresolveclub.com/davinci-resolve-export-settings/) for codec, container, bitrate, audio and platform decisions, or follow the [full Deliver-page walkthrough](https://davinciresolveclub.com/export-video-davinci-resolve/). Render a short motion-heavy section first and inspect it in an external player before committing to the full job. ## Check frame rate before the real edit - Confirm the exact delivery timebase, including fractional rates. - Inspect representative camera, phone, screen, and archive sources. - Decide which high-rate clips are real time and which are slow motion. - Set the timeline before bulk import. - Test motion, audio sync, titles, subtitles, and export. - Document the project rate for every editor and camera operator. ## Frequently Asked Questions ### What frame rate should I use in DaVinci Resolve? Use the exact delivery timebase required by the client, broadcaster or production. For self-published work, normally preserve the planned capture cadence instead of converting it for a style label. Set the project rate before adding media. ### Why is timeline frame rate greyed out? The project Timeline frame rate locks after one or more files are added to the Media Pool. You can create a new timeline with Use Project Settings disabled and choose a different timeline rate, but that doesn't unlock the project setting. Copy the edit only after duplicating it, then inspect every timing-dependent element. ### Should a 60 fps clip go on a 24 fps timeline? Yes, when 24 fps is the required program rate. Keep mixed-frame-rate conforming for normal-speed playback, or reinterpret or retime the clip deliberately for slow motion. A 60 fps source doesn't require a 60 fps timeline. ### Does changing Clip Attributes change video speed? Yes. Changing Clip Attributes > Video Frame Rate changes the video duration and playback speed. Resolve doesn't change the clip audio with that setting, so synchronized audio can fall out of step with the reinterpreted picture. ### Is 23.976 the same as 24 fps? No. They're close but distinct timebases. Use the exact rate required by capture, production and delivery, especially for long-form audio sync, timecode, interchange and broadcast specifications. ### DaVinci Resolve Transitions: Add, Trim and Fix Them URL: https://davinciresolveclub.com/davinci-resolve-transitions/ Last updated: 2026-09-05T03:10:05.000Z A Cross Dissolve that refuses to sit on the cut isn't asking for a different preset. It is usually asking for frames. A transition borrows source material beyond the visible end of the outgoing shot and before the visible start of the incoming shot. Get those handles and the edit timing right first; choosing the effect is the easy part. If this is one step in your first project, follow the [Resolve tutorial map](https://davinciresolveclub.com/davinci-resolve-tutorial/) so the cut, sound and export are learned in working order. Most DaVinci Resolve transitions use this same edit-point logic. This workflow was rechecked on September 5, 2026 against the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) and uses the Edit page. The core video and audio transitions are available in Resolve Free. Resolve FX, Fusion templates and third-party transitions can have separate Studio, hardware or licensing requirements, so verify the specific item rather than assuming the whole library follows one rule. ## Add a transition between two clips 1. Place two clips next to each other on the same video track. 2. If the clips use their first or last recorded frames, shorten the outgoing tail and incoming head, then close the gap. That creates handles without changing the source files. 3. Open **Effects > Toolbox > Video Transitions**. 4. Drag Cross Dissolve onto the edit point, or select the video edit and choose Timeline > Add Video Only Transition. 5. Select the transition and set its Duration and Alignment in the Inspector. Only adjust effect-specific controls after the timing works. 6. Play through the cut with audio and review every frame the transition reveals. For a video-only transition, select the video edit point and choose Timeline > Add Video Only Transition. The default shortcut is Option-T on macOS and Alt-T on Windows, as shown in Blackmagic's [current beginner training guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Beginners-Guide.pdf?ref=davinciresolveclub.com). Timeline > Add Transition is a different command: it can add the standard transition to selected video and audio edits. If a shortcut behaves differently, open Keyboard Customization; imported keyboard maps can override the defaults. ![DaVinci Resolve Effects Library menu for setting Cross Dissolve as the standard video transition](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-transitions-library-real-ui.webp) Real Resolve Effects Library captured by CodeWithSusan in 2026\. Right-click the transition you actually use, choose Set As Standard Transition, then apply it to a selected edit point. ## Understand handles before Resolve trims for you A handle is recorded source material outside the section currently visible in the timeline. If a ten-second shot is cut off at eight seconds, the unused tail can feed the outgoing side of a transition. The source file is unchanged. If trimming itself is unfamiliar, use the [split-and-trim guide](https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/) before adding effects. ![DaVinci Resolve timeline sequence trimming two clips to create transition handles before closing the gap](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-transition-handles-real-ui.webp) Real Resolve timeline sequence captured by CodeWithSusan in 2026: shorten the outgoing tail and incoming head, close the gap, then apply the transition. The unused source frames beyond the new cut become the handles. A centered transition divides its overlap around the edit, so both sides need enough unused frames for their part of the duration. If either clip is already using the first or last recorded frame, Resolve can't invent the missing action. A freeze or repeated frame may be technically possible in another construction, but it isn't the same motion as a real handle. | Edit condition | What a centered transition needs | Best decision | | ------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------ | | Both clips have handles | Unused frames on both sides | Add the transition, then inspect revealed action | | Only outgoing clip has a handle | Incoming frames are missing | Shorten or realign the transition, or trim the incoming clip | | Neither clip has handles | No overlap is available | Change the edit, shorten the transition, or use a different construction | | Still image | Duration rather than recorded frames controls the edge | Extend the still and test the edit point | When Resolve offers Trim Clips, read the dialog literally. It shortens the selected clips to create the missing overlap, which changes the visible edit and shortens the timeline. Skip Clips leaves insufficient edits unchanged; Cancel abandons the batch. Before accepting Trim Clips, check dialogue sync, beats, action matches and any downstream timing that depends on the cut. ![DaVinci Resolve Add Transitions warning with Trim Clips Skip Clips and Cancel choices for insufficient handles](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-transition-handles-warning-real-ui.webp) Real Resolve dialog captured by CodeWithSusan in 2026\. Trim Clips shortens the timeline, Skip Clips leaves those edit points unchanged, and Cancel abandons the operation. ## Choose start, center, or end alignment deliberately Resolve names the three positions Start on Edit, Center on Edit and End on Edit. Center uses frames on both sides. Start on Edit places the effect after the cut and leans on the incoming side; End on Edit places it before the cut and leans on the outgoing side. The options Resolve can honor still depend on the available handles. Alignment changes which real frames the audience sees. If a spoken word, kick drum, hand movement or screen action must land on the cut, replay from before the transition after every alignment change. A dissolve can look smooth while moving the story beat to the wrong frame. ## Set duration from the rhythm, not a preset Resolve's standard transition duration is a preference, not an editorial recommendation. The factory default documented for Resolve 21 is one second, or as much of that duration as the available handles permit. Use it as a convenient insertion value, then set the real duration from the shot rhythm and purpose. Drag either edge in the timeline to change duration symmetrically. For an exact value, right-click and choose Change Transition Duration, or open the Transition Inspector and enter seconds or frames. The Resolve 21 manual documents Command-dragging on macOS to adjust one side. On Windows, verify the modifier in your installed build instead of copying the Mac key literally. Zoom into the timeline before assuming a short transition can't be selected. ![DaVinci Resolve transition Inspector with duration alignment ease and transition curve controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-transition-inspector-real-ui.webp) Real Resolve 19 interface from Storyblocks. Resolve 21 still documents Duration and Alignment in the Transition Inspector; controls such as Mode, Ease and Transition Curve depend on the selected transition. | Editorial purpose | Useful starting thought | Review for | | -------------------------------- | ------------------------------------------------- | ------------------------------------------- | | Hide a tiny visual discontinuity | Use the shortest duration that solves it | Ghosting or a visible softness pulse | | Suggest time passing | Let both shots remain readable during the overlap | Double exposure that becomes visually messy | | Fade from or to black | Use the clip fade handle or Dip to Color | Whether tracks below become visible | | Music or dialogue edit | Build an audio crossfade independently | Phase, room tone, consonants, and the beat | ## Use a fade handle when no second clip is needed A clip-edge fade handle is the cleaner choice when there is no second video clip to overlap. Drag the upper corner of the clip to fade its opacity toward or away from whatever is underneath. That is different from a two-shot Cross Dissolve, which mixes real frames from both clips. Use Dip to Color when the edit should pass through a defined color. Use Cross Dissolve when both images should overlap. Do not leave a one-frame gap as a substitute for handles: the transition may reveal transparency or a black flash, depending on the tracks below. ## Add audio transitions separately Open Effects > Toolbox > Audio Transitions. Resolve 21 provides Cross Fade +3 dB, -3 dB and 0 dB. To add the standard audio transition to selected audio edits, choose Timeline > Add Audio Only Transition or press Shift-T on the default keyboard map. Those are different gain relationships through the overlap, not quality tiers. Start with the curve that best preserves the perceived level, then listen on the actual material. - **Cross Fade 0 dB:** compare it when the two sides are closely related and the center otherwise builds or dips unexpectedly. - **Cross Fade -3 dB:** audition its different overlap curve against room tone, music and correlated ambience. - **Cross Fade +3 dB:** test it only by ear and meter when the other curves produce a noticeable hollow or level dip. Listen rather than choosing by name. On dialogue, check consonants, breaths and room tone. On music, check the beat, phase relationship and transients. If you need track-level control rather than one clip overlap, continue in the [Fairlight task map](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/). ![DaVinci Resolve Edit page with Audio Transitions and Cross Fade plus 3 minus 3 and 0 dB options](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-audio-crossfade-real-ui.webp) Real Resolve 17 Edit page from Motion Array. Resolve 21 still documents the same three Cross Fade choices: +3 dB, -3 dB and 0 dB. Audition them on the actual edit instead of treating one curve as universal. Before adding a picture effect, test an L-cut or J-cut. Letting the outgoing sound continue under the incoming picture, or introducing the next sound first, often hides the edit more naturally than matching the audio and video transition lengths. ## Preview and customize without losing the cut Hover Scrub Preview in the Effects Library can narrow the choices, but it previews a possibility, not the final edit. Judge the transition on the actual two clips. In the Inspector, Duration and Alignment are common controls; style, ratios, ease, curves and other parameters vary by transition type. Duplicate the timeline before applying a styled transition across many edits. Repetition is fast, but it can also expose five different bad handles or turn every cut into the same visual punctuation. Approve one representative edit, then inspect each batch result at full speed and frame by frame. ## Set and change the standard transition Right-click the transition you genuinely use and choose Set as Standard Transition. The command changes what Resolve inserts with the standard-transition commands; it doesn't change existing transitions. The default duration is controlled separately in Preferences > User > Editing. Select several edit points only after checking their handles and track selection. A batch can create valid-looking icons while revealing rejected frames at half the cuts. If Resolve reports insufficient handles, use Skip Clips when you need to preserve timing and fix those edits individually. ## Fix a transition that will not apply ### There are no usable handles Shorten the outgoing tail and incoming head, close the gap, then try again. If the cut cannot move, reduce the duration or align the effect to the side with usable frames. When neither side has real handles, keep the straight cut or redesign the edit instead of forcing a fake overlap. ### The transition lands on only one clip edge Zoom in and target the edit point between two adjacent clips on the same track. Confirm there's no tiny gap and that the intended track is selected. A transition dropped on the head or tail of one clip behaves as an edge transition, not as a centered blend between two shots. ### The transition reveals a bad frame The transition is revealing real frames from the handles. Roll the edit, trim a different section, shorten or realign the transition, or return to the cut. Do not blame the effect for showing a focus pull, camera bump or mouth movement that lives just outside the visible edit. ### Playback stutters over the transition If playback drops frames only over the effect, cache that section or reduce the preview load before judging timing. A demanding transition can miss real-time playback without proving that the render is bad. Use the [slow-playback checklist](https://davinciresolveclub.com/davinci-resolve-slow-playback/) for the performance side, then inspect the exported frames and audio around the edit. ### A nested timeline or compound clip changes size Test the same effect on the underlying clips. If that works, compare timeline resolution, scaling, compound-clip transforms and the order of other effects. A nested timeline or compound clip presents a new raster and handle boundary, so the transition may be processing different material than the original edit suggests. ## Use transitions as editorial grammar Start with the straight cut. Add a dissolve to connect moments or imply time, Dip to Color to separate sections, a wipe when the direction itself carries meaning, or Smooth Cut only when its interpolation suits the shot. The name of the preset isn't a reason to use it. Finally, hide the interface and watch from several seconds before the edit. If you notice the preset before the story beat, shorten it or remove it. Then listen once without watching: room tone, dialogue and music often decide whether a cut feels smooth long before a video effect does. ## Frequently Asked Questions ### Why can’t I add a transition in DaVinci Resolve? The edit usually lacks unused source frames, called handles. Shorten the outgoing clip before its recorded end and the incoming clip after its recorded start, close the gap, then add or shorten the transition. If Resolve offers Trim Clips, remember that accepting it changes the visible edit and shortens the timeline. ### How do I add the same transition quickly? Set the effect as the Standard Transition, select the video edit point, then choose Timeline > Add Video Only Transition. On the default map that's Option-T on macOS or Alt-T on Windows. Timeline > Add Transition is a different command that can add the standard transition to selected video and audio edits. ### Why does a dissolve show frames I cut out? A dissolve overlaps source frames beyond the visible edit. Those handles may contain the movement, focus change or unwanted frame you removed from the straight cut. Roll the edit, shorten or realign the transition, or keep the cut. ### What is the best transition for most edits? A straight cut is the safest default. Use Cross Dissolve when an overlap has editorial meaning, Dip to Color for a deliberate separation, and an audio crossfade only after listening to the room tone, phase and level through the edit. ### Are transitions available in DaVinci Resolve Free? The core video and audio transition workflow is available in Resolve Free. Some individual Resolve FX, Fusion templates or third-party plugins can have Studio, hardware or license requirements, so check the label and vendor requirements for that specific item. ### DaVinci Resolve Keeps Crashing? Find the Exact Trigger URL: https://davinciresolveclub.com/davinci-resolve-keeps-crashing/ Last updated: 2026-09-05T02:52:57.000Z “Resolve keeps crashing” is a symptom, not a diagnosis. A crash at launch, a freeze when one H.265 clip is imported, a Fusion failure on one node, and a whole-computer lockup during export need different tests. The fastest route is to protect the project, reproduce one trigger, and change one variable at a time. Before touching drivers or reinstalling anything, write down the exact Resolve version and build, Free or Studio, operating system version, GPU, RAM, footage format, and the last action before the failure. That short record prevents the troubleshooting loop where five settings change and nobody knows which one mattered. ## First decide whether it crashed, froze, or exhausted the system | Symptom | What it means operationally | First useful test | | ----------------------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | Resolve disappears to the desktop | Application crash | Reproduce once, then create a diagnostics archive | | Resolve says Not Responding but the OS remains usable | Application hang or a long operation | Watch whether CPU, disk, or GPU activity continues before force quitting | | The display resets or the whole machine locks | Driver, hardware, power, thermal, or system-level failure is possible | Check OS event and system logs, temperatures, and stability outside Resolve | | Only one render stops or fails | Delivery-path failure, not automatically an application crash | Use the [render-failed workflow](https://davinciresolveclub.com/davinci-resolve-render-failed/) | | Playback drops frames but Resolve stays open | Performance problem | Use the [slow-playback diagnosis](https://davinciresolveclub.com/davinci-resolve-slow-playback/) | A busy application can look frozen while it builds waveforms, analyzes media, loads a large project, or processes a heavy effect. Give the process a short observed interval and watch CPU, disk and GPU activity rather than repeatedly clicking the window. A repeatable hang still matters, but describe it accurately. If the symptom doesn't fit this table, use the [Resolve troubleshooting map](https://davinciresolveclub.com/fix-davinci-resolve/) before changing unrelated settings. ## Protect the project before experimenting If Resolve still opens, duplicate the affected timeline and choose File > Export Project to create a DRP. The [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) says standard Export Project omits stills and LUTs; a separate Export Project with Stills and LUTs command includes them. Neither DRP option bundles source media or generated cache, so preserve those separately. For important work, also back up the project library from Project Manager. Open Preferences > User > Project Save and Load and verify both controls. In Resolve 21, Live Save is on by default and saves changes incrementally. Project Backups works independently, keeps timed project versions, and opens a recovered backup as an independent project rather than overwriting the original. Check the retention schedule and confirm that the backup location is available. ![DaVinci Resolve Project Save and Load preferences with Live Save Project Backups retention and backup location](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-project-save-load-real-ui.webp) Real Resolve 17 Project Save and Load controls. Resolve 21 keeps Live Save and Project Backups in this User Preferences panel, but choose your own retention and backup location instead of copying the values shown here. Don't reset preferences, delete a project library, or remove application-support folders until you have a restorable copy. A troubleshooting step isn't safe merely because it appears in a short video. ## Build a reproducible crash note Open a plain text file and capture one failure in this format: - Resolve 21.x.x build number, Free or Studio. - Operating system version and recent OS update. - GPU model, driver version, VRAM, RAM, and free disk space. - Project and timeline name. - MediaInfo details for the source used at the crash point. - Exact action: “Open Color page, select clip 43, enable temporal noise reduction.” - Result: crash to desktop, hang, display reset, or full system restart. - Whether the same action fails again after relaunch. If it can't be repeated, note what was different before the next occurrence. Intermittent failures often become understandable after two or three observations reveal the shared effect, media source, display state, or background task. ## Use the trigger to choose the branch | Repeatable trigger | Best isolation test | Evidence it produces | | -------------------------------------------------- | ------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | Resolve crashes before the Project Manager appears | Disconnect optional hardware, test a clean OS user where practical, and inspect launch logs | Separates application startup from one project | | One project crashes while others open | Open a backup or duplicate, then disable the last suspect effect or media group | Project-specific boundary | | Importing one folder crashes | Add small batches, then individual files | Identifies one malformed or unsupported asset | | One effect or Fusion comp crashes | Bypass the effect, node group, or third-party plugin | Effect/plugin/GPU branch | | Moving or minimizing the window crashes | Test one display, remove overlays, and compare the current certified GPU driver | Display/driver/window-state branch | | Export crashes | Render a short range around the repeatable frame | Separates one clip/frame/effect from general encoding | ## Test a new project before blaming the installation Create an empty local project, add one known-good file, make a simple timeline, and play it. If the clean project is stable, the installation can launch, decode that file, and run the basic edit path. Return to a duplicate of the problem project and isolate what it adds. If the clean project also fails, the scope shifts toward the application build, GPU driver, system resources, optional hardware, preferences, or OS. Reinstalling the same build without collecting evidence may change nothing because media, drivers, plugins, and preferences remain outside the application bundle. ## Isolate media without converting the whole job A crash on import or at the same timeline frame can be caused by one incomplete image, damaged video, unusual audio stream, or unsupported codec profile. Copy the suspect item to a local drive, inspect it with MediaInfo, and test it in an empty project. Compare the actual video and audio streams with [Blackmagic's codec matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com) rather than trusting the filename extension. When a folder import crashes, use a binary search: import half the files, then half of the failing half, until one asset remains. [Blackmagic Support has recommended the same divide-and-conquer method](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=209795&ref=davinciresolveclub.com) for a repeatable folder-import crash. Don't delete the suspect source. Move a copy out of the test set and preserve the original for recovery or vendor analysis. If a phone or screen recording imports but crashes during seeking, create one constant-frame-rate intermediate and repeat the same action. If the intermediate is stable, you have evidence about the source path. You don't yet have a reason to transcode every unrelated camera file. ## Separate GPU memory pressure from a driver failure Noise reduction, Magic Mask, Super Scale, optical flow, large Fusion frames, many OpenFX plugins, and high-resolution timelines can increase GPU memory and processing pressure. If Resolve reports GPU memory full, follow the dedicated [GPU memory workflow](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/). A display reset, driver timeout, or whole-system lock needs a broader check. Record the driver version, compare it with the current support notes and [Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/), and inspect the operating system's event or crash report. On Windows, test the appropriate supported driver branch for the installed Resolve build and GPU when one is specified. On macOS, GPU drivers arrive with the OS, so a Windows clean-driver tutorial doesn't apply. ![DaVinci Resolve Memory and GPU preferences showing memory limits GPU processing mode and GPU selection](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-memory-gpu-real-ui.webp) Use the real Memory and GPU panel to record what Resolve detected. The 48 GB Resolve limit, 36 GB Fusion cache and Apple M1 Max shown here belong to this workstation; they are evidence, not settings to copy. Monitor temperatures and system stability during the repeatable test. Resolve can expose marginal cooling, power, RAM, GPU, or overclock stability because it loads several subsystems at once. That doesn't prove Resolve caused the hardware fault. Remove overclocks and test the machine at known-stable defaults before drawing conclusions. ## Disable third-party plugins as a controlled test If the crash begins when loading a title, transition, audio effect, LUT tool, or OpenFX plugin, duplicate the timeline and bypass that item. Update the plugin from its vendor only after confirming compatibility with your Resolve and OS versions. A plugin can also fail while Resolve scans it at launch. Temporarily moving one suspect plugin out of its documented scan path can be a useful test, but record the original location and change only one product at a time. A current [Maxon support example](https://support.maxon.net/hc/en-us/articles/115015832767-Resolve-isn-t-loading-my-Universe-plugins?ref=davinciresolveclub.com) uses Preferences > Video Plugins and the product's own plugin cache for Universe. Don't apply product-specific file paths to unrelated plugins. ## Clear only the cache tied to the failure Render cache and optimized media are generated files. A damaged cache entry can reproduce a problem at one frame, so deleting the cache for the selected clip or timeline is a reasonable controlled test. Deleting every cache on every disk isn't a universal crash fix and can turn a short diagnosis into hours of regeneration. Check free space and write access on the cache drive. A full or disconnected cache location can create failures that look like a bad effect. Keep source media, cache, proxies, and project-library backups conceptually separate so removing generated files never removes the only copy of a source. ## Update or roll back with a rollback path Check Blackmagic's [Resolve support page](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) for the current build and release notes. This workflow and its Resolve 21 commands were rechecked against the current manual and support material on September 5, 2026. If the notes name your failure or your build is far behind, an update may be justified. If crashing began immediately after an application, OS, driver, or plugin update, the previous known-good combination is useful evidence. Before changing Resolve, back up the project library and export important projects. Newer project libraries may not be usable in older Resolve versions. The [safe update procedure](https://davinciresolveclub.com/update-davinci-resolve-safely/) covers the backup and verification sequence. ![DaVinci Resolve 18 Project Manager menu with Export Project Export Project with Stills and LUTs and Project Backups](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-project-manager-context-real-ui.webp) Real Resolve 18 Project Manager. Resolve 21 still separates Export Project, Export Project with Stills and LUTs, and Project Backups. A DRP protects project data; it does not bundle the source media or generated cache. ## Create diagnostics while the failure is fresh After reproducing the crash, reopen Resolve, open any project if needed, and choose Help > Create Diagnostics Log on Desktop. The command is documented in Resolve 21, and [Blackmagic Support asks for that archive](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=177883&ref=davinciresolveclub.com) together with system information and, for project-specific failures, a DRP plus exact reproduction steps. ![DaVinci Resolve Help menu with Create Diagnostics Log on Desktop selected](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-help-diagnostics-real-ui.webp) The real Resolve Help command creates the diagnostics archive Blackmagic Support asks for. Run it after reproducing the failure, then keep the archive private unless you deliberately share it with support. On Windows, save a System Information NFO rather than a text export when support requests it. On macOS, save the System Report. Don't post diagnostic archives publicly without reviewing the privacy implications. They can contain machine details, paths, plugin information, and project context. Share them through the support route you intentionally choose. ## Know when to stop changing settings Escalate with evidence when a clean project and known-good media still reproduce the failure, the same action crashes after a supported driver and application update, or the issue is tied to a specific project that survives a backup restore. Send the exact build, system report, diagnostics archive, minimal project or sample media where licensing permits, and concise steps. For a whole-system restart, thermal shutdown, storage errors, memory-test failure, or repeated crashes in other GPU-heavy applications, troubleshoot the system before continuing production. An NLE preference reset cannot fix unstable RAM or a failing drive. ## Frequently Asked Questions ### Why does DaVinci Resolve keep crashing? Common branches include one damaged or unsupported media file, GPU memory pressure, a driver or display failure, a third-party plugin, one project or effect, a full cache drive, and an application bug. Reproduce the exact trigger before choosing a fix. ### Will clearing the cache stop Resolve from crashing? Only when generated cache media is part of the repeatable failure. Delete the cache for the selected clip or timeline as a controlled test. A launch crash, plugin scan failure, unsupported source, or unstable GPU will not be repaired by clearing unrelated cache files. ### Should I reinstall DaVinci Resolve? Not as the first step. Test a clean project and known-good media, collect diagnostics, and isolate plugins, drivers, and project-specific factors. Reinstalling the same build may leave the real cause unchanged. ### How do I get DaVinci Resolve crash logs? After the failure, reopen Resolve and choose Help > Create Diagnostics Log on Desktop. If Resolve can't reach Project Manager, use Blackmagic's platform-specific CaptureLogs utility for your installed build. Keep the archive private unless you intentionally share it with support. ### Can low RAM or VRAM make Resolve crash? Resource pressure can contribute, especially with high-resolution media, Fusion, noise reduction, AI tools, and large frame buffers. Record RAM and VRAM use around a repeatable trigger, but don't treat capacity as proof when a driver, plugin, damaged file, or hardware fault can produce a similar failure. ### DaVinci Resolve Won't Import MP4? Fix Audio-Only Clips URL: https://davinciresolveclub.com/davinci-resolve-wont-import-mp4/ Last updated: 2026-09-05T02:41:02.000Z An MP4 that imports as audio only is not one problem with one fix. The file may contain a video stream that your Resolve edition can't decode, the MP4 container may be damaged, or the video may already be available while the timeline's V1 source patch is turned off. Those cases look similar when you drag a clip, but converting every file will waste time and can reduce quality. Start by checking where the picture disappears. If the clip is audio-only inside the Media Pool, inspect the file and codec. If video plays in the Source Viewer but only audio lands on the timeline, inspect source patching. Keep the original file untouched until you know which problem you have. ## Match the symptom before changing anything | What you see | Most useful first check | Likely route | | ----------------------------------------------------------------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | The MP4 is missing from the import browser or Resolve rejects it | Open it in another player, then inspect its streams in MediaInfo | Codec, container, file access, or damaged media | | The clip appears as audio-only in the Media Pool | Read the video codec, profile, bit depth, and chroma sampling | Unsupported video stream or incomplete file | | The Source Viewer plays picture and sound, but dragging adds only audio | Look at the V1 source patch and destination track | Timeline patching, not conversion | | The clip imports but displays Media Offline | Check the path, drive access, and decoder details | Use the dedicated [Media Offline diagnosis](https://davinciresolveclub.com/media-offline-davinci-resolve/) | | Picture works but audio is silent or absent | Inspect the audio stream and Resolve's track and bus routing | Use the [no-audio troubleshooting path](https://davinciresolveclub.com/davinci-resolve-no-audio/) | This separation matters. A valid video stream doesn't need to be re-encoded because V1 was disabled. A genuinely unsupported stream won't be repaired by toggling a track control. If your symptom falls outside the table, start with the [DaVinci Resolve troubleshooting map](https://davinciresolveclub.com/fix-davinci-resolve/) before changing the file. ## MP4 is a container, not the video codec The \`.mp4\` extension tells you how streams are packaged. It doesn't tell you whether the video is H.264, H.265, AV1, MPEG-4 Part 2, or something less common. It also doesn't reveal the profile, bit depth, chroma sampling, frame-rate mode, or whether the file was finalized correctly by the recorder. That's why two files from the same folder can behave differently. A phone export, screen recording, camera original, and downloaded clip may all end in \`.mp4\` while carrying different video streams. Resolve can read the audio stream and reject the video stream, which produces the familiar audio-only result. The current [official codec matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com) lists support by operating system, container, codec, and edition. Check the row for your operating system rather than relying on a general list copied from another tutorial. The public matrix located during this September 5, 2026 check is labeled Resolve 20; Resolve 21 is current, so use the support center for any newer matrix Blackmagic releases. ## Read the file with MediaInfo Install [MediaInfo from its official site](https://mediaarea.net/en/MediaInfo?ref=davinciresolveclub.com), open the problem file, and switch to Text or Tree view. Don't stop at the line that says MPEG-4\. Record the following fields: ![MediaInfo Tree view for an MP4 H.264 file showing profile frame-rate mode chroma subsampling and bit depth](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/mediainfo-mp4-streams-real-ui.webp) Read the Video section first. General > MPEG-4 alone does not expose the codec details you need. This real MediaInfo Tree view exposes AVC profile, constant or variable frame-rate mode, 4:2:0 chroma and 8-bit depth so you can compare the right Blackmagic matrix row. - **Format and codec ID:** identifies the actual video compression. - **Format profile and level:** narrows down which decoder capability the stream expects. - **Bit depth and chroma subsampling:** for example 8-bit 4:2:0 or 10-bit 4:2:2. - **Frame-rate mode:** constant or variable. - **Audio format:** the audio can be readable even when the video isn't. - **Duration and stream count:** spells out that the file actually contains a video stream. Then note Resolve's exact version and build from **DaVinci Resolve > About DaVinci Resolve**, whether it's Free or Studio, your operating system, and your GPU. Those details aren't forum bureaucracy. They determine which row of the codec matrix applies. ## Compare the stream with your OS and Resolve edition H.264 and H.265 in MP4 are common, but their support isn't identical on every platform. The official matrix shows broad H.264/H.265 decoding on macOS and Windows, with additional profiles and GPU acceleration tied to Studio in some Windows cases. Linux is more restrictive and can require Studio and compatible Nvidia hardware for streams that work elsewhere. | Environment | What to verify | Do not assume | | ----------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------- | | macOS | Codec, profile, OS-native decode support, and current Resolve build | Every damaged or unusual MP4 will decode because ordinary H.264 does | | Windows | Codec profile, bit depth, chroma sampling, Free/Studio differences, and GPU path | Every 10-bit file fails in Free or every H.265 file requires Studio | | Linux | The Linux section of the matrix, Resolve edition, codec, and Nvidia requirements | A file that works in VLC or on Windows must work in Resolve for Linux | Don't buy Studio based on the MP4 extension. Identify the exact stream first. Studio can expand supported profiles and hardware decoding, but it doesn't repair a truncated recording, a bad container header, or a disabled V1 patch. ## Fix V1 source patching when the Source Viewer has picture If the clip plays normally in the Source Viewer, Resolve has decoded the video. On the far left of the Edit page timeline, Resolve 21 uses a two-column [Source Track Selector](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20.2%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com): blue controls on the left represent source components, while red controls on the right represent timeline destinations. The two-column interface arrived in Resolve 20.2 and remains documented in Resolve 21. 1. Load the clip into the Source Viewer and confirm that picture is visible. 2. On the timeline, make sure an unlocked video destination track exists in the red right column. 3. Enable the blue source V1 control and map it to the intended red video destination. 4. Enable only the blue source audio components you want and map them to suitable red audio destinations. 5. Perform a short overwrite or insert edit as a test. ![DaVinci Resolve 20.2 Source Track Selector with blue source V1 and A1 beside red timeline destinations](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-20-2-source-patch-real-ui.webp) The blue left column is the source clip; the red right column is the timeline. If the Source Viewer has picture but the edit inserts only audio, enable blue V1 and map it to an unlocked red video destination. Resolve 21 keeps this two-column model. If blue source V1 is absent because the Source Viewer contains an audio-only item, return to codec diagnosis. If blue V1 is present but can't be selected, check that a compatible red video destination exists and is unlocked. Don't transcode until this branch is ruled out. ## Use a safe repair ladder Work from the least destructive test to the most expensive conversion. Save the original camera or downloaded file in a separate location first. ### 1\. Test the file outside Resolve Open the MP4 in a second player and scrub near the beginning and end. A player succeeding doesn't prove Resolve supports the stream, because players ship different decoders. A player failing, freezing, or reporting a much shorter duration is useful evidence that the file is incomplete or damaged. ### 2\. Copy one clip to a simple local path Copy a single source to a local folder with a short filename. This separates codec trouble from cloud placeholders, disconnected volumes, read permission problems, and unstable network storage. Import that copy into a new empty project. Don't move the whole production until the test proves location is the cause. ### 3\. Compare it with a known-good file Import a small MP4 that already works on the same machine. If every supported test file fails after an update, investigate Resolve, the GPU driver, or the operating system. If only files from one camera or recorder fail, compare their MediaInfo reports. ### 4\. Remux only when the streams are already supported A remux places the existing streams into a fresh container without re-encoding them. It's fast and avoids generation loss, but it can't turn an unsupported video codec or profile into a supported one. The current [Shutter Encoder documentation](https://www.shutterencoder.com/documentation/?ref=davinciresolveclub.com) calls this Rewrap and requires the chosen output container to support the source codec. Use it only when MediaInfo shows compatible streams and the evidence points to a malformed header or container. ![Shutter Encoder Rewrap function with MP4 output selected for a container-only repair](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/shutter-encoder-rewrap-real-ui.webp) Rewrap copies supported existing streams into a new container without a video re-encode. This older Shutter Encoder interface shows the real function; the current 2026 documentation keeps the same rule: the destination container must support the source codec. After rewrapping, verify duration, picture, audio and sync. Keep the untouched source until the edit and final export are complete. ### 5\. Transcode an unsupported or unreliable stream Transcoding creates a new video stream. For editing, ProRes or DNxHR is usually a safer intermediate than repeatedly converting to another highly compressed delivery MP4. Choose a flavor appropriate to the source quality, preserve the source dimensions and intended cadence, and keep audio uncompressed when practical. Encode one short clip and test picture, audio, duration and sync before processing a batch. ![Shutter Encoder DNxHR HQ editing-codec conversion with source scale and frame-rate controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/shutter-encoder-dnxhr-real-ui.webp) DNxHR is a transcode, not a rewrap: it creates a new edit-friendly video stream. This real v16.6 screen uses an older layout, but DNxHR remains a current Shutter Encoder 20.2 editing-codec function. Do not copy the shown 30 fps blindly; preserve cadence unless a deliberate CFR conversion is required. An intermediate will be larger than the camera MP4\. That's expected. It trades storage for easier decoding and more predictable seeking. If storage or playback is the real constraint, the [proxy workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) explains how to create lighter working media without replacing your masters. ## Treat variable frame rate as a separate risk Phones, screen recorders, meeting apps, and browser capture tools often produce variable-frame-rate media. VFR can cause drifting sync, uneven playback, or frame-accurate editing problems. It does not automatically explain why Resolve sees no video stream at all. If MediaInfo reports variable frame rate and the clip imports but behaves unpredictably, encode a test copy to an intended constant frame rate and inspect it from start to finish. Shutter Encoder's [Conform control](https://www.shutterencoder.com/documentation/?ref=davinciresolveclub.com) changes frame-rate metadata and its documentation explicitly says it doesn't solve VFR. Don't type a frame-rate number into a converter without confirming the source cadence and timeline target. ## Update Resolve only when the evidence supports it A newer Resolve build can include decoder fixes, but updating is not the first move for one unusual file. Compare the release notes, back up the project library, export a project archive for important work, and confirm system compatibility. Follow the [safe Resolve update checklist](https://davinciresolveclub.com/update-davinci-resolve-safely/) instead of changing the application in the middle of diagnosis. If the whole application is unstable or decoding fails across many known-good files, confirm that the machine meets the current [Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). One unsupported MP4 and a general GPU or driver failure require different repairs. ## Avoid the fixes that create new problems - **Don't rename \`.mov\`, \`.mkv\`, or another extension to \`.mp4\`.** A new filename doesn't change the container or codec. - **Do not transcode before reading MediaInfo.** You may hide a V1 patching error or convert hundreds of clips unnecessarily. - **Don't assume HandBrake is a remux tool.** Its normal video workflow re-encodes, so choose settings deliberately and inspect the result. - **Don't delete the only source after one successful import.** Verify the full clip, sync, metadata, and final render first. - **Don't clear every cache folder for an import rejection.** Cache is relevant to generated working media, not to making an unsupported source stream decodable. ## Prevent the next MP4 import failure 1. Record a short test in the exact camera or capture settings planned for the job. 2. Import it into the same Resolve edition and operating system used for the edit. 3. Check the first and last minute for picture, audio, sync, and seeking. 4. Save a MediaInfo report with the camera preset notes. 5. If the source is VFR or difficult to decode, plan intermediates or proxies before the deadline. 6. Keep camera originals read-only and separate from generated media. ## Frequently Asked Questions ### Why does DaVinci Resolve import my MP4 as audio only? Resolve may be able to decode the MP4's audio stream but not its video stream. Use MediaInfo to check the actual video codec, profile, bit depth and chroma sampling. Then compare those fields with your operating system and Free or Studio edition in Blackmagic's codec matrix. If picture plays in the Source Viewer, check V1 source patching instead. ### Does DaVinci Resolve support MP4 files? Resolve supports many streams stored in MP4 containers, including common H.264, H.265, and AV1 cases, but support varies by operating system, codec profile, hardware, and edition. The \`.mp4\` extension alone can't prove compatibility. ### Can I fix the file by changing its extension? No. Renaming an extension doesn't change the container, video codec, or file structure. Remux the streams into a fresh container when they're supported, or transcode to a supported edit codec when the video stream itself is the problem. ### Should I convert the MP4 to H.264? Not automatically. H.264 still has profiles, bit depths, and platform-specific decoding limits, and another delivery codec may remain difficult to edit. For an unsupported source, ProRes or DNxHR is usually a more predictable intermediate. Test one clip before processing a batch. ### Why can I see video in the Source Viewer but only audio reaches the timeline? That symptom usually points to source patching rather than codec support. Enable the blue source V1 control, map it to an unlocked red video destination track, and repeat a short insert or overwrite edit. ### Export Transparent Video in DaVinci Resolve (Alpha) URL: https://davinciresolveclub.com/davinci-resolve-export-transparent-background/ Last updated: 2026-09-05T02:27:35.000Z **Quick answer:** To export transparent video from DaVinci Resolve 21, first confirm that the empty area is genuinely transparent, not filled by a black clip or an opaque Fusion Background node. On the Deliver page choose Single Clip for the completed composition, select an alpha-capable format/codec/type combination that your installation exposes, enable **Export Alpha**, and render a short test. If Export Alpha doesn't appear, the current output cannot carry alpha. Reimport the file above a bright layer before trusting it. A checkerboard in Fusion is only the first gate. The composition must reach MediaOut with alpha, the output codec must store RGBA, and Resolve must be told to write the alpha channel. These Resolve 21 controls and codec examples were rechecked on September 5, 2026 against Blackmagic's current Reference Manual. Miss any one of those steps and transparent pixels become ordinary black pixels in the file. ![DaVinci Resolve Fusion page with a transparent checkerboard in the viewer and MediaIn connected to MediaOut](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fusion-transparency-real-ui.webp) Inspect the node connected to MediaOut. An upstream keyer alone does not prove that the final output contains transparency. The checkerboard confirms that this real Resolve 19 Fusion output contains transparent areas; the same RGBA viewer and MediaOut check applies in Resolve 21. ## Confirm the Timeline Contains Real Transparency Before changing render settings, prove that the frame has transparent pixels. Hide every video track that shouldn't be part of the overlay. Remove Solid Color generators, full-frame adjustment graphics and background plates that fill the frame. In Fusion, follow the final pipe into **MediaOut**. A black Background node isn't automatically transparent. Select it and check its Alpha value: zero is transparent, while a value above zero creates opaque or partially opaque black. If a Merge node is used, the transparent image should remain the background canvas and the title, key or graphic should enter the foreground input. 1. Open the final clip or Fusion composition. 2. View the node connected directly to MediaOut. 3. Toggle the viewer from RGB to Alpha and look for white/gray content against black transparent areas. 4. Return to the Edit page and make sure no lower track fills the intended empty area. 5. Render a short two-second test before committing a long sequence. If you still need to create the cutout, use the [Fusion rotoscoping workflow](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/) or follow the [Delta Keyer settings guide](https://davinciresolveclub.com/davinci-resolve-delta-keyer/) first. Export settings preserve an existing matte; they don't remove a background on their own. ## Choose Single Clip or Individual Clips | Render mode | Use it for | What the alpha represents | | ---------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------ | | Single Clip | A finished title, lower third, keyed composite or complete transparent timeline | One alpha channel for the composited timeline output | | Individual Clips | Round-trip source clips, keyed shots or separate VFX plates | Each source clip's embedded alpha or Color-page Alpha Output | For a finished motion-graphics overlay or transparent timeline, choose Single Clip. Resolve 21 has a dedicated Single Clip alpha workflow when the selected codec supports a fourth channel. Choose Individual Clips when each source needs its own file, source naming, handles, embedded source alpha, or Color-page Alpha Output. This distinction matters because some older tutorials still say alpha works only in Individual Clips. That advice is incomplete for Resolve 21\. Single Clip writes one alpha channel for the composited timeline; Individual Clips preserves or creates alpha separately for each delivered source clip. ## Pick a Format and Codec That Can Store Alpha ![DaVinci Resolve 20 Deliver page with QuickTime GoPro CineForm RGB 16-bit and Export Alpha enabled](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/deliver-export-alpha-real-ui.webp) Real Resolve 20 Deliver settings: an RGBA-capable codec makes Export Alpha available. Resolve 21 uses the same control names, but the format, codec and type choices shown by your installation are the ones that count. The container and codec are different choices. QuickTime is a wrapper; ProRes 4444, ProRes 4444 XQ and DNxHR 444 are codecs that can carry alpha in supported Resolve configurations. ProRes 422, H.264 and the usual H.265/MP4 delivery choices aren't substitutes for ProRes 4444 just because they appear in the same Format menu. | Output | Best fit | Tradeoff | | -------------------------- | -------------------------------------------------------- | ----------------------------------------------------------- | | QuickTime + ProRes 4444 | High-quality motion graphics and NLE handoff | Large files; encoder availability depends on system/install | | QuickTime + ProRes 4444 XQ | Higher-data-rate mastering when the pipeline requires it | Usually unnecessary for simple web overlays | | QuickTime + DNxHR 444 | RGBA interchange when DNxHR suits the receiving system | Confirm import support and alpha interpretation downstream | | OpenEXR or TIFF sequence | VFX interchange, long renders and frame-level recovery | Many files and more storage management | Blackmagic's [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) names TIFF, OpenEXR, ProRes 4444, ProRes 4444 XQ and DNxHR 444 as RGBA examples in the Deliver alpha workflow. These are examples, not a promise that every encoder appears on every operating system or Resolve installation. Use the options actually shown by your Resolve installation. Operating system, Resolve edition, hardware and codec support can change the Format, Codec and Type menus. Don't force a tutorial's exact preset when it's absent. Choose another exposed RGBA combination and test one short file in the application that will receive it. ## Use the Correct Deliver Settings 1. Open the **Deliver** page and set the intended render range. 2. Choose **Single Clip** for a completed transparent composition, or Individual Clips for source-by-source output. 3. Select an alpha-capable Format, Codec and Type. 4. Match resolution and frame rate to the destination. 5. Enable **Export Alpha**. 6. Choose Straight or Premultiplied only when the receiving application's requirements are known. Premultiplied is Resolve's documented default in Single Clip mode. 7. Add the job to the Render Queue and render a short test. If the Export Alpha checkbox is missing, stop. Resolve only shows it when the selected output supports alpha. Changing the filename extension or placing transparent pixels in Fusion can't make an RGB-only codec carry a fourth channel. For ordinary opaque delivery, use the broader [export settings guide](https://davinciresolveclub.com/davinci-resolve-export-settings/). An alpha master is normally an intermediate asset for another editor, compositor, live graphics tool or web conversion step, not the final YouTube upload. ## Keep the Fusion Pipe Transparent A reliable title setup can start with a Background node whose Alpha is zero, then merge the title or foreground over it and send the result to MediaOut. A keyed subject can carry alpha from the keyer or matte tools. Inspect the Alpha channel on the node connected to MediaOut, because a later Merge, effect or opaque background can fill or alter it. If you're new to the page, the [Fusion beginner tutorial](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) explains the MediaIn, Merge and MediaOut flow. For a transparent export, the important addition is to inspect the fourth channel at the end of that flow. ### Do not confuse black RGB with opaque black Transparent pixels still have RGB values. A viewer may display those pixels against black even when their alpha value is zero. That's why the appearance of a standalone file in a player isn't a sufficient test. ### Avoid unnecessary full-frame effects Adjustment clips, background generators and some effects can change the result or its edges. If an alpha render develops a black rectangle or fringe, bypass downstream effects one at a time and inspect the final Alpha view again. ## Choose Straight or Premultiplied Alpha Deliberately Straight and Premultiplied aren't stronger and weaker transparency. They describe how RGB values around semitransparent edges relate to alpha. - **Straight:** RGB remains unmultiplied by alpha. It preserves full edge color but must be interpreted correctly by the receiver. - **Premultiplied:** RGB has been multiplied by alpha. Fusion's Merge expects a premultiplied foreground, and Resolve documents Premultiplied as the Single Clip export default when the codec offers the choice. A mismatch can create a dark halo, a bright fringe or washed semitransparent pixels. Start with the destination's documented expectation. If there is no specification, export a short test with the default, reimport it, and try the other mode only when the edge proves wrong. When an imported file has the wrong edge behavior, right-click it in the Media Pool, open Clip Attributes, and change Alpha Mode rather than rebuilding the key. Resolve 21 documents None, Premultiplied, Invert and Straight/nonpremultiplied handling. Judge the setting over a visible layer at 100%, not from the file thumbnail. ![DaVinci Resolve Clip Attributes Video tab with Alpha Mode options None Premultiplied Invert and Straight](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/clip-attributes-alpha-mode-real-ui.webp) Clip Attributes changes how Resolve interprets an imported alpha channel. Try Straight or Premultiplied only when a real edge test shows that the current interpretation is wrong. ## Verify Transparency Instead of Trusting the Player ![DaVinci Resolve 19 Edit page with a transparent overlay composited on a video layer below](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/alpha-reimport-composite-real-ui.webp) A real compositing test is stronger than a player window. Put the rendered asset on V2 over visible footage or a bright solid on V1 and inspect the transparent area and semitransparent edges. 1. Create a new empty timeline or use a clean section away from the source composition. 2. Place a bright Solid Color generator on V1. 3. Import the rendered file and place it on V2. 4. Confirm that the color is visible through the transparent area. 5. Inspect edges at 100% and during motion. 6. Check Clip Attributes if the alpha appears inverted or fringed. This test is stronger than playing the file by itself. Some players composite transparency over black; others don't expose video alpha at all. If the V1 color shows through cleanly, the file contains usable transparency even if its thumbnail looks black. ## Fix the Common Alpha Export Failures ### Export Alpha is missing The selected format/codec/type combination isn't alpha-capable in the current installation. Choose an exposed RGBA option such as ProRes 4444, ProRes 4444 XQ, DNxHR 444, TIFF or OpenEXR. ProRes 422 and ordinary H.264/H.265 delivery outputs don't gain alpha just because the source is transparent. ### The render is truly opaque black Return to the final composition. Hide lower video tracks, set any intended transparent Background node to Alpha 0, and inspect the Alpha channel on the node connected to MediaOut. Then confirm Export Alpha is enabled. ### The player shows black but Resolve composites correctly The player is displaying transparent pixels against black. The alpha is present. Test in the destination application rather than converting the file blindly. ### There is a dark or bright edge Check whether the receiving app expects Straight or Premultiplied alpha. Also bypass color corrections or effects applied after premultiplication. In Fusion, color work on premultiplied RGBA may require Pre-Divide/Post-Multiply so edge RGB is treated correctly. ### The destination does not accept the alpha master Keep the verified RGBA master, then make a separate destination-specific conversion that explicitly preserves alpha. Do not overwrite the working master. For a long render or uncertain VFX pipeline, an OpenEXR or TIFF sequence makes failed-frame recovery easier than restarting one large movie file. ## Use This Handoff Checklist - Timeline or Fusion output contains genuine transparent pixels. - MediaOut receives the final RGBA pipe. - Single Clip or Individual Clips matches the intended deliverable. - Codec/type supports alpha in this Resolve installation. - Export Alpha is enabled. - Straight/Premultiplied matches the destination or passes a short test. - Resolution, frame rate and duration are correct. - The exported file has been reimported above a bright background. - Edges and semitransparent motion are clean at 100%. - The verified alpha master is retained before any web or playback conversion. ## Frequently Asked Questions ### Which DaVinci Resolve codec exports a transparent background? Resolve 21 documents ProRes 4444, ProRes 4444 XQ and DNxHR 444, plus RGBA image sequences such as TIFF and OpenEXR. Use an alpha-capable format/codec/type combination that your installation actually exposes. ### Why is Export Alpha not showing in DaVinci Resolve? Resolve only displays Export Alpha when the selected format, codec and type support an alpha channel. Change to an RGBA-capable option; renaming an RGB-only output won't add transparency. ### Can DaVinci Resolve export alpha as Single Clip? Yes. The Resolve 21 manual documents Single Clip alpha export when the selected codec supports it. Use Single Clip for a finished transparent composition and Individual Clips for separate source or round-trip files. ### Why does a transparent video look black after export? The alpha may be missing, or the player may simply display transparent pixels over black. Reimport the file above a bright solid layer. If the color shows through, the alpha is present. ### Should alpha be Straight or Premultiplied? Use the mode required by the receiving application. Premultiplied is Resolve's documented default for Single Clip when available. Change modes only when the destination or an edge test shows an interpretation mismatch. ### Can I export transparent H.264 or MP4 from Resolve? Don't use the ordinary H.264/H.265 MP4 delivery path for this workflow. Export an alpha-capable master or image sequence first, verify it, then create a separate destination format that explicitly preserves alpha if needed. This workflow sits inside the [export hub](https://davinciresolveclub.com/davinci-resolve-export-settings/). Continue with the [Fusion learning map](https://davinciresolveclub.com/davinci-resolve-fusion/) when the real problem is building or refining the matte rather than writing it to a file. ### Stabilize Video in DaVinci Resolve: Edit, Color & Fusion URL: https://davinciresolveclub.com/davinci-resolve-stabilize-video/ Last updated: 2026-09-05T02:17:51.000Z **Quick answer:** Select the finished timeline clip, open Inspector > Video > Stabilization, and start with Translation when the unwanted movement is only horizontal or vertical. Leave Zoom on for a normal full-frame result, click Stabilize, and watch the entire shot. Use Similarity when rotation or scale must be corrected; try Perspective only when its perspective model improves the shot without bending the image. Stabilization trades movement for transformed frame area. Zoom can hide the blank edges created by correction, but stronger correction usually means more crop. These Resolve 21 steps were rechecked on September 5, 2026 against the current [Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com); every mode or Smooth/Cropping Ratio change requires another click on Stabilize. The goal isn't to make every handheld shot look bolted to a tripod. It's to remove the high-frequency shake, bump or drift that pulls attention away from the subject while preserving the move that belongs in the shot. ![DaVinci Resolve 20 Edit page Inspector with Stabilization expanded and controls for mode, Camera Lock, Zoom, Cropping Ratio, Smooth and Strength](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/stabilize-edit-inspector-real-ui.webp) Real Resolve 20 Edit Inspector from Storyblocks' May 2025 walkthrough. The same control names and behavior were rechecked in the Resolve 21 manual. Select the finished clip, choose the motion model and run Stabilize before judging the entire shot. ## Prepare the Shot Before You Stabilize It 1. Finish the clip's in and out points. Stabilize the duration that will actually be used. 2. Remove speed ramps or confirm their final timing before analysis. 3. Correct lens distortion first when it's severe enough to bend the motion model. 4. Check whether the problem is camera shake, subject movement, rolling shutter or motion blur. 5. Duplicate the timeline or keep an unstabilized version for comparison. A stabilizer can't reconstruct detail lost to motion blur, undo rolling-shutter skew perfectly or invent the frame edges that move out of view. It may hide some of those symptoms, but asking it to remove motion that's baked into each exposure often creates a sharper-looking path with visibly distorted frames. Analyze the final edit. Trimming or retiming a clip after stabilization can change the frame range and motion behavior that should be evaluated. Reanalyze when the used section changes. ## Use the Edit Page Stabilizer First 1. Select one clip on the Edit-page timeline. 2. Open the **Inspector** and expand **Stabilization**. 3. Choose a mode, starting with the simplest model that matches the unwanted movement. 4. Leave **Zoom** enabled for a normal full-frame result. 5. Click **Stabilize** and wait for analysis. 6. Play the whole shot at normal speed and compare stabilization on/off. ![DaVinci Resolve 20 Stabilization Mode menu showing Perspective, Similarity and Translation in the Edit Inspector](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/stabilize-mode-dropdown-real-ui.webp) Real Resolve 20 Mode menu from the same walkthrough, rechecked against Resolve 21\. Translation models pan and tilt; Similarity adds zoom and rotation; Perspective adds the broader perspective transform. The current [Edit page documentation](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) describes the same controls for reducing handheld shake, removing a bump or attempting a static lock-off. The real Edit and Color interface captures below come from [Storyblocks' May 2025 Resolve 20 walkthrough](https://www.storyblocks.com/resources/tutorials/davinci-resolve-stabilize-video?ref=davinciresolveclub.com), updated in April 2026; every label and behavior used here was rechecked against Resolve 21\. Don't judge from the first and last frames. Watch the middle, where crop, warping and recovery errors are easiest to spot. ## Choose Translation, Similarity or Perspective | Mode | Models | Start here when | Watch for | | ----------- | -------------------------------- | ------------------------------------------------------------- | ------------------------------------------------ | | Translation | Horizontal and vertical movement | The frame jitters in X/Y with little rotation or scale change | Residual rotation or zoom movement | | Similarity | Translation, rotation and scale | The camera rotates slightly or the subject distance changes | Crop pressure and scale breathing | | Perspective | Broader perspective-aware motion | The shot genuinely needs the more flexible model | Rubbery edges, faces bending and parallax errors | Start with Translation, then escalate. Perspective is not automatically the highest-quality setting; it simply allows a more complex correction. A simpler model can be more stable when the scene contains moving people, foreground parallax, water, foliage or a large object crossing the frame. Resolve 21 defines Translation as pan-and-tilt analysis, Similarity as pan, tilt, zoom and rotation, and Perspective as adding perspective analysis. Each mode changes the analysis and must be followed by another click on Stabilize; switching the menu during playback doesn't reuse an equivalent track. If eligible footage from a Blackmagic Cinema Camera contains embedded gyroscope data, Camera Gyro appears as another mode. It stabilizes from that recorded motion data. The option is conditional, so its absence on another camera file is expected rather than a missing Resolve control. Compare its full-shot result with image-based stabilization instead of assuming either source is automatically better. ## Tune Crop, Smoothness and Strength - **Zoom:** enlarges the image enough to hide blank edges created by the correction. Disable it when a compositor needs the complete moving frame and will fill edges separately. - **Cropping Ratio:** limits how aggressively stabilization can work. At 1.0 no stabilization is applied; progressively lower values allow more correction and therefore more blanking or automatic zoom pressure. - **Smooth:** controls how much analyzed motion is smoothed while allowing intended movement to remain. - **Strength:** scales how tightly the analyzed correction is applied. - **Camera Lock:** attempts to remove all camera movement and disables the normal smooth-motion tradeoff controls. ![DaVinci Resolve 20 Edit Inspector stabilization controls with Similarity, Camera Lock, Zoom, Cropping Ratio, Smooth and Strength](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/stabilize-controls-real-ui.webp) Real Resolve 20 controls, rechecked against Resolve 21\. Zoom hides exposed edges, Cropping Ratio limits correction pressure, Smooth changes the analyzed motion curve, and Strength scales the current analysis. Change one control at a time. Mode, Cropping Ratio and Smooth require another click on Stabilize because they change the analysis; Strength scales the correction from the current analysis. If a result is smooth but visibly warped, reduce Strength or use a simpler mode before sacrificing more frame. If the ugly jitter is gone while some intended handheld movement remains, that may already be the best result. Camera Lock suits a shot that was supposed to be static, such as a tripod interview bumped by wind. It's usually the wrong first choice for a deliberate pan, push-in or walking shot because it tries to erase the move rather than clean it. ## Edit and Color Use the Same Stabilizer The Color page isn't a second automatic algorithm to stack after Edit. Blackmagic's Editors Guide states that the Inspector controls are the same stabilizer found in the Color-page Tracker palette and that the result carries between them. Color adds the tracker graph and deeper inspection. 1. Open the clip on the **Color** page. 2. Open the **Tracker** palette and select its Stabilizer controls. 3. Inspect the analyzed path and compare the same mode/settings used from Edit. 4. Use the graph or classic controls only when they provide a specific correction you can't make from the simple Inspector view. ![DaVinci Resolve 20 Color page Tracker Stabilizer graph with Cropping Ratio, Smooth, Strength, Camera Lock, Zoom and Similarity controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/stabilize-color-tracker-real-ui.webp) Real Resolve 20 Color Tracker, rechecked against Resolve 21\. It shows the same clip-level stabilization analysis as Edit plus its motion graph; the source arrows identify Tracker and Stabilizer, not a second pass to stack. Don't stabilize once in Edit and again in Color expecting twice the quality. You're looking at the same clip-level process. If the automatic tracker follows the wrong motion, move to a workflow where you choose the tracked feature instead of piling on another pass. ## Move to Fusion When You Need a Chosen Target Use Fusion when automatic whole-frame analysis follows the wrong subject or when the shot needs an explicitly chosen track. The standard Tracker is the documented route for removing or smoothing camera motion from the background. Its real Operation tab below comes from [Creative Video Tips' practical Tracker walkthrough](https://creativevideotips.com/tutorials/fusion-split-screen-compositing?ref=davinciresolveclub.com); Match Move and BG only were rechecked against the Resolve 21 manual. A Planar Tracker serves a narrower purpose here: Steady is strong for checking a planar track or temporarily locking a surface while an effect is applied, but Blackmagic says it isn't very useful as the default full-shot stabilizer. The [Fusion tracking guide](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/) covers the wider tracking toolkit. ### Point-tracker route for shot stabilization 1. Add a Tracker with the clip connected to its yellow background input and place one or more patterns on sharp, persistent background features. 2. Track from a clear reference frame in both directions and repair every slip before using the motion. 3. In the Operation tab, choose Match Move and set Merge to BG Only for stabilization. 4. One pattern can correct position. Use at least two patterns when rotation or scale must also be corrected. 5. Choose Start or End for a fixed reference, or Start & End when the goal is to smooth a deliberate camera move rather than freeze it. 6. Inspect frame edges, crop and sharpness through the complete shot; stabilization can't restore image data that leaves the frame. ![DaVinci Resolve Fusion Tracker Inspector with Operation set to Match Move and Merge set to BG only for background stabilization](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/stabilize-fusion-match-move-bg-only-real-ui.webp) Real Fusion Tracker Operation tab from Creative Video Tips. Match Move with BG only applies the tracked correction to the yellow background input; the same labels and behavior are documented in Resolve 21. ### Planar Steady route for a locked effect workspace 1. Track one rigid, textured plane and exclude moving foreground objects or details at another depth. 2. Switch to Steady and inspect the tracked surface closely. Residual movement indicates a slipping track or a surface that wasn't actually planar. 3. For paint or another effect that needs a temporarily fixed plane, place the effect after the Steady Planar Tracker. 4. Use a second Planar Tracker with Invert Steady Transform after the effect to restore the original movement. 5. Keep Clipping Mode set appropriately for off-frame image data and remember that the steady/invert pair resamples the image. Don't confuse track inspection with final stabilization. Planar Steady is excellent for revealing drift: the chosen plane should stop moving while the rest of the frame distorts around it. For a normal full-shot correction based on selected features, use the point Tracker Match Move route. ## Fix Common Stabilization Failures ### The image bends or looks like jelly Switch from Perspective to Similarity or Translation, reduce Strength and inspect rolling shutter or parallax. A flexible warp cannot make foreground and background obey one camera plane when they move differently. ### The clip zooms in too far Use a higher Cropping Ratio or reduce Strength/Smooth, then reanalyze. Turn Zoom off temporarily to see the actual blank-edge movement. You can reframe after stabilization, but no anchor-point adjustment can restore image data that left the frame. ### The wrong subject appears locked A large moving person or car may dominate the automatic analysis. Shorten the clip, use a simpler motion model or track a chosen background feature/plane in Fusion. ### The result has micro-jitters Try a simpler mode, shorten the analyzed section and check whether the source itself has dropped frames, optical-stabilizer jumps or shutter artifacts. Higher Smooth is not always the fix when the track is wrong. ### Black edges enter the frame Enable Zoom for an automatic crop, reduce correction, or keep Zoom off and create a controlled dynamic reframe. For VFX work, preserve the edges and fill them downstream rather than hiding them with a large static zoom. ### The long shot works in one section and fails in another Split the used shot into motion phases and stabilize each section independently, hiding the cut where editorially safe. A single model may not fit a lock-off, fast pan and walk-and-talk inside the same long clip. ## Run a Playback and Export QC Pass 1. Compare stabilized and original playback at normal speed. 2. Watch faces, vertical lines and frame edges for warping. 3. Check the sharpest and most blurred moments. 4. Inspect the amount of crop against your delivery framing and captions. 5. Render a short range and check it outside Resolve. 6. Keep the original when the artifact is more distracting than the shake. Stabilization can make playback heavier while Resolve analyzes or renders effects. If the correction is good but editing becomes slow, use the [proxy and optimized-media workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) for responsiveness rather than weakening the final effect just to make the timeline play. If proxies don't solve it, follow the broader [slow playback diagnostic](https://davinciresolveclub.com/davinci-resolve-slow-playback/) to separate decoding, GPU and effect bottlenecks. ## Frequently Asked Questions ### What is the best stabilization mode in DaVinci Resolve? There's no universal best mode. Start with Translation, use Similarity when rotation or scale must be modeled, and try Perspective only when the broader correction improves the shot without warping it. ### Is Color-page stabilization better than Edit-page stabilization? No. They expose the same clip stabilizer and result. The Color Tracker adds a graph and deeper controls, but it isn't a separate pass to stack on top of Edit. ### Why does stabilization crop the video? Correcting motion moves and warps the frame, exposing blank edges. Zoom enlarges the image to hide them. More aggressive correction usually needs more crop. ### Should I enable Camera Lock? Use Camera Lock when the shot should have been static and you want to remove all camera motion. Leave it off for deliberate pans, pushes and handheld movement you only want to smooth. ### When should I stabilize in Fusion? Move to Fusion when automatic full-frame analysis follows the wrong subject or you need a chosen feature to define the motion. Use the standard Tracker in Match Move with BG Only for full-shot stabilization. Use Planar Tracker Steady mainly to inspect or temporarily lock a rigid plane for an effect, then invert that transform afterward. ### Can stabilization fix motion blur or rolling shutter? It can reduce the path of the movement, but it can't fully reconstruct detail blurred during exposure or guarantee removal of rolling-shutter skew. Aggressive correction can make those artifacts more visible. This guide belongs to the [DaVinci Resolve tutorial map](https://davinciresolveclub.com/davinci-resolve-tutorial/). Use the [Fusion hub](https://davinciresolveclub.com/davinci-resolve-fusion/) when the job changes from automatic cleanup to deliberate tracking, paint or compositing. ### DaVinci Resolve Color Management: RCM vs CST & LUT Order URL: https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/ Last updated: 2026-09-05T02:05:05.000Z **Quick answer:** Use Resolve Color Management when you want project-wide input, working-space and output transforms. Use CST nodes when you want those transforms visible and placed explicitly. For either workflow, identify each camera input correctly, grade in a known working space such as DaVinci Wide Gamut/Intermediate, and feed every LUT the color space and gamma it was designed to receive. Don't combine RCM with matching input/output CSTs unless you intentionally override part of the managed pipeline. A color-managed image is a controlled route from source encoding to a timeline working space and then to a display or file. Resolve Color Management runs that route at project level; Color Space Transform nodes make selected mappings visible in the graph. The workflows and version-sensitive labels below were rechecked on September 5, 2026 against the final [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). Most failures come from losing track of the signal: a clip is tagged as the wrong log curve, normalized twice, or sent into a LUT that expects a different input. This guide builds the pipeline from the signal outward so you can change cameras, LUTs or deliverables without guessing. Use the [Resolve scopes guide](https://davinciresolveclub.com/davinci-resolve-scopes-explained/) to judge whether the transform preserves useful highlight, shadow and saturation information instead of trusting the viewer alone. ![DaVinci Resolve RCM project-level and CST node-level color-management signal paths](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/rcm-cst-signal-path-v1.webp) RCM centralizes the input and output mapping; a manual CST workflow makes both transforms visible in the node graph. ## RCM and CST Solve the Same Mapping Problem | Question | RCM | CST workflow | | -------------------------------- | ------------------------------------------ | ------------------------------------------------------------ | | Where are transforms controlled? | Project settings and clip input tags | Visible nodes, groups or timeline nodes | | Mixed camera formats | Efficient when inputs are tagged correctly | Explicit but requires per-camera transform management | | Changing SDR/HDR output | Central output setting | Change or branch the output transform | | Debugging | Fewer visible nodes, more hidden state | Signal path is visible in the graph | | Image quality | Accurate when configured correctly | Accurate when equivalent transforms are configured correctly | Choose by project design, not by a claim that one route creates inherently better color. RCM is usually easier for long edits with mixed cameras and several deliveries. CSTs are useful when a colorist wants to inspect, move, group or branch transforms explicitly. Equivalent input, working and output mappings can be built either way, but RCM Output DRT and CST tone/gamut-mapping settings must also match before the rendered results can be compared. Don't enable DaVinci YRGB Color Managed and then add a camera-to-DWG CST at the start plus a DWG-to-Rec.709 CST at the end out of habit. RCM may already be doing both. That stack can normalize the source twice and apply the display transform twice. ## Understand Input, Timeline and Output Color Space - **Input color space:** the camera gamut and transfer function that encoded the clip, such as Sony S-Gamut3.Cine/S-Log3 or Blackmagic Wide Gamut/Film Gen 5. - **Timeline color space:** the working environment in which color-aware tools and nodes operate. - **Output color space:** the target display or deliverable mapping, such as Rec.709 Gamma 2.4 for a controlled SDR viewing environment. An input tag isn't a creative conversion. It tells RCM how to interpret the numbers already in the file. Wrong tags produce wrong contrast, saturation and hue before you touch a wheel. Do not identify a clip by how flat it looks. Check camera metadata, the production notes or the source-camera settings. Automatic color management can save time when files carry reliable metadata, but inspect mixed-camera and transcoded media. A transcoded file may no longer expose enough information for correct identification. In a managed project, right-click clips in the Media Pool or Color-page clip strip and assign the actual Input Color Space when needed. ## What DaVinci Wide Gamut and Intermediate Actually Mean **DaVinci Wide Gamut** is the color gamut. **DaVinci Intermediate** is the companion log-like transfer function. Together they form a large scene-referred working space designed to hold camera data and behave consistently across SDR and HDR grades. Working in DWG/Intermediate doesn't make every source HDR, recover clipped sensor data or improve an 8-bit file. It gives correctly transformed sources a common, roomy environment. You still need to balance exposure and color, match shots and control saturated colors. In a manual DaVinci YRGB plus CST workflow, setting the project's Timeline Color Space to DWG/Intermediate doesn't perform the input or output conversion. It declares the working environment to color-space-aware tools and output metadata; the explicit CST nodes still perform the image mappings. ## Set Up Resolve Color Management 1. Open **Project Settings > Color Management**. 2. Set **Color science** to **DaVinci YRGB Color Managed**. 3. Disable Automatic color management if you need to inspect and control custom input, timeline and output settings directly. 4. Choose **DaVinci Wide Gamut/Intermediate** as the timeline working space. 5. Set the output to the actual monitoring and delivery target. 6. Save, then verify and correct the Input Color Space for every source family. 7. Grade in normal clip/group nodes without adding redundant normalization CSTs. The output transform occurs after the managed grading pipeline. This makes it convenient to change a well-built scene-referred grade from an SDR output to a separately checked HDR output, but it doesn't remove the need for output-specific trim and monitoring. RCM handles mapping, not shot correction. A correct source tag can't know that the camera was two stops under, the white balance was wrong or one angle used a different ND filter. Continue with the balancing and shot-matching process in the [color grading guide](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/). The real Resolve 21 panel below comes from [Video Village's May 2026 Resolve 21 photography workflow](https://videovillage.com/blog/2026/05/12/filmic-photography-resolve-21?ref=davinciresolveclub.com). Its sRGB output is correct for that example, not a universal video preset; choose the output that matches your calibrated monitoring and delivery target. ![DaVinci Resolve 21 Project Settings showing DaVinci YRGB Color Managed, automatic color management off, DWG Intermediate processing and output color space](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-rcm-project-settings-real-ui.webp) Real DaVinci Resolve 21 Project Settings from Video Village's May 2026 workflow. This example targets sRGB photography; for video, keep the same controlled RCM structure but set Output Color Space to the actual calibrated monitoring and delivery target. ## Build a Manual CST Sandwich For explicit node-based management, leave project Color science on **DaVinci YRGB**. Then build a clean signal path: 1. **Input CST:** camera gamut/gamma to DaVinci Wide Gamut/DaVinci Intermediate. 2. **Balance:** exposure and white-balance corrections. 3. **Shot match:** align the scene. 4. **Look:** creative contrast, palette and texture in the known working space. 5. **Output CST:** DWG/Intermediate to the monitoring/delivery space. 6. **Output-space finishing:** only effects intentionally designed for that display space. For many clips from one camera, put the input transform at Group Pre-Clip level. Put a shared output transform at Group Post-Clip or Timeline level when the whole group or timeline shares one destination. Keep clip nodes for shot-specific work. This prevents 100 slightly different copies of the same technical transform. The Colorist Guide also documents a valid single-CST pattern: grade upstream in the source space and transform camera input directly to output near the end. The two-CST sandwich is easier when several camera families need a common working space; it isn't a law for every project. ## Place LUTs by Their Input and Output Contract Before applying any LUT, answer two questions: 1. What gamut and gamma does the LUT expect? 2. What gamut and gamma does it produce? A camera technical LUT may expect one exact log profile and output Rec.709\. A creative show LUT may expect and return DWG/Intermediate. A film-print emulation may expect Cineon Film Log and produce a display-referred Rec.709 result. Resolve can't infer those conditions from a generic `.cube` file. | LUT type | Safe placement logic | Common error | | ----------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------- | | Camera log to Rec.709 technical LUT | Use it as the intended normalization/output mapping, or do not use it | Adding it after RCM already mapped the same camera to Rec.709 | | DWG-to-DWG creative LUT | Inside the DWG/Intermediate grading section | Feeding it camera log or display-referred Rec.709 | | Rec.709 creative LUT | Feed it the specified Rec.709 variant and account for its output | Dropping it directly into a DWG node tree | | Resolve film-print LUT | Prepare its documented Cineon Film Log input and design the output path around it | Treating it as a generic DWG look | The official [Resolve 20 Colorist Guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf?ref=davinciresolveclub.com) says the bundled Rec709 Kodak 2383 film-look LUTs anticipate Cineon Film Log as the input transfer function and are intended for Rec.709 monitoring or delivery. Its worked example converts the incoming Rec.709 gamma to Cineon immediately before the LUT. If you don't want to manage that contract and its display-referred result explicitly, use a DWG-native look or a suitable film-look tool instead of treating the LUT as a generic DWG look. For installation, preview and intensity controls, use the separate [Resolve LUT guide](https://davinciresolveclub.com/how-to-use-luts-in-davinci-resolve/). The rule here's narrower: the node before a LUT must produce what that LUT expects. ![LUT input and output contract examples for camera technical LUT, DWG look LUT and Resolve Kodak 2383](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/lut-contract.webp) A LUT has a fixed signal contract. Feed it the documented input and continue from the space it produces; its position is a consequence of that contract. ## Choose Node Order Without Memorizing a Template ![DaVinci Resolve double-transform diagnostic for duplicate RCM and CST input or output mapping](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/double-transform-diagnostic-v1.webp) Keep one intentional input path and one intentional output path; duplicated mapping changes the starting or delivery image. Ask of every node: what space enters, what operation happens, and what space leaves? A qualifier may key differently before and after a display transform. Grain or halation may be designed for scene-referred or display-referred values. A LUT has a fixed contract. Put the operation in the section it was designed for. A practical wide-gamut tree is: **Camera input to DWG/I | balance | matching | look | DWG/I to output | output-specific finish** In RCM, the first and last stages are managed outside the visible clip tree. In a CST workflow, you can see them. If a particular look requires Rec.709 or Cineon, build a deliberate transform around that operation rather than pretending the whole node tree changed spaces. ## Diagnose Double Transforms and Wrong Tags ### The log image becomes harsh before grading Bypass CST and LUT nodes one at a time. If RCM is enabled and a technical LUT or input CST adds the same normalization, remove the duplicate. Also verify the clip's Input Color Space. ### Changing the RCM output makes the image break A display-referred LUT or node may be sitting inside the scene-referred tree. Identify what that operation expects. A DWG-native look should survive an output change more predictably than a Rec.709-baked LUT. ### Different cameras do not match after RCM First verify every input tag. Then balance exposure and white balance. Color management normalizes encoding; it doesn't erase sensor, lens, lighting or exposure differences. ### The manual CST image looks different from RCM Compare the actual input gamut/gamma, output gamut/gamma, tone mapping, gamut mapping and timeline settings. "CST to Rec.709" isn't specific enough; several Rec.709 gamma choices and mapping options can produce different results. ### The LUT looks correct only after random CSTs Stop and inspect the LUT documentation or filename. Reconstruct its stated input and output deliberately. A visually pleasing accidental chain can still clip, remap or double-transform values in ways that fail on the next shot. ## Validate the Pipeline Before the Full Grade 1. Choose representative clips from every camera and graphics source. 2. Verify source tags and transform only those clips. 3. Check scopes for clipping and out-of-gamut behavior. 4. Temporarily bypass the look and confirm the technical pipeline remains coherent. 5. Test the darkest, brightest and most saturated shots. 6. Render a short file with the intended output tags and inspect it on the target playback path. 7. Only then ripple the pipeline across the project. Monitoring is part of color management. A correct Rec.709 mapping viewed on an uncalibrated display or through a player with different color handling can still look inconsistent. The pipeline and the viewing path must both be known. ## Frequently Asked Questions ### Is RCM better quality than CST? No inherent quality advantage exists when both routes use equivalent input, timeline and output transforms with matching tone- and gamut-mapping choices. RCM centralizes the pipeline; CSTs expose selected mappings in nodes. Operational consistency and deliberate settings are the deciding advantages. ### Do I need CST nodes in a color-managed project? Usually not for the same input-to-timeline and timeline-to-output transforms RCM already performs. Use a CST only for an intentional local conversion, special effect or LUT requirement, and return to the expected managed space when necessary. ### What is the difference between DWG and DaVinci Intermediate? DaVinci Wide Gamut defines the color gamut. DaVinci Intermediate defines the transfer function used with it. Together they form the common DWG/Intermediate working space. ### Where should a LUT go in the node tree? Place it where the incoming gamut and gamma match the LUT's documented input, then account for the LUT's output. There's no correct universal position for every LUT. ### Why does my image look double-normalized? RCM may be applying an input or output transform while a CST or technical LUT applies the same conversion again. Bypass each mapping stage and keep only one intentional route. ### Should I grade before or after the output CST? In a scene-referred wide-gamut workflow, perform most balancing, matching and look work before the output CST. Put only operations intentionally designed for the output/display space after it. This guide is part of the [DaVinci Resolve color grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/). Use the hub to move from pipeline setup into balancing, matching, LUT work and delivery checks without mixing their intents. ### DaVinci Resolve Audio Ducking: Ducker, AI & Sidechain URL: https://davinciresolveclub.com/davinci-resolve-audio-ducking/ Last updated: 2026-09-05T01:56:00.000Z Quick answer: Put dialogue and music on separate tracks, select the music track, enable Ducker, and choose the dialogue track as Source. Start with a modest Duck Level in the Inspector, then tune Lookahead, Rise Time, Hold and Recovery until speech stays clear without obvious pumping. Use the current Fairlight Dynamics sidechain when a track or bus should control another track or bus; use manual keyframes for editorial exceptions. Audio ducking has one job: clear space for the words while keeping the music emotionally present. The technical setup takes minutes. The difficult part is making the movement quiet enough that viewers hear the dialogue, not the mixer working. DaVinci Resolve 21 offers three routes that are often described as the same feature. Ducker Track FX is the fastest direct method. Fairlight sidechain compression provides routing and compressor control for tracks or busses. Studio's AI Audio Assistant can apply ducking during a much broader automatic mix. Choose deliberately instead of stacking all three. ## Pick the Right Ducking Method | Situation | Best route | Why | | ------------------------------------------------------ | ------------------------------------ | ------------------------------------------------------------------------------- | | One or more dialogue tracks should lower a music track | Ducker Track FX | Fast setup, purpose-built timing controls and clear source selection. | | A dialogue bus should control a music bus | Fairlight compressor sidechain | The Dynamics sidechain can use a track or bus as its detector source. | | Only a few phrases need a carefully shaped dip | Volume keyframes or fader automation | You decide exactly where and how far every move happens. | | The entire unmixed timeline needs a first-pass mix | AI Audio Assistant in Studio | It categorizes and balances the larger mix, with ducking as only one operation. | Ducker Track FX is available in the free version as well as Studio. The official [Fairlight Audio Post guide](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveFairlightAudioPost.pdf?ref=davinciresolveclub.com) explicitly says the free Resolve 20 build shows two Track FX, Dialogue Leveler and Ducker. On September 5, 2026, the current Resolve 21 Reference Manual still documented Ducker without a Studio-only label. AI Audio Assistant is different: its manual heading is explicitly Studio Version Only. ## Prepare Dialogue and Music Before Ducking Automation can't fix a timeline whose categories are mixed together. Keep dialogue on dialogue tracks and music on music tracks. Don't place a voiceover clip between music clips on the same track and expect a track-level Ducker to understand the editorial meaning. 1. Move speech to clearly named tracks such as **Dialogue** or **VO**. 2. Keep the bed on a separate **Music** track. 3. Set a sensible static balance first. The music should already be close to its non-dialogue level. 4. Clean obvious bumps, clothing noise and long empty regions from the dialogue source. 5. Listen once without ducking and mark the places where the voice is actually masked. Ducking reacts to signal level, not meaning. A breath, mic bump or loud room tone can trigger it just like a word. Basic clip cleanup from the [mute and split audio workflow](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/) often prevents more false triggers than another round of control tweaking. ## Set Up Ducker Track FX 1. Open the **Edit** or **Fairlight** page and expose the audio mixer. 2. Select the **music track**. This is the target whose level will be reduced. 3. Open Track FX from the track's Inspector or mixer channel and enable **Ducker**. 4. In **Source**, choose the dialogue or voiceover track that should trigger the reduction. 5. Add more dialogue sources with the plus control when several speakers live on separate tracks. 6. Loop a section containing speech, silence and another speech phrase while you tune the controls. Put the Ducker on the music, not the voice. The source is only the detector. The target is the signal that changes. This source-versus-target reversal is the most common setup mistake. Blackmagic's latest [Fairlight overview](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) describes the same flow: open Ducker on the target track, choose one or more dialogue sources, then adjust depth and recovery. In the full Ducker window, Command-click on macOS or Ctrl-click on Windows to add tracks; in the Inspector, use the plus control to create Source 2 and Source 3. The real interface frames below come from [Dunna Did It's January 2026 ducking walkthrough](https://www.youtube.com/watch?v=nQ50HyeBHDg&ref=davinciresolveclub.com) in Resolve Studio 20; the controls and paths were checked against the current Resolve 21 manual. ![DaVinci Resolve Studio 20 Track Inspector with Ducker enabled on the music track and Dialogue 01 selected as Source 1](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/ducker-inspector-source-real-ui-1.webp) Real DaVinci Resolve Studio 20 interface from Dunna Did It's January 2026 audio-ducking walkthrough. Ducker is enabled on the target music track, while Dialogue 01 is the source; the same target/source path is documented in the current Resolve 21 manual. ## Understand the Ducker Controls - Duck Amount / Duck Level: how far the target track is reduced while a source is active. The full Ducker window says Duck Amount; the Inspector says Duck Level. - **Lookahead:** lets reduction begin before the detected speech reaches the output, preventing the first syllable from fighting the music. - **Rise Time:** how the Ducker moves into the reduced state. - **Hold:** how long it stays reduced through a short pause. - **Recovery:** how it returns toward the original music level after speech. ![DaVinci Resolve Studio 20 Ducker Track FX window with Source, Duck Level, Lookahead, Rise Time, Hold and Recovery controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/ducker-timing-controls-real-ui-1.webp) Real DaVinci Resolve Studio 20 Ducker window from the same January 2026 walkthrough. The full Resolve 21 window calls the depth control Duck Amount; the Inspector calls it Duck Level. Tune depth first, then entry, pause handling and return. Start with depth, then timing. Lower Duck Amount until the words are clear, but stop before the music appears to fall through a trapdoor. Next, tune the entrance around the first syllable. Finally, set Hold and Recovery so brief pauses inside a sentence don't make the music breathe between every few words. There's no universal dB preset. The Resolve 21 manual gives 2.7 dB as the default and says 2 to 5 dB works best most of the time, but that's a starting range, not a delivery standard. A sparse piano bed, dense rock track, quiet narrator and energetic presenter mask one another differently. Use the actual program and monitor at a realistic playback level. ## Use Fairlight Sidechain Compression for Tracks or Busses Ducker is Track FX. When several dialogue tracks feed a dialogue bus and music stems feed a music bus, use the Dynamics sidechain on the music bus. In Resolve 21, choose the source track or bus directly inside the Sidechain module. Tutorials that tell you to enable Send on the dialogue channel and Listen on music are showing the pre-19 routing. The [Fairlight bus routing guide](https://davinciresolveclub.com/fairlight-bus-routing/) explains the submix structure before you choose the detector. 1. Route dialogue tracks to a dialogue bus and music tracks to a music bus using the Fairlight bus assignments. 2. Open **Dynamics** on the music bus. 3. Enable the **Compressor**. 4. In the compressor's Sidechain area, switch sidechain **On**. 5. Choose the dialogue bus as the sidechain source. 6. Use **Listen** briefly to confirm the detector hears the intended dialogue bus, then turn Listen off. 7. Set Threshold and Ratio for gain reduction; shape the move with Attack, Hold and Release. Threshold determines when the detector causes compression. Ratio controls how strongly the music is reduced after that threshold is crossed. Attack controls entry; Hold keeps the reduction steady; Release controls the return. The [Fairlight compressor guide](https://davinciresolveclub.com/fairlight-compressor-dialogue/) explains the same controls in a dialogue context. Watch the gain-reduction meter, but decide with your ears. A sidechain isn't an audible cable from dialogue into music. The dialogue bus remains in the normal mix. A detector feed measures it and controls the compressor on the music bus. If Listen remains enabled, you may hear only the detector and think the routing failed. ![Fairlight sidechain signal flow from three dialogue tracks through a dialogue bus detector to gain reduction on the music bus](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/sidechain-bus-signal-flow-2026.webp) Dialogue remains audible in the main mix. A separate detector path measures the dialogue bus and controls gain reduction on the music bus, which is why Sidechain Listen is only an audition tool, not the normal listening state. ## Where AI Audio Assistant Fits AI Audio Assistant is a whole-mix starting point in Resolve Studio, not simply a newer Ducker button. The current [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) says it can organize and color-code tracks, even dialogue levels, adjust mixer faders, clean dialogue, apply music ducking, write automation and add finishing processing for the chosen delivery standard. Use it only after separating audio elements by track and assigning the correct track categories. Run Timeline > AI Tools > Audio Assistant on an unmixed duplicate timeline, play the entire result, inspect written automation and compare it with the untouched version. If a track was categorized incorrectly, fix its Track Category and rerun the tool. If all you need is one music bed under one voiceover, Ducker is faster and more transparent. Don't run Audio Assistant, Ducker and a bus sidechain blindly on the same music path. Their reductions can add together and make the bed collapse. Bypass routes one at a time and keep the system whose result is easiest to control. ## Use Keyframes for Editorial Exceptions Automatic detection can't know that a musical hit should stay loud under a quiet line, or that the music needs to rise before the speaker finishes. Draw clip volume keyframes or record fader automation for those moments. ![DaVinci Resolve Studio 20 Edit timeline with dialogue above music and manual volume keyframes on the music waveform](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/manual-volume-keyframes-real-ui-1.webp) Real DaVinci Resolve Studio 20 Edit timeline from Dunna Did It's January 2026 walkthrough. Four points isolate the dip: two define the entrance, two define the return. Manual keyframes are the right choice when story timing should override a detector. A practical hybrid is: 1. Use Ducker or sidechain compression for the consistent baseline. 2. Bypass or reduce it for a shot where the music must lead. 3. Shape the exception with keyframes that begin before and finish after the words. 4. Check the handoff into the next automatic section for a level jump. Manual moves are slower, but they follow story rather than threshold. Use them where meaning matters more than repeatability. ## Fix Pumping, False Triggers and Bad Renders ### The music pumps between words Increase Hold or lengthen Recovery Time/Release so short speech gaps don't restore the full bed. If reduction is deep, make Duck Amount milder or lower the compressor ratio. ### The first syllable is masked Add enough Lookahead in Ducker or shorten compressor Attack. Confirm the trigger track begins with the actual consonant and does not have a late clip fade. ### Breaths and room noise trigger the music Clean or edit the source, then retest. On a compressor sidechain, adjust Threshold so useful speech crosses it but the noise floor doesn't. Don't gate aggressively enough to clip word endings. ### The music never returns Solo or Listen to the detector source. A noisy dialogue track may remain above threshold. Also check Hold/Recovery Time or Release, and make sure another dialogue source isn't continuously active. ### The timeline is clean but the render crackles Render a short problem range, then bypass Ducker or sidechain and render the same range again. This A/B test tells you whether the processor path is involved; it does not prove a general Resolve bug. If the fault follows the processor, save a duplicate project and rebuild that delivery move with keyframes or recorded automation. Verify both files in an external player before changing the rest of the mix. ## Finish the Mix After Ducking Ducking creates separation; it doesn't set final program loudness. Listen on headphones and small speakers, inspect the loudness meters and check the full mix for peaks after all busses and processing. The [Resolve LUFS and audio-level guide](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/) handles that delivery pass. Export a short representative section before the final render. Include a strong music entrance, normal dialogue, a pause and the loudest transition. If that section is clean, render the full program and check the resulting audio outside Resolve. The [audio export guide](https://davinciresolveclub.com/export-audio-davinci-resolve/) covers stems and audio-only files. ## Frequently Asked Questions ### Is audio ducking available in DaVinci Resolve Free? Yes. Ducker Track FX is available in the free edition. AI Audio Assistant is Studio-only. Fairlight's regular mixer and Dynamics tools provide the non-AI route for controlled mixes. ### Which track gets the Ducker effect? Put Ducker on the track you want to lower, usually music. Select dialogue as its source. The source triggers the change; the target receives it. ### What is the difference between Ducker and sidechain compression? Ducker is a purpose-built Track FX with direct depth and timing controls. Sidechain compression uses the Fairlight Dynamics compressor and can use a track or bus as the detector, making it better for bus-based mixes. ### Can several voice tracks trigger one music Ducker? Yes. Current Resolve versions let you add multiple source tracks in the Ducker. This is useful for dialogue split across speakers, microphones or voiceover tracks. ### How much should music duck under dialogue? There's no universal value. Reduce it only until the words remain clear on the intended playback devices. Deep, fast moves sound like pumping; dense music may need more space than a sparse bed. ### Should I use AI Audio Assistant instead? Use AI Audio Assistant in Studio when you want a first-pass mix across categorized dialogue, music and effects tracks. Use Ducker or sidechain when you want predictable control over one specific relationship. This guide is part of the [Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/). Start there for the complete path from track organization and dialogue cleanup through loudness, bus routing and delivery. ### DaVinci Resolve Subtitles: Create, Style, Import & Export URL: https://davinciresolveclub.com/davinci-resolve-subtitles-captions/ Last updated: 2026-09-05T01:47:20.000Z **Quick answer:** Use a subtitle track for readable captions you can edit, restyle and export. Import an SRT if the text is already timed, add cues manually if it isn't, or use [Create Subtitles from Audio](https://davinciresolveclub.com/transcribe-audio-davinci-resolve/) in Resolve Studio. Finish the edit before final timing, then choose a separate subtitle file, embedded captions or permanent burn-in on the Deliver page. Subtitles are easy to add and surprisingly easy to finish badly. A clean-looking track in the Edit page can still export an hour out of sync, lose its styling in an SRT file or disappear because the wrong subtitle track was enabled. The fix is to treat captions as four separate jobs: text, timing, presentation and delivery. This guide covers the subtitle-track workflow in DaVinci Resolve 21\. On September 5, 2026, Blackmagic's current [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) still documented the import, speech-to-text, timing, styling and delivery labels used below, while the [current Edit page](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) confirmed the broader subtitle-track workflow. The important boundary is between ordinary captions, Studio speech-to-text tools and Text+ graphics: choosing the wrong route at the start creates most of the avoidable work later. ## Choose the Right Caption Workflow First Resolve offers three routes that look related but do different jobs. Pick from the output backward: | You need | Use | Why | | ------------------------------------------------------------------- | --------------------------- | --------------------------------------------------------------------------------------- | | YouTube captions, localization files or accessible on/off subtitles | Subtitle track | Cues keep timecode and can export as SRT, VTT or TTML. | | Fast first-pass captions from spoken audio | Create Subtitles from Audio | Resolve Studio generates timed cues that you correct on a subtitle track. | | Animated words, kinetic typography or free placement | Text+ or a Fusion title | These are graphics, not normal caption cues, so they allow deeper animation and design. | The subtitle track is the default for long-form work because it keeps hundreds of cues manageable. Track style lets you change the common font, size, position, color, outline and background without rebuilding every line. Resolve supports several subtitle tracks for different languages or uses, but only one can be visible at a time. Name each track clearly before delivery because Resolve uses subtitle track names during export and encoding. Do not build a 20-minute caption job from separate Text+ clips just because a social tutorial demonstrates animated words. Use graphics only when the animation is part of the creative brief. Our [Text and Text+ guide](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/) covers that separate workflow. ## Add a Subtitle Track and Create Captions Manually 1. Open the finished timeline on the **Edit** page. 2. Right-click in the track-header area at the left of the timeline and choose **Add Subtitle Track**. 3. Move the playhead to the first spoken line. 4. Right-click the subtitle track and add a subtitle, or use the subtitle command available in your workspace menu. 5. Select the cue and open **Inspector > Caption** to type or correct the text. 6. Drag the cue's left and right edges until it enters and leaves with the spoken phrase. Keep captions as short reading units rather than transcribing punctuation mechanically. Break a line at a natural phrase boundary, not between an article and noun or a person's first and last name. Two balanced lines are usually easier to scan than one line that stretches across the frame. Lock picture before the detailed timing pass. If you trim dialogue after captions are finished, downstream cues may no longer match the speech. For a late edit, inspect every caption after the cut instead of assuming the track followed the editorial change correctly. ## Import an SRT Without Losing the Timing Resolve 21 imports subtitle files in SRT, SRTX, VTT, XML and TTML formats. SRT is the common interchange choice: it contains numbered cues, start and end timestamps, and plain text, but it does not carry your Resolve font, outline, screen position or animation. That separation is useful because timing and language can move between platforms while presentation stays under control in the project or player. 1. Open the Media Pool, right-click a bin or its background, choose Import Subtitle, then select the subtitle file. 2. Create a subtitle track if the timeline doesn't have one, or drag the file into the unused gray area above the video tracks and let Resolve create the track. 3. For manual placement, drag the file onto a subtitle track. Resolve places the cues relative to the first subtitle and the point where you drop the file. 4. When the subtitle file was authored against the same program timecode, right-click it and choose **Insert Selected Subtitles to Timeline Using Timecode**. 5. Play the first, middle and last cues before styling anything, then rename the track for its language or use. The classic failure is a zero-based SRT whose first cue starts near `00:00:01,000` and a timeline that starts at `01:00:00:00`. Absolute timecode placement puts them in different ranges. Either align the timeline start and SRT timestamps, or place the file relative to the playhead when that matches your intended workflow. If accented or non-Latin characters arrive as boxes or nonsense, save the subtitle file as UTF-8 and test a font that contains the required glyphs. If cues drift progressively rather than remaining a fixed distance early or late, check the source timing and whether the video was retimed or re-edited after the subtitle file was created. The real interface frame below comes from [Easy Tech Steps' February 2026 SRT export walkthrough](https://www.youtube.com/watch?v=9gTjdMPs%5FYs&ref=davinciresolveclub.com); it shows Resolve Studio 20, and the placement behavior was checked against the Resolve 21 manual. ![DaVinci Resolve Studio 20 Edit timeline with imported SRT cues on subtitle track ST1 above the video and audio tracks](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/subtitles-srt-track-resolve20.webp) Real DaVinci Resolve Studio 20 interface from Easy Tech Steps' February 2026 walkthrough. The ST1 row shows imported cues as editable timeline clips; the placement behavior and current menu labels were checked against the Resolve 21 Reference Manual. ## Generate Captions from Audio in Studio Resolve Studio can turn timeline speech into a first-pass subtitle track. Build and clean the dialogue first, then use **Timeline > AI Tools > Create Subtitles from Audio**. Choose the language, caption preset, maximum characters per line, one or two lines, and the gap between cues. Generate the track, then correct it against the actual audio. The interface frame below comes from [MrAlexTech's automatic-subtitles walkthrough](https://www.youtube.com/watch?v=y9hkjtO-Mn8&ref=davinciresolveclub.com); it shows Resolve Studio 20, and every visible dialog control was checked against the current Resolve 21 manual. ![DaVinci Resolve Studio 20 Create Subtitles from Audio dialog with language, preset, line length, lines and gap controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/create-subtitles-from-audio-resolve20.webp) Real DaVinci Resolve Studio 20 interface from MrAlexTech's automatic-subtitles walkthrough. The dialog exposes Language, Caption Preset, maximum characters per line, one or two lines, gap and Create; those controls match the current Resolve 21 manual. This speech-to-text route is a **Studio** feature. The free edition can still create manual subtitles, import an SRT, style the track and deliver captions. If the automatic command is absent, confirm which edition is installed before troubleshooting menus or reinstalling. Automatic captions aren't a final transcript. Check names, numbers, homophones, acronyms and speaker changes. Blackmagic specifically warns that overlapping dialogue on multiple audio tracks can defeat the analysis; mute tracks you do not want analyzed before generating captions. If transcription itself is the main job, use the [full Resolve 21 transcription workflow](https://davinciresolveclub.com/transcribe-audio-davinci-resolve/) rather than duplicating that process here. ## Time and Style the Subtitle Track Select a cue and use the Caption controls for its words and cue-level settings. Select the track and use Inspector > Track when you want the same presentation across every cue. Enable Customize Caption only for a deliberate cue- or word-level exception. The editorial rule is simple: global consistency belongs at track level; a specific exception belongs on the cue. Start with these checks: - **Position:** keep captions inside a safe area and above player controls, lower thirds or burned-in platform UI. - **Contrast:** use a restrained outline, shadow or background so light footage doesn't erase white text. - **Line breaks:** preserve meaning and avoid a single short word stranded on the second line. - **Duration:** give the viewer time to read without leaving an old caption over the next thought. - **Case:** sentence case is usually faster to read than long blocks of all caps. Set measurable warnings before the QC pass. In Project Settings > Subtitles, Resolve can flag Characters Per Line, Minimum Caption Duration and Maximum Characters Per Second; the CPS value turns red when a cue exceeds the current threshold. For a language track that needs different limits, select the track, open Inspector > Track > Subtitle Settings, disable Use Project Settings, then set Max Line Length, Min Duration and Max CPS for that track. ![Caption quality check for subtitle timing, natural line breaks, contrast and safe screen position](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/subtitle-qc-reading-frame.webp) Judge captions in motion, not as isolated text boxes. Each cue needs enough reading time, a natural phrase break, readable contrast and a position that stays clear of player controls and other graphics. Resolve 21 adds finishing tools documented in Blackmagic's [New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com). The subtitle Inspector can find and replace a name across the track. Manually entered or imported captions can run Update Word Timings, and a track-header command can Synchronize Word Timings for the whole track. Subtitle clips also have fade handles. AI Animated Subtitles templates are a Studio feature; ordinary subtitle timing, styling and delivery don't require those animated templates. ## Run a Real Caption QC Pass Don't proof captions only while stopped on individual frames. Watch the program at normal speed with sound, then watch difficult sections muted. The first pass checks fidelity to speech; the muted pass exposes whether the text can stand on its own. 1. Correct spelling, names, numbers and technical terms. 2. Check that each cue begins with the phrase and clears before the next speaker or idea. 3. Remove accidental double spaces and inconsistent punctuation. 4. Identify meaningful non-speech audio when the delivery requires accessible captions. 5. Check captions over the brightest and busiest shots. 6. Confirm that every active language track has the intended label and content. 7. Export a short test and inspect the actual output outside Resolve. Find and Replace is excellent for a consistently misspelled surname, but review replacements in context before using Replace All. A short word can be part of a longer word, and capitalization may differ at the beginning of a cue. ## Export SRT, Embedded Captions or Burned-In Subtitles Move to the Deliver page and open Subtitle Settings. Enable Export Subtitle, choose the correct subtitle track, then match the mode to the destination. The real interface frame below comes from [Easy Tech Steps' February 2026 walkthrough](https://www.youtube.com/watch?v=9gTjdMPs%5FYs&ref=davinciresolveclub.com); it shows Resolve Studio 20, while the current Resolve 21 manual confirms the same separate-file, burn-in and embedded delivery labels. ![DaVinci Resolve Studio 20 Deliver page with Export Subtitle enabled, separate-file format, SRT and subtitle track selection](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/export-subtitles-srt-resolve20.webp) Real DaVinci Resolve Studio 20 Deliver interface from Easy Tech Steps' February 2026 walkthrough. Export Subtitle is enabled with As a separate file, SRT and a selected track; the same delivery labels are documented in the Resolve 21 manual. | Delivery | Best for | Main tradeoff | | -------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------------------- | | Separate file such as SRT or VTT | YouTube, review, localization and accessible playback | Styling is limited and the file must stay paired with the video. | | Embedded captions | A compatible broadcast or professional master specification | Support depends on the chosen container, codec and destination. | | Burn into video | Social feeds, review copies and guaranteed on-screen text | The viewer cannot turn captions off or switch languages. | For a separate file in Deliver, Resolve 21 lists IMSC1, DFXP, SRT and WebVTT. File > Export Subtitle and the subtitle-track header Export Subtitle command offer SRT and VTT. SRT is broadly accepted but plain; don't expect it to preserve the exact Resolve typeface or background box. For a permanent result, choose Burn into video and inspect the rendered file for clipping, line wrapping and timing. Embedded delivery is container-specific. Resolve 21 documents CEA-608 inside MXF OP1A and QuickTime, with Text or CEA-608 codec choices where supported. Confirm the receiver, container, caption standard, language metadata and frame rate before rendering a long master. The [general video export guide](https://davinciresolveclub.com/export-video-davinci-resolve/) covers codecs and render settings; this page stays focused on the subtitle payload. ## Fix Common Subtitle Problems ### The imported subtitles are missing Zoom out and compare the SRT's first timestamp with the timeline start timecode. The cues may have been inserted correctly at a time your current timeline doesn't reach. Also confirm the subtitle track is visible and enabled. ### Every cue is early or late by the same amount That's usually an offset, not drift. Move the imported group together or correct the zero point in the SRT workflow. Don't retime every cue separately. ### The error grows toward the end Progressive drift points to a duration or timing-base mismatch. Check whether the program was speed-changed, frame-rate converted or re-edited after the subtitle file was generated. ### The font and box disappear from the exported SRT That's expected. SRT stores cue timing and text, not Resolve's complete visual design. Burn the subtitle track into the picture when exact appearance is mandatory, or use a delivery format and player that support the required styling. ### Automatic subtitles are not available Built-in speech-to-text subtitle creation requires Resolve Studio. Manual cues, SRT import, track styling and subtitle delivery don't require the AI generation step. ## Frequently Asked Questions ### Can the free version of DaVinci Resolve add subtitles? Yes. The free edition can create a subtitle track, add cues manually, import SRT files, adjust timing and style, and export or burn subtitles. Create Subtitles from Audio is part of the Studio speech-to-text toolset. ### How do I import an SRT file into DaVinci Resolve? In the Media Pool, right-click a bin or its background and choose Import Subtitle, then place the imported subtitle clip on a subtitle track. Check the first cue, timeline start timecode and last cue before styling the track. ### Why are imported subtitles one hour out of sync? The SRT may start near zero while the timeline starts at 01:00:00:00, or the reverse. Align the timecode ranges for absolute placement, or place the SRT relative to the playhead when that matches the project. ### Does SRT preserve subtitle fonts and styling? No. Standard SRT primarily carries cue numbers, timestamps and text. Burn subtitles into the video when their exact font, position, outline or background must survive delivery. ### Should I use subtitles or Text+ for animated captions? Use the subtitle track for long, exportable captions and multiple languages. Use Text+ or Fusion titles when per-word animation and free graphic placement matter more than caption-file export. ### Can DaVinci Resolve translate subtitles automatically? Do not plan around a native translation step unless your exact Resolve build and documentation confirm one. A reliable localization workflow is to export a timed subtitle file, translate and review it externally, then import the translated file onto a separate language track. This guide belongs to the [DaVinci Resolve tutorial map](https://davinciresolveclub.com/davinci-resolve-tutorial/). For the next step, use the transcription guide when audio must become text, the Text+ guide for animated graphics, or the [export settings hub](https://davinciresolveclub.com/davinci-resolve-export-settings/) when the subtitle decision is part of a larger delivery workflow. ### DaVinci Resolve Multicam Editing: Sync to SmartSwitch URL: https://davinciresolveclub.com/davinci-resolve-multicam-editing/ Last updated: 2026-09-05T01:30:11.000Z A reliable multicam edit starts before the first camera switch. Put the angles into one properly synced multicam clip, decide which audio should remain continuous, and only then perform the switching pass. If you skip that setup, every later correction becomes a fight with sync, duplicate audio, or cuts that change the microphone along with the picture. This workflow is written for DaVinci Resolve 21\. On September 5, 2026, Blackmagic's [Edit page](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) and the current [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) still documented the standard multicam viewer, waveform, timecode, in/out-point and marker sync, plus separate video- and audio-switching controls. Multicam SmartSwitch requires Studio. The manual describes SmartSwitch as a first pass to finesse, not a substitute for checking speaker choice, rhythm and continuity. It also documents the four audio structures and full-clip-extents control used below. ## Use multicam when the cameras share the same event Multicam is the right structure when two or more cameras recorded the same interview, performance, ceremony, class, or podcast at the same time. Resolve keeps those sources aligned inside one clip and lets you choose which angle appears at each moment. You can trim a switch or replace an angle later without manually sliding the original camera files. Don't build a multicam clip just because a project contains footage from several cameras. B-roll captured at another time belongs in normal bins and timeline tracks. A multicam clip is for simultaneous coverage that shares a sync reference. | Footage | Best structure | Reason | | --------------------------------------- | -------------------------------------------- | ---------------------------------------------- | | Two-person interview with three cameras | Multicam clip | Every angle covers the same conversation | | Concert with shared timecode | Multicam clip | Long continuous angles can stay frame-aligned | | Talking head plus unrelated B-roll | Main camera on timeline, B-roll above | The B-roll has no continuous sync relationship | | Several takes of one scripted line | Source tape, take selector, or stacked clips | The takes happened at different times | ## Prepare the source clips before synchronization Create one bin for the shoot and use camera or scene metadata consistently. If a camera stopped and restarted, keep its spanned clips together and inspect their timecode before selecting everything. Renaming clips carelessly can make angle ordering harder to read later, so preserve the original filename in metadata if you add friendlier display names. Check three things before Resolve analyzes anything: 1. **Frame rate:** confirm the sources have the expected recorded frame rate. A genuine off-speed recording shouldn't be forced into sync as if it were normal-speed coverage. 2. **Audio reference:** every camera used for waveform sync needs a recognizable version of the same sound. A scratch mic is enough when it captured the room clearly. 3. **Timecode:** use timecode only when the cameras or recorder were actually synchronized. Similar-looking clock values aren't proof of jam sync. If decoding several angles at once makes the viewer stutter, solve playback before judging sync. The [Proxy Media workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) explains when to use proxies, optimized media, timeline proxy resolution, or render cache. Multicam is hard enough to review without dropped frames pretending to be bad cuts. ## Choose the sync method from the material you recorded Select the simultaneous source clips in the Media Pool, right-click, and choose **Create Multicam Clip Using Selected Clips**. The creation dialog is where you choose the synchronization method and angle ordering. The real Resolve 21 interface below comes from [Adens Archive’s May 2026 multicam walkthrough](https://www.youtube.com/watch?v=CyHzVgpT4GM&ref=davinciresolveclub.com); the menu labels were checked against Blackmagic’s latest manual. | Sync method | Use it when | Verify afterward | | ----------- | ----------------------------------------------------------- | --------------------------------------------------- | | Timecode | All cameras and the audio recorder shared reliable timecode | A slate close and a late-program sync point | | Sound | Each angle recorded the same usable reference audio | Hard consonants, claps, or visible impacts | | In points | You manually marked the same event on every source | The exact marked frame and a later point | | Out points | The shared reference is near the end of the clips | The marked frame and the beginning of usable action | Timecode is the cleanest choice only when the cameras were genuinely jam-synced. Sound is practical when every angle recorded the same clear event. In or Out points work when you marked one matching frame in every source, while Marker sync uses a matching manual marker on each clip. If scratch audio is weak, place the same In, Out or Marker sync point on a visible slate close, hand clap or camera flash. Never accept a multicam clip just because Resolve created it without an error. ![DaVinci Resolve 21 New Multicam Clip dialog with Angle Sync, Multicam Audio and angle naming controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/multicam-create-dialog-resolve21.webp) Real DaVinci Resolve Studio 21 interface from Adens Archive’s May 2026 walkthrough. The New Multicam Clip dialog is where Angle Sync, audio structure and angle naming are chosen before Create. ## Create the clip without losing the audio you need Name the multicam clip for the scene or recording rather than leaving a generic generated name. Set video angle ordering so Camera A, Camera B, the wide shot, and any presentation feed appear in a predictable order. The order matters because viewer tiles and keyboard angle commands become much easier to remember. The audio choice deserves more attention than most tutorials give it: - **Reference Audio/Angle 1** is useful when one recorder or camera angle should provide the continuous master sound. - **All Angles**, added as a creation option in Resolve 21, carries all audio tracks from the selected angle sources into the multicam clip. Use it when you genuinely need access to several isolated microphones, not merely because it keeps more data. - A dedicated mix placed on its own timeline track is often simpler for interviews. Lock that audio and switch video only. Resolve 21 documents four Multicam Audio choices: Source Audio Channels, Reference Audio, Adaptive Tracks and All Angles. The [Resolve 21 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) spells out that All Angles includes every audio track from every angle and that Use full clip extents preserves the selected sources’ full lengths. A three-camera podcast with two channels per camera can therefore become an unnecessarily crowded structure. Keep every track only when you have a routing and mixing plan for it. ## Verify sync before you edit the program Open the multicam clip in its own timeline or place it in a short test timeline. Find a sharp sound with visible movement: a clap, a hand hitting a table, a slate closing, or a word with a clear mouth movement. Check the first useful minute and another point near the end. If the beginning is aligned but the end drifts, investigate source frame rate, variable-frame-rate recordings, audio clock differences, or an incorrect interpretation setting. A single nudge can fix a constant offset; it can't repair progressive drift. Rebuild or correct the source rather than hiding a changing sync error under frequent camera cuts. When one angle is wrong, open the multicam clip and correct that source against the others. Do not slip random segments on the finished program timeline unless you intend to create a deliberate local offset. ## Cut camera angles while keeping the sound stable Place the multicam clip on a timeline and switch the source viewer to multicam mode so you can see the angle grid. During playback, click an angle or use the assigned multicam angle commands to create switches in real time. The [beginner editing workflow](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) and [keyboard-shortcuts guide](https://davinciresolveclub.com/davinci-resolve-keyboard-shortcuts-guide/) cover the viewer and angle commands. If you need ordinary blade edits before switching live, use the [split-video guide](https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/) first; it keeps that basic timeline intent out of this multicam workflow. For an interview or podcast, switch **video only** while the clean recorder mix continues underneath. Switching video and audio together can be right for a performance where each angle carries a purposeful source, but it's a poor default for speech. Camera cuts shouldn't make room tone, microphone character, or dialogue level jump. ![DaVinci Resolve 21 multicam viewer angle grid above a timeline with camera cuts and continuous audio tracks](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/multicam-viewer-angle-cuts-resolve21.webp) Real DaVinci Resolve Studio 21 multicam viewer from the same walkthrough. The angle grid is the switching surface while the timeline records cuts; use video-only switching when one program mix must stay continuous. Your first pass should favor content over polish. Follow the speaker, use the wide shot to reset geography or cover overlaps, and leave enough shot duration for the viewer to read an expression. Then replay the sequence and trim switches away from blinks, camera bumps, mid-gesture mismatches, and words that need reaction shots. ## Replace a bad angle without rebuilding the edit A multicam switch is editable. Select a segment and choose a different multicam angle to replace the picture while preserving the segment's timing. Trim the edit point when the correct camera is already selected but the cut lands early or late. This is safer than flattening the entire sequence just to change one choice. Use match frame when you need to identify the underlying source. The [Resolve 21 feature guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) says Match Frame to Source Clip now finds the underlying source for multicam and nested clips automatically. Keep a duplicate timeline before structural changes so you can compare the revised cut with the previous pass. ## Use SmartSwitch as a Studio first pass SmartSwitch is available in Studio, not the free edition. Blackmagic’s [official SmartSwitch guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) says it analyzes the active speaker, audio, lip movement and whether an angle is wide or close. The result is a starting timeline, not a finished edit. The real settings and result below come from [Jason Yadlovski’s Resolve 20 walkthrough](https://www.youtube.com/watch?v=Wko-K0bIWZ8&ref=davinciresolveclub.com); those controls remain part of the Resolve 21 workflow documented in the current manual. 1. Create and verify the multicam clip. 2. Edit that multicam clip into a timeline. 3. Right-click the timeline clip and choose Multicam SmartSwitch. 4. Set Minimum Edit Duration, Edit Change Delay and wide-angle behavior. Choose Video Only or Video and Audio, choose Quality: Faster or Better, and enable Use Audio Only Fast Analysis only when an audio-only decision pass fits the material. 5. Run Analyze, then duplicate or version the resulting timeline before manual review. | Control | What it changes | Practical starting judgment | | ---------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------ | | Minimum Edit Duration | Prevents another switch before the duration expires | Raise it when the result feels nervous or overcut | | Edit Change Delay | Offsets the cut after speech begins | Use a small delay when immediate switches feel mechanical | | Wide Angle Frequency | Controls how often the wide shot returns | Use the wide as punctuation, not a timer | | Video Only | Keeps timeline audio from changing with every camera cut | Preferred for a continuous interview mix | | Quality: Faster or Better | Trades analysis speed for accuracy | Test a short representative section before a long session | | Use Audio Only Fast Analysis | Uses audio without video analysis and runs faster | Use only when lip movement and shot type are not needed for the decision | ![DaVinci Resolve Multicam SmartSwitch settings for edit duration, delay, wide angles, quality and audio-only analysis](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/multicam-smartswitch-settings-resolve20.webp) Real DaVinci Resolve Studio 20 SmartSwitch interface from Jason Yadlovski’s September 2025 walkthrough. The control groups set cut timing, wide-shot behavior, video or audio switching, Quality and optional audio-only fast analysis. ## Review SmartSwitch in three passes First, check speaker accuracy. SmartSwitch can misunderstand an off-camera voice, overlapping speech, laughter, a silent reaction, or an angle without useful audio. Replace incorrect speaker shots before worrying about rhythm. Second, check pacing. An automatic cut can be logically correct and still feel impatient. Extend reactions, remove repetitive ping-pong switching, and let the wide shot establish the space. A podcast edit needs editorial listening alongside active-speaker detection. Third, check continuity and technical quality. Watch for blinks, focus searches, camera bumps, exposure changes, or an angle that was never meant to be used during a reset. SmartSwitch analyzes the available choices; it does not know the director's intention. Blackmagic notes that SmartSwitch analysis time depends on the program length and number of camera angles. On a long event, test a representative excerpt on a duplicate timeline first. That reveals whether speaker choices, wide-shot frequency and edit duration suit the material before you analyze the full program. ![DaVinci Resolve timeline after Multicam SmartSwitch with editable camera-angle cuts over program audio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/multicam-smartswitch-result-resolve20.webp) Real SmartSwitch result on a DaVinci Resolve Studio 20 timeline from the same walkthrough. The first-pass cuts remain editable multicam segments, so review speaker accuracy, pacing and continuity before delivery. ## Finish color, audio, and export without breaking the structure You don't need to flatten immediately. Keep the multicam structure while angle changes are still likely. For color, open the multicam clip to correct an underlying angle consistently, or grade timeline segments when the shot needs local work. Duplicate the timeline before flattening because flattening removes the convenient multicam relationship from those timeline segments. Move dialogue cleanup and mix decisions into a deliberate audio pass. The [Fairlight task map](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) routes noise, EQ, compression, routing, and loudness work without forcing all of it into the multicam stage. When the sequence is approved, choose the delivery target through the [export settings hub](https://davinciresolveclub.com/davinci-resolve-export-settings/) and watch the rendered file outside Resolve. ## Fix the failures that waste the most time ### The angles are offset by a constant amount Open the multicam clip, line up a strong visual and audio event, and move the incorrect source by the fixed offset. Verify another point later. If the offset stays constant, the correction is valid. ### The angles drift farther apart Check frame-rate interpretation, variable-frame-rate media, and recorder clock behavior. Re-encoding troublesome phone or screen recordings to a stable edit codec may be necessary. A fixed nudge can't solve progressive drift. ### Every camera cut changes the sound Switch video only and keep the chosen recorder mix on a continuous track. If you need isolated microphones, use Resolve 21's All Angles audio option deliberately and route the channels in Fairlight instead of allowing camera choices to control the mix. ### The multicam viewer stutters Reduce the decoding and processing load before judging the edit. Use the proxy decision workflow, lower timeline proxy resolution, or cache effects that are expensive after decoding. Don't confuse dropped playback frames with sync drift. ### SmartSwitch ignores or overuses the wide shot Choose the wide angle manually in the SmartSwitch setup, adjust its frequency, and decide whether it should cover silence, intro, or outro. Then review every occurrence. Automatic detection is a convenience, not an instruction to accept every wide-shot choice. ## Frequently Asked Questions ### Is multicam editing available in DaVinci Resolve Free? Yes. You can create multicam clips, synchronize angles, use the multicam viewer, and switch angles in the free edition. Multicam SmartSwitch is different: Blackmagic lists it as a Studio-only feature. ### Should I synchronize multicam clips by sound or timecode? Use timecode when the cameras and recorder were genuinely synchronized during production. Use sound when every angle captured a clean version of the same event. Whichever method you choose, verify sync near the beginning and end of the usable recording. ### How do I keep one microphone while switching cameras? Place the clean recorder or reference mix on a continuous timeline track and switch video only. Resolve 20 added the Reference Audio/Angle 1 choice, while Resolve 21 added All Angles when a more complex mix genuinely needs every source track. ### Does SmartSwitch finish a multicam edit automatically? No. It creates a first-pass cut based on speaker and shot analysis. You still need to correct speaker choices, improve rhythm, protect reaction shots, remove unusable camera moments, mix audio, grade the program, and review the export. ### Should I flatten the multicam clip before color grading? Not automatically. Keep the multicam structure while angle changes remain likely. Correct underlying angles inside the multicam clip or grade timeline segments as needed. Duplicate the timeline before flattening so the editable multicam version remains available. This workflow belongs to the [DaVinci Resolve tutorial map](https://davinciresolveclub.com/davinci-resolve-tutorial/). Return there when multicam is only one stage in a larger path through editing, color, audio and delivery. ### Fusion vs After Effects in 2026 URL: https://davinciresolveclub.com/fusion-vs-after-effects/ Last updated: 2026-09-05T01:16:47.000Z DaVinci Resolve Fusion and After Effects can both composite a tracked screen, key a green background and animate a title. That overlap makes the usual “nodes versus layers” summary look complete when it is only the start. The real decision is where the shot comes from, how often it will change, who must edit it next and where the finished result has to live. **Quick verdict:** start with Fusion when visual effects belong to clips already being edited, graded and delivered in DaVinci Resolve, especially for tracking, keying, cleanup and multi-step shot composites. Start with After Effects when the work is driven by typography, shape animation, expressions, Adobe assets or reusable Motion Graphics templates for Premiere. Keep both when a project genuinely contains both kinds of work. ## Choose by the job, not the interface | Recurring job | Better first test | Reason | | --------------------------------------------------------- | ----------------- | ------------------------------------------------------------------------- | | Tracked screen replacement inside a Resolve edit | Fusion | The clip, composite, grade and delivery remain in one project | | Animated brand package with many text variations | After Effects | Layer animation, expressions and the motion-design ecosystem fit the task | | Green-screen composite with several masks and corrections | Fusion | A node tree makes image routing and mask reuse explicit | | Editable lower thirds for a Premiere team | After Effects | MOGRT can expose approved controls directly in Premiere | | Cleanup, roto and integration before a Resolve grade | Fusion | The result can pass directly into the Color page | | Character, type and shape-led motion design | After Effects | Its layer, precomp, expression and template workflows are mature | These are starting points, not software laws. An experienced Fusion artist can build excellent broadcast graphics, and an experienced After Effects compositor can finish difficult live-action shots. The better application is the one whose project structure remains readable after the third revision, not the one that wins a feature checklist. ## What you are actually paying for The [Fusion page is included in DaVinci Resolve 21](https://www.blackmagicdesign.com/products/davinciresolve/fusion?ref=davinciresolveclub.com), including the free desktop application. Blackmagic currently lists [Resolve Studio 21 at $295](https://www.blackmagicdesign.com/products/davinciresolve?product=sales&ref=davinciresolveclub.com) as a one-time purchase. Studio adds specific tools and capabilities, but a beginner can learn the core node, merge, mask, keyframe, tracking and title workflow without buying it. Our [Free vs Studio guide](https://davinciresolveclub.com/davinci-resolve-vs-studio/) helps identify the exact feature that justifies an upgrade. Adobe sells After Effects by subscription. On September 5, 2026, the [US After Effects plan page](https://www.adobe.com/products/aftereffects/plans.html?ref=davinciresolveclub.com) listed the individual single-app plan at $22.99 per month on an annual commitment billed monthly. Adobe says After Effects is not sold as a perpetual license and offers a seven-day full trial. The single-app plan lists the desktop application, Adobe Express Premium, Frame.io, 100GB of cloud storage and 25 monthly generative credits. Prices vary by country, tax, billing term and promotion, so confirm the final renewal amount in your own regional checkout. Don't compare $295 with one month of Adobe and stop there. Record the cost over the period you expect to use the application, then include the software around it. After Effects may be easier to justify when a team already pays for Premiere, Photoshop, Illustrator, fonts and Creative Cloud libraries. Fusion may be easier to justify when the edit, grade, mix and delivery already happen in Resolve. ## Nodes and layers store different kinds of logic Fusion represents processing as a flow. A MediaIn node feeds a keyer, a mask limits a correction, a tracker supplies motion and a Merge combines foreground with background. Branches can reuse one source or matte. When a composite fails, you can inspect the image at different points in the tree and see which operation introduced the problem. The [Fusion nodes guide](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) covers that signal flow before you build a large comp. ![DaVinci Resolve Fusion node graph connecting MediaIn, Merge and Blur tools to MediaOut](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fusion-node-graph-real-interface.webp) Blackmagic's real Fusion interface exposes the processing route in the node graph: follow the source through branches and merges before opening individual tool controls. After Effects organizes a composition around a layer-based timeline. Transform properties, effects, masks, mattes, parenting, precomps and expressions build the result over time. This is direct for motion design because the question is often “when does this element enter, move and leave?” The cost is that a large project can hide relationships across collapsed properties and nested compositions unless naming and organization are disciplined. ![Adobe After Effects layer timeline and Graph Editor with animated position curves and keyframes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/after-effects-graph-editor-real-interface.webp) Adobe's real After Effects interface keeps layer properties beside the Graph Editor, so timing, value curves and nested layer relationships become the first debugging surface. Neither structure is automatically easier. Layers feel familiar to people coming from Photoshop or Illustrator. Nodes often become clearer when one source must feed several operations or one matte must control several branches. Give each method the same task before declaring that your brain “works” only one way. ## Run the same ten-second shot through both A useful comparison needs the same source and the same revision. Choose a ten-second moving shot with a screen, a foreground obstruction and enough camera motion to expose a weak track. Add a replacement graphic, match its perspective, place it behind the obstruction, soften the composite and animate a short title. Keep the source resolution, frame rate and final codec identical. | Checkpoint | Record | Failure to watch for | | ---------- | ----------------------------------------------- | ------------------------------------------------ | | Setup | Time until the first editable composite | Wrong color, frame rate or source interpretation | | Track | Manual repairs after the automatic pass | Drift, perspective slip or occlusion failure | | Composite | Steps needed to reuse masks and corrections | Hidden dependencies or duplicated work | | Animation | Time to change timing and easing | Keyframes scattered across an unclear structure | | Revision | Time to replace the graphic and extend the shot | A fast first pass that is expensive to alter | | Handoff | Missing fonts, effects, media and instructions | A project that opens but cannot be reproduced | Don't use this as a universal performance benchmark. Cache state, codec, effects, GPU, CPU, memory, plug-ins and project structure can reverse a render result. The useful measurement is whether your own workstation completes the full edit, revision and handoff loop without fragile workarounds. ## Fusion fits shot-based compositing inside Resolve Fusion becomes compelling when the effect is attached to editorial context. Open a clip from the Resolve timeline, build the comp, return to Edit, grade it in Color and deliver from the same project. Blackmagic's own workflow includes 2D and 3D tools, planar and point tracking, keying, paint, masks, particles, titles, spline animation and reusable macros. The [Fusion task hub](https://davinciresolveclub.com/davinci-resolve-fusion/) routes each of those jobs without turning the hub into another manual. The node graph is especially useful for composites with several dependencies. A tracked matte can limit multiple corrections. A foreground branch can be treated separately before the final Merge. A clean plate can feed paint and restoration operations without duplicating the source. That structure does not make a difficult key or roto automatic, but it makes the reasoning visible. Resolve 21 also improves the path from a comp to a reusable edit asset. Blackmagic's own [Resolve 21 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) documents the updated Macro Editor and the option to save a macro as an Edit template. That matters for lower thirds and repeatable effects, but it isn't the same delivery ecosystem as an After Effects MOGRT. Test how much control an editor needs and whether the template will be used in Resolve or Premiere. ![DaVinci Resolve Fusion Macro Editor selecting editor-facing controls, defaults and value ranges](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fusion-macro-editor-real-interface.webp) Blackmagic's real Macro Editor makes template design a control-selection job: expose only what the editor should change, then verify names, defaults and safe minimum and maximum values. ## After Effects fits motion design and Premiere delivery After Effects is built around motion graphics as a first-class job. Adobe's current feature set covers text and shape animation, presets, tracking, keying, Content-Aware Fill, an integrated 3D workspace and AI Object Matte. Expressions can connect properties and produce controlled variations. Photoshop and Illustrator assets fit naturally into a design pipeline that already uses Adobe applications. The strongest workflow advantage appears when another editor works in Premiere. Adobe's [Motion Graphics template workflow](https://helpx.adobe.com/after-effects/using/creating-motion-graphics-templates.html?ref=davinciresolveclub.com) lets a designer package a composition and expose only approved controls such as text, color and replaceable media. The Premiere editor can make safe changes without opening the whole After Effects project. Some template features and third-party effects still require After Effects to be installed, so validate that dependency before delivery. After Effects is also a capable compositor. Tracking, mattes, keying, roto, paint and effects can solve real shots. The reason to prefer Fusion for some composites isn't that layers can't do the work. It is that a node tree can expose complex image routing more clearly, especially when several mattes and branches interact. ## Tracking, keying and roto need footage tests Feature names are poor evidence for difficult footage. A tracker that holds on a sharp daylight sign may fail on motion blur, reflections or an object that leaves the frame. A one-click matte may look convincing in a small viewer but chatter around hair at delivery resolution. A key can remove green while leaving spill, noisy edges and mismatched light. ![DaVinci Resolve Fusion tracker path and node graph over a moving motocross composite](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fusion-tracker-real-interface.webp) Fusion's authentic tracking view keeps the tracked result, path and relevant node branch in one workspace; inspect the path where occlusion or motion blur causes a repair. Use three short problem shots from your actual work: one with occlusion, one with hair or fine detail, and one with camera noise or compression. Count manual corrections and inspect the final export frame by frame. For Fusion, the [tracking workflow](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/), [rotoscoping guide](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/) and [green-screen keying guide](https://davinciresolveclub.com/davinci-resolve-delta-keyer/) provide the task-specific checks. ![Adobe After Effects Mask Path tracking controls expanded in the composition layer timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/after-effects-mask-tracker-real-interface.webp) After Effects exposes Mask Path tracking from the expanded mask property. The buttons start the operation; the real quality check is the full-resolution edge across difficult frames. Some automated tools differ between free and paid tiers, and their names change across releases. Verify the exact tool in the installed build instead of buying software because a comparison page promises “AI rotoscoping.” Manual mask quality, edge refinement and a reproducible project structure still matter after the automated first pass. ## Handoff is where the workflows separate Fusion stays closest to Resolve editorial. That removes an application boundary, but a collaborator still needs the correct Resolve version, fonts, plugins, media and project assets. Use a duplicate project or archive, open it on the receiving workstation and verify one change plus one render. A successful upload isn't a successful handoff. After Effects has a tighter live relationship with Premiere through [Adobe Dynamic Link](https://helpx.adobe.com/after-effects/using/dynamic-link-effects.html?ref=davinciresolveclub.com). Adobe says Premiere and After Effects must be on matching versions and warns that Dynamic Link will not work when the app versions differ. It also notes that complex linked compositions can delay playback and recommends Render and Replace when needed. Dynamic Link is useful, but it doesn't remove version management, caching or the need for a stable render fallback. Moving an editable composition between Fusion and After Effects is not a normal one-click interchange. Preserve source media, reference renders, alpha channels, mattes, camera data where supported, font records and a written description of the intended result. For client delivery, a high-quality rendered intermediate is often safer than assuming every proprietary effect and expression will translate. ## Performance depends on the comp you build Performance depends on the comp and hardware, not a one-line GPU-versus-CPU rule. Adobe's [After Effects 26.3 system requirements](https://helpx.adobe.com/after-effects/desktop/get-started/technical-requirements/system-requirements.html?ref=davinciresolveclub.com), checked on September 5, 2026, recommend that Windows users have 32GB or more RAM for 4K and higher, 8GB of GPU memory and a fast internal SSD for the application and cache. On macOS, Adobe recommends Apple silicon M1 Pro, M1 Max, M1 Ultra or newer and 16GB of unified memory. Minimum specifications do not promise smooth playback. Test with the codec, resolution and effects you actually use. Clear and warm the cache deliberately, record preview behavior and render to the same delivery format. Then change one thing at a time. If a comp is slow, inspect project structure before assuming a hardware purchase will fix it: oversized sources, unbounded effects, repeated calculations, deep precomps, high sample counts and unnecessary motion blur can dominate the result. The decision should survive a revision under deadline. A workflow that renders five percent faster but takes twice as long to diagnose isn't faster in production. ## A practical learning path If you already edit in Resolve, spend the first week inside Fusion before adding another subscription. Learn MediaIn and MediaOut, Merge, Transform, masks, Tracker, Text+, keyframes and the Spline editor. Build one screen replacement and one lower third. The [Fusion beginner tutorial](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) gives those tools a project instead of presenting a list of buttons. If your work is primarily animated design, or the team expects AEP and MOGRT delivery, start in After Effects. Learn composition settings, layers, parenting, masks, shape layers, graph editing, precomps, expressions and project collection. Build a title package with three exposed variations and hand it to a Premiere editor before calling the template finished. A mixed pipeline can be the correct answer. Finish tracked cleanup and shot composites in Fusion, render a documented intermediate, then create the title package in After Effects. Or keep an After Effects brand system while the main program is edited, graded and mixed in Resolve. A studio centered on Nuke compositing or Cinema 4D scenes should test that existing interchange too; this two-application comparison is only one boundary in a larger pipeline. Add a boundary only where the next application earns it. For editor-level choices around [Premiere](https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/), Final Cut Pro, CapCut and Resolve editions, use the [DaVinci Resolve comparisons hub](https://davinciresolveclub.com/davinci-resolve-comparisons/). It keeps this page focused on the Fusion-versus-After-Effects production boundary instead of turning it into a generic scorecard. ## Frequently asked questions ### Is Fusion better than After Effects? Fusion is often the stronger first test for node-based shot compositing inside a Resolve project. After Effects is often the stronger first test for typography, shape animation, expressions and Premiere Motion Graphics templates. Neither is universally better because the production job and handoff differ. ### Can Fusion replace After Effects? Fusion can replace After Effects for many tracking, keying, cleanup, compositing, title and motion-graphics tasks. It isn't a drop-in replacement for an established After Effects pipeline built around AEP files, MOGRT, expressions, Adobe assets or third-party templates. Test one representative project before migrating. ### Is Fusion free with DaVinci Resolve? Yes. The Fusion page is included in the free edition of DaVinci Resolve 21\. Resolve Studio is a separate paid edition with additional tools and capabilities. Learn the core Fusion workflow in the free edition, then upgrade only when a named Studio feature blocks real work. ### Which is easier to learn, Fusion or After Effects? After Effects layers may feel more familiar to designers coming from Photoshop or Illustrator. Fusion nodes may become clearer for editors who need to see how several image-processing branches connect. The fastest way to decide is to build the same small composite in both, including one revision. ### Can After Effects work with DaVinci Resolve? Yes, but Resolve doesn't use Adobe Dynamic Link. A reliable workflow renders a high-quality intermediate from one application and imports it into the other, with alpha where needed. Preserve source media, color assumptions, frame rate and a reference render, then test the return path before the deadline. ### Which is better for motion graphics? After Effects is usually the better first choice for typography, shape animation, expressions, character-style work and reusable Premiere templates. Fusion can handle strong motion graphics and is convenient when the result belongs in a Resolve edit. The destination and revision model should decide. Choose Fusion when the shot needs to remain part of Resolve's post-production chain. Choose After Effects when motion design and Premiere delivery define the project. If both conditions are real, use a documented render boundary instead of forcing one application to imitate the other. ### DaVinci Resolve vs CapCut in 2026 URL: https://davinciresolveclub.com/davinci-resolve-vs-capcut/ Last updated: 2026-09-10T09:48:33.000Z DaVinci Resolve and CapCut are both free to start, but “free video editor” is almost the only clean overlap. CapCut is built around fast creation across phone, web and desktop, with captions, templates and social delivery close to the edit. Resolve is a desktop post-production suite that expects you to make more decisions but gives you much deeper control over the timeline, color, effects, audio and final file. **Quick verdict:** use CapCut when the job is same-day Shorts, Reels, TikTok videos or another caption-heavy social format and speed matters more than a controlled finishing pipeline. Use Resolve when the project is longer, the source media needs careful organization, or color, sound, VFX, collaboration and delivery specifications matter. Don't pay for CapCut Pro or Resolve Studio until one named limit stops a real project. For the CapCut side of that call, see [Is CapCut Pro worth it](https://capcutguide.com/capcut-pro-worth-it/?ref=davinciresolveclub.com) on CapCut Guide. ![CapCut web editor beside the DaVinci Resolve 21 Edit page with labeled media, captions, tracks and page workflow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/capcut-resolve-editing-surface.webp) The real editing surfaces make the trade-off concrete: CapCut keeps creator tools near the timeline; Resolve exposes bins, tracks and dedicated finishing pages. ## The choice starts with publishing rhythm | Your recurring job | Better first test | Why | | --------------------------------------------------- | ----------------- | -------------------------------------------------------------------------- | | Daily vertical clips from a phone | CapCut | Mobile capture, templates, captions and social formats stay close together | | Weekly long-form YouTube episodes | Resolve | Stronger media organization, audio, color and repeatable delivery | | Trend-led edits with animated text | CapCut | Fast preset and template route with less manual construction | | Client work with mixed cameras and defined masters | Resolve | Deeper codec, color-management, audio and export control | | Editing on a phone, browser and laptop | CapCut | Cross-device creation is part of the product's core workflow | | One project moving through edit, grade, VFX and mix | Resolve | Color, Fusion and Fairlight live inside the same project | That table deliberately avoids a universal winner. A fifteen-second product clip can take longer in Resolve because you're building what CapCut already packages. A twenty-minute interview can become harder in CapCut because the quick tools don't replace a deliberate media, color and audio workflow. Pick the application that matches what you publish every week. ## Free does not mean the same thing Prices and plan terms below were checked on September 5, 2026\. Blackmagic publishes a stable desktop split: [DaVinci Resolve 21 is free and Resolve Studio 21 is listed at $295](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com). Free includes the core Edit, Cut, Color, Fusion, Fairlight and Deliver pages. Studio adds specific AI, effects, codec, performance and high-end delivery capabilities. The [Free vs Studio decision guide](https://davinciresolveclub.com/davinci-resolve-vs-studio/) identifies the actual blockers instead of treating paid as automatically better. CapCut's cost needs a different answer. CapCut's own help center says [Pro pricing varies by region, device and available promotion](https://www.capcut.com/help/how-much-does-capcut-pro-cost?ref=davinciresolveclub.com), and instructs users to check the current price inside the web, desktop or mobile account. That makes a fixed global price copied into an article unreliable, even if it was correct for one account on one day. CapCut Standard and Pro also differ by platform; a feature count alone misses that boundary. [CapCut says Standard benefits are primarily designed for mobile](https://www.capcut.com/help/valid-devices-for-standard-subscription?ref=davinciresolveclub.com), while premium access on PC requires Pro. Its multi-device guidance also says Standard premium benefits don't extend to desktop or web. If you edit on more than a phone, confirm the entitlement on every device before paying. CapCut also separates plan access from usage credits. Standard and Pro are subscriptions, while some advanced AI actions consume AI credits. The formal [CapCut Credits Rules](https://www.capcut.com/clause/credits-rule?ref=davinciresolveclub.com) say credits cannot buy Pro or Space plans, move to another account or be exchanged for cash. A Pro subscription can include credits, but that doesn't make every AI action unlimited. Before upgrading, capture four things from your own checkout and export panel: 1. the renewal price after any introductory promotion; 2. whether the plan works on every device you use; 3. which export resolution and premium assets are unlocked; 4. how many credits the specific AI action consumes. Don't rely on a universal CapCut cloud storage number. CapCut's own current help pages conflict: its [Standard-vs-Pro comparison](https://www.capcut.com/help/capcut-standard-vs-pro?ref=davinciresolveclub.com) says around 100GB for Standard and up to 1TB for Pro, while its [separate Pro storage guidance](https://www.capcut.com/help/capcut-pro-cloud-storage-full?ref=davinciresolveclub.com) says 100GB. CapCut also says [new free Web spaces may have 0GB, displayed as a 1KB placeholder](https://www.capcut.com/help/web-cloud-storage-explain?ref=davinciresolveclub.com). Treat the signed-in Space and checkout screens for your platform, region and account as authoritative, then keep source media outside the service as a separate backup. On Resolve, use the [Resolve pricing guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) to separate the permanent desktop license from organization-managed options. ## Run one vertical video through both A fair test isn't a cinema trailer in Resolve versus a template in CapCut. Build the same 45-second vertical video in both applications using the same phone clips, voice recording and delivery target. The test should include one bad take, one reframed landscape shot, captions, music ducking, a brand color, a speed change and a final 1080 × 1920 export. If 4K delivery matters, repeat the export on the actual device, account and plan you intend to use. ![CapCut and DaVinci Resolve interfaces used for the same 45-second vertical video workflow test](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/capcut-resolve-vertical-job-test.webp) Run the same vertical job in both editors and time the complete loop: setup, rough cut, caption correction, reframing, audio, revision and export. | Checkpoint | What to record | Decision impact | | ---------- | ------------------------------------------------------------- | ----------------------------------------------------------- | | Start | Time to import and set a vertical canvas | Measures project friction before creative work | | Rough cut | Time to remove the bad take and reshape pacing | Tests the timeline, not the effect library | | Captions | Correction time after transcription | Generation speed is irrelevant if cleanup is slow | | Reframe | Time to keep the subject inside the vertical frame | Tests one of the most common social tasks | | Audio | Time to make speech clear without pumping music | Exposes the difference between a preset and a mix | | Revision | Time to change the opening, caption style and logo color | Client notes reveal whether the structure stays editable | | Export | Settings used and whether the uploaded file passes inspection | A fast render is not useful if the platform result is wrong | The winner is the application that completes the whole loop with fewer manual repairs. Save the project, reopen it the next day and make one change. That final step catches cloud-sync, missing-asset and organization problems that a speed run misses. ## CapCut is faster when the template is the workflow CapCut's advantage is product design, not a lack of seriousness. It puts animated text, automatic captions, social effects, reframing, background tools, stock assets and platform-shaped outputs close to the timeline. When the desired result resembles a current social format, starting from that format can be faster than constructing every element. That's especially useful for a solo creator who records, edits and publishes on the same device. CapCut spans mobile, web and desktop, while desktop Resolve is designed around a workstation and a more deliberate project library. But cross-device availability is not the same as cross-device paid entitlement: [CapCut Pro covers mobile, desktop and web](https://www.capcut.com/help/use-capcut-subscription-membership-on-multiple-devices?ref=davinciresolveclub.com), while Standard premium benefits are mobile-only in CapCut's current guidance. A creator working between a phone and an ordinary laptop may still finish more consistently in CapCut, but should test the exact plan on both devices. The trade-off arrives during revision. A template can hide which layer, animation, font or asset created the result. Before committing to it for a client series, change the brand color, replace the opening shot, extend a caption and create a second aspect ratio. If those routine changes fight the template, the initial speed was borrowed from the revision stage. ## Resolve is stronger when the project must survive finishing Resolve asks for more setup because it is solving a wider problem. The Edit and Cut pages handle the timeline; the Color page handles grading and color management; Fusion handles compositing and motion graphics; Fairlight handles repair, routing and mixing; Deliver handles controlled output. The [Resolve learning hub](https://davinciresolveclub.com/davinci-resolve-tutorial/) routes beginners by task so they do not attempt to learn every page before making a cut. For long-form YouTube, courses, interviews, events and paid client work, that media management structure becomes useful when footage multiplies. Bins, smart bins, metadata, multiple timelines, proxies, scopes, buses and render queues give each problem a defined place. Resolve doesn't automatically make the story better. It makes a complicated project easier to inspect. Vertical delivery isn't a reason to avoid Resolve. Set the vertical timeline before reframing and validate the safe areas and captions on a phone. Our [vertical aspect-ratio workflow](https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/) covers the canvas and reframing steps, while the [export hub](https://davinciresolveclub.com/davinci-resolve-export-settings/) handles the final file. The difference is that Resolve expects you to choose those settings rather than infer them from a social template. ## Captions, AI and credits need separate decisions CapCut's AI pitch is immediacy. Auto captions, avatars, background tools, tracking and generative features are presented close to the creator workflow. Resolve's AI tools sit across media search, editing, color, restoration, masking and speech generation. Many Resolve Neural Engine features require Studio; some CapCut actions require Pro, credits or both. ![CapCut export dialog beside the DaVinci Resolve 21 Color page with nodes, grading controls and scopes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/capcut-resolve-finishing-export.webp) After the rough cut, verify CapCut's actual export dialog and compare it with Resolve's dedicated finishing surface; this is a workflow-depth comparison, not a claim that CapCut lacks adjustments. Don't compare the number of AI buttons. Compare the unit of work: - For captions, measure correction and restyling time, not transcription time alone. - For background removal, inspect hair, motion blur and hand edges on the final frame size. - For auto reframing, test a subject who crosses the frame instead of a centered talking head. - For generative tools, record the credits consumed by rejected attempts as well as the accepted result. - For a client project, confirm whether the input, generated output and included asset are cleared for the intended commercial use. The [Resolve transcription guide](https://davinciresolveclub.com/transcribe-audio-davinci-resolve/) covers editable transcripts and subtitles; the [Resolve 21 AI breakdown](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/) separates confirmed tools and edition limits. On the CapCut side, check the live plan and credit screens rather than assuming that a Pro badge makes every AI action unlimited. ## Color, audio and VFX are not equal categories CapCut can make footage look and sound better quickly. Filters, adjustments, effects, denoise and loudness tools cover ordinary social work, and that can be exactly enough. Resolve becomes meaningfully different when you need repeatability: one color-managed path for mixed cameras, scopes that show the signal, tracked corrections, reusable node structures, dialogue repair, buses, automation and deliverable-specific audio. Use the [color grading workflow map](https://davinciresolveclub.com/davinci-resolve-color-grading/) if shots must match rather than merely share a filter. Use the [Fairlight hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) if dialogue, music and effects need separate control. Use the [Fusion hub](https://davinciresolveclub.com/davinci-resolve-fusion/) when a motion element must stay editable beyond a template's exposed controls. There's no prize for using the deeper tool on a simple clip. If a CapCut adjustment produces the approved result and the project remains editable, it solved the job. Resolve earns its extra complexity when you need to diagnose, reproduce or hand off the result. ## Client work adds rights, backup and handoff Trending music, premium templates and stock elements aren't automatically cleared for every brand, platform, country or paid campaign. The current [CapCut Materials License Agreement](https://www.capcut.com/clause/material-license-agreement?lang=en&ref=davinciresolveclub.com) distinguishes personal-only materials from items specifically marked for limited commercial use, and the permitted term and territory can vary by asset. A Pro badge alone isn't a rights record. Save the asset-specific license details with the job and replace anything the client can't document. Cloud convenience is also not a backup policy. [CapCut's current Terms of Service](https://www.capcut.com/clause/terms-of-service?lang=en&ref=davinciresolveclub.com) say the company does not guarantee permanent availability of user content and advises regular backups of anything you value. Resolve can use local project libraries, exported DRP projects, DRA archives and Blackmagic Cloud, but the editor still needs a separate copy of project data and source media. For either application, hand a collaborator a duplicate test project before the deadline. Confirm that fonts, music, templates, effects, captions and source media open under the collaborator's account and plan. A share link that opens isn't proof that every asset remains editable or licensed. ## How to move from CapCut to Resolve without rebuilding everything Do not switch editors in the middle of a healthy recurring series just because Resolve is more powerful. Start the next episode in Resolve and keep the last CapCut project available as a visual reference. Export brand assets, fonts, logos, music licenses, caption text and a clean high-quality master from CapCut. Rebuild only the reusable structure you need. 1. Create the Resolve timeline at the final aspect ratio and frame rate. 2. Import camera originals rather than a compressed social export whenever possible. 3. Rebuild one title style and one caption style, then save them before making variants. 4. Set up dialogue, music and effects tracks before the first full edit. 5. Use [Proxy Media](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) if the source codec overwhelms the workstation. 6. Export a short test, upload it privately and compare captions, color and audio on a phone. Keep CapCut for the jobs it finishes well. A mixed workflow is sensible: quick reactive clips in CapCut, longer or specification-heavy work in Resolve. The mistake isn't using two tools. It is moving a project between them without an interchange plan. For a wider shortlist, use the [DaVinci Resolve vs Premiere Pro comparison](https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/) to separate price, platform, handoff and finishing requirements before testing another application. Browse the [DaVinci Resolve comparisons hub](https://davinciresolveclub.com/davinci-resolve-comparisons/) when the choice includes another editor or the Free-versus-Studio edition split. ## Frequently asked questions ### Is CapCut better than DaVinci Resolve for beginners? CapCut usually gives a beginner a gentler learning curve because templates, captions and platform formats are close to the edit. Resolve takes longer to learn but gives the beginner a more transferable timeline, color, audio and delivery workflow. The better start depends on the work you plan to repeat. ### Is CapCut really free? CapCut has a free starting tier, but plan, export, premium asset and AI availability can vary by platform and account. CapCut says current Pro pricing must be checked inside your own account. Standard benefits are primarily mobile, while premium PC and web access requires Pro. Some AI actions use credits separately from the subscription. ### Does DaVinci Resolve add a watermark? Normal editing and export from Resolve Free don't add a general watermark. Applying a Studio-only effect in the free edition can place a watermark on that effect's output, so check the Inspector before delivery. ### Which is better for YouTube, CapCut or Resolve? CapCut is efficient for Shorts and fast caption-led videos. Resolve is usually the stronger base for long-form episodes, mixed cameras, detailed audio, consistent color and controlled exports. Many channels can reasonably use CapCut for reactive short-form work and Resolve for the main program. ### Can CapCut projects open in DaVinci Resolve? Don't assume a complete editable project transfer. Preserve camera originals, captions, fonts, brand assets and a high-quality reference export, then rebuild the reusable structure in Resolve. Test any available interchange route on a duplicate rather than risking the active project. ### Should I pay for CapCut Pro or Resolve Studio? Pay for CapCut Pro when a verified plan feature, asset or cross-device workflow repeatedly saves more than its renewal and credit cost. Buy Resolve Studio when a named codec, AI, effect, performance or delivery limit blocks paid work. Neither upgrade is required just because the free tier exists. CapCut isn't merely Resolve with fewer controls, and Resolve isn't CapCut for professionals. They optimize different production rhythms. Choose CapCut when publishing speed is the product. Choose Resolve when the project must remain controllable after the first export. ### DaVinci Resolve vs Final Cut Pro in 2026 URL: https://davinciresolveclub.com/davinci-resolve-vs-final-cut-pro/ Last updated: 2026-09-05T00:47:44.000Z DaVinci Resolve and Final Cut Pro can both finish professional work on a Mac, but they reward different editing habits. Final Cut Pro is the cleaner choice for a Mac-only editor who values the Magnetic Timeline, fast media organization and a focused editorial workspace. Resolve is the stronger fit when color, Fusion, Fairlight, cross-platform access or simultaneous collaboration are part of the same job. **Quick verdict:** choose Final Cut Pro when cutting speed on a Mac is the main requirement and its library-and-role workflow suits the way you organize work. Start with Resolve Free when budget matters or you want one application for editing, color, visual effects and audio. Buy neither on reputation alone. Put the same five-minute project through both before moving a real library. ## DaVinci Resolve vs Final Cut Pro at a glance | Decision point | DaVinci Resolve 21 | Final Cut Pro 12.3 | | --------------------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | | Desktop platforms | macOS, Windows and Linux | macOS only | | Entry price in the US | Free; Studio is $295 | $299.99 standalone, or included with Apple Creator Studio | | Timeline model | Traditional track-based Edit page plus the faster Cut page | Magnetic Timeline with a Primary Storyline, connected clips and roles | | Color | Dedicated node-based Color page | Color wheels, curves, masks, keying and automatic matching inside the editor | | Visual effects | Fusion is built into the application | Built-in effects and FxPlug ecosystem; Motion handles deeper template and motion-graphics work | | Audio | Fairlight page for editing, repair, mixing, buses and delivery | Role-based audio organization, multichannel editing and built-in effects | | Collaboration | Blackmagic Cloud and Project Server workflows are documented for simultaneous project work | Libraries, XML and third-party ecosystem workflows | | Best first fit | Cross-platform editors and deeper post-production | Solo or small-team Mac editors focused on fast editorial work | The table is a filter, not a scorecard. A wedding editor delivering weekly films on one Mac has a different bottleneck from a colorist receiving timelines from three operating systems. The right choice is the one that removes the expensive friction from your actual handoff. ## Price now has more than one answer Resolve still has the simplest entry point. Blackmagic lists [DaVinci Resolve 21 as free and Resolve Studio 21 at $295](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com). The free edition isn't a short trial. It includes the Edit, Cut, Color, Fusion, Fairlight and Deliver pages, with specific Studio features and higher-end limits reserved for the paid version. Our [Resolve Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) is the better place to decide whether any of those limits block your work. Final Cut Pro now has two legitimate Mac licensing routes. The [US Mac App Store lists the standalone application at $299.99](https://apps.apple.com/us/app/final-cut-pro/id424389933?mt=12&ref=davinciresolveclub.com). Apple also includes Final Cut Pro, Motion and Compressor in [Apple Creator Studio at $12.99 per month or $129 per year](https://www.apple.com/final-cut-pro/?ref=davinciresolveclub.com) in the US. Education pricing is lower, and prices vary by country and tax. Apple continues to sell the one-time app, although some premium content is reserved for Creator Studio subscribers. | US licensing path | Up-front cost | Cost after three years | What matters | | ---------------------------- | ---------------- | ---------------------- | ------------------------------------------------------------------------------- | | Resolve Free | $0 | $0 | Stay here until a named Studio limit blocks delivery | | Resolve Studio | $295 | $295 | One-time desktop license at the currently listed price | | Final Cut Pro standalone | $299.99 | $299.99 | Mac application only; Motion and Compressor are separate purchases if required | | Apple Creator Studio annual | $129 per year | $387 | Includes Final Cut Pro, Motion, Compressor and the wider suite while subscribed | | Apple Creator Studio monthly | $12.99 per month | $467.64 | Flexible, but the most expensive of these three-year examples | Those totals use US list prices checked on September 5, 2026, before tax. They aren't a promise that future upgrades will always be free. The practical question is whether you need only an editor or whether Motion, Compressor, Logic Pro and Pixelmator Pro replace other paid tools. If you need the bundle, comparing $295 with $299.99 misses most of the decision. For the Resolve side alone, the [current Resolve pricing guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) separates the permanent desktop license from organization-managed rental and hardware bundles. ## The timeline is the real dividing line ![Final Cut Pro primary storyline beside DaVinci Resolve video and audio tracks](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/timeline-model-comparison.webp) Final Cut Pro attaches connected clips to a primary storyline; Resolve exposes conventional video and audio tracks. Final Cut Pro isn't a simplified version of a conventional NLE. Its Magnetic Timeline is a different editing model. The Primary Storyline keeps the main sequence together; connected clips stay attached to the moment they belong to; roles organize dialogue, music, effects and other media without forcing every decision into fixed tracks. Apple says the timeline is designed to keep material in sync, prevent collisions and eliminate accidental gaps. That design is fast when the story has a clear spine. Interviews, events, courses, YouTube episodes and social cutdowns can move quickly because shifting the main edit carries connected material with it. The cost is relearning track-based muscle memory. If you spend the first week trying to force every connected clip into the mental model of V1, V2, A1 and A2, Final Cut will feel less predictable than it is. Resolve gives you two editorial routes. The Edit page uses the familiar track model, while the Cut page removes some interface overhead for fast assembly, source-tape work and multicam. That makes Resolve easier to place inside teams already exchanging traditional timelines. It also means more controls are visible and more pages are competing for a beginner's attention. The [Resolve learning path](https://davinciresolveclub.com/davinci-resolve-tutorial/) exists because learning all seven working pages at once is the slow route. Neither model is universally faster. Final Cut often reduces timeline housekeeping; Resolve reduces the number of application handoffs later in post. Decide which kind of friction costs you more. ## Media organization favors different project shapes ![Final Cut Pro roles and timeline index beside the DaVinci Resolve Media Pool](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/media-organization-comparison.webp) Final Cut Pro organizes editorial meaning with libraries, events, keywords and roles; Resolve uses project libraries, bins, smart bins and metadata. Final Cut Pro's libraries, events, keyword ranges, favorites, Smart Collections and roles are more than browser conveniences. They let an editor describe useful parts of a long clip without duplicating media or cutting everything into selects timelines. For documentary interviews, event footage and recurring channels, that metadata-first approach can be the feature that saves the most time. Resolve organizes work with project libraries, bins, smart bins, clip metadata, flags, markers and separate timelines. Its structure is more familiar to editors arriving from Premiere Pro or Avid-style track workflows. It also keeps the same media available to Color, Fusion and Fairlight without exporting a new version for each department. Test organization before effects. Import one messy card with duplicate takes, camera audio and an external recorder. Find three spoken moments, build selects, replace one shot and prepare audio stems. The application that makes those ordinary actions obvious will save more time than the one with the longer AI feature list. ## Color, VFX and audio change the answer Resolve's clearest advantage isn't that Final Cut lacks professional tools. It's that Resolve gives color, compositing and audio dedicated workspaces inside the same project. The Color page uses nodes, tracking, qualifiers, windows, color management and scopes as a primary workflow. Fusion adds node-based compositing and motion graphics. Fairlight provides detailed audio editing, repair, routing, buses, automation and delivery. Blackmagic's [official training library](https://www.blackmagicdesign.com/products/davinciresolve/training/?ref=davinciresolveclub.com) treats editing, color, Fusion and Fairlight as separate disciplines for a reason. ![Final Cut Pro color wheels beside the DaVinci Resolve Color page with nodes and scopes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/finishing-surface-comparison.webp) Final Cut keeps capable color tools in the editor; Resolve dedicates a full page to nodes, grading controls and scopes. [Final Cut Pro 12.3](https://support.apple.com/102825?ref=davinciresolveclub.com) has capable color wheels, curves, masks, keying, HDR/SDR tone mapping and the current Match Color tool. Its built-in effects and FxPlug ecosystem cover a large amount of editorial finishing. For custom titles and motion templates, Apple positions Motion as the companion application. Audio roles, multichannel editing and Logic-derived effects are strong for editorial work, but the workspace isn't trying to reproduce a full Fairlight console inside Final Cut. The 2026 releases also narrow several everyday workflow gaps. [Apple's release notes](https://support.apple.com/en-us/102825?ref=davinciresolveclub.com) show that Final Cut Pro 12.0 added Transcript Search, Visual Search and Beat Detection. Transcript Search and Visual Search require Apple silicon. Final Cut Pro 12.3 then added Generate Captions, Auto Mask, Match Color and Edit Detection. Generate Captions requires Apple silicon and is currently limited to U.S. English. These tools can shorten logging, captioning and first-pass masking, but they don't replace a test with your language, footage and delivery requirements. If 90 percent of the job is selection, pacing, titles and delivery, Final Cut's narrower surface can be an advantage. If the edit regularly turns into tracked cleanup, shot matching, complex keys, dialogue repair or deliverable-specific mixing, Resolve keeps more of the finishing work native. Use our [color grading map](https://davinciresolveclub.com/davinci-resolve-color-grading/), [Fusion hub](https://davinciresolveclub.com/davinci-resolve-fusion/) and [Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) to judge the depth without turning this comparison into three tutorials. ## Performance needs a reproducible test “Final Cut is faster on every Mac” and “Resolve uses the GPU better” are both too vague to guide a purchase. Apple controls Final Cut, macOS, Apple silicon and the media engines, so its current product page reasonably emphasizes optimization for that hardware, including ProRes workflows. Resolve also runs well on Apple silicon, but performance changes with edition, codec, debayering, noise reduction, Fusion, memory pressure and export settings. Don't compare a background-rendered Final Cut timeline with an uncached Resolve timeline and call it a benchmark. Final Cut Pro 12.3 now defaults background rendering to Off, so verify the current setting instead of assuming an older default. Use the same Mac, power mode, external drive, camera originals, timeline resolution and output file. Then record: 1. time from application launch to a playable project; 2. dropped frames during a one-minute multicam or effects section; 3. scrubbing response before and after proxies; 4. memory pressure after ten minutes of editing; 5. export time, the decoded result and the progress bar; 6. time required to change one title, one grade and one audio fix after client notes. Run the test once with camera originals and once with each application's intended proxy workflow. Resolve's [Proxy Media workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) is documented separately. Final Cut Pro 12.3 generates new proxies as HEVC, so record proxy format and resolution too. On an Intel Mac, decide compatibility before comparing speed: [Apple's current requirements](https://www.apple.com/final-cut-pro/?ref=davinciresolveclub.com) still list a Metal-capable Intel graphics card for the base Final Cut Pro app but note that some features require Apple silicon, while the [current Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) document Resolve 21's Apple-silicon requirement on macOS. ## Collaboration and handoffs need a dry run Resolve 21 has a clear answer for simultaneous project work. Blackmagic lays out [Blackmagic Cloud and Project Server collaboration](https://www.blackmagicdesign.com/products/davinciresolve/collaboration?ref=davinciresolveclub.com), including multiple people working in the same project and timeline, bin and timeline locking, shared markers, chat and timeline comparison. Media still needs a deliberate storage or sync plan; a shared project library does not make terabytes of source footage appear on another workstation. Final Cut Pro centers collaboration around libraries, media management, roles, XML and its third-party ecosystem. Apple documents both [import and export of FCPXML](https://support.apple.com/guide/final-cut-pro/use-xml-to-transfer-projects-verdbd66ae/mac?ref=davinciresolveclub.com) for exchanging libraries, events, projects and clips with compatible applications. That's a transfer format, not a promise that every plug-in, title, generator, retime, mask or effect will recreate itself in Resolve. Before committing to a cross-application workflow, duplicate the project and transfer a one-minute stress section. Include a compound clip, speed change, mixed frame rate, title, connected audio, color adjustment and third-party effect. Compare timecode, framing, transforms, audio channels and rendered reference. If the handoff fails there, it will fail more expensively at the end of the job. ## Which editor fits your work? ### Choose Final Cut Pro if - you edit only on Mac and do not need a Windows or Linux workstation in the same pipeline; - the Magnetic Timeline and metadata-first browser make sense after a real trial project; - fast selection, organization and editorial iteration matter more than built-in finishing depth; - Motion, Compressor and the broader Apple Creator Studio bundle replace tools you would otherwise buy; - your collaborators already exchange Final Cut libraries, roles and FCPXML reliably. ### Choose DaVinci Resolve if - you want a capable free editor before committing to a paid license; - projects move between macOS, Windows or Linux; - color, Fusion compositing or Fairlight mixing are regular parts of the job; - multiple specialists need to work in the same project through a documented Resolve collaboration workflow; - a conventional track timeline is easier to exchange with the rest of your team. ### Keep both if A two-application workflow is rational when Final Cut is the fastest place to shape the story but Resolve is the required finishing environment. The cost is handoff discipline. Lock the edit, simplify unsupported effects, export FCPXML plus a reference movie, confirm source timecode and render back into Final Cut only if the return trip is genuinely necessary. Owning both applications doesn't make an undisciplined round trip safe. If Final Cut Pro is only one option on your shortlist, the [DaVinci Resolve vs Studio breakdown](https://davinciresolveclub.com/davinci-resolve-vs-studio/) separates edition, pricing and workflow decisions before you test another editor. For the full editor-and-edition map, browse the [DaVinci Resolve comparisons hub](https://davinciresolveclub.com/davinci-resolve-comparisons/). ## Frequently asked questions ### Is DaVinci Resolve better than Final Cut Pro? Resolve is better for cross-platform work and deeper color, Fusion, Fairlight and simultaneous collaboration workflows. Final Cut Pro can be the better editor for a Mac-only creator who works faster with the Magnetic Timeline, libraries and roles. The project decides the winner. ### Is Final Cut Pro easier to learn than DaVinci Resolve? Final Cut presents a smaller working surface, but its Magnetic Timeline requires unlearning track-based assumptions. Resolve looks familiar on the Edit page but becomes broader once Color, Fusion, Fairlight and delivery enter the job. Test the same short project rather than judging the first hour. ### Is Final Cut Pro still a one-time purchase? Yes. Apple lists the standalone Mac application at $299.99 in the US. Final Cut Pro is also included in Apple Creator Studio, listed at $12.99 per month or $129 per year in the US. Regional pricing and tax vary. ### Can Final Cut Pro projects open in DaVinci Resolve? Final Cut Pro can export FCPXML for compatible third-party workflows, and Resolve can use that interchange route. Treat it as a timeline transfer, not a complete application clone. Validate titles, effects, generators, retimes, audio channels and plug-ins on a copy before moving a live project. ### Which is better on Apple silicon? Final Cut Pro is designed by Apple around macOS and Apple silicon, while Resolve performance depends more visibly on codec, edition and the amount of color, Fusion, AI and noise-reduction processing. A controlled test with your media is more useful than a universal speed claim. ### Should a beginner start with Resolve Free or Final Cut Pro? Start with Resolve Free if cost or cross-platform flexibility matters. Try Final Cut Pro if you already own a suitable Mac and value a focused editorial workflow. Build the same five-minute video in both before paying or moving a real library. For a Mac-only editor, this is a workflow decision before it is a feature decision. Final Cut Pro removes friction from selecting, organizing and reshaping an edit. Resolve removes friction from moving that edit through color, VFX, audio and delivery. Choose the friction you need gone every week, not the feature you might use once. ### Adjustment Clips in DaVinci Resolve URL: https://davinciresolveclub.com/adjustment-clips-davinci-resolve/ Last updated: 2026-09-05T00:36:30.000Z Drag an Adjustment Clip to a video track above the shots, trim it to the exact range, then add the effect, transform or grade. Resolve processes every lower video layer during that overlap. If a title, transition or picture-in-picture layer sits underneath, it's part of the result; if it sits above, it stays outside the adjustment. ![DaVinci Resolve 21 Adjustment Clip on V2 processing the video tracks below it](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/adjustment-clip-track-scope-v2-5.webp) Track position controls scope: the purple clip processes lower video layers only for the frames it overlaps. ## What an Adjustment Clip actually does An Adjustment Clip has no source picture of its own. It receives the current composite from lower video tracks for the frames it overlaps, applies its processing, and passes the result onward. Its horizontal duration defines *when* the effect runs; its vertical track position defines *which lower layers* are included. Checked September 5, 2026, the current [Adjustment Clips documentation](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) confirms the top-down workflow and shows the clip being placed on a higher video track, trimmed, named and dragged back into a Media Pool bin. The final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) also documents the supported processing: Resolve FX/OpenFX, Inspector Composite, Transform, Cropping and Dynamic Zoom, Fusion effects, plus Color-page grading and sizing. An Adjustment Clip is a good fit when the rule is “process the visible result under this exact timeline span.” It isn't automatically the best way to make several source clips share every type of change. For the surrounding edit-to-delivery sequence, use the [task-first DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/). Browse the [Workflow hub](https://davinciresolveclub.com/tag/workflow/) when you need the next focused editing or finishing task. ## Adjustment Clip vs Compound Clip, shared grade, and timeline node | Method | Best use | What changes | | ------------------------------ | ---------------------------------------------------------------------------- | --------------------------------------------------------------- | | Adjustment Clip | A bounded effect, transform or finishing look across visible lower layers | Processes the composite below for its overlap | | Multi-select in Inspector | Several clips need the same relative or absolute Inspector value | Writes that parameter to each selected clip | | Paste Attributes | Selected clip attributes or effects must be copied to chosen clips | Copies only the attributes selected in the dialog | | Compound Clip | Several selected clips must behave as one nested container | Changes edit organization and creates an internal timeline | | Group Pre-Clip/Post-Clip grade | Source shots need shared color processing while retaining clip-level control | Lives inside the Color pipeline for members of a group | | Shared Node | One grade node must stay linked across selected shots or timelines | Updates linked node instances, not the whole timeline composite | | Timeline Node | A final grade or technical operation truly applies to the whole timeline | Processes the timeline-level result in the Color page | Choose the narrowest method that matches the job. An Adjustment Clip is right when the already composited result needs one time-bounded treatment. Multi-select or Paste Attributes is cleaner when the same Inspector setting should remain attached to each source clip. For Color work, use groups, Shared Nodes or a one-time copy when each camera clip still needs its own input transform, balance, isolation or shot match. The [Resolve 21 grade-copy guide](https://davinciresolveclub.com/copy-color-grade-davinci-resolve/) separates replace, append and linked methods. ## How to add and use an Adjustment Clip ### 1\. Define the exact affected range Mark the first and last frame and inspect every video layer crossing that range. Decide whether titles, subtitles, overlays, transitions, and borders should be included. Create a clean higher video track if the current stacking order is ambiguous. ### 2\. Add the Adjustment Clip above the footage Open **Effects Library, then Toolbox, then Effects** and drag **Adjustment Clip** to the new track. Place graphics above it when they must remain untouched. Resolve doesn't offer a “skip V2 but affect V1” switch inside one Adjustment Clip; scope follows top-down compositing. ### 3\. Trim and split at meaningful boundaries Snap the start and end to the intended edits. Split around an exception instead of offsetting the underlying shot to cancel the effect. Short, purpose-specific clips are easier to audit than one purple bar spanning unrelated scenes. ### 4\. Apply one clearly named job Select the Adjustment Clip. Use the [Inspector](https://davinciresolveclub.com/davinci-resolve-inspector/) for transform, crop, Dynamic Zoom, opacity, and compositing controls; drag Resolve FX/OpenFX onto the clip for an Edit-page effect; or select the Adjustment Clip on the Color page for a bounded grade. Rename it by purpose: **Push-In 102–118**, **Glow Montage**, or **Final Warm Look**. “Adjustment Clip 7” tells the next editor nothing. ### 5\. Bypass before you trust it Disable the Adjustment Clip and compare the same frame. Then disable the track to catch other overlapping adjustment layers. Check the first and last frame, every transition underneath, and every title that enters or exits its range. ![DaVinci Resolve 21 Adjustment Clip selected with Inspector Transform and Opacity controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/adjustment-clip-inspector-v2-5.webp) Select the Adjustment Clip, open Inspector > Video, apply one clearly named job, and compare it disabled before moving on. ## Use Adjustment Clips for shared transforms and effects A single animated zoom, position move, crop, or opacity change can run across several edits without copying keyframes to every shot. This is useful for a montage push-in, shake, blur, glow, grain treatment, or an animated treatment spanning a cut. Remember that the transform acts on the *composited frame*. If a title sits below, the title moves too. If a clip has already been reframed, the Adjustment Clip adds another transform after that result. A double zoom may be intentional, but it should never be accidental. Because an Adjustment Clip processes the timeline result beneath it, treat Inspector Zoom there as a post-composite enlargement. Don't rely on it to recover the extra raster area of a 4K source in a 1080p timeline. Reframe the source clips when that source-resolution headroom matters, then reserve the Adjustment Clip for the shared treatment. For letterboxing or a delivery aspect ratio, don't automatically scale the whole composite with an Adjustment Clip. Output Blanking, timeline settings, or a correctly built matte may express the requirement more safely. The [Resolve aspect-ratio guide](https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/) separates framing, resolution, and black-bar workflows. ## What happens when Adjustment Clips are stacked Resolve processes the timeline from lower layers upward. A higher Adjustment Clip receives the result of footage plus any lower Adjustment Clip. That makes order visible in the track stack: 1. V1 footage is composited. 2. The Adjustment Clip on V2 processes that result. 3. Titles or graphics on V3 are added if they sit above V2. 4. A second Adjustment Clip on V4 processes everything below, including the V3 title. Stacking is valid when the order is deliberate. Keep separate clips when the jobs need independent ranges or bypass checks, but do not duplicate the same effect on source clips, a Compound Clip, two adjustment layers, and the Timeline node. Bypass each stage one at a time if the image looks too strong. ![DaVinci Resolve 21 Color page with an Adjustment Clip selected in the mini timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/adjustment-clip-color-page-v2-5.webp) Use the Adjustment Clip for a bounded finishing look after the source shots have been normalized and balanced. ## Color grading with an Adjustment Clip Yes, Resolve lets you grade an Adjustment Clip on the Color page. The important limitation is scope: the grade sees the composite under that clip, not each underlying source as an independent camera original. That makes an Adjustment Clip sensible for a limited finishing look, vignette, glow, monochrome passage, or a creative treatment across several already balanced shots. It's a poor place for camera-specific input transforms when the lower clips use different log curves, gamuts, white balances, or exposure corrections. In a color-managed project, do not paste a camera LUT onto an Adjustment Clip simply because every lower shot looks flat. Normalize and balance each source in the appropriate input pipeline first, then use the Adjustment Clip for a deliberately shared finishing look. The [DaVinci Resolve color-grading guide](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/) explains the correction-before-look order and the clip, group and timeline levels. ## Why transitions look different underneath An Adjustment Clip processes [the transition’s composited output](https://davinciresolveclub.com/davinci-resolve-transitions/) while the overlap is active. That can be exactly what you want for a glow or blur spanning the cut. It's different from placing the effect separately on each source before the transition is built. If only one side should receive the treatment, split or trim the Adjustment Clip at the edit. If the effect must influence transition generation per source, apply it to the source clips or use a [Compound Clip/Fusion structure](https://davinciresolveclub.com/davinci-resolve-compound-clips/) that gives you the required order. ## Save an Adjustment Clip as a reusable preset After naming and testing it, drag the Adjustment Clip from the timeline into a Media Pool bin. Put it in a Power Bin only when it should be available to projects in the same project library; in a multi-user setup, that shared access follows the Resolve user. Preserve enough duration for any animation, then check the first and last visible frame after placing and trimming a copy. Treat each placed copy as an independent timeline item unless you've verified linked behavior for the exact parameter. Updating a saved bin item isn't a safe substitute for checking existing timeline instances. For reusable animated transforms, check the first and last visible frame after every trim. That observable check is safer than assuming a saved animation still lands on the intended edit. The [Resolve keyboard shortcuts guide](https://davinciresolveclub.com/davinci-resolve-keyboard-shortcuts-guide/) includes timeline navigation and splitting commands that speed up range cleanup. ## Playback and render performance A heavy effect on one Adjustment Clip can force Resolve to process every lower pixel across a long range. Several stacked blur, noise, optical-flow, or AI effects can turn a smooth edit into a slow timeline even though the source clips play normally. - Bypass Adjustment Clips to identify the expensive layer. - Disable individual effects to find the real cost. - Use render cache or proxies where appropriate, but don't confuse cached playback with a verified final render. - Render the hardest short section and reopen it before committing to the full delivery. If the symptom is dropped frames rather than a memory error, work through the [Resolve slow-playback checklist](https://davinciresolveclub.com/davinci-resolve-slow-playback/). If Resolve reports exhausted VRAM, use the separate [GPU Memory Full troubleshooting guide](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/). Removing duplicate effects or shortening their scope is often more useful than lowering quality everywhere. ## Adjustment Clip troubleshooting ### A title or graphic is affected The title sits below the Adjustment Clip during the overlap. Move it to a track above, shorten or split the Adjustment Clip, or restructure the title and effect inside a Compound Clip if they must be processed together but isolated from the footage. ### I need to affect V1 but skip V2 One Adjustment Clip can't selectively ignore an intervening lower layer. Reorder tracks, move the unaffected layer above the Adjustment Clip, compound only the intended elements, or apply the effect directly to the chosen clip. The fix belongs in the timeline structure; there's no skip-track switch inside the Adjustment Clip. ### The effect is applied twice Check the source clip, Compound Clip, lower adjustment layers, Color group nodes, shared nodes, and Timeline node. Bypass from top to bottom until the duplicate disappears. ### Transitions change or flash The Adjustment Clip may start or end inside the transition, or the effect may process the combined transition rather than each source. Extend it across the entire transition or split it so neither side is ambiguously covered. ### Playback is smooth but the export differs Clear the assumption that real-time preview is final proof. Render a short section with the delivery settings, then check frame boundaries, motion blur, noise, and effect order in the file. ## A clean Adjustment Clip checklist - The clip’s name states one clear job. - Its duration starts and ends on intentional frames. - Every lower title, overlay, and transition has been reviewed. - No identical effect exists elsewhere in the processing chain. - The clip is bypassed and compared on the same frames. - The hardest section has been rendered and reviewed outside Resolve. ## Adjustment Clips FAQ ### What does an Adjustment Clip affect in DaVinci Resolve? It affects the composited video on lower tracks for the frames where it overlaps. Layers above it and frames outside its duration aren't processed. ### Where is the Adjustment Clip in Resolve 21? On the Edit page, open Effects Library, then Toolbox and Effects. Drag Adjustment Clip to a video track above the footage. ### Can I color grade with an Adjustment Clip? Yes. Use it for a bounded finishing look across the composite below. Use clip, group, or shared nodes when underlying sources need independent color management and shot-level control. ### Why does an Adjustment Clip affect my title? The title is on a lower track inside the Adjustment Clip’s time range. Move the title above it or change the range and timeline structure. ### Can I stack Adjustment Clips? Yes. Higher Adjustment Clips process the result of all lower layers. Name each job, keep ranges narrow, and verify that the same effect isn't duplicated elsewhere. ### Do Adjustment Clips work in Resolve Free? The Adjustment Clip itself is a standard Edit-page feature in Resolve Free. The Resolve FX, OpenFX or AI tool placed on it may still be Studio-only, so check the specific effect rather than treating the container as the license boundary. ### Change Resolution and Aspect Ratio in DaVinci Resolve URL: https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/ Last updated: 2026-09-05T00:27:34.000Z Timeline resolution sets the editing canvas; aspect ratio describes its shape, and output resolution sets the rendered pixel dimensions. For a vertical or square version, duplicate the timeline, choose Use Custom Settings, set the target resolution, and reframe the clips there. Keep the Deliver page on Match timeline settings unless the delivery brief requires different output dimensions. Pixel aspect ratio is a separate setting. Normal web and social delivery uses square pixels; change pixel aspect only when a documented anamorphic or broadcast workflow requires it. It isn't a shortcut for turning a 16:9 edit into 9:16. ## Common Aspect Ratios and Timeline Resolutions | Aspect ratio | Common resolution | Typical use | | ------------ | ------------------------------------------------------------------------ | ---------------------------------------------- | | 16:9 | 1920 × 1080 or 3840 × 2160 | Standard landscape video | | 9:16 | 1080 × 1920; 2160 × 3840 only when the destination and format support it | Vertical Shorts, Reels, and TikTok-style video | | 1:1 | 1080 × 1080 | Square social posts | | 4:5 | 1080 × 1350 | Portrait feed posts | | 2.39:1 | Custom canvas or output blanking | Widescreen delivery or a letterboxed look | These are practical starting points, not permanent platform laws. Check the destination’s current upload specification before delivery. Keep the project frame rate unchanged unless the brief also calls for a frame-rate conversion; changing shape and cadence at the same time creates an avoidable second problem. ## Timeline Resolution, Output Resolution, and Clip Reframing I separate aspect-ratio work into three layers: - **Timeline resolution** defines the canvas you edit and judge. - **Output resolution and scaling** can override or resize the finished canvas for delivery, but they don't choose the composition inside the frame. - **Clip transforms** decide which part of each source shot appears inside the canvas. For a dedicated vertical version, change the timeline and edit inside the vertical Viewer. Don't leave the timeline landscape and rely on Deliver to crop it at the end. You need to see missing faces, clipped titles, and empty areas while you still have time to fix them. Checked September 5, 2026, the final [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) documents individual timeline settings, Use Custom Settings, Use vertical resolution, mismatched-resolution rules, Inspector transforms, Smart Reframe, and sizing/blanking delivery behavior. Blackmagic’s [official Edit page](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) provides the current editing overview. ## Change the Aspect Ratio of One Timeline 1. **Duplicate the original timeline.** Right-click it in the Media Pool and choose **Duplicate Timeline**. Name the copy by destination, such as `Cut_Vertical_9x16`. 2. **Open Timeline Settings.** Right-click the duplicated timeline and choose **Timelines, then Timeline Settings**. 3. **Choose custom controls.** Select **Use Custom Settings** so this duplicated timeline can use its own Format, Monitoring, Output, and Color settings. 4. **Enter the target resolution.** Set 1080 × 1920 for a common Full HD 9:16 canvas, 1080 × 1080 for square, or the dimensions required by the delivery brief. When a landscape preset only needs its axes swapped, enable **Use vertical resolution**. 5. **Choose mismatched-resolution handling.** Use **Scale full frame with crop** when the frame must be filled, or **Scale entire image to fit** when retaining every edge matters more than avoiding bars. 6. **Save and inspect the Viewer.** Confirm that the Viewer itself has the new shape before reframing clips. If you're starting a project that will only ever be vertical, you can set the project timeline resolution before editing. If you already have a finished 16:9 cut, always work from a duplicate. That keeps the landscape master intact and lets the two versions diverge where a vertical edit needs a different shot, title, or cut point. ![DaVinci Resolve 21 Project Settings with a 1080 by 1920 vertical timeline and square pixels](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/aspect-ratio-timeline-settings-v2.webp) For a vertical-only project, Project Settings uses a 1080 × 1920 square-pixel canvas. For a second deliverable, apply the same canvas in the duplicated timeline’s custom settings instead. Resolve 20.1 and later also exposes a Timeline Resolution control in the Cut, Edit and Color viewers. The [official Resolve 20.1 guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20.1%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) shows Full HD, Ultra HD, Portrait, Square and Custom Timeline Settings. Use that menu as a shortcut to the active timeline, then still review its mismatch rule and the queued Deliver resolution. ## Choose Fit, Crop, or Manual Reframe | Scaling choice | What Resolve does | Use it when | | ---------------------------- | -------------------------------------------------------------- | ----------------------------------------------- | | Scale entire image to fit | Shows the whole source and adds blank space when shapes differ | No edge can be lost | | Scale full frame with crop | Fills the canvas and crops the excess dimension | A full-bleed frame matters | | Center crop with no resizing | Keeps source scale and crops pixels outside the canvas | You need deliberate pixel-for-pixel framing | | Stretch frame to all corners | Distorts width or height to fill the canvas | Usually only for a specific anamorphic workflow | For wide footage in a vertical timeline, I normally start with full-frame crop and then reframe every shot that contains a face, product, text, or meaningful action. Stretching a normal shot isn't a shortcut; it changes people’s proportions and makes graphics look wrong. ![DaVinci Resolve 21 Image Scaling menu comparing Scale entire image to fit and Scale full frame with crop](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/aspect-ratio-scaling-fit-crop-v2.webp) Project Settings > Image Scaling sets the default: Fit preserves the complete source and may add blank space; Crop fills the canvas by removing excess edges. A custom timeline can use its own mismatch rule. ## Reframe Each Clip with Zoom and Position 1. Select a clip on the Edit timeline. 2. Open **Inspector, then Video, then Transform**. 3. Adjust **Zoom** until the image fills the new canvas without unwanted bars. 4. Use **Position X** to choose which part of a wide shot remains visible. Use Position Y only when the vertical composition also needs to move. 5. Play the entire clip. Its first frame cannot reveal every framing problem. When several clips have genuinely similar composition, copy the transform and use Paste Attributes. Don't batch-paste one crop across an interview, a two-shot, a screen recording, and a product close-up. The [DaVinci Resolve Inspector guide](https://davinciresolveclub.com/davinci-resolve-inspector/) explains the transform controls and reset buttons if stacked adjustments become confusing. ![DaVinci Resolve 21 Edit page Inspector using linked Zoom and Position to reframe a clip for vertical video](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/aspect-ratio-inspector-reframe-v2.webp) Reframe shot by shot with linked Zoom and Position, then inspect both ends of every moving clip. ## Follow a Moving Subject with Keyframes A centered crop works only while the subject stays near the center of the source. If a person walks across a landscape frame, place the playhead where the reframe should begin and enable the diamond beside Position. Move forward, change Position X to follow the action, and Resolve creates the next keyframe. Use as few keyframes as the shot allows. A constant series of small corrections feels like a nervous camera operator. I place keyframes around real direction changes, then watch the move at normal speed and adjust easing if the crop accelerates abruptly. AI Smart Reframe is Studio-only in Resolve 21\. It can make a useful first pass when converting 16:9 material to 9:16, but it still needs shot-by-shot review when subjects cross, graphics enter, or the important object isn't the automatically chosen target. ![DaVinci Resolve 21 Studio AI Smart Reframe controls with Object of Interest and Reframe workflow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/aspect-ratio-smart-reframe-v2.webp) In Resolve Studio, AI Smart Reframe can create the first pass; review the complete shot before accepting its framing. ## Cinematic Widescreen: Canvas or Output Blanking? If you want a 2.39:1 letterboxed look inside a standard 16:9 delivery, use Timeline > Output Blanking. It masks the top and bottom of the image; it doesn't change the timeline or encoded file resolution. A 1920 × 1080 timeline rendered at 1920 × 1080 remains a 1920 × 1080 file with the bars in the picture unless sizing and blanking output is disabled. If the distributor requests a native wide raster with no encoded bars, set the actual timeline and Deliver dimensions to that specification. These are different deliverables. In Deliver Advanced Settings, leave **Disable sizing and blanking output** off when approved sizing and blanking must be baked into the rendered picture; if it is on, those operations aren't rendered. Confirm this switch before queueing the final job. ## Protect Titles, Captions, and Graphics A frame can be technically 9:16 and still fail on a phone because interface controls cover the lower caption line or a username sits under an overlay. Keep critical text away from extreme edges, preview the file on the target device, and make a private test upload when the platform UI matters. Check compound clips, Fusion compositions, and adjustment clips separately. Their transforms can react differently from the source clips after a canvas change. If an adjustment layer carries a global effect, review the boundaries using the [adjustment clips guide](https://davinciresolveclub.com/adjustment-clips-davinci-resolve/) before copying it to the vertical version. ## Match the Deliver Page to the New Timeline Open Deliver and verify the queued job as well as the active timeline. The resolution should match the intended canvas, the correct vertical or square timeline should be open, and frame rate should match the edit unless the delivery brief separately requires conversion. Recheck **Disable sizing and blanking output**: off bakes approved sizing/blanking; on omits it. Render a short representative section first. Inspect the file’s pixel dimensions, watch it outside Resolve, and check that no black bars were added by an unintended scaling option. Then use the [Resolve export settings guide](https://davinciresolveclub.com/davinci-resolve-export-settings/) for codec and bitrate decisions. For a complete render walkthrough, the [video export guide](https://davinciresolveclub.com/export-video-davinci-resolve/) covers the Render Queue and final file checks. ## Resolve Free vs Studio DaVinci Resolve Free can create custom vertical, square, landscape, and widescreen timelines. It also includes manual Zoom, Position, cropping, keyframes, scaling rules, and ordinary exports within the free version’s format limits. Studio isn't required for a 9:16 timeline. Resolve Free includes custom vertical, square and widescreen canvases plus manual Zoom, Position, crop and keyframes. Blackmagic's [current Free specification](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) promises resolutions as high as Ultra HD 3840 × 2160 at up to 60 fps, but it does not explicitly guarantee 2160 × 3840 vertical. Verify that exact workflow before committing to it, and use Studio when UHD vertical delivery is a hard requirement. ## Fix Aspect-Ratio Problems ### Black bars appear after changing resolution The current mismatch rule is preserving the complete source frame. Choose Scale full frame with crop, or zoom and reposition that clip manually if the frame must be filled. ### The subject is cut off in vertical video Select the clip and change Position X in the Inspector. Add position keyframes if the subject moves. An automatic center crop can't preserve off-center action. ### The export is still landscape Confirm that the correct timeline is active and that the queued render job shows vertical dimensions. A queue can retain an earlier job made from the landscape timeline. ### The image looks soft Check the source resolution and how far you zoomed. Avoid scaling the same image at the clip, timeline, and output layers without a reason. Judge sharpness in the rendered file at its actual display size. ### The timeline settings are locked Choose Use Custom Settings in the individual Timeline Settings window. If the resolution controls still don't respond, confirm you opened the duplicated timeline’s settings rather than changing project-wide Master Settings. ### Captions are covered on the phone Move them into a conservative safe area and test the final upload interface. Resolve’s clean Viewer can't predict every platform overlay. ## My Final Reframe Check I watch the vertical or square timeline full-screen without the Inspector open. On every cut I check faces, hands, products, subtitles, lower thirds, and motion entering from the cropped edges. Then I compare the rendered pixel dimensions with the destination requirement and watch the file on a phone. A vertical version is a new edit, not an export checkbox. A duplicated timeline plus shot-level framing takes longer than a blind center crop, but it's the difference between a recycled landscape video and a version that actually belongs on a vertical screen. If the destination is YouTube, finish with the current [YouTube export settings](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/). For the broader sequence from timeline setup through delivery, follow the [task-first DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/). ## DaVinci Resolve Aspect Ratio FAQ ### What resolution should I use for 9:16 video? 1080 × 1920 is a common Full HD 9:16 canvas. Blackmagic publishes Resolve Free for resolutions as high as Ultra HD 3840 × 2160 at up to 60 fps, but doesn't explicitly guarantee 2160 × 3840 vertical. Verify that exact workflow before committing to it, and use Studio when UHD vertical delivery is a hard requirement. ### How do I make a square video in Resolve? Duplicate the timeline, open Timeline Settings, choose Use Custom Settings, and set 1080 × 1080\. Then choose fit, crop, or manual reframe for the clips and match the Deliver resolution. ### Why do I get black bars after changing aspect ratio? Scale entire image to fit preserves the whole source and adds unused space when the shapes differ. Use full-frame crop or a manual Zoom and Position adjustment to fill the canvas. ### Can I keep vertical and landscape versions in one project? Yes. Give each version its own timeline and custom timeline settings. This protects the original composition and keeps their edits and exports separate. ### Does changing aspect ratio reduce quality? The new shape doesn't automatically reduce quality. Heavy zooming, insufficient source resolution, stacked scaling, and another platform encode can make the final image softer. ### Do I need Resolve Studio for vertical video? No. Custom vertical timelines and manual reframing work in Resolve Free. Smart Reframe requires Studio; availability of other AI tools varies by feature and platform. ### How to Blur a Face or Background in Resolve URL: https://davinciresolveclub.com/blur-face-background-davinci-resolve/ Last updated: 2026-09-05T00:15:57.000Z To blur a moving face in DaVinci Resolve, add a dedicated Color-page node, draw a soft Power Window around the entire recognizable area, track the window forward and backward, then increase Blur Radius or add Mosaic Blur. Resolve Free can do that complete route. Resolve Studio adds Magic Mask 2 and depth-aware tools for difficult subject isolation, but they don't remove the need to inspect the final render frame by frame. Background blur is a different job. It keeps the person sharp and softens the outside region, so it can't anonymize that person. Start by deciding what must be hidden or what must remain sharp; that choice determines the mask, tracker and review standard. ## Choose the Blur Method by the Job - Moving face, license plate or logo: tracked Power Window on a dedicated Color node; available in Free and Studio. - Irregular object or a track that needs detailed occlusion repair: Polygon or B-spline mask with point or planar tracking in Fusion. - Moving person with hair, hands and changing silhouette: Magic Mask 2 in Resolve Studio. - Creative background blur with several depth planes: Depth Map or Lens Blur in Resolve Studio. - Locked-off subject with a simple outline: custom Power Window plus an Outside node; available in Free and Studio. Checked September 5, 2026, the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) documents Power Windows, Window-mode tracking, the Color-page Blur palette, Outside nodes and Mosaic Blur. It marks Magic Mask v2 and Lens Blur as Studio-only. Blackmagic’s [Studio feature page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) also lists Magic Mask, object isolation and tracking, Depth Map and Lens Blur among Studio features. ## Blur a Moving Face with a Power Window 1. Open the Color page and select the clip. Place the playhead on a frame where the face is clear, large enough to inspect and not covered by another object. 2. Add a serial node with Option+S on macOS or Alt+S on Windows. Rename it Face Blur so the privacy correction is easy to isolate and audit. 3. Open the Window palette, choose a circular window and fit it around the full recognizable area. Include forehead, chin, ears and enough margin for normal head motion. 4. Increase window softness so the boundary doesn't look pasted on. Softness changes the transition, not the protected area, so don't feather away essential coverage. 5. Open the Tracker palette in Window mode. From the clean reference frame, analyze to the end and then to the beginning of the clip. 6. Open the Blur palette and increase the ganged Radius control until facial detail is no longer recognizable at final output size. Mosaic Blur is another documented option when an obvious pixelated treatment suits the job. 7. Review the complete rendered section. Stop on profile turns, fast movement, frame edges, reflections, occlusions and every place where two people cross. ![DaVinci Resolve 21 Color page Power Window sized around a face on a dedicated serial node](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/face-blur-power-window-v2.webp) Use a dedicated node, draw a circular Power Window around the full recognizable area, and soften the edge without reducing privacy coverage. Tracking before or after applying the blur produces the same basic node structure: the node contains both the Power Window key and the correction. Tracking the clean image makes the feature easier to see; applying a temporary visible blur first makes it obvious which node is active. What matters is that the window is analyzed from a useful reference frame and the final result is checked after rendering. ## Make the Window Large Enough for Privacy A flattering beauty blur isn't an anonymizing blur. Light softening can preserve eye spacing, profile shape, scars, hairline or a distinctive tattoo. Cover the full recognizable area, allow for motion beyond the reference frame, and judge the result at the exported resolution rather than in a small proxy viewer. Look beyond the face. A reflection, name badge, license plate, house number, computer screen, clothing, voice or distinctive location can identify someone even when the face is hidden. Separate moving targets should normally get separate nodes so each has an independent track, blur strength and repair history. ## Repair a Power Window That Drifts The tracker analyzes image motion; it doesn't understand your privacy requirement. A completed analysis can still slide onto the wrong face, lag behind a fast turn or follow the object that caused an occlusion. Repair the track where it first becomes wrong, not several seconds later where the error was first noticed. 1. Find the last correct frame and then the first frame where the window leaves the protected area. 2. Reposition or resize the window on that first failed frame. 3. Track only through the next clean segment instead of repeatedly analyzing the whole clip. 4. When another object covers the face, use manual window keyframes through the occlusion. 5. When the face becomes visible again, establish a clean window and resume automatic tracking from there. 6. If the person leaves frame, keep the window away from other visible subjects until the intended face returns. ![DaVinci Resolve 21 Tracker Window controls and first-failed-frame repair for a drifting face mask](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/face-blur-tracker-repair-v2.webp) Track from a clean reference frame, inspect the first failed frame, reposition the window, and analyze the next clean segment. If crossings, changing perspective or a moving surface make the Color tracker unreliable, use the [Fusion tracking guide](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/) to choose between a point track and a planar track. Neither tracker is a face detector, and the manual explicitly notes that no tracker is a 100% solution. ## Soft Blur or Mosaic Blur? Soft blur is visually quieter. Raise the Color-page Blur Radius and soften the window boundary, then pause on the sharpest source frame and check whether recognizable features remain. A gentle portrait-softening setting is rarely strong enough for privacy. Mosaic Blur creates a visibly pixelated treatment. The final Resolve 21 manual lists it without a Studio-only label and specifically illustrates it as a way to hide a witness’s face. Choose cells large enough to remove detail in the delivered file, not merely in the viewer. Neither mosaic nor soft blur creates a legal or technical guarantee of anonymity. ## Blur Multiple Faces Without Losing Control Use one serial node and one tracked window per moving face. A compact node graph with several windows on one node may look tidy, but independent tracks are easier to inspect and repair when people move at different speeds or cross each other. Rename nodes Face 1, Face 2 and so on, and verify that each effect begins and ends with the correct person. Static targets can share a node when the correction and timing are identical. Once targets move independently, separate nodes reduce the chance that fixing one mask silently breaks another. For a dense crowd or long privacy-critical sequence, budget time for a full-frame review; automation doesn't turn that requirement into a spot check. ## Blur the Background and Keep the Person Sharp For background blur, isolate the entire subject and apply blur to the outside region. A small inverted oval around the face leaves the head sharp but blurs hair, shoulders, hands and foreground objects inconsistently. It can work as a vignette, but it does not resemble shallow depth of field. ## Resolve Studio: Magic Mask 2 1. Add a new Color node and open Magic Mask 2. 2. On a clear reference frame, place an add click inside the subject. Resolve 21 Magic Mask v2 no longer has separate Person and Object modes. 3. If the result includes a background object, place a subtract click on that object and verify the entries in the Click List. 4. Track forward and backward, then inspect the matte overlay around hair, hands and gaps between limbs. 5. Use an Outside node or invert the key so the correction affects the background rather than the selected subject. 6. Apply moderate blur first, repair weak matte frames, then increase strength only if the edge remains convincing in motion. The full [Resolve 21 Magic Mask guide](https://davinciresolveclub.com/davinci-resolve-magic-mask/) explains click tracking, first-failure repair and Render in Place. Magic Mask is best when the decision is “subject sharp, everything else softer.” It isn't the privacy route while that same subject remains sharp. ![DaVinci Resolve 21 Studio Magic Mask 2 subject isolation for blurring the background](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/background-blur-magic-mask-v2.webp) Magic Mask 2 can keep the subject sharp while a separate node blurs the outside region; this is a background effect, not anonymization. ## Resolve Studio: Depth Map and Lens Blur Use Depth Map when the effect should vary across more than two depth regions. The depth matte estimates perceived distance, which can separate foreground, subject and far background more naturally than one outside mask. Inspect hair, glass, foliage, motion blur and overlapping objects because inferred depth can be wrong or unstable. Lens Blur is a Studio-only Resolve FX simulation of optical lens blur. It can create more lens-like bokeh than the basic Blur palette, but it still depends on a sound isolation or depth decision. It doesn't recover real optical depth data that was never captured. ## Background Blur in Resolve Free Resolve Free can blur the outside of a custom Power Window. For a locked-off interview or a subject with a simple silhouette, draw a Curve window around the person, soften and track it, then add an Outside node to apply the blur to the inverse area. The manual documents Option+O on macOS for Add Outside Node; the menu command is also available by right-clicking the source node. Hair, moving hands and frequent occlusions require a maintained matte. In Fusion, animate Polygon or B-spline masks and use point or planar tracking where the motion supports it. The [Fusion rotoscoping guide](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/) covers the manual route without pretending that one automatic selection can solve every frame. ## When an Adjustment Clip Helps An adjustment clip can carry a full-frame blur across several timeline clips, but it does not isolate or track a moving face by itself. It also affects every visible layer beneath it unless the effect is constrained. Use a clip-level Color node for identity protection; use an adjustment clip only when its timeline coverage is intentional. The [adjustment clip guide](https://davinciresolveclub.com/adjustment-clips-davinci-resolve/) explains stacking and scope. A timeline convenience should never make it harder to prove that every protected frame is covered. ## Resolve Free vs Studio for Blur Work - Tracked Power Window face blur: Free and Studio. - Color-page Blur palette and Outside nodes: Free and Studio. - Mosaic Blur: listed in the current manual without a Studio-only mark. - Fusion Polygon/B-spline masks with point and planar tracking: core Free and Studio workflow. - Magic Mask 2: Studio only. - Depth Map and Lens Blur: Studio only. Studio can shorten difficult isolation work; it doesn't replace quality control. For a conventional face blur, the Power Window route remains the clearest path because its coverage and tracking can be inspected directly. ## Fix Common Blur Problems ### The blur drifts off the face Return to the first incorrect frame, reposition the window and analyze a shorter section. If rotation or perspective dimensions introduce motion the shot doesn't contain, disable those dimensions and retrack the segment. ### The window edge is obvious Slightly enlarge the window and increase softness. Judge the boundary after the main correction because contrast and sharpening can reveal an edge that looked acceptable earlier in the node tree. ### The blur disappears during an occlusion Keyframe through the covered frames and restart tracking from a clean frame after the face returns. Do not allow the tracker to jump onto the object crossing in front. ### The face is still recognizable Increase the protected area and blur strength, then check profile frames, reflections and the final output size. Hiding only the eyes or center of the face leaves other identifying structure visible. ### The background matte flickers around hair Repair weak frames, refine the edge and avoid an unnecessarily extreme blur that exaggerates every matte error. Depth discontinuities, fine hair and motion blur can expose a poor selection even when one paused frame looks clean. ### Playback becomes too slow Cache or render the effect for review, especially with several Studio masks or depth effects. Don't approve privacy coverage from skipped playback frames; inspect a full-quality render. ## Final Privacy Review Before Export - Watch once while looking only at mask boundaries and every entrance, exit and occlusion. - Watch again while actively looking for identifying detail: profile, reflection, screen, plate, badge, tattoo, clothing and location. - Check the first and last frame of every protected section at final delivery resolution. - Listen for names or a distinctive voice and inspect metadata when anonymity matters. - Keep the protected master separate from unblurred source and confirm the correct file is delivered. For the wider node, qualifier and tracking context, continue with the [DaVinci Resolve color-grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/). The [Resolve learning roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/) connects this skill to Edit, Color and Fusion workflows without duplicating the same blur intent. ## DaVinci Resolve Blur FAQ ### Can I blur a face in DaVinci Resolve Free? Yes. Add a Color-page node, draw and track a Power Window, then increase Blur Radius or use the available Mosaic Blur effect. Magic Mask isn't required for a conventional moving-face blur. ### How do I blur the background but keep a person sharp? Isolate the full person, invert the key or add an Outside node, then apply blur to the background. A custom tracked mask works in Free; Magic Mask, Depth Map and Lens Blur are Studio options. ### Is Magic Mask available in Resolve Free? No. Magic Mask v2 is Studio-only in the current Resolve 21 Reference Manual. Power Windows and manual Fusion masks provide the Free alternatives. ### Should I use soft blur or mosaic for anonymization? Either can remove picture detail when the protected area, strength and track hold at final resolution. Soft blur is quieter; mosaic makes the treatment obvious. Neither guarantees anonymity, so check every frame and other contextual clues. ### Why does the Power Window stop following the face? Occlusion, fast movement, motion blur, leaving frame or a weak reference frame can break the analysis. Repair from the first failed frame and use manual keyframes through difficult sections. ### Can I track more than one face? Yes. Use separate nodes and windows so each moving face has independent tracking and blur strength. That makes crossings and failed segments easier to repair. ### Does strong blur guarantee anonymity? No. A missed frame, reflection, voice, location, clothing or metadata can still identify someone. Review the complete final render rather than only the mask overlay. ### Is Lens Blur available in Resolve Free? No. Lens Blur is marked Studio-only in the current Resolve 21 manual. The Color-page Blur palette remains the core Free route for softening a masked region. ### Audio Levels and LUFS in DaVinci Resolve URL: https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/ Last updated: 2026-09-12T11:52:52.000Z A mix can peak safely and still be much louder or quieter than the programs around it. It can also hit the right integrated LUFS while a short transient clips after encoding. Do not choose between peak and loudness meters. They answer different questions. ![DaVinci Resolve Fairlight signal path with track meters, Main Control Room output, and loudness meter](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/audio-levels-signal-path-v2.webp) Read levels in signal-flow order: repair an overloaded track or bus before using the final Loudness meter to judge the complete program. ## LUFS, dBFS, and True Peak in Plain English | Reading | What it tells you | Common mistake | | ------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------ | | **Sample peak (dBFS)** | The highest encoded sample value | Assuming a safe sample peak guarantees safe encoded playback | | **True peak (dBTP)** | An estimate of inter-sample peaks after reconstruction or conversion | Leaving no headroom for lossy encoding | | **Momentary loudness** | Very short loudness window, roughly 400 ms under EBU mode | Trying to master an entire program from a jumping number | | **Resolve numeric Short / Short Max** | The final Resolve 21 manual describes a 30-second window | Confusing this readout with the three-second history curve | | **Loudness History: Short Term** | The past three seconds | Confusing one loud scene with the program average | | **Integrated loudness** | Gated loudness across the measured program | Reading it before the whole relevant range has played | | **Loudness Range (LRA)** | A statistical view of program loudness variation | Treating it as a mandatory target without a delivery spec | Checked September 5, 2026, LUFS means Loudness Units relative to Full Scale. LKFS is the equivalent K-weighted term used by some standards; for the same BS.1770 measurement, the numerical values are treated equivalently. [Blackmagic's official Fairlight page](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) confirms selectable standards, tolerance color coding, a main-bus loudness graph, and offline clip analysis. The final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) documents the meter controls and readouts on pp. 4133–4137. ## Which LUFS Target Should You Use? Use a signed delivery specification when one exists. The examples below are orientation, not permission to ignore a network, distributor, or client document. | Destination | Published reference | True peak | | ---------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------ | | **European broadcast (EBU R 128)** | \-23 LUFS program loudness | Generally no higher than -1 dBTP | | **US broadcast (ATSC A/85)** | \-24 LKFS for content without matching metadata; about ±2 dB measurement tolerance | Below -2 dBTP in the cited guidance | | **Apple Podcasts** | About -16 dB LKFS, ±1 dB | No higher than -1 dBFS true peak | | **Netflix commissioned delivery** | Specification-dependent dialogue-gated and/or full-program measurement | Use the current title-specific delivery specification | | **YouTube creator upload** | No public fixed upload LUFS requirement in YouTube’s creator formatting guidance | Leave sensible encoding headroom and verify the upload | The [EBU’s loudness guidance](https://tech.ebu.ch/loudness?ref=davinciresolveclub.com) specifies -23 LUFS and defines momentary, short-term, and integrated measurement. [ATSC A/85](https://www.atsc.org/wp-content/uploads/2025/06/A85-2013-with-Corrigendum-No-1.pdf?ref=davinciresolveclub.com) uses -24 LKFS when loudness metadata is absent or unspecified and recommends true peaks below -2 dBTP in that context. [Apple Podcasts’ current requirements](https://podcasters.apple.com/support/893-audio-requirements?ref=davinciresolveclub.com) recommend about -16 LKFS ±1 with true peak no higher than -1 dBFS. You'll often see “-14 LUFS for YouTube” repeated as if it were an upload contract. It can be a useful community mastering reference, but YouTube's current public [video and audio formatting guidance](https://support.google.com/youtube/answer/4603579?hl=en&ref=davinciresolveclub.com) does not state a universal creator-upload LUFS requirement. Its separate [audio-enhancements guidance](https://support.google.com/youtube/answer/16619284?hl=en&ref=davinciresolveclub.com) says playback audio may be adjusted and that viewers can manage Stable volume or Voice boost. Don't crush a good mix merely to chase a screenshot from “Stats for nerds.” ## Fix Levels in Signal-Flow Order 1. **Set repeatable monitoring.** Pick a sensible speaker or headphone level and stop changing it every scene. 2. **Repair clip-level outliers.** Use clip gain so unusually quiet or loud recordings enter the track chain in a workable range. 3. **Build dialogue first.** Balance representative quiet, normal, and loud lines before music and effects. 4. **Shape tracks.** Use EQ, compression, automation, and cleanup only where they solve an audible problem. 5. **Place music and effects around speech.** Lower or automate competing material instead of forcing dialogue through it. 6. **Watch buses and Main.** Several safe tracks can sum into an overloaded subgroup or output. 7. **Measure after all processing.** The loudness meter must see the same final bus that the deliverable uses. Clip gain is pre-track correction; a track fader balances that track in the scene; a bus fader balances a group; Main controls the program output. If your routing is unclear, fix that before metering with our [Fairlight bus-routing guide](https://davinciresolveclub.com/fairlight-bus-routing/). ## Build a Dialogue Anchor Before Chasing LUFS Choose several passages: a normal line, the quietest intentional line, an excited line, and a section under music. Set clip gain so the track processor receives consistent material without flattening performance. Then automate phrases that still wander. Peak position alone doesn't define good dialogue. Mic distance, noise, spectral balance, accent, room reflections, music masking, and dynamic range all affect intelligibility. Use the tools in order: clean obvious problems, shape tone with the approach in our [Fairlight dialogue EQ guide](https://davinciresolveclub.com/fairlight-eq-dialogue/), control excessive variation with the [dialogue compressor workflow](https://davinciresolveclub.com/fairlight-compressor-dialogue/), then rebalance in context. Resolve 21’s Voice Isolation and Dialogue Leveler can help specific recordings, but neither is a master-loudness control. Our [Voice Isolation vs Dialogue Leveler comparison](https://davinciresolveclub.com/voice-isolation-vs-dialogue-leveler/) explains which problem each tool is designed to solve. ## Set Up Fairlight Loudness Monitoring 1. Go to the **Fairlight** page and open the Mixer and Control Room monitoring controls. 2. Confirm that you're monitoring the same Main bus used for export. 3. Open the loudness meter options and choose the required standard: for example EBU R128, ATSC A/85, BS.1770, or another listed profile. 4. Confirm the meter’s target and tolerance against the current delivery document. 5. Enable true-peak measurement where the chosen meter or Loudness Meter effect exposes it. 6. Reset the integrated measurement immediately before the program start. If Lock Metering to Transport is enabled, moving the playhead resets the analysis; confirm that behavior before a compliance pass. 7. Play the complete delivery range without jumping the playhead. 8. Record the metrics required by the delivery spec: Integrated, the relevant Short/Short Max or Short Term history view, Loudness Range, and maximum True Peak. Resolve’s colored loudness display is a compliance aid, not an automatic mix decision. Blue, yellow, and red depend on the selected standard and tolerance. A blue reading under EBU R128 is not necessarily wrong for a podcast, and a yellow reading under a custom -14 preset isn't broadcast approval. ![DaVinci Resolve Loudness meter standard menu and Offline Analyze Audio Level results](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/audio-levels-live-offline-metering-v2.webp) Live and offline readings are comparable only when they use the same loudness standard, bus, and measured range. ## Measure the Correct Range Integrated loudness is only meaningful for the program that actually played after the last reset. Start at the first frame required by delivery and finish after the required tail. If the spec includes bars, tone, ident, or silence outside the measured program, follow its measurement boundaries precisely. For a bounced or rendered audio clip, right-click it and use Analyze Audio Level for the offline check. The three-second Short Term history curve helps you locate a shout, music sting, or weak scene. The numeric Short/Short Max readout is a different Resolve measurement, and Momentary loudness is more local still. Neither can replace a complete integrated pass. If you change a bus limiter, music automation, dialogue gain, or the measured duration, reset and measure again. ![DaVinci Resolve Loudness History graph with Integrated, Momentary, and Short Term curves enabled](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/audio-levels-loudness-history-v2.webp) Reset at program start, play the required range without skipping, and repeat the measurement after any material mix change. ## Use a Limiter for Peaks, Not as a Loudness Bulldozer A true-peak limiter on the final bus can catch remaining transients, but it should be the guardrail after a balanced mix. If it's shaving several decibels throughout every chorus or sentence, lower the contributing buses or revise compression upstream. Constant limiting changes punch, ambience, and speech texture. Set the output ceiling from the delivery spec. Online work often leaves at least 1 dB of true-peak headroom because AAC or other lossy encoders can create inter-sample overs. Broadcast and platform contracts may require a different ceiling. Measure after the limiter. For the mechanics behind inter-sample overs, see [true peak explained](https://soundforgepro.com/true-peak-explained/?ref=davinciresolveclub.com). ## Should You Normalize Audio on Export? Resolve’s Deliver page offers two different operations. Normalize to Standard scales toward the chosen standard until either the loudness or peak constraint governs. Optimize to Standard can optimize loudness while keeping peaks below the selected threshold. Neither is a substitute for mixing: delivery processing can't decide that one interview is buried under music, repair a clipped bus, or preserve the intended drama of every scene. 1. Measure and save the final mix first. 2. Select the correct bus and channel format on Deliver. 3. Choose Normalize to Standard or Optimize to Standard deliberately, and select the exact standard only when the delivery requires or benefits from it. 4. Check what happens when the requested gain would violate the true-peak ceiling. 5. Render a test file. 6. Reimport that file, route it directly to a clean measurement bus, reset, and measure it again. Our [DaVinci Resolve audio export guide](https://davinciresolveclub.com/export-audio-davinci-resolve/) covers bus selection, mono/stereo layout, WAV versus AAC, and reimport verification in detail. ## Resolve Free vs Studio The core Fairlight mixer, bus routing, standard loudness monitoring, and audio rendering workflow are available in Resolve Free. Studio adds advanced features and immersive formats, but buying Studio doesn't choose the correct loudness specification or mix the program for you. Exact standards, presets, effects, and labels can change by Resolve release. This article targets Resolve 21; verify the installed point release and the current client document before final QC. ## Troubleshooting Audio Levels and LUFS ### Integrated LUFS never settles It will keep updating as new material plays. Reset at the true program start and play the complete range once. Do not loop a loud section and expect a program value. ### Dialogue meets LUFS but is hard to understand LUFS doesn't diagnose masking, noise, reverb, poor articulation, or spectral imbalance. Lower competing music, automate phrases, and repair the dialogue before changing the master target. ### The Main bus clips although tracks look safe Tracks sum at buses. Check subgroup gain, parallel sends, makeup gain, and Main processing. Fix the earliest overloaded stage instead of placing a limiter after accidental clipping. ### The exported file measures differently Confirm the Deliver page rendered the intended bus, channel count, timeline range, and Normalize/Optimize setting. A different bus or per-output normalization choice changes the measurement, and lossy encoding can alter true peak. Reimport and measure the rendered file through a clean path instead of trusting only the live timeline meter. ### Music is loud enough but masks every word Volume is only part of masking. Automate the music under speech and reduce competing midrange selectively. Do not keep boosting dialogue until the Main bus runs out of headroom. ## Final Audio QC Checklist - Listen through the complete program at a repeatable monitor level. - Check dialogue on speakers, headphones, and a small mono-compatible device. - Verify clip, track, subgroup, and Main stages do not clip. - Reset and measure the exact delivery range. - Record integrated loudness and maximum true peak. - Compare those numbers with the current destination specification. - Render the actual bus and channel layout. - Reimport and remeasure the file after encoding. - Check sync, start, tail, fades, channel order, and unexpected silence. The meter proves compliance with a measurement. Your ears prove that dialogue is clear, music supports the scene, and dynamics still make sense. A finished mix needs both. The [Fairlight Audio in DaVinci Resolve hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) places loudness measurement after routing, dialogue processing, and mix decisions, not before them. ## DaVinci Resolve Audio Levels and LUFS FAQ ### What is LUFS? LUFS is a K-weighted loudness measurement relative to digital full scale. Integrated LUFS summarizes the measured program; short-term and momentary views show local changes. ### Is LUFS the same as dBFS peak level? No. Peak readings show signal headroom; LUFS estimates perceived loudness across time. A mix can pass one limit and fail the other. ### What LUFS should I use for YouTube? YouTube does not publish a universal -14 LUFS creator-upload requirement in its public formatting guidance. Use a sensible web master with true-peak headroom, avoid destructive loudness chasing, upload privately or unlisted, and verify playback. ### What is the EBU R128 loudness target? EBU R128 specifies -23 LUFS program loudness. Current delivery documents can also define tolerance, true peak, and Loudness Range requirements. ### Should I normalize audio on export? Only after the mix is balanced and you understand the selected standard. Render normalization can shift overall level, but it can't repair dialogue masking, bad routing, or excessive dynamics. ### Why does LUFS change after export? The rendered bus, channel layout, range, normalization, and codec may differ from the monitoring path. Reimport the actual file and measure it through a clean bus. ### Can DaVinci Resolve Free measure LUFS? Yes. The core Fairlight loudness-monitoring workflow is available in Resolve Free. Confirm the exact standards and controls in your installed Resolve 21 build. ### Fix GPU Memory Full in DaVinci Resolve URL: https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/ Last updated: 2026-09-04T23:51:02.000Z When Resolve reports “GPU memory is full,” it means the requested GPU allocation failed; it doesn't prove that every byte of VRAM is occupied. The cause may be genuine capacity pressure, one extreme frame or node, the wrong selected adapter, or a [driver, compute-API, display, or offload fault](https://davinciresolveclub.com/davinci-resolve-keeps-crashing/). This guide isolates that specific message. If Resolve has a different symptom, begin with the [symptom-first Resolve troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/) instead of applying GPU fixes blindly. ![Resolve 21 Viewer controls for Proxy Handling and bypassing Color grades and Fusion effects](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/gpu-memory-isolate-operation-v2.webp) Isolate the expensive operation with the real Proxy Handling and Bypass Color Grades and Fusion controls. ## First, classify the failure | What happens | Most likely area | First useful test | | -------------------------------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Only one frame or clip fails | Source media, huge still, transition, node, or effect | Bypass that clip’s Color and Fusion processing | | Playback works but Deliver fails | Full-resolution processing, render-only setting, or cache difference | Render five seconds around the first failing frame | | Every project fails immediately | Driver, processing API, selected GPU, hybrid graphics, or unsupported configuration | Open a new empty project and verify Memory and GPU preferences | | The error starts after one effect | Temporal or AI memory demand | Disable only that effect and retest the same frame | | The error follows a Resolve or driver update | Version compatibility or changed GPU selection | Check Blackmagic’s current notes and the selected adapter before rolling back | Don't begin by deleting cache folders or reinstalling Resolve. Record the exact timeline, frame, page, operation, Resolve build, operating system, GPU model, VRAM or unified-memory amount, driver version, timeline resolution, and source resolution. A screenshot of the full error and the node/effect state is more useful than the sentence “it happens randomly.” ## Protect the project before troubleshooting 1. Save the project. 2. Duplicate the project or export a project backup. 3. Duplicate the failing timeline when you need to disable nodes, remove effects, or render in place. 4. Keep source media untouched. A cache cleanup is never permission to delete camera originals, graphics, or project libraries. If project libraries and backups are unfamiliar, read [where DaVinci Resolve projects are stored](https://davinciresolveclub.com/where-davinci-resolve-projects-saved/) before changing folders. For an application update or rollback, follow the [safe Resolve update workflow](https://davinciresolveclub.com/update-davinci-resolve-safely/); project-library compatibility matters more than getting through one launch. ## Find the clip, node, or effect that crosses the limit Duplicate the timeline and place a short In/Out range around the first failing frame. Disable one processing family at a time: - temporal and spatial noise reduction; - Speed Warp, optical-flow retiming, motion estimation, and frame interpolation; - Super Scale and other high-resolution transforms; - Magic Mask, Depth Map, object removal, relighting, and other AI analysis; - large blurs, defocus, glow, film grain, and third-party OpenFX; - Fusion compositions, especially deep branches and large Loader images; - stacked Adjustment Clips processing the same range. Re-enable items one by one on the same short range. The goal isn't merely to make the popup disappear; it is to identify the smallest change that makes the failure return. The number of Color nodes alone is a poor measure, one temporal effect can demand more memory than many simple correctors. For AI features, the [Magic Mask guide](https://davinciresolveclub.com/davinci-resolve-magic-mask/) shows how to limit analysis and repair only the necessary section. If a long Adjustment Clip carries a heavy effect across many shots, use the [Adjustment Clip scope guide](https://davinciresolveclub.com/adjustment-clips-davinci-resolve/) to shorten or split it instead of disabling unrelated work. ## Reduce GPU memory demand without damaging the edit ### Lower Timeline Proxy Resolution Choose **Playback > Timeline Proxy Resolution** and test Half, then Quarter. The final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) describes this as a lower working timeline resolution; it's reversible and doesn't rewrite the source clips. If the lower working resolution succeeds, the failure is resolution-dependent; it doesn't prove the full-resolution delivery will succeed. Keep a short final-resolution render in the test loop. If the project only stutters without the allocation message, use the [slow-playback workflow](https://davinciresolveclub.com/davinci-resolve-slow-playback/) rather than treating every performance problem as exhausted VRAM. ![Resolve 21 playback status and Viewer controls with the Timeline Proxy Resolution Half and Quarter workflow](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/timeline-proxy-resolution-ui-v3.webp) Use Playback > Timeline Proxy Resolution to lower working resolution; test the required final resolution before delivery. ### Use proxy or optimized media for difficult codecs [Proxy media and optimized media](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) can reduce decode pressure and improve playback, especially with highly compressed H.264 or H.265 camera formats. They do not guarantee that every Color or Fusion effect will run at proxy resolution. Verify the result rather than assuming a lightweight proxy removes all GPU demand. ### Reduce oversized stills and Fusion inputs A very large PNG, TIFF, EXR, or layered graphic can consume more memory than the timeline suggests. Resize a *copy* to the largest resolution the shot actually needs and preserve the master file. In Fusion, keep the working canvas and branches only as large as the output requires. Complex tracking and 3D scenes can also expand memory use. The [Fusion tracking guide](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/) helps choose a 2D or planar solution when a full 3D camera solve is unnecessary. ### Reduce temporal history Temporal noise reduction, optical flow, and AI tools need information from multiple frames. Reduce the temporal radius or frames, lower the quality mode, or process the demanding clip separately. Compare the lighter setting against the original at the delivery resolution before accepting it. ### Cache or render the proven bottleneck Once the expensive operation is proven, cache that node or clip, or use **Render in Place** to create a suitable intermediate. This trades repeated live GPU work for disk storage and a rendered file. Preserve an untouched timeline, or use **Decompose to Original** to return the rendered clip to its source and effects before later changes. ## What clearing cache can and cannot fix Render cache lives on storage; VRAM lives on or is allocated to the GPU. Deleting cache doesn't increase the GPU’s physical memory. It can help when cached frames are stale, corrupt, or built under settings that no longer match the timeline, but it shouldn't be the first response to every GPU allocation error. Use Resolve’s **Playback, then Delete Render Cache** controls and target Selected Clips or the smallest relevant scope. Confirm the project cache location before touching files outside Resolve. Never delete a broad folder because its name contains “cache” unless you've verified what owns it. Restarting Resolve is different: it can release allocations and reset a failed GPU context. If a restart fixes the problem temporarily but the same action recreates it, continue isolating the operation or driver fault. ## Check Memory and GPU preferences Open **DaVinci Resolve, then Preferences, then System, then Memory and GPU**. On supported Windows and Linux configurations, confirm that Resolve sees the intended discrete GPU, the processing mode is appropriate for the installed driver, and an integrated GPU isn't being selected for compute by mistake. Depending on platform, hardware and build, the processing API may be Automatic, CUDA, OpenCL or Metal; don't force a mode copied from a guide for another system. Checked September 5, 2026, the Memory and GPU page in the [final Resolve 21 manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) describes the application memory limit as system RAM. It isn't hidden extra VRAM, and raising it can't enlarge a discrete card’s physical GPU memory. Apple silicon uses shared unified memory, so its diagnosis is different and is covered below. Automatic selection is normally sensible, but hybrid laptops and mixed-GPU desktops deserve verification. After changing GPU selection or processing mode, save preferences and restart Resolve before testing the same project. ![Resolve 21 Memory and GPU preferences with Auto processing, selected GPU, and system RAM callouts](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/gpu-memory-preferences-v2.webp) Memory Configuration limits system RAM, not extra VRAM; verify Auto processing and the intended GPU before forcing a mode. Don't blindly disable integrated graphics in firmware or Device Manager. On many laptops it drives the display and power-management path. Prefer the operating system’s per-application high-performance GPU setting and the laptop vendor’s supported hybrid/discrete mode. ## Use a supported driver, not a random driver Start with the exact Resolve build and platform notes on Blackmagic’s [official support page](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com). If those notes name a minimum driver or a known issue, follow that boundary. For NVIDIA, choose a compatible package from the [official driver page](https://www.nvidia.com/en-us/drivers/?ref=davinciresolveclub.com); the Studio branch is one vendor-supported option for creative applications, not a universal cure. For AMD, use the appropriate package from [AMD Support](https://www.amd.com/en/support/download/drivers.html?ref=davinciresolveclub.com). Don't copy a driver prescription from another operating system, GPU generation, or Resolve point release. The newest driver isn't automatically the best match for every Resolve point release, and an old “known good” driver isn't safe forever. Change one variable, restart, and retest the same frame. Keep the installer and version record for rollback. ## Windows, macOS, and Linux differences ### Windows Verify the discrete GPU in both Resolve and Windows Graphics settings, then confirm the installed vendor driver. Hybrid laptops can launch Resolve on the low-power adapter even when a discrete GPU is present. ### macOS and Apple silicon Apple silicon uses unified memory rather than a separate user-visible VRAM pool. The same error can still reflect an allocation limit. Close other GPU-heavy apps, reduce working resolution and temporal effects, and verify that the macOS and Resolve versions are compatible. Adding system RAM later is not possible on current integrated Apple silicon machines, so project design matters. ### Linux Driver, compute API, display server, and hybrid-GPU configuration can matter as much as nominal VRAM. A current [Resolve 21 Linux case](https://www.reddit.com/r/davinciresolve/comments/1vbx2ti/davinci%5Fresolve%5Fout%5Fof%5Fgpu%5Fmemory/?ref=davinciresolveclub.com) reported the error with low apparent usage and traced it to the Wayland/X11 and NVIDIA offload stack. Treat that as directional evidence, not a command recipe: distributions and GPU setups differ, so use documented settings for your exact system. ## Do not assume multiple GPUs combine their memory Two 8 GB cards don't become one 16 GB memory space for an individual operation. Resolve can distribute processing across supported GPUs while the frames and resources needed by an operation still have to fit the active configuration. Don't add the capacities together when sizing a job; test the exact Blackmagic-supported configuration for the platform, and compare stability with the weaker processing GPU excluded. ## Playback works, but export fails A final render can exercise a different resolution, cache, codec, or effect path from timeline playback, and temporal processing may need neighboring frames. Find the first failing frame from the progress point or log and render a very short range around it. If the failure isn't the GPU-memory message, follow the broader [DaVinci Resolve render-failed diagnosis](https://davinciresolveclub.com/davinci-resolve-render-failed/) so codec, destination, media, and frame-specific errors stay in scope. 1. Disable the suspected effect and rerun the short range. 2. Restore it with a lighter temporal or quality setting. 3. Cache or render in place only the confirmed bottleneck. 4. Render the same short range at final resolution. 5. Reopen the file and check the transition into and out of the processed section. Don't lower the final deliverable below the specification just to make the queue finish. If the approved effect genuinely exceeds the hardware at final resolution, render an intermediate on a suitable system or redesign that specific operation. ![Resolve 21 Render in Place dialog annotated for intermediate format, included processing, and final-output retest](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-in-place-ui-v3.webp) Render only the proven bottleneck, retest final output, and use Decompose to Original when the clip needs to be editable again. ## When a GPU upgrade is actually justified Consider more VRAM only after all of these are true: - the failure is repeatable at the required final resolution; - Resolve selects the intended supported GPU; - the driver and Resolve build are known compatible; - the source file is valid and not absurdly oversized for the shot; - the expensive effect is necessary and can't be cached or rendered separately; - lower working resolution proves that memory capacity is the deciding variable. System RAM can help decode, Fusion, and overall stability, but it doesn't turn a discrete card’s fixed VRAM into a larger pool. [Before buying hardware](https://davinciresolveclub.com/davinci-resolve-hardware-compatibility/), compare the project’s resolution, codecs, effects, and Fusion workload with the [current Resolve system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). Once the allocation error is stable, return to the [DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/) and test editing, Fusion, Color, Fairlight, and delivery as separate stages. Keep the [troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/) for symptoms that no longer reproduce as this specific GPU-memory message. ## GPU Memory Full FAQ ### What causes “GPU memory is full” in DaVinci Resolve? Resolve can't complete a GPU allocation. High resolution, temporal effects, Fusion, AI tools, oversized stills, a wrong selected adapter, or a driver/API problem can all cause the message. ### Will clearing render cache fix GPU memory errors? Only when the cached data is stale or corrupt. Cache is stored on disk and deleting it doesn't increase physical VRAM. Restarting Resolve can release allocations, but a recurring failure still needs diagnosis. ### Should I lower the timeline resolution? Yes, as a reversible diagnostic and editing workaround. Always repeat a short render at the required final resolution because the memory demand can return during delivery. ### Why does the error appear when VRAM monitoring shows free memory? A utilization graph may not expose every resource or the failed request, and the GPU or driver context may be at fault. Reproduce the same frame after a restart and in a new empty project. If the empty project also fails, investigate GPU selection, the processing API, driver, and display or offload configuration before assuming capacity. ### Can more system RAM fix GPU memory full? It can improve system and Fusion headroom, and it contributes to the unified pool on Apple silicon, but it doesn't increase fixed VRAM on a discrete GPU. ### Does Resolve Studio use less GPU memory than Resolve Free? Not as a general rule. Studio unlocks additional accelerated and AI tools that may increase demand. Codec acceleration can improve performance on supported hardware, but the project’s processing chain still determines memory use. ### DaVinci Resolve Inspector: Core Controls Explained URL: https://davinciresolveclub.com/davinci-resolve-inspector/ Last updated: 2026-09-04T23:42:31.000Z The Inspector is contextual: it shows properties for the selected clip, title, transition, generator, subtitle, or applied effect, not one universal panel for the project. If it looks blank or a control disappears, first confirm the selected timeline item and tab; then check whether the panel is too narrow or a template, plug-in, or Resolve build is involved. ![DaVinci Resolve Edit page with the Inspector button and Video, Audio, Effects, Transition, Image, and File tabs](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-inspector-tabs.webp) Open Inspector at the top right, then choose the tab that matches the selected item. Resolve grays out tabs that do not apply to the current selection. ## What the Inspector Controls | Selected item | Inspector shows | Use it for | | ------------------ | ----------------------------------------------- | ------------------------------------------------------- | | Video clip | Video, Audio, Effects, Image/File when relevant | Framing, clip sound, applied effects, source properties | | Audio-only clip | Audio and File | Clip volume, pan, pitch, EQ, metadata | | Title or generator | Custom text/design controls plus settings | Content, font, layout, animation | | Transition | Transition controls | Duration, alignment, style-specific parameters | | OpenFX effect | Effects controls | Effect strength, masks, blend, animation | | Fusion composition | Published controls | Parameters intentionally exposed from Fusion | The Inspector changes a timeline instance. Project Settings define timeline-wide behavior; the Color page stores node-based corrections; Fairlight handles track and bus processing; Fusion owns its node graph. Keeping those scopes separate is the fastest way to diagnose a clip that looks or sounds different from its Inspector values. The [official Edit page](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) describes Inspector animation, Dynamic Zoom, stabilization, lens correction, titles, transitions, and picture-in-picture workflows. Checked September 5, 2026, the exact panel behavior and control definitions used here come from the final [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). ## Open the Inspector and Select the Right Item 1. Go to the Edit or Cut page. 2. Click the clip, transition, title, or effect you actually want to change. 3. Click **Inspector** at the upper right. 4. Read the Inspector header and confirm it matches the selected timeline item. 5. Open the tab that owns the setting: Video, Audio, Effects, Transition, Image, or File. A Media Pool source and a timeline instance are different scopes. Changes made to the Media Pool source are carried into future edits of that source; changes made to an instance already in the timeline stay independent and don't rewrite the Media Pool settings. For animation in a cut, select the timeline instance. With stacked tracks, click the exact upper or lower clip rather than trusting only what is visible in the Viewer. ## Video Inspector: Transform **Transform** controls where the picture sits inside the timeline frame: - **Zoom X/Y:** scales width and height. Keep the chain linked for normal proportional scaling; unlink it only for deliberate distortion. - **Position X/Y:** moves the image horizontally or vertically. - **Rotation Angle:** rotates the clip around its anchor point. - **Anchor Point X/Y:** moves the pivot used by rotation and scale without simply repositioning the visible image. - **Pitch and Yaw:** create perspective-like tilts around horizontal and vertical axes. - **Flip:** mirrors the image horizontally or vertically. For a normal reframe, start with Zoom and Position. Move Anchor Point only when the motion needs a different pivot, for example, a graphic swinging from one corner. The [aspect-ratio guide](https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/) shows how these controls work inside a vertical or square timeline. ![DaVinci Resolve Video Inspector Transform panel with Zoom, Position, Rotation, Anchor Point, Pitch, Yaw, keyframes, and reset controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-inspector-transform.webp) The Video Inspector keeps the everyday Transform controls together. Use the diamond beside a parameter to animate it and the circular arrow to reset only that control. ## Cropping Cropping removes pixels from the left, right, top, or bottom of the visible clip. A negative **Softness** value feathers inside the crop box; a positive value feathers outside it. With **Retain Image Position** enabled, the crop stays locked when you resize with Transform. Disable it when the crop should scale and move with the image. Crop and Zoom solve different problems. Crop hides an edge; Zoom changes the scale of everything. For a split screen, crop each layer and use Position to place it. For a simple reframe, start with Transform alone. ## Dynamic Zoom Dynamic Zoom creates a start-to-end push, pull, or pan without manually setting several Transform keyframes. Turn it on, enable the Dynamic Zoom overlay in the Viewer, and adjust the green start frame and red end frame. Swap them to reverse the move and choose an easing style in the Inspector. Do not run Dynamic Zoom and manual Zoom/Position keyframes on the same clip unless you intend to combine both. If the framing feels impossible to predict, disable one system and rebuild the move with a single method. ## Composite **Composite Mode** defines how the selected clip combines with tracks below it. Normal is the standard opaque layer; modes such as Screen, Multiply, or Add produce different mathematical blends. **Opacity** controls how much of the selected clip contributes to the result. Composite controls matter only when something exists underneath the clip. If changing the mode appears to do nothing, inspect track order, disabled tracks, and whether the lower layer contains visible pixels at that frame. ## Speed Change, Stabilization, and Lens Correction **Speed Change** handles a constant clip-speed adjustment, reverse playback, and related timing behavior. For a variable speed ramp, open Retime Controls and the curve editor instead of forcing the whole job through one percentage field. The shortcuts in the [Resolve keyboard guide](https://davinciresolveclub.com/davinci-resolve-keyboard-shortcuts-guide/) make it faster to open retime controls and inspect the timeline. **Stabilization** analyzes camera motion and attempts to smooth or lock the shot. Its mode and controls cover camera lock, zoom, crop ratio, smoothing, and strength. Start with moderate settings, click Stabilize, then watch the edges and subject motion. Stronger isn't automatically better; warping and aggressive crops can look worse than the original shake. **Lens Correction** is Studio-only. Analyze examines edges in the frame at the current playhead position and moves the Distortion control automatically; Distortion lets you adjust or back off that warp manually. It isn't a camera-profile lookup, so don't diagnose a missing control as a missing lens profile. ## Retime and Scaling This section controls how Resolve creates frames and how mismatched media fits the timeline: - **Retime Process:** chooses how new frames are produced, such as nearest frame, frame blend, or optical flow. - **Motion Estimation:** chooses the optical-flow analysis mode when optical flow is active. - **Scaling:** can fit, crop, stretch, or use the project setting for this individual clip. - **Resize Filter:** chooses the resampling filter used when the image is resized. These per-clip options can override the project’s general mismatch rule. That's useful for one awkward source, but it also explains why one clip has bars while every other clip fills the frame. With Optical Flow, compare the result on the actual shot: the most expensive motion-estimation mode isn't automatically the cleanest. Speed Warp is Studio-only, and AI Speed Warp Metal is macOS-only. ## Super Scale and Source-Specific Controls Super Scale is Studio-only source processing, not a per-instance Zoom. It increases the processed source resolution, is processor-intensive, and changing it affects every additional edit that references the selected media. Cache or optimized media can make the workflow practical, but a compressed or out-of-focus source still has limited real detail. RAW clips and certain image formats can expose additional controls under Image or File. Those panels depend on the source codec, so a phone H.264 clip, a Blackmagic RAW clip, a still image, and a Fusion composition shouldn't be expected to show identical Inspector sections. ## Audio, Effects, Transition, Image, and File Tabs The **Audio** tab changes the selected clip’s sound: typically clip volume, pan, pitch, and equalizer controls. This is not the Fairlight Mixer. If you want the same compressor or EQ across an entire dialogue track or bus, use Fairlight; the [Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) separates clip, track, and bus processing. The **Effects** tab is not an effects browser. It shows controls for Fusion, OpenFX, or audio effects already assigned to the selection and is dimmed when none apply. Parameters, keyframes, blend options, and resets depend on the applied effect. The **Transition** tab appears when the transition at an edit point is selected. It can contain duration, alignment, easing, border, or style-specific options. The **Image** and **File** tabs expose source-dependent image controls, RAW decoding where applicable, clip metadata, and file properties. Blackmagic’s [official Cut page](https://www.blackmagicdesign.com/products/davinciresolve/cut?ref=davinciresolveclub.com) explicitly describes Effects as the place for applied-effect options and File as the place for metadata and RAW controls. ![DaVinci Resolve Audio Inspector with Volume, Pan, Voice Isolation, Dialogue Leveler, Pitch, Speed Change, and Equalizer controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-audio-inspector.webp) Select an audio clip to expose clip-level Volume, Pan, Pitch, Speed Change and Equalizer controls. Voice Isolation and Dialogue Leveler appear only when the installed Resolve edition and selected clip support them. ## Titles, Generators, and Fusion Controls Select a Text title and the Inspector changes to text content, font, size, color, alignment, spacing, layout, and animation controls. Text+ and Fusion title templates expose the controls their creator published, so two title templates can look completely different. The [Resolve text guide](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/) covers the distinction between Text and Text+. A Fusion composition can expose a compact set of published controls in the Edit Inspector while the full node settings remain on the Fusion page. Resolve 21 also adds a **Multi-Inspector inside Fusion**: when several Fusion tools are selected, it can combine properties common to those tools. Blackmagic spells out that feature in the [final Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). It isn't the same thing as the normal Edit-page Inspector. ## Animate Inspector Controls with Keyframes 1. Move the playhead to the first frame where the animation should be defined. 2. Click the gray diamond beside the property. At a stored keyframe on the playhead it's orange; the left and right arrows jump to earlier or later keyframes. 3. Move to a later frame. 4. Change the value; Resolve adds another keyframe. 5. Open the clip’s keyframe or curve editor to move points and adjust easing. ![DaVinci Resolve 21 Edit page creating two Position keyframes from the Inspector and timeline lane](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/create-two-keyframes.webp) Define the first value, move the playhead, then change the same parameter. The orange Inspector diamond marks the keyframe under the playhead. A gray diamond means there's no keyframe for that parameter at the playhead; orange means the playhead is on a keyframe. Keyframes can still exist elsewhere in the clip, so use the previous/next arrows or open the timeline Keyframe and Curve Editor before retyping a value that changes as you scrub. ## Copy, Paste, and Reset Without Collateral Damage Use **Copy, then Paste Attributes** when you want to transfer only Transform, Crop, Composite, audio, or selected effects. Read every checkbox before applying it. A careless paste can copy speed, stabilization, or audio changes along with the framing you wanted. Each Inspector section has a reset arrow. Reset the smallest scope that is wrong: one property if available, then a group, and only then the entire clip. If the result still doesn't return to normal, another system is involved, Color sizing, a Fusion node, an adjustment clip, a higher video layer, or project scaling. An [adjustment clip](https://davinciresolveclub.com/adjustment-clips-davinci-resolve/) deliberately affects everything visible below it, so inspect upper tracks before blaming the selected source clip. ## Resolve Free vs Studio Core Inspector tabs, Transform, Crop, Dynamic Zoom, Composite, clip audio, standard keyframes, common stabilization, and per-clip scaling are available in Resolve Free. Confirmed Studio-only examples in this panel include Lens Correction, Super Scale, Speed Warp, and individual Studio effects or AI tools. The safe rule is contextual: the Inspector itself isn't a paid feature, but some tools displayed inside it are. If a control adds a Studio watermark or is unavailable, check the current feature list for that specific effect instead of assuming the whole panel is locked. ## Fix Inspector Problems ### The Inspector is blank Click Inspector at the upper right, then select a compatible timeline item. If a Media Pool source is selected, click its edited instance in the timeline. On a narrow or full-screen laptop layout, widen the Inspector or leave full screen so controls at the right edge aren't merely cropped out. ### A tab or control is missing Select the object that owns it. Effects requires an already-applied effect, Transition requires a selected transition, and RAW controls require compatible media. If the correct item and tab are selected but a template or plug-in panel is still blank, record the Resolve build, edition, item type, and package version; treat it as a version/template-specific defect rather than inventing a universal reset fix. ### The image jumps later in the clip A keyframe may exist away from the current playhead. Use the previous/next arrows, then open the Keyframe or Curve Editor and inspect every animated property. ### Reset does not restore the image Bypass upper video tracks, adjustment clips, Color sizing, Fusion, and project/timeline scaling one layer at a time. The Inspector can reset only the controls it owns. ### Changes affect the wrong clip Verify the timeline outline and Inspector header before adjusting values. This is especially important with linked audio/video and stacked tracks. ### A clip is soft after scaling Check Zoom, per-clip Scaling, timeline resolution, output resolution, and source dimensions. Stacked resizing can magnify a low-resolution source more than the Inspector value suggests. ![DaVinci Resolve 21 Keyframe Editor lanes compared with Curve Editor timing and value graph](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/keyframe-vs-curve-editor.webp) Use lanes to move diamond markers earlier or later. Use the Curve Editor when the vertical value, interpolation or acceleration also needs attention. ## Inspector Check Before Export Scrub from the first frame of the clip to the last while watching the Viewer and gray/orange keyframe states. Expand Transform, Crop, Composite, Speed, Stabilization, Retime and Scaling, and Effects, then compare the clip with effects bypassed. For audio, confirm whether the decision belongs to the clip or should live on its Fairlight track. The Inspector stays readable when each system has one job. If Transform, Color sizing, Fusion, and output scaling all correct the same frame, simplify the chain before adding another adjustment. For a clean node-versus-Inspector division, use the [beginner Color-page workflow](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/). The Inspector is an early stop in the [DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/), before adjustment clips, reframing, tracking, and delivery. ## DaVinci Resolve Inspector FAQ ### Why is my Inspector empty? No compatible timeline item is selected, the panel is closed, or you selected a source instead of its timeline instance. Select the clip, title, transition, or effect again. ### How do I reset one Inspector setting? Click the circular reset arrow beside that property or section. Reset the smallest scope first so unrelated work remains intact. ### What does the diamond icon do? It enables animation and stores a keyframe at the current playhead position. Move to another frame and change the value to create motion over time. ### Why does the Inspector look different for every clip? It's contextual. Video, audio, titles, transitions, generators, RAW media, Fusion compositions, and effects expose different properties. ### Can I copy Inspector settings to another clip? Yes. Use Paste Attributes and select only the categories you need. Review the target clip afterward for unwanted speed, audio, crop, or effect changes. ### Is the Inspector available in Resolve Free? Yes. The core Inspector is included in Resolve Free. Individual Studio-only effects, AI tools, or advanced processing modes remain restricted. ### DaVinci Resolve Magic Mask: Resolve 21 Guide URL: https://davinciresolveclub.com/davinci-resolve-magic-mask/ Last updated: 2026-09-04T23:33:42.000Z Magic Mask 2 is Studio-only. To isolate a person or object in DaVinci Resolve 21, start on a clear frame, add a dedicated Color node, place one positive click inside the subject, track forward and backward, then inspect the complete black-and-white matte. At the first failure, return to the last good frame and move the tracked click to a better feature before adding guidance. Add or subtract a click only when the mask needs different guidance; use Paint only for a few frame-local repairs because Paint doesn't track. The tracking button is not the finish line. A Magic Mask that looks convincing on one paused frame can leak into the background, drop a hand behind an occlusion or pulse around hair during playback. Resolve 21 adds a useful final step, rendering the finished mask in place as an external matte, so a verified track can stop being recalculated every time the project changes. ![DaVinci Resolve 21 Magic Mask 2 palette annotated with click tools, tracking, Click List, Smart Refine, and matte finesse controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/magic-mask-2-interface-overview-v2.webp) The current palette separates selection clicks, tracking history, Better-mode Smart Refine, and post-mask finesse controls. ## Use Magic Mask Only When the Outline Justifies It | Isolation method | Use it for | Main limitation | | ------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------- | | Magic Mask 2 | People, body regions, products, vehicles, animals and irregular subjects | Hair, repetitive surfaces, motion blur and occlusion still require review | | Magic Mask 2 Paint repair | A small include/exclude correction on a specific frame | Frame-local cleanup is not a substitute for a sound tracked selection | | Tracked Power Window | Faces, signs and objects that fit a simple geometric window | The outline does not deform around complex limbs or hair | | Fusion Polygon or roto | A deterministic matte that must survive difficult occlusion | More manual keyframes and edge work | A tracked window is usually the better tool for a circular face blur or a rectangular screen. Magic Mask earns the extra processing when the edge changes shape and a simple window would include too much background. If the final job is anonymization rather than grading, the [face and background blur workflow](https://davinciresolveclub.com/blur-face-background-davinci-resolve/) covers tracking, Mosaic Blur and privacy checks. Magic Mask 2 is Studio-only, as Blackmagic’s [Resolve Studio feature page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) and the final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) confirm. Version 2 removed separate Person/Object modes and replaced core selection strokes with Add/Subtract clicks; Paint is a frame-local repair tool. Resolve Free still offers Power Windows, qualifiers, conventional tracking, and Fusion masks. ## Prepare the Shot Before the First Click Set the intended edit, speed, and source before final approval. A trim or retime changes the analyzed range or source-frame timing and therefore requires inspection of the affected range; retrack only when the matte no longer follows. A source replacement also requires a fresh full-range check rather than an automatic assumption that the mask is invalid or valid. Put the isolation on its own serial node. Name it **Magic Mask** or **Subject Matte**. A dedicated node makes three later decisions obvious: whether the mask is enabled, which correction it controls and which node must be rendered or rebuilt. Choose a reference frame where the subject is visible, reasonably sharp and not crossing an object with similar color or texture. The middle of the shot is often better than the first frame because it may show more of the subject. Do not begin on a frame dominated by motion blur just because the playhead happens to be there. ## Track a Person or Object in Magic Mask 1. Open the clip on the **Color** page and add a separate serial node. 2. Open the **Magic Mask 2** palette. Do not look for the old Person/Object switch; version 2 recognizes either type from the clicks you place. 3. Park on the strongest reference frame and place one positive add click inside a distinctive part of the subject. 4. Inspect the initial overlay. If it includes a background object, place a subtract click on that object rather than clicking around the entire background. 5. Use the **Click List** to identify or delete a prompt instead of adding another click blindly. 6. Track forward to the end of the clip and backward to the beginning. 7. Switch to the black-and-white mask view and scrub the complete analyzed range. 8. Stop at the first failed frame, return to the last good frame, and first drag the tracked click to a better feature. Add or subtract guidance only when the matte semantics require it; use Paint only for a few frame-local repairs. Then track away from the corrected frame. 9. Only after the track is stable, refine the edge and render or cache the result. ![DaVinci Resolve Magic Mask 2 viewer with blue include clicks, red exclude clicks, and the current Click List](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/magic-mask-2-add-subtract-clicks-v2.webp) Blue clicks identify what belongs in the mask; red clicks reject specific look-alike regions. Move a poor click before adding more guidance. More clicks aren't automatically more precise. Several prompts on the same subject can describe conflicting regions and make later diagnosis harder. One well-placed add click on a distinctive area is the better first test. Add a subtract click or another local prompt only where the matte proves that it needs more. ## Repair the First Bad Frame, Not the Last Obvious One When a matte drifts, the visible disaster may occur several frames after the model first lost the edge. Scrub backward until you find the first frame where a hand thins, a sleeve disappears or background texture enters the subject. Correct there and track forward again. At an occlusion, back up to the last frame where the tracked click still follows a useful feature and drag that click to a better position before tracking again. After the subject reappears, reposition the tracked click again if needed. Add or subtract another click only when the mask needs different semantic guidance; reserve Paint for a few stubborn frames because Paint doesn't track. ![Magic Mask 2 Click List and Overall Track bar annotated for forward and reverse tracking from a clear reference frame](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/magic-mask-2-tracking-click-list-v2.webp) Start on a clear reference frame, track both directions, and repair the first bad frame by moving the responsible click at the last good frame. If the subject repeatedly crosses foreground objects, combine tools. Let Magic Mask describe the subject and use an additional Power Window or Key Mixer logic to exclude the occluder. For more controlled hand-built isolation, the [Fusion rotoscoping guide](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/) covers multiple shapes, keyframe spacing and occlusion layers. ## Refine the Matte in the Right Order Finish tracking before pushing matte-finesse controls. Clean Black and Clean White can remove small background specks or fill small holes, but aggressive values also erase semi-transparent hair, motion blur and fabric detail. Blur Radius can blend a hard edge; it can't recover an arm the track lost. Quality offers **Faster** and **Better**. Faster creates a lower-quality mask more quickly and is useful for garbage-matte work; Better preserves more detail at higher processing cost. In Better mode, Smart Refine expands or contracts the generated mask from image analysis before the matte-finesse pass. Consistency adds temporal smoothing only after a click has duration across multiple tracked frames. Raise it cautiously and watch for edge lag or lost detail. ![DaVinci Resolve 21 Subtract Paint tool removing silver rings from a Magic Mask on one frame](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/magic-mask-2-paint-frame-repair-v2.webp) Paint repairs the current frame only. Use a small add or subtract brush for short local misses, then inspect adjacent frames independently. Use this order: 1. At the last good frame, move the tracked click to a better feature and retrack. Add/subtract clicks only when different guidance is needed; use a small Paint correction only for a few frame-local misses. 2. Use Clean Black for isolated contamination outside the subject. 3. Use Clean White for small holes inside a stable matte. 4. Adjust In/Out Ratio only when the edge is consistently too far inside or outside. 5. Add the minimum Blur Radius that blends the correction at delivery resolution. Check the finished correction as well as the matte. A technically clean silhouette can still look cut out when exposure, saturation or sharpness changes too abruptly at the boundary. ## Grade the Subject and Background Separately Use the Magic Mask node for the subject correction, then create an outside node or an inverted key for the background. Keep the corrections separate. This makes it possible to soften the background, reduce its saturation or guide attention with exposure without changing the subject node. Don't stack an aggressive subject grade, noise reduction and a heavy background effect before the mask is proven. Bypass the corrections and inspect the matte first. Once the isolation is stable, add the creative work one node at a time. If the node structure is unfamiliar, the [Resolve nodes guide](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) explains serial, parallel and outside-node decisions. ## Render Magic Mask in Place in Resolve 21 Resolve 21 can render Magic Mask 2 as an external matte. In the Magic Mask palette, open the three-dot options menu and choose **Render in Place Magic Mask**, then select a location for the cached matte frames. Resolve creates a separate external matte node that can feed later corrections or effects. Checked September 5, 2026, the final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) documents the exact three-dot-menu command: Render in Place Magic Mask. The rendered frames become an external alpha source for downstream nodes, preserving the approved result until the source, timing, matte, render location, or rendered frames themselves need to be updated. The [Resolve 21 AI tools guide](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/) provides the wider Neural Engine context without replacing this shot-level workflow. Render only after checking the complete matte; a rendered error is still an error. Keep the original Magic Mask setup until approval, choose a deliberate render location, and include the external matte frames in the project handoff or archive. A DRP alone doesn't package source media or arbitrary external files, so verify the receiving system rather than assuming transient cache or matte media will travel. ![DaVinci Resolve 21 Render in Place Magic Mask menu and the resulting external matte node](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/magic-mask-2-render-in-place-v2.webp) After the full track passes review, Render in Place Magic Mask writes cached frames and creates an external matte node for downstream work. ## Keep Magic Mask from Taking Over the GPU Magic Mask, temporal noise reduction, Depth Map and heavy Fusion work all compete for GPU memory and processing time. Track the mask before adding the most expensive downstream nodes. Use a lower working timeline resolution when necessary, but inspect the final matte at full resolution before approval. If playback slows after a good track, render the mask in place or cache the specific result instead of repeatedly clearing unrelated cache. When Resolve reports a capacity error rather than ordinary slow playback, follow the [GPU memory troubleshooting sequence](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/) to isolate the failing node or clip. ## Common Magic Mask Failures ### The mask selects part of the background Remove unnecessary prompts. Start with one add click on a distinctive subject region, then place one subtract click on the specific background object that leaks into the matte. ### A hand or leg disappears Return to the last good frame and first move the tracked click onto a feature that remains identifiable. Retrack and inspect. Add a local positive click only if the matte still lacks subject guidance; use Paint for a few frame-specific patches. Clean White can't reconstruct a large missing limb reliably. ### Hair flickers during playback Inspect at full resolution, reduce aggressive cleanup and add only a small amount of edge blur. If hair crosses a similar background, accept that some frames need new guidance or a manual auxiliary mask. ### The track is lost after trimming or retiming A trim or retime may change the analyzed range or the source frames seen at each timeline position. Inspect the complete affected range first; retrack if the matte no longer follows. Set timing before final approval, then render or cache the verified result and retest after any later editorial change. ### Resolve keeps recalculating the mask Confirm whether source media, clip timing, upstream processing, matte guidance, or rendered frames changed. After approval, Render in Place Magic Mask lets downstream work read an external matte rather than repeatedly evaluating the live AI track; update that rendered matte when an upstream dependency changes. ## Review the Matte Like an Editor, Not a Screenshot Play the shot at normal speed, then pause on the fastest movement, the deepest motion blur and every occlusion. Check both the black-and-white matte and the finished correction. Look for pulsing edges, background color changes, holes inside the subject and one-frame flashes at the beginning or end. A strong Magic Mask uses the fewest clicks needed to describe the target, survives the complete shot and has an explicit handoff plan. The goal isn't to make the overlay look impressive on the reference frame; it's to make the correction invisible during playback. The [DaVinci Resolve color-grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/) places this mask in the node workflow. For deterministic manual isolation when repair cost becomes unreasonable, switch to the [Fusion rotoscoping workflow](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/). Compare edition-dependent tools in the [Resolve Free versus Studio breakdown](https://davinciresolveclub.com/davinci-resolve-vs-studio/). ## DaVinci Resolve Magic Mask FAQ ### Is Magic Mask available in DaVinci Resolve Free? No. Magic Mask is a DaVinci Resolve Studio feature. Free users can isolate subjects with Power Windows, qualifiers, Fusion masks and conventional trackers. ### Does Magic Mask 2 still have Person and Object modes? No. Magic Mask 2 removed the separate Person and Object modes. Place an add click inside the person, feature or object you need; use a subtract click or Paint repair only where the generated matte needs correction. ### Why does Magic Mask lose the subject? Return to the last good frame and first move the tracked click to a better feature. Add or subtract a click only when the mask needs different guidance, and use Paint only for a few frame-local repairs. ### Can I grade inside and outside the same Magic Mask? Yes. Use the matte for the subject node and an outside node or inverted key for the background. Separate nodes keep the two corrections easy to bypass and tune. ### Does Magic Mask work on a retimed clip? It can. Retiming changes which source frames appear when, so inspect the complete affected range and retrack it if the matte no longer follows. Set the speed before final approval, then render or cache the verified result. ### What changed for Magic Mask in DaVinci Resolve 21? Resolve 21 adds Render in Place Magic Mask, which creates an external matte node and cached matte frames for reuse after the track has been verified. ### DaVinci Resolve Keyboard Shortcuts That Save Time URL: https://davinciresolveclub.com/davinci-resolve-keyboard-shortcuts-guide/ Last updated: 2026-09-12T14:18:23.000Z The best shortcut is the one that removes a mouse trip you make dozens of times a day. Start with a deliberately small map: transport under one hand, a few editing actions, markers, and timeline navigation. Learn the command name as well as the key, because the active preset, operating system, keyboard layout, page, and focused panel can all change what a physical key does. The annotated Edit page below groups the starter commands by task; the table that follows gives the Windows and macOS defaults. ![DaVinci Resolve 21 Edit page annotated with J K L playback, I O range, A B T edit modes, and Split Clip commands](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-shortcut-starter-map-real-ui-v2.webp) Use the commands in context: J/K/L for playback, I/O for the active range, A/B/T for edit modes, and Split Clip at the playhead without changing pointer mode. ## Essential DaVinci Resolve 21 Shortcuts The table below assumes the default DaVinci Resolve keyboard preset. On compact Mac keyboards, the key labeled Delete behaves like Backspace; the forward-delete variant may require Fn. If a key differs on your machine, search the command name rather than forcing the printed combination. Interactive reference ### Search 40 editing commands Type a command, filter by task, or show one operating system. Default keys are listed where specified; Ripple Delete and Keyboard Customization use verification or menu guidance. Check your installed preset before a destructive edit. [Download printable PDF](https://davinciresolveclub.com/content/files/2026/09/davinci-resolve-21-1-keyboard-shortcuts-cheat-sheet.pdf) Search DaVinci Resolve shortcuts BothWindowsmacOS AllPlaybackEditTrimNavigationProject 40 commands shownDefault Resolve preset | Action | Windows | macOS | What it does | | ----------------------------------------------- | -------------------- | -------------------- | -------------------------------------------------------------------------- | | Play reversePlayback | J | J | Shuttle backward; repeated presses increase speed | | StopPlayback | K | K | Stop shuttle playback | | Play forwardPlayback | L | L | Shuttle forward; repeated presses increase speed | | Mark InPlayback | I | I | Set the start of a source, timeline, or render range | | Mark OutPlayback | O | O | Set the end of a source, timeline, or render range | | Selection ModeEdit | A | A | Return to the normal selection pointer | | Blade Edit ModeEdit | B | B | Turn the pointer into a click-to-cut blade | | Trim Edit ModeTrim | T | T | Work with ripple, roll, slip, and slide trims | | Split Clip at playheadEdit | Ctrl + \\ | Cmd + \\ | Add a cut without changing pointer mode | | Toggle snappingNavigation | N | N | Turn timeline snapping off or on | | Add markerNavigation | M | M | Add the current marker at the playhead | | Fit timeline in windowNavigation | Shift + Z | Shift + Z | Show the complete timeline; press again to restore zoom | | Previous edit or clipNavigation | Up Arrow | Up Arrow | Move to the previous edit or clip | | Next edit or clipNavigation | Down Arrow | Down Arrow | Move to the next edit or clip | | Nudge left 1 frameTrim | , | , | Move the selected clip or edit one frame left | | Nudge right 1 frameTrim | . | . | Move the selected clip or edit one frame right | | Fast nudge left 5 framesTrim | Shift + , | Shift + , | Move left by the default fast-nudge amount | | Fast nudge right 5 framesTrim | Shift + . | Shift + . | Move right by the default fast-nudge amount | | Extend edit to playheadTrim | E | E | Move the selected edit point to the playhead | | Trim start to playheadTrim | Shift + \[ | Shift + \[ | Trim the clip start at the playhead | | Trim end to playheadTrim | Shift + \] | Shift + \] | Trim the clip end at the playhead | | Enable or disable clipEdit | D | D | Toggle the selected clip without deleting it | | Toggle linked selectionEdit | Ctrl + Shift + L | Cmd + Shift + L | Change whether linked picture and sound select together | | Select clips forward on current trackNavigation | Y | Y | Select later clips on the targeted track | | Select clips forward on all tracksNavigation | Alt + Y | Option + Y | Select later clips across tracks | | Ripple cut selectionEdit | Ctrl + Shift + X | Cmd + Shift + X | Cut the selection to the clipboard and close the gap | | Ripple DeleteEdit | Verify active preset | Verify active preset | Delete and close time; physical Delete labels and emulation maps vary | | Insert editEdit | F9 | F9 | Insert source material and move later timeline content | | Overwrite editEdit | F10 | F10 | Replace timeline material without moving later content | | Replace editEdit | F11 | F11 | Replace by matching the source and timeline positions | | Place on topEdit | F12 | F12 | Place video above existing clips, or audio below, on the first empty track | | Fit to FillEdit | Shift + F11 | Shift + F11 | Retime the source range to fill the destination duration | | Append to endEdit | Shift + F12 | Shift + F12 | Add source material at the end of the timeline | | Save projectProject | Ctrl + S | Cmd + S | Save the current project | | UndoProject | Ctrl + Z | Cmd + Z | Reverse the last action | | RedoProject | Ctrl + Shift + Z | Cmd + Shift + Z | Restore the last undone action under the Resolve preset | | CutProject | Ctrl + X | Cmd + X | Cut the current selection | | CopyProject | Ctrl + C | Cmd + C | Copy the current selection | | PasteProject | Ctrl + V | Cmd + V | Paste at the active destination | | Keyboard CustomizationProject | Resolve menu | Resolve menu | Open the documented menu route and confirm the active map | Premiere Pro, Final Cut Pro, Avid, and custom presets can replace these assignments. Panel focus can also change what a key does. Confirm destructive commands in DaVinci Resolve > Keyboard Customization before using them on a live timeline. Blackmagic’s [official Edit page](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) explains the source/timeline and trimming model behind these commands, while the [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) supplies the current command tables and Keyboard Customization workflow. The shortcut name matters more than the printed keycap: Resolve, Premiere Pro, Final Cut Pro, Avid, and custom presets can assign the same physical key differently. ## Playback: Build J-K-L Muscle Memory First J plays backward, K stops, and L plays forward. Press J or L repeatedly to shuttle faster. Hold K and J together for slow backward playback, or K and L for slow forward playback. Keep K held and tap J or L to step one frame at a time. These controls act on the focused source or timeline viewer; Dynamic Trim Mode changes their job to trimming a selected edit. Add the left and right arrow keys for precise frame stepping. Don't scrub wildly with the mouse when you're trying to land on a single consonant, clap, or visual cut. Shuttle close, stop, then step frame by frame. ## Mark, Insert, and Overwrite Without Guessing `I` sets an In point and `O` sets an Out point. Use them in the Source Viewer to choose a shot before editing it into the timeline. Use them on the timeline to define a playback, render, or replace range. If Resolve exports only part of a sequence, stale In and Out marks are an early check; our [audio export guide](https://davinciresolveclub.com/export-audio-davinci-resolve/) shows the same range check on the Deliver page. The default professional edit keys are `F9` for Insert, `F10` for Overwrite, `F11` for Replace, and `F12` for Place on Top. Laptop function rows may require Fn or an operating-system setting. Beginners can still drag clips, but learning Insert and Overwrite makes track targeting and duration consequences visible. Our [Resolve beginner tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) covers the surrounding source-to-timeline workflow. ## Split Clip Is Not the Same as Blade Mode `Ctrl+\` on Windows or `Cmd+\` on macOS runs **Split Clip** at the playhead on selected clips and tracks governed by the current timeline targeting. `B` enters **Blade Edit Mode**, where every click can create a cut; `A` returns to Selection Mode. Blackmagic’s [official beginner training guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Beginners-Guide.pdf?ref=davinciresolveclub.com) gives the platform-specific backslash combinations, and the Resolve 21.1 manual lists Command-\\ in its Edit shortcut table. For one precise cut at the playhead, use Split Clip without changing pointer mode. Blade mode is useful for several cuts at visually chosen positions, but accidental edits multiply when the pointer remains a razor. The habit is simple: Ctrl+\\ or Cmd+\\ for the playhead cut; B for click-to-cut work; A as soon as the blade pass is finished. The complete selection, track-targeting, linked-audio, and Cut-page workflow lives in the [dedicated split-clip guide](https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/). When the task is to make a copy rather than a cut, use the separate [duplicate-clip workflow](https://davinciresolveclub.com/duplicate-clip-davinci-resolve/) so the original timing stays intact. ## Ripple Delete and Trim Commands Delete removes selected material and leaves a gap; Ripple Delete also closes the time it occupied. Distinguish the command from the keycap: the manual calls the ripple key Forward Delete, while compact Mac keyboards label the backspace key Delete. Confirm your assignment in Keyboard Customization. Check the selected clips or marked range, track locks, linked selection and Sync Locks before a ripple. Sync Locks determine which downstream tracks move. Timeline markers follow only when Timeline > Ripple Timeline Markers is enabled. For J/K/L trimming on the Edit page, select the edit point and press W, or choose Trim > Dynamic Trim Mode. Inspect the highlighted edge before pressing J or L: enabling this mode can automatically select the nearest edit. J and L trim the selection during playback; K stops. Press W again to leave Dynamic Trim Mode before reviewing the result. Resolve 21.1 enables Trim Edit Mode when you switch into Dynamic Trim. In older builds, use T for a ripple, roll, slip or slide trim; Selection Mode can resize or move instead. If you clear the selection while Dynamic Trim is active, J/K/L return to ordinary playback. The highlighted selection and mode, not the key alone, determine what changes. Audio often reveals a bad ripple before the picture does. After closing dialogue gaps, inspect waveforms and listen across the join. The workflow in our [Remove Silence guide](https://davinciresolveclub.com/remove-silence-davinci-resolve/) shows why pre-head, post-tail, and crossfades matter even when the delete itself is automatic. ## Timeline Navigation and View Shortcuts - **Shift+Z:** fit the complete timeline into the available window; press again to return to the previous zoom. - **Up/Down Arrow:** move between edit points, subject to active tracks and mapping. - **N:** toggle snapping when the playhead or an edit keeps jumping to nearby boundaries. - **M:** add a marker; press M again at that location to open its details. - **Cinema Viewer:** choose Workspace, Viewer Mode, Cinema Viewer, then search that command in Keyboard Customization before relying on a printed key; the manual shows different defaults in different page contexts. - **Shift+2 through Shift+8:** switch between Media, Cut, Edit, Fusion, Color, Fairlight, and Deliver pages under the standard Resolve map. Page shortcuts are especially useful on a single display. If you keep losing context between Edit and a parameter panel, our [Inspector guide](https://davinciresolveclub.com/davinci-resolve-inspector/) explains which controls belong to the selected clip and which belong to the timeline or project. ## How to Customize Shortcuts Without Breaking the Map ![DaVinci Resolve 21 Keyboard Customization window with preset, visual keyboard, command groups, and search field annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-keyboard-customization-overview-real-ui-v2.webp) Confirm the active preset first, then use the visual keyboard, command hierarchy, and search field to inspect the map installed on your system. 1. Choose DaVinci Resolve > Keyboard Customization and check the active preset. 2. From the options menu, choose Save As New Preset. Give your copy a descriptive name before changing the map. 3. Search for the command name. Choose the correct Application or Panels scope; similarly named commands can act in different places. 4. Select the proposed key on the visual keyboard and inspect its existing assignments. 5. Click the command’s Keystroke cell and press the replacement key combination. Use the plus button only if you need a second assignment for that command. 6. Resolve any conflict warning. Reassign or clear the competing command at the same scope instead of accepting an ambiguous map. 7. Click Save, then Close. 8. Reopen Keyboard Customization and use Export Preset in its options menu. Keep the dated export outside Resolve. 9. Test the changed commands on a duplicate timeline, including the panels and selections you actually use. Keep the previous preset until the new map behaves as expected. ![DaVinci Resolve Keyboard Customization search for Ripple commands with scope and keystroke columns annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-search-command-scope-real-ui-v2.webp) Search the command name, distinguish application and panel scope, and read the current keystroke before changing a mapping. The [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) documents the exact sequence: choose a starting mapping, use Save As New Preset, and manage Export Preset or Import Preset from the options menu. Before changing Resolve versions, also export a project checkpoint and follow our [safe update checklist](https://davinciresolveclub.com/update-davinci-resolve-safely/). ## Resolve, Premiere, Final Cut, or Avid Preset? If you're temporarily moving between applications, the familiar preset reduces friction. If Resolve is becoming your main editor, keep the old preset only long enough to stay productive, then add Resolve-specific commands deliberately. An imported Premiere layout can't make Resolve’s Trim Edit Mode, Color page, Fusion nodes, or Fairlight routing behave like Premiere. Shared rooms need a stricter rule: never overwrite the facility default. Load your named preset at the start, export changes at the end, and restore the house layout for the next editor. Include the preset file in the same workstation documentation as fonts, LUTs, plugins, and project-recovery notes. ## Free vs Studio and Resolve 21 Notes Keyboard Customization and the editing commands in this guide work in both DaVinci Resolve Free and Studio. A shortcut can still point to a Studio-only effect or AI command, but mapping the key doesn't unlock the feature. [Resolve 21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) say new user keyboard presets inherit updates to factory defaults. The manual recommends creating a new custom layout in 21.1 or later to use this behavior: later non-conflicting defaults can update without overwriting your custom assignments. Keep an exported backup. New multicam and track-selection commands may be assignable without having a factory key, so inspect the installed command list instead of guessing a combination. ## Why a DaVinci Resolve Shortcut Does Not Work ![DaVinci Resolve Keyboard Customization keystroke cell for remapping End to Playhead and adding a second assignment](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-remap-keystroke-real-ui-v2.webp) Select the keystroke cell, type the replacement, and use the plus control only when the command genuinely needs a second key combination. ### The shortcut does nothing Record the exact Resolve build, Free or Studio edition, operating system, and keyboard layout before changing anything. Click the panel where the command should act, because many commands are page-, mode-, and focus-sensitive. Then search the command in Keyboard Customization and check whether the active preset, macOS or Windows, an input method, screen recorder, or keyboard utility intercepts the same combination. ### The wrong command fires Select the key on the visual keyboard and inspect every listed assignment. Confirm the preset at the upper right. The same key can have application- and panel-specific actions, so a command that works on Edit may do something else, or nothing, when a text field, Media Pool, Viewer, Fusion panel, or Color page owns focus. ### Ripple Delete removes too much Undo immediately. Check selected clips, track auto-select controls, linked selection, and locked tracks. Ripple operations change time; a shortcut cannot decide which downstream sync relationships you intended to preserve. ### A shortcut types into a field instead Text entry has focus. Click the timeline or viewer, press Escape if appropriate, and try again. Don't keep hammering a destructive key while a rename or metadata box is active. ### The custom preset disappeared Confirm the current OS user, Resolve build, edition, and selected preset, then import the dated export. A temporary default preset can separate a broken custom map from a build, layout, or focus problem, but export the current map first and never overwrite the only working copy. If defaults also fail, capture a full UI screenshot and the exact command assignment before reporting a build-specific defect. ## A Seven-Day Shortcut Practice Plan - **Day 1:** J, K, L, arrows, I, and O. - **Day 2:** A, B, and Ctrl+\\ or Cmd+\\ for Split Clip. - **Day 3:** Delete versus Ripple Delete. - **Day 4:** T and edit-point navigation. - **Day 5:** M, N, and Shift+Z. - **Day 6:** Insert, Overwrite, and source/timeline focus. - **Day 7:** review the commands you still reach for with the mouse and map one new cluster. Keep the cheat sheet visible, but say the command name in your head rather than memorizing a colored key. That makes the skill survive a different keyboard, OS, or preset. Build the shortcut set around the actual tasks in our [DaVinci Resolve learning roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/), not around a memorized list of commands. ## DaVinci Resolve Keyboard Shortcuts FAQ ### How do I open Keyboard Customization? Choose **DaVinci Resolve, then Keyboard Customization.** That menu route is reliable across presets. If you use a remembered keyboard combination, verify it in the active preset and on your physical keyboard layout rather than assuming every installation maps it identically. ### What is the shortcut to cut a clip in DaVinci Resolve? Split Clip is Ctrl+\\ on Windows and Cmd+\\ on macOS under the default Resolve preset. B enters Blade Edit Mode for click-to-cut work; press A to return to Selection Mode. If the backslash combination does not fire, search Split Clip in Keyboard Customization and confirm the active preset and keyboard layout. ### What are J, K, and L in Resolve? J plays backward, K stops, and L plays forward. Repeated J or L presses increase shuttle speed. Hold K together with J or L for slow playback; hold K and tap J or L to step one frame. In Dynamic Trim Mode, these controls trim the selected edit instead. ### What is the difference between Delete and Ripple Delete? Delete removes selected material and leaves a gap. Ripple Delete closes that time and can move later material on tracks with Sync Locks enabled. Timeline markers move only when Timeline > Ripple Timeline Markers is enabled. Check the command assignment, selection, range and track state before deleting. ### Can I use Premiere Pro shortcuts in Resolve? Yes. Resolve includes presets that emulate other NLEs. Check every Resolve-specific trim, Color, Fusion, and Fairlight command because the applications don't map one-to-one. ### Can I export my DaVinci Resolve keyboard preset? Yes. Save the layout as a named preset, then use the Keyboard Customization options menu to export it. Keep a dated copy outside the application. ### Do keyboard shortcuts differ between Resolve Free and Studio? The core editing and customization shortcuts are the same. A mapped command for a Studio-only feature won't make that feature available in the free edition. ### DaVinci Resolve 21 AI Slate ID and Slate Finder URL: https://davinciresolveclub.com/davinci-resolve-slate-finder-slate-id/ Last updated: 2026-09-04T23:24:02.000Z The expensive mistake is treating Slate Finder and Slate ID as one automatic button. In current Resolve Studio 21, Finder adds a duration marker over the frames where it sees a readable board. Select that analyzed clip, click Slate ID in Metadata, choose which recognized fields to keep, then Save. Blackmagic lays out those as two separate operations in the [current Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). The software can shorten the logging pass; it can't decide whether a production-specific value is trustworthy. ![DaVinci Resolve 21 Media Pool context menu with AI Tools and Analyze for Slate selected](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-analyze-for-slate-menu.webp) Real DaVinci Resolve 21 interface captured by Resolve by Rocco in April 2026\. Select the camera clips in the Media Pool, then open AI Tools and choose Analyze for Slate; this is the Finder step, not the metadata approval step. Checked September 5, 2026, the UI screenshots in this guide were captured from [Resolve by Rocco’s April 2026 walkthrough](https://www.youtube.com/watch?v=DCUf2j4EtYs&ref=davinciresolveclub.com) and checked against Blackmagic’s [final Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com); they are real app captures, not manual page crops or generated imitations. That distinction matters because the April beta guide and several third-party tutorials show an older or incomplete sequence. ## Slate Finder vs Slate ID: What Each Tool Does | Operation | What it does | What you get | | ---------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------- | | **Slate Finder** | Finds frames where a readable slate is visible | A duration marker in the color selected in AI Clip Analysis | | **Slate ID** | Runs separately on a clip already analyzed by Slate Finder | A Slate Information window with recognized fields to accept or reject | | **Save** | Writes only enabled Slate Information rows | Selected clip metadata; rejected or incorrect values remain for manual entry | Slate Finder is the navigation step. Slate ID is the recognition-and-write step. A Finder marker doesn't mean that Scene, Take, Camera, Date, or any other field has been saved. Conversely, a plausible Slate ID result is still only a proposal until you enable that row and click Save. One version trap is worth calling out. Blackmagic’s April New Features Guide used a yellow duration marker and retained a beta warning. The final Reference Manual says the marker color is selectable and illustrates blue. Current instructions should therefore say “duration marker,” not promise yellow. Both tools are Studio-only in Resolve 21\. Resolve Free still provides the Metadata Editor, list view, Smart Bins, and manual metadata entry; it doesn't provide this Slate Finder/Slate ID analysis. The [Resolve 21 AI tools guide](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/) maps the same Free-versus-Studio boundary across the rest of the current AI feature set. ## Prepare the Media Pool Before You Analyze Run a representative trial before sending an entire shooting day through Finder. Start with ten clips: that is a manageable review sample, not a performance benchmark. Include different cameras, board layouts, interiors, exteriors, head slates, and tail slates so the trial exposes the production’s main failure patterns before you scale it. - Preserve camera, sound-roll, and script-supervisor metadata before running any bulk operation. - Group camera originals by shooting day and camera so the review set stays understandable. - Confirm source timecode and project frame rate before you start a separate audio-sync workflow. - Exclude audio-only files, graphics, and rolls that never contain a visible board. - Write down the house style: whether 12B is a scene variant, camera identifier, angle, or another field. - Choose a marker color that isn't already carrying another production meaning. If bins and ingest are still unsettled, finish the [DaVinci Resolve beginner workflow](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) first. Slate analysis belongs after the media has a stable home and before editorial starts depending on the metadata. ## Install the Slate AI Model 1. Confirm that the application is DaVinci Resolve Studio 21. 2. Open DaVinci Resolve > Extras Download Manager. 3. Download the AI model corresponding to Slate Finder and Slate ID. 4. Wait for the download and installation to complete, then return to the Media page. 5. For a shared facility, record the exact Resolve build and verify the Extra on every ingest workstation before production. The model download is an official prerequisite. The current manual doesn't say that a missing model must hide the command, so don't diagnose installation state from the menu alone. If the operation fails, verify the installed build and the Extra itself. ## Run Slate Finder and Choose the Marker Color 1. Go to the Media page and select the camera clips that contain visible boards. 2. Right-click one selected clip and choose AI Tools > Analyze for Slate. 3. Alternatively, open AI Clip Analysis at the top of the bin column, set the clip selection range, enable Analyze for Slate, and choose a marker color. 4. Start the analysis and wait for the Slate Finder progress box to finish. 5. Open each duration marker and confirm that the board is visible and readable in the marked interval. 6. Ignore a marker that points to a monitor image, rehearsal board, false start, or the wrong slate for the take. ![DaVinci Resolve 21 source viewer with a detected clapperboard and Detected Slate duration marker](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-detected-slate-marker.webp) Real Resolve 21 Slate Finder result captured by Resolve by Rocco. The viewer displays the clapperboard while the marker overlay identifies the Detected Slate range; inspect that range before trusting the next recognition step. A Finder marker isn't metadata and it isn't audio sync. It tells you where Resolve believes a readable slate appears. The next operation is per-clip metadata recognition and approval. ## Run Slate ID and Save Only Verified Fields The final manual documents Slate ID after Finder, not as part of the same click. It also describes the approval on a selected clip; don't assume that one approval safely writes an entire Finder batch. ![DaVinci Resolve 21 Metadata panel with the Slate ID button above the selected Media Pool clip](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-slate-id-metadata-icon.webp) Real Resolve 21 Metadata panel captured by Resolve by Rocco. After Slate Finder marks the board, select that clip and click the Slate ID button at the top of Metadata to start the separate recognition step. 1. Select one clip that has already been analyzed with Slate Finder. 2. Open Metadata and click the Slate ID icon at the top of the Metadata bar. 3. Wait for the separate Slate ID progress box. 4. In Slate Information, compare every AI Recognized value with the photographed board and the production record. 5. Disable the checkbox for any field that's wrong, ambiguous, or mapped to the wrong production concept. 6. Click Save to write only the enabled rows to clip metadata. 7. Correct rejected or incorrect values afterward in Metadata Editor; the Slate Information values aren't editable in that window. ## Review the Slate Information Window ![DaVinci Resolve 21 Slate Information window comparing AI Recognized slate fields with existing metadata](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-slate-information-window.webp) Real Resolve 21 Slate Information window captured by Resolve by Rocco. Compare every AI Recognized value with the photographed board and existing metadata, enable only the rows you have verified, then click Save. The recognized rows depend on the board and what the model can read. Blackmagic names Scene, Take, Shoot Day, and other information; the final-manual examples also show Date and Camera. Do not turn that list into a promise that every layout will produce every field. Use three plain review states so every handoff distinguishes AI-recognized values from human-approved metadata: - **Verified:** the photographed board and production record support the value and its destination field. - **Needs review:** a character is unclear or the show’s field convention is ambiguous. - **Manual:** the board is unreadable, absent, or laid out in a way that makes manual entry faster and safer. Use clip colors, flags, keywords, or a custom metadata field to keep those states visible. The exact device matters less than separating AI-recognized values from human-approved values. Blackmagic’s [Media page overview](https://www.blackmagicdesign.com/products/davinciresolve/media?ref=davinciresolveclub.com) shows how metadata and bins support the broader ingest workflow. ## Slate ID Does Not Sync Production Audio Slate Finder marks a visual interval and Slate ID writes selected metadata. Audio synchronization is a separate Resolve workflow using matching timecode, waveform comparison, In/Out points, markers, or manual alignment. A correct Scene and Take value cannot repair bad timecode, mismatched sample rates, or drift. **Critical metadata warning:** the current Reference Manual says Auto Sync Audio can make the video clip inherit metadata from the audio file when Retain Video Metadata is off, and off is the default. If the Slate ID values on the video clip must survive, enable Retain Video Metadata or verify that the sound metadata is the intended authority before syncing. After sync, spot-check the clap at the head and a later section for drift, then sort the Media Pool again. A successful sync doesn't prove that the desired metadata source won the merge. ## Where Slate ID Commonly Needs Manual Help ![DaVinci Resolve 21 Metadata panel populated with Scene 17B and Take 2 beside the photographed slate](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-populated-slate-metadata.webp) Real Resolve 21 post-save result captured by Resolve by Rocco. Scene 17B and Take 2 now appear in Metadata beside the visible board; use this side-by-side check to catch glare, handwriting, date, or field-mapping errors before the values drive bins or clip names. - **Glare:** a reflection erases thin marker strokes or part of a digit. - **Motion blur:** the board exists, but no frame is sharp enough for reliable reading. - **Tail slates:** the board may be inverted, brief, or close to the end of the clip. - **Multiple boards:** a rehearsal board, monitor image, false start, or second slate can create the wrong interval. - **Handwriting:** 1/7, 3/8, 5/6, B/8, and O/0 remain predictable recognition traps. - **House conventions:** the same letter can mean a scene variant, camera, angle, or shot depending on the production. - **Digital boards:** LED refresh and shutter timing can leave a field incomplete in an individual frame. Community evidence is mixed, which is exactly why the trial matters. In an April 2026 [Resolve slate-detection discussion](https://www.reddit.com/r/davinciresolve/comments/1smf1qe/how%5Fto%5Fuse%5Fthe%5Fnew%5Fai%5Fslate%5Fdetection%5Ffeature/?ref=davinciresolveclub.com), one professional dailies operator reported that a keyboard-driven manual workflow beat the beta model on an M3 Ultra. That's one operator’s beta-era result, not a universal benchmark for the shipping build. Measure your own error and review time. ## A Safer Batch Workflow for a Shooting Day 1. Export the existing metadata first: File > Export Metadata From > Media Pool or Selected Clips. Save CSV, or ALE when Avid compatibility is required. 2. Group the day by camera, board style, or another boundary that makes review manageable. 3. Run Slate Finder on ten representative clips and inspect every duration marker. 4. For each useful result, run Slate ID, reject doubtful rows, and Save only verified fields. 5. Record the error pattern: missed board, false board, wrong character, or wrong destination field. 6. If the trial saves time, expand Finder analysis in controlled batches while keeping Slate ID approval accountable per clip. 7. Sort by Scene, Take, Camera, Date, and Shoot Day to expose blanks, duplicates, impossible sequences, and inconsistent punctuation. 8. Before Auto Sync Audio, decide whether video or sound metadata is authoritative and set Retain Video Metadata accordingly. 9. Export the cleaned metadata again and create a DRP project checkpoint before renaming clips or handing the project off. If camera media goes offline during this work, stop and fix storage with the [Media Offline guide](https://davinciresolveclub.com/media-offline-davinci-resolve/). Reanalyzing relinked duplicates can produce a harder metadata problem than the original missing media. For the difference between Project Libraries, DRP files, archives, and recovery files, use the [Resolve project storage guide](https://davinciresolveclub.com/where-davinci-resolve-projects-saved/). ## Troubleshooting Slate Finder and Slate ID ### Analyze for Slate is missing Confirm Resolve Studio 21, install the corresponding model through Extras Download Manager, and verify the exact build in the About dialog. Menu placement for About varies by platform. Then compare your build with the current [Blackmagic support downloads and release notes](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com). ### The model download fails Check network access and free disk space, close Resolve cleanly, reopen it, and retry the official Extra. Don't install model files from an unofficial mirror. A June 2026 [Extras Download Manager failure thread](https://www.reddit.com/r/davinciresolve/comments/1txuln8/extras%5Fdownload%5Fmanager%5Fdownload%5Ffailed/?ref=davinciresolveclub.com) documents one Windows download failure and a separate extraction/rename error; it doesn't establish one universal cause or file path. If the failure repeats, use Help > Create Diagnostics Log on Desktop and report the exact build, OS, and failing Extra to Blackmagic support or the official forum. ### No slate is detected Open the clip and confirm that a board is actually visible and readable for more than a fleeting blurred frame. Try the single clip through Analyze for Slate. If the only board is distant, obscured, or unreadable to you, log it manually instead of repeating the same analysis. ### Slate Finder marks the wrong board Inspect the selected-color duration marker for a rehearsal board, monitor image, false start, or tail slate. A marker is a navigation aid, not permission to write metadata. Continue only with the production-approved board. ### Slate ID reads a value incorrectly Disable that row in Slate Information and Save only the fields you trust. The recognized values aren't editable in the Slate Information window; enter the corrected value afterward in Metadata Editor. ## Final Verification Before Editorial - Sort list view by the fields your production actually uses and scan for blanks, duplicates, and broken sequences. - Open at least one clip from every scene/camera group and compare saved metadata with the photographed board. - Confirm that rejected Slate Information rows didn't overwrite trusted camera or sound-report values. - If audio was synced, confirm the intended metadata source survived and spot-check head sync plus later drift. - Open the exported CSV or ALE and verify that the expected populated fields are present before handoff. The useful division of labor is simple: Finder narrows the search, Slate ID proposes fields, and the editor or assistant editor decides what becomes project metadata. That's faster than blind manual scrubbing without pretending the model is the production record. For the larger ingest-to-delivery sequence around these tools, use the [task-first DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/). ## DaVinci Resolve AI Slate ID FAQ ### Is Slate Finder available in DaVinci Resolve Free? No. The current Resolve 21 Reference Manual labels Slate Finder and Slate ID as Studio-only. Resolve Free users can still enter and organize clip metadata manually. ### What does AI Slate Finder detect? It finds the interval where a readable clapperboard appears and adds a duration marker. The marker color is selectable in AI Clip Analysis; it isn't permanently yellow. ### What does AI Slate ID read? After Slate Finder analysis, Slate ID can recognize fields such as Scene, Take, Shoot Day, Date, Camera, and other information present on the board. The available result depends on what it recognizes. ### Where is Analyze for Slate in Resolve 21? On the Media page, select clips and right-click one of them, then choose AI Tools and Analyze for Slate. You can also enable Analyze for Slate in AI Clip Analysis at the top of the bin column. ### How do I save Slate ID metadata? Select a clip already analyzed by Slate Finder, click the Slate ID icon in the Metadata pane, wait for Slate Information, enable only the fields you trust, and click Save. Correct rejected values later in Metadata Editor. ### Does Slate ID synchronize production audio? No. Slate detection, metadata extraction, and audio synchronization are separate operations. Use timecode, waveform, markers, or manual sync, and review Retain Video Metadata before Auto Sync Audio. ### Can Slate ID replace a script supervisor or dailies operator? No. It can shorten the search and transcription work on readable boards, but production conventions, continuity, ambiguous handwriting, and final metadata approval still require human judgment. ### How to Export Audio Only in DaVinci Resolve URL: https://davinciresolveclub.com/export-audio-davinci-resolve/ Last updated: 2026-09-04T23:10:52.000Z For one finished mix, open Deliver and start from the Audio Only preset or Custom Export. Confirm that Export Video is off and Export Audio is on, choose WAVE/Linear PCM, and select the actual stereo Main or Submix bus. 24-bit/48 kHz is common for video post, but the delivery specification wins. For dialogue, music, and effects stems, route those groups to separate Fairlight buses first and render every bus over the same timeline range. ![DaVinci Resolve Deliver page with Audio Only preset and Single clip selection annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-audio-only-preset-real-ui-v2.webp) Audio Only is a useful starting preset for one finished mix. Select Single clip, then verify every setting below instead of assuming the preset matches the delivery specification. ## Decide What You Are Delivering: One Mix or Stems Before touching the Deliver page, ask one question: should the recipient hear your finished mix, or should they be able to rebalance parts of it? | Deliverable | Choose in Resolve | What it contains | | ---------------------------------- | -------------------------- | ---------------------------------------------------------------------------------- | | Finished stereo mix | Main stereo bus | All tracks, automation, track processing, and bus processing routed into that bus | | Dialogue, music, and effects stems | Separate D, M, and E buses | Processed groups that can be recombined downstream | | Raw or lightly processed tracks | Individual timeline tracks | Each selected track, which may not include downstream bus processing | | Bounced clip or track | Fairlight bounce command | A rendered asset created during editing, not necessarily the final delivery master | Use the approved Main or Submix bus for approval files, podcasts, YouTube voiceovers, and final audio masters unless the handoff specification says otherwise. A timeline-track export isn't automatically a stem. If dialogue passes through a dialogue bus with EQ or compression, exporting the source track can produce a different result from the mix you approved. Blackmagic’s [Fairlight overview](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) explains the routing model. The final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) defines the Deliver Audio panel: Output Track can select a Main or Submix bus, the plus control adds more outputs to the same job, and All Timeline Tracks is a separate choice rather than a processed stereo mix. ## How to Export One Audio File from DaVinci Resolve 1. **Set the render range.** On the Deliver page, choose **Entire Timeline** unless you deliberately set In and Out points. Leave enough space for the last reverb or music tail. 2. **Choose Audio Only or Custom Export.** Audio Only is a quick starting preset; verify its format, bit depth, and Output Track. Custom Export exposes every setting for a manual setup. Give the file a useful name such as `project_mix_v03.wav` and choose a normal delivery folder, not a cache directory. 3. **Confirm that Export Video is disabled.** Audio Only does this automatically. In Custom Export, open the Video section and clear **Export Video**. If the deliverable must include picture, use the [video-export workflow](https://davinciresolveclub.com/export-video-davinci-resolve/) instead. 4. **Enable Export Audio.** In the Audio section, turn on **Export Audio**. 5. **Choose WAV and Linear PCM.** For a reliable master, select WAV, Linear PCM, 24-bit, and the project’s sample rate. In video post, that's normally 48 kHz. 6. **Select the real output bus.** In Output Track, choose the stereo Main or Submix bus that receives the approved mix. Use the project’s actual bus name; Resolve doesn't guarantee that every session calls it Bus 1. 7. **Keep channel-splitting options off for a normal stereo master.** Render one track per channel and Render as discrete audio tracks have different channel/interleaving behavior. Enable either only when the delivery specification requires that structure. 8. **Add and render.** Click **Add to Render Queue**, inspect the queued summary, then click **Render All**. If Bus 1 isn't your actual mix bus, stop here and fix the routing. Open the Fairlight mixer, play the timeline, and watch the bus meters. The bus you select for delivery must receive every track you expect to hear. The [Fairlight bus-routing guide](https://davinciresolveclub.com/fairlight-bus-routing/) shows the track-to-bus signal path without treating every track as an isolated output. ![DaVinci Resolve Audio export panel with Wave, Linear PCM, 48 kHz, and 24-bit annotated](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-wave-linear-pcm-real-ui-v2.webp) For one stereo master, enable Export Audio, choose Wave with Linear PCM, match the required sample rate and bit depth, and leave split-channel options off unless the handoff specification requests them. ## WAV, MP3, or AAC? **WAVE with Linear PCM is the safe default.** That combination stores uncompressed PCM audio, survives another edit or encode without adding lossy-compression damage, and makes channel count, sample rate, and bit depth explicit. A common video-post starting point is 24-bit, 48 kHz WAVE/Linear PCM unless a broadcaster, editor, or client supplies a different specification. **MP3 and AAC are listening-copy formats.** They're smaller and useful for review, but they should not replace an uncompressed master that will be edited, mixed, or encoded again. Checked September 5, 2026, the final Resolve 21 manual confirms that **AAC audio encoding is macOS-only**. Don't promise AAC from Windows or Linux, and don't infer availability from a screenshot made on another platform. Verify the options on the delivery machine. | Format | Use it for | Avoid it when | | ------------------------------ | ------------------------------------------------ | ---------------------------------------------- | | WAV / Linear PCM | Master, archive, editor handoff, stems | File size is the only concern | | MP3 | Small speech or music review copy | The file will be processed or encoded again | | AAC (macOS only in Resolve 21) | Compressed playback or a specified macOS handoff | The recipient asked for an uncompressed master | ## How to Export Dialogue, Music, and Effects Stems A stem is a deliberately routed group, not a synonym for every visible timeline track. A Dialogue bus can include the intended EQ, compression, automation, and level trim; a source-track export can omit downstream bus processing. Verify the actual route and insert state, because a bus export contains what reaches that selected output path, not whatever the editor meant to include. ![DaVinci Resolve Output Track menu selecting processed stereo buses for separate stem render jobs](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-processed-bus-stems-real-ui-v2.webp) A processed bus is selected in Output Track and added as its own render job. Repeat for each required stem without changing the timeline range, format, sample rate, or bit depth; All Timeline Tracks is a different output mode. 1. Create or identify the processed stem buses. Route dialogue to DX, music to MX, and effects to FX, using the channel format required by the handoff. 2. Verify the routes and processing. Watch each bus meter, check inserts and automation, and confirm the buses reach the approved monitoring path without double-counting. 3. Set one common start and end range. Every stem must begin at the same time and end after the same final tail, including stems that are silent at the head or tail. 4. Create one render job per standalone stem file. Select only the intended bus as Output Track, use a unique filename such as project\_DX\_v03.wav, and add the job to the queue. Repeat for MX and FX without changing range, sample rate, bit depth, or format. 5. Render and verify. Reimport all stems at the same start time, sum them at unity gain, and compare the result with the approved mix. For more complex sessions, set up the groups before the last day of the mix. Retrofitting buses at export time is how sends, sidechains, and bus plug-ins get missed. If dialogue dynamics are part of the approved sound, check the routing alongside the [dialogue compressor workflow](https://davinciresolveclub.com/fairlight-compressor-dialogue/). ## Bounce Is Not the Same as Deliver Fairlight bounce commands create working media during the edit. The [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) says Bounce Mix to Track processes a selected bus mix to a new or existing timeline track and writes new media to the Project Settings > Capture and Playback > Save clips to location. Deliver instead creates the controlled handoff job, range, filename, destination, and output assignment. Use Bounce Mix to Track when you need a reusable timeline asset; use Deliver when you need the final master or handoff. A successful bounce doesn't validate the Deliver range, selected output, channel layout, normalization, or destination. ## Check Loudness, Peaks, and the Render Range Don't turn on normalization just because the export sounds quiet. First measure the mix, identify the required loudness target, and adjust the mix intentionally. A web video, podcast, broadcast master, and cinema deliverable may have different requirements. The [Resolve loudness and LUFS guide](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/) explains what to measure before using any target-based normalization. - **Start:** confirm that the first transient or word isn't before the chosen In point. - **End:** listen past the last visible edit so reverb, room tone, and music decays aren't chopped. - **Peaks:** fix clipping in the mix. Saving the same clipped signal as WAV doesn't repair it. - **Channels:** confirm mono, stereo, or multichannel delivery against the specification. - **Version:** put the revision in the filename instead of overwriting an approved file with an ambiguous name such as `final.wav`. ## Resolve Free vs Studio The standard audio-only Deliver workflow, WAVE/Linear PCM export, Fairlight mixing, and ordinary bus routing are available in DaVinci Resolve Free. Specialized codecs and advanced workflows can vary by operating system, container, installed components, and edition. Don't use edition labels as a substitute for the actual Audio panel. Codec availability also depends on the operating system and selected format: Resolve 21 documents AAC encoding as macOS-only. WAVE/Linear PCM is the portable choice for a dependable audio-only master when the recipient hasn't supplied another specification. ## Fix Common Audio Export Problems ### The exported file is silent Confirm that Export Audio is enabled and that the selected bus meter moves during playback. Then check track mute, bus mute, automation, and routing. If the timeline itself is silent, start with the [Resolve no-audio checklist](https://davinciresolveclub.com/davinci-resolve-no-audio/) before changing render settings. ### The export contains only one track or misses music You probably selected a timeline track or a bus that doesn't receive the whole mix. Follow the signal from each source track through any subgroup bus to the output chosen on Deliver. Don't assume Bus 1 is the master in a project with custom routing. ### The WAV is mono instead of stereo Inspect both the bus format and Output Track selection. A mono bus produces a mono output even when the timeline contains many audio clips. Change the routing or create the required stereo bus; renaming the file will not change its channel layout. ### The render has separate tracks or channels instead of one stereo mix Return to Audio and select the intended stereo Main or Submix bus. Disable Render one track per channel and Render as discrete audio tracks unless the delivery specification requests that structure. Those switches change how channels are stored in compatible rendered media; they don't substitute for a processed stereo bus or guarantee one standalone WAV file per stem. ### The file ends too early Check the In/Out range and move the Out point after the full audio tail. Entire Timeline is safer for a normal master, but still listen through the last seconds because a muted or trimmed tail can still sound abrupt. ### The render is quieter or different from playback Make sure Deliver is using the same bus path you monitored and that its meter moves through the full range. A bus render includes only audio actually routed through that output, with its active insert and automation state. Timeline-track output can differ, and normalization in the render job can change level after the mix. ## A Two-Minute Verification After Every Export Open the exported file in a player outside Resolve and listen to the beginning, a loud section, a quiet section, and the ending. Check duration and channel count. For a client master or stems, reimport the files into a clean timeline, line them up at the same start time, and compare them with the approved mix. ![DaVinci Resolve File panel and Render Queue followed by finished WAV files opened outside Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-render-queue-verify-real-ui-v2.webp) Use a clear filename, inspect the queued job before rendering, then open the finished WAV outside Resolve to check duration, channel count, beginning, loudest passage, quiet passage, and ending. A green render-complete message proves only that Resolve wrote a file. It doesn't prove that you selected the correct bus, included the full range, preserved the channel layout, or delivered the version the recipient asked for. Once that verification passes, keep the WAV master and create a smaller listening copy only if somebody needs it. For the rest of the picture-and-sound handoff, use the [DaVinci Resolve export settings guide](https://davinciresolveclub.com/davinci-resolve-export-settings/). For the routing, dialogue, loudness, and bus work that comes before an audio master, continue through the [Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/). This page stays focused on audio-only files, buses, tracks, stems, and verification. ## DaVinci Resolve Audio Export FAQ ### What are the best settings for audio-only export? For a general video-post master, use WAV, Linear PCM, 24-bit, 48 kHz, and the main stereo bus. Follow a supplied delivery specification when it requires something different. ### How do I export one finished stereo mix? Turn off Export Video, turn on Export Audio, and choose the stereo bus that receives the complete approved mix. Keep individual-track and split-channel options disabled. ### Can DaVinci Resolve export separate audio stems? Yes. Route dialogue, music, and effects to separate processed buses, then create one named render job per bus with an identical start and end range, format, sample rate, and bit depth. Reimport and sum the files once to verify alignment and content. ### Why is my exported audio silent? The usual causes are Export Audio being off, the wrong output bus, a muted bus or track, automation, or source tracks that never reach the selected bus. ### Should I use 44.1 or 48 kHz? Match the project and delivery specification. Video post-production normally uses 48 kHz; some music-only workflows use 44.1 kHz. ### Does audio-only export work in Resolve Free? Yes. Resolve Free supports the standard audio-only workflow, WAV export, mixing, and ordinary bus routing. Specialized formats and advanced workflows can depend on Studio, the operating system, or additional components. ### Fairlight Bus Routing Explained URL: https://davinciresolveclub.com/fairlight-bus-routing/ Last updated: 2026-09-04T23:01:31.000Z For a simple DX/MX/FX house layout, one normal output per stage makes the route easy to audit: source track to its submix, then submix to Stereo. That's an editorial recommendation, not a FlexBus limit. Resolve supports multiple outputs and sends; the failure begins when parallel paths rejoin unintentionally, such as VO feeding both DX and Stereo while DX also feeds Stereo. ![DaVinci Resolve Fairlight Mixer with dialogue tracks routed to a Dialogue bus and other tracks routed to Bus 1](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fairlight-mixer-bus-outputs.webp) Real DaVinci Resolve Fairlight Mixer captured by JayAreTV in 2025\. The Bus Outputs row shows dialogue tracks feeding the Dialogue bus while music, effects, and voice-over follow their assigned paths; trace those labels before changing a fader or processor. ## The Fairlight signal flow in plain English A track contains clips. A bus sums the output of one or more tracks or other buses. That summed signal gets its own channel strip, so you can change the level, EQ, dynamics, plug-ins, panning, automation, and destination for the whole group. | Path | What it does | Use it when | | -------------------------------------------------- | --------------------------------------------------- | ---------------------------------------------------------------------------------------- | | Track, then Stereo | Sends the track directly to the final output bus | The timeline is small and you do not need group processing or stems | | Track, then DX/MX/FX, then Stereo | Routes related tracks through a controllable submix | You want one fader, shared processing, automation, or a deliverable stem for each family | | Track, then normal output plus Bus Send, then VERB | Creates a second, parallel path | You want reverb, delay, a cue mix, or another effect without replacing the dry route | Resolve 21 uses **FlexBus**. A bus role comes from what feeds it and where its output goes, rather than a permanent “main,” “submix,” or “aux” type. The final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) documents track-to-bus, bus-to-bus, bus-to-track, output, and send assignments; use those active paths as the source of truth. ## Build a clean DX, MX, and FX bus layout ### 1\. Name the source tracks before touching routing Rename generic tracks such as A1 and A2 by role: VO 1, Boom, Lav, Music, SFX, Ambience. A routing matrix full of anonymous track numbers is hard to diagnose later. If the dialogue is already edited, clean the clips first; our [Remove Silence guide](https://davinciresolveclub.com/remove-silence-davinci-resolve/) covers the fastest safe workflow. Check the track format as well. Most individual microphones belong on mono tracks. Music and many effects arrive as stereo. The bus format should match what the group needs to deliver, not merely the format of the first clip you see. ### 2\. Create and name the buses Open the Fairlight page and choose **Fairlight, then Bus Format**. Keep or rename the default stereo bus to **Stereo**, then add the submixes you actually need. A practical starting layout is DX, MX, and FX. Add VERB only if you need a shared parallel effect. - **Stereo:** final two-channel mix. - **DX:** dialogue and voice-over. Mono can be appropriate for a mono dialogue stem; stereo is also valid when your delivery or processing requires it. - **MX:** music, normally stereo. - **FX:** effects and ambience, normally stereo for web and standard stereo delivery. - **VERB:** stereo auxiliary return for reverb or delay. Don't copy those formats blindly into a surround or broadcast project. The delivery specification wins. Blackmagic also documents adaptive tracks for unusual channel layouts, but a normal YouTube or course video doesn't become better because its routing diagram is more complicated. ### 3\. Assign every source to one submix output You can assign routing in the Mixer or open **Fairlight, then Bus Assign**. In the Mixer, expose **Bus Outputs** from the Mixer Options menu if that section is hidden. Assign all dialogue tracks to DX, music tracks to MX, and effects tracks to FX. Bus assignments can be additive. After assigning a source to DX, inspect Bus Outputs or Bus Assign and remove a direct Stereo route only if both paths reach the same destination unintentionally. The recommended house path is **VO 1 > DX > Stereo**; a deliberate parallel route is valid when its purpose and destination are documented. ### 4\. Route the submix buses to Stereo Select the DX, MX, and FX bus channel strips and add Stereo in their Bus Outputs. Now play a section containing every category. The source-track meter should move, then its submix meter, then the Stereo meter. If one stage stops, the fault is immediately upstream of that meter. ## Bus Output vs Bus Send: the difference that prevents doubling A **Bus Output** is the normal destination. A **Bus Send** is an additional feed. That distinction matters more than the names on the buses. For shared reverb, keep VO 1’s normal output on DX. Add VERB under Bus Sends, place the reverb plug-in on the VERB bus, and route VERB to Stereo. Adjust the wet amount with the send level or the VERB bus fader. This preserves the dry dialogue path and adds the processed return in parallel. A post-fader send follows later moves to the source fader, which is usually sensible for reverb: lower the voice and its reverb falls with it. A pre-fader send remains independent of the source fader and is useful for specialized cue or monitoring feeds. Pick deliberately; neither mode is universally “more professional.” Shared processing that should affect the entire group belongs on the submix, not on an aux return. For example, use the [Fairlight dialogue EQ workflow](https://davinciresolveclub.com/fairlight-eq-dialogue/) and [dialogue compression guide](https://davinciresolveclub.com/fairlight-compressor-dialogue/) to shape DX. Use a send for reverb or delay that must sit beside the dry sound. ![DaVinci Resolve Fairlight Bus Assign and Bus Format windows with separate Send and Out assignments](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fairlight-flexbus-bus-assign.webp) Blackmagic Design's real Fairlight Bus Assign and Bus Format interface. Send and Out are separate assignments: use Out for the normal destination and add a Send only when the mix intentionally needs an additional feed. ## Verify the route before mixing Use three short tests before inserting more plug-ins. They reveal routing errors faster than staring at a large mixer. 1. **Meter test:** play one source at a time and follow its meters from track to submix to Stereo. 2. **Mute test:** mute DX. Every dialogue track should disappear, while music and effects remain. Repeat for MX and FX. 3. **Unity test:** bypass bus processing, set the relevant faders to unity, and compare the rebuilt route with the original. A sudden level jump often means a duplicate direct path is still active. 4. **Speaker/device test:** if track, submix, and Stereo meters all move but the speakers are silent, stop rebuilding buses. Check Bus Outputs, Control Room or monitor selection, Resolve audio I/O, the operating-system output device, and any required patching. Don't confuse routing, monitoring, and delivery. If the Stereo meter moves, the track-to-bus chain is passing signal. Silence after that point belongs to Bus Outputs, Control Room or monitor selection, Resolve's audio I/O/output-device configuration, operating-system audio, or patching. The monitoring choice also doesn't select the Deliver output. ## Export the full mix and stems on the Deliver page Open Deliver and choose an audio-capable preset or Audio Only. For lossless handoff, Wave with Linear PCM is a common choice; the required bit depth and channel layout still come from the client or platform specification. 1. Choose **Single Clip** so every output spans the same render range. 2. Under Audio, set **Output Track 1** to the final Stereo bus. 3. Use the plus button to add DX, MX, and FX as additional Output Tracks when stems are required. 4. Confirm each displayed format, Mono, Stereo, 5.1, or another layout, before queuing the render. 5. Render a short test, then reimport it into a blank timeline and check the start time, duration, channel count, and content. The Deliver page can output several buses in the same render job. That's different from choosing “All Timeline Tracks,” which prints timeline tracks rather than the processed submix structure. If the stem must contain the EQ, compression, automation, and other processing on DX, export the DX bus. Real broadcast deliveries can require empty channels, multiple language mixes, or a precise interleaved layout. A useful [community routing example for an eight-channel broadcast file](https://www.reddit.com/r/davinciresolve/comments/1ay2v1s/need%5Fhelp%5Fwith%5Foutputting%5Faudio%5Ftracks%5Ffor/?ref=davinciresolveclub.com) illustrates why the bus names, formats, Output Track order, and “Render one track per channel” choice must follow the delivery sheet rather than a generic preset. For a normal web upload, export the final Stereo bus and check its loudness after all submix processing. The targets and measurement workflow are covered in our [Fairlight LUFS and audio levels guide](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/). For codec and file settings, use the separate [DaVinci Resolve audio export guide](https://davinciresolveclub.com/export-audio-davinci-resolve/). ![DaVinci Resolve Fairlight Bounce Mix to Track window mapping printmaster and DX MX FX buses to stem tracks](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fairlight-bounce-mix-stems.webp) Real Fairlight Bounce Mix to Track window captured by Zoo Productions. Each named bus is mapped to a matching destination track, which makes processed printmaster, dialogue, music, and effects stems explicit before delivery. ## Fairlight bus routing troubleshooting ### The track meter moves, but the bus is silent Check the track’s Bus Outputs as well as its sends. Confirm the playhead is over an audible clip, the destination bus isn't muted, and the source fader or automation hasn't pulled the signal down. Then open Bus Assign in List view and verify the output abbreviation beside that track. ### The submix moves, but Stereo is silent If the submix meter moves but Stereo does not, inspect the submix Bus Output, fader, mute, automation, and Stereo mute state. If Stereo also moves but the speakers are silent, routing has passed the meter test: inspect Control Room or monitor selection, Bus Outputs, Resolve audio I/O, the OS output device, and patching instead of recreating the submix. ### The full mix is louder after adding submixes The source tracks probably still feed Stereo directly while also feeding submixes that feed Stereo. Remove the direct Stereo output from those source tracks. Don't fix a duplicated route by arbitrarily lowering the master fader; repair the signal flow. ### The stem is missing bus effects You exported timeline tracks or the wrong bus. Choose the processed DX, MX, or FX bus in Output Track. If an effect lives on a separate aux return, decide whether the delivery specification expects that return folded into the stem, delivered separately, or only present in the full mix. ### The export is mono when the mix should be stereo Inspect the format at every stage: source track, submix, final bus, and selected Output Track. One mono bus in the chain can collapse the result. Change formats intentionally in Bus Format and confirm the Deliver dropdown reports the expected channel layout. ## Does Fairlight bus routing require Resolve Studio? No. Standard FlexBus routing, buses, sends, channel mapping, mixer processing, and stereo stem workflows are available in DaVinci Resolve Free. Studio adds tools and formats that may matter for advanced immersive work, but you don't need Studio to build a clean DX/MX/FX mix. Checked September 5, 2026, this guide targets DaVinci Resolve 21\. The [current Fairlight overview](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) confirms the channel-strip processing model. Interface placement can shift, so use the documented names, Bus Format, Bus Assign, Bus Outputs, Bus Sends, Control Room, and Output Track, as anchors. ## A routing checklist I would trust at delivery - Every source track has a clear name and the intended mono, stereo, or multichannel format. - Every source has one normal output path unless duplication is deliberate and documented. - DX, MX, and FX reach the final Stereo bus. - Aux buses such as VERB also reach Stereo and contain only the intended parallel return. - Mute tests isolate exactly one family at a time. - The Stereo bus and every requested stem are selected explicitly under Deliver, then Output Tracks. - A rendered test has been reimported and checked outside the live routing session. Routing is the backbone of the [Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) and the broader [DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/). If every bus meter moves but no speaker output exists, use the [no-audio device and monitoring checklist](https://davinciresolveclub.com/davinci-resolve-no-audio/) before changing the routing graph. ## Fairlight bus routing FAQ ### What is a bus in DaVinci Resolve Fairlight? A bus is a signal path that sums one or more tracks or other buses into a new mixer channel. It lets you control, process, monitor, route, or export those sources as a group. ### Should every audio track go to its own bus? No. Create buses for useful groups and deliverables. Multiple dialogue tracks can share DX, music tracks can share MX, and effects can share FX. A tiny project may route tracks directly to Stereo. ### What is the difference between a bus output and a bus send? A Bus Output is the track’s normal destination. A Bus Send is an additional parallel feed with its own level and pre- or post-fader behavior. Sends are commonly used for shared reverb, delay, or cue mixes. ### Why does audio get louder after I route it to a submix? The source is often reaching Stereo twice: once directly and once through the submix. Remove the direct Stereo output from the source so it travels only through the intended submix. ### How do I export dialogue, music, and effects stems? Route those families to named DX, MX, and FX buses. On Deliver, use the plus button under Output Tracks to add each bus, verify its channel format, render the same range, and reimport the files for an alignment check. ### Can I route one Fairlight track to more than one bus? Yes. FlexBus supports multiple bus outputs and sends. Use them only when the design requires parallel paths, and trace every path to its destination; unintended routes that rejoin can raise level or bypass group processing. ### Fairlight Compressor Settings for Dialogue URL: https://davinciresolveclub.com/fairlight-compressor-dialogue/ Last updated: 2026-09-04T22:52:44.000Z Quick answer: fix large clip-gain differences before compression, then test the loud, normal, and quiet phrases. Blackmagic lays out 2.5:1–3:1 as commonly used dialogue ratios, but threshold must follow the actual input. Tune attack for intact consonants, release for smooth recovery, and use the post-Dynamics Makeup Gain only to match bypass. If room noise breathes or the processed version merely sounds louder, back off. ![DaVinci Resolve Studio 20 Fairlight Dynamics window with dialogue compressor controls and Mixer context](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve20-dialogue-compressor-real-ui.webp) Real DaVinci Resolve Studio 20 Fairlight interface captured by DETCH-UP WORLD in 2025\. The Compressor curve, threshold, ratio, timing, makeup gain, Mixer channel, and dialogue clip remain visible together; the shown values are one example, not a universal preset. ## What a Dialogue Compressor Does A compressor reduces gain when the signal crosses a threshold. Ratio controls how strongly it reduces the portion above that threshold; Attack and Release control when reduction begins and recovers. The resulting smaller dynamic range can keep loud words from jumping out and make softer words easier to place in the mix. It does *not* repair clipped audio, remove background noise, or know which whisper should remain quiet for the story. It also does not set LUFS by itself. Compression is one stage between editing and final measurement. Checked September 5, 2026, the final July 2026 [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) notes that every Mixer channel has built-in Dynamics with separate Expander/Gate, Compressor, and Limiter modules. Double-click the channel-strip Dynamics indicator to open the window; the graph maps input on the X axis, output on the Y axis, threshold as a blue line, and the active response as the green curve. Blackmagic’s [Fairlight Audio Guide](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveFairlightAudioPost.pdf?ref=davinciresolveclub.com) provides project media for learning the wider dialogue workflow. For version-sensitive controls and ranges, this article follows the final Resolve 21 manual above rather than a copied preset or an older tutorial screenshot. ## Clip Gain, Track Compression, or Bus Compression? | Stage | Use it for | Do not ask it to | | --------------------------- | ------------------------------------------------------------- | ----------------------------------------------------- | | **Clip gain / automation** | Large edit-to-edit jumps, one bad phrase, microphone changes | Automatically follow an entire performance | | **Track compressor** | Remaining dynamics from one consistent speaker and microphone | Reconcile unrelated rooms and recording chains | | **Dialogue bus compressor** | Very gentle cohesion after tracks are balanced | Repair one bad track without moving the others | | **Main limiter** | Catch final peaks against a delivery ceiling | Create a good dialogue mix from an unbalanced session | Move boom, lav, phone, ADR, and narrator recordings to sensible tracks before processing. If the signal path isn't obvious, follow our [Fairlight bus-routing guide](https://davinciresolveclub.com/fairlight-bus-routing/) before touching Main. ## Fairlight Compressor Controls - **Threshold:** the level where compression begins. Its useful value depends completely on the signal arriving at the track. - **Ratio:** how much the level above threshold is reduced. At 2:1, 2 dB above threshold becomes roughly 1 dB at the output before other controls. - **Attack:** how quickly gain reduction engages. Too fast can dull consonants; too slow can let a shout or plosive through. - **Hold:** how long reduction is held before release behavior takes over. It can keep the compressor from fluttering between closely spaced syllables. - **Release:** how quickly gain returns. Too short pumps; too long keeps the next phrase unnecessarily suppressed. - **Knee:** how gradually the compressor enters its ratio around threshold. A softer knee often makes ordinary dialogue control less obvious. - **Mix:** blends compressed signal at 0 with the original uncompressed input at 100\. The default is 0, meaning all compressed signal. Use it deliberately; don't mistake the scale direction for a conventional wet control. - **Makeup Gain:** a post-Dynamics level control shared by the module, not a compressor threshold target. It raises voice and noise together; use it to level-match bypass, not to win the comparison. - **Gain Reduction meter:** the amount the compressor is turning down at that moment. It helps diagnose behavior but doesn't judge sound quality. ![DaVinci Resolve Fairlight compressor panel with threshold, ratio, response, gain, and gain reduction meter](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fairlightfx-compressor-real-ui.webp) Real Fairlight compressor panel captured by FOG in 2024\. Threshold and ratio set the compression curve, Response changes how quickly it reacts, Gain restores output level, and the reduction meter shows when the processor is working. ## Set a Fairlight Compressor for Dialogue 1. **Level extreme clips manually.** Bring obviously mismatched lines near the track’s normal working level. Keep intentional whispers and shouts unless the brief says otherwise. 2. **Choose three test sections.** Loop normal speech, the loudest useful phrase, and a quiet phrase with room tone. 3. **Open Fairlight Dynamics.** Enable Compressor and temporarily bypass Gate, Expander, and Limiter so you hear one process. 4. **Start with a gentle ratio.** Blackmagic identifies 2.5:1–3:1 as commonly used for dialogue. Treat it as an audition range, not a preset; the recording and threshold still control how much compression occurs. 5. **Lower Threshold.** Stop when louder words show a few decibels of reduction while ordinary speech moves less. 6. **Set Attack.** Resolve 21 defaults to 1.4 ms and allows 0–100 ms. Start from the documented default, then lengthen only when consonants keep their edge and shorten when peaks still distract. The recording decides the value; this guide doesn't present an untested timing preset. 7. **Set Release.** Resolve 21 defaults to 93 ms and allows 50–4000 ms. Start from the documented default and follow the phrase rhythm: the response should recover smoothly rather than chatter or hold down the next line. This guide does not claim one universal speech-release range. 8. **Adjust Knee and Hold if needed.** Use a softer transition and enough stability to avoid syllable-by-syllable movement. 9. **Match Makeup.** Toggle bypass and match perceived loudness before deciding which version is better. 10. **Review the complete scene.** Check every microphone change, edit, breath, pause, and downstream bus. Attack, Release, and Threshold are source-dependent. The official ranges are wide, and threshold is especially non-portable because clip gain changes what reaches the detector. A current [editor discussion of long dialogue with sentence-by-sentence level changes](https://www.reddit.com/r/davinciresolve/comments/1rzv2j8/sometimes%5Fi%5Fhave%5Faudio%5Ffiles%5Flike%5Fthis%5Fone%5Fover/?ref=davinciresolveclub.com) points in the same practical direction: manual phrase gain before track compression is often cleaner than forcing very quiet lines through an extreme threshold. Community experience is directional; the manual controls the parameter facts. ## How Much Gain Reduction? For transparent ordinary dialogue, a few decibels on louder words is a useful place to begin. If gain reduction stays pinned through normal speech, ask whether the clip needs manual leveling or whether the threshold is too low. If only one peak triggers reduction, the compressor may be acting as a loose limiter rather than shaping the performance. Don't chase a fixed meter number. Listen for a stable sentence, intact consonants, believable room tone, and natural differences between emotion and distance. Then compare in the full mix. A 6 dB reduction can be correct on one shout and obvious on another. ## EQ, Isolation, Leveler, and Compression Order Use clip gain first. Remove low rumble or a strong resonance before compression so the unwanted energy doesn't drive gain reduction; our [dialogue EQ workflow](https://davinciresolveclub.com/fairlight-eq-dialogue/) explains that corrective stage. If Voice Isolation substantially changes the spectrum, use it conservatively before final EQ and dynamics. Dialogue Leveler already rides speech. Stacking aggressive Dialogue Leveler and aggressive compression commonly raises breaths and produces pumping. The [Voice Isolation vs Dialogue Leveler comparison](https://davinciresolveclub.com/voice-isolation-vs-dialogue-leveler/) helps decide whether you need separation, automatic leveling, conventional compression, or manual gain. ## When Automation Beats More Compression If a speaker leans away for one sentence, raise that clip or phrase. If one laugh is too loud, lower it. If music masks only three lines, automate the music. When music should move automatically under recurring speech, use the separate [Fairlight audio-ducking workflow](https://davinciresolveclub.com/davinci-resolve-audio-ducking/) instead of over-compressing the dialogue. Lowering Threshold until the dialogue compressor solves every exception usually flattens the normal material and lifts the noise floor. Automation also preserves story dynamics. A whisper can remain a whisper while still being intelligible; a shout can feel larger without clipping. The compressor then handles smaller performance variation instead of doing editorial triage. ## Dialogue Bus Compression and Limiting Once separate dialogue tracks already match, a dialogue-bus compressor can add gentle cohesion. Use a low ratio, little gain reduction, and slower behavior than an emergency clip repair. Bypass it on the whole scene, not one line, to confirm it improves continuity. A limiter on Main is a peak guardrail after the mix. It isn't a replacement for clip gain, track compression, or correct loudness. Resolve 21 describes it as a very-high-ratio ceiling controlled by Threshold, Attack, Hold, and Release; too much limiting can remove internal dynamics. Measure after every bus processor with our [LUFS and true-peak guide](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/). ## Free vs Studio The built-in Fairlight channel compressor is available in both DaVinci Resolve Free and Studio. Voice Isolation and some other AI repair tools require Studio, but ordinary clip gain, EQ, dynamics, routing, automation, and loudness monitoring don't. ## Troubleshooting Dialogue Compression ### Dialogue pumps between words Lengthen Release, add appropriate Hold, reduce Ratio or gain reduction, and check whether a Gate or downstream Limiter is creating the movement. ### Consonants sound dull Slow Attack or reduce compression. Listen at matched output level; the bypassed signal shouldn't lose simply because it's quieter. ### Room noise becomes louder Reduce Makeup and compressor workload. Compression narrows the difference between voice and noise; it can't separate them. Repair or automate the source first; the [Resolve background-noise guide](https://davinciresolveclub.com/remove-background-noise-davinci-resolve/) separates steady noise, hum, Voice Isolation, and manual cleanup before you push the compressor harder. ### Quiet lines remain too quiet Raise those clips or phrases before compression. Driving Threshold lower until every whisper triggers reduction will usually flatten normal lines. ### The bus clips after Makeup Lower Makeup, inspect the dialogue bus and Main, and check downstream EQ boosts. Makeup should match bypass, not exceed it. ### The export sounds different Confirm the Deliver page renders the intended bus and channel layout, then reimport and listen. Our [audio export checklist](https://davinciresolveclub.com/export-audio-davinci-resolve/) covers the verification. ![DaVinci Resolve Fairlight Dynamics panel for a lavalier dialogue track with compressor gain reduction and output meters](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/fairlight-dynamics-dialogue-real-ui.webp) Real DaVinci Resolve Fairlight Dynamics panel published by Filmmakers Academy. Watch input, compressor gain reduction, makeup, and output while normal, quiet, and loud phrases play; the pictured settings belong to that recording and should not be copied blindly. ## Final Compressor Check - Large edit-to-edit jumps are fixed before the compressor. - Normal, loud, and quiet passages have all been tested. - Gain reduction moves smoothly rather than staying pinned. - Consonants retain their leading edge. - Breaths and room noise don't surge. - Makeup is level-matched to bypass. - The track, dialogue bus, and Main retain headroom. - The rendered file has been reimported and checked. If you stop hearing the compressor and simply understand every line more easily, the settings are doing their job. To place compression inside the complete signal path, use the [DaVinci Resolve Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) alongside the contextual routing, EQ, Voice Isolation versus Dialogue Leveler, loudness, and export guides. ## Fairlight Dialogue Compressor FAQ ### What ratio should I use for dialogue? Blackmagic walks through 2.5:1 to 3:1 as commonly used for dialogue processing. Treat that as an audition range, not a preset: incoming level, threshold, performance, and intended dynamics still decide the result. ### How much gain reduction is enough? A few decibels on louder words is a transparent starting point. If normal speech remains heavily reduced, fix clip gain or use less compression. ### What attack time works for speech? Resolve 21 defaults to 1.4 ms and allows 0–100 ms. Start from the documented default, then lengthen only while consonants keep their edge; the recording decides the value. ### Why does compression raise background noise? Gain reduction narrows the difference between voice and room sound, then the post-Dynamics Makeup Gain raises the complete result. Reduce compressor workload, match bypass level, and repair or automate the source first. ### Should I use Dialogue Leveler and a compressor together? Only if each solves a remaining audible problem. Dialogue Leveler already rides level, so keep both stages gentle and watch for breaths, noise, and pumping. ### Should dialogue compression go on clips or tracks? Correct exceptional clips with gain or automation. Use track compression for a consistent speaker and microphone, and bus compression only for subtle shared control. ### Is the Fairlight compressor available in Resolve Free? Yes. The built-in channel Dynamics compressor is part of the standard Fairlight toolset in Free and Studio. ### Fairlight EQ: Clean Dialogue in DaVinci Resolve URL: https://davinciresolveclub.com/fairlight-eq-dialogue/ Last updated: 2026-09-04T22:40:07.000Z Quick answer: start Fairlight dialogue EQ flat, name the audible problem, make one move, and compare at matched loudness. Use clip EQ for one recording that differs, track EQ for a consistent speaker, microphone, and room, and bus EQ only for a broad change to a controlled stem. A high-pass filter can reduce rumble or hollow a low voice; the curve shows what you set, not whether the dialogue still sounds believable. ![Annotated DaVinci Resolve Fairlight Mixer showing where to open track EQ and compare it in the full mix](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-fairlight-track-eq-real-ui.webp) Annotated real Resolve Studio 21 Fairlight capture (base capture: CineD): choose the track, open its Mixer EQ, make one audible move, and compare in the full mix. Values shown are not a dialogue preset. ## Clip EQ vs Track EQ in DaVinci Resolve | Placement | Use it for | Avoid it when | | ------------------------------------ | ------------------------------------------------------------------------ | -------------------------------------------------------------- | | **Clip EQ** | One take, one microphone change, or one edit that differs from the track | Dozens of clips need exactly the same baseline curve | | **Track channel EQ** | A consistent speaker, microphone, and room across many clips | The track mixes lav, boom, phone, ADR, and different locations | | **Bus EQ** | A gentle broad adjustment to a controlled dialogue stem | Individual sources still have different defects | | **Automation or dynamic EQ plug-in** | A frequency problem appears only on certain words or moments | A static, subtle cut already solves it | In the Fairlight Mixer, double-click the EQ area on a channel strip to open track EQ. The current [Fairlight page](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) and the detailed Mixing chapter of the Resolve 21 manual describe a six-band parametric equalizer in the Mixer. An earlier overview on manual page 3837 calls the same panel four-band with additional high- and low-pass filters. That's an internal documentation conflict; use the controls visible in your installed build as the practical authority. Checked September 5, 2026, the final July 2026 [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) controls the panel, filter-type, Q, and processor-order facts in this guide. The current [Fairlight product guide](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) confirms the public six-band Mixer workflow and A/B auditions. Neither source supplies a universal dialogue curve because the recording decides the correction. If substantially different recordings share one track, move them before equalizing. The organization steps in our [Fairlight routing guide](https://davinciresolveclub.com/fairlight-bus-routing/) make later EQ, compression, automation, and delivery much easier to verify. ## Dialogue Frequency Ranges: Starting Clues, Not Presets | Approximate area | What you might hear | Possible move | | ------------------- | -------------------------------------------------------- | -------------------------------------------------------- | | **Below 60–100 Hz** | Handling noise, traffic vibration, plosives, HVAC rumble | High-pass only until the problem improves | | **150–400 Hz** | Warmth or mud, depending on voice and room | Small broad cut if congested; do not remove body blindly | | **300–800 Hz** | Boxiness, enclosure, room coloration | Search for a resonance, then use a modest cut | | **700 Hz–1.5 kHz** | Nasal or honky tone | Narrow-to-medium cut only after confirming it in context | | **2–5 kHz** | Intelligibility, presence, or harshness | Broad small boost for clarity or cut for fatigue | | **5–10 kHz** | Sibilance, hiss, consonant detail | De-esser or automation for changing S sounds | | **10–16 kHz** | Air, brightness, or broadband hiss | Very gentle shelf; avoid lifting noise | Those ranges overlap because voices, microphones, proximity, rooms, and monitoring differ. They narrow the search; they do not choose the frequency. Q controls bandwidth: lower Q affects a wider range, while higher Q narrows the move. If a web preset says “cut 300 Hz by 4 dB” before hearing the recording, it's guessing. ![Annotated DaVinci Resolve six-band Equalizer explaining Band 1, Bands 2 to 5, Band 6, Frequency, Gain, and Q](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-fairlight-six-band-controls-real-ui.webp) Annotated real Resolve 20 Equalizer capture (base capture: Storyblocks): Band 1 and Band 6 filtering plus Frequency, Gain, and Q. Start flat; the displayed values are not recommended dialogue settings. ## A Repeatable Fairlight Dialogue EQ Workflow 1. **Choose a representative loop.** Include vowels, consonants, a breath, and some room tone. Also mark the worst phrase for later checking. 2. **Set clip gain first.** Large level differences bias tonal judgment and change how later compression behaves. 3. **Listen in the mix.** Solo helps identify a defect; music, effects, and other speakers decide whether it matters. 4. **Enable a high-pass filter only for audible low-frequency contamination.** Raise the cutoff slowly, then back down when the voice loses weight. 5. **Find one resonance.** Use a temporary narrow boost and sweep cautiously. When the offending ring or boxiness jumps forward, turn the boost into a small cut and widen Q if that sounds more natural. 6. **Reduce masking before boosting clarity.** A modest low-mid cut often reveals speech without adding hiss or sibilance. 7. **Add broad tone only if needed.** A small shelf or presence move should survive matched-bypass listening. 8. **Check other words and edits.** A curve that fixes one vowel can damage another. 9. **Render a difficult passage.** Listen away from the on-screen curve and judge the rendered audio on ordinary playback. Don't leave the narrow search boost engaged. It's a magnifying glass, not the repair. Cap the number of corrective bands until each existing move has a clear purpose; six colorful nodes don't make a more professional curve. ## Set the High-Pass Filter by Ear There is no correct universal dialogue cutoff. A high female voice recorded close may tolerate a higher cutoff than a resonant male voice, but microphone proximity and room rumble can reverse that assumption. Start below the useful voice, raise the filter until the low disturbance improves, then retreat slightly. Check plosives separately. A high-pass filter may reduce the low-frequency burst, but a cutoff high enough to erase it completely can thin the entire sentence. Clip-specific EQ, a short gain envelope, or dedicated repair can be cleaner than sacrificing every vowel. ## Cut Mud and Resonance Without Hollowing the Voice Mud is usually broad congestion; resonance is a narrower ring. Treat them differently. For broad buildup, start with a low-Q, small cut and listen in context. For a ring, search with a narrower Q, then reduce the gain and widen the final cut until it stops calling attention to itself. If every clip needs a deep 400 Hz notch, question the room, microphone, or track assignment. EQ can improve coloration, but it cannot remove the time smear of strong reflections. If the defect is steady hiss, hum, or broadband noise rather than tone, use the [background-noise cleanup workflow](https://davinciresolveclub.com/remove-background-noise-davinci-resolve/) before cutting wide frequency ranges. Voice-restoration tools have different limits; our [Voice Isolation vs Dialogue Leveler guide](https://davinciresolveclub.com/voice-isolation-vs-dialogue-leveler/) explains when separation or leveling is the actual task. ## Presence, Harshness, and Sibilance The 2–5 kHz region carries much of speech intelligibility and much of listening fatigue. If dialogue is buried under music, first lower or automate the music. A large presence boost consumes headroom and may make the microphone harsh without solving masking. Sibilance changes word by word, so a static high-frequency cut is often too blunt. Undo the clarity shelf, identify the S range, then use a de-esser or clip automation. Always check T, F, and breath detail afterward; removing every bright consonant makes speech dull and less intelligible. ## EQ Before or After Voice Isolation and Compression? Start with this logic: - Use clip gain before processors so they receive a workable level. - Remove severe low rumble early if it would drive isolation or compression unnecessarily. - Run Voice Isolation before final tonal shaping when it substantially changes the spectrum. - Use corrective EQ before compression if an ugly resonance would trigger the compressor. - Use gentle tonal EQ after restoration when you need to restore body or clarity. - Compress after corrective work, then recheck tone because compression changes spectral balance perceptually. Resolve 21 routes Track FX directly from disk and then onward to other processing. The track Order menu reorders ordinary insert effects, built-in Dynamics, and built-in EQ; its default is **FX, Dynamics, EQ**. Track FX such as Voice Isolation aren't ordinary inserts in that menu. A recent [editor report that EQ seemed less effective after heavy Voice Isolation](https://www.reddit.com/r/davinciresolve/comments/1utq3t8/ai%5Fvoice%5Fisolation%5Fand%5Feq/?ref=davinciresolveclub.com) is useful as a symptom to audition, not as signal-flow documentation. Change one stage, bypass at matched loudness, and use our [dialogue compression guide](https://davinciresolveclub.com/fairlight-compressor-dialogue/) for the dynamics stage. ## Match Two Microphones Without Chasing Identical Curves 1. Align clip gain and compare the same speaker and performance energy. 2. Use the cleaner, more natural microphone as the reference. 3. Remove each microphone’s obvious defect independently. 4. Make one or two broad tonal moves on the mismatched source. 5. Cut between the mics in context, then listen to both the voice and the room tone. 6. Add consistent ambience and crossfades where the acoustic background changes. EQ can move timbre closer, but it can't make a distant boom share the perspective, noise, and reflections of a close lav. A slightly imperfect but stable transition is better than two aggressively processed voices that change room at every cut. ## Fairlight EQ in Free vs Studio Built-in Fairlight EQ is available in DaVinci Resolve Free and Studio. You do not need Studio or a third-party plug-in for ordinary high-pass, low-pass, bell, notch, shelf, frequency, gain, and Q work. Voice Isolation is explicitly Studio-only; built-in EQ isn't. Studio changes access to specific AI and advanced tools, but it doesn't turn a copied curve into a correct listening decision. ## Troubleshooting Dialogue EQ ### The voice becomes thin Lower the high-pass cutoff, reduce the low-mid cut, and check at matched loudness. Restore the last move rather than adding a new bass boost to compensate. ### EQ sounds good solo but disappears in the mix Make the final decision with music and effects playing. The voice may be masked, not badly equalized. Lower or automate the competing element. If the track is silent or its meters stop moving, EQ isn't the fix; use the [no-audio routing and monitoring checklist](https://davinciresolveclub.com/davinci-resolve-no-audio/) instead. ### Sibilance gets worse Remove the high shelf or presence boost and use a de-esser or phrase automation. Don't darken every word to repair a few S sounds. ### Room tone changes at each cut Use clip EQ or separate tracks for the mismatched microphone, then add consistent room tone and crossfades. Track-wide EQ can't reconcile unrelated acoustic spaces. ### The mix clips after an EQ boost Reduce band gain or channel output and inspect the next bus. Boosts consume headroom. Verify the final program with our [LUFS and true-peak checklist](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/). ![Annotated Fairlight dialogue EQ example showing A B comparison, output Gain, and why the visible curve should not be copied](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-fairlight-dialogue-eq-example-real-ui.webp) Annotated real Fairlight Equalizer capture (base capture: Larry Jordan): this curve belongs to one example. Use A/B or bypass and the post-EQ Gain control; do not copy the displayed values. ## Final EQ Check - Every enabled band solves a named audible problem. - The high-pass filter removes rumble without thinning the lowest useful voice notes. - No temporary search boost remains. - Bypass is compared at matched loudness. - Dialogue still works with music and effects. - Every speaker, microphone change, and edit boundary has been checked. - The mix translates to speakers, headphones, and a small mono device. - A rendered test matches the timeline; the [audio export workflow](https://davinciresolveclub.com/export-audio-davinci-resolve/) covers that verification. A clean dialogue curve is usually boring to look at. That's a compliment: the voice sounds natural, the words arrive clearly, and nobody notices the equalizer. EQ is one stage in the audio path. The [DaVinci Resolve Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) connects it contextually to routing, Voice Isolation and Dialogue Leveler, compression, loudness, and export without sending readers to unverified or unpublished pages. ## Fairlight Dialogue EQ FAQ ### What frequencies make dialogue muddy? Mud often appears somewhere around 150–400 Hz, but the exact buildup depends on the voice, microphone, proximity, and room. Sweep to confirm it, then make a small broad cut. ### Where should I set a high-pass filter for speech? There is no universal cutoff. Raise it only until audible rumble improves, then back down before the voice loses body. Check every speaker and microphone. ### Should I boost 3 kHz for dialogue clarity? Not automatically. The 2–5 kHz area can improve intelligibility or create harshness. Reduce masking first, then test a small broad move in the full mix. ### Is EQ better on clips or tracks? Use clip EQ for one take, microphone change, or edit that differs. Use track EQ when the speaker, microphone, and room stay consistent. Use bus EQ only for a gentle broad change after the individual sources are controlled. ### Can EQ remove room echo? No. It may reduce a prominent ring, but reflections overlap the voice across time and frequency. Better microphone choice, editing, ambience, restoration, or rerecording may be required. ### Should EQ come before compression? Corrective EQ often comes before compression so rumble or resonance doesn't trigger it, but Fairlight lets you reorder insert effects, Dynamics, and EQ. The default track order is FX, Dynamics, EQ; compare the actual source. ### Does Fairlight EQ work in DaVinci Resolve Free? Yes. Built-in Fairlight EQ works in Resolve Free and Studio. Voice Isolation is explicitly Studio-only, but ordinary high-pass, low-pass, bell, notch, shelf, frequency, gain, and Q work doesn't require Studio. ### DaVinci Resolve Fusion Tracking: Point, Planar & 3D URL: https://davinciresolveclub.com/fusion-tracking-davinci-resolve/ Last updated: 2026-09-04T22:15:35.000Z Checked September 5, 2026, for motion tracking in DaVinci Resolve, use Tracker for one or more recognizable 2D features, Planar Tracker for a rigid surface such as a screen or sign, and Camera Tracker for a parallax-rich 3D solve. Point and planar tracking work in Resolve Free; Camera Tracker requires Studio. Most failed tracks begin with the wrong geometry, weak texture, mixed depths, reflections, motion blur, or an occluder crossing the analyzed pixels. ![Real Fusion point, planar, and camera tracking interfaces compared by shot geometry](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-tracker-choice-real-ui.webp) Choose by geometry, not by tool complexity: one distinct feature for Tracker, one rigid surface for Planar Tracker, and parallax across a static scene for the Studio-only Camera Tracker. ## Choose the right Fusion tracker | Tool | Use it for | Do not expect it to solve | Edition | | -------------- | ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | --------------- | | Tracker | Position, stabilization, and match moving from one or more recognizable 2D features | A full surface bending in perspective or a 3D camera move with parallax | Free and Studio | | Planar Tracker | Screens, signs, walls, phone faces, vehicle panels, and other rigid planes | A face, cloth, curved object, or pixels crossing several depths | Free and Studio | | Camera Tracker | Recreating camera motion and a 3D point cloud so 3D objects can sit in the shot | A locked-off shot or pure zoom that provides too little parallax to reconstruct useful depth | Studio | If you only need a title to follow a shoulder, don't solve a 3D camera. If you are replacing a screen seen at an angle, a position-only point track is usually too weak. Blackmagic’s [Fusion overview](https://www.blackmagicdesign.com/products/davinciresolve/fusion?ref=davinciresolveclub.com) introduces point, planar, and camera tracking; the current [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) controls the exact steps and interface terms used below. This page is the tracking route inside the [DaVinci Resolve Fusion hub](https://davinciresolveclub.com/davinci-resolve-fusion/). If MediaIn, Merge, masks, and node inputs are still unfamiliar, start with the [Fusion tutorial for beginners](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) before applying tracker data. ## Prepare the shot before tracking Open the clip on the Fusion page and inspect it at full resolution. Tracking is easier on the clean image than after grain, glow, heavy blur, or aggressive grading changes the texture. Fusion processes before the Color page in Resolve’s normal image pipeline, so the original clip is often already the best starting point. Choose a reference frame where the target is sharp, large, unobstructed, and close to the orientation you want for the insert. Starting on frame one is convenient, not automatically correct. For a planar track, Blackmagic’s training specifically recommends starting when the surface is large, clear, least distorted, and moving slowly enough to avoid motion blur. If the shot has significant lens distortion, correct it before planar analysis. Straight graphics tracked into a distorted plate can otherwise look attached in the center but slide near the edges. Restore distortion after the insertion only when the finished graphic must inherit the original plate’s lens shape; the required node order depends on the composite and delivery pipeline. ## How to use the 2D Tracker node In Resolve 21, the Fusion Tracker can default to IntelliTrack. IntelliTrack is Studio-only. The classic Point tracker remains available and is the Free-compatible pattern/search-box workflow described here; choose **Point** when you need those manual controls or are working in Resolve Free. 1. Select MediaIn and press **Shift-Spacebar**. Search for **Tracker** and add it after MediaIn. 2. Move to a clear frame and place the tracker on a unique, high-contrast feature that belongs to the motion you need. 3. Size the inner **pattern box** around the recognizable detail. Size the outer **search box** only large enough to contain the feature’s next-frame movement. 4. Track forward or backward while watching the viewer. Stop when the marker jumps to a different edge or texture. 5. Open the Operation tab and choose the result you need, such as **Match Move** for an attached foreground or stabilization for the plate. 6. Connect the graphic to the Tracker’s foreground input when using its merge operation, then inspect the composite at normal speed. The inner box answers “what should I recognize?” The outer box answers “where should I look for it next?” A huge search area is not insurance; it slows analysis and gives the tracker more wrong candidates. Fast motion may need a larger search area, while slow motion usually doesn't. ![Annotated Fusion point tracker pattern box, search area, and tracking center](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-point-tracker-boxes-real-ui.webp) Annotated real Fusion viewer capture (base capture: Creative Video Tips): the inner solid box defines the pattern, while the outer dashed box limits the next-frame search. One tracked pattern supports position. Two well-separated patterns are required to correct rotation. Blackmagic recommends a third pattern to correct scale in stabilization and notes that more good patterns can improve the solution; the published Steady Size output itself needs at least two. Keep every pattern fixed relative to the others on the same rigid object and depth. ## How to track a screen or sign with Planar Tracker Planar tracking analyzes many pixels across one rigid surface. It's usually the best first choice for a screen replacement, billboard, book cover, wall graphic, or flat vehicle panel. 1. Add **Planar Tracker** between MediaIn and MediaOut. 2. Go to the best reference frame and draw a polygon around textured pixels on one plane. The shape doesn't have to trace the final graphic’s corners. 3. Exclude the background, rotating wheels, reflections, hands, faces, or anything that moves independently of the plane. 4. Choose the simplest **Motion Type** that explains the shot. Translation handles position; rotation and scale add those changes; perspective is appropriate when the plane’s apparent angles change. 5. Click **Set** at the reference frame, track to the start, return to the reference with **Go**, and track to the end. 6. After analysis, switch Operation Mode to **Steady**. The tracked plane should appear locked. Residual wobble exposes drift more clearly than a polished insert does. 7. Return the mode to Track. For a simple same-frame corner pin, use the Planar Tracker’s corner-pin workflow. For reusable motion data, click **Create Planar Transform** and feed the [graphic, matte, or clean plate](https://davinciresolveclub.com/remove-objects-davinci-resolve/) through that node. The tracking shape identifies pixels to analyze; it isn't the corner pin. This distinction prevents a common mistake: drawing a tight four-corner rectangle around a glossy screen even though the border or nearby textured frame would provide a more stable plane. ![Annotated DaVinci Resolve Planar Tracker reference time, motion type, tracking buttons, and Planar Transform](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-planar-tracker-real-ui.webp) Annotated real DaVinci Resolve 19 PlanarTracker capture (base capture: Scopique): set a clean reference, track both directions, inspect in Steady mode, then create reusable transform data. Resolve 21 keeps this workflow. The final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) documents the current sequence: choose a clean reference, click Set, define the track region, analyze the needed range, inspect the result in Steady, and create a Planar Transform when reusable motion data is required. The older Resolve 18 practice guide is useful training, but it isn't the controlling source for current UI claims. ## When to use the 3D Camera Tracker Use Camera Tracker when the camera moves through a scene and the insert must live in 3D space: a sign on a wall revealed by parallax, a 3D title behind foreground objects, or an object placed on a ground plane. The tool analyzes many features, solves a virtual camera, and produces a point cloud that represents scene structure. A useful solve needs parallax: static features at different depths must shift by different amounts as the camera moves. Locked shots and pure zooms provide little depth information. Heavy rolling-shutter wobble can also corrupt feature paths, so a numerically solved camera may still fail a simple geometry test. 1. Add Camera Tracker after MediaIn. Connect a rough matte to the node’s white **Occlusion Mask** input when moving people, cars, water, reflections, or other non-static regions would generate bad tracks. White areas are ignored; unmasked fixed scenery remains available for analysis. Preview the generated points before solving and confirm that excluded motion isn't contributing camera tracks. 2. Enter the recorded focal length and film gate or camera model when they're known. If the metadata is missing, give the solver the closest defensible camera information and estimate only what the shot supports. 3. Analyze the clip, inspect the generated tracks, and solve the camera. Delete obvious outliers in small groups, rerun Solve, and compare the result. Removing too many tracks can leave the solver without enough information and make the error worse. 4. Evaluate the solve visually as well as numerically. Average Solve Error is a reprojection error in pixels, not a complete quality score. The Resolve 21 manual calls below 1.0 a good target for HD and below 0.5 the goal for 4K, but a low number still doesn't prove that ground orientation, scene scale, contact, or parallax is correct. 5. Select suitable points to establish the ground plane and origin, then export the solved 3D scene. 6. Place a simple ImagePlane3D or primitive first. Check contact, perspective, and parallax before building the final asset. ![Annotated Fusion Camera Tracker Solve tab with static scene tracks and filtering controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-camera-tracker-real-ui.webp) Annotated real Fusion CameraTracker capture (base capture: Storyblocks): keep tracks fixed to the set, clean poor tracks in small groups, and rerun the solve after each change. Camera Tracker requires Studio. Camera Tracker requires DaVinci Resolve Studio; point and planar tracking remain available in Free. Blackmagic lists that edition boundary in the [official Studio feature comparison](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5FStudio%5FFeatures.pdf?ref=davinciresolveclub.com). The [Resolve Free vs Studio breakdown](https://davinciresolveclub.com/davinci-resolve-vs-studio/) puts that limitation in context before you build a 3D workflow around a Studio-only solve. ## Track through occlusion without poisoning the data A tracker can't see detail hidden by a hand, person, car, or frame edge. Continuing blindly through the obstruction creates confident-looking but wrong keyframes. For a point track, stop on the last good frame. Reposition the pattern on a different feature of the same rigid object, use append-style manual tracking where appropriate, or keyframe through the short gap. Resume automatic analysis only when recognizable detail returns. For a planar track, keep foreground motion outside the tracking polygon or feed a matte into the white Occlusion Mask input. White areas in that matte are ignored by the Planar Tracker; they identify the foreground occluder, not the plane to analyze. A [community planar-tracking case](https://www.reddit.com/r/davinciresolve/comments/1tzcee4/advice%5Fregarding%5Fplanar%5Ftracker/?ref=davinciresolveclub.com) illustrates the symptom and repair pattern: check the grid, mask a crossing hand, and return to the last reliable frame. The Resolve 21 manual remains the controlling technical source. If the obstruction needs to pass in front of the insert, tracking is only half the composite. Build a holdout mask or roto layer for the foreground object. The [Fusion rotoscoping guide](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/) explains manual edge work, while the [Magic Mask guide](https://davinciresolveclub.com/davinci-resolve-magic-mask/) covers the Studio-assisted option. If the deliverable is simply a moving face or object that must be obscured, stay on the Color page unless Fusion solves a real occlusion problem. The [face and background blur guide](https://davinciresolveclub.com/blur-face-background-davinci-resolve/) covers Power Window tracking, first-bad-frame repair, mosaic, and the final privacy review without turning a simple anonymization task into a larger composite. ## How to diagnose and fix tracking drift ### The track slides gradually Return to the first visibly wrong frame. Choose texture that changes less, enlarge the useful planar region, remove pixels at another depth, or reduce the motion model. Don't blur or smooth a path that follows the wrong surface. ### The tracker jumps during motion blur Use a broader recognizable pattern or a nearby feature on the same rigid object. A larger search region helps only when displacement is the problem. If the pixels themselves become unreadable, bridge those frames manually and reconnect to valid analysis. ### The plane flips or bends The shape probably includes independently moving detail, a reflection, two depths, or too little stable texture. Go back to the reference frame, redraw the region, and verify the result in Steady mode before creating new transform data. ### The insert moves twice Tracking data has likely been applied in two places, for example, through a Planar Transform and again through a tracked Transform or corner pin. Follow the node chain from the graphic to Merge and keep one intentional motion transfer. ### The object disappears near the frame edge Check Domain of Definition and frame bounds at each node, then inspect Global In/Out, mask bounds, timing, and Merge order. A Transform or crop can clip the insert even when the tracking data remains valid. The [Resolve Inspector guide](https://davinciresolveclub.com/davinci-resolve-inspector/) is useful when Edit-page transforms or clip timing are also involved. ## Make the tracked insert look attached A perfect path can still produce a fake composite. Match the insert’s perspective, brightness, contrast, black level, sharpness, grain, and motion blur to the plate. If the sign sits behind a foreground object, restore that occlusion. If it belongs on a glossy screen, consider reflections and glare rather than covering them with a perfectly clean rectangle. If the insert also depends on a keyed foreground, the [Delta Keyer workflow](https://davinciresolveclub.com/davinci-resolve-delta-keyer/) covers matte cleanup before that foreground is recombined with the tracked composite. Place the graphic at the reference frame before judging the track. A Planar Transform moves it relative to that reference, so a poorly chosen initial position can look like drift even when the data is stable. Finish the artwork before the tracked transform when you want all its elements to move as one; place view-dependent finishing after the transform when the effect belongs to the final composite. For styled cards or labels, build the design first and then pass the combined result through the tracking transform. The [rounded-corner workflow](https://davinciresolveclub.com/round-corners-davinci-resolve/) shows a reusable graphic treatment that can be attached this way. ## Final tracking QA - Watch the raw tracker or Steady view before judging the finished graphic. - Inspect the first frame, reference frame, last frame, occlusions, blur, and frame exits. - Check the insert’s corners and edges at full resolution. - Confirm only one node applies the tracking transform. - Play at normal speed, then render a short test and review it outside Fusion. After the short test render passes, use the [DaVinci Resolve Fusion hub](https://davinciresolveclub.com/davinci-resolve-fusion/) to continue into node fundamentals, keying, rotoscoping, masks, and motion-graphics workflows without duplicating this page’s tracking scope. ## Fusion tracking FAQ ### Which Fusion tracker should I use for text? Use the 2D Tracker when the text follows a distinct feature without meaningful perspective change. Use Planar Tracker when it sits on a flat surface. Use Camera Tracker when the text must exist in solved 3D space with camera parallax. ### Is Planar Tracker available in DaVinci Resolve Free? Yes. The classic 2D Tracker and Planar Tracker are available in Resolve Free and Studio. Fusion Camera Tracker requires Studio. ### What is the best frame to start a planar track? Choose a frame where the plane is large, sharp, unobstructed, relatively undistorted, and not smeared by fast motion. Set that frame as the reference and analyze in both directions. ### How can I check whether a planar track is good? After tracking, change Operation Mode to Steady and watch the tracked surface. It should remain locked without residual sliding or bumps. A temporary grid or high-contrast insert also makes edge drift visible. ### Why does my tracked graphic slide? The tracker may be following weak texture, multiple depths, reflections, or an occluding object. The motion type may also be too simple, or more complex than the shot supports. Fix the first bad frame and retest the raw data. ### Should I use Planar Transform or corner pin? Use the direct corner-pin workflow for a straightforward screen or sign replacement. Create a Planar Transform when you want reusable planar motion on a graphic, mask, clean plate, or irregular element elsewhere in the node tree. ### How to Remove Silence in DaVinci Resolve URL: https://davinciresolveclub.com/remove-silence-davinci-resolve/ Last updated: 2026-09-04T22:05:45.000Z This is the native automatic workflow introduced in Resolve 20.2 and carried into Resolve 21\. It can save a lot of blade work, but it's still a level detector, not an editor listening for meaning. Quiet consonants, breaths, dramatic pauses, captions, music cues, and visible jump cuts all need a human pass afterward. If a search result says Resolve has no built-in way to remove dead air, check its date and version. That advice describes older releases or a different workflow: Blackmagic’s [Resolve 20.2 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20.2%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) introduced the native Ripple Delete Silence command, and the command remains documented in current Resolve 21. ## Remove Silence and Ripple Delete Silence Do Different Jobs | Command | Where | Timeline result | | ------------------------------------ | ------------------------------------- | ---------------------------------------------------------------------------------------------------- | | Ripple Delete Silence | Edit/Cut: Clip > Audio Operations | Cuts detected quiet sections and closes the gaps, shortening the sequence | | Remove Silence (Studio only) | Fairlight: selected clip context menu | Creates separate audio clips with gaps while keeping the original timeline duration | | Remove Silent Portions (Studio only) | Transcription window | Filters silence markers from the transcript before the selected text range is edited into a timeline | | Gate or expander | Fairlight dynamics | Reduces level during quiet passages but removes no timeline duration | | Manual ripple edit | Edit/Cut timeline | Removes only the pauses the editor chooses | Use **Ripple Delete Silence** to tighten a linked talking-head, interview, podcast-camera, or tutorial timeline where detected pauses should disappear from picture and sound. Use Fairlight **Remove Silence** in Studio when audio should be split around quiet regions without changing the program length. In the Studio-only Transcription window, Remove Silent Portions filters silence markers before you edit the selected transcript range into a timeline; it's a text-based assembly route, not a dB-threshold control. The full steps live in the [Resolve 21 transcription workflow](https://davinciresolveclub.com/transcribe-audio-davinci-resolve/). Use a gate or expander only when the timing is already right and quiet passages should become lower, not shorter. ![Annotated Fairlight Remove Silence controls over a DaVinci Resolve audio waveform](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-fairlight-remove-silence-annotated.webp) Annotated real Resolve 20 Fairlight capture: Remove Silence detects low-level ranges and leaves gaps, so the timeline duration stays fixed. Resolve 21 still lists this Fairlight command as Studio-only. Checked September 5, 2026, the final [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) documents the Edit/Cut command, its five parameters, the red-striped preview, and current Sync Lock behavior. It also marks the separate Fairlight Remove Silence tool as Studio-only. ## Prepare the Timeline Before Automatic Removal 1. **Duplicate the timeline.** Give the copy a clear name such as `Interview_AutoSilence_Test`. 2. **Choose one representative section.** Test 30–60 seconds containing normal speech, quiet speech, breaths, and real pauses before processing a one-hour recording. 3. **Confirm linked picture and production audio.** If the audio belongs to the camera clip, keep Linked Selection on and select the linked clip. 4. **Inspect other tracks.** Decide whether music, B-roll, graphics, subtitles, markers, and sound effects should ripple with the dialogue. 5. **Set sync locks deliberately.** They operate independently from source/destination track selection: enabled tracks participate in ripple timing, while disabled tracks stay put and may lose relative sync. Don't start on a compound clip, multicam stack, or nested timeline until the behavior is understood on a simple duplicate. A ripple that's correct for the dialogue track can still move a music cue or leave a graphic covering the wrong sentence. ## Automatically Remove Silence in Resolve 21 1. **Select the eligible timeline clip.** On Edit or Cut, click the linked audio/video clip or the audio clip you want Resolve to analyze. 2. **Open the command.** Choose **Clip, then Audio Operations, then Ripple Delete Silence**. 3. **Set Threshold.** Start from the recording’s room-tone level, not a value copied from another microphone. 4. **Protect the word edges.** Use Pre Head and Post Tail to retain time before and after detected audible regions. 5. **Set Minimum to Trip.** Make Resolve ignore short low-level dips that are part of normal speech. 6. **Enable Cross fade audio.** Let Resolve smooth adjacent audio edges when the retained handles are long enough. 7. **Inspect the red stripes.** They show the sections Resolve intends to remove. Scrub quiet words, phrase endings, and breaths before committing. 8. **Click Remove.** Resolve cuts the detected intervals and ripples the remaining sections together. The numbers in the screenshot are an example, not a preset. A close-miked voice in a treated room, a laptop microphone, and a street interview have different noise floors and dynamic ranges. Adjust from the weakest real words in the selected clip. ![Annotated DaVinci Resolve Ripple Delete Silence dialog and linked video-audio timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-ripple-delete-silence-annotated.webp) Annotated real Resolve 20.2 Edit-page capture: preview every red range before Remove. The current Resolve 21 manual calls the frame-based control Minimum to Trip; the older captured dialog says Minimum to strip. ## What Each Ripple Delete Silence Setting Does ### Threshold Any signal below the threshold can be classified as silence. Raising the threshold removes more audio; lowering it preserves more. Set it too high and Resolve can remove soft syllables or breathy words. Set it too low and room tone prevents pauses from being detected. ### Pre Head Pre Head retains frames before each audible section. It protects the attack of an incoming word and keeps the edit from beginning exactly on a consonant. ### Post Tail Post Tail retains frames after each audible section. It protects word endings, breaths, and the decay of the room. The outgoing and incoming handles also give the crossfade somewhere to work. ### Minimum to Trip This is the minimum silent duration, measured in frames in the Edit/Cut command, that Resolve will strip. A higher value ignores short pauses; a lower value creates more cuts and can make speech sound chopped. ### Cross fade audio This adds a simple crossfade between remaining audio clips. It can prevent clicks and soften a room-tone change, but it can't restore a clipped consonant. If head and tail handles are too short, the transition still needs manual repair. ## Dial In the Threshold Without Cutting Words Find the quietest sentence you intend to keep, then compare it with a true pause containing only room tone. The threshold belongs between those levels. After each adjustment, inspect the red-striped preview: the stripes should cover pauses, not the front or tail of words. If speech and noise overlap at similar levels, no threshold can separate them reliably. Lower the threshold to protect speech, remove only longer pauses, and finish difficult cuts manually. Noise reduction, EQ, and compression are later mixing decisions; don't preprocess the dialogue so aggressively that the detector mistakes artifacts for silence. The [Fairlight dialogue EQ guide](https://davinciresolveclub.com/fairlight-eq-dialogue/) explains the cleanup stage without using EQ as a silence detector. ## Protect Music, B-Roll, Graphics, and Captions Resolve 20.2 changed ripple behavior so sync locks can preserve relationships across tracks independently of ordinary track selection. That is helpful, but it means the timeline must be prepared intentionally. - **Music:** let it ripple when it belongs to the dialogue timing; disable sync lock when the cue must stay anchored to absolute time. - **B-roll:** decide whether it follows the spoken passage or should be re-edited after the dialogue changes. - **Titles and graphics:** check both start and end after the ripple. - **Captions:** regenerate, realign, or inspect every caption after timing changes. - **Bus and track automation:** never assume it followed the editorial change. Compare automation breakpoints, fader moves, and music hits before and after the ripple. - **Markers:** confirm whether critical delivery or music markers still identify the intended moment. The safest first pass isolates a dialogue-driven duplicate. Once the timing is approved, rebuild or realign the supporting layers instead of assuming every overlay survived. ## Make the Audio Joins Sound Natural Cross fade audio handles simple joins, but automatic cuts can still reveal a changing noise floor. Listen with the picture hidden. If one edit jumps from air conditioner hum to near-digital silence, extend the audio edges, add consistent room tone under the cut, or adjust the crossfade by hand. Don't use a gate to repair editorial rhythm. A gate or expander changes level, not duration. After the timing is stable, the [Fairlight compressor guide](https://davinciresolveclub.com/fairlight-compressor-dialogue/) can shape dynamics without changing where the words occur. ## Fix the Picture Jump Cuts Every removed pause in a single-camera talking head creates a picture cut. Sometimes that direct jump is the house style. When it is distracting, use one of these editorial fixes: - cut to a genuine second angle; - cover the edit with relevant B-roll; - use a restrained punch-in or alternate crop; - change the cut point with a J-cut or L-cut; - restore part of the pause when the face or gesture can't be joined cleanly. Smooth Cut can help only when subject and background position remain similar. In Resolve Studio 20 and later, the [official Resolve 20 feature guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) says Smooth Cut uses AI Speed Warp by default and provides an Inspector option to return to the earlier optical-flow method. That AI Speed Warp option is Studio-only. Keep the transition short and inspect every frame; an honest jump cut is better than a warped face. ## Use Fairlight Remove Silence Without Changing Duration On the Fairlight page in Resolve Studio, select one clip or a collection of clips, right-click, and choose Remove Silence. This IntelliCut tool uses Threshold, Pre Head, Post Tail, Minimum to Strip in milliseconds, and Fade Head and Tail. It creates separated audio clips with gaps while the overall timeline timing remains fixed. This is useful before mixing dialogue, ADR, or isolated microphones where you want empty regions but must not make picture shorter. It's associated with Fairlight’s IntelliCut feature set in Blackmagic’s Resolve 20 documentation, while the later Edit/Cut Ripple Delete Silence command is the straightforward current route for pacing a linked talking-head clip. Blackmagic’s [official Fairlight overview](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) explains the wider track, bus, dynamics, and delivery workflow. For the practical clip-versus-track path, use the [Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/). ## Manual Ripple Edit: The Reliable Fallback Automatic detection is the first pass, not a requirement. For emotional interviews, noisy field recordings, overlapping speakers, or a few remaining mistakes, manual edits give better control: 1. Listen to the pause in sentence context. 2. Cut linked picture and sound after the outgoing word and natural breath. 3. Cut before the next word without touching its initial consonant. 4. Ripple-delete the chosen gap. 5. Add short fades or room tone. 6. Review captions, graphics, music, and visible motion. The [Resolve shortcuts guide](https://davinciresolveclub.com/davinci-resolve-keyboard-shortcuts-guide/) covers blade, trim, and ripple-delete commands for this cleanup pass. When the goal is to mute or detach audio without shortening the program, use the separate [mute and split audio workflow](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/). ## Resolve Free vs Studio The Edit/Cut **Ripple Delete Silence** command introduced in Resolve 20.2 is available in current Resolve 21 Free and Studio and doesn't require transcription. Manual cuts, ripple edits, fades, sync locks, and ordinary Fairlight mixing also work in Free. The separate Fairlight Remove Silence command and Audio Transcription/Text Based Editing are Studio-only in Resolve 21\. Ripple Delete Silence itself is the Free-and-Studio Edit/Cut route. If it's missing or gray, confirm Resolve 20.2 or later, switch to the Edit or Cut page, select an eligible timeline clip rather than a bin item, and open Clip > Audio Operations. ## Fix Silence-Removal Problems ### Resolve cuts quiet words Lower the threshold, increase Pre Head and Post Tail, and raise Minimum to Trip. Retest a short section containing the quietest real speech. ### Nothing is detected Raise the threshold gradually and inspect whether constant room noise sits above it. A noisy recording may need manual candidates rather than an aggressive threshold. ### Video and audio go out of sync Undo, restore Linked Selection for the production pair, and inspect sync locks on every relevant track. Do not repair drift by sliding one component until the cause is known. ### Music, captions, or graphics move incorrectly Return to the duplicate, set track sync locks deliberately, and run the command again. Then inspect every timed overlay. Automatic dialogue cuts can't decide the story role of other tracks. ### The dialogue sounds breathless Restore pauses that carry emphasis or comprehension. Increase Minimum to Trip and Post Tail on the next pass. Fast is a style; nonstop is usually fatigue. ### One-frame gaps or clicks remain Zoom into the edit, close any residual gap manually, and add or adjust the crossfade. Keep room tone continuous. If the source is silent for unrelated reasons, the [Resolve no-audio checklist](https://davinciresolveclub.com/davinci-resolve-no-audio/) separates playback failures from intentional pauses. ![Annotated linked DaVinci Resolve timeline for reviewing proposed silence cuts](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-ripple-review-annotated.webp) Annotated real Resolve timeline: check quiet word edges, room tone, lip sync, captions, music, B-roll, and picture jumps before accepting the automated pacing. ## The Review Pass Automation Cannot Do Watch once without looking at the waveform. Then listen with the picture hidden. Check sentence meaning, breath, room tone, clicks, lip sync, captions, graphics, music hits, gestures, and every visible jump created by the removals. A good silence pass removes waiting without removing the speaker. When timing is approved, measure the final mix with the [Resolve audio levels and LUFS guide](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/); pacing and loudness are separate deliverables. For the next step, the [Resolve workflow hub](https://davinciresolveclub.com/tag/workflow/) groups proxy, timeline, relinking, multicam, and finishing routes by task. If you are learning the application in sequence, the [DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/) moves from editing through dialogue repair, loudness, and export. ## Remove Silence in Resolve FAQ ### Where is Ripple Delete Silence in Resolve 21? Select an eligible clip on the Edit or Cut timeline, then choose Clip, then Audio Operations, then Ripple Delete Silence. ### What is the difference between Remove Silence and Ripple Delete Silence? Fairlight Remove Silence creates gaps while keeping the timeline duration. Edit/Cut Ripple Delete Silence closes the detected gaps and shortens the sequence. ### Does a noise gate remove silent sections from the timeline? No. A gate reduces level during quiet passages but doesn't remove time. Use a ripple edit to shorten the program. ### What threshold should I use? Set it from the specific recording: above the room tone but below the quietest words you need to keep. There's no universal value for every microphone and room. ### Why did video and audio go out of sync? The linked pair or relevant tracks didn't share the ripple operation. Undo, check Linked Selection and sync locks, then retry on a duplicate. ### Can Resolve Free automatically remove pauses? Yes. Current Resolve 21 Free includes Clip, then Audio Operations, then Ripple Delete Silence, along with manual ripple editing and fades. ### How to Round Corners in DaVinci Resolve URL: https://davinciresolveclub.com/round-corners-davinci-resolve/ Last updated: 2026-09-04T21:52:12.000Z To round a video in DaVinci Resolve, open the clip in Fusion, select MediaIn1, and add a Rectangle mask. Confirm Rectangle1 feeds MediaIn1’s blue mask input, then select Rectangle1 and increase Corner Radius. Keep Soft Edge near zero for a clean card; place a background on the track below when the transparent outside area shouldn't appear black. The click sequence is short. The part that catches editors is everything around it: the mask can land on the wrong node, non-uniform scaling can stretch the curves, and a perfectly good transparent result can look black when there's nothing underneath it. This guide covers the dependable Fusion setup first, then the faster alternatives for graphics and multi-clip sequences. ## Choose the Method That Matches the Job | What you are building | Best starting point | Why | | ---------------------------------------- | --------------------------------------------------------- | -------------------------------------------------------------------------------------- | | Picture-in-picture video or image | Fusion Rectangle mask | The shape, transparency and node order remain visible and editable. | | Several cuts that should share one frame | Compound Clip, then Fusion mask | One mask controls the complete sequence instead of being copied to every shot. | | Label, lower third or interface card | Fusion Background + Rectangle | Color, alpha, size and radius stay procedural. | | One quick overlay | Resolve FX Transform: enable Crop, then set Edge Rounding | Fast on the Edit page; Edge Softness is optional feathering, not the rounding control. | Checked September 5, 2026, the standard Fusion method works in DaVinci Resolve Free. The final [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) documents Rectangle masks, the blue effects-mask input, Width, Height, Soft Edge, and Corner Radius. No plug-in or baked PNG frame is required. ## Round a Video with a Fusion Rectangle Mask 1. On the Edit page, place the clip on **V2**. Put the background video, color or graphic on **V1**. 2. Select the V2 clip and open the **Fusion** page. 3. Confirm that **MediaIn1** is connected to **MediaOut1**. 4. Select **MediaIn1**, then click the **Rectangle** mask button in the Fusion toolbar. Resolve should create **Rectangle1** and connect it to the blue mask input on MediaIn1. 5. Select Rectangle1\. Set **Width** and **Height** so the mask sits slightly inside the frame. 6. Increase **Corner Radius** until the curve suits the card. 7. Leave **Soft Edge** at zero or very low for crisp UI-style corners. Add feather only when the composite genuinely needs a softer edge. 8. Return to the Edit page and watch the entire clip over its final background. ![DaVinci Resolve 21 Fusion Rectangle mask connected to MediaIn1 with Corner Radius controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-fusion-rectangle-mask-ui.webp) Resolve 21 interface reconstruction: Rectangle1 feeds MediaIn1's blue mask input; the checkerboard around the rounded card is transparent. The checkerboard in the Fusion Viewer means transparency; it isn't a fault. On the Edit page, that area reveals the lower track. If there's no lower track, the timeline background is normally black, so the finished frame looks as though the mask added a black border. ![DaVinci Resolve checkerboard transparency compared with a V2 rounded clip revealing the V1 background](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-alpha-timeline-ui.webp) Resolve 21 workflow reconstruction: Checkerboard means transparent pixels in Fusion; on the Edit page, those pixels reveal the lower V1 background. ## If the Rectangle Does Nothing, Check the Connection A Fusion node has different input types. The yellow connection carries an image. The blue input limits that image or effect with a mask. Rectangle1 must feed the blue input on the node you want to cut. If you drop a Rectangle into empty space, Resolve creates the tool without necessarily connecting it where you intended. Drag Rectangle1’s output square to MediaIn1’s blue triangle, or delete the loose node, select MediaIn1 and add Rectangle again. The latter is usually faster and avoids connecting the mask to MediaOut or an unrelated effect. If the node graph still feels opaque, the site’s [Fusion tutorial for beginners](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) explains viewers, image connections, masks and Merge nodes before you build a larger composite. Use the [Fusion learning hub](https://davinciresolveclub.com/davinci-resolve-fusion/) to choose the next workflow by task. Blackmagic also provides current [Resolve training books and lesson files](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com) with downloadable practice projects. ## Resize the Card Without Stretching Its Corners Rectangle1 defines the visible shape. A Transform node changes the position and scale of the image. Those jobs look interchangeable until X and Y are scaled by different amounts. If you create the rounded mask and then stretch the finished result vertically or horizontally, the curve stretches with it. A circular corner becomes an oval. Apply the aspect-ratio-changing transform *before* the Rectangle mask, or calculate the mask after the image reaches its final proportions. When the entire timeline needs a new shape rather than one picture-in-picture card, use the separate [aspect-ratio workflow for Resolve](https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/) before building the mask. ![Fusion node-order comparison showing rounded mask before and after a non-uniform Transform](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-mask-order-comparison-ui.webp) Resolve 21 node-order reconstruction: A downstream Transform stretches the existing mask; masking Transform1 keeps the final corners round. Blackmagic lays out Corner Radius as a normalized 0.0–1.0 control but doesn't publish a fixed-pixel formula. In practice, editors report that the same value can look different after Width or Height changes; this recurring [Fusion Rectangle discussion](https://www.reddit.com/r/davinciresolve/comments/1nv0su1/?ref=davinciresolveclub.com) is directional workflow evidence, not an official algorithm definition. Set the radius by eye at the final size, or use Shape tools or an expression when dimensions animate. ## Use One Rounded Frame Across Multiple Clips Copying the same Fusion composition to ten edits works until one clip is trimmed, reframed or replaced. If the whole sequence should play inside one rounded window, select the clips on the Edit page, right-click and choose **New Compound Clip**. Open that Compound Clip in Fusion and apply the Rectangle mask once. This is the clean route for a demo reel, app walkthrough or montage inside a persistent device-style frame. Keep individual clips separate when their positions or radii must change independently. A Compound Clip creates another level of timing, so name it clearly and open it when you need to adjust the cuts inside. An Adjustment Clip is not my first choice for this job. It processes everything beneath its time range, which can unintentionally include titles, backgrounds or overlays. The dedicated [Adjustment Clips guide](https://davinciresolveclub.com/adjustment-clips-davinci-resolve/) explains that top-down scope and when a shared timeline effect is the better tool. ## Build a Rounded Color Card for Text For a label or lower-third panel, start with a Fusion **Background** node rather than a Solid Color generator imported from the Edit page: 1. Add a Background node and choose the card color and alpha. 2. Select the Background node and add Rectangle1 to its blue mask input. 3. Set Width, Height and Corner Radius on Rectangle1. 4. Add Text+ and Merge the text over the rounded Background. 5. Connect the Merge output to MediaOut. The result remains editable: you can change the fill, opacity, proportions and text without replacing an asset. For typography, layout and Text+ controls, continue with the [DaVinci Resolve text guide](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/). ## Add a Border and Shadow That Follow the Radius Build the border from a second rounded shape instead of applying an outline to the rectangular source. Duplicate Rectangle1, enlarge the duplicate slightly, and use it to mask a Background node set to the border color. Merge the rounded video over that larger background. For a shadow, duplicate the outer rounded shape again, darken it, soften it and offset it behind the card. Keep the shadow on its own branch. Blurring the completed video branch softens the picture as well as the edge, which is rarely what you want. ## When the Edit-Page Method Is Enough For a one-off overlay, apply **Resolve FX Transform** from the Effects Library. In Resolve 21, enable **Crop**, then adjust **Edge Rounding**. Use **Edge Softness** only when the alpha edge needs feathering; it isn't the rounding control. This method is quicker than Fusion when one clip needs no reusable border or node branching. ![Resolve FX Transform Image Adjustment with Crop, Edge Softness and Edge Rounding in DaVinci Resolve 21](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-resolve-fx-transform-ui.webp) Resolve 21 interface reconstruction: For a one-off Edit-page overlay, enable Crop, set Edge Rounding, and keep Edge Behavior on Transparent. Don't confuse that effect with the normal Inspector controls named Crop Left, Crop Right, Crop Top and Crop Bottom. Those controls remove straight strips; they don't create curved corners on their own. The [Resolve Inspector control guide](https://davinciresolveclub.com/davinci-resolve-inspector/) maps those clip-level transform and crop groups. Move back to Fusion when the effect is combined with stabilization, several transforms, animation or a reusable border. The node graph makes the processing order visible instead of forcing you to guess which crop happened first. ## Round Only the Top or Bottom Corners The standard Rectangle mask applies the same radius to all four corners. For a panel with only the top corners rounded, make the mask taller than the frame and move it down until the bottom curves sit outside the visible area. Reverse that placement for only the bottom corners. For four independently controlled corners or a true squircle, combine multiple masks or use the Shape tools rather than fighting the standard Rectangle. Community threads about [independent Fusion corner radii](https://www.reddit.com/r/davinciresolve/comments/1kvqaju/?ref=davinciresolveclub.com) show why this becomes an expression-and-shape problem, not a hidden checkbox in Rectangle1. ## Animate the Card Without Making the Edge Wobble Width, Height, Center, and Corner Radius have keyframe controls. A clean entrance usually keeps Corner Radius fixed and animates Center or overall size. If Width and Height change by different proportions, the apparent curve can breathe. Treat that as a geometry observation and verify the rendered motion; Blackmagic doesn't document a fixed-pixel radius formula for Rectangle. Set the final radius at the final card size, then preview the complete animation at normal speed. Use the Spline editor to ease the position or scale; don't add extra Corner Radius keyframes unless the design intentionally changes from square to rounded. ## Export Rounded Corners with or Without Transparency If the rounded video is already composited over its final background, export it normally. The transparency outside the mask has already been replaced by the lower track. If another editor needs a file with real transparency, choose a delivery format and codec that expose alpha-channel export in your installed Resolve build, enable the alpha option, and test the rendered file by placing it over a bright color. Don't assume an H.264 MP4 will preserve transparency. For ordinary YouTube or social delivery, composite over the intended background first and use the settings in the [Resolve export settings hub](https://davinciresolveclub.com/davinci-resolve-export-settings/). ## Fix the Five Problems That Waste the Most Time ### The corners are black The outside of the mask is transparent, but there is nothing underneath it. Put the rounded clip on V2 and a background on V1, or render to an alpha-capable format when the next application needs transparency. ### The entire clip disappears Select Rectangle1 and reset Width, Height and Center. Confirm that **Invert** is off and that the mask feeds MediaIn1’s blue input. A tiny, inverted or off-screen Rectangle can hide the whole frame. ### The curves turn into ovals A non-uniform transform is happening after the mask. Move the stretch or aspect-ratio change before Rectangle1, then set the mask at the final proportions. ### The edge looks soft Reduce Soft Edge and check the composition at delivery resolution. A small feather can hide aliasing; a large one makes a UI card look out of focus. ### The mask works in Fusion but not in the timeline Make sure you opened the same timeline clip whose Fusion composition you edited. Confirm MediaIn1 still reaches MediaOut1 and that no later Edit-page crop or transform hides the rounded boundary. If this is your first effect built from clip geometry, the [DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/) places it after Inspector basics and before more complex Fusion work. ## Rounded Corners in DaVinci Resolve: FAQ ### Can I round corners in DaVinci Resolve Free? Yes. The native Fusion Rectangle mask, Background, Merge, Transform and basic keyframe controls used here are available in the free edition. ### Why does Corner Radius change when I resize the Rectangle? Blackmagic lays out Corner Radius as a 0.0–1.0 Rectangle control but doesn't define a fixed-pixel formula. In practice, the same value can look different after Width or Height changes. Set final proportions first; use a Shape or expression workflow when dimensions animate. ### Can I apply rounded corners to several clips at once? Yes. Put the shots into a Compound Clip and apply one Fusion Rectangle mask to the compound. Keep them separate if each clip needs different framing or animation. ### Can I round only two corners? Extend the Rectangle beyond the frame so the unwanted curved corners sit outside the visible area. Use multiple masks or Shape tools when every corner needs independent control. ### Why are my rounded corners uneven? Check for non-uniform X/Y scaling after the mask. Apply that scaling before Rectangle1 and build the mask in the final image proportions. ### How do I export rounded video with transparency? Render with a format and codec that expose alpha-channel output in Resolve, enable alpha export, and verify the file over another color. Composite over the final background first when the delivery platform doesn't accept alpha. ### DaVinci Resolve Rotoscoping: Polygon, B-Spline & MultiPoly URL: https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/ Last updated: 2026-09-15T17:03:23.000Z In DaVinci Resolve Fusion, rotoscoping means animating one or more mask shapes to isolate a subject over time. Split independent motion into overlapping Polygon, B-Spline, or MultiPoly shapes, set a clean reference pose, build end and middle poses, then add keys only where interpolation fails. Start with sparse control points and a few key poses. Add shapes for independent motion and more keys wherever the silhouette stops following the plate. ## Choose the right rotoscoping method | Method | Best use | Main limitation | | -------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------- | | Polygon | Hard or mixed edges that need direct Bézier control | Too many points and handles become slow to animate | | B-Spline | Smooth organic curves with fewer control points | The curve is influenced by points rather than passing directly through each one | | MultiPoly | Several named shapes for body parts or a complex holdout inside one node | Shape animation must be enabled before keyframing | | Tracked or stabilized roto | Removing broad camera or rigid-object motion before manual shape work | Tracking does not understand anatomy or changing occlusion | | Magic Mask | A fast AI-assisted first matte for a recognizable person or object | Studio-only and still needs edge, occlusion, and temporal QA | Use a keyer for hair, transparency, and fine edge detail when the plate has usable color separation. The [Delta Keyer guide](https://davinciresolveclub.com/davinci-resolve-delta-keyer/) covers pulling and refining that key. Use roto shapes for solid cores, unwanted regions, foreground occluders, and edges you can define reliably. Checked September 15, 2026 against Resolve 21.1, Blackmagic’s [Fusion overview](https://www.blackmagicdesign.com/products/davinciresolve/fusion?ref=davinciresolveclub.com) confirms the Bézier and B-Spline roto workflow; the current [DaVinci Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) documents the mask inputs, alpha behavior, animation, MultiPoly, Roto Assist, and softness controls used below. ## Plan the matte before drawing Watch the whole shot and write down what changes: frame entry and exit, pose reversals, hands crossing the torso, motion blur, hair movement, and foreground occlusions. Also decide what the matte is for. A rough local color correction does not need the same edge fidelity as a subject cutout placed over a bright contrasting background. Pick a reference frame where the pose is readable and the important edges are sharp. Then divide the subject by independent motion: - head and neck; - torso or coat body; - upper arm and forearm; - hand when its silhouette matters; - upper leg and lower leg; - props, loose clothing, or hair as separate problem areas. Overlap neighboring shapes slightly around joints. A small controlled overlap is easier to manage than a one-pixel gap opening between an upper arm and torso. Name every shape before the shot becomes crowded. ## Manual rotoscoping step by step ### 1\. Add the mask where it can do the intended job First identify the input you're feeding. A blue Effect Mask on most Fusion tools limits that tool’s result to the mask. A mask connected directly to a MediaIn or Loader input can instead add an alpha channel; Blackmagic recommends drawing the closed shape while the mask is disconnected, then connecting it. For an explicit roto-to-alpha branch, connect the source image to MatteControl Background and the Polygon to its gray Garbage Matte input. A garbage matte removes its white region. If you drew around the subject you want to keep, enable Garbage Matte > Invert in MatteControl and check that the subject is white in the output alpha. Its white Solid Matte input instead fills alpha holes; it is not the same operation as cutting away the outside. Feed the resulting image to a Merge node's green Foreground input, the replacement plate to yellow Background, and Merge to MediaOut. Masking Merge's blue Effect Mask limits that merge; it does not create a reusable alpha on the upstream source. Check Post-Multiply Image when preparing the cutout for a premultiplied Merge; do not apply repeated alpha multiplication to an already premultiplied branch. ![Polygon connected to MatteControl Garbage Matte beside the source image input](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc150-mattecontrol-routing.webp) Feed the source image to MatteControl Background and the shape to Garbage Matte. Set Garbage Matte > Invert to keep the subject rather than cut a subject-shaped hole. Official UI crop: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1729. This input distinction explains why an animated outline may appear to do nothing, blank the image, limit only an effect, or produce an unexpected small alpha. Before rebuilding the shape, load the affected node in a viewer, inspect the connected input, and check the matte as white foreground over black. ### 2\. Draw with the fewest points that hold the silhouette Place points at real direction changes: jaw corner, shoulder, elbow, wrist, knee, heel. Let curve handles or B-Spline influence describe smooth sections between them. Don't add points at uniform intervals when the curve doesn't need them. Every unnecessary point is another control that can chatter between frames. Keep each point following the same feature across poses, and avoid crossing the spline. Adding a point fits it into every existing shape keyframe; deleting one removes it from every keyframe. Review the whole animation after changing point count. For soft organic areas, a B-Spline can describe a smooth arc with fewer points. For a hard prop or clothing corner, Polygon gives more direct control. Resolve 21 also includes Roto Assist, which can snap newly drawn points to the nearest high-contrast edge. Multiple Points can add several points along an edge with one click, Distance sets the pixel search range, and Reset clears the snapped state so those points are no longer available for tracking. Treat it as drawing assistance, not an automatic finished matte: review point count, edge choice, and every interpolated pose. ![Roto Assist options for Multiple Points, Distance and Reset](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc150-roto-assist-controls.webp) Use Distance to control how far Roto Assist searches for a high-contrast edge. Inspect the snapped points before building the next pose. Official UI crop: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1741. Roto involves constant viewer navigation and frame stepping. Set up the commands you actually use, full-frame view, next/previous key, and tool search, before a long shot; the [Resolve keyboard shortcuts guide](https://davinciresolveclub.com/davinci-resolve-keyboard-shortcuts-guide/) explains how to verify and customize them without overwriting an existing layout. ### 3\. Build key poses with divide and conquer Close the shape by clicking its first point on the reference frame. Keep Solid enabled for a filled mask rather than an outline. Polygon and B-Spline control points auto-animate by default: move to another frame and adjust the points to create a new shape keyframe. Center and rotation do not auto-animate; enable their Inspector keyframes separately if you use those controls. Move to the end of the required range and fit the silhouette, then go to the midpoint and correct it. Play the two halves. Add another key only in the half that fails, then repeat. The current [Resolve 21.1 manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) notes that Polygon and B-Spline control points auto-animate and interpolate between shape keyframes. ### 4\. Add keys at changes, not every frame Useful keyframes usually sit at a change of direction, a pose extreme, a silhouette change, an occlusion boundary, or the start and end of heavy blur. If interpolation already follows the edge, leave it alone. Adding a key on every frame often creates tiny inconsistent corrections that read as edge vibration during playback. ### 5\. Review the matte, then the composite View the result as white foreground over black background to find holes, gaps, and temporal chatter. Then place it over the actual destination background. A matte can look clean in isolation yet reveal a dark halo over white or a bright fringe over black. ## Use MultiPoly for complex subjects MultiPoly stores several independent named shapes in one node. It is useful for a person, creature, vehicle, or any holdout that would otherwise produce a tangle of separate mask nodes. Create one shape per independently moving part and set its combine behavior deliberately. **Important:** MultiPoly doesn't auto-enable shape animation the way Polygon and B-Spline masks do. Select the animation diamond beside **Right-click here for shape animation** at the bottom of the Inspector, or right-click the label and choose Animate, before changing shapes across time. ![Three separate MultiPoly outlines drawn over the Fusion viewer image](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc150-multipoly-shapes.webp) Use separate shapes for independently moving parts instead of making one outline follow every overlap. Select each shape in the Inspector and enable its shape animation. Official UI crop: Blackmagic Design, Resolve 21.1 Reference Manual, p. 2479. If the animation diamond, combine controls, or per-shape settings are hidden, select MultiPoly and reopen the Inspector rather than redrawing the mask. The [DaVinci Resolve Inspector guide](https://davinciresolveclub.com/davinci-resolve-inspector/) covers panel state and control discovery across pages. During the rough pass, fit the main masses with minimal points. Select each shape and confirm that edits at a second frame produce a distinct keyframe before continuing the shot. Use Modify Only to move existing points without accidentally adding new ones. It still allows deletion, so check earlier keys if you remove a point. ## Track broad motion before detailed roto If the subject or camera translates, rotates, or scales while local deformation is modest, track the broad motion first. Track a rigid feature or plane, remove its motion, animate the roto on that steadied image, then apply the original motion to the matte. For Planar Tracker, Steady is the mode intended for a locked-off paint or roto view; Stabilize smooths camera movement and is not the same operation. This is not a shortcut for every shot. It works when the tracking data describes the same rigid motion as the body part or object you're isolating. A tracker attached to the torso won't correctly animate a swinging forearm. Use tracking for the base movement and manual keys for deformation. Keep the inverse transform and the re-applied transform paired. If the mask or image receives both tracked motion and a second Planar Transform, it can drift or move twice. The [Fusion tracking guide](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/) covers reference frames, Planar Transform, occlusion masks, and drift checks in detail. ## Handle occlusion as layers When a hand crosses the torso, don't force one torso outline to describe both depths. Keep the torso matte stable and animate the hand as a separate foreground shape. If you are combining separate takes of the same performer, the [clone-effect workflow](https://davinciresolveclub.com/clone-yourself-davinci-resolve/) covers shooting and compositing those takes; the roto here only supplies the matte. When a subject passes behind a pole, make a separate holdout matte for the pole and use it to remove that foreground region from the subject result. The pole must remain visually in front; changing the label or mask color doesn't change the composite order. If the tracked feature becomes hidden, stop at its last reliable frame rather than accepting drift. Track the visible sections separately or use another feature with the same rigid motion. Keyframe the necessary transition and inspect the join. An occlusion mask can exclude an obstruction from a planar track, but it cannot recover an entirely hidden surface. If Studio is available, [Magic Mask](https://davinciresolveclub.com/davinci-resolve-magic-mask/) can create a fast first pass for the recognizable subject. Keep manual shapes for corrections and hard holdouts. Don't treat an AI matte as finished simply because the first frame looks good. ## Refine edges only after motion is stable ### Soft Edge Match the plate's focus and edge contrast. A sharp prop may need almost no softness; defocused clothing needs more. Excessive global feather can produce halos or lose detail. For local softness, click Double Polyline or choose Make Outer Polyline from the mask's viewer menu. Press Tab to select the dashed outer contour, then move only the segments that need a wider falloff. Adjust the outer contour, not the inner subject outline. ![Inner and outer polyline contours controlling local softness around a subject](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc150-double-polyline-edge.webp) Select the outer contour and move only the segments that need a wider falloff. Keep sharp edges close to the inner contour. Official UI crop: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1742. ### Motion blur A moving hand can have a blurred edge even when the torso remains sharp. Fit the matte to the photographed boundary and use the outer polyline where a local falloff is enough. For a mask animated in Fusion, its Settings tab also has Motion Blur, Quality and Shutter Angle controls. Motion Blur samples the mask's animated movement; it does not recover missing detail from the footage. Increase Quality only when the blur needs smoother sampling, and judge Shutter Angle against the plate rather than assuming one value fits every shot. If a separate element is match-moved, add motion blur from the transform that actually drives that element and compare direction and extent with the plate. ### Combine modes For chained masks, Merge is the default Paint Mode; Maximum keeps the higher mask value in an overlap. Add sums values and can make overlapping soft edges more opaque, so it is not an interchangeable default. Use Subtract for holes or excluded regions and inspect the combined matte. MultiPoly also gives each shape its own combine controls. Names such as Torso, Arm\_FG, and Coat\_Hole help you identify the shape that needs correction. ### Hair and transparency Roto the solid core of the head and shoulders. Preserve flyaway hair with a keyer, Magic Mask, or a separate edge matte when possible. Drawing each strand is slow and rarely temporally stable. ## Resolve Free vs Studio for rotoscoping Resolve Free includes the manual masks, keyframing, conventional point tracker and Planar Tracker used in this workflow. You do not need Studio to draw, animate or combine these mattes. This does not mean every Fusion tracking tool is free; the 3D Camera Tracker is a separate Studio feature and is not required here. Magic Mask requires DaVinci Resolve Studio. Blackmagic’s [Resolve Studio page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) confirms the edition boundary. It can reduce first-pass labor on people and recognizable objects, but it does not remove the need to check every cut, edge, occlusion, and motion-blurred frame. Use the [Fusion hub](https://davinciresolveclub.com/davinci-resolve-fusion/) to place the manual roto workflow inside a complete node-based composite. ## Rotoscoping troubleshooting ### The edge chatters Remove unnecessary points and keyframes. Return to the first meaningful deviation, fix that pose, and let interpolation carry more frames. Watch at normal speed instead of correcting harmless single-frame texture. ### A limb disappears or a gap opens Split the limb into its own shape and overlap it slightly with the torso or neighboring segment. Check the shape’s combine mode, animation state, and active frame range. ### The MultiPoly shape does not animate Enable the shape-animation diamond at the bottom of the Inspector. Then create distinct poses on different frames and confirm key indicators appear. ### The mask is tiny or offset Compare the source and mask image dimensions, pixel aspect ratio, Domain of Definition, and any Transform, resize or tracking operation between them. Display the same reference frame on both branches. A matte built on a steadied image must receive the matching motion exactly once before it is applied to the original moving plate. ### The matte works in Fusion but fails after an edit Check the clip’s Global In/Out, source timing, retime, and Fusion composition range. A slip, trim, or copied mask on a different-resolution clip can separate existing shape keys from the intended frames. ## Final roto QA checklist - Scrub the matte in black and white for holes and shape pops. - Watch the full shot at normal speed for chatter. - Check every occlusion, frame entry, frame exit, and direction change. - Inspect hard, soft, blurred, and transparent edges against the final background. - Confirm the matte is connected to the intended node or alpha operation. - Render a short test and inspect it outside the interactive Fusion viewer. Roto makes more sense after node and tracking basics; the [DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/) keeps those Fusion skills in a practical order. ## Rotoscoping in Fusion FAQ ### What is rotoscoping in DaVinci Resolve? Rotoscoping is the animation of masks or mattes over time to isolate a subject for compositing, correction, removal, replacement, or foreground holdout work. ### Should I use Polygon, B-Spline, or MultiPoly? Use Polygon for direct Bézier control, B-Spline for smooth organic curves with fewer points, and MultiPoly when one complex subject needs several named independent shapes in a single node. ### How many mask points should I use? Use the fewest points that describe real changes in curvature. Place them at joints and silhouette corners, then let curves handle the sections between them. ### Do I need to keyframe every frame? No. Build start, end, and middle poses, then add keys only where interpolation fails. Every-frame corrections are appropriate only for genuinely unpredictable motion or brief difficult sections. ### Can I rotoscope in DaVinci Resolve Free? Yes. Resolve Free includes the core manual masks, MultiPoly, keyframing, and tracking tools needed for rotoscoping. Magic Mask requires Studio. ### Why does a Polygon mask not make the background transparent? A blue Effect Mask on most Fusion tools limits that tool’s effect. A mask connected directly to MediaIn or Loader can add alpha, while MatteControl provides an explicit branch for combining or inverting mattes. Check the node and input type before rebuilding the shape. ### How to Update DaVinci Resolve Safely URL: https://davinciresolveclub.com/update-davinci-resolve-safely/ Last updated: 2026-09-15T16:20:44.000Z The rule is simple: the new build must not touch the only recoverable copy. Export every active project, back up the whole Project Library, protect media and custom assets, then open an imported test copy. If any recovery layer is missing, the update waits. The installer is rarely the dangerous part. The risky moment is opening a project in a newer version and discovering that an older build, a plug-in, a GPU driver, or a collaborator’s workstation can no longer reproduce it. A safe update creates a rollback path before Resolve changes any project data. Use this maintenance checklist alongside the [DaVinci Resolve learning path](https://davinciresolveclub.com/davinci-resolve-tutorial/). It covers changing an existing installation safely, rather than a first-install walkthrough or a guide to locating lost projects. ## Check the Exact Release Before Opening Projects Checked September 15, 2026: Blackmagic’s official stable-download feed returns [DaVinci Resolve 21.1, build 14](https://www.blackmagicdesign.com/api/support/latest-stable-version/davinci-resolve?ref=davinciresolveclub.com), and its release notes are dated September 8\. The [21.1 pre-install notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) say Blackmagic made efforts to keep Project Libraries compatible with Resolve 20.3.2\. Individual projects created or opened in 21.1 are no longer accessible in 20.3.2\. Library access and project compatibility are different checks. Don't test that boundary by opening the only copy of a live Resolve 20 project. Export a pre-update DRP, make the full library backup, install 21.1 only after both are verified, import the DRP under a new test name, and open that copy. Keep the untouched pre-21 project and backup as the rollback source. Recheck the build and edition on the [official Resolve support page](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) on the day you update. The September 15 receipt identifies the build verified for this guide, not a permanent promise that it remains the newest. Read the pre-install notes for that exact download. A point release can still affect project or library compatibility. ## DRP, Project Library Backup, and DRA Are Not Interchangeable | Backup | Protects | Does not automatically protect | | ---------------------- | ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | Export Project (.drp) | One project’s data; Gallery stills and LUTs only with Export Project With Stills and LUTs | Source media, fonts, plug-in installers, shared assets | | Project Library backup | The library/database containing many projects and folders | External media and most system-level custom assets | | Project Archive (.dra) | A project plus copied media chosen for the archive | Third-party plug-ins, fonts, licenses, every external dependency | | Project Backups | Timed earlier states of a project | A failed system drive or library if stored beside the originals | The current [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) separates these recovery layers. A normal DRP has no source media and excludes Gallery stills and LUTs; Export Project With Stills and LUTs adds those project assets, not the camera originals. A library backup and a DRA solve different scopes. ## When to Delay an Update Don't change Resolve, the operating system, the GPU driver, and core plug-ins in the same maintenance window. If something breaks, that creates four suspects and no clean baseline. Delay the update when: - a delivery is due before there's time for a full test; - the project depends on an unverified OpenFX, audio plug-in, control panel, script, or codec; - another editor must keep using the older version or a shared library; - the exact update doesn't solve a bug or add a feature the job needs; - the build is a beta and the project is production-critical. “There's an update notification” isn't a production reason. Finish the job on the known build, or clone the workflow and test away from the delivery path. ## Record the Working Baseline Before changing anything, make a short reference render and a plain checklist containing: - Resolve edition, full version, and build number; - operating system version and hardware architecture; - GPU model, VRAM, and driver version where applicable; - active Project Library name and whether it's Local, Network, or Blackmagic Cloud; - third-party OpenFX, audio plug-ins, Fusion tools, scripts, and control panels; - project frame rate, color management, audio buses, and a known render preset; - fonts, LUTs, DCTLs, macros, title templates, Power Bins, and keyboard presets the job uses. Don't put Studio activation codes, passwords, or license secrets in screenshots or shared notes. Record only what you need to identify the installation. ## Confirm Live Save and Project Backups Open DaVinci Resolve > Preferences > User > Project Save and Load. **Live Save** is enabled by default and incrementally writes the current state. **Project Backups** must be enabled separately; they create periodic complete project files but exclude stills and LUTs. Loading one later opens an independent project rather than overwriting the original. Timeline Backups are another separate switch: use them when you need restore points for an individual timeline, but don't count them as a backup of the full project or library. Neither replaces a manual export. The [guide to saving work in DaVinci Resolve](https://davinciresolveclub.com/how-to-save-work-davinci-resolve/) explains the different roles of manual saves, Live Save, Project Backups, and DRP exports. Live Save can faithfully preserve a bad change, and automatic backups stored on the failed system drive can disappear with it. Put the backup destination on independent reliable storage with enough space, then make and test the DRP and library backup anyway. ![Project Backups window listing dated recovery points and the Load control](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc149-project-backups.webp) Load a dated Project Backup as an independent project, then verify it before upgrading. Official UI from Blackmagic Design, Resolve 21.1 Reference Manual, p. 88. ## Export Every Active Project as DRP 1. Open Project Manager. 2. Right-click the active project. 3. Choose **Export Project**. 4. Name the file with the project, working Resolve version, and date, such as `Documentary_R20.3.2_pre_R21.1_2026-09-15.drp`. 5. Save it outside the live Project Library and preferably off the system drive. 6. Repeat for every project you can't afford to lose. For important work, import one exported DRP into a separate test library under a new name before updating. Confirm that it opens and contains the expected bins, timelines, grades, Fusion comps, and Fairlight structure. If the job depends on Gallery stills or LUTs, use Export Project With Stills and LUTs and verify those too. A file that has never been imported is an unverified backup. ## Back Up the Entire Project Library For a Local or Network library, close the open project, show Project Libraries in Project Manager, select the exact library, click the circled details icon, and choose Back Up. Save the .resolve.backup file away from the live library. Use Restore to create a separate test library with a new name and location, then inspect its projects before retiring the old setup. For a managed Network library, coordinate with its administrator; the Project Server application also provides Back Up and Restore. A library backup protects projects you forgot to export individually and preserves library-level organization. The .drp exports remain valuable because they give you small, direct recovery units if the library itself becomes unhealthy. Cloud libraries use a different destination. The [Cloud backup procedure in the Resolve 21.1 manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=4178) uses Project Manager’s Cloud library Details > Back Up and confirms that the backup was made to Blackmagic Cloud. Details > Restore lets you choose a backup and assign a new library name. Have the owner or administrator verify a separate restored copy, and keep exported DRPs and media outside the Cloud library too. A Cloud library backup is not a downloaded .resolve.backup file. ![Cloud Project Manager showing cloud libraries and project thumbnails](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc149-cloud-library.webp) Confirm the Cloud library before coordinating the team update. Use its Details controls to back up in Blackmagic Cloud, and export offline DRPs separately. Official UI from the Resolve 21.1 Reference Manual, p. 4173. Never delete a library, replace database internals, or overwrite the original to make room for an update. Restoring to a new name and location keeps both recovery paths available. If you aren't sure which library contains the project, the [guide to where Resolve projects are saved](https://davinciresolveclub.com/where-davinci-resolve-projects-saved/) explains Local, Network, and Cloud libraries without encouraging manual edits inside them. ![Project Library details with an upgrade-required warning and Upgrade control](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc149-library-upgrade.webp) Stop at an upgrade warning until a library backup and exported projects have been test-restored. This illustrative warning comes from the Resolve 21.1 Reference Manual, p. 84; its displayed schema date is not your installed app version. ## Protect Media and Custom Assets Original camera files, audio, graphics, and deliverables should already exist independently of Resolve. Confirm that backup rather than assuming proxy, cache, or optimized-media folders are the originals. For a portable critical project, choose Export Project Archive. Select Media Files when camera originals must be included; Proxy Media alone protects proxies, not those originals. Choose Render Cache only when you need it. Resolve 21.1 adds archive options for stills, LUTs and used media, so review every option in your installed build rather than assuming an older dialog contains the full list. A DRA is a folder, not a substitute for plug-ins, fonts, licenses or every external dependency. Use Restore Project Archive to test a separate copy and inspect its media before treating it as cold storage. Back up custom dependencies separately: - LUTs and DCTLs; - Fusion macros, scripts, templates, and third-party toolsets; - fonts and title packages with their licenses; - audio plug-ins, impulse responses, and sound libraries; - keyboard presets and workspace layouts; - render presets and delivery notes; - plug-in installers and license-manager information without exposing credentials. ![Archive Settings with Media Files, Render Cache and Proxy Media choices](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc149-archive-options.webp) This official example selects only Proxy Media. For an originals backup, include Media Files instead of copying this selection. Resolve 21.1 Reference Manual, p. 215; inspect the additional archive choices in your installed build. ## Download the Correct Installer Use Blackmagic’s support page, not a download mirror. Match all three variables: operating system and architecture, DaVinci Resolve Free versus DaVinci Resolve Studio, and the exact stable build you intend to test. In Resolve, choose DaVinci Resolve > Check For Updates to check and download an available build; use the support page when you need to select the exact edition, platform, or older installer. Blackmagic currently lists packages for macOS, Windows, Windows for Arm, and Linux; choose the one that matches the system you actually tested. Keep the previous working installer in the recovery folder. Read minimum requirements and release notes before installation, especially GPU and operating-system requirements. The [current Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) help identify a machine that shouldn't be moved to the new build yet. Keep the distribution channel consistent on a Mac. Update a Mac App Store installation through the App Store; use Blackmagic’s installer for its direct-download edition. Do not assume both channels offer the same build on the same day. The [official Studio App Store listing](https://apps.apple.com/us/app/davinci-resolve-studio/id900392332?mt=12&ref=davinciresolveclub.com) warns that some control panels and third-party OpenFX or VST plug-ins may be unsupported. A Store purchase is a separate license, not an activation key for the direct installer; [Blackmagic’s edition matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5FStudio%5F20%5FFeatures.pdf?ref=davinciresolveclub.com) documents that channel restriction in its July 2025 Resolve 20 edition. Check your purchase channel before switching distributions. If the installer also offers control-panel or Desktop Video components, change them only when the release notes and hardware workflow require it. One maintenance variable at a time makes rollback understandable. For direct downloads, unpack the downloaded package and run its DaVinci Resolve installer. On macOS, open the disk image and double-click the installer icon; do not substitute a drag-to-Applications instruction. On Windows, run the extracted installer. On Linux, run the supplied installer on a supported system. The [21.1 platform installation instructions](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) say to follow the onscreen installer prompts on all three platforms. Finish the backup and restore test before approving installation. ## Install, Then Test an Imported Copy 1. Close Resolve and any dependent plug-in managers or Project Server administration tools. 2. Install according to Blackmagic’s instructions for the exact operating system and build. 3. Launch Resolve and confirm the edition and build number. 4. Create or use a separate test library. 5. Import the pre-update .drp with a name that clearly marks it as the Resolve 21 test. 6. Open only that copy first. For a Network or Cloud library, appoint one person to control the update and agree the target Resolve build before anyone opens production projects. Matching the team’s build is a conservative maintenance rule, not a claim that every version difference blocks connection. Match plug-ins, fonts and media access too. Cloud creation includes a Resolve-version choice, and library upgrades are performed in Resolve, not the web interface. Follow the [Cloud project-library instructions](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=4175) and the exact release’s compatibility note, not a blanket rule that all major releases upgrade libraries or all point releases are safe. Keep three version numbers separate: the Resolve application, the Project Library schema, and the database engine used by a Network library. Resolve 21.1’s notes say Project Server now bundles PostgreSQL 18 while Resolve and Project Server still work with Network libraries based on PostgreSQL 13 and above. That is not an instruction to migrate a working database engine during the app update. Let the administrator plan any server migration independently. ## Run a Real Post-Update Test Opening the project without an error is only the first checkpoint. Test a representative timeline containing the parts most likely to break: - online and relinked source media; - camera RAW and 10-bit codecs; - Text, Text+, subtitles, and third-party fonts; - OpenFX and audio plug-ins, including license state; - Color management, LUTs, DCTLs, grades, and stills; - Fusion comps, macros, and cached effects; - Fairlight buses, automation, plug-ins, and channel mapping; - hardware decode/encode and the normal delivery codec; - control panels, audio interfaces, and monitoring output. Render the same short range you saved before the update. Compare picture, audio, duration, frame rate, and file properties. Close Resolve, reopen it, and open the test project again. A clean first launch isn't enough. ## Rollback Without Damaging the Only Copy If the update fails, stop experimenting on the live library. Preserve logs and screenshots of the exact error, then separate the failure: - **Application won't launch:** verify OS and GPU requirements, then follow Blackmagic’s platform-specific uninstall/reinstall guidance. - **Project doesn't open:** return to the older application and the untouched pre-update .drp or restored library copy. - **Plug-in is missing:** verify vendor compatibility and licensing before replacing the effect in a duplicate. - **Media is offline:** reconnect storage and paths; don't overwrite a healthy library with an empty one. - **Playback or export changed:** compare GPU preferences, drivers, decode settings, caches, and the pre-update reference render. A project opened in Resolve 21.1 is not a rollback asset for Resolve 20.3.2\. A safe downgrade starts from the untouched pre-update project, verified DRP, and Project Library backup. If GPU memory or decoding becomes the failure point, use the [GPU memory troubleshooting guide](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/) before changing several system components at once. ## Resolve Free vs Studio Updates Free and Studio are separate downloads. Install the edition you actually use. Accidentally replacing Studio with Free can make Studio-only effects and codecs appear unavailable even though the project data still exists. Studio can be licensed by activation code, dongle, or an assigned [Blackmagic Cloud license](https://help.cloud.blackmagicdesign.com/license-manager/logging-in-to-davinci-resolve/?ref=davinciresolveclub.com). Keep licensing material secure and available before maintenance; never place activation details in a project note, screenshot, or support post. ## Common Update Problems ### Projects are missing after the update Open Project Manager and inspect which Project Library is connected. Reconnect the original library or import a .drp; don't create projects in an empty library and assume the old one was erased. ### Resolve asks to upgrade or change a library Cancel until the full library backup and individual DRP exports exist. A library that remains connectable in 20.3.2 does not make a project opened in 21.1 accessible to 20.3.2. ### A plug-in has a watermark or is unavailable Confirm that you installed the same Resolve edition, compatible plug-in build, architecture, and license. Test on a duplicate before removing or replacing nodes. ### Resolve crashes after updating Preserve logs, check the exact release notes and requirements, and test whether the problem is [application launch, GPU initialization, a plug-in, or one project](https://davinciresolveclub.com/davinci-resolve-keeps-crashing/). The broader [Resolve crash guide](https://davinciresolveclub.com/fix-davinci-resolve/) keeps those branches separate. ### Exports look different Compare the saved render preset, color management, GPU decode/encode settings, plug-ins, LUTs, audio buses, and the pre-update reference file. Rebuild no settings until you identify the first mismatch. ## The Go/No-Go Check Move live work to the updated build only after the imported test copy opens twice, all media is online, plug-ins load, Color and Fusion results match, Fairlight routing survives, and a known render matches the checkpoint. Keep the pre-update backups and installer until the project is delivered and archived. Update for a feature, fix, or compatibility need you can name. The [Resolve 21 changes guide](https://davinciresolveclub.com/davinci-resolve-21-whats-new/) helps decide whether the benefit is worth entering the maintenance window now. After the update passes the test project, return to the [DaVinci Resolve tutorial roadmap](https://davinciresolveclub.com/davinci-resolve-tutorial/) and verify the editing, Fairlight, Fusion, and export workflows you actually depend on. ## Safe Resolve Update FAQ ### Will updating Resolve delete my projects? An update shouldn't delete projects, but libraries can disconnect, projects can change compatibility, and failures happen. Export active projects and back up the Project Library first. ### Is a .drp file enough? No. A standard DRP protects one project’s data, not source media, Gallery stills, LUTs, fonts, third-party plug-ins, scripts, licenses or the other projects in the library. Export Project With Stills and LUTs adds those named assets, but you still need media and library backups. ### Can Resolve 20 open a project saved in Resolve 21? Don't rely on it. Blackmagic’s Resolve 21.1 notes say a library can remain accessible in Resolve 20.3.2, but any project created or opened in 21.1 is no longer accessible in 20.3.2\. Preserve a pre-update DRP and Project Library backup before opening the project. ### Should I uninstall the old version first? Follow the release notes and installer instructions for the exact operating system and build. Preserve the previous installer and verified backups before changing application state. ### Where should I store backups? Outside the live Project Library and preferably off the system drive. Important work should have another copy on independent storage. ### Should I update during an active project? Only when the update solves a blocking problem and there's time to test and roll back. Otherwise finish the delivery on the known build. ### Voice Isolation vs Dialogue Leveler in DaVinci Resolve URL: https://davinciresolveclub.com/voice-isolation-vs-dialogue-leveler/ Last updated: 2026-09-15T15:29:07.000Z **Quick answer:** Voice Isolation separates a recorded human voice from competing sound; Dialogue Leveler rides loud dialogue down and soft dialogue up. Voice Isolation requires DaVinci Resolve Studio, while Dialogue Leveler is available on desktop in both Free and Studio. Match obvious clip-gain differences first, isolate only when noise masks speech, level second, then EQ or compress only if the mix still needs it. These tools sit close together in the Audio Inspector, but they solve different problems. If the problem is an air conditioner, crowd, traffic, or room sound, test Voice Isolation and use the [broader Resolve background-noise workflow](https://davinciresolveclub.com/remove-background-noise-davinci-resolve/) when hum, broadband noise, or other repair needs a different tool. If the speaker turns away from the microphone or two people land at different levels, test Dialogue Leveler. If only two words are wrong, manual gain is usually cleaner than either processor. ## Voice Isolation vs Dialogue Leveler | Tool | Problem it solves | Controls | Edition | | -------------------------- | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | --------------- | | **Voice Isolation** | Background ambience, noise, music, or competing sound around a voice | Enable and Amount 0–100% | Studio | | **Dialogue Leveler** | Speech that varies too much between phrases or speakers | Preset, Reduce Loud Dialogue, Lift Soft Dialogue, Background Reduction, Output Gain 0 to +6 dB | Free and Studio | | **Clip gain / automation** | A few predictable level jumps or words needing editorial judgment | Clip gain, keyframes, fader automation | Free and Studio | | **Compressor** | Remaining dynamics needing threshold-, ratio-, and timing-based control | Threshold, ratio, attack, release, makeup gain | Free and Studio | Checked on September 15, 2026 against the September 2026 [DaVinci Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=4014), these instructions cover desktop Resolve on macOS, Windows and Linux. The manual labels Voice Isolation as Studio-only and documents Dialogue Leveler separately without that restriction. Ordinary clip and Track FX instances process existing recordings, not a general live input. The dedicated Cut page Voiceover Tool is a separate recording path that can apply Voice Isolation and Dialog Leveler as it records. That exception does not make these effects a general live-stream noise filter. ## What Voice Isolation Actually Does Voice Isolation uses an AI model trained for human voices to separate recorded speech from competing sound. Amount is a wet/dry blend: at 50, the original and isolated voice are roughly equal. Blackmagic recommends 70–80 as a useful natural-sounding range while strongly isolating the source, but that's a starting range, not a target every recording should reach. Push only until the background stops masking the words. Voice Isolation supports mono, stereo and dual-mono audio tracks, not tracks with more than two channels. Clip controls also depend on the selected source and its channel configuration; putting a multichannel source on a mono track does not by itself prove that its clip controls will be available. Resolve 21.1 documents Voice Isolation in the Cut page Voiceover Tool during recording. For existing material, keep the original media and an unprocessed timeline copy so you can return to the recorded sound. Separation does not guarantee usable words when clipping, a siren or another voice covers the speech. Audition the hardest recoverable line, raise Amount only until competing sound stops masking words, then compare bypass at matched loudness. Keep enough stable ambience for the cut to sound continuous. If consonants smear, room tone pumps, or the voice turns watery, split the difficult section or reduce Amount instead of treating 70–80 as a target. ![Voice Isolation plugin with its enable control and Amount blend slider](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc148-voice-isolation.webp) Compare enabled and bypassed on the same phrase; Amount blends the original and isolated voice. Official interface crop: Blackmagic Design, Resolve 21.1 Reference Manual, p. 774. ## What Dialogue Leveler Actually Does Dialogue Leveler analyzes dialogue, rides louder areas down, lifts softer areas, and can lower background it classifies as non-dialogue. It aims for the result of detailed clip-gain or fader work without forcing you to draw every move, while preserving more of the original relative dynamics than simply crushing the track with a limiter. The real controls matter: - Preset: In the Edit/Fairlight documentation, Allow wider dynamics is the default for medium-to-high material with wider loud-to-soft changes. More lift for low levels suits quiet dialogue; Lift soft whispery sources addresses whispered dialogue with background noise; Optimize moderate levels suits material at medium levels throughout. Choose by source, not as a quality ladder. - **Reduce Loud Dialogue:** rides peaks in louder speech downward. - Lift Soft Dialogue: an on/off switch that raises low-level dialogue. Background occurring at the same time as speech may rise too; listen for newly exposed breaths or mouth noise. - **Background Reduction:** gently lowers non-dialogue sound according to the analysis and preset. It isn't the same separation process as Voice Isolation. - **Output Gain:** adds 0 to +6 dB after leveling. It isn't a target-loudness control. Dialogue Leveler is designed to retain relative dynamics while increasing intelligibility and average level, but the editorial goal still sets the boundary. A wide shot may need to sound more distant than a close-up, and a whisper shouldn't automatically match a shout. Like Voice Isolation, it works on existing mono, stereo, or dual-mono material; ordinary clip and Track FX instances can't process a general live audio input, and tracks above two channels are unsupported. The Cut page Voiceover Tool can apply Dialog Leveler during recording. Its label uses Dialog rather than Dialogue in parts of the manual. This guide does not extend desktop Inspector or Mixer instructions to the iPad interface. ![Dialogue Leveler track plugin with processing waveform, preset and three switches](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc148-dialogue-leveler.webp) The processing waveform belongs to the track plugin; Lift Soft Dialogue is a switch, while Output Gain sets the resulting level. Official interface crop: Blackmagic Design, Resolve 21.1 Reference Manual, p. 4015. ## Where to Find the Controls On the Edit or Fairlight page, select the audio clip, open Inspector, then Audio, and enable the required module. Preset documentation is inconsistent: the Cut and Edit Inspector summaries on pages 743 and 928 list Optimized for most sources as the default in a three-preset menu. The detailed plugin sections on pages 775, 1116 and 4015 list four presets with Allow wider dynamics as default. The descriptions above follow those detailed sections, not a verified universal menu. Check the labels in your installed build and chosen clip or track panel. For track-wide treatment, open the Fairlight Mixer. If its Track FX section is hidden, use the Mixer's three-dot menu and select Track FX. The [manual's Track FX instructions](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=4014) put Voice Isolation and Dialogue Leveler at fixed dedicated points, visible by default when that section is shown. Visible Track FX controls which modules appear. Dialogue Leveler's scrolling processing waveform belongs to the track plugin, not its clip Inspector version. ![Fairlight Mixer menu with Track FX and Visible Track FX controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc148-mixer-menu.webp) If the track processors are hidden, reveal Track FX from the Mixer menu. Official interface crop: Blackmagic Design, Resolve 21.1 Reference Manual, p. 4014. Clip processing is safer when only a few shots have noise or level problems. Track processing is convenient when one microphone and environment remain consistent. Don't apply a track-wide setting to a lane that mixes lavs, booms, phone recordings, and room tone unless you've auditioned every transition. If controls are missing, check the installed edition, select one eligible audio clip and confirm its source channels and track format. Test a separate mono or stereo clip first. Do not unlink a working edit or remap channels blindly; preserve sync and channel assignments. ## Best Processing Order When You Need Both 1. **Listen raw.** Mark noise, level jumps, clipping, overlap, and unusable words across the entire scene. 2. **Edit first.** Choose the cleaner microphone or take, remove covered words where possible, and split clips when conditions change radically. 3. **Match gross clip gain.** Bring edit-to-edit differences into the same working neighborhood without flattening performance. 4. **Apply Voice Isolation only where needed.** Raise Amount until the noise stops masking speech, then back off if the voice loses texture. 5. Add Dialogue Leveler. Choose the preset matching your source from the labels available in your panel; the detailed manual describes Allow wider dynamics as one baseline option. Enable only the modules that solve a heard problem. Output Gain is not a target-loudness control. 6. **Shape tone.** Use the steps in our [dialogue EQ guide](https://davinciresolveclub.com/fairlight-eq-dialogue/) after restoration so you're not boosting noise the isolation stage will later remove. 7. **Control remaining dynamics.** Add light compression or automation only if the leveler hasn't already done enough. 8. **Mix in context.** Restore room tone, music, and effects around the cleaned voice. 9. **Measure the final bus.** Use the [LUFS and true-peak workflow](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/) after all processing. This is a listening and adjustment sequence, not a promise that enabling effects in that order rearranges their signal path. Voice Isolation and Dialogue Leveler have fixed dedicated Track FX positions; the Mixer Order control for ordinary inserts, Dynamics and EQ does not move those Track FX slots. Keep clip and track processing distinct, and avoid unintentionally applying the same treatment twice. Track Trim is after Track FX, as manual page 3940 explains; neither track Trim nor the track fader should be treated as an input-gain control for these processors. ## Clip-Level or Track-Level Processing? | Scope | Use it when | Risk | | ---------------- | ----------------------------------------------------------- | ------------------------------------------------------- | | **Clip** | Noise, mic position, or speaker changes between edits | Different settings can make room tone jump at every cut | | **Track** | One consistent microphone, speaker, and environment | A single setting may overprocess exceptional clips | | **Split tracks** | Boom, lav, phone, ADR, and narrator need separate treatment | More routing work, but clearer control and automation | If you split speakers or microphones across tracks, name and color them before adding effects. Keep dialogue, room tone, music, and effects on intentional buses; our [Fairlight bus-routing tutorial](https://davinciresolveclub.com/fairlight-bus-routing/) prevents a cleaned voice from accidentally feeding the wrong print master. ## Compare Bypass at Matched Loudness Keep the source file unchanged and render tests to a new filename. Toggle the effect's enable/bypass control on the same phrase and compensate output or monitor level so the perceived loudness is close. A louder result can seem clearer even when it has more artifacts. Listen for consonant edges, sibilance, room tails, breaths and transitions into silence. Test four places, not one easy loop: the noisiest sentence, the softest line, a loud line, and an edit where the microphone or room changes. Then render the hardest 20–30 seconds and listen outside Resolve on headphones, speakers, and a small mono-compatible device. If playback becomes unreliable after enabling an effect, bypass that instance and compare the same passage. Keep approved settings noted, then re-enable and check a short export before delivery. No fixed CPU percentage or render-speed gain applies to every computer, source and processing chain. ## When Neither Tool Is the Right Fix - Clipped recording: do not expect these tools to repair recording overload. Try an unclipped microphone or take before pushing isolation harder. - **Covered speech:** a horn, clap, or second voice may occupy the same time-frequency region as the word. - Very distant microphone: reducing room sound does not guarantee the natural detail of a closer recording. - **A few bad words:** clip gain or automation is faster and more transparent. - **Music or effects:** these dialogue tools can mistake sung or speech-like material for the target. - **Mixed program master:** process dialogue stems before the final mix whenever possible. For missing or covered words, alternate takes, lav/boom choice, ADR, captions, or an editorial rewrite may be more honest than extreme restoration. The goal is intelligibility without pretending the source contains information it does not. ## Free vs Studio: The Correct Answer On desktop, Dialogue Leveler works in Free and Studio; Voice Isolation requires Studio. The [current Studio overview](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) lists Voice Isolation among its paid audio tools. Blackmagic's [Studio and iPad feature matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5FStudio%5F20%5FFeatures.pdf?ref=davinciresolveclub.com) marks desktop Dialogue Leveler Yes and Voice Isolation Studio on page 9\. That matrix is dated July 2025 for Resolve 20, not 21.1; it corroborates the edition split in the current manual rather than proving every current interface detail. Dialogue Separator is a different Studio tool with independent dialogue, background and ambience levels. The Resolve 21.1 manual still calls it mono-only: stereo sources need separate processing of the two mono channels. Do not confuse that limit with Voice Isolation and Dialogue Leveler's mono/stereo support. ## Troubleshooting Artifacts ### The voice sounds watery or robotic Reduce Voice Isolation Amount and compare the same difficult section with bypass. Keep enough stable room tone for adjacent edits to match. If the words are still smeared or metallic, prefer a cleaner take or microphone over a stronger setting. Do not enable Dialogue Leveler's Background Reduction automatically just because isolation is on; audition whether a second background-reduction stage helps. ### Breaths and mouth noise surge Disable Lift Soft Dialogue for that clip, then correct the quiet phrase or offending breath manually. It is a switch, not an amount slider. If the added noise occurs with speech, compare a different preset and the isolation setting rather than assuming Output Gain can change the balance between voice and noise. ### Noise changes at every edit Use different clip-level settings for different microphones and locations, then bridge cuts with matching room tone and short crossfades. One track-wide value cannot make unrelated rooms identical. ### Dialogue Leveler pumps Match clip gain first, choose a gentler preset, and inspect any [dialogue compressor settings](https://davinciresolveclub.com/fairlight-compressor-dialogue/) or limiters later in the chain. Stacking two aggressive level-control stages can exaggerate movement. ### The last word is cut or fades strangely Check whether the original edit cuts through a word, breath or room tail. Extend handles only where source media exists, then compare with both processors bypassed. If the raw ending is intact but the processed one is not, back off the processing or use a manual edit; do not assume the problem is missing source audio. ### The processed export differs from playback Render a short WAV test from the correct bus, reimport it, and compare phase, channel layout, and level. Our [audio export checklist](https://davinciresolveclub.com/export-audio-davinci-resolve/) covers bus and channel-selection mistakes. ## Final Dialogue QA - Listen to every processed edit at normal speed. - Compare bypass at matched loudness. - Check breaths, S sounds, plosives, and word endings. - Listen for ambience opening and closing around speech. - Confirm intentional distance and performance dynamics remain. - Check downstream EQ, compression, limiter, and bus routing. - Render and reimport the hardest passage. - Measure final loudness and true peak only after the mix is complete. Voice Isolation should make the background less distracting. Dialogue Leveler should make the performance easier to follow. If the tool itself becomes the first thing you hear, it is doing too much. Use the [DaVinci Resolve Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) to connect cleanup with routing, EQ, compression, export, and loudness checks. For licensing decisions outside this pair of tools, continue with the [DaVinci Resolve Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/). ## Voice Isolation vs Dialogue Leveler FAQ ### What is the difference between Voice Isolation and Dialogue Leveler? Voice Isolation separates a recorded human voice from competing sound. Dialogue Leveler rides louder dialogue down, lifts softer dialogue, and can reduce some non-dialogue background for a more consistent level. ### Is Dialogue Leveler available in DaVinci Resolve Free? Yes. Dialogue Leveler is available on desktop in both Resolve Free and Studio. Voice Isolation requires Resolve Studio. ### Which tool should go first? When both are needed, match large clip-gain differences first, apply Voice Isolation conservatively, then use Dialogue Leveler. Treat that order as a starting point and compare the full chain at matched loudness. ### Can Voice Isolation remove wind and crowd noise? It can reduce them when the speech remains recoverable. It can't reliably reconstruct words covered by strong gusts, clipping, applause, or another voice. ### Why does Dialogue Leveler raise breaths and room noise? Lift Soft Dialogue raises quiet dialogue, and noise occurring with speech may rise too. Disable that switch or correct the phrase manually. Output Gain changes the level after processing; it is not a noise-reduction amount or a loudness target. ### Should I still use a compressor? Only if the dialogue needs additional controlled dynamics after clip gain and leveling. Start gently and check that the compressor isn't exaggerating pumping or breaths. ### Can I apply these tools to an entire track? Yes, on existing mono, stereo, or dual-mono tracks. Ordinary clip and Track FX instances can't process a general live audio input. The Cut page Voiceover Tool is a separate recording workflow that can apply Voice Isolation and Dialog Leveler while it records. Track processing is safest when the microphone, speaker, and room stay consistent. ### Where DaVinci Resolve Projects Are Saved URL: https://davinciresolveclub.com/where-davinci-resolve-projects-saved/ Last updated: 2026-09-15T14:20:51.000Z Resolve doesn't save an active desktop project beside your footage as a normal project file. It writes the project inside the selected Project Library. Before moving, updating, or cleaning a drive, identify that library in Project Manager and create a separate export you can test. ![Project Manager with the Project Libraries sidebar and selected local library](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc147-library-sidebar.webp) Select the library that contains the project before inspecting its location. Official interface figure: Blackmagic Design, Resolve 21.1 Reference Manual, p. 80. ## Where DaVinci Resolve Projects Actually Live A project library is the working database that holds your timelines, edits, grades, Fusion compositions, Fairlight work, bins, metadata, and project settings. Your camera originals usually live somewhere else. So do render cache, proxies, optimized media, gallery stills, and automatic project backups. | Item | What it contains | Use it for | | --------------------------------- | ----------------------------------------------------- | ------------------------------------------- | | **Project Library** | One or many live Resolve projects | Daily work and library-level backup | | **.drp** | One exported project, without source video/audio | Small, portable checkpoints and handoffs | | **.dra** | Project archive plus selected media and dependencies | Moving a self-contained job | | **Project Backups** | Timed versions of a project | Rolling back after a bad edit or corruption | | **Source media and dependencies** | Video, audio, graphics, fonts, LUTs, and other assets | Rebuilding and relinking the edit | | **Cache/proxies** | Replaceable performance files | Smoother playback, not disaster recovery | Checked against the September 2026 [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com), this guide separates the working library from exports, archives and media. Use the selected library's details to find your actual location; do not move database files to match a path from a tutorial. ## Do Not Guess the Folder: Check the Active Library The Resolve 21.1 manual says the default local-library location depends on the operating system. You can choose a different folder when creating a library, and an upgraded installation can keep using an older library. The library name does not tell you which drive contains it. Read its Location before searching hidden folders. Common path lists show Windows AppData/Roaming, macOS Library/Application Support or Linux .local/share/DaVinciResolve. Treat those as search clues, not verified defaults for every 21.1 installation. Older layouts and Mac App Store installations can differ. If Resolve opens, use its recorded Location; if it does not, preserve the suspected library before attempting recovery. | Library type | Where the project data lives | Reliable way to identify it | | ------------ | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | **Local** | A filesystem directory recorded for that library | Select the library, read **Location** in its details and use the file-location control | | **Network** | A managed project library on the selected network server | Verify the selected Network library and its connection details; do not look for a matching project folder | | **Cloud** | The selected Blackmagic Cloud project library | Verify the signed-in account and library in Project Manager; source media remains a separate storage decision | Select the local library and click its circled i details icon to read Location. The manual calls the right-click reveal command Reveal in Finder; Windows interfaces also label it Open File Location. Use the file-location control shown by your build. Network and Cloud selections identify a server-backed library, not a matching folder on this computer. Inside a local library, a path may end in Resolve Projects/Users/guest/Projects/Project Name/Project.db. That Project.db belongs to the managed library structure. It is not a portable DRP: do not rename, delete, replace or manually edit it to make a project appear. Use Resolve to connect the parent library or import an export. The manual documents a complete project-folder copy method for local libraries on macOS and Windows, not Linux. That is a constrained migration procedure, not permission to swap individual database files. For the steps here, use a tested DRP, DRA or library backup instead, with the original library kept intact. ## Find the Exact Library Resolve Is Using If the page layout is still unfamiliar, keep our [DaVinci Resolve beginner guide](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) open beside this checklist; Project Manager sits outside the normal Edit, Color, Fusion, and Fairlight pages. 1. **Open Project Manager.** Click the house icon at the lower-right of the Resolve window, or use **File, then Project Manager**. 2. **Show the Libraries panel.** If the left column is closed, click the Project Libraries button at the top-left. 3. **Select the library that contains the project.** Do not assume the library called “Local” is the one you used last year. 4. Read the exact location. Click the circled i details icon to display Location. Use the local library's reveal/open-location control if available, then compare the opened directory with that recorded path. A file manager window alone may not identify the correct folder among several libraries. 5. **Record the name, type, and location.** Save that note with the job. For a custom or upgraded library, this is more reliable than any default path copied from the web. To open a recorded path on macOS, use Finder > Go > Go to Folder and paste it, as explained in [Apple's folder-navigation instructions](https://support.apple.com/guide/mac-help/go-directly-to-a-specific-folder-on-mac-mchlp1236/mac?ref=davinciresolveclub.com). If AppData is hidden on Windows 11, [Microsoft documents View > Show > Hidden items](https://support.microsoft.com/en-us/windows/experience/fileexplorer/file-explorer-in-windows?ref=davinciresolveclub.com). Neither operation changes which library Resolve uses. Local libraries use a directory on your workstation. Network libraries use PostgreSQL on a server, often managed through the DaVinci Resolve Project Server application. Ask the administrator to verify the library and server connection; a shared media drive is not itself the project database. Do not move PostgreSQL data folders in Finder or File Explorer. Blackmagic Cloud libraries keep project data on Blackmagic's servers. In Project Manager, check Cloud, the signed-in personal or organization account, and the selected library, including Shared with me. The [Blackmagic collaboration overview](https://www.blackmagicdesign.com/products/davinciresolve/collaboration?ref=davinciresolveclub.com) treats library access and media synchronization separately: opening the project does not prove that this computer has every original clip. ## Export a DRP: The Smallest Useful Safety Copy A `.drp` is an exported snapshot of one project. It carries project data and references source media where it already lives; it doesn't package the camera originals. The normal Export Project command also excludes Gallery stills and LUTs. Choose Export Project With Stills and LUTs when the recipient needs those embedded project dependencies, but copy or archive the source media separately. 1. Open Project Manager and right-click the project thumbnail. 2. Choose **Export Project**. 3. Name it with the project, date, and a short milestone, such as `Documentary_2026-08-04_picture-lock.drp`. 4. Save it outside the live Project Library, ideally on storage covered by a second backup. 5. Test it: import the DRP into a non-production test library, open it, and verify the important timelines before relying on the export. Export a DRP before a Resolve upgrade, before a destructive timeline change, and after any work session whose loss would be expensive. Project Backups provide rolling recovery; a dated DRP is a separate checkpoint you choose and can test. If you're upgrading, follow the full [safe DaVinci Resolve update checklist](https://davinciresolveclub.com/update-davinci-resolve-safely/) before opening important projects in the new version. ## Create a DRA When the Media Must Travel A .dra is an archive folder containing a project and the media you select. In Resolve 21.1, the Archive dialog offers Media Files, Proxy Media, Only include used media, Include Render Cache, Include LUTs and Include Gallery Stills. A proxy-only archive omits camera originals; a used-media archive can omit clips that are not in a timeline. 1. Open Project Manager and right-click the project. Choose Archive in the current manual's interface; older builds call this Export Project Archive. 2. Choose a destination with enough free space. 3. Select Media Files when original video, audio and graphics must travel. Review the used-media filter and optional proxies, cache, LUTs and Gallery stills. Choose deliberately rather than assuming every dependency is included. 4. Wait for completion and check any missing-media errors. Put the complete DRA folder on the destination storage, then use Restore in Project Manager (Restore Project Archive in older interfaces), or drag the DRA into Project Manager. Restore imports the project; it does not relocate the archive's media. A DRA shouldn't be the only copy of irreplaceable camera originals. Keep an independently verified media backup and a DRP even when you make an archive. If the restored project opens but clips are red, use the steps in the [Media Offline relinking guide](https://davinciresolveclub.com/media-offline-davinci-resolve/). ![Resolve Archive dialog with Media Files, Proxy Media, used-media, cache, LUT and Gallery still options](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc147-archive-options.webp) Choose what the DRA should contain; a proxy-only archive is not an original-media backup. Official interface figure: Blackmagic Design, Resolve 21.1 Reference Manual, p. 92. ## Project Backups, Live Save, and Library Backups Are Different Live Save incrementally updates the current project in its library and is on by default. It does not create an independent copy of that library, and it can save an unwanted edit too. Project Backups store periodic recovery versions separately. Read Project backup location under DaVinci Resolve > Preferences > User > Project Save and Load; it is not the library Location. These backups exclude stills and LUTs and load as independent projects. For enabling them, intervals and rollback steps, use the [Resolve saving and Project Backups guide](https://davinciresolveclub.com/how-to-save-work-davinci-resolve/). For a local library, open Project Libraries, select its circled i details icon and choose Back Up. Save the .resolve.backup outside the live library. The sidebar Restore control imports it into a separate library name and location. For Network/PostgreSQL libraries, use the Project Server tools or an administrator-approved database backup, not a manual copy of a running database. Cloud library Back Up works differently: the backup is made in Blackmagic Cloud. In the Cloud library details, Restore lets you select a saved version and assign a new library name. That does not put a .resolve.backup file on your local drive. Export a separate DRP when you also need an offline copy of project data. Cache, proxies and optimized media help playback; they are not project-library backups. Do not classify recorded audio, custom assets or Gallery stills as disposable just because they sit near cache. Inspect the project's configured media and working-folder paths before any cleanup. If opening or saving fails, use the non-destructive checks in our [DaVinci Resolve troubleshooting guide](https://davinciresolveclub.com/fix-davinci-resolve/) rather than deleting a whole storage folder. ## Safest Way to Move a Project to a New Computer Use a DRA with Media Files selected when you want Resolve to gather the job's media. If you already have a verified media copy, import a DRP and relink that copy instead. Neither approach automatically installs fonts or licensed plug-ins. Keep their installers, license details and version notes separately. 1. On the old computer, export a dated DRP. 2. Copy and verify the source media. Compare file counts and, for critical work, hashes. 3. Install the required fonts and audio plug-ins on the destination under their licenses. Transfer custom LUTs, Gallery stills and external graphics when they are not already included in the chosen export or archive. 4. Install a compatible Resolve version on the new computer. Check the [current Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) first. 5. Import the DRP into a new or existing library. 6. Relink media at the highest common parent folder. 7. Check timelines, grades, Fusion comps, audio plugins, frame rate, color management, and deliver presets before retiring the old machine. To relocate an entire local library, make and test a library backup before changing its location. Restore to a new name and destination, open representative projects and verify their media. Keep the original library unchanged until the new copy and an independent backup are checked. Do not rename or delete live database directories to force a reconnection. ## Project Missing? Use This Recovery Order This recovery sequence belongs to the [Fix DaVinci Resolve hub](https://davinciresolveclub.com/fix-davinci-resolve/). Start with the library list and verified exports before reinstalling, moving folders or deleting cache. 1. **Stop cleaning or reinstalling.** Do not write more data to a drive that may contain the only library. 2. **Check every listed library.** A blank “Local” library may simply be a newly created library, not proof that the old project was deleted. 3. **Reconnect known storage.** Confirm the external drive is mounted under the expected Windows drive letter or macOS/Linux volume path. 4. **Connect the parent library.** In Project Manager, use **Add Project Library, then Connect** and select the library root, not an individual `Project.db`. 5. **Look for your exported DRPs and library backups.** Restore them into a separate library so you do not overwrite evidence. 6. **Inspect Project Backups through Resolve.** Right-click the expected project and choose **Project Backups** when the library still sees it. 7. **Relink media only after the project opens.** Offline clips and a missing project are two separate problems. ![Add Project Library dialog with Connect selected and Name and Location fields](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc147-connect-library.webp) Connect to the known local library root, not an individual Project.db file. Official interface figure: Blackmagic Design, Resolve 21.1 Reference Manual, p. 82. Cache, Project Backups, and live Project Library data are easy to confuse, and Resolve can open a different empty library after an installation change. Treat those symptoms as diagnostic clues, not permission to paste a random Project.db into a managed library. If storage may be physically failing, stop using the drive and involve a data-recovery specialist before experimenting. ## Back Up Before a Project Library Upgrade Resolve may request a library schema upgrade for a major release or a point release. Back up before accepting that prompt. Test restoration separately, and do not upgrade the only surviving library merely to see whether a missing project returns. A successful backup operation is not the same as a successful restore test. Treat a library upgrade as a compatibility boundary, not as a routine file open. Keep the old application and original library untouched until the upgraded copy, its timelines, media links, grades, Fusion compositions, Fairlight work, and deliver settings have been checked. Don't assume an older Resolve release can reopen a library after its schema has been upgraded. ## A No-Surprises Project Backup Checklist - Confirm the active library name, type, and exact location in Project Manager. - Export a dated DRP after every meaningful edit session. - Enable Project Backups and verify the destination is actually writable. - Back up the complete library on a regular schedule. - Keep at least two verified copies of original media on separate storage. - Include fonts, LUTs, graphics, audio assets, and plugin notes. - Create a DRA when a self-contained handoff is worth the extra space. - Test-import a DRP and test-restore a library backup before deleting or upgrading anything. Before retiring the old storage, open the restored library and test an exported project with its media. Check an actual timeline, grade, title and audio section. Keep the original copy until those checks and an independent backup are complete. Project-library safety comes before every workflow in the [DaVinci Resolve Workflow hub](https://davinciresolveclub.com/tag/workflow/), especially updates, editing, and delivery. ## DaVinci Resolve Project Storage FAQ ### Does DaVinci Resolve save projects as normal files? Working desktop projects normally live inside the selected Project Library. A .drp is a portable project export you save to a chosen folder; it is not the same thing as the internal Project.db file. ### How do I find the Resolve Project Library on Windows, macOS, or Linux? Open Project Manager, show Project Libraries, select the local library and click the circled i details icon to read Location. The reveal command is called Reveal in Finder in the manual and Open File Location in Windows interfaces. Follow the label in your build and confirm the opened path matches the selected library. ### Why does my Project Library path differ from a tutorial? Local libraries can use a folder chosen during creation or retained from an older installation. OS and installation differences also matter. Network and Cloud libraries identify server-backed storage rather than an equivalent local folder. For a local library, trust its recorded Location instead of a generic default path. ### Does a DRP include video and audio files? A normal DRP export contains project data, not your source video and audio. Copy media separately or create a DRA with Media Files selected. A proxy-only DRA is not a copy of the camera originals. ### Can I open or move a Project.db file manually? Do not treat an individual Project.db as a portable project. Connect the parent library or use Resolve's export, import, backup, and restore commands to avoid damaging its managed structure. ### Are cache and proxy files a project backup? No. Cache, proxies, and optimized media are replaceable performance files. They don't preserve the project database and they don't necessarily contain your original-quality source media. ### Should I use DRP or DRA to move a project? Use a DRP when media is already copied or will be relinked separately. Use a DRA when you want Resolve to package the project with selected media for a more self-contained transfer. ### How to Change Clip Speed in DaVinci Resolve URL: https://davinciresolveclub.com/change-clip-speed-davinci-resolve/ Last updated: 2026-09-15T13:34:29.000Z For one constant speed, right-click the timeline clip and choose Change Clip Speed. Enter 200% to play twice as fast or 50% to play at half speed. For a speed change inside the shot, open Retime Controls with Command-R on macOS or Ctrl-R on Windows, add speed points and adjust the segments. In Resolve 21.1, shape the ramp in the Keyframes panel. Motion quality is a separate decision under Inspector > Retime and Scaling. Use percentage when the playback rate is the target and Duration when the clip must fill an exact gap. For clean slow motion from high-frame-rate footage, calculate timeline fps ÷ source fps × 100 before enabling Optical Flow. If Resolve must invent frames, compare Frame Blend with Optical Flow on the actual shot; Speed Warp is a Studio-only motion-estimation mode, not a universal quality switch. Before experimenting, duplicate the timeline and keep the original unchanged. Select only the intended video and audio items. A ripple can move later cuts, and Freeze Frame can replace the playback of an entire selected clip. This guide covers fixed speed, variable speed, ramp shape and frame generation, not changing the delivery frame rate. ## DaVinci Resolve Change Clip Speed Dialog: Fixed Speed in One Box Right-click a clip in the Edit page timeline and choose Change Clip Speed, or select it and use Clip > Change Clip Speed. The dialog describes the same change three ways: a percentage, a frame rate, or a duration in HH:MM:SS:FF. Use Duration when the selected source range must fill an exact gap. For example, a ten-second source range takes five seconds at 200% or twenty seconds at 50%. Those lengths assume you preserve that source range and allow its timeline duration to change. Check Ripple Sequence and the surrounding edit before applying the change. ![Change Clip Speed dialog with duration, ripple and pitch controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc146-speed-dialog.webp) Set a fixed speed or duration, then decide whether later clips may move. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1217. The checkboxes matter more than the number you type: - **Ripple Sequence** pushes or pulls clips after the retimed clip to make room for its new duration. - **Reverse Speed** changes playback direction. - **Freeze Frame** holds the frame under the playhead; Shift-R creates the same whole-clip freeze without opening the dialog. - **Pitch Correction** keeps attached audio closer to its original pitch, but large changes can still sound processed. - **Maintain Timing / Stretch to Fit** leaves Composite, Transform and Cropping keyframes at their timeline positions or compresses and expands them with the retimed clip. If Ripple Sequence is off, the timeline won't open or close space automatically, so previously trimmed frames can reappear at the tail while the clip keeps its original slot. When that happens, check Ripple Sequence before changing the speed value again. ## Retime Controls: Speed Points, Ramps and Freeze Frames Select the clip and choose Clip > Retime Controls, or press Command-R on macOS or Ctrl-R on Windows with the default DaVinci Resolve keyboard preset. Custom presets may differ. The current manual also uses the wording Retime Clip in one contextual-menu instruction; the main-menu path avoids that naming inconsistency. Read the numeric speed beside each segment first. Arrow spacing and direction offer a quick visual check, but the percentage tells you exactly how fast that portion plays. Confirm the selected clip before dragging its retime handles. ![Retime Controls with a freeze-frame range between two speed points](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc146-speed-points.webp) The two points bound a temporary hold; playback resumes after the second. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1220. To isolate a middle section, park the playhead at its start, open the speed pop-up and choose Add Speed Point. Move to its end and add a second point. Change that bounded section with its Change Speed menu or its handles: - Dragging the **top handle** of the second speed point right slows that segment and left speeds it up, changing the clip length either way. - Dragging the **bottom handle** widens the range of the clip playing at that speed, reallocating frames from before and after the segment. Use the upper handle when the segment speed is the direct target: right slows it, left speeds it, and the clip becomes longer or shorter. The lower handle reallocates source frames before and after that speed point. It also changes the clip duration, but by a different amount; it isn't a locked-duration control. For a temporary hold, park the playhead on the desired frame and choose Freeze Frame from the Retime Controls speed pop-up. Resolve adds two points around the hold and resumes playback after it. Drag the second point to change the hold length. This differs from Clip > Freeze Frame or Shift-R, which freezes the entire selected clip. Reverse Segment reverses the current section; Rewind adds a reverse-and-replay effect. The Speed Ramp presets replace the current speed effect, so try them only on your backup copy. Resolve automatically eases one speed segment into the next. Start with that result, then open the Keyframe Editor only when the boundary still lands too hard or must hit a precise moment. ## Retime Curve: Shaping a Ramp You Already Built In Resolve 21.1, select the timeline clip, open the Keyframes tab at the top of the interface, click the Keyframe Curves icon and choose Retime Speed or Retime Frame in the parameter list. Older tutorials that say right-click > Retime Curve describe the former under-clip workflow. Retime Frame maps source frames against timeline time: shallower slopes slow motion, steeper slopes speed it up and a descending slope reverses it. Use Retime Speed to adjust speed segments and verify the resulting numeric percentages in Retime Controls. Control points on either curve correspond one to one with the speed points in the Retime controls, so adjusting one updates the other live. ![Retime curves in the Keyframes editor with speed transition handles](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc146-retime-curves.webp) Open Keyframes and its Keyframe Curves view to shape retiming, rather than looking for the old under-clip curve command. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1223. Start with speed points when you want a quick ramp. Use the curves when you need finer timing or a shaped acceleration. You can also build the effect directly in the curve editor; it is not restricted to repairing an existing ramp. Checked against [Blackmagic Design’s September 2026 Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=1225). Resolve 21 added Bezier easing for retime parameters. Use the curve controls to shape the transition, then inspect the start, end and any freeze boundary in a rendered sample. This is a documentation-based workflow, not a claim of hands-on testing on every platform. Resolve 21.0.3 added new ease modes for Retime Speed and Retime Frame curves, configurable keyframe ease actions and a legacy speed-mode curve option, as reported in [RedShark’s July 2026 release coverage](https://www.redsharknews.com/davinci-resolve-21.0.3-whats-new?ref=davinciresolveclub.com). Legacy speed mode changes curve behavior; it does not restore the old under-clip editor. Do not switch curve modes across a finished sequence without testing a duplicate first. Verify numeric segment percentages and render a short sample before copying the ramp. ## Clip Speed and Audio: Pitch, Muting and Linked Tracks Attached audio can follow a fixed video retime. Use Pitch Correction in Change Clip Speed when you want the duration to change without the obvious chipmunk-or-monster pitch shift. The [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) warns that large speed changes can still sound worse than small ones, so this checkbox isn't a guarantee of transparent dialogue. Variable-speed audio has its own Pitch Correction option in the Speed menu of Retime Controls. Check that control in the exact Resolve build you're using; the current manual explicitly documents pitch-corrected and un-pitch-corrected variable-speed playback there. The Resolve 21.1 manual still contains conflicting audio descriptions: the overview on p. 1216 says variable-speed audio is muted, while the audio section on p. 1127 documents pitch-corrected or uncorrected variable-speed playback. Do not treat silence as inevitable or assume the checkbox guarantees usable dialogue. Check the audio component, selection, mute/solo state and the Speed menu in your installed build, then listen to a rendered sample. Before locking the retime, check two audio boundaries that are easy to miss: - **Linked Selection** makes corresponding linked video and audio select together, and edits to linked items can travel together; it doesn't merge them into a new media file. Confirm both items are selected before a fixed retime. Use a Compound Clip only when several timeline items genuinely need to behave as one container. - **Pitch Correction** becomes less transparent as the speed change grows; compare it on and off on the actual source. If attached dialogue still smears with Pitch Correction enabled, undo the picture retime on that audio component and solve its timing separately. Elastic Wave is the appropriate Fairlight tool when audio must stretch without forcing the picture to follow. On the Fairlight page, right-click the audio clip and choose Elastic Wave retiming. Its timing points stretch or compress audio while maintaining pitch, without retiming picture on the Fairlight page. ## Retime Process and Motion Estimation: Fixing Choppy Slow Motion When a slowdown asks for more timeline frames than the source holds at its effective frame rate, Resolve has to repeat, blend or synthesize frames. Which of those it does is set project-wide under Project Settings > Master Settings > Frame Interpolation, and per clip in the Inspector under Retime and Scaling. - **Nearest** duplicates frames for slow motion and drops them for fast motion. Cheapest to process, and the reason untouched slow motion looks stepped. - **Frame Blend** dissolves adjacent duplicated frames together. The manual recommends it specifically when Optical Flow produces unwanted artifacts. - **Optical Flow** generates new frames using motion estimation. Exceptionally clean on linear motion, and prone to tearing when two elements cross in different directions or the camera moves unpredictably. Optical Flow exposes Motion Estimation choices: Standard Faster, Standard Better, Enhanced Faster, Enhanced Better, Speed Warp Faster and Speed Warp Better. On macOS, Resolve 21 also lists AI Speed Warp Metal, a Mac-hardware-optimized Neural Engine mode. The best-looking option is shot-dependent; crossing subjects and unpredictable camera movement can make a lower mode cleaner. [Speed Warp is a Studio feature](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com). Resolve Free users can compare Standard and Enhanced modes, with Enhanced Better as the highest non-Speed-Warp option in this menu. The [Resolve Free feature guide](https://davinciresolveclub.com/davinci-resolve-free-version-features/) and [Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) cover the wider license boundary. Most guides treat Speed Warp as the answer to every stuttering shot. It isn't. Optical flow methods estimate motion, so a busy foreground crossing the frame can produce worse edge tearing than a simple Frame Blend, at a higher render cost. Test both on the actual shot instead of picking the highest setting on principle. If both preview and the rendered file show irregular cadence, inspect the source before raising Motion Estimation quality. Phone and screen recordings are often variable frame rate; transcode a test to a constant frame rate, relink it and compare the same section. Optical Flow can synthesize intermediate images, but it can't guarantee a repair for irregular capture timing. If only the timeline preview stutters while the export is clean, use the separate [slow-playback checklist](https://davinciresolveclub.com/davinci-resolve-slow-playback/). ## Speed Percentages That Skip Interpolation Entirely For high-frame-rate footage with stable capture timing, the source-to-timeline ratio gives a slowdown that can use one real source frame per timeline frame. Start with Nearest so you are not asking an interpolation algorithm to blend or invent frames unnecessarily. Speed percentage = timeline frame rate divided by source frame rate, times 100. Use the [actual rates shown in Clip Attributes and Timeline Settings](https://davinciresolveclub.com/davinci-resolve-frame-rate/) rather than the rounded numbers on the camera body. 59.94fps into a 23.976fps timeline is also 40%. Footage that was previously conformed, variable frame rate files, and clips that already carry a retime can all change how this calculation behaves. | Source | Timeline | Speed | What Resolve does | Recommendation | | ------ | -------- | ------------------- | ---------------------------------------- | -------------------------------------- | | 60fps | 24fps | 40% | Every timeline frame is one source frame | Use this before touching Optical Flow | | 120fps | 24fps | 20% | Every timeline frame is one source frame | Uses original source frames | | 240fps | 24fps | 10% | Every timeline frame is one source frame | No synthesized frames needed | | 60fps | 30fps | 50% | Every timeline frame is one source frame | Standard choice for 30fps delivery | | 120fps | 30fps | 25% | Every timeline frame is one source frame | Safe down to a quarter speed | | 50fps | 25fps | 50% | Every timeline frame is one source frame | Useful for 25fps delivery | | 24fps | 24fps | Anything below 100% | Frames must be repeated or generated | Frame Blend first, Optical Flow second | The familiar “60 fps at 50%” advice is correct for a 30 fps timeline, not a 24 fps timeline. At 24 fps, 60 fps footage uses every source frame at 40%. Exact fractional pairs work the same way: 59.94 ÷ 23.976 is 2.5, so the clean playback percentage is 40%. This assumes the clip hasn't already been conformed or retimed and the source cadence is stable. Changing Media Pool > Clip Attributes > Video Frame Rate is a different operation: it changes how Resolve interprets the source, rather than adding a timeline speed effect. Setting a genuine 60fps source to 24fps makes it play slowly at 100%, but its audio is unaffected and can lose sync. Record the original setting and test on a separate copy of the project before changing source interpretation. Do not also apply the 40% timeline retime to an already interpreted slow-motion clip unless you intend a second slowdown. ## Clip Speed Changes That Break the Timeline Check the timeline copy before rippling. Which clips move depends on the speed tool, edit mode and track controls: - The Change Speed dialog ripples only when Ripple Sequence is ticked. - The Retime controls ripple in Trim mode (T) and can overwrite neighboring clips in Selection mode (A). On a cut locked to music, a ripple can move later cuts off their beats. With Ripple Sequence off, inspect the changed clip’s out point and available source handles; keeping its timeline slot does not guarantee the same visible ending. With Retime Controls in Selection mode, extending the clip can overwrite a neighbor. Trim mode can ripple instead. Neither choice replaces checking the adjacent cuts. Sync Lock is enabled by default. Turn it off only on tracks that must stay outside a cross-track ripple; those tracks may then lose relative sync with the retimed section. Position Lock is the stronger finishing control: it prevents horizontal clip movement and all ripple operations, while still allowing many non-positional edits. Do not treat an empty higher video track as protection against cross-track ripple or lost audio sync. Work in the duplicate timeline and inspect the neighboring cuts, linked audio and any titles after each change. Undo immediately if the result is wrong. ## Changing Speed on Multiple Clips Select every clip you want changed and open Change Clip Speed. The dialog applies across the whole selection, and so does the Inspector's Speed Change group. To copy a full ramp, build and verify one clip, copy it, select the targets, choose Paste Attributes and enable Retime Effects. The same dialog has a Ripple Sequence choice. Remove Attributes can remove retime effects from a batch and also asks whether the timeline may ripple. Check mixed-frame-rate destinations individually rather than assuming one interpolation mode fits the selection. The [clip-duplication guide](https://davinciresolveclub.com/duplicate-clip-davinci-resolve/) covers the separate problem of copying timeline items rather than their attributes. Review each target after a batch change. A percentage copied between different source frame rates does not produce the same motion cadence. For multicam, check synchronization and the selected audio before retiming; do not flatten or decompose the original merely to make a speed control appear. A compound clip can retime a group as one container, but inspect its internal audio and effects. For Fusion compositions, check the composition’s frame range and animation after retiming a duplicate; changing picture timing is not a guaranteed way to stretch every internal animation. ## Speed Methods Compared | Method | Where it lives | Best for | Recommendation | | ------------------------ | ------------------------------------ | -------------------------------------------------------------- | ------------------------------------------------ | | Change Clip Speed dialog | Right-click clip, or Clip menu | One fixed speed, a duration target, freeze frame, reverse clip | Default choice for anything that is not a ramp | | Retime controls | Command-R or Ctrl-R on the Edit page | Speed points, speed ramp, mid-clip freezes, rewind presets | Use for timeline speed segments | | Retime curve | Keyframes tab > Keyframe Curves | Reshaping how one speed eases into the next | Use for precise timing and shaped acceleration | | Inspector Speed Change | Video Inspector, Cut and Edit pages | Keyframeable speed, numeric entry, Cut page work | Best option when you are cutting on the Cut page | Choose the speed tool for the job, then check how it affects duration and neighboring clips. Numeric speed, audio timing and frame interpolation each need their own check. ![Video Inspector Speed Change settings including duration and Pitch Correction](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc146-speed-inspector.webp) Use the Inspector on Cut or Edit for numeric speed changes. Frame interpolation is a separate Retime and Scaling setting. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1218. Once motion and audio pass a short test render, use the [Resolve export settings guide](https://davinciresolveclub.com/davinci-resolve-export-settings/) for delivery. The [DaVinci Resolve Tutorial hub](https://davinciresolveclub.com/davinci-resolve-tutorial/) keeps this retime workflow inside the larger edit-to-export path. ## Clip Speed FAQ ### Can you change clip speed in the DaVinci Resolve Cut page? Yes. Speed Change in the Video Inspector works on both Cut and Edit pages and includes Direction, Speed %, Frames Per Second, Duration, Ripple Sequence and Pitch Correction. The timeline Retime Controls overlay with draggable speed points is an Edit-page workflow. ### How do you reset a clip to 100% speed in DaVinci Resolve? Open the Retime controls with Command-R or Ctrl-R, click the pop-up next to the speed percentage at the bottom of the clip, and choose Reset to 100%. To strip retiming from several clips at once, use Remove Attributes and turn on the retime checkbox, then decide whether the timeline should ripple. ### Does changing clip speed in DaVinci Resolve reduce video quality? Retiming doesn't reduce spatial resolution by itself, but it can reduce motion quality. Speeding up skips source frames; slowing beyond the clean source-to-timeline ratio requires repeated, blended or synthesized frames. Judge cadence and artifacts in a rendered sample, especially with Optical Flow. ### Can DaVinci Resolve change the speed of audio without the video? Yes. On the Fairlight page, right-click an audio clip and choose Elastic Wave retiming. Add timing points to stretch or compress the waveform while maintaining pitch; picture isn't retimed from the Fairlight page. ### How to Copy a Color Grade in DaVinci Resolve URL: https://davinciresolveclub.com/copy-color-grade-davinci-resolve/ Last updated: 2026-09-15T10:47:49.000Z Copying a grade is easy once you answer two questions first: should the destination grade be replaced or should new nodes be appended, and should later changes stay linked across clips? A middle-click can replace twenty grades in one action. The same click can also erase twenty clip-specific corrections if you chose the wrong method. Before replacing a grade, save the project and preserve the destination correction as a still or separate version. Test one destination first. Appending preserves existing nodes but can still change the image incorrectly if transforms, LUTs or effects are doubled. Use ordinary copy/paste, middle-click or Apply Grade for a one-time replacement. Use Append Node Graph to keep the existing tree, or paste into a chosen node to replace only its settings. For ongoing linked changes, consider Groups, Shared Nodes or Remote Grades. Check the preservation settings before copying. ## DaVinci Resolve Copy Grade Methods Compared | Method | What it moves | Overwrites? | Stays linked? | | ------------------------------------- | ------------------------------- | -------------- | ------------- | | Cmd/Ctrl+C then Cmd/Ctrl+V | The whole grade | Yes | No | | Middle-click a clip in the film strip | The whole grade | Yes | No | | Gallery still, then Apply Grade | The saved node tree | Yes | No | | Gallery still, then Append Node Graph | The saved nodes, added on | No | No | | Copy and paste a single node | One correction | That node only | No | | Apply Grade From One Clip Prior | The previous clip's whole grade | Yes | No | | Groups | A group-level grade | No | Yes | | Shared Nodes | One node, live on many clips | No | Yes | | Ripple Node Changes to Selected Clips | One node's change, once | That node only | No | One-time copies are independent only when the copied graph has no linked Shared Nodes and the destination is not using a linked remote version. Inspect those relationships before changing a copied correction. Checked on September 15, 2026 against Blackmagic's Resolve 21.1 Reference Manual. Here, whole grade means the node tree at the active grade level, subject to the preservation settings. Ordinary clip-to-clip copying excludes keyframes and motion tracking; the Gallery and individual-node workflows below control those separately. In a project with Node Stack Layers, do not assume a middle-click transfers every layer. Check the copy scope and active layer before applying a grade to multiple clips. A Gallery still saves all stack layers, while the documented Copy Active Layer command is explicitly layer-specific. Inspect the destination layers after applying the saved grade. Groups and Shared Nodes keep chosen corrections linked. Remote Grades offer a third relationship: clips using remote versions and the same Media Pool source share grades, even across timelines in one project. This is not remote grading between workstations. Ripple Node Changes is a one-time command, not a persistent link. ## Copy a Whole Color Grade With the Keyboard Click the source clip in the Thumbnail Timeline, press Cmd+C on macOS or Ctrl+C on Windows, select the destination clip or clips, and press Cmd+V or Ctrl+V. The current [DaVinci Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) documents two behaviors: Thumbnail Timeline focus copies the whole grade, while Node Editor focus copies the selected node. The catch is that the same two shortcuts do a different job depending on what has interface focus. With the Node Editor active they operate on the selected node rather than the whole grade. There is also a checkbox at Preferences, then User, then Color, labeled Always perform copy and paste on selected nodes, which pins the behavior to nodes only. If Ctrl+V is pasting one node when you wanted the whole tree, or the whole tree when you wanted one node, that checkbox and where you last clicked are the two things to check. On the Edit page, use Copy on the source clip, select the destination clips and choose Edit > Paste Attributes (Option+V on macOS, Alt+V on Windows/Linux in the default preset). Enable Color Correction and leave unrelated attributes unchecked. This is a clip-level operation, not the Color-page node dialog. It replaces the copied color correction rather than appending nodes. ## How to Copy a Color Grade With Middle Click Blackmagic calls this the fastest route on [its own Color page documentation](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com): middle-click a clip in the film strip to copy its grade to the current shot in the viewer. Most copy-paste habits run source first, destination second. This one runs backwards. 1. Open the Color page and make sure the Thumbnail Timeline is visible. 2. Click the clip you want to **change**. It becomes the current clip. 3. Middle-click the thumbnail of the clip you want to copy **from**. The destination grade is replaced, subject to the Copy Grade preservation settings. Select several destination clips first to apply the same operation to all of them. Inspect the first result before repeating this on valuable graded shots. A trackpad has no middle button by default, and you don't need to save a still to work around it. Select the destination clip or clips, right-click the graded source clip, and choose Apply Grade. A third-party trackpad utility can also map a three-finger click to mouse button 3 if you want the one-action version back. ## Copy a Color Grade With Gallery Stills and Apply Grade A Gallery still is more than a picture: Resolve saves the grade with a reference frame so you can recognize, compare and reuse it. 1. Grade a clip the way you want it. 2. Right-click anywhere in the viewer and choose Grab Still. Blackmagic spells out this as the way to save a grade into the Gallery. 3. The still appears in the Gallery at the top left. Stills sort into albums. 4. Select one or more destination clips in the timeline. 5. Right-click the still and choose Apply Grade. Middle-clicking the still does the same job. Enable Live Preview in the Gallery options menu to inspect a saved grade before applying it. The preview depends on the selected node and preview settings, so check the actual applied result as well. A hover preview is not a saved change. ![Gallery stills hold reference frames and saved grades](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc145-gallery.webp) Use Gallery stills to keep a reusable grade beside a reference frame. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3333. ## Add a Saved Grade Without Overwriting Nodes Apply Grade replaces the destination tree. When you want the saved correction sitting on top of a balance pass you already built, right-click the Gallery still and choose Append Node Graph instead. Resolve places those nodes after the existing ones rather than in place of them. You can also drag a still from the Gallery onto a connection line in the Node Editor and drop it when the plus icon appears, which lets you choose where in the tree the nodes land. Command-drag on macOS or Ctrl-drag on Windows appends the saved graph as a single compound node, which keeps a long saved grade from turning your graph into a row of boxes you have to scroll past. ![Existing Color node tree before appending a saved grade](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc145-append.webp) Check the existing node tree before adding a saved graph. Append keeps these nodes; it does not guarantee the combined transforms suit your footage. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3366. This is the answer to a common complaint about the Gallery, which is that reusing a look destroys the per-shot correction underneath it. ## Copy One Node Instead of the Whole Resolve Grade Select the node you want, press Ctrl+C or Cmd+C, select the node on the destination clip, then press Ctrl+V or Cmd+V. Holding Option or Alt and dragging a node onto another node is the same idea with the mouse: it pushes that node's settings across. Use node-level copy for a window, qualifier, keyframed correction or tracked operation that must move without replacing the rest of the grade. The node's settings overwrite the selected destination node, so create or choose the correct target first. For selective node copying on the Color page, copy the source node, select the destination node and choose Edit > Paste Attributes (Option+V on macOS, Alt+V on Windows/Linux). Choose the palettes, individual windows, effects and keyframe options you need. The dialog copies palette-level settings, not arbitrary individual parameters. Recheck or retrack a copied window on different footage; the old movement does not describe a different subject. ![Color page Paste Attributes controls for node palettes, windows and keyframes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc145-attributes.webp) Select only the node attributes you need. These Color-page controls differ from the Edit-page clip attributes dialog. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3368. [How nodes pass signal down the tree](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) is what makes node-level copying safe. Paste a saturation node into position 2 of a tree that expected a balance node there and every node downstream sees a different image than it was built for. ## Shortcuts for Copying the Previous Clip's Grade Two commands live in the Color section of Keyboard Customization: **Apply Grade From One Clip Prior** and **Apply Grade From Two Clips Prior**. In the default DaVinci Resolve keyboard preset, Equals (=) applies the grade from one clip prior, and Minus (-) applies the grade from two clips prior. Custom presets, remapped keyboards and non-US layouts all change this. If neither key responds, open DaVinci Resolve, then Keyboard Customization, choose Color in the Commands list, and search for Apply Grade to see what your build has assigned. Both commands copy the entire grade from the earlier clip, so they suit grading a scene in timeline order rather than cherry-picking a look from somewhere else in the edit. ## Copy a Color Grade to Many Clips With Groups Use Groups when several clips need the same correction and later revisions should affect every member. Group clips by the correction they actually share, not just because they sit next to each other in the timeline. Select the clips you want to group, right-click one and choose Add Into New Group. Switch the Node Editor to Group Pre-Clip or Group Post-Clip before making the shared correction. Clip mode is separate from the group grade; it can still contain Shared Nodes or use a linked remote version. Grouped clips add Group Pre-Clip and Group Post-Clip choices to the Node Editor mode selector alongside Clip and Timeline. Balance shared camera or scene conditions in Pre-Clip, keep shot-specific corrections in Clip, and place a common look or output-side adjustment in Post-Clip. Node trees built in Group Pre-Clip and Group Post-Clip affect every member of the group automatically. That's a persistent group-level relationship, not a one-time Ripple Node Changes command. ## Share One Node Across Clips Without Copying It To share one correction, build a Corrector node, right-click it and choose Save as Shared node. Give it a useful label. Add that named node to other clips through the Node Editor's Add Node submenu. Blackmagic locks shared nodes by default so you can't change every clip in a project by accident. Unlock it and your edits transfer across every clip using that node. Use Shared Nodes for adjustments that must remain identical: a camera-wide CST, a show LUT, a film-emulation layer or an output trim. Use a plain copy for anything a shot might need to deviate from later. Check every instance before unlocking a Shared Node. To make one instance independent, right-click it and choose Convert to Corrector. Switching to local grades does not unlink Shared Nodes already in the tree. Avoid broad remote-to-local conversion as a quick fix: some timeline conversion commands overwrite local versions and cannot be reversed with normal per-clip Undo. ## Ripple a Resolve Grade Change Across Clips You Already Graded Rippling is for clips you already copied a grade onto and now need to revise together. Select the clip you want to change so it's outlined orange, then Command-click on macOS or Ctrl-click on Windows to add non-adjacent clips, or Shift-click for a continuous range, so the targets turn red. Make your adjustment, then choose Color, then Ripple Node Changes to Selected Clips. A matching command exists for the current group. Rippling matches by node **number**. A change made to Node 3 reaches Node 3 on every other selected clip. Clips with no node of that number receive nothing at all, silently. Color, then Append Node to Selected Clips, adds the currently selected node to the end of every selected clip's node tree. It helps when the targets are missing the node you're about to ripple, but it won't reorganize node structures that already differ from each other. ## Save a Resolve Color Grade for Other Projects PowerGrade albums make reusable grades available to projects stored in the same project library for the same user login. Each project library has its own PowerGrade collection; an ordinary still album remains project-specific. Create a PowerGrade album from the Gallery album list and move or save the still there. For another library, workstation or colorist, export the still. Exporting a still in an image format writes the reference image and a matching DRX file containing the grade. A DRX can also be imported by itself: the node structure survives, but there is no reference image to wipe against. Keep both files when available. Right-click the still and choose Export, then import it into the destination Gallery. Keep the reference image and DRX together when sending a pair. A DRX is not a project backup: confirm required LUTs, DCTLs, plug-ins and supported effects are available on the receiving system. ![PowerGrade albums shared among projects in a project library](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc145-powergrade.webp) Store reusable stills in a PowerGrade album; a different project library has its own collection. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3342. Blackmagic's [free official training guides](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com) work through the same gallery and group workflows in lesson form. ## Why Copying a Color Grade Does Nothing If the grade does not change, check these controls before repeating the paste: - **The Keyframe Timeline Mode is on Sizing.** Mark, then Keyframe Timeline Mode, sets what a copy carries. All copies both the grade and the sizing. Color copies only the grade and leaves the target clip's Input Sizing alone. Sizing copies only the Input Sizing and leaves the target's grade alone. Sitting on Sizing while you copy a color change looks exactly like nothing happening. - **Copy Grade: Preserve Number Of Nodes is above zero.** Right-click the gray background of the Gallery to find it. Set it to 5 and the first five nodes of a copied grade are ignored, as long as the destination clip already has at least five nodes. It exists for colorists who reserve leading nodes for balance and shot matching. On a short node tree this can make the copy appear to do nothing, because every copied node falls inside the protected range. - **Copy and paste is acting on nodes, not the grade.** Preferences, then User, then Color: Always perform copy and paste on selected nodes. When enabled, Ctrl+V only writes into the selected node. - **Keyframes aren't coming across.** Right-click the gray background of the Gallery and open Apply Grades Using. No Keyframes applies the state of the grade at the frame the still was saved from. Keyframes Aligning Source Timecode suits copying back to the same clip or a duplicate of it. Keyframes Aligning Start Frames suits a completely different clip with different timecode. Check the selected clip, active grade level and node focus again before applying the correction to several clips. ## Keep Sizing and Stabilization When You Copy a Resolve Grade Set Mark, then Keyframe Timeline Mode, to Color so the target clip keeps its own Input Sizing. When keyframes aren't part of what you're copying, set Apply Grades Using to No Keyframes as well. Copy Grade: Preserve Input Sizing in the Gallery menu protects the destination clip's Input Sizing values directly. Stabilization and other clip-specific operations can differ by copy method and preservation setup. Do not assume a setting survived: copy to one destination, open the Stabilizer and Sizing controls, and verify the result before applying the same operation to a full selection. Also review Copy Grade > Preserve Camera Raw Settings before applying a look to raw footage. A copied tree may contain camera-specific CSTs or LUTs. Confirm source, working and output color spaces in both projects; do not add duplicate input/output transforms to an RCM-managed pipeline. The [RCM and CST workflow guide](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/) explains which transforms belong where. ## Copying a Resolve Grade Is Not the Same as Matching Shots A copy moves numbers. It doesn't know that your second camera was a stop and a half under, or that the sun moved between takes. Identical wheel positions on differently exposed footage produce two different images, which is why a copied grade so often looks wrong on the clip next door. Balance first, then copy the look. Shot Match analyzes clips against a reference instead of copying a node tree. Auto Color analyzes the current frame for an automatic correction. A LUT is a color transform, not a saved editable node graph. Keep those operations separate from copying an existing grade. Review automatic corrections rather than treating them as a finished match. The [shot-matching guide](https://davinciresolveclub.com/davinci-resolve-shot-matching/) covers reference selection and comparison; the [automatic-color guide](https://davinciresolveclub.com/davinci-resolve-auto-color/) explains the separate analysis tools. Check both the image and the waveform or vectorscope after every copy. The scopes expose black-point, exposure and color-balance differences that can be harder to judge on an uncalibrated display. The [beginner grading workflow](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/) covers the correction order that makes copying work at all. ## Copy Grade FAQ ### Does copying a color grade in DaVinci Resolve also copy power windows and tracking? Power windows and qualifier settings are part of a grade, but an ordinary clip-to-clip grade copy excludes keyframes and motion tracking. Use Apply Grades Using when copying keyframed Gallery grades, or copy/paste the individual node when you need its windows, qualifiers, keyframes or tracking. Input Sizing remains controlled by Keyframe Timeline Mode and Copy Grade: Preserve Input Sizing. ### Can I copy a color grade between two different DaVinci Resolve projects? PowerGrade albums are shared across projects in the same project library for the same user. For another library or machine, export a still and send its reference image with the matching DRX file. A DRX can be imported alone, but cannot provide the missing reference image for a wipe. ### Do I need DaVinci Resolve Studio to copy a color grade? No. Copy and paste, middle-click copying, gallery stills, Apply Grade, Append Node Graph, groups, shared nodes and node rippling are part of the standard Color page. Remote Grades that link instances of one Media Pool source are different from Studio's remote grading between systems. A copied grade can still depend on Studio-only effects, installed LUTs or third-party plug-ins. Copying the nodes does not provide those licenses or missing resources. Check the [free versus Studio guide](https://davinciresolveclub.com/davinci-resolve-vs-studio/) before sharing effect-heavy grades. ### Can I copy a grade to a clip on a different timeline? A saved Gallery still is one way to copy a grade between timelines, but it is not required. Open the Gallery Timelines album and use its timeline dropdown to browse grades from another timeline in the current project. Select the destination and apply the source grade. Check the active grade level and node-stack scope before applying it. ### How do I undo a copied color grade in DaVinci Resolve? On the Color page, select the affected clip and use Edit > Undo: Cmd+Z on macOS or Ctrl+Z on Windows/Linux with the default preset. Each clip has its own Color undo history, so inspect every affected clip after a multi-clip operation. Closing the project clears undo history. Reset commands remove adjustments; they do not restore the previous grade. Restore a saved version, still or project backup if undo is unavailable. ### Does copying a color grade overwrite the grade already on the clip? Middle-click, a full clipboard paste and Apply Grade overwrite the destination grade, subject to the Copy Grade preservation settings in the Gallery menu. Append Node Graph adds the saved nodes to the existing tree instead. Copying a single node writes into the one node you paste onto and leaves the rest of the tree alone. The safe shortcut is the one that preserves the boundary you need: replace, append or stay linked. The [Color Grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/) connects this transfer workflow with nodes, scopes, LUTs and color management. ### How to Duplicate a Clip in DaVinci Resolve (Fast Ways) URL: https://davinciresolveclub.com/duplicate-clip-davinci-resolve/ Last updated: 2026-09-12T20:34:56.000Z On the Edit page, select the clip you want to copy, hold **Alt** on Windows or Linux or **Option** on Mac, then drag it to the new position. Release the mouse button before releasing the key. The original stays in place. For an exact start frame, copy the clip and paste at the playhead instead. Use **Paste Insert** when you need to make room between existing clips. **Duplicate Clip** in the Media Pool has a different purpose: it creates another project source entry, with its own metadata and markers. None of these operations creates another media file on disk. The shortcuts below assume Resolve's default keyboard mapping. If you use a different preset, the menu command is the reliable reference. ## Duplicate a timeline clip with Alt/Option-drag 1. Select the clip, or select several clips to copy them together. 2. Hold Alt on Windows/Linux or Option on Mac. 3. Drag the selection to an empty destination in the timeline. 4. Release the mouse, then release Alt or Option. Keep the modifier down until the drop is finished. If the original disappears from its starting position, undo the move and repeat the sequence. Check the destination before dropping: a copy should not replace a shot you meant to keep. ![Selected timeline clip with Alt or Option drag steps and mouse-before-key release order](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drag-annotated-v1.webp) Annotated adaptation of [Blackmagic Design’s](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) Edit-page example. Select the clip before dragging and keep the modifier held until the mouse is released; no completed copy is shown. You can copy a selected transition with the same modifier-drag gesture, dropping it on another edit point. ### Copy only the video or audio Turn off **Linked Selection**, select only the component you need, then duplicate it. The default toggle is Ctrl+Shift+L on Windows/Linux or Command+Shift+L on Mac. Turn Linked Selection back on afterward so your next move selects linked picture and sound together. You do not need to permanently unlink the clip; use the [audio splitting guide](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/) if permanent separation is the task. When copying linked video and audio to other tracks, inspect both components before dropping. **Timeline > Linked Move Across Tracks** controls whether dragging picture vertically also changes its linked audio track. It does not remove their horizontal timing relationship. ## Copy and paste at the playhead Select the timeline clip and press Ctrl+C / Command+C. Choose the destination track using the controls below, set the playhead where the copy should begin, then press Ctrl+V / Command+V. A normal paste overwrites media occupying that track’s destination range, so choose empty space unless replacement is intentional. To put the duplicate directly above its original, place the playhead at the original's first frame and choose the higher video destination before pasting. If you also copied audio, choose its destination separately. ![Timeline playhead as the paste start, with overwrite and Paste Insert warnings](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/paste-annotated-v1.webp) Annotated adaptation of [Blackmagic Design’s](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) timeline example, before pasting. Set the playhead and destination first; normal Paste can replace clips already in that range. ### Paste onto a different track In the current Edit interface, use the **red Destination Track Selector** buttons in the track headers. Older tutorials call this Auto Select or Auto Track Selector. Since Resolve 20.2, the old standalone Auto Select icon has been replaced by the red timeline buttons. The blue column beside them patches source-viewer components. 1. Copy the clip and position the playhead. 2. Alt/Option-click the red destination button for the video track you want. This leaves that video destination enabled and disables the other video destinations. 3. If the copy includes audio, choose the audio destination the same way. Video and audio selection are separate. 4. Paste, inspect both components and restore the destination selection you need for subsequent edits. Blackmagic's [current reference manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) describes these controls under Editing Basics. Do not confuse selecting a destination with locking a track or controlling its ripple behavior. ![Red Destination Track Selector and separate Sync Lock controls in the Resolve timeline header](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/destination-sync-annotated-v1.webp) Annotated interface reference: the red destination button selects where an edit goes; Sync Lock determines whether other tracks follow a ripple. The example identifies controls without changing their enabled states. For a multi-track selection, the lowest copied track establishes the base and higher clips keep their relative arrangement. Resolve can create missing tracks. This matters when copying between timelines with different layouts: inspect the entire pasted stack, not just its first video clip. If pasted audio loses a channel, check the destination track's format. Extra channels are muted when a clip contains more channels than the track supports. Right-click that track's header and use **Change Track Type To** to choose a suitable channel configuration. ### Copy only part of a clip Clear any manually selected clips, mark the required timeline range with **I** and **O**, and enable the destination selectors for the tracks you want to copy. Copy, clear the range with **Alt+X / Option+X**, move the playhead and paste. Clearing the marks prevents the old range from interfering with the destination. To make the destination In/Out range limit a paste, enable **Preferences > User > Editing > Prioritize pasting to the in and out range**. Leave that behavior out of an ordinary whole-clip copy unless you specifically want a range-limited result. ## Paste Insert without overwriting the next shot Copy the selection, set the playhead and choose **Edit > Paste Insert**. Its default shortcut is **Ctrl+Shift+V / Command+Shift+V**. The selection is inserted at the playhead and later material moves to make room. Before inserting, check **Sync Lock** on the other tracks that must follow the edit. Sync Lock controls participation in ripple operations independently of the red destination selectors. Blackmagic explains that separation in its [track-control walkthrough](https://www.linkedin.com/posts/blackmagic-design%5Fwhats-new-in-davinci-resolve-202-watch-activity-7371418733447323648-G3Dj?ref=davinciresolveclub.com). For example, disabling Sync Lock on a music track can keep it from following an insertion on a video track. That also changes its alignment with picture that moves. Leave Sync Lock enabled when those moments must stay together, then check the first sync point after the insertion. A track's padlock is different: it prevents edits to that track. Use **Copy**, not Cut, when the original must remain. After inserting, inspect titles, sound effects and dialogue on neighboring tracks before continuing. ## Duplicate a Media Pool source In the Media Pool, select the clip and choose **Edit > Duplicate Clip**, or right-click it and choose **Duplicate Clip**. You can also Alt/Option-drag a selected clip into another bin to create a duplicate there. ![Media Pool clip selection and Duplicate Clip command for a separate project source entry](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/media-pool-annotated-v1.webp) Annotated adaptation of [Blackmagic Design’s](https://www.blackmagicdesign.com/products/davinciresolve/media?ref=davinciresolveclub.com) Media Pool example. Duplicate Clip creates another project entry, not another file on disk; the menu command is described beside the interface. The new entry can have its own metadata and markers. It still refers to the same underlying media file. Renaming the project entry does not create a new recording or a second copy on storage. ### Make an independent compound copy Copying a compound clip on the timeline creates another instance of the same nested source. Editing clips **inside** that compound can therefore change what its other instances contain. That is different from trimming or applying an effect to one outer timeline instance. For a separate nested version, duplicate the compound in the **Media Pool**, give the new entry a recognizable name and insert that new source into the timeline. Confirm that you opened the new compound before changing its contents. The [compound-clips guide](https://davinciresolveclub.com/davinci-resolve-compound-clips/) covers opening, editing and decomposing compounds when you need their individual clips back. If it arrives as separate clips, turn off Edit > Edit Options > Decompose Compound Clips on Edit before inserting the new source again. ## Copy the settings instead of the clip If you want a different shot to use the same adjustments, copy the source clip, select the target and choose **Edit > Paste Attributes** with **Alt+V / Option+V**. Tick only the attributes you want to transfer. You are applying settings to the selected shot, not inserting another clip. When transferring a speed change, check **Ripple Sequence** in the dialog before applying it. Use the [clip-speed guide](https://davinciresolveclub.com/change-clip-speed-davinci-resolve/) for retiming decisions. On the Color page, **\=** applies the grade from one clip prior; the [copy-a-color-grade workflow](https://davinciresolveclub.com/copy-color-grade-davinci-resolve/) explains the other grade-copy choices. For the next editing step, use the [split-and-trim guide](https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/) to shape the copy or the [text guide](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/) for title changes. The [DaVinci Resolve Tutorial hub](https://davinciresolveclub.com/davinci-resolve-tutorial/) groups those beginner tasks. ## Duplicate clip FAQ ### What is the shortcut to duplicate a clip in DaVinci Resolve? On the Edit page, use Alt/Option-drag or copy with Ctrl/Command+C and paste with Ctrl/Command+V. The Media Pool's Duplicate Clip command creates a separate source entry. Keyboard presets can change assigned shortcuts, so check the command in the menu if your mapping differs. ### Why does Alt-drag move the clip instead of copying it? Check the release order: keep Alt or Option held until after you release the mouse. Select the timeline clip before dragging and confirm that its destination track is unlocked. If you moved the original, undo before trying again. ### How do I duplicate a clip onto another track at the same time? Copy it, place the playhead at its original start frame, Alt/Option-click the red destination selector for the new video track, then paste. Set the audio destination separately if audio was copied. Check both components after the paste. ### Does duplicating a clip create another media file? No. Timeline copies reuse their source media. Duplicate Clip in the Media Pool creates another project source entry with separate metadata and markers, but it does not copy the physical media file. ### How do I duplicate without overwriting existing clips? Use Edit > Paste Insert, or Ctrl/Command+Shift+V. It inserts at the playhead and makes room for the copied selection. Check Sync Lock on neighboring tracks so the tracks that must follow the edit participate in the ripple. ### Why does changing a copied compound affect the original? Timeline instances can share the same compound contents. For an independently editable nested version, use Duplicate Clip on the compound in the Media Pool, rename it and insert that new source before opening its contents. Check that you are editing the new compound, not the original source. ### How to Clone Yourself in DaVinci Resolve (Clone Effect) URL: https://davinciresolveclub.com/clone-yourself-davinci-resolve/ Last updated: 2026-09-14T19:24:42.000Z A convincing clone effect starts with two performances that share the same camera position, exposure, focus and lighting. In DaVinci Resolve, the easiest version uses two stacked takes and one fixed crop. Use a maintained matte only when the performances cross, and use Fusion tracking only when the camera movement is repeatable enough to align both takes. **Quick answer:** if your clones stand on opposite, non-overlapping sides of a locked frame, stack two takes on separate tracks and crop the upper clip at the split line to reveal the lower take underneath. No drawn mask, no Magic Mask, no Studio license. Save Magic Mask or a Power Window for clones that cross paths, share the center of frame, or move through a changing outline. ## Before You Film Yourself Twice for a DaVinci Resolve Clone Effect Lock the camera on a tripod and keep its position, focal length and focus unchanged between takes. A small bump can misalign background edges across the split. Record a few seconds of the empty scene before moving anything; that clean plate gives you background pixels for later repairs. Lock exposure and white balance manually too, on the camera itself, before your first take. Auto white balance drifting between takes is a real problem that shows up as a visible seam right where your clones meet. Record a few seconds of room tone before and after each performance, and mark a clap, spoken cue, or hand signal at the exact moment one clone needs to react to the other. Trim both clips to that cue once you're editing. Don't assume matching clip lengths on their own keep two takes in sync. What actually keeps them in sync is trimming both clips to the same reference moment, not the raw duration of either one. For the crop method, mark a separate floor position for each performance. Keep hands, props and their shadows clear of the planned split, and avoid moving curtains or fans in the background. For an interaction, rehearse the timing and decide which clone or prop should pass in front. ## Free Method: The Resolve Split-Screen Clone Effect The simplest version of this effect needs no drawn mask, AI isolation, or frame-by-frame rotoscoping. If your clones never cross a fixed line in the frame, this is the entire technique: 1. Put your clean base take on the bottom video track, V1. 2. Put your second take directly above it on V2. 3. Select the V2 clip on the Edit page, open Inspector, then Video and Cropping. If the clone you want from V2 is on the right, increase Crop Left until V1 is revealed on the left. Use Crop Right for the opposite arrangement. Keep Composite Mode at Normal and Opacity at 100 while building the split. 4. If the seam is visible under your lighting, add a small amount of Softness in the Cropping section to blur the edge rather than leaving a hard line. For a locked-off shot, this route stays entirely on the Edit page and works in Resolve Free. The Inspector's Crop Left, Right, Top and Bottom controls create transparency, so the lower V1 take becomes visible. Temporarily lower V2 opacity to compare fixed background edges, then restore it to 100\. Do not use a half-transparent mix as the finished clone effect. Align the interaction cue rather than just the clip starts, and mute unused take audio so the room tone and spoken cues do not double up. The [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=921) defines negative Softness as feathering inside the crop box and positive Softness as feathering outside. Use only enough to hide a minor boundary; softness cannot repair different camera positions, changing shadows or moving background detail. ![Resolve Video Inspector Crop Left, Right, Top, Bottom and Softness controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc144-crop-upper-take.webp) Crop the side you do not need from the upper take; the lower track remains visible through the removed area. Authentic interface from Blackmagic Design’s Resolve 21.1 Reference Manual, p. 921. This only holds up while your clones stay on their own side of that line. The moment they need to reach across it, you're into real masking, covered next. ## Studio Method: Magic Mask for a Resolve Clone Effect In Resolve 21.1, the Color-page Magic Mask 2 is a Studio feature, not a Resolve Free tool. Blackmagic lists it on the [Studio feature page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com). Use it when the upper clone needs a changing subject outline. Leave the base take intact unless that take also needs isolation. Magic Mask 2 builds the selection from Add and Subtract clicks. It no longer has separate Person and Object modes. The older stroke-driven tool remains available as Legacy Object Mask, but it isn't the current default workflow. 1. Keep the base performance on V1 and the take to isolate on V2\. On the Color page, select that V2 clip and add a Serial node for its matte. Confirm the correct take is selected before drawing the mask. 2. Move to a frame where your full outline is visible and unobstructed, not necessarily the first frame of the clip. Open the Magic Mask palette and click once on yourself in the Viewer to add a point. Add more points, or subtract points, only where the mask misses you or grabs background it shouldn't. 3. Set Quality to Better if the edge needs refinement, then track forward and backward from the chosen reference frame across the required shot range. A forward track from the middle does not analyze the earlier frames. Play the entire matte and repair failures before accepting it. 4. Right-click an empty area of the node graph and choose Add Alpha Output, then connect the node's blue key output to the blue Alpha Output connector so the mask carries transparency instead of a color correction. 5. If playback needs relief after the matte is approved, choose Render in Place Magic Mask from the palette’s three-dot menu and select a location for the cached frames. The [manual’s external-matte instructions](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3288) describe this optional step. Keep those files with the project and regenerate them when source timing or the approved mask changes. This is not the Edit-page Render in Place command. For click placement, first-failure repair, matte finesse and the Resolve 21 external-matte command, use the complete [Magic Mask 2 workflow](https://davinciresolveclub.com/davinci-resolve-magic-mask/). Keep this page focused on how that matte participates in the clone composite. Only isolate additional takes that need their own matte. Rendering a mask does not fix a bad edge, and multiple live masks can slow playback. If the composite remains sluggish after caching, use the [DaVinci Resolve slow playback guide](https://davinciresolveclub.com/davinci-resolve-slow-playback/) to check GPU and cache constraints. The broader [Resolve 21 AI tools guide](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/) covers where Magic Mask sits alongside the rest of the Neural Engine features if you want the full picture before deciding on Studio. ## Free Method: Power Window and Tracker Masking The free version skips Magic Mask, but it doesn't skip masking entirely. Power Windows and the Tracker palette ship in every version of DaVinci Resolve, Studio or not, per [Blackmagic's Color page feature rundown](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com). What they don't do is replace Magic Mask's actual job. A Power Window defines a shape. The Tracker can move, rotate, and scale that shape to follow an object through the frame. Neither one turns your shape into a semantic outline that reshapes itself around a moving arm or a turning body on its own. When your own outline changes, you're moving the window's points by hand at the frames where the shape actually changes, and letting Resolve interpolate between those points, not trusting one continuous track to hold a changing silhouette. 1. Select the upper take on the Color page, add a Serial node and draw a Curve Power Window around the region you need to keep. For a separated clone, a loose boundary through unchanged background may be enough; crossings need a closer outline. 2. Open the Tracker palette, set the mode to Window, and track both forward and backward from that frame for a shot where your position moves but your outline doesn't change much. 3. When the outline changes, switch the Tracker palette from Clip to Frame mode before moving window points. Add a keyframe where the fit is still good, move to a changed pose and adjust the shape. Frame mode keyframes and interpolates these edits; Clip mode changes the shape across the whole clip. 4. Right-click an empty area of the node graph and choose Add Alpha Output, then connect the node's blue key output to the blue Alpha Output connector once the shape holds for the full clip. Review the tracked window and the finished composite throughout the shot. Blackmagic’s [Frame-mode instructions](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3328) explain the difference between a clip-wide correction and an animated shape. For complex limbs, repeated occlusions or several holdouts, the [Fusion rotoscoping workflow](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/) is a more suitable next step than forcing one window to describe everything. ![Color node key output connected to the blue Alpha Output](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc144-color-alpha-output.webp) Keep the green image output connected and route the matte through the blue Alpha Output. Blackmagic’s keying example illustrates the same connection used by a Power Window clone matte. Resolve 21.1 Reference Manual, p. 3447. ## Making Two Resolve Clones Interact or Cross Paths A fixed split works while the content you need from each take stays inside its retained region. Looking at each other does not break it. If a hand, prop or shadow reaches the boundary, first see whether moving the seam through unchanged background avoids the crossing. If not, animate the boundary or isolate the crossing element; a subject mask alone does not preserve every cast shadow. Use the clap, spoken cue or hand signal from the shoot to find the exact frame where the interaction needs to land. Trim both clips to that reference before masking; matching raw clip lengths doesn't synchronize two performances. For a Fusion version, select the aligned, overlapping video takes on the Edit timeline, right-click and choose New Fusion Clip. Open Fusion and identify each MediaIn by viewing it; do not infer which take it contains from the node number. Connect the base take to Merge’s orange Background input and the upper take to its green Foreground input, then send Merge to MediaOut. The [manual’s Merge input reference](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=1403) distinguishes these from the blue Effect Mask input. ![Fusion Merge combines a green foreground branch with an orange background branch](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc144-fusion-merge-inputs.webp) The manual uses a keyed foreground to demonstrate Merge wiring. For a clone, connect the second take as foreground; a Polygon on the blue Effect Mask input can limit its visible region. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1403. Connect a Polygon or B-Spline mask to the Merge’s blue Effect Mask input to limit where the upper take appears. A loose garbage mask can discard unwanted background when its boundary stays away from either performance. It is not a detailed subject matte and will not solve a body crossing that boundary. Animate the shape when needed; keep the base take visible outside it. When the front-to-back order changes, use a separate holdout shape or another masked branch for the crossing hand, body or prop. The later foreground Merge appears on top where its alpha and mask allow it. Check the first overlap frame, the tightest crossing and the last overlap frame, then play the interval; one correct still frame is not enough. ## Moving-Camera Clone Effect in Fusion A moving-camera clone isn't the fixed-crop method with stabilization added at the end. Both takes need repeatable camera movement or enough shared background detail to produce compatible tracks. If the camera path and parallax differ substantially between takes, no node arrangement can make the perspectives identical; a controlled reshoot is often faster and cleaner. In Fusion, track stable background detail, not the performer, in each take. Use compatible reference frames. One tracked pattern supports position; the Resolve 21.1 manual requires at least two for Steady Angle and Steady Size. More patterns do not make incompatible perspectives match. Steady each take, then register the two backgrounds at the reference frame before masking and merging. Independent stabilization removes motion relative to each take; it does not automatically align one take to the other. Compare fixed edges across the full shot, not just the reference frame. For translation-only motion, connect a pre-Merge Transform Center on each take to that take's Tracker Steady Position. After the Merge, connect one post-Merge Transform Center to the base take's Unsteady Position to restore the chosen camera move. ![Fusion Transform Center Connect To menu with Tracker Steady Position selected](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc144-tracker-steady-connection.webp) This connection counteracts tracked translation before compositing. Register the second take separately, then restore the base move after Merge with Unsteady Position. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1795. Rotation and scale also require the paired Steady/Unsteady Angle and Size connections with the corresponding pivot/axis setup. The [Tracker output reference](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=1793) explains the published controls. This is shot-dependent, so use the [Fusion tracking guide](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/) for the tracker and reference-frame setup rather than treating position-only wiring as a complete solution. Inspect blank edges and parallax throughout the composite. At a hand-off, body turn or crossing, add mask points or keyframes where the outline and occlusion order change. Resolve can interpolate keyed shapes, but it can't decide which clone belongs in front. The [Fusion tutorial for beginners](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) explains Merge order, while the [DaVinci Resolve Fusion hub](https://davinciresolveclub.com/davinci-resolve-fusion/) keeps this effect inside the wider node and tracking path. ## Fixing Resolve Clone Effect Edges, Shadows and Sync Edge flicker can come from a drifting track, an occlusion, changing motion blur, noise or weak subject contrast. On the Color page, use Highlight (Shift+H with the default shortcuts) to inspect the selection, then turn it off to judge the composite. In Fusion, view the relevant mask or alpha channel. Do not treat Color-page Highlight as a Fusion matte-view command. If the takes were shot against a green or blue screen, keying is another route to a subject matte. It does not remove the need to match timing, lighting and foreground order. For chroma-key footage, refine the alpha before chasing edge spill; use the [Delta Keyer guide](https://davinciresolveclub.com/davinci-resolve-delta-keyer/) for that separate workflow. An ordinary room background is not a reason to add a chroma keyer. Keep lights in the same positions and shoot the takes close together if daylight is changing. A shadow may need its own retained region or matte; cutting tightly around the body can remove the contact shadow and make the clone look detached from the floor. Avoid feathering across a second shadow or moving object, which can create a translucent double image. A clean background plate is not mandatory for a locked split because one performance take can remain the base. An empty take is useful when neither performance reveals the background you need or when an unwanted prop or shadow must be patched. Match its camera, lighting and timing where background motion matters. It supplies background pixels, not a missing hand, a correct contact shadow or an automatic occlusion solution. For three or more separated performances, repeat the same upper-track crop logic and keep each take on its own video track. The [duplicate and stack clips guide](https://davinciresolveclub.com/duplicate-clip-davinci-resolve/) covers the underlying timeline mechanics; masking and performance sync still need to be checked for each clone. ## Clone Effect FAQ ### Do you need DaVinci Resolve Studio to clone yourself? No. The split-screen crop method and manual Power Window masking both work in the free version. Magic Mask speeds up masking specifically when your clones cross paths or move through a changing outline, but it's Studio-only. ### What's the easiest way to clone yourself without masking in DaVinci Resolve? Stack two takes on separate tracks and crop the upper clip at a fixed line using Inspector, Video, Cropping. Keep both performances and required shadows inside their retained regions. If something crosses the boundary, move the seam if possible or use an animated boundary or subject matte with the necessary shadow and occlusion work. ### Why do my DaVinci Resolve clone effect edges flicker? A drifting track, occlusion, motion blur, noise or low subject contrast can make an edge flicker. On the Color page, inspect the selection with Highlight (Shift+H with default shortcuts). In Fusion, inspect the mask or alpha channel. Then review the actual composite in motion before changing the edge settings. ### How many clones can you stack in DaVinci Resolve? This workflow has no two-clone rule. The practical ceiling depends on the system, source codec, timeline resolution and compositing method. Cropped split-screen layers are relatively light; multiple live Magic Masks, tracked mattes and high-resolution Fusion branches demand much more GPU memory and processing time. ### Can you do the DaVinci Resolve clone effect without a green screen? Yes. A green or blue screen is optional. A locked-camera crop needs no subject key at all; Power Windows and Magic Mask isolate a subject against an ordinary background. Use Delta Keyer only when the footage was actually shot for chroma keying. ### Can you clone yourself with a moving camera in DaVinci Resolve? Yes, if the takes have compatible camera motion and perspective. Steady the takes, register their backgrounds, composite, then restore the chosen camera move. Translation uses Steady/Unsteady Position; rotation and scale need their paired controls and pivot setup. Different handheld parallax may require a reshoot. **Part of the DRC guide system:** [DaVinci Resolve Fusion hub](https://davinciresolveclub.com/davinci-resolve-fusion/) ### DaVinci Resolve Auto Color: How It Works, When It Fails URL: https://davinciresolveclub.com/davinci-resolve-auto-color/ Last updated: 2026-09-14T18:54:02.000Z Quick answer: Auto Color analyzes the current frame under the playhead and applies a self-contained automatic balance and contrast correction to the selected clip/node. In Resolve 21.1, click the A button in Primaries, choose Color > Auto Color, or use Option-Shift-C on the default macOS keymap. Treat the result as a proposal: compare the node, read the scopes, and reset it when the shot no longer fits the scene. This guide was checked on September 14, 2026 against the [DaVinci Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3128). The manual documents the current-frame analysis, DaVinci Neural Engine method, Rec.709 gamma 2.4 design target, Resolve Color Management behavior, default shortcut and the still-available Legacy Auto Color preference. Those version-sensitive details matter more than a one-click demo from an older release. Auto Color doesn't know which warmth belongs to a sunset, which darkness belongs to a low-key scene or which practical light is intentionally colored. Blackmagic describes it as a neutral starting point and calls the result hit-or-miss. If the correction damages the shot, reset it and grade manually instead of trying to justify the automatic result. ## Where to Find the DaVinci Resolve Auto Color Button Open the Color page and the Primaries palette. The A button is at the lower left of the palette beside the other automatic controls. [Blackmagic's Color-page overview](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com) gives the same task-level instruction: use the auto color button at the left of the color wheels to balance color and contrast. The Resolve 21.1 manual lists three current triggers: click A in Primaries, choose Color > Auto Color, or use Option-Shift-C on the default macOS keymap. A custom keyboard preset can override the shortcut, so search for Auto Color in Keyboard Customization when the menu command works but the keys don't. ![Auto Color A button beside the Primaries white-balance eyedropper](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc143-auto-color-control.webp) Use the A button for an automatic whole-frame proposal. The adjacent eyedropper asks you to choose a white reference. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3129. Auto Balance is also used as a descriptive name for automatic balancing, but check the page before following a tutorial. Resolve 21.1 separately documents Auto Balance in the Photo page’s Looks toolbar and Photo Inspector adjustments. The Cut page has Auto Color in its Viewer Tools Color section. This walkthrough uses the Color page so you can select, compare and reset the correction node directly. [The manual distinguishes Photo controls](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=605) and [Cut Viewer Tools](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=771). ## How Resolve Auto Color Actually Balances a Shot Auto Color reads the frame under the playhead and applies an automatic correction. Do not expect it to expose an editable recipe of Lift, Gamma and Gain moves. Compare the image with the correction node enabled and disabled, then make any manual refinements on a separate node. Since Resolve 16, the command has used an algorithm based on the DaVinci Neural Engine. Blackmagic says it was developed for Rec.709 gamma 2.4 and can work with Resolve Color Management normalizing media before the analysis. Legacy Auto Color is still available under Preferences > User > Color. With Use Legacy Auto Color enabled, Resolve neutralizes RGB balance at the darkest and brightest portions of the image, then moves Master Lift and Master Gain toward 0 and 100 percent. Leave it off unless you deliberately need that historical behavior; it changes what the same A button does. ## Is Resolve Auto Color Free or Locked to Studio Auto Color is available in Resolve Free as well as Studio. A Neural Engine label does not automatically mean a tool requires the paid edition. Blackmagic’s desktop feature matrix explicitly lists Auto Color as available, while Magic Mask is marked Studio. [Check the official edition matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5FStudio%5F20%5FFeatures.pdf?ref=davinciresolveclub.com) (the published matrix is labeled Resolve 20; the current 21.1 manual continues to document Auto Color without a Studio restriction). Magic Mask isolates a subject for selective work; it is not an automatic whole-shot balance command. The [Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) covers upgrade decisions. ## Why Resolve Auto Color Gives You a Worse Image Bad results usually have one of three roots: the playhead is on an unrepresentative frame, the image reaches the algorithm in an unsuitable color-management state, or the scene contains an intentional cast or contrast shape that automatic neutralization mistakes for an error. First, select the intended clip and an ordinary serial node. Apply Auto Color once on a dedicated node so the proposal can be disabled, reset or deleted without touching the rest of the grade. Because the adjustment is opaque, comparing that node is more informative than staring at unchanged wheel values or clicking A repeatedly. Second, move the playhead to a frame that represents the clip. A flash, whip pan, blown window, lighting transition or atypical close-up can produce a correction that makes no sense for the rest of the take. Auto Color analyzes one frame, but the resulting clip correction remains in force across the clip unless you deliberately limit or animate it. Third, test the command inside the real pipeline. Auto Color was developed around normalized Rec.709 gamma 2.4 imagery. Unnormalized log, a wrong input transform or a misplaced LUT can distort what the algorithm receives. Check the pipeline before adding another conversion; the [Resolve color-management guide](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/) separates RCM, CST nodes and LUT order. Watch faces as well as neutral objects. A tungsten-lit face can legitimately look warm, and mixed lighting can put different casts on opposite sides of a face. An overall automatic balance cannot decide which light should remain colored. Reject the proposal if it makes skin implausible or introduces a mismatch at the cut; do not force every face onto a fixed vectorscope line. Play through the whole shot and its neighbors before keeping the correction. ## A Safer Resolve Auto Color Workflow, Step by Step Compare before and after under the same viewing conditions. Use Waveform to catch crushed or lifted endpoints, RGB Parade to find a new channel imbalance and Vectorscope to check an implausible hue or saturation shift. The [Resolve scopes guide](https://davinciresolveclub.com/davinci-resolve-scopes-explained/) explains those readings; here the goal is simply to decide whether Auto Color helped this shot. To compare only this step, select the dedicated node and choose Color > Nodes > Enable/Disable Selected Nodes. The documented macOS shortcut is Command-D; confirm your own mapping in Keyboard Customization. View > Bypass Color and Fusion is a different comparison: it can bypass grading and Fusion effects according to its checked options. It does not isolate Auto Color. [See selected-node disabling and reset controls. ](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3392) ![View menu Bypass Color and Fusion options for grades and Fusion effects](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc143-bypass-color-fusion-menu.webp) Global bypass can hide much more than Auto Color. Use Enable/Disable Selected Nodes to compare just the dedicated correction. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3393. 1. **Choose the frame.** Scrub away from flashes, transitions and atypical moments to a representative frame. 2. **Isolate the proposal.** Add a dedicated serial node named Auto Balance before creative look nodes. 3. **Store a comparison.** Grab a still or set up a clean before/after view before changing the node. 4. **Apply once.** Click A, use Color > Auto Color, or press the default macOS shortcut Option-Shift-C. 5. **Disable the node.** Compare the selected Auto Balance node on and off; don't confuse later look nodes with the automatic change. 6. **Read the signal.** Check Waveform, RGB Parade and Vectorscope for new clipping, imbalance or an implausible neutralization. 7. **Keep, refine or reset.** If the proposal helps, continue grading downstream. If it hurts, reset or delete that node. 8. **Change the reference.** Use White Balance, Shot Match or Color Match when the problem calls for a white patch, reference clip or chart. ## Where to Apply Resolve Auto Color in Your Node Tree Auto Color applies its hidden adjustment at the selected correction stage. Upstream RAW decoding, normalization and earlier nodes affect the signal it sees; downstream nodes can still change the final image. Put the command on an early ordinary serial node, not deep inside a branch already restricted by a qualifier or power window. For a simple SDR pipeline that explicitly converts camera log to Rec.709 Gamma 2.4 before grading, a technical transform followed by Auto Color and then a look makes the order easy to inspect. This is an example, not a universal CST recipe. In RCM, verify the assigned input space and the project’s working and output spaces; do not add a second log-to-Rec.709 conversion just because the Viewer already looks normalized. Keep the existing output transform active during the comparison. [Follow the node-order guide for more complex trees.](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) ## Auto Color vs Auto White Balance vs Shot Match vs Color Match These four tools aren't stronger and weaker versions of one command. Each one uses a different reference. Choosing the reference that actually exists in the shot is the useful decision. Auto Color reads the whole current frame. Auto White Balance uses the Primaries eyedropper and expects you to sample something that's supposed to be white, isn't off-white and is not clipped. Shot Match changes selected target clips toward a separate reference clip through Shot Match to This Clip. Color Match uses a photographed chip chart aligned in the Color Match palette. None of those references guarantees a finished grade; each result still needs a visual and scopes check. ![Primaries White Balance eyedropper next to the automatic correction control](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc143-white-balance-control.webp) Choose the eyedropper only when you can sample an unclipped feature that should be white under the intended neutral lighting. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3127. | Tool | Reference | Use it when | Trigger | | ------------------ | ------------------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------ | | Auto Color | Current frame at the playhead | You need a fast neutral proposal for one shot | A in Primaries; Color > Auto Color; Option-Shift-C on the default macOS keymap | | Auto White Balance | An unclipped patch that should be white | A trustworthy white reference is visible | White Balance eyedropper in Primaries | | Shot Match | A separate reference clip | Target clips should move toward an already balanced shot | Right-click the reference and choose Shot Match to This Clip | | Color Match | A supported color chart photographed on set | The chart was captured under the relevant lighting | Align the chart in Color Match and click Match | Use Auto Color when the current frame itself is the only available reference. Use Auto White Balance only when the frame contains an unclipped object that should genuinely be white, not a warm wall, gray object or clipped reflection. Use Shot Match when another clip is the target look. Use Color Match when production captured a supported chart under the lighting you need to normalize. ## Applying Resolve Auto Color Across Multiple Clips Copying a correction isn't the same as running a new analysis. Applying a Gallery still to another clip copies the stored grade. Auto Color analyzes the current playhead frame on the selected clip. For multiple targets that should resemble one balanced shot, select the targets, right-click the reference and choose Shot Match to This Clip. Blackmagic says the updated Shot Match algorithm was designed to follow Auto Color on both the target clips and the reference. That's an order of operations, not permission to batch-accept the results: normalize first, create a neutral proposal only where it helps, match toward the strongest reference, then review every target in sequence. ![Blackmagic example sequence before and after matching selected clips to clip 62](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc143-shot-match-comparison.webp) Top: original sequence. Bottom: Blackmagic’s Shot Match example toward clip 62\. This illustrates reference-based matching, not an Auto Color-only result. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3130. For reference selection, match direction and a full sequence review, use the [shot-matching walkthrough](https://davinciresolveclub.com/davinci-resolve-shot-matching/). Keep this page’s Auto Color decision separate from copying a finished grade or balancing an entire scene. ## Frequently Asked Questions About Auto Color ### Is DaVinci Resolve Auto Color free or Studio only? Auto Color is available in Free and Studio. Blackmagic’s edition matrix lists Auto Color as available rather than Studio-only, and the 21.1 manual documents it as a standard command. Do not infer a paid license requirement just because its algorithm uses the DaVinci Neural Engine. ### Why does DaVinci Resolve Auto Color make my footage look worse? Usually the playhead frame is unrepresentative, the signal reaches the algorithm before correct normalization, or the scene contains intentional warmth, coolness, darkness or brightness that the automatic neutral target misreads. Reset the dedicated node and correct the shot manually when the proposal harms the scene. ### Can I apply DaVinci Resolve Auto Color to multiple clips at once? Not as a documented one-click reanalysis of every selected clip. Applying a Gallery still copies one fixed grade. Use Shot Match when several selected targets should move toward a reference clip, then review each result. ### What's the keyboard shortcut for DaVinci Resolve Auto Color? Option-Shift-C is the documented default on macOS in Resolve 21.1\. You can also choose Color > Auto Color. If the keys do nothing, check Keyboard Customization because a preset or personal mapping can override the default. ### Does DaVinci Resolve Auto Color work differently than the legacy version from older releases? Yes. Resolve 21.1 still offers Use Legacy Auto Color under Preferences > User > Color. The default method uses the newer Neural Engine-based analysis; Legacy balances the darkest and brightest RGB regions and moves Master Lift and Gain toward 0 and 100 percent. ### How do I undo DaVinci Resolve Auto Color? On the Color page with the same clip active, use Edit > Undo if Auto Color is the most recent color change. Color has a separate undo history for each clip; Undo on the Edit page can undo an edit instead. To discard the dedicated correction, right-click that node and choose Reset Node Grade. This clears every adjustment and keyframe on that node, so use it only when you intend to clear that node. Do not choose Reset All Grades and Nodes unless you mean to erase the entire grade. ### Does DaVinci Resolve Auto Color affect one frame or the whole clip? It analyzes the current frame under the playhead, but the resulting correction applies at the clip/node level. It therefore affects the clip until you limit or animate the correction; choosing a representative frame is essential. ### Why does the DaVinci Resolve Auto Color button do nothing when I click it? Confirm the intended clip and ordinary serial node are selected, place the playhead on a representative frame, and compare that node enabled versus disabled. The automatic adjustment is opaque, so unchanged visible wheel values do not prove nothing happened. If the image is unsuitable, reset the node. Auto Color is only a starting correction. For the complete manual order after this decision, follow the [beginner color-grading workflow](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/). The [Color Grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/) connects that workflow with nodes, LUTs, scopes, color management and the rest of the correction path. ### DaVinci Resolve Scopes Explained: How to Read Every Scope URL: https://davinciresolveclub.com/davinci-resolve-scopes-explained/ Last updated: 2026-09-14T18:27:38.000Z DaVinci Resolve's scopes answer different questions about the same frame. Waveform shows signal level while preserving horizontal position; Parade separates components so channel imbalance is easier to see; Vectorscope maps hue and saturation; Histogram counts pixels across the tonal range; CIE Chromaticity compares color values with a gamut boundary. They measure the signal. They don't decide whether a low-key shot, warm practical light or clipped sun is creatively wrong. A plausible picture on an uncalibrated display can still contain clipped channels or an unintended cast. Use scopes to investigate the signal, and a calibrated reference display to judge its appearance. Verified on September 14, 2026 against the [DaVinci Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3093). On macOS, open the floating window with Workspace > Video Scopes > On/Off (Command-Shift-W). The same floating scopes are available from the Media, Color and Deliver pages; a dual-screen layout can place them on another display. ## Quick Map: Which DaVinci Resolve Scope to Use Five scopes live in DaVinci Resolve's Color page, and you rarely need all five open at once. - **Waveform:** exposure, contrast and clipping while retaining left-to-right image position; choose Y, CbCr or RGB analysis. - **RGB Parade:** component balance in separate lanes; Resolve also offers YRGB and YCbCr parade modes. - **Vectorscope:** hue, saturation, color casts and a skin-hue guidepost. - **Histogram:** pixel distribution from black to white without location in the frame. - **CIE Chromaticity:** a rough gamut-boundary check, with 1931 xy or 1976 uv views. Waveform, Parade and Vectorscope handle most correction work. Histogram is useful when distribution matters more than location. CIE becomes relevant when the delivery gamut is part of the question. Opening every graph at once is not more accurate; it is often just harder to read. ## What a Resolve Video Scope Actually Measures A scope analyzes the current image signal and plots levels or color components instead of reproducing the picture. Its quality setting affects drawing detail: use High when a small excursion needs close inspection, or Auto for a workstation-dependent balance. The graphs do not measure your display’s calibration or prove what another player will show. Confirm the signal path before treating a reading as a delivery check. For a focused working layout, start with 2-Up or 4-Up from Workspace > Video Scopes, then choose a scope from the name menu in each pane. Resolve also supports 1-, 2-, 4- and 9-pane arrangements in the floating window. Use only the panels needed for the decision in front of you. ## Waveform: Exposure and Clipping In Y (luma) mode, the waveform maps signal level from left to right, preserving horizontal position in the frame. Height means level, not vertical position in the shot. This is a signal measurement, not a direct measurement of scene brightness or your monitor’s light output. A bright object in the bottom corner of your frame still shows up near the top of the waveform. In RGB-based modes, the waveform displays channel information rather than brightness alone, covered in more depth below. ![Resolve Y waveform with colorized trace and Extents enabled](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc142-waveform-luma.webp) Read left-to-right position on the horizontal axis and signal level on the vertical axis. Colorize links parts of the trace to image colors. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3097. By default, Waveform and Parade use a 10-bit full-range display scale from 0 to 1023\. The three-dot scopes menu also offers 12-bit, Percentage and millivolt labels. These options relabel the measurement; they don't remap the clip or change the grade. Resolve 21.1 calls the 0–100 option Percentage, so don't treat the label itself as a change to legal range. A trace touching the displayed ceiling is a reason to investigate, not proof that the camera permanently clipped. Check the display range and enabled transforms, compare RGB channels, and lower exposure before the suspected clipping operation. If detail returns, it was still present upstream. Lowering an already clipped recording only makes the flat patch darker; it cannot recreate the missing detail. A bright exterior doesn't have to touch 100 percent to be correctly exposed; there's no single correct mark for every shot, since that depends on the subject, the lighting and the creative call. The waveform confirms your exposure decision. It doesn't hand you a target to hit regardless of what the shot actually needs. ## Waveform vs Parade Modes: Y, RGB, YRGB and YCbCr Open the Waveform pane's custom controls from its option button. Y shows true luma, CbCr isolates the color-difference components, and RGB overlays red, green and blue. Parade is the separated view: RGB, YRGB or YCbCr components appear side by side. Use Y Waveform for a fast exposure read, RGB Parade for channel comparisons, and YCbCr only when that component representation helps the delivery check. Use RGB Parade for a neutral-reference comparison. For component chroma inspection, select CbCr in Waveform or YCbCr in Parade. Waveform does not have the Parade’s YRGB or YCbCr combined modes. A component reading alone is not a complete broadcast compliance test. ## RGB Parade: Finding Color Casts Parade places component waveforms side by side. On a neutral patch, corresponding red, green and blue features should reach comparable levels; a channel that departs from the others reveals the direction and tonal region of an imbalance. This is a comparison of matching image features, not a rule that the entire three traces must have identical shapes. Read the bottom, middle and top of the traces separately. A mismatch concentrated in highlights points to a different correction than one running through the whole signal. The graph identifies where the imbalance lives; it doesn't prescribe a fixed Gain, Gamma or Offset value. A colored lamp or neon sign can legitimately bias the parade. Compare a known neutral surface under the light you intend to render as neutral, such as a grey card or white shirt. Skin is not a neutral RGB patch, so do not equalize its three channels. ## Vectorscope: Hue, Saturation and Skin The vectorscope plots color on a circular graph. Distance from the center is saturation; angle around the circle is hue. A fully desaturated image, pure grayscale, collapses to a single point dead center. Push saturation on any color and its trace moves outward toward the edge, following the same rotational order as a standard color wheel. Enable Show Skin Tone Indicator in the Vectorscope controls to display the traditional in-phase angle. The Resolve 21.1 manual calls it a general guidepost for average skin-tone hue. Complexion, undertone, lighting, makeup, white balance, camera color science and the intended look can all move the trace, so use the line to investigate a hue shift rather than force every face onto it. [Blackmagic's Color page](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com) describes the vectorscope as a way to spot unflattering green, yellow or magenta shifts, not as a universal skin coordinate. If the trace is difficult to read, Vectorscope controls can isolate Low, Mid or High tonal ranges, show 2X Zoom, colorize the graph or display combined extents. Isolate only long enough to diagnose the subject, then return to the full image and judge the result on a calibrated display. The 75% and 100% vectorscope targets are references for color signals, not mandatory skin saturation or universal broadcast-safe limits. The skin line gives no luma target. Judge a face in its lighting context rather than forcing it to a fixed saturation percentage or waveform height. ![Resolve vectorscope controls including tonal ranges zoom and skin tone indicator](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc142-vectorscope-controls.webp) Show Skin Tone Indicator adds a hue reference. ALL restores the complete tonal range after a Low, Mid or High analysis. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3104. ## Histogram: Distribution Without Position Histogram counts how many pixels fall at each tonal value: black at the left, white at the right. Resolve offers RGB and YRGB views. Unlike Waveform, Histogram discards horizontal image position, so a bright window on the left and a bright lamp on the right can produce similar peaks without telling you where either object is. ![Resolve YRGB histogram with separate luma red green and blue distributions](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc142-histogram-yrgb.webp) Horizontal spread shows the occupied tonal range; graph height counts pixels. A peak does not identify where those pixels sit in the frame. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3099. Use Histogram when the shape of the tonal distribution itself is useful, or when you want a second view of channel clipping. Use Waveform when you need to connect a high or low value back to a horizontal region of the image. For grading, that retained position usually makes Waveform the faster diagnostic tool. ## CIE Chromaticity: Gamut Boundaries CIE Chromaticity draws the image analysis over a triangle for the selected working gamut and white point. Resolve 21.1 offers CIE 1931 xy and the more perceptually uniform CIE 1976 uv view, plus an optional second gamut triangle for comparison. If the trace crosses a gamut triangle, the manual treats that as a definite violation of that boundary. The reverse isn't guaranteed: a trace inside the triangle is only a rough indication, because this two-dimensional view can't prove that every value in the three-dimensional color volume is safe across shadows, midtones and highlights. Use CIE as a warning and comparison tool, not as a complete HDR or delivery validator. ![Resolve CIE xy chromaticity scope comparing P3 and Rec 709 gamut triangles](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc142-cie-gamut-comparison.webp) Check the labeled reference triangles before judging an excursion. This chromaticity comparison does not certify luminance or complete delivery compliance. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3100. ## Scope Scale vs Data Levels: Do Not Confuse Them Keep three decisions separate: source-clip interpretation, scope display, and output-file mapping. The scope controls do not repair a wrong source range or export tag. In the scopes’ three-dot menu, Waveform Scale Style chooses 10-bit, 12-bit, Percentage, millivolt or Studio HDR labels. Video Level Scopes is in that same submenu and changes the graph’s Data/Video display mapping. Neither control changes the monitored or rendered image. Clip interpretation and render mapping are separate. A source tagged or interpreted with the wrong range can enter the grade incorrectly; a mismatched Deliver-page range or metadata choice can make the export play washed out or crushed. Don't try to repair either problem by switching the scope ruler. For nominal 10-bit video-range coding, luma and RGB reference black and white are 64 and 940; chroma uses 64 to 960 around neutral 512\. These are coding references, not universal exposure targets. [ITU-R BT.709 defines the HDTV coding conventions.](https://www.itu.int/rec/R-REC-BT.709-6-201506-I/en?ref=davinciresolveclub.com) Resolve’s default scope ruler is 0 to 1023\. Its Deliver-page documentation describes 10-bit Full output as 4 to 1019; that is not a universal definition for every codec. For example, BT.2100 distinguishes narrow-range permitted data from full-range coding. Follow the actual delivery format and receiver, not the scope labels. [Compare the Resolve output-level documentation](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=224) with [BT.2100’s digital representation tables](https://www.itu.int/rec/R-REC-BT.2100-3-202502-I/en?ref=davinciresolveclub.com). Don't choose Full simply because the destination is the web. [YouTube's current upload guidance](https://support.google.com/youtube/answer/1722171?ref=davinciresolveclub.com) says it converts full color range to limited range during processing. The safe workflow is consistent interpretation, output mapping and metadata. The [YouTube export settings guide](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/) covers those Deliver-page choices; the [Color Grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/) keeps them in the wider color-management path. | Scale option | What changes | Use it when | | ------------------------ | ------------------------------------------------------- | ---------------------------------------------------------- | | 10-bit (default) | Labels the WFM/Parade ruler from 0 to 1023 | You want a familiar scale for the internal signal | | 12-bit | Relabels the same measurement on a 12-bit scale | Your specification or hardware workflow uses 12-bit values | | Percentage | Labels the ruler from 0 to 100 | You read percentage faster than code values | | Millivolt | Uses mV labels | You need that engineering reference | | HDR ST.2084/HLG (Studio) | Shows Waveform, Parade and Histogram against nit values | The signal and project are set up for HDR measurement | ## Low Pass Filter and Qualifier Focus Low Pass Filter suppresses signal noise so dense Waveform and Parade traces are easier to read. It affects the graph, not the image, but it can make the visible highlight and shadow excursions appear slightly short. Enable Extents when the filter is on: the outline preserves the true overshoots and undershoots documented by Blackmagic. Display Qualifier Focus connects a viewer sample to every open graph. Turn it on in the Video Scopes option menu, switch the Viewer to Qualifier mode, then move the eyedropper over the image. Resolve circles the sampled pixels in each visible scope. This is more precise than trying to guess which cluster belongs to a face, lamp or clipped reflection. ## Scopes and the Node Tree: What They Actually Measure Scopes normally follow the signal shown in the Viewer after the enabled grade graph. Clicking a different node selects the correction you're editing; it doesn't automatically solo that node or remove downstream processing from the Viewer. The [Resolve nodes guide](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) explains the graph order and bypass controls in context. To inspect an intermediate stage, use an intentional bypass or node-isolation method and confirm what the Viewer is showing before reading the graph. Highlight mode, a qualifier matte or a disabled downstream node can radically change the trace. The same caution applies when evaluating a [LUT in the node tree](https://davinciresolveclub.com/how-to-use-luts-in-davinci-resolve/): confirm the input transform and node order before blaming the scope. ## A Four-Step Resolve Scope Workflow A useful pass moves from broad signal structure to delivery-specific checks: 1. Waveform: find unintended clipping or crushed detail, while respecting the shot's lighting and creative contrast. 2. RGB Parade: compare matching neutral features and locate channel imbalance by tonal region. 3. Vectorscope: check hue direction and saturation; use the skin indicator as a guidepost when a face matters. 4. CIE Chromaticity: compare against the delivery gamut when wide-gamut or HDR output makes that boundary relevant. Then return to the calibrated picture. The graphs answer measurable questions; the image decides whether the correction serves the scene. For the complete correction-first order around this pass, use the [beginner color-grading workflow](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/). ## Scopes: Free vs Studio Blackmagic walks through the five standard scope types in Resolve's Color tools. In the Resolve 21.1 manual, the explicit Studio-only scope feature is HDR (ST.2084/HLG) measurement, which replaces the ordinary Waveform, Parade and Histogram scale with nit values. Standard SDR readings described in this guide don't require that HDR scale. For HDR, select Waveform Scale Style > HDR (ST.2084/HLG) only when the project and signal interpretation match that measurement. The 21.1 manual warns that in a non-Resolve-Color-Managed workflow the scopes still read as HDR even when the selected output space is Rec.709\. Changing the ruler does not turn SDR into HDR or measure the physical nits of your display. [Check the HDR scope warning](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3094) and the [RCM versus CST setup guide](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/) before reading nit values. The [official Resolve Studio page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) describes its HDR scopes as measuring ST.2084 and HLG images. That scale doesn't by itself validate an HDR master: output transform, mastering setup, metadata and format still matter. The [Free versus Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) covers the rest of the paid feature split. ## Common Resolve Scope Mistakes - **Forcing skin onto the indicator.** Blackmagic calls it a guidepost; lighting and complexion still matter. - **Making the entire Parade match.** Compare corresponding neutral features, not unrelated red, green and blue image content. - **Treating the scope ruler as media range.** Scale style and Video Level Scopes change display labels/mapping, not the clip or render. - **Smoothing without Extents.** Low Pass Filter can understate visible excursions unless Extents is enabled. - **Reading an isolated or highlighted Viewer as the full grade.** Check Highlight, bypass and downstream node state first. - **Treating CIE as a complete pass/fail test.** Outside the triangle is meaningful; inside alone isn't proof of a valid color volume. ## Scopes FAQ ### What is the best scope to use in DaVinci Resolve? Start with Waveform for exposure and clipping, Parade for component balance, and Vectorscope for hue, saturation and skin-hue reference. Histogram is a compact distribution view; CIE is a gamut-boundary check. The best scope is the one that answers the current measurement question. ### Are DaVinci Resolve's scopes different in the free version? The five standard scope types are documented in Resolve's Color tools. Resolve 21.1 explicitly marks the HDR ST.2084/HLG nit scale as Studio-only. For ordinary SDR Waveform, Parade, Vectorscope, Histogram and CIE work, the free version provides the measurements described here. See the [free-version feature guide](https://davinciresolveclub.com/davinci-resolve-free-version-features/) for non-scope differences. ### Should I trust my monitor or my scopes in DaVinci Resolve? Use scopes for objective signal questions such as clipping, channel imbalance and gamut excursions. Use a calibrated display and your eyes for appearance, mood and intent. Scopes don't replace monitoring, and an attractive picture doesn't prove technically safe levels. ### Why doesn't my skin tone line up with the vectorscope's skin tone indicator? It may not need to. Resolve's line is a general hue guidepost, not a strict coordinate. Complexion, undertone, lighting, makeup, white balance, camera color science and the creative grade can all move the trace. Investigate an obvious green, yellow or magenta shift; don't force every face onto the line. ### Should I grade to legal range or full range in DaVinci Resolve? Match the delivery specification. Nominal 10-bit video-range reference values are commonly 64–940 for luma/RGB and 64–960 for chroma, but they're coding references, not creative exposure targets. Full range isn't automatically safer for the web: YouTube says it converts full color range to limited during processing. Keep source interpretation, output mapping and metadata consistent. ### What is CIE Chromaticity used for in DaVinci Resolve? It compares the image analysis with one or two gamut triangles in either CIE 1931 xy or CIE 1976 uv. A trace outside the selected triangle identifies a gamut violation. A trace inside is only a rough check, because the two-dimensional graph cannot prove the entire three-dimensional color volume is safe. ### Why does the histogram look different from the waveform in DaVinci Resolve? Waveform preserves horizontal frame position, so a bright feature on the left appears on the left side of the graph. Histogram counts pixels at each tonal value and discards location. Use Waveform to find where a level occurs; use Histogram to read the overall tonal distribution quickly. ### Why aren't my scopes showing up in DaVinci Resolve? Choose Workspace > Video Scopes > On/Off on the Media, Color or Deliver page. If the window opens without a trace, confirm that the Viewer has an active frame and the intended scope pane is selected. Check Highlight, bypass and any custom display range. To undo customized scope controls, open the scopes option menu and choose Reset All. ### What's the difference between IRE and 10-bit values on DaVinci Resolve's scopes? Resolve 21.1 offers a Percentage scale and a default 10-bit scale. Percentage labels the ruler 0–100; 10-bit labels it 0–1023\. They're two labels for the internal measurement, and switching between them doesn't change the grade, the media range or the render. ### Can I zoom in on the DaVinci Resolve vectorscope? Yes. Enable Show 2X Zoom in the Vectorscope controls. You can also view the full tonal range or isolate Low, Mid or High ranges. Zoom makes a small trace easier to inspect; it doesn't make the skin indicator a mandatory target. ### Why do my DaVinci Resolve scopes look different after I export? Color-page scopes measure the signal currently presented through Resolve's Viewer path. An exported file can differ because of an output transform, data-level mapping, codec conversion, metadata tags or the playback application's color management. Re-import the export into a correctly configured project when you need to compare the encoded file with the timeline signal. The useful habit is simple: choose the graph by question, confirm the Viewer and scale state, make the correction, then judge the picture again. That turns scopes from background decoration into a fast diagnostic layer without letting them dictate the look. ### How to Remove Background Noise in DaVinci Resolve URL: https://davinciresolveclub.com/remove-background-noise-davinci-resolve/ Last updated: 2026-09-14T15:36:26.000Z Quick answer: diagnose the noise before choosing the processor. Use Fairlight Noise Reduction for steady broadband hiss, fan or room tone; De-Hummer for a narrow 50/60 Hz fundamental and its harmonics; a Gate or clip edit for noise mainly between phrases; and Studio's Voice Isolation for changing background around recorded speech. This guide sits in the [Fairlight audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) and was rechecked on September 14, 2026 against the [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). A constant refrigerator compressor, fan, HVAC bed or preamp hiss is a good candidate for a learned noise profile because the unwanted sound stays reasonably consistent. Variable traffic, wind, crowd noise and competing voices need a different test. Room reverberation is another problem again: reducing the noise floor doesn't remove reflections already mixed into the voice. Blackmagic's [current Fairlight overview](https://www.blackmagicdesign.com/products/davinciresolve/fairlight?ref=davinciresolveclub.com) is the product boundary; the steps below name the controls that actually solve each case. ## Which DaVinci Resolve Noise Removal Tool Should You Use? Start here before touching a control. The same phrase, background noise, can describe five different failures, and each one reacts differently. - Steady broadband hiss, fan or room tone: test Noise Reduction in Manual or Auto Speech mode. - Narrow mains hum or buzz: start with De-Hummer and verify the fundamental plus harmonics. - Noise mainly between words: use the channel Gate, a short fade or manual clip gain; none removes noise under speech. - Changing background around recorded dialogue: test Voice Isolation in Studio and listen for separation artifacts. - Dialogue that's only uneven in level: use Dialogue Leveler or compression after restoration; leveling isn't noise removal. | Problem | Use this first | Why | | -------------------------------------- | ------------------------------------ | -------------------------------------------------------------------- | | Steady hiss, fan, fridge, HVAC | Noise Reduction FX in Manual + Learn | It can learn a constant noise print and reduce matching noise. | | Traffic, wind, crowd, mixed background | Voice Isolation in Studio | A useful first test for changing sound; listen for speech damage. | | Noise only between words | Gate in Dynamics | A gate lowers gaps. It doesn't remove noise under speech. | | 50/60 Hz electrical hum | De-Hummer | Hum sits at predictable power-line frequencies and their harmonics. | | Low-end rumble | High-pass EQ below the useful voice | Raise the cutoff only until rumble improves without thinning speech. | ## DaVinci Resolve Noise Reduction FX for Free-Version Background Noise Cleanup The tool is called Noise Reduction and lives among the Fairlight FX. On the Edit page, open Effects Library, then Audio FX, search for Noise Reduction, and drag it onto the clip. On the Fairlight page, you can add the same plugin as a clip effect or in a track's Effects insert when every clip on that track shares the same noise. Clip processing is safer when recordings came from different rooms or microphones; track processing is faster only when the problem is genuinely consistent. ![Fairlight Noise Reduction controls for Manual Learn and Listen to Noise Only](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc141-noise-reduction.webp) Learn from noise alone, then disable Learn before speech. Use Listen to Noise Only to check what is being removed, and turn it off to review the result. Source: Blackmagic Design, Resolve 21 Reference Manual, p. 4041. Noise Reduction offers Auto Speech Mode and Manual workflows. Auto Speech adapts its noise profile during playback without a Learn pass. For a repeatable Manual pass: find a region containing only the unwanted sound, enable Manual and Learn, then play that region. Turn Learn off before speech starts so the wanted voice does not enter the profile. Replay a complete phrase, not just the gap you sampled. Enable Listen to Noise Only while adjusting. If intelligible consonants or words appear in the removed signal, reduce the processing. Turn Listen to Noise Only off again to hear the cleaned recording, then compare with Bypass at matched loudness. Do not leave the noise-only monitor enabled for final playback. Threshold relates processing to the source signal-to-noise ratio. In Auto Speech, Attack controls how quickly the detected noise profile updates; Sensitivity exaggerates that profile and can remove more wanted dialogue. Ratio trades transient preservation against profile accuracy. Frequency and Time Smoothing address ringing and temporal artifacts. Dry/Wet blends processed and original signal, while Level compensates output loss rather than improving the reduction itself. The De-Hiss, De-Rumble and combined presets are starting configurations, not noise profiles captured from your recording. Compare bypassed and processed playback at matched loudness: a louder result can seem clearer even when it contains more artifacts. ## DaVinci Resolve Voice Isolation for Studio-Only AI Background Noise Removal Voice Isolation uses the DaVinci Neural Engine to separate recorded human voice from competing sound and remains a DaVinci Resolve Studio feature. Blackmagic's [current Studio page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) and the manual agree on that boundary; the Free version doesn't expose it. The [Resolve 21 AI tools guide](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/) separates it from Dialogue Separator, Music Remixer and other Neural Engine features. In Resolve 21 Studio, Voice Isolation can be used from clip controls or the Fairlight track-effects area. For a full dialogue track, open the three-dot Mixer menu and make sure Track FX is visible. The Amount control blends the original and isolated voice. The current manual notes that values around 70 to 80 can keep a more natural result while providing strong isolation, but that is a listening reference rather than a preset for every recording. Try Voice Isolation when the background changes over time or overlaps the voice, such as traffic, fans that ramp up, crowd ambience or music. Manual Noise Reduction is a better first test for steady, sampleable noise. Neither tool guarantees a clean result when another voice or a sharp transient occupies the same frequencies and moment as the wanted dialogue. Dialogue Separator is another Studio option when you want to retain room sound while lowering crowd noise or music. It gives separate level controls for Voice, Background and Ambience rather than one isolation blend. Start with the original balance and lower only the unwanted component. The Resolve 21 manual documents it as mono-only: stereo material needs separate mono processing, not an assumption that it behaves like stereo Voice Isolation. These controls rebalance the recording; they do not guarantee clean separate stems. See [Blackmagic’s Dialogue Separator documentation](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=4016) for the channel-format restriction. ![Studio Dialogue Separator Voice Background and Ambience level controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc141-dialogue-separator.webp) Lower Background while retaining useful Ambience. The documented plugin is mono-only, unlike Voice Isolation’s mono and stereo support. Source: Blackmagic Design, Resolve 21 Reference Manual, p. 4016. ## Voice Isolation vs Dialogue Leveler Dialogue Leveler primarily rides louder dialogue down and softer dialogue up. Its Background Reduction option also gently reduces background noise according to the selected preset, so calling it incapable of noise reduction would be misleading. It is not the same separation process as Voice Isolation and is not a replacement for targeted hum or broadband repair. Level only if the restored speech still needs it. The [Voice Isolation vs Dialogue Leveler comparison](https://davinciresolveclub.com/voice-isolation-vs-dialogue-leveler/) covers the full controls and desktop Free/Studio distinction. ## DaVinci Resolve Noise Gate Method for Removing Noise Between Words A gate doesn't remove noise underneath speech. It reduces the level when the signal falls below its threshold, so it can hide room tone in pauses. In the Fairlight Mixer, open the channel's Dynamics panel and enable Gate. Set the threshold just above the noise floor but below quiet syllables, then adjust attack, hold and release so the gate opens before words and closes without cutting breaths or word endings. Use this branch when the noise is acceptable under speech but distracting in the gaps. An aggressive threshold can snap shut mid-breath or chatter open and closed around quiet words. If that happens, lower the threshold or reduce the gate range instead of forcing complete silence; consistent room tone often sounds more natural than visibly edited gaps. ## DaVinci Resolve EQ and De-Hummer Fixes for Hiss and Hum Power-line hum is usually built around a 50 or 60 Hz fundamental plus harmonics. Add De-Hummer to the affected clip or track, choose the matching Frequency option, and use Listen to Hum Only to hear what is being removed. Adjust Amount conservatively; Slope changes the balance between the fundamental and higher harmonics. If wanted vocal tone enters that monitor, back off. Turn noise-only monitoring off and compare Bypass before continuing. Diagnose the recording rather than assuming geography proves the frequency. ![De-Hummer Frequency Amount Slope and Listen to Hum Only controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/drc141-de-hummer.webp) Match the fundamental, then check whether Amount or Slope removes wanted vocal tone. Disable hum-only monitoring before judging the cleaned voice. Source: Blackmagic Design, Resolve 21 Reference Manual, p. 4024. For low-frequency rumble, Fairlight channel EQ can be a controlled first pass. Start the high-pass filter below the lowest useful part of the voice, then raise it while listening in context. There is no universal 80 Hz cutoff. Back down when vowels lose body. Broadband hiss overlaps speech consonants, so a low-pass filter is a blunt tool. Use gentle EQ only when the unwanted band is clearly outside the useful dialogue, and let Noise Reduction handle the remaining broadband component. For wind noise, separate low rumble from bursts that mask words. Try a conservative high-pass filter for the low component, then audition Studio Voice Isolation if changing wind still overlaps speech. A noise print captured from one gust may not represent the next. If the microphone recording is distorted or a gust obliterates a syllable, stronger filtering is not a reliable recovery plan: use an alternate microphone, take or ADR. For a future recording, reduce wind at the microphone rather than relying on cleanup. The [Fairlight dialogue EQ guide](https://davinciresolveclub.com/fairlight-eq-dialogue/) explains how to retain voice body while cutting rumble. ## Why DaVinci Resolve Background Noise Removal Sometimes Makes Voices Sound Robotic Metallic, muffled or watery dialogue usually means useful speech is being removed with the noise. Common causes are excessive Sensitivity or wet mix, an inaccurate Learn sample, and stacked cleanup processes. Use Listen to Noise Only, compare at matched loudness, and stop when consonants, breaths or vocal texture enter the removed signal. The target is controlled distraction, not digital silence. A loud transient laid directly over a word may not be recoverable from the mixed recording. If it lands between words, cut or reduce it and bridge the gap with room tone from the same setup; the [clip splitting and mute guide](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/) covers that edit. If it covers dialogue, check another microphone, alternate take or ADR before forcing more separation. Voice Isolation is worth testing, but it can't promise to reconstruct speech that wasn't captured cleanly. Before delivery, audition the full sentence in the real mix, bypass the restoration at matched loudness, and check both headphones and speakers. The [Resolve export guide](https://davinciresolveclub.com/export-video-davinci-resolve/) starts after that approval; export settings can't repair a damaged dialogue chain. ## Frequently Asked Questions ### Is DaVinci Resolve's noise reduction free? Yes. Noise Reduction, De-Hummer, channel EQ and the Expander/Gate support basic cleanup in [Resolve Free](https://davinciresolveclub.com/davinci-resolve-vs-studio/). Voice Isolation is a Studio-only Neural Engine feature, so check the current Free-versus-Studio boundary when that specific separation tool is required. ### Why did Voice Isolation disappear from my Fairlight Mixer? Open the Mixer's three-dot menu and confirm Track FX is visible. If the Track FX section is hidden, Voice Isolation and the other dedicated track effects disappear from that Mixer view. Voice Isolation also requires Resolve Studio. ### Why does noise reduction make my voice sound muffled or robotic? Useful speech may be removed by an inaccurate noise profile or excessive processing. Relearn from noise only, use Listen to Noise Only, reduce Sensitivity or Dry/Wet, and bypass stacked restoration. Switch noise-only monitoring off again and compare at matched loudness; louder is not automatically clearer. ### Can I remove background noise from a whole track instead of one clip at a time? Yes. Add Noise Reduction or De-Hummer to a Fairlight track insert when every clip on that track shares the same problem. Use clip processing when rooms, microphones or noise profiles change. The Gate lives in the channel Dynamics panel. ### Does Noise Reduction work on music or only on dialogue? Noise Reduction can process other audio, but Auto Speech Mode is designed for speech. For music or ambience, Manual mode with a representative noise-only region is the safer starting test, followed by a bypassed level-matched comparison. ### What if the background noise happens at the same time as someone talking? No tool guarantees clean separation when noise overlaps wanted speech. Voice Isolation in Studio is worth testing for changing background, but a sharp event over a word may require another microphone, alternate take or ADR. Events between words can be edited and bridged with matching room tone. For damage beyond Resolve's own processors, a dedicated repair editor can be [round-tripped from Fairlight](https://izotoperx.net/izotope-rx-davinci-resolve-fairlight/?ref=davinciresolveclub.com) with External Audio Process. ### Should I use Noise Reduction or Voice Isolation? Use Noise Reduction for steady, sampleable broadband sound such as hiss, fan or HVAC. Use Studio Voice Isolation when a changing background overlaps recorded speech. Use De-Hummer, not either of those by default, for a narrow mains fundamental and harmonics. ### Is a noise gate the same as noise reduction? No. A Gate reduces signal below its threshold, so it controls pauses but doesn't remove noise under speech. Noise Reduction targets a detected noise profile while dialogue is present. Set Gate threshold, range, attack, hold and release so quiet syllables and word endings remain intact. ### DaVinci Resolve No Audio URL: https://davinciresolveclub.com/davinci-resolve-no-audio/ Last updated: 2026-09-15T08:03:57.000Z Don't change every audio preference at once. Play a known-good clip and follow its signal through the track and bus meters, monitoring controls and output device. Check where each meter reads the signal: a pre-fader meter can move even with the fader all the way down. This guide covers sound that goes missing while you're working: in the timeline, on the Edit or Fairlight page, through your speakers or headphones. If your exported file has no audio but the timeline sounds fine, that's a separate problem with a separate fix. Check the [DaVinci Resolve export settings guide](https://davinciresolveclub.com/export-video-davinci-resolve/) for that instead. ## DaVinci Resolve No Audio: Quick Symptom Map Match the symptom below. Waveforms are a display aid, not an audibility test. If they are missing, first check Timeline View Options > Display Audio Waveforms, documented in the [Resolve timeline display controls](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=847). Then play an audible part of the source and watch the meters. - No waveform and no meter activity: check waveform display, source audio and channel mapping - Waveform visible but clip or track meter idle: check clip mute/enable, clip level, channel mapping, track mute and solo - Track meter moves but intended bus meter does not: check faders, mute/solo and output assignments - Intended bus meter moves but speakers are silent: check bus monitor selection, monitor level, mute/DIM, device and OS app volume - Source Viewer has sound but timeline doesn't: test a new track, then compare track type, mapping, mute/solo and bus assignment - Timeline sounds correct but the export is silent: use the export-audio workflow rather than changing playback monitoring Before changing Resolve, play the source in another trusted player and confirm the operating system can reach the intended output; a [browser stereo test](https://soundforgepro.com/left-right-speaker-test/?ref=davinciresolveclub.com) is enough for that check. This checks the file and device, but it does not rule out app-specific muting. On Windows 11, open Settings > System > Sound > Volume mixer. Under Apps, check Resolve's volume, mute state and Output device if it appears there. Microsoft documents these [per-app audio checks](https://support.microsoft.com/en-us/windows/hardware/audio/fix-app-audio-not-working-while-system-sounds-work-in-windows?ref=davinciresolveclub.com). ASIO interface routing also needs its own driver configuration. If the source plays outside Resolve and the operating system reaches the intended speakers or headphones, continue inside Resolve without changing the source file. These control names were checked against the current [Blackmagic Resolve reference manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com). Start at a low speaker or headphone level and raise it gradually; restoring a blocked route can suddenly make a loud mix audible. ![Real DaVinci Resolve Fairlight interface showing waveform, track meters and Control Room bus activity](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-follow-live-signal-real-ui.png) Watch the track and intended output bus during playback. Check fader position too if pre-fader meters are enabled; a moving meter is not proof that the monitored output is audible. ## Unmute Resolve Monitoring and Clear DIM The monitoring controls at the far right of the Fairlight transport include a speaker button, level slider and DIM button. In the final Resolve 21 manual, the speaker icon turns red when monitoring is muted and the slider turns yellow when DIM is active. Unmute the speaker, turn DIM off and return the monitor level to a safe audible setting. ## No Audio: Check Track and Clip Mute States Next inspect the M and S controls on every relevant audio track. A muted track is silent; a soloed track can make the others appear broken. Also check the bus strip for mute or solo and clear accidental solos before changing routing. At clip level, check Enable Clip in the timeline context menu and the Audio Inspector volume. A disabled clip is dimmed and does not play or render. Separately, check whether a required source channel is muted or mapped to an empty channel in Audio Configuration or Clip Attributes. These are different controls; avoid blindly toggling a linked video selection. Use the [guide to muting and splitting audio](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/) for intentional edits rather than troubleshooting silence. Still silent after clearing accidental mute and solo? Temporarily bypass the channel's insert chain with Effects In. The [manual explains the bypass limits](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3943): Fairlight FX, AU and VST inserts are bypassed, but Track FX and built-in Dynamics and EQ are not. A closed gate or extreme attenuation in those other stages still needs a separate check. If sound returns, re-enable the chain and bypass plug-ins one at a time. Don't delete the processing until you've found which insert blocks or radically attenuates the signal. ## Confirm Track Routing to the Monitored Bus In a simple stereo timeline, audible tracks must reach the bus you intend to monitor, directly or through a submix. Its displayed name may be Bus 1, Main 1 or a custom name. FlexBus allows different destinations, so don't assign every track to the first bus or add a duplicate direct route around an existing submix. Open the Fairlight Mixer. In Bus Outputs, use the + control to inspect the assigned bus, or choose Fairlight > Bus Assign for the matrix. If the track is meant to feed a submix, follow that submix onward. Correct a missing assignment only after checking faders and mute/solo. The [Fairlight bus-routing guide](https://davinciresolveclub.com/fairlight-bus-routing/) covers deliberate submix construction. ![Real DaVinci Resolve Fairlight Mixer showing track Bus Outputs and the monitored bus meter](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-track-to-bus-real-ui.png) Bus Outputs determine which bus receives each track. Preserve existing submix routes and check faders, mute and solo before adding a new assignment. Check track and bus faders as well as mute/solo and output assignments. Existing automation may pull a fader down during playback. With [pre-fader metering](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3967), a track meter can keep moving with its fader at minus infinity; ghost meters can also remain visible on tracks excluded by solo. Meter movement alone does not clear those controls. Save a project copy and record the existing routing before altering a complex mix. ## Check Monitor Selection Before Manual Patching If the intended output bus meter moves, inspect the bus monitoring menu below the Control Room meters. Select the bus you actually want to hear and check the adjacent speaker-set selection. The [Fairlight monitoring menus](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=4053) choose the listening source and speakers. A working mix can be silent at your headphones simply because you are monitoring a different bus. Only inspect manual patching when the setup requires it. In Fairlight > Patch Input/Output, Audio Outputs are the hardware destinations. [Monitor Out versus Bus Out](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=3816) is a real distinction: Monitor Out is after monitor level, DIM and mute, while Bus Out is a direct bus feed. Do not blindly replace the monitoring path with Bus Out; that can bypass the controls you expect to protect listening level. Lower hardware volume, save the project and record existing patches before changing a required left/right connection. Never clear all patches as a troubleshooting shortcut. ## Check Resolve Preferences for the Wrong Output Device Open Preferences > System > Video and Audio I/O. With System Audio selected under I/O Engine, check Input Device, Output Device and Automatic speaker configuration against the [current audio I/O controls](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=101). Choose connected hardware you have verified outside Resolve. If you use an ASIO interface on Windows, select its compatible driver rather than treating System Audio as the only valid engine. With Automatic speaker configuration enabled, Resolve uses the workstation's built-in system output. Disable it only when you need to define monitor sets and map channels manually. In a manual stereo set, confirm that Left and Right point to the intended device channels; a correct device name with empty channel mapping is still silent. ## No Audio After Switching Headphones or Bluetooth Devices After changing speakers, headphones, Bluetooth devices or an audio interface, first confirm the new device works at the operating-system level. Then select it as Resolve's Output Device. If Resolve still holds the previous device, save the project, quit the application completely and reopen it once. ![Real DaVinci Resolve Video and Audio I/O settings for System Audio, output device and speaker mapping](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-output-device-real-ui.png) With System Audio selected, choose the connected output device and check automatic or manual speaker mapping. An ASIO interface uses its own compatible driver configuration. A restart is a device-handoff test, not a routing fix. If reopening Resolve doesn't restore sound, return to the meters: track meter, monitored bus meter, then monitor output. That prevents repeated restarts from hiding a bus or patching mistake. On a Mac, Bluetooth sound that becomes quiet or distorted when a conferencing app opens may be a microphone-mode change rather than missing timeline audio. Apple recommends [quitting apps that use the headset microphone and reselecting the headphones](https://support.apple.com/en-us/102217?ref=davinciresolveclub.com). This explains reduced quality or volume, not every case of complete silence. ## Check Project and Audio Device Sample Rates Project Settings > Fairlight exposes Audio Sample Rate. The final Resolve 21 manual says it defaults to 48 kHz and locks after the first timeline is created. It also says imported audio at other sample rates is automatically resampled to the timeline rate, so a 44.1 kHz music file in a 48 kHz project shouldn't be silent merely because the numbers differ. Sample-rate troubleshooting belongs at the device or driver when it refuses the active format, crackles or drops out. Record its current settings first. On Windows, use the interface or ASIO control panel; on macOS, [Audio MIDI Setup lets you select Format](https://support.apple.com/guide/audio-midi-setup/set-up-audio-devices-ams59f301fda/mac?ref=davinciresolveclub.com) for the chosen device. Use a rate that the device supports for your project and restart only if the driver requires it. Do not rebuild an existing project to make a 44.1 kHz source file match a 48 kHz timeline. Set the project sample rate before creating the first timeline because it then locks. The [Resolve Fairlight project settings](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=161) document this limit. For initial setup rather than a silence fix, see the [beginner DaVinci Resolve tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/). ## No Audio: Check Channel Mapping and Codec Support For one silent clip, inspect Audio Configuration or Clip Attributes for channel mapping and muted source channels. [Identify the codec and container from metadata](https://davinciresolveclub.com/davinci-resolve-wont-import-mp4/), then compare the platform-specific combination with the [current Supported Formats and Codecs list on Blackmagic Support](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com). A container extension alone doesn't prove codec support. Linux AAC is a specific case worth checking early. Blackmagic's [published Resolve 20 codec matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com) leaves AAC decode and encode unavailable in its Rocky Linux section, and the [Blackmagic Linux AAC discussion](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=214300&ref=davinciresolveclub.com) confirms the limitation for both Free and Studio in the versions discussed. Do not assume buying Studio or changing MP4 to MOV adds AAC decoding. Check the matrix for your installed release; when AAC is unsupported, convert the audio to PCM in a new file. The [supported codecs guide](https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/) explains the container, codec and platform distinction. If the file has an audio stream that Resolve can't decode on this platform, make a new file rather than modifying the original. For audio-only replacement, use uncompressed WAV/Linear PCM with the same start and duration. If video must also be transcoded, use a documented edit-friendly codec and verify frame rate, duration and sync before replacing the clip. Do not delete caches or reset preferences just because audio is silent. First test the original media rather than a proxy, using a duplicate timeline if you need to compare results. A proxy with missing audio channels can behave differently from its original. Keep the source, project backup and current settings intact; a display-only waveform problem is not evidence of a broken audio route. ## No Audio in Timeline But Fine in Source Viewer If the Source Viewer plays the clip but the timeline doesn't, first check that an audio item was actually edited into the timeline. Video-only edits cannot play an absent audio item. Test the same source with its audio on a new, appropriate audio track in a duplicate timeline. If it plays there, compare the original clip state, track type, mute/solo, faders and bus assignment. If the new track is also silent, inspect Audio Configuration in the File Inspector or the Audio panel of Clip Attributes. Confirm that the needed embedded channel is mapped and not muted. A stereo container can hold two different microphones, including an empty channel; listen to the required source channel rather than assuming both sides contain the same sound. ## Fast Resolve No Audio Checklist - Monitoring speaker icon unmuted, DIM off and monitor level audible - Clip enabled, required source channels mapped, clip level audible - Track mute off and no unrelated solo isolating the mix - Tracks reach the intended bus directly or through the correct submix; faders and automation checked - Monitored bus meter moving and bus not muted or soloed - Monitor source and speaker set correct; manual patches checked only when required - I/O Engine and Output Device point to connected hardware - Automatic speaker configuration or manual Left/Right mapping matches the setup - A silent single source is tested against Blackmagic's platform codec support - Original media compared with proxies without deleting caches or preferences ## No Audio FAQ ### Why does DaVinci Resolve show audio meters moving but I hear nothing? Moving track meters show signal at that meter's position, not necessarily at the speakers. With pre-fader metering, check the fader and mute/solo too. If the intended bus meter stays still, check track outputs and bus state. If it moves, check bus monitor selection, monitor level and mute/DIM, speaker mapping, output device and OS app volume. ### Does restarting DaVinci Resolve actually fix audio device issues? It can after an output-device handoff. Save the project, choose the correct Output Device in Video and Audio I/O, and reopen Resolve once if the previous device remains active. A restart doesn't repair track routing, bus assignment or a muted monitor. ### Can a sample rate mismatch really cause silence with no error message? Not by itself. Resolve 21 automatically resamples imported audio to the timeline rate. A device or driver that cannot operate at the active rate can still crackle or go silent, so check its control panel or Audio MIDI Setup rather than changing Clip Attributes or blaming every 44.1 kHz file. ### Why is only one clip on my timeline silent when everything else plays? Check the clip's Audio Configuration or Clip Attributes for channel mapping and muted source channels. Then identify the actual audio codec and container from metadata and compare them with the current platform codec list. Don't treat Clip Attributes as a codec detector. ### Should I check bus routing before or after checking my output device in Preferences? After a quick OS device test, trace the signal through the track and intended output bus. Check faders, mute/solo and bus assignments if the bus stays still. If it moves, check which bus and speaker set you are monitoring, then the output device and any required patching. Do not add a direct Bus Out patch as a universal fix. ### Why do I see waveforms but hear no audio in DaVinci Resolve? Waveforms show that Resolve generated waveform data; they do not prove the current playback path is audible. Check clip state and channel mapping, track faders and mute/solo, bus assignments, monitor selection, speaker mapping and Output Device. Pre-fader meter activity can remain visible even when the track is inaudible. ### Why did DaVinci Resolve lose audio after I changed headphones? Confirm the new headphones or speakers work in the operating system, select them under Preferences > System > Video and Audio I/O > Output Device, and reopen Resolve once if it still holds the previous device. Use manual speaker mapping only when Automatic speaker configuration doesn't fit the setup. For other media, GPU, render and crash symptoms, start with the [Fix DaVinci Resolve troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/). If the meters reveal a bus-routing problem, or you need EQ, dynamics and delivery work after sound returns, continue in the [Fairlight Audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/). ### DaVinci Resolve Delta Keyer: Complete Settings Guide URL: https://davinciresolveclub.com/davinci-resolve-delta-keyer/ Last updated: 2026-09-14T14:15:21.000Z To remove a green screen, connect the clip to Delta Keyer, sample the screen with Background Color, then feed the keyed result into a Merge foreground. Connect your replacement background to the Merge background and send Merge to MediaOut. Refine the alpha before adjusting spill or edge color. This guide is part of the [Fusion learning hub](https://davinciresolveclub.com/davinci-resolve-fusion/). Control names were checked against the September 2026 [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=2516). Blackmagic also demonstrates the basic setup in its [Fusion green-screen overview](https://www.blackmagicdesign.com/products/davinciresolve/fusion?ref=davinciresolveclub.com). Start with the node connections below, then use the tab-by-tab controls to fix uneven backing, holes in the subject and contaminated edges. Judge the result over the replacement background and through the full shot, not on one convenient frame. If nodes are unfamiliar, the [Fusion beginner tutorial](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) explains MediaIn, Merge and viewers. This page focuses on the key itself. ## Set Up Delta Keyer and the Replacement Background Select the green-screen clip on the Edit timeline and open Fusion. Select its MediaIn node, press Shift+Space, search for Delta Keyer and add it. Check that MediaIn feeds the orange Input on Delta Keyer; do not assume automatic insertion made the connection you intended. For a complete composite in Fusion, drag the replacement background from the Media Pool into the node area. Add Merge. Connect Delta Keyer to the green Foreground input and the background MediaIn to the orange Background input. Connect the Merge output to MediaOut. View Merge to judge the composite, and view Delta Keyer separately to inspect its alpha. Alternatively, send the keyed Delta Keyer output directly to MediaOut and place the replacement background below that clip on the Edit timeline. You do not need both an opaque background inside Fusion and a second background below it. A black viewer alone does not prove the key failed: inspect the alpha and confirm where the replacement background enters. Keep the source encoding consistent before keying. In a color-managed project, do not add a log-to-linear transform merely because an unmanaged tutorial uses one. Follow the [RCM and CST workflow](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/) to avoid applying the same conversion twice. ## DaVinci Resolve Delta Keyer Workflow: The Fast Order Use this diagnostic order rather than treating every control as a required step. An even screen may need only a sample and small matte adjustments. Add masks before making the final alpha judgment, and revisit earlier stages if an edge disappears. - **Key tab:** sample the screen color and adjust Gain and Balance only enough to get a workable first alpha. - **Pre-Matte or Clean Plate:** even out screen color before pushing the main key any harder. - **Matte tab:** refine the alpha with Threshold, Restore Fringe, Clean Foreground and Clean Background. - Mask tab: set how connected solid and garbage mattes combine with the key, then inspect the final alpha. - **Fringe tab:** remove green or blue spill once the matte is solid enough to protect edge detail. - **Tuning tab:** adjust shadows, midtones and highlights separately, only when one tonal range keeps breaking. ## Delta Keyer Key Tab: Gain, Balance and Background Color Select Delta Keyer and drag the Background Color eyedropper onto a representative clean patch of green or blue in the viewer. Avoid sampling skin, reflections or motion-blurred edges. The keyer compares the dominant screen channel with the other two channels to produce an initial alpha. Two sliders do the real work once that first pick is in. **Gain** increases how much influence the sampled screen color has, pushing more of the background toward full transparency. Push it too far and edges around hair or motion blur start disappearing along with the green. Balance controls the mix between the other two color channels the keyer compares against: 0 uses their minimum, 1 uses their maximum, and 0.5 uses half of each. Compare small changes in the alpha and composite; a setting that clears the backing can also change foreground transparency. Pre-Blur applies a blur before generating the alpha. It can help certain noise, edge-enhancement and source artifacts, but too much can cost fine detail. Uneven screen color is a separate reason to try Pre Matte or Clean Plate; not every edge defect comes from that stage. ## Delta Keyer Pre-Matte Tab and the Clean Plate Node Pre-Matte exists because a single background color pick rarely matches every patch of a real screen. Shadows, wrinkles, and uneven lighting read as different shades. Switch View Mode to Pre Matte, box-select screen areas that differ from the first pick, expand the selection with Soft Range, and use Erode to keep the range from clipping subject edges. Lock Color Picking after the range is established so an accidental drag doesn't expand it. A Clean Plate node solves the same problem from a separate branch. Feed the green- or blue-screen source into both Clean Plate and Delta Keyer, then connect Clean Plate output to the Delta Keyer's magenta Clean Plate input. In Clean Plate, Method offers Color for an even screen or Ranges for a shadowed/mixed screen; Matte Threshold, Erode, Grow Edges and the Fill checkbox build the plate. Sequence generates it per frame, while Hold Frame uses one frame. A separately recorded empty screen is useful only when camera, focus, screen and lighting still match the performance shot. When generating a plate, select the screen, not the person. Use Erode to remove non-screen pixels at the selection boundary, then Grow Edges and Fill to extend screen color into the subject-shaped gap. View the plate itself: remaining foreground-colored contamination can undermine the key. Hold Frame is appropriate only if that single plate remains valid through the shot. A matching clean plate helps normalize uneven screen color, wrinkles, gradients, reflections, and screen variation behind fine hair, smoke, or motion blur so the keyer can preserve delicate transparency without choking the matte. It does not remove green light already cast onto skin, restore foreground detail already clipped by Threshold, or compensate for a plate whose camera or lighting no longer matches the shot. Use a clean plate only when it improves the alpha across the full shot. A good direct key on an even screen doesn't need one; a mismatched or overgrown plate can introduce new edge and transparency errors. ![Clean Plate branch feeding the magenta Delta Keyer input while the original image feeds both nodes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/delta-keyer-139-official-2512-0.webp) Generate the screen plate on a separate branch; it is not the replacement background. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 2512. ## Delta Keyer Matte Tab: Threshold, Erode and Restore Fringe In the Matte tab, inspect the alpha channel of the Final Result output before touching Threshold. View Mode Matte is a diagnostic view of the key before solid and garbage masks are combined; it is not the finished masked alpha. The lower Threshold handle turns values below it black and transparent; the upper handle turns values above it white and opaque. Values between them retain relative transparency. Move only as far as the shot needs: aggressive thresholds can remove hair or make soft detail unnaturally solid. Restore Fringe can bring back legitimate soft edge detail lost during thresholding while keeping the matte core solid. Erode/Dilate expands or contracts the matte, and Blur softens it. Clean Foreground fills slightly transparent light-gray areas that should be opaque. Clean Background clips the lower dark range that should be transparent. Apply small changes while watching both the alpha and Final Result; none of these controls knows which gray pixels are hair and which are noise. Replace Mode controls how matte adjustments restore color: None makes no color replacement, Source uses the original image, Hard Color uses a solid replacement, and Soft Color weights that color by how much background was removed. Choose by inspecting the final composite; a mode that fills the alpha but adds noisy or artificial edge color isn't a clean result. ![Delta Keyer Matte tab showing Threshold, Restore Fringe and cleanup controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/delta-keyer-139-official-2520-0.webp) Inspect the alpha of Final Result while adjusting this tab so connected auxiliary mattes remain part of the check. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 2520. ## Delta Keyer Mask Tab: Solid and Garbage Mattes Delta Keyer has five inputs. The orange Input receives your green- or blue-screen image. The gray Garbage Matte input makes masked areas transparent; the white Solid Matte input makes them opaque. The magenta Clean Plate input receives the generated screen plate. Hover over a connector to read its name rather than relying on its position. Connect a Polygon or B-Spline to Garbage Matte to remove a light stand, microphone or area outside the backing. If you draw around the subject instead of the unwanted area, use Garbage Mask Invert so the outside is removed. Connect a separate shape to Solid Matte to fill an opaque core, keeping it inside the subject and away from hair or motion blur. The Mask tab determines how the connected solid and garbage mattes combine with the key. Solid Source Alpha can ignore, add, or subtract the source alpha; Solid Replace Mode and Color control how forced-opaque areas restore color; Garbage Mask Invert swaps which side is removed. It doesn't control the Clean Plate node’s Grow Edges or Fill operations. The blue Effect Mask input limits where the keying operation runs. It is not a substitute for Garbage Matte: outside an effect mask, unkeyed source can remain visible. Scrub the full shot and animate auxiliary masks when the subject moves beyond them. Use the [Fusion rotoscoping workflow](https://davinciresolveclub.com/rotoscoping-davinci-resolve-fusion/) for moving auxiliary shapes. [Magic Mask subject isolation](https://davinciresolveclub.com/davinci-resolve-magic-mask/) is a different tool family, useful when color separation alone cannot isolate a region. Neither replaces checking fine transparency at the key edge. ## Delta Keyer Fringe Tab: Spill Suppression Settings Spill is screen color visible through semi-transparent edge pixels or reflected onto the subject. The Fringe tab handles most Delta Keyer spill suppression. Spill Method chooses algorithm strength: Rare is lightest, Medium is documented for green screens, Well Done for blue screens, and Burnt for troublesome blue-screen material. Spill Suppression controls the amount. Raise it only until the unwanted screen color recedes; excessive suppression can bleach legitimate foreground color. Fringe Gamma adjusts the brightness of the fringe or halo. Fringe Size expands or contracts that region, while Fringe Shape pushes it toward the outer or inner edge. The Cyan/Red, Magenta/Green and Yellow/Blue controls color-correct remaining semi-transparent edge pixels toward the new background. These are different jobs, so change one while comparing the alpha and final composite. Don't mix Delta Keyer labels with the Color page's 3D Keyer terminology. Matte Finesse is used in the Color-page workflow; Delta Keyer exposes Matte and Fringe controls with different names. The [Color grading guide](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/) covers qualifiers and windows when the task is a selection rather than a Fusion key. ## Separate Despill When the Alpha Is Already Good If spill correction damages otherwise correct color, Blackmagic documents a separate route: in Delta Keyer, open Matte and set Replace Mode to Source, then handle spill with a downstream color correction or a separate source branch combined through MatteControl. See [Dealing with Spill in the current manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=1720). This is an alternative workflow, not an instruction to stack every despill method. ![Delta Keyer Matte tab Replace Mode menu with Source selected](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/delta-keyer-139-official-1720-1.webp) Use Source when following the separate-despill workflow, then correct unwanted color on a deliberate downstream branch. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 1720. ## Delta Keyer Tuning Tab: Shadows, Midtones and Highlights Tuning divides the image into shadow, midtone and highlight ranges and lets matte strength and spill suppression vary by tonal value. Use it only after Key, Pre Matte/Clean Plate, Matte and Fringe are behaving. Dark hair, bright edges or noisy midtones can still be caused by a bad sample, clipped Threshold or an uneven screen; they aren't automatically Tuning problems. Lock Alpha/Spill Removal Tuning applies the same tonal ranges to alpha generation and spill removal while it's enabled. Disable it when the two jobs need different ranges, for example stronger alpha work in the shadows without equally strong color subtraction there. Simple sets linear ranges; Smooth creates a smoother tonal gradient. Start with those shapes before hand-adjusting every range control. Leave this tab alone on a well lit shot. It earns its place only when a specific tonal range keeps breaking after Matte and Fringe are already dialed in. ## Edge Integration After the Key Delta Keyer finishes the alpha and spill work; it does not automatically match the subject to a new background. After the key is stable, compare black level, white balance, contrast, sharpness, grain, and edge light with the destination plate. Make those adjustments on clearly labeled downstream branches so the matte remains inspectable. Check premultiplication when a color correction creates dark or bright fringes. A premultiplied image already has RGB weighted by alpha. For color tools that require straight RGB, use their Pre-Divide/Post-Multiply option, or put Alpha Divide before the correction and Alpha Multiply after it. Do not add another multiply to an already premultiplied result as a generic edge fix. Delta Keyer Final Result is the ready-to-merge output; intermediate views are for diagnosis or deliberate downstream processing. A subtle background-colored edge treatment can help when the destination actually casts that light, but it must follow the new scene’s direction, color, and softness. If the treatment creates a glowing outline or hides a broken alpha, remove it and repair the Matte or Fringe stage instead. This guide doesn't prescribe one universal light-wrap node recipe because the correct build depends on the shot and composite. ## Green Screen Lighting Mistakes That Break the Key A difficult screen can consume far more cleanup than a well-prepared one. Uneven illumination, wrinkles, reflective contamination, and subject shadows all create screen colors that one sample may not cover. Reduce those differences on set, keep the backing out of focus where the shot allows, and record a matching clean reference when the setup is static enough to make it useful. Subject-to-screen distance matters because closer placement usually increases green or blue bounce onto skin, hair, and clothing. Move the subject far enough from the backing for the actual lens, screen size, room, and lighting setup; there's no universal distance that guarantees a clean result. Light the screen and subject as separate jobs, and avoid subject shadows on the backing whenever possible. A matching clean plate can help with shadows and uneven color on the backing. It cannot relight the subject or remove reflected green light by itself. Separate screen variation from foreground spill before choosing the next correction. ## Delta Keyer Performance on Heavier Composites A larger keying tree can reduce interactive playback, especially with multiple keyers, a Clean Plate branch, edge work, and high-resolution footage. Use a lower viewer proxy only while adjusting, then inspect the full-resolution alpha and final composite before approval. The [Resolve system-requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) covers the wider decode, memory, and GPU context; smooth proxy playback isn't proof that fine hair, motion blur, or noise survived the key. Once the matte, spill correction, and edge integration are locked, the composite returns to the Edit page like any other shot. The [DaVinci Resolve export workflow](https://davinciresolveclub.com/export-video-davinci-resolve/) covers the delivery stage; recheck the full-resolution composite before rendering. ## Troubleshoot the Symptom Before Changing Settings Black background: inspect Delta Keyer alpha, then the Merge inputs or the lower Edit track. If alpha is transparent where expected, supply the replacement background rather than increasing Gain. If the Edit page shows no change, confirm the finished output reaches MediaOut. Missing hair or motion blur: back off Threshold and aggressive cleanup, compare Restore Fringe, and check that a solid or garbage mask does not cut through the soft edge. Do not force every gray alpha pixel to black or white. Holes in clothing: use conservative Clean Foreground or an interior Solid Matte. If one setting cannot retain both the core and hair, use a separate hard core key feeding the soft key’s Solid Matte input, as shown in the manual. Keep the core away from the soft perimeter. Green fringe or dark outlines with a sound alpha: compare spill correction, replacement color and premultiplication. Eroding the matte may hide an outline by removing the subject edge; fix color contamination instead when the alpha already follows the subject. Flickering edges: play the entire shot at full resolution. Check changing screen illumination, source noise, a held plate that no longer matches and masks that fail to follow movement. A clean still frame is not sufficient evidence of a stable key. ## Delta Keyer FAQ ### What's the difference between the Delta Keyer and the Chroma Keyer in Fusion? Delta Keyer is an advanced color-difference keyer optimized for blue and green screens, with Pre Matte, Clean Plate, Matte, Fringe and Tuning controls. Chroma Keyer can target another chosen color with a simpler control set. Use the tool whose controls match the shot rather than assuming one keyer wins every source. ### Do I need a clean plate for every green screen shot? No. A Background Color sample can handle an even screen. Use a matching Clean Plate when screen variation would otherwise force aggressive matte cleanup and the plate preserves useful soft detail. It cannot restore detail already clipped by Threshold or remove screen-colored light reflected onto the subject. ### Why does my key still show green on hair after adjusting the Fringe tab? Inspect the alpha first. If Threshold removed the hair detail, use less aggressive thresholding and Restore Fringe before increasing spill suppression. Once the matte contains the legitimate semi-transparent edge, use Fringe controls to correct remaining screen color. ### Can the Delta Keyer key a blue screen the same way it keys green? Yes. Sample the blue screen and use the same Key, Pre Matte or Clean Plate, Matte, Mask, Fringe and Tuning workflow. The settings remain shot-specific. Blackmagic spells out Well Done for blue screens and Burnt only for troublesome blue-screen material. ### Why does my Delta Keyer key show black splotches or noisy edges? Compare the alpha with the color result. If the alpha has holes or chatter, inspect source noise, Pre Matte and Threshold first. If the alpha is sound but black or discolored pixels appear in the composite, compare the spill settings or use a separate despill branch. Pre-Blur and stronger cleanup are not universal fixes. ### Is the Delta Keyer available in the free version of DaVinci Resolve? Yes. The core Delta Keyer and Clean Plate workflow is available in Resolve Free. The current [Resolve manual documents these nodes](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com#page=2511) without the Studio-only label used for restricted nodes in the same chapter. Other tools in your composite may still require Studio; check the [Resolve Free versus Studio guide](https://davinciresolveclub.com/davinci-resolve-vs-studio/) for those separate limits. ### DaVinci Resolve Fusion Tutorial for Beginners URL: https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/ Last updated: 2026-09-12T19:19:13.000Z Fusion becomes predictable once you read every comp as a flow from sources, through tools and Merge nodes, into MediaOut. This beginner path sits inside the [Fusion learning hub](https://davinciresolveclub.com/davinci-resolve-fusion/): first learn the workspace and node logic here, then move into the specialist tracking, keying and motion-graphics guides when a shot needs them. Start with one rule: a Merge node's orange input is the background, green is the foreground, and blue is an optional effect mask. Use a short clip with a textured wall for the tracking exercise and a separate green-screen shot for the keying exercise. Save the project before experimenting. These are desktop Fusion-page workflows; you do not need the separate Fusion Studio application to build them. ## DaVinci Resolve Fusion Basics: Nodes Instead of Layers A timeline-based Fusion comp normally opens with MediaIn, which brings the timeline clip into the graph, and MediaOut, which returns a chosen result branch to the Edit page. Keep that return path visible while learning. A generator-only title can be built without MediaIn, but the branch you want on the timeline must still reach MediaOut. Follow the wires from each source toward MediaOut. The example below merges a graphic over the clip and then passes the combined image through a blur. For a basic title, the Merge output can go straight to MediaOut. Canvas position does not determine which operation happens first. ![Fusion Merge ports: background, foreground, optional mask and output leading to MediaOut](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/fusion-merge-annotated-v2.webp) Annotated adaptation of [Blackmagic Design's published node example](https://www.blackmagicdesign.com/products/davinciresolve/fusion?ref=davinciresolveclub.com). The white square sends the Merge result onward; the blue triangle is an optional mask input, not an output. The example includes a downstream blur; a basic title can connect Merge directly to MediaOut. The switch that trips people up coming from After Effects or Premiere is that screen position in the Node Editor does not create a layer stack. Connections define the image flow. A Merge combines two images: orange is background, green is foreground and blue is an optional effect mask. Connect a shape to blue and it limits the Merge result. The [full guide to Fusion and Color nodes](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) explains the two node systems without pretending they're interchangeable. Swapping the background and foreground changes their compositing order and can hide the element you meant to keep on top. ## Fusion Nodes: Quick Map These eight nodes cover the three exercises below. Skim their jobs first, then return to the list when a connection stops making sense. - **MediaIn:** brings the timeline clip or imported media into the comp. - **MediaOut:** sends the selected result branch back to the Edit page timeline. The branch you want rendered must reach it. - **Merge:** combines a foreground and background image. This is the node to understand first. - **Text+:** creates editable text and title graphics. - **Planar Tracker:** tracks a flat surface and can drive a corner pin or match move composite. - **Delta Keyer:** removes a green or blue screen background. - **Background:** generates a solid color or gradient. Fills the entire frame unless you mask it. - **Rectangle mask:** draws a rectangular shape you can connect to another node's mask input to limit its area. ## Fusion Comp 1: A Tracked Title That Sticks to a Surface Use a planar track when the title needs to follow a wall, sign, laptop lid or another flat surface with perspective change. The tracker analyzes the surface; a Planar Transform transfers that motion to the title. Keeping the original clip on the Merge background branch makes the composite easier to read and repair. 1. Select the clip on the Edit page and open the Fusion page. Confirm that MediaIn is connected to MediaOut before changing the graph. 2. Add a Planar Tracker connected to MediaIn and load that tracker into a viewer: select it and press 1 or 2\. In the Inspector, keep Operation Mode set to Track. Move to a sharp, unobstructed frame where the surface is clearly visible, click Set to establish the reference frame, then draw a region around textured detail on that same plane. 3. Track from the reference frame to the start, return to the reference frame, and track to the end. Switch to Steady to inspect whether the plane slips, then return to Track. 4. Click Create Planar Transform. This creates a separate Planar Transform node carrying the solved motion. 5. Add Text+ and enter a short label in its text field, then connect Text+ into the Planar Transform. 6. Add a Merge. Connect MediaIn directly to the orange background input, the Planar Transform output to the green foreground input, and the Merge output to MediaOut. Load the Merge into a viewer with 1 or 2, return to the reference frame, then select Text+ to place and style the label over the tracked surface while watching the composite. ![DaVinci Resolve Fusion tracked-title node flow with Text Plus through Planar Transform into a Merge over MediaIn](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/tracked-title.webp) Track the surface first, create a Planar Transform from that track, then apply the transform to Text+ before merging it over the untouched clip. Scrub the complete shot. The middle alone cannot reveal every tracking failure. If the title drifts, repair the track or choose a better reference region before adjusting the text. Create a new Planar Transform from the repaired track and reconnect the title through it: the earlier exported transform contains the old motion, not a live link to later tracking changes. A tracker cannot recover image detail that is fully blurred, occluded or outside the frame. For a rectangular screen or sign replacement, the Planar Tracker's built-in Corner Pin route can be faster than creating a separate transform. That is a different output choice, not a second step after Match Move. The [Fusion tracking guide](https://davinciresolveclub.com/fusion-tracking-davinci-resolve/) covers point, planar and camera tracking, reference frames and drift repair. ## Fusion Comp 2: A Basic Green Screen Key A useful beginner key has two separate jobs: create a clean alpha channel, then control green or blue spill on the foreground. Delta Keyer provides dedicated Key, Pre-Matte, Matte and Fringe controls for those jobs. Don't push one global control until hair and motion blur disappear. 1. Connect the green-screen MediaIn output to Delta Keyer. Select Delta Keyer and press 1 or 2 to load it into a viewer. Open the Key tab and sample a clean part of the screen with the eyedropper. 2. In Delta Keyer, switch View Mode to Matte and set the viewer to display the alpha channel. This view shows the key before garbage and solid masks are combined. The subject should remain opaque, the screen transparent, and fine edges should retain useful softness. 3. Use the Pre-Matte and Matte controls to repair holes in the subject or leftover screen pixels. Make small changes and recheck hair, fabric, motion blur and shadows. 4. Return View Mode to Final Result and set the viewer back to RGB. Open the Fringe tab for spill suppression. Compare the color result against the original so skin, hair and wardrobe do not become unnaturally neutral. 5. Drag the replacement plate from the Media Pool into the node graph to create another MediaIn, then add a Merge. Connect that plate to the Merge's orange background input, the Delta Keyer output to the green foreground input, and the Merge output to MediaOut. ![DaVinci Resolve Fusion green-screen workflow using Delta Keyer, Fringe controls, and a Merge over a replacement background](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/green-screen-key.webp) Refine transparency inside Delta Keyer and use its Fringe tab for spill. Garbage and solid mattes can connect directly to Delta Keyer; MatteControl is optional for a separate downstream operation. Delta Keyer already has dedicated Garbage Matte and Solid Matte inputs. Connect a mask to the appropriate input when you need to exclude unwanted areas or hold the subject opaque. MatteControl is optional for a separate downstream matte-combining operation; it is not required just to feed those masks into Delta Keyer, and it is not the default fix for green fringe. Spill controls live in Delta Keyer's Fringe tab. Uneven screens, translucent edges, reflections and smoke can need separate mattes, edge work or more than one keying pass. The [complete Delta Keyer guide](https://davinciresolveclub.com/davinci-resolve-delta-keyer/) covers clean plates, matte diagnosis, edge repair and the point where reshooting is safer than stronger keying. ## Fusion Comp 3: An Animated Lower Third From Scratch This is the comp with the most moving pieces, and it's the one that teaches keyframing inside Fusion's spline editor, which behaves differently from the Edit page's keyframe row. 1. Add a Background node (Shift+Spacebar, search "Background") and set its color in the Inspector. 2. Add a Rectangle mask node and connect it to the Background node's blue mask input. Without this step the Background node fills the entire frame instead of forming a strip. Adjust the Rectangle mask's Width, Height, and Center in the Inspector until the bar sits where you want it, usually along the lower third of frame. 3. Add one Text+ node for the name. For this first exercise, use a line break in the same Text+ if you also need a subtitle. Separate Text+ nodes are useful later when the two lines need different animation, but each must be connected into the graphic branch. 4. Merge Text+ over the masked Background: text into green, bar into orange. Load this Merge into a viewer, then select Text+ and adjust its size and placement until the name sits on the bar. Keep the text inside the masked graphic area you want to animate. 5. Add a second Merge: connect MediaIn to its orange background input and the complete bar-and-text branch to its green foreground input. Connect this Merge's white output to MediaOut so the lower third reaches the timeline over your footage. 6. Select the final Merge that places the complete lower-third branch over MediaIn. Move to the frame where the entrance should finish. Leave Center at the position that displays the finished graphic, right-click Center and choose Animate. Confirm that a keyframe exists there before continuing. 7. Move to the earlier frame where the entrance should start. Adjust that same Merge Center until the entire bar and text are outside the image. With Center animated, this records the starting position. Play from the earlier frame to the later frame and check that both elements enter together. 8. Open the Spline Editor and select the Center animation. Adjust its interpolation to ease the entrance, then replay it. Check that the curve does not overshoot the final position unless that bounce is intentional. ![DaVinci Resolve Fusion lower-third node flow with masked Background, Text Plus, Merge animation, and macro controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/lower-third.webp) Build the bar and text as one branch, merge that branch over the clip, then animate the final Merge so every lower-third element travels together. Save the composition with the project for one-off reuse. This exercise animates the final Merge, which also receives the shot; exporting just the upstream text and bar would omit that movement. For a reusable Edit-page title, the [Fusion macros and templates guide](https://davinciresolveclub.com/davinci-resolve-fusion-macros-templates/) explains how to separate the animated graphic from its footage input and save it in the Titles category. Do not package this specific MediaIn clip into a generic title. Test the saved template on a different clip and duration. ## Why Nothing Shows Up in Fusion Check these five points before rebuilding the composition. - **MediaOut is disconnected.** Connect the final branch you want returned to the timeline to MediaOut. If the wrong branch is connected, the Edit page receives the wrong result or no intended result. - Merge inputs are swapped. Background goes into orange and foreground into green. If the wrong image is on top, swap the connections and inspect the result, including any transparency. - **A Background node is covering the whole frame.** If you wanted a lower-third strip and got a full-screen color instead, you skipped the Rectangle mask step. - Text is connected but invisible. Load Text+ into a viewer and check that it contains text, has visible alpha and sits inside the frame. Then check the Merge foreground connection and Blend. Viewing Text+ alone previews that node; it does not choose what MediaOut returns to the timeline. - **The tracker drifts partway through the clip.** Retrack using a sharper, higher-contrast area of the frame, and avoid regions with motion blur. ## Fusion vs the Edit Page: When to Actually Use It Skip Fusion for a title that just needs to sit centered on screen for 4 seconds. The Edit page's Text+ tool handles that with fewer clicks and no node graph. Fusion earns its place when text needs to track a surface, when you're keying footage, or when an animation needs more control than the Inspector's basic keyframe row gives you. If you're unsure which text tool fits your shot, the site's [guide to Text, Text+ and titles](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/) breaks down exactly where the Edit page stops being enough. ## Saving Fusion Templates in Resolve 21.1 In the current Macro Editor, the Save to dropdown sits to the left of Macro Name. Choose a plain .setting file or the appropriate template category; an older tutorial may show Save to Edit Template instead. The [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) documents the current layout and exported controls. Fairlight Animator can drive an animatable numeric control from audio analysis when you need an audio-reactive graphic. Neither feature changes the source, Merge and MediaOut connections used in these exercises. ## Fusion Performance: Why Comps Crawl on Some Machines Fusion evaluates the graph frame by frame, so 4K media, keys, blurs and tracking can make interactive playback slow. Use the viewer's half- or quarter-resolution proxy while building, then return to full resolution for edge and quality checks. For Edit-page playback, use the clip's Render Cache Fusion Output > On command with the appropriate cache mode. Inside Fusion, Cache to Disk is the node-level alternative. The [slow playback troubleshooting guide](https://davinciresolveclub.com/davinci-resolve-slow-playback/) separates Fusion caching from proxy, optimized-media and general timeline problems. ## Fusion FAQ ### Is Fusion included in the free version of DaVinci Resolve? Yes. Resolve Free includes the Fusion page and the tools used here: Merge, Text+, masks, Delta Keyer and Planar Tracker. The separate 3D Camera Tracker requires Studio, as listed in Blackmagic's [published Studio feature table](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5FStudio%5F20%5FFeatures.pdf?ref=davinciresolveclub.com). IntelliTrack also requires Studio. Use the Planar Tracker workflow in this guide for a flat surface; do not substitute the Camera Tracker and expect it to run in Free. ### Do I need to learn Nuke or After Effects first? No. Fusion's node logic is closer to Nuke's than to After Effects' layer stack, but nothing here assumes prior compositing software. The Merge node's color-coded inputs, orange background, green foreground and blue mask, are the one thing worth memorizing first. ### What does the Merge node do in DaVinci Resolve Fusion? The Merge node combines a foreground image with a background image. The orange input is background, the green input is foreground, and the blue input is an optional effect mask. ### Why does my tracker fail on a shot with motion blur? Planar and point trackers need stable image detail. Heavy motion blur, occlusion or a low-contrast surface can remove that detail. Choose a sharper region, use a better reference frame and inspect the complete track; difficult frames may need repair or manual help. ### Can I reuse a Fusion comp on other clips? Yes. Keep the comp in the project for one-off reuse, or create a Macro and save it in the appropriate Fusion Templates category when it should appear on the Edit or Cut page. Expose only the controls that need to change, then test it on a different clip and duration. ### Why isn't my Fusion comp showing on the Edit page? Check that the final branch you want rendered is connected to MediaOut. Selecting a node in a Fusion viewer only changes that preview; it does not choose the timeline output. MediaOut returns the connected Fusion result to the Edit page. ### Is Fusion better than the Edit page for titles? Use Fusion when a title needs tracking, complex animation, masking or reuse as a template. For a static title with a simple fade, the Edit page is faster and easier to maintain. ### DaVinci Resolve Render Failed URL: https://davinciresolveclub.com/davinci-resolve-render-failed/ Last updated: 2026-09-12T10:46:45.000Z A failed job in the Deliver page Render Queue is a symptom, not a diagnosis. This page covers failed jobs and exports that stall while Resolve stays open. If the application closes or its whole interface becomes unresponsive, use the dedicated [DaVinci Resolve keeps crashing guide](https://davinciresolveclub.com/davinci-resolve-keeps-crashing/) as well. Copy the exact message, timecode and percentage before changing settings. Then test the smallest range that still fails. That sequence separates a bad clip or Fusion frame from a decoder, GPU, cache, storage or device problem without hiding damaged output. ## DaVinci Resolve Render Failed: Quick Reference Table Match the wording in the first column, then run the safe test in the last column. The rows narrow the search; they don't claim that one message always has one cause. | Error message or symptom | What it narrows | First safe test | | ------------------------------------------------------------ | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | Render Job failed as the current clip could not be processed | Clip, Fusion/Text+, OFX, source frame, or cache | Note the timecode and render a short range around it | | Error decoding full resolution media for \[file\] | File access, source integrity, codec support, or decode path | Verify the file and codec support; compare hardware decode only where available | | Your GPU memory is full | VRAM pressure from resolution, nodes, NR, OFX, Fusion, or large stills | Bypass the heaviest process on the failing clip | | Unable to Initialize GPU | GPU selection, processing mode, driver, or unsupported device | Check Memory and GPU preferences before changing the project | | No error and the render barely moves | Very slow processing or stalled source/cache/destination I/O | Test a short range, check storage, and compare processing activity | | Media Offline appears on specific frames | Missing media, storage interruption, damaged frames, or variable-frame-rate source | Verify the source; test a CFR transcode only for confirmed VFR | | Render fails near the end or while writing cache | Late problem clip, destination space, cache space, or write failure | Check both drives and range-test the late section | ## Render Job Failed: Keep the Error Check On If Resolve reports that the current frame or clip cannot be processed, write down the timecode and test that range with error checking still enabled. Preferences > User > UI Settings includes Stop renders when a frame or clip cannot be processed. The [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) describes it as stopping the render when an encoding error is detected. Turning it off may let a diagnostic job continue, but it does not repair the failed frame and is not the first fix to try. ![Real DaVinci Resolve 21 Render Queue with four steps for diagnosing a failed render](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-failure-diagnostic-real-ui-v2-1.png) After a failure, copy the exact message, note the timecode or percentage, test a short range, then change one variable. A repeatable location points first to timeline content; a moving failure shifts the check to disk, cache, GPU and system state. ![DaVinci Resolve render failure diagnosis for repeatable timecodes and random stalls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/repeatable-vs-random-failure-v1.webp) A failure at the same timecode points toward timeline content; a moving failure points toward disk, cache, GPU or system conditions. Re-enable the stop-on-error option after the test. If the diagnostic file finishes, inspect the named timecode frame by frame for black frames, missing titles, frozen images, audio gaps and corrupt pixels. Never deliver a file just because disabling the warning let the progress bar reach 100 percent. ## Fusion Composition Could Not Be Processed For a named Fusion composition, choose Playback > Render Cache > Smart. For manual control instead, choose User, then right-click the failing clip and select Render Cache Fusion Output > On. Marking a clip On does not build its cache while the overall cache mode is Off. In User mode, Automatically cache Fusion effects in user mode is enabled by default under Project Settings > Master Settings, but confirm your actual project setting. Wait for the affected cache indicator to turn blue before testing the range. A blue cache bar alone does not tell the Deliver page to use it. To test the cached output, enable Use render cached images in the video render settings where available. Use a cache format suitable for the intended delivery, and inspect the result. If the composition cannot generate valid cached frames in the first place, this route cannot repair it; isolate the failing node or source instead. If caching still fails, duplicate the timeline before troubleshooting the comp. Bypass the last expensive node or OFX effect, render the same short range, and work backward until the range passes. Check that MediaOut is connected and that all source paths used by Loader or MediaIn nodes are available. Rebuild only the node or template that the test isolates. ## Error Decoding Full Resolution Media When the message names a file, verify that it still exists at that path, is readable, and plays through the reported timecode. If Resolve has lost the source path, follow the [Media Offline relinking checks](https://davinciresolveclub.com/media-offline-davinci-resolve/). Copy network or removable media to a local drive for a test. For an H.264 or HEVC source, look under Preferences > System > Decode Options for Decode H.264/HEVC using hardware acceleration. If that control is available, turn it off for one comparison, save, restart when prompted, and retry the same range. Availability depends on your platform, edition, hardware and codec profile; a missing option is not itself a fault. Check the [platform-specific codec guide](https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/) rather than assuming an MP4 extension guarantees support. A successful software-decode test points toward the hardware decoding path or its interaction with this media; it does not prove a corrupt file or a broken GPU. A failed test still leaves source damage, an unsupported profile, storage access or an effect in scope. Restore the setting if it makes no difference. Before changing Resolve, the OS or a driver, save individual project and library backups and check the release requirements. Do not uninstall unrelated codecs or plug-ins on a hunch. Full resolution media not found calls for an original-media availability check, separate from the decoder tests above. The wording alone does not prove the original file was deleted. A proxy can play while its original is unavailable. Reconnect the original and check its path before final output; do not silently substitute a lower-quality proxy just to make the job finish. If the same frame fails in more than one player or a trusted transcoder, treat source integrity or an unsupported stream as the leading hypothesis, not proof that the file is corrupt. If a trusted transcoder can read the complete clip, make a new constant-frame-rate mezzanine file, replace only the problem clip in a duplicated timeline, and verify sync before the final render. ## GPU Memory Is Full During Render GPU memory errors indicate pressure, not one guaranteed culprit. Timeline and output resolution, temporal or AI spatial noise reduction, Resolve FX or third-party OFX, Fusion, motion blur and oversized stills can all contribute. Use the [GPU Memory Full diagnostic](https://davinciresolveclub.com/davinci-resolve-gpu-memory-full/) for that exact message, compare the workload with the [DaVinci Resolve system requirements breakdown](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/), then isolate the failing clip before changing hardware. Start with the failing clip: bypass temporal or AI spatial noise reduction if used, the heaviest Resolve FX or third-party OFX, large Fusion branches, motion blur and oversized stills one at a time. A lower-resolution test reduces processing demand and may support a memory-pressure hypothesis, but it does not prove the cause. Restore the required delivery resolution after the test. Don't buy hardware from the error message alone. First prove that the job passes when one memory-heavy operation is bypassed. If the final grade requires that operation, render the isolated shot to a suitable high-quality intermediate or move the job to a verified machine with enough supported GPU memory. ## Unable to Initialize GPU When Rendering Unable to Initialize GPU is different from a full-memory warning: Resolve hasn't established a usable processing device. Open Preferences > System > Memory and GPU and check GPU Processing Mode and GPU Selection. Start with Auto. Manual mode exposes CUDA, OpenCL or Metal when the operating system and GPU support them; if the correct supported GPU is missing, close Resolve and update the vendor driver or the operating system before forcing a manual selection. On Windows laptops with integrated and discrete graphics, the operating-system Graphics preference can assign Resolve to the high-performance GPU. On macOS, GPU drivers arrive with system updates rather than separate NVIDIA or AMD installers. Change one layer at a time so you know whether the failure came from Resolve selection, the OS assignment, or the driver. ## Render Stuck With No Progress and No Error A render that barely advances may be processing one expensive frame rather than being frozen. Test a ten-second range with heavy NR, optical flow and Fusion bypassed one at a time, recording which change helps. Watch CPU, GPU and disk activity, but do not treat low readings as proof of a particular fault. Check that source, cache and destination storage remain available. If playback is slow too, use the [slow-playback diagnostic](https://davinciresolveclub.com/davinci-resolve-slow-playback/) to separate decoding, effects and storage limits. If monitoring is also broken or an audio device was recently disconnected, check Preferences > System > Video and Audio I/O > I/O Engine. The manual lists System Audio, Desktop Video, Fairlight Audio Accelerator and ASIO, with ASIO limited to Windows. Select an available device and work through the [DaVinci Resolve no-audio checks](https://davinciresolveclub.com/davinci-resolve-no-audio/). This is a targeted check when there is an audio symptom, not evidence that every stalled render is waiting for an ASIO device. ## Render Fails Only On Certain Clips When failures follow clips from one phone or camera, inspect the named source rather than blaming every clip from that device. Check whether it is offline or on unstable storage, whether the failing frame decodes, and whether the source uses variable frame rate. Keep codec and delivery decisions in the [DaVinci Resolve export settings guide](https://davinciresolveclub.com/export-video-davinci-resolve/); this section is for isolating the source. Do not change Clip Attributes to pretend variable-frame-rate media is constant; that changes interpretation, not the source timestamps. Confirm VFR with a media inspector before trying a constant-frame-rate transcode. Keep the original, transcode the complete clip to a supported editing format, and replace it only in a duplicated timeline. Verify duration, start timecode, frame rate, audio sync and color. Not every phone clip is VFR, and different camera frame rates are not automatically an error. ## Render Failed Because the Disk or Cache Drive Is Full Resolve can export to one drive while reading or writing cache on another, so check free space and write access on both. Also verify the target filesystem's file-size limits and whether a network or removable destination stayed mounted through the failed job. ![Timeline range bisection for locating the clip or effect that breaks a DaVinci Resolve render](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/range-bisection-v1.webp) Narrow the failing range, then change one variable at a time instead of repeating the complete export. Use Playback > Delete Render Cache > Unused to remove cache entries that no longer correspond to timeline clips or effects. The final Resolve 21 manual also offers All and Selected Clips; use the narrowest option because deleted cache must be rebuilt. Moving the cache location doesn't move or repair an existing partial cache. ## Render Fails at the Same Percentage Every Time A repeatable percentage often points to the same timeline region, but the job percentage is only an estimate. Note the reported timecode when available; otherwise render a short range around the approximate point and inspect every clip, transition, Fusion comp, OFX process and source file that overlaps it. If the failure moves between attempts, widen the test to system state: GPU memory, driver stability, source or destination storage, cache space, audio I/O and hardware decoding. A moving point makes one deterministic bad frame less likely, but it does not prove every source clip is healthy. ## How to Find the Exact Clip That Breaks the Render When Resolve supplies a timecode, test a few seconds before and after it. With percentage only, estimate the timeline position, then include handles because transitions, retiming and Fusion can process frames outside the visible cut. Set In and Out points around the suspect region and render that range. If it fails, halve the range and test again; if it passes, expand toward the original boundary. Once one clip is isolated, duplicate the timeline and bypass only its Fusion comp, OFX, grade, retime or source replacement in separate tests. If no short test isolates it, choose Help > Create Diagnostics Log on Desktop. Record the exact Resolve build and Free/Studio edition, OS, GPU and driver, source codec details, output settings and failure timecode. A minimal project reproducing the failure is more useful to support than another complete export attempt. Check Blackmagic’s [current release notes](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) before updating: the 21.1 notes warn that a project opened in 21.1 cannot be opened in 20.3.2, even though the library remains compatible. Keep a pre-upgrade backup, and review logs and project files for private paths or client material before sharing them. ## Render Failed FAQ ### Why does DaVinci Resolve render fail at the same percentage every time? A repeated percentage often means Resolve reaches the same clip, frame, Fusion composition, OFX effect, cache section or source file. Test a short range around that point before changing project-wide settings. ### Does DaVinci Resolve Studio render fail less often than the free version? No edition guarantees a successful render. Free and Studio share core processing, while Studio adds different codec paths, noise reduction, AI effects and higher-end delivery options that can introduce different bottlenecks. Match the failure to the active feature, then use the [free versus Studio breakdown](https://davinciresolveclub.com/davinci-resolve-vs-studio/) to verify the edition difference. ### Does restarting your computer actually fix a DaVinci Resolve render failure? A restart can clear temporary GPU, driver and audio-device state, so it's a reasonable first diagnostic step. It isn't proof of a fix. If the same range fails again, return to the exact message, timecode and isolated test instead of restarting repeatedly. ### Can "Use render cached images" be part of a final delivery after troubleshooting? Only when the cache format is suitable for final delivery. Use render cached images lets the Deliver page use cached media instead of recalculating that processing. The Resolve 21 manual recommends a format of the same quality as the output or better. Rebuild changed sections and inspect the final file; if the cache is lower quality, leave the option off and render from the original media. For export format, codec, bitrate and platform delivery, use the [DaVinci Resolve Export Settings hub](https://davinciresolveclub.com/davinci-resolve-export-settings/). For other playback, media and hardware failures, start from the [Fix DaVinci Resolve troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/). ### DaVinci Resolve YouTube Export Settings URL: https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/ Last updated: 2026-09-12T10:17:19.000Z For a standard SDR upload from a Resolve installation that offers these codecs, start with MP4, H.264 High Profile, the timeline’s intended resolution and frame rate, AAC audio at 48 kHz, and matching BT.709 metadata. YouTube’s published bitrates are reference values, not minimums. Use the YouTube preset for a quick setup or Custom Export when you need more control. The built-in preset is the faster route and now covers 720p, 1080p, 1440p and 2160p. Custom Export is useful when you need to inspect Quality, keyframes, audio routing or color tags. Neither route prevents YouTube from re-encoding the upload, so the goal is a clean source file with correct timing, color and audio, not a mythical setting that avoids compression. If the Deliver page itself is unfamiliar, start with the [full Resolve export walkthrough](https://davinciresolveclub.com/export-video-davinci-resolve/). This guide stays on the YouTube-specific decisions. For every other delivery target, the compact [DaVinci Resolve Export Settings hub](https://davinciresolveclub.com/davinci-resolve-export-settings/) routes by task without repeating this YouTube recipe. ## DaVinci Resolve YouTube Export Settings: Quick Answer | Control | Recommended starting point | Decision impact | | ---------------- | --------------------------------------------------------- | ----------------------------------------------------------- | | Preset | YouTube 720p/1080p/1440p/2160p or Custom Export | Both are valid; Custom exposes more controls | | Resolution | Match the intended timeline/output | Do not upscale only to chase a codec rumor | | Frame rate | Keep the intended timeline frame rate | YouTube asks for the source frame rate | | Format / codec | MP4 / H.264 | Matches YouTube's published upload baseline | | Encoding profile | High | The profile named in YouTube's baseline | | Quality | Automatic quality, where offered, or a deliberate bitrate | Resolve's Restrict to field is a maximum data rate | | Key frames | Automatic | Avoid forcing the wrong GOP for a platform-specific encoder | | Audio | AAC, normally stereo, 48 kHz | Matches YouTube's upload audio guidance | | SDR color | BT.709 primaries, transfer and matrix | Avoids an avoidable metadata conversion | ![DaVinci Resolve 21 Deliver page YouTube preset with annotated resolution, frame rate, H.264, bitrate and audio controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-ui-corrected.webp) Resolve's YouTube preset is a valid starting route. Match the timeline, inspect the bitrate as a recommendation rather than a minimum, confirm AAC at 48 kHz, then add the job to the Render Queue. On the YouTube preset, choose the resolution version that matches the timeline and confirm the timeline frame rate. Resolve 21's [Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) says the preset renders one clip at the timeline frame rate with MP4, H.264 High and AAC. It can also upload directly after you connect a YouTube account, including chapter markers from timeline markers and a selected thumbnail. The preset also inherits Data Burn-In from the project, so confirm that no unwanted burn-in preset is active before rendering. On Custom Export, choose MP4 and H.264, then inspect the controls available on your system. Encoder and rate-control choices vary with operating system, GPU, driver and edition. Use a quality-based Automatic setting if the encoder offers it, or set a deliberate bitrate and check a short export. There is no single Quality menu shared by every encoder. Resolve describes Restrict to as a maximum data rate, not a guaranteed average; enter Kb/s rather than Mbps. For a finished edit, choose Single clip and confirm Entire Timeline in the render-range menu; use an In/Out range only for a deliberate excerpt. Check the filename and destination, add the job to the Render Queue, then inspect that queued job before rendering. If Entire Timeline is unavailable, clear clip filtering first. A correct codec cannot fix a job that exports only half the timeline. Keep the timeline’s intended frame rate, including fractional rates such as 23.976 or 29.97\. With mixed-rate footage or slow motion, review the retiming in the edit rather than switching the whole export to one camera’s rate. Check pans and lip sync in the rendered sample; a higher export frame rate does not recreate missing source frames. ## YouTube Bitrate Recommendations for 1080p, 1440p and 4K The current [YouTube recommended upload encoding settings](https://support.google.com/youtube/answer/1722171?hl=en&ref=davinciresolveclub.com) page gives the following SDR references. Standard frame rate means 24, 25 or 30 fps; high frame rate means 48, 50 or 60 fps. Multiply Mbps by 1,000 when Resolve asks for Kb/s. | Resolution | 24/25/30 fps | 48/50/60 fps | | ---------- | ------------ | ------------ | | 2160p (4K) | 35–45 Mbps | 53–68 Mbps | | 1440p | 16 Mbps | 24 Mbps | | 1080p | 8 Mbps | 12 Mbps | | 720p | 5 Mbps | 7.5 Mbps | ![YouTube recommended SDR upload bitrates for 720p, 1080p, 1440p and 4K video](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/youtube-sdr-bitrates.webp) YouTube's recommended SDR upload references vary by resolution and standard or high frame rate. These numbers are not a quality floor and YouTube explicitly says no bitrate limit is required. They're a useful size-and-quality reference for an H.264 upload. A quality-based export may produce a larger file; a manually restricted export may be smaller and more predictable. Fast motion, grain, particles and gradients are harder to compress than a locked talking head, so inspect a representative rendered section before committing to a long queue. YouTube's H.264 baseline also names progressive scan, two consecutive B-frames, CABAC, 4:2:0 chroma, variable bitrate and a closed GOP of half the frame rate. Resolve exposes different subsets of these controls depending on container and encoder. Leave Key Frames on Automatic unless the selected encoder exposes a reliable manual option and you understand how its value maps to the recommended GOP. ## H.264 vs H.265 for a YouTube Upload Choose H.264 when you want the closest match to YouTube's published baseline and the broadest handoff compatibility. H.265/HEVC can make a smaller upload at a given visual quality, but the exact result depends on the encoder and source. YouTube accepting an HEVC file doesn't mean it prefers HEVC for ordinary SDR uploads, and no honest guide can replace a test with one universal H.264-to-H.265 bitrate conversion. For HDR, the choice changes because YouTube requires 10- or 12-bit video and valid HDR metadata. Its [HDR upload guidance](https://support.google.com/youtube/answer/7126552?hl=en-GB&ref=davinciresolveclub.com) recommends HEVC, VP9 Profile 2 or AV1\. That does not mean every Resolve installation can export every listed codec or profile. Changing an SDR file’s codec or tag alone does not make an HDR master. ## Free vs Studio: Check the Controls You Actually Have Resolve Free’s overall delivery ceiling is Ultra HD 3840×2160 at up to 60 fps. That is separate from codec availability. Studio extends the resolution and frame-rate ceiling and adds accelerated encoding options on supported systems; it does not make every GPU, operating system and codec combination interchangeable. Before buying Studio to fix a slow render, compare your actual Encoder and Audio menus with the [Free-versus-Studio boundaries](https://davinciresolveclub.com/davinci-resolve-free-version-features/) and [system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). Use software H.264 only where your installation offers it. In particular, do not assume a Linux setup has the same H.264/AAC route as a Mac or Windows machine. Check the [platform-specific codec guide](https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/) before selecting an intermediate file or a separate encoding step. ## Audio Export Settings for YouTube In Render Settings > Audio, export the Main bus you actually monitored. Use AAC for a normal MP4 upload, 48 kHz sample rate, and the correct channel layout. YouTube currently recommends 384 kbps for stereo and 512 kbps for 5.1\. A clean mix matters more than pushing the codec number while the wrong bus, a muted track or clipping is present. For an ordinary stereo upload, export the stereo mix rather than individual timeline tracks. If the AAC encoder does not offer exactly 384 kbps, use an available high-quality setting and check the file; the recommendation is not an upload rejection threshold. For surround, check the stereo presentation too—YouTube’s listed channel layout includes stereo plus 5.1, not a reason to send an unmonitored multichannel mix. Loudness is a different control. The Resolve 21 manual describes a YouTube normalization target around -14 LUFS and the YouTube preset exposes Normalize Audio. Treat that as Resolve's delivery target, not a rule that YouTube's upload form uses to accept or reject the file. The [Resolve LUFS and audio-level guide](https://davinciresolveclub.com/davinci-resolve-audio-levels-lufs/) covers integrated loudness, true peak and bus measurement without mixing them up with AAC bitrate. ## Color Space: SDR BT.709 and the HDR Boundary For SDR, YouTube recommends BT.709 for color primaries, transfer characteristics and matrix coefficients. If the project uses DaVinci Wide Gamut, ACES or CST nodes, verify that the output transform lands in SDR BT.709 and that the exported file carries matching tags. Color Space Tag and Gamma Tag describe the file; changing those tags alone does not apply the missing output transform. Don't fix a color-management problem by raising bitrate. HDR needs its own master, compatible 10- or 12-bit encoding, Rec.2020 primaries and non-constant-luminance matrix, and a PQ or HLG transfer function with matching metadata. YouTube publishes separate HDR bitrate references: 44–56 Mbps for 4K at 24/25/30 fps and 66–85 Mbps at 48/50/60 fps. The [Resolve color-management guide](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/) explains RCM, CST order and double-transform failures before you reach Deliver. ## YouTube Preset vs Custom Export Use the YouTube preset when you want a fast, documented MP4/H.264 High export and optional direct upload. Use Custom Export when you need to control a delivery ceiling, inspect the audio bus, choose a different codec, verify color tags or save a reusable preset. Custom isn't automatically higher quality; it only exposes more decisions. If the selected MP4 encoder exposes Network Optimization, enable it for a web-delivery file. YouTube asks for the MP4 moov atom at the front, commonly called Fast Start. Because Resolve's available controls vary by encoder, verify the finished file when this packaging detail matters instead of treating one checkbox as universal across every platform. Before a final upload, check Use Proxy Media, Use optimized media and Use render cached images if they are available in the selected preset. Those options can use generated media in the output. Leave them off when those files are lower quality than the intended master, and confirm that the originals are online. Playback proxies and delivery choices are different decisions. ## Exporting Vertical Video for YouTube Shorts For a vertical Short, prepare and reframe a portrait timeline—1080×1920 is a practical starting size—then verify the exported dimensions instead of assuming a landscape preset will rotate them. YouTube’s player adapts to the file’s aspect ratio, so do not bake black side bars into a widescreen frame. The [aspect-ratio guide](https://davinciresolveclub.com/change-aspect-ratio-davinci-resolve/) covers reframing subjects and captions. For new uploads, YouTube currently classifies square or vertical videos up to three minutes as Shorts. Its [three-minute Shorts guidance](https://support.google.com/youtube/answer/15424877?hl=en&ref=davinciresolveclub.com) also explains an important exception: a Short over one minute with an active Content ID claim is blocked globally. Check the upload’s classification and restrictions in Studio; changing bitrate will not remove a claim. ## Why a YouTube Upload Looks Soft, Dark or Incomplete First, wait for high-resolution processing. YouTube makes a low-resolution version available before 1080p and 4K processing finishes, and [high-resolution processing can take hours](https://support.google.com/youtube/answer/71674?hl=en-EN&ref=davinciresolveclub.com). Judge the upload only after the intended quality option appears. If it is still wrong, isolate the failure. Soft blocks in motion point toward the source encode or an overly restrictive data rate. A global gamma or saturation shift points toward color primaries, transfer or matrix tags. Missing sound points toward the selected output bus or Audio checkbox. If the local file looks different, reimport a short sample into the same managed project and compare it with the timeline, then check another player. That helps separate an export or transform error from player interpretation. If the local file checks out but the processed upload does not, investigate metadata, YouTube processing and playback before changing the grade. ![Pre-upload checklist for a DaVinci Resolve YouTube export](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/youtube-upload-checklist.webp) Verify frame rate, progressive scan, audio, BT.709 tags, a short test file and the final destination before uploading. Render a short section containing motion, gradients, dialogue and the darkest shot. Play that file outside Resolve, inspect audio, then upload it as unlisted and wait for the intended resolution. That test is faster and more reliable than changing five unrelated settings after a full-length export fails. ## YouTube Export FAQ ### What bitrate should I use for a 4K YouTube export in DaVinci Resolve? YouTube recommends 35–45 Mbps for 4K at 24/25/30 fps and 53–68 Mbps at 48/50/60 fps for SDR H.264 uploads. Treat these as reference values, not minimums. A quality-based Automatic mode is another option where your encoder offers one; check a representative export rather than trusting the label alone. ### Should I use the YouTube preset or Custom Export in Resolve 21? Both are valid. The YouTube preset gives you a documented MP4, H.264 High, timeline-frame-rate export and optional direct upload. Use Custom Export when you need explicit control over bitrate, audio routing, codec or color tags. ### Should I export H.264 or H.265 for YouTube? Use H.264 for the closest match to YouTube's published SDR upload baseline and broad compatibility. HEVC can reduce upload size, and it's useful for supported HDR workflows, but there's no universal bitrate conversion that makes it automatically better. ### What audio settings should I use for YouTube? Use AAC in a normal MP4 file, 48 kHz sample rate, and the bus and channel layout you actually mixed. YouTube recommends 384 kbps for stereo and 512 kbps for 5.1 uploads. ### What color space should I export for SDR YouTube video? Use BT.709 primaries, transfer characteristics and matrix coefficients for SDR. If the project is managed in DaVinci Wide Gamut, ACES or CST, verify the final output transform and tags rather than changing only the codec. ### Does upscaling 1080p to 4K guarantee better YouTube quality? No. Upscaling does not recreate detail that was never captured, and these upload settings cannot guarantee which playback codec or quality a viewer receives. If you want to compare a higher-resolution upload, make a short A/B test and wait for both versions to finish processing. Keep the version that actually looks better for your footage. ### Why is my YouTube upload blurry even though the local export is sharp? Wait until 1080p or 4K processing finishes; YouTube publishes the low-resolution version first. If the final high-resolution stream is still soft, compare a short test for source quality, frame rate, bitrate restriction and color metadata one variable at a time. ### How to Use LUTs in DaVinci Resolve URL: https://davinciresolveclub.com/how-to-use-luts-in-davinci-resolve/ Last updated: 2026-09-14T13:15:44.000Z Open Project Settings > Color Management > Lookup Tables, click Open LUT Folder, copy your extracted LUT file, then click Update Lists and Save. On the Color page, apply it to a dedicated node. Check the LUT's expected input and output before judging the picture or adjusting strength. If exposure and white balance still need work, use the [beginner color-grading workflow](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/) alongside this guide. Here, start with installation and application, then check node order and color management before adjusting the look. ## Where DaVinci Resolve Stores LUT Files on Mac and Windows Resolve's safest installation route is inside the application: open Project Settings > Color Management and use Open LUT Folder. That button opens the folder the current installation actually reads. The [DaVinci Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) documents this path, the Update Lists control and the current LUT Browser behavior. The standard macOS folder is /Library/Application Support/Blackmagic Design/DaVinci Resolve/LUT/. On Windows, it is C:\\ProgramData\\Blackmagic Design\\DaVinci Resolve\\Support\\LUT. The current manual lists two different Linux defaults in separate chapters, so use Open LUT Folder rather than guessing a Linux path. Windows ProgramData is normally hidden; the button avoids that navigation problem. The non-Studio Mac App Store build uses a self-contained location. Don't copy a path from another tutorial and assume it applies. Open the folder from Resolve, then add or remove files there. Facilities can add custom LUT paths in DaVinci Resolve Preferences > System > General when several workstations share a library. ## How to Install a LUT in Resolve's Color Management Settings If your download is a ZIP archive, extract it first. Copy the actual LUT files into the folder Resolve opened. Resolve 21 supports 1D and 3D .cube LUTs, externally created Shaper LUTs in .cube format, Panasonic VLUT and CLF. DCTL files are code-based transforms, not ordinary lookup tables. Keep the vendor's input/output notes with the files; an accepted extension doesn't prove that a LUT suits your footage. Return to Color Management, click Update Lists, then Save to close Project Settings. In the Color page LUT Browser, you can instead select the relevant category, right-click in the browser area and choose Refresh. Update Lists refreshes the LUT menus; Refresh reloads the selected browser category from disk. Use named subfolders for camera transforms, show looks and calibration LUTs, but don't rename a vendor pack blindly: a project can report a LUT as missing when its expected path or filename no longer matches. Resolve 21 also exposes a Missing LUTs tab when a grade refers to unavailable files. ## Applying a LUT to a Node in Resolve's Color Page Open the Color page and select your clip. Click LUTs in the toolbar to open the LUT Browser. Select a node in the Node Editor and choose Color > Nodes > Add Serial for a separate LUT node. With that new node selected, right-click the LUT and choose Apply LUT to current node, or drag it onto the node. Dropping another LUT on the same node replaces the previous one. ![LUT Browser with categories and preview thumbnails on the Resolve Color page](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/lut-browser.webp) Select the category containing your LUT, then apply it to the selected node. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3481. Resolve can also apply a LUT directly to one or more source clips from the Media Pool or Color-page thumbnail timeline. That isn't inherently wrong, but the current manual warns that source-clip LUTs don't travel between timelines through ColorTrace. A node LUT is usually easier to label, bypass, reorder and revise as part of the grade. Keep a transform or look on a dedicated node when you expect to compare or blend it. The [nodes explained guide](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) covers the wider serial, parallel and layer logic; here the important point is that the node makes the LUT's place in the signal path visible. ## Technical LUT vs Creative LUT A technical LUT maps a known source state to another defined state: for example, one camera gamut/gamma to a monitoring or delivery space. A creative LUT creates a look. Some LUTs combine both jobs, so labels such as “cinematic” or “log conversion” aren't enough; read the documentation for the exact expected input and output. If a creative LUT expects Rec.709 but receives camera log or DaVinci Wide Gamut, it can clip, wash out or distort color. If a camera-transform LUT expects S-Log3/S-Gamut3.Cine but receives another Sony profile, the file may load perfectly while the image is still wrong. Installation success and color accuracy are separate checks. ## Where to Place the LUT Node in a Resolve Node Tree Place a LUT where the signal matches its documented input. That single rule is more reliable than “technical first” or “creative last.” A technical LUT that converts native camera log must see that native encoding. A creative LUT built for an already normalized image belongs after the normalization and the corrections its designer expects. Resolve applies a LUT as the last operation inside its node, after the other Color page adjustments made in that same node. This means the node's color and contrast controls can trim the signal before it enters the LUT. A separate upstream node is often clearer, but it isn't required by the image pipeline. If the LUT clips highlights, lower exposure or contrast before it, either in an upstream node or with that node's controls. A trim after the LUT only lowers the already-clipped result. This doesn't damage your source file: bypassing the LUT removes its processing. But no LUT adjustment can recreate detail already clipped in the recorded source. There's no universal slot number for every LUT. The correct position depends on four facts: current signal state, expected input, LUT output and the output transform that still remains. Label the node with the LUT's job, not merely “LUT.” ## Node-Order Examples That Do Not Double-Transform the Image Use these as diagnostic patterns, then replace the generic labels with the actual color spaces from the LUT documentation: - **Camera-transform LUT:** exact camera log/gamut, then exposure and balance trim while still in the expected input, then transform LUT, then display-referred finishing. - **Creative Rec.709 LUT:** deliberate normalization to Rec.709, then balance and shot matching, then creative LUT, then final trim and scope check. - **Scene-referred creative LUT:** correct input tagging, then work in the LUT's documented scene-referred space, then creative LUT, then one intentional output transform. - **Cineon film-print LUT:** convert the working signal to the documented Cineon input, then film-print LUT. Do not append another output CST unless the LUT documentation and delivery pipeline require it. If the image breaks, read the chain from left to right and name the signal between every node. Don't add another normalization step just because a tutorial shows one. Use the [RCM vs CST guide](https://davinciresolveclub.com/davinci-resolve-color-management-rcm-cst/) to choose the full project color-management setup. ## Fixing LUTs That Won't Show Up First, refresh the list. In Project Settings > Color Management, click Update Lists. In the LUT Browser, select the category, right-click in the browser area and choose Refresh. Restarting Resolve can also force a rescan, but it shouldn't be the first or only instruction. If the file is still absent, check that you copied the extracted LUT, not its ZIP archive or a download shortcut. Confirm the location and format against the vendor's instructions. A damaged file, unsupported syntax or unavailable custom path can stop discovery even when the extension looks familiar. Renaming another file to .cube does not convert it into a LUT. When a project opens with missing transforms, look for the Missing LUTs overlay and the Missing LUTs tab in the Browser. Restore the original file/path when possible instead of silently substituting a different look. In an App Store installation, always reopen the actual folder from Resolve because its sandbox path differs from the standard macOS location. ## Blending LUT Intensity with Resolve's Key Output Gain For a creative LUT that preserves the same input and output color space, select its node, open the Key palette and lower Key Output Gain. This blends the node's result toward its input. It doesn't rewrite the LUT or fix a color-space mismatch. ![Resolve Key palette with Key Input and Key Output controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/key-palette.webp) Use Gain under Key Output, not the primary color-wheel Gain control, to fade a same-space creative look. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3436. Keep a technical conversion at full strength. Lowering the gain of a log-to-Rec.709 LUT mixes log and display-referred values instead of giving you a gentler but still correct conversion. If a LUT combines a look with a technical transform, use a documented strength control or separate the look from the conversion before blending. Key Output Gain affects the whole node, including its exposure adjustments, windows and qualifiers. Keep the creative LUT separate for predictable control. Start at the default 1.00 and compare the image and scopes as you lower it. There is no universal percentage that suits every look or shot. ![Four versions of a grade compared at Key Output Gain 1, 0.75, 0.5 and 0.25](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/node-strength-comparison.webp) Compare the entire image as node strength changes. These values illustrate the control, not recommended LUT percentages. Source: Blackmagic Design, Resolve 21.1 Reference Manual, p. 3438. ## LUTs in Resolve Color Management and DaVinci Wide Gamut A wide-gamut timeline isn't the problem by itself. The mismatch happens when a LUT designed for another signal receives DaVinci Wide Gamut/Intermediate values. Identify whether the LUT expects camera log, Cineon, Rec.709 or a scene-referred working space, and whether it returns a look in the same space or includes a display transform. In Resolve Color Managed projects, input and output mapping may already happen outside the clip node tree. Adding a camera-to-Rec.709 LUT or duplicate CST on top of that can apply the conversion twice. Inspect the clip's Input Color Space and the project Timeline/Output spaces before adding another transform. A CST before the LUT is appropriate when it intentionally converts the current working signal into the LUT's required input. A CST after it's appropriate only when the LUT's documented output must be returned to another working space. Don't build an automatic “CST sandwich” around every LUT; a film-print LUT that already outputs a display-referred result may make the second transform wrong. Converting the LUT's output back to a wide-gamut space cannot restore detail that the LUT or an earlier transform clipped. In an RCM project, prefer a creative LUT that expects and returns the timeline's working space when you don't have a documented integration for another LUT. When the signal path is unclear, bypass the LUT and every adjacent transform, then enable them one at a time while reading the waveform, RGB parade and vectorscope. The [Resolve scopes guide](https://davinciresolveclub.com/davinci-resolve-scopes-explained/) helps separate real clipping from a viewer or monitoring impression. ## Reduce LUT Banding Without Guessing Resolve must interpolate values between the points stored in a 3D LUT. Project Settings > Color Management > 3D Lookup Table Interpolation offers Trilinear and Tetrahedral. The current manual describes Trilinear as the backward-compatible default and Tetrahedral as slightly more processor-intensive with higher-quality LUT/DCTL processing and reduced color banding. Use Tetrahedral when the project does not need to reproduce an older grade or match LUT processing in another application. Also inspect the source bit depth, codec, scopes and the result with each LUT bypassed. Stacking LUTs can compound clipping or quantization, so interpolation is one check, not permission to keep every transform in the chain. ## Creating a Custom LUT Right-click a clip thumbnail in the Color-page timeline and open Generate LUT. Resolve 21 offers 17 Point Cube, 33 Point Cube, 65 Point Cube and Panasonic VLUT. The manual doesn't recommend 17-point LUTs for grading, but they can suit on-set devices that need a smaller, broadly compatible cube. Higher point counts improve sampling precision but can reduce device compatibility. Choose the destination in the file dialog, enter a name and click Save. Include the intended input and output spaces in your handoff notes. If you save outside Resolve's LUT directories, copy the exported file into a configured folder and refresh the list before using it. The native LUT Browser, node workflow and Generate LUT path are part of the current Resolve 21 color workflow; they don't depend on the Studio-only AI and extra Resolve FX listed on the [official DaVinci Resolve page](https://www.blackmagicdesign.com/products/davinciresolve?ref=davinciresolveclub.com). If the broader edition decision matters, use the [Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) rather than buying Studio to solve an ordinary LUT-install problem. A generated LUT is not a portable copy of the whole grade. Resolve can translate Primaries, Custom Curves and compatible Color Space Transform, ACES Transform and Gamut Mapping operations. Nodes containing qualifiers, Power Windows, incompatible filters such as sharpening or blur, or incompatible ResolveFX/OpenFX are completely ignored, including other corrections in those nodes. Keep exportable adjustments on separate nodes, then re-import the LUT and compare it with the intended grade on footage with the same input encoding. ## Frequently Asked Questions About LUTs ### Are LUTs free to use in DaVinci Resolve? The normal install, LUT Browser, node application, Key Output Gain and Generate LUT workflow is available in the free version of Resolve. You don't need Studio for an ordinary .cube LUT. A third-party LUT pack can still have its own price and usage license; free software support doesn't make every pack free. ### Can I use LUTs made for Premiere Pro in DaVinci Resolve? Usually, if the file is a compatible .cube LUT and you know the color space and gamma it expects. The extension alone doesn't guarantee the look will match: Resolve must feed the LUT the same signal it was designed to receive. ### Should a LUT go on a single clip's node or the whole timeline? Use a clip or camera group when the transform belongs to one source type. Use a timeline-level LUT only when every shot should receive the same transform at that stage. For mixed cameras, one global technical LUT can misinterpret part of the timeline. ### What's the difference between a 1D and 3D LUT in DaVinci Resolve? A 1D LUT maps channels independently and is suited to tone or per-channel transforms. A 3D LUT maps red, green and blue together, so it can change hue and saturation as well as tone. Resolve 21 supports both in .cube workflows. ### Why does my LUT look wrong in DaVinci Resolve? Check for a signal mismatch first: wrong camera gamut or gamma, duplicate color management, or a LUT receiving DaVinci Wide Gamut when it expects another space. Verify its documented input and output, then check exposure and clipping before changing saturation or stacking another LUT. ### How do I reduce LUT strength in DaVinci Resolve? For a same-space creative LUT, put it on its own node, open the Key palette and lower Key Output Gain. This fades the whole node. Don't use that shortcut to weaken a technical log-to-display conversion, because it mixes differently encoded signals. Separate the creative look from the conversion first. ### Should I use a LUT or a Color Space Transform in DaVinci Resolve? Use Resolve Color Management or a Color Space Transform when you need an explicit, adjustable conversion between known color spaces. Use a technical LUT only for the exact input it was built for, and use a creative LUT when you want its specific look. Use the [Color Grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/) to continue through color management, scopes, node structure and matching in a deliberate order. A LUT should make a known pipeline faster; it should never be the part of the grade you can't explain. ### How to Color Grade in DaVinci Resolve: Beginner Tutorial URL: https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/ Last updated: 2026-09-12T18:25:56.000Z **Quick answer:** Decide how the footage is color-managed before touching the wheels. Then correct exposure and color balance, shape contrast, match the shots, build the look, isolate only what still needs local work, and check the result through the intended output transform. Use the waveform, RGB parade and vectorscope as measurements, but judge the picture on a trustworthy display. A beginner doesn't need a giant node tree or a LUT on every clip. ## The Beginner Color-Grading Order Use this sequence as a diagnostic order, not as a rigid recipe: 1. Confirm the clip's input color space and the project's output target. 2. Open the Color page and scopes. 3. Correct exposure, neutral balance and obvious shot-to-shot differences. 4. Shape contrast and color with primaries or curves. 5. Match adjacent shots before polishing a hero frame. 6. Build the creative look. 7. Add qualifiers, Power Windows or tracking only where global controls can't solve the problem. 8. Review the full sequence, then render a short test in the actual delivery format. “Correction” and “grading” are useful labels, not separate engines inside Resolve. The same controls can do both. The distinction helps you debug: first make the image technically coherent with the sequence, then make deliberate creative choices. If the look breaks when a clip changes, return to the correction or color-management decision instead of piling on another node. ## Step 1: Set Color Management Before You Grade Flat log footage isn't a cue to add the first LUT you find. Resolve needs to know what the source represents, what working space the grade uses and what the output should be. In Resolve Color Management, those responsibilities are the Input, Timeline and Output color spaces. The [current DaVinci Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) explains that the input-to-timeline and timeline-to-output transforms are distinct parts of the pipeline. For a simple managed project, open **Project Settings > Color Management**, set **Color science** to **DaVinci YRGB Color Managed**, and choose an automatic or manual setup that matches the job. Automatic Color Management simplifies common cases; a manual preset exposes more control. The **Output color space** must match the delivery and monitoring target, not whatever looks punchiest in the menu. ![DaVinci Resolve 21 Color Management settings for managed mode, grading environment and output space](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-color-management.webp) Choose one deliberate color-management path. The output space follows the delivery target; an extra CST or technical LUT can double-transform footage that Resolve already manages. Next, verify the clips. RCM gets a camera RAW clip's input color information from the camera manufacturer's specifications; you cannot override that clip's Input Color Space assignment manually. Non-RAW media may use embedded metadata or the project's default input. If a non-RAW log clip was interpreted incorrectly, select it in the Media Pool and check its Input Color Space assignment. Fix the tag before reaching for extreme contrast and saturation. A manual **DaVinci YRGB** project can instead use Color Space Transform nodes or appropriate technical LUTs. That's a valid pipeline, not a beginner mistake. The mistake is stacking transformations without knowing what each one expects: for example, an input CST in the node tree on media that RCM has already transformed. Pick one deliberate normalization strategy and test it before grading the timeline. You also don't have to convert every clip into a “normal Rec.709 image” before any useful work can happen. A managed project can grade in a wide-gamut timeline space and convert to the chosen output later. If this boundary feels unclear, the [Color Grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/) keeps the color-management, node, scope and LUT guides in one learning path. ## Step 2: Open the Color Page and Scopes Click **Color** in the page bar. The viewer, clip thumbnails, Node Editor and grading palettes now describe one selected clip. To open floating scopes from the Media, Color or Deliver page, use **Workspace > Video Scopes > On/Off**. Resolve can also place scopes in a dual-screen layout. Start with three measurements: - **Waveform:** shows signal level across the horizontal position of the frame. Use it to locate exposure, contrast and clipping, not to force every image to fill the scale. - **RGB Parade:** displays channel strengths side by side. It helps identify a cast, but equal channels are only expected in neutral parts of the scene. - **Vectorscope:** plots hue by angle and saturation by distance from the center. The optional skin-tone indicator is a general reference for average skin hue, not an instruction to rotate every face onto one line. ![DaVinci Resolve waveform RGB parade and vectorscope reading a portrait grade](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-scopes.webp) Waveform measures signal level, RGB Parade compares channels and Vectorscope plots hue and saturation. The skin-tone line is a guidepost, not a verdict on the shot. Scopes measure the image signal; they do not know whether the scene is meant to be blue at night, warm at sunset or lit by a colored sign. Do not “neutralize” intentional lighting because a graph is uneven. Conversely, the computer viewer isn't proof of accurate output. For dependable finishing, the display path and monitor must be appropriate for the target. The detailed [Resolve scopes guide](https://davinciresolveclub.com/davinci-resolve-scopes-explained/) shows what each graph can and can't tell you. ## Step 3: Build a Node Tree You Can Debug A Corrector node can contain several Color page operations. Resolve doesn't require one tool per node. Separating responsibilities is still useful when order matters or when you need to bypass one decision without disabling everything else. A clean beginner chain might use **Balance**, **Contrast**, **Subject** and **Look**. These labels describe responsibilities, not mandatory positions for every pipeline. A technical transform may sit elsewhere or be handled by RCM; a simple clip may need only two nodes; a complex shot may need branches and mixers. ![DaVinci Resolve Color page with Balance, Contrast, Subject and Look serial nodes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-node-workflow.webp) A short labeled chain is easy to debug. These names describe responsibilities, not a mandatory node recipe or a one-operation-per-node rule. To add a serial node, use **Color > Nodes > Add Serial**. Right-click a node and choose **Change Label** to name it. Before adding another node, ask one question: does this change need a separate order, isolation or bypass point? If not, the current node may be enough. Node order changes the image presented to downstream tools. A qualifier after a strong hue shift or saturation change samples different values than the same qualifier before that change. A LUT also sees whatever the upstream nodes give it. The [Color nodes guide](https://davinciresolveclub.com/davinci-resolve-nodes-explained/) explains serial, parallel, layer, Outside and Key Mixer behavior without imposing an artificial node count. ## Step 4: Correct Exposure and Color Balance Select the **Primaries Wheels** palette. Lift, Gamma and Gain aren't hard boxes for shadows, midtones and highlights; their tonal ranges overlap broadly. In practical terms: - **Lift** alters the black point and perceived shadow density. - **Gamma** redistributes much of the midrange between the black and white points. - **Gain** alters the white point and highlight level. - **Offset** moves the whole image more globally. Use small moves while watching the waveform and the picture. Set the black and white relationships the shot needs, then place the important midtones. A bright high-key interview should not be graded like a night exterior merely because both can be made to touch the same scope limits. For a visible color cast, first ask whether the scene contains something that should be neutral. Temperature and Tint can solve broad camera-balance errors; Offset or the color wheels can rebalance the image when you need different control. The RGB parade makes channel differences easier to see, but a blue sky and warm lamp naturally produce unequal traces. Sample context before chasing symmetry. ![DaVinci Resolve Primaries Wheels and Custom Curves controls for tonal correction](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-wheels-curves.webp) Lift, Gamma and Gain influence broad overlapping tonal ranges. Curves provide targeted shaping, but the picture and scopes, rather than a fashionable S-curve, decide how far to push it. Contrast and Pivot can shape the overall tonal relationship quickly. Custom Curves provide more targeted control: place points deliberately, keep an eye on smoothness, and avoid creating a kink just because an S-curve is fashionable. More contrast isn't automatically more cinematic. If faces become brittle, highlights flatten or shadows lose useful separation, back off and compare with the node bypassed. ## Step 5: Match the Sequence Before Building the Look Color grading isn't a collection of attractive still frames. Play the cut. Compare adjacent angles, coverage from different cameras and shots captured as the light changed. A polished close-up that jumps against the wide shot is still a failed sequence. Choose one representative reference shot for a scene. Correct it, then compare neighboring shots by switching between clips or using Gallery stills and split-screen tools. Match the large relationships first: exposure, black level, white balance, contrast and saturation. Save small skin or background refinements for later. Copying a grade is a starting point, not an automatic match. Camera exposure, lens, lighting and framing can make the same settings behave differently. The [copy color grades guide](https://davinciresolveclub.com/copy-color-grade-davinci-resolve/) covers stills, middle-click workflows and ways to keep shared looks separate from clip corrections. ## Step 6: Create the Look Without Losing the Correction Once the scene holds together, decide what the look is doing for the story. A useful creative change has a direction you can name: cooler shadows while keeping skin believable, softer highlight contrast, restrained saturation, a palette biased toward a production design color, or a cleaner commercial separation. Put the look in a node or group you can bypass. That comparison answers a better question than “does it look cinematic?”: does the look improve focus, mood and continuity without hiding technical problems? Play motion rather than judging only the most flattering frame. ### LUTs Need an Expected Input A LUT maps input values to output values. It does not inspect the camera, infer the scene or repair a wrong color-space tag. A technical camera LUT expects a particular input encoding; a creative LUT may expect an already normalized or specifically managed image. Place it only where the node receives that expected input. If RCM or a CST has already transformed the clip, adding another camera-to-Rec.709 LUT can create an accidental double transform. If a LUT clips or crushes data, upstream adjustment may change what enters it, but that isn't a reason to guess the order. Check the LUT documentation and the pipeline. The [Resolve LUT guide](https://davinciresolveclub.com/how-to-use-luts-in-davinci-resolve/) covers installation, node placement and blending in detail. ## Step 7: Use Qualifiers and Power Windows Only Where Needed Global tools are stable and fast. Reach for a secondary correction when one region needs different treatment: a face under mixed light, an oversaturated product color, a bright window pulling attention, or a background that should fall back. The **Qualifier** creates a key from sampled color values. Turn on Highlight view and inspect the matte rather than trusting the final picture alone. Use the Matte Finesse controls conservatively; a perfectly white face surrounded by crawling holes, hair contamination and noisy edges won't survive playback. A **Power Window** limits the correction spatially. Draw it larger and softer than the feature when possible so the adjustment blends into the shot. For a moving subject, open the **Tracker** palette in Window mode, start from a frame with reliable detail, and track forward and reverse as needed. ![DaVinci Resolve qualifier matte Power Window and Tracker workflow on a moving face](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/05-qualifier-window-tracker.webp) Inspect the matte, limit it with a soft window when useful, track from a reliable frame and then scrub the whole clip. One clean still frame does not validate the isolation. Then scrub the entire clip. Watch occlusions, motion blur, turns, reframing and objects crossing the window. For a correction at specific frames, switch the Tracker to Frame mode and adjust the window: those changes become keyframes. In Clip mode, moving the window offsets the whole tracked path instead. You can also retrack a failed section, but retracking replaces the existing data in that section. Check the surrounding frames after either repair. A secondary that looks clean on one still but flashes at frame 87 isn't finished. ## Step 8: Check Free vs Studio Without Blocking the Workflow The free edition includes the core beginner Color page workflow: nodes, primary wheels, curves, standard scopes, qualifiers, Power Windows, tracking, LUT support and Resolve Color Management. You can learn and complete a conventional SDR grade without buying Studio. Studio adds temporal and spatial noise reduction, Magic Mask, extra Resolve FX, HDR scopes with nit scales, and Dolby Vision/HDR10+ grading and rendering. Advanced Dolby Vision trim controls require a separate Dolby license, as the [official Studio feature overview](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) explains. Free Resolve already includes HDR grading tools; HDR is not an all-or-nothing paywall. Use the [Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) for feature-level decisions. If a tutorial relies on a Studio-only control, don't replace it blindly with a random LUT. Solve the underlying task: noise reduction may need cleaner acquisition or restrained temporal work elsewhere; an AI isolation may be replaceable with a qualifier and tracked window; a licensed HDR deliverable needs a correctly monitored HDR pipeline; making the image brighter alone does not create one. ## Step 9: Review and Export a Test Compare one node at a time with its correction enabled and bypassed, then restore it before checking the next node. Confirm each label still describes what changes. Before rendering, make sure the intended grade is enabled. Play the whole scene at normal speed. Check skin, neutrals, saturated colors, shadow detail, highlight roll-off and transitions between shots. Look for qualifiers that chatter and windows that reveal themselves. Verify the project's **Output color space** and the export settings for the destination. A render can appear different in another player because the display, player and metadata interpretation are part of the viewing chain; that doesn't justify changing random gamma tags until one application looks right. Render a short representative section and evaluate it in the intended delivery context. The [export guide](https://davinciresolveclub.com/export-video-davinci-resolve/) covers the Deliver page separately. ## A Repeatable Beginner Checklist - Identify source color space; don't grade around a wrong input tag. - Choose one deliberate managed or manual transform strategy. - Match the output color space to the delivery target. - Open waveform, RGB parade and vectorscope. - Correct exposure and broad balance before building the look. - Use labeled nodes only where order, isolation or bypassing benefits. - Match adjacent shots before polishing one frame. - Verify every LUT's expected input and output role. - Inspect qualifier mattes and track windows through the whole clip. - Review the sequence in motion and render a short delivery test. ## DaVinci Resolve Color Grading FAQ ### What is the difference between color correction and color grading? Color correction is the practical phase of making exposure, balance and shot-to-shot relationships coherent. Color grading includes the creative shaping of mood and palette. Resolve uses the same Color page tools for both, so the distinction is a workflow convention rather than a hard software boundary. ### Should I use Resolve Color Management or CST nodes? Both are valid. Resolve Color Management handles input, timeline and output transforms at the project pipeline level. CST nodes provide explicit transform placement in a manual node workflow. Choose one deliberate design, tag sources correctly, and avoid applying a second transform to media that's already normalized. ### Do I need to convert log footage to Rec.709 before grading? Not always. A color-managed project can transform log or RAW input into a chosen timeline working space and convert that grade to the output space later. A manual workflow can use CSTs or suitable technical LUTs. The important requirement is a known input, working and output path, not a universal Rec.709-first rule. ### What scopes should a beginner use in DaVinci Resolve? Start with the waveform for signal levels, RGB parade for channel balance and vectorscope for hue and saturation. Read them together with the image. Scopes measure the signal but do not know the intended lighting, mood or subject. ### Should every correction have its own node? No. One Corrector node can contain multiple operations. Separate nodes when order matters, when an adjustment needs its own isolation, or when independent bypassing and revision will make the grade easier to debug. ### Where should a LUT go in the node tree? Place a LUT where its expected input matches the image reaching that node. A camera technical LUT, a display transform and a creative LUT may require different positions. Don't add a camera-to-Rec.709 LUT after RCM or another transform has already normalized the clip. ### Is the skin-tone line a target for every face? No. Resolve describes it as a general guidepost for average skin-tone hue. Lighting, creative intent, makeup, reflections and the selected skin sample all affect the trace. Use the vectorscope as evidence, then judge the actual face and scene. ### Can I color grade in the free version of DaVinci Resolve? Yes. The free edition includes nodes, primaries, curves, standard scopes, qualifiers, Power Windows, tracking, LUTs, color management and HDR grading. Studio adds temporal and spatial noise reduction, Magic Mask, extra Resolve FX, HDR scopes with nit scales, and Dolby Vision/HDR10+ grading and rendering. Advanced Dolby Vision trim controls require a separate Dolby license. ### DaVinci Resolve Nodes Explained URL: https://davinciresolveclub.com/davinci-resolve-nodes-explained/ Last updated: 2026-09-12T17:55:02.000Z **Quick answer:** A Color page node is one processing container in a grade. Serial nodes run in sequence; Parallel nodes start from the same image state and mix equally; Layer Mixer inputs have overlap priority; Outside nodes invert an incoming key; Key Mixer combines keys; Splitter/Combiner separates RGB channels. Start with serial nodes, branch only when the way corrections interact requires it, and read the green image path separately from the blue key path. ## DaVinci Resolve Nodes: The Decision Map - **Serial:** one operation after another; the usual starting structure. - **Parallel:** several branches receive the same upstream image and mix with equal priority. - **Layer Mixer:** overlapping branches need priority or a composite mode. - **Outside:** reuse the inverse of an existing key or Power Window isolation. - **Key Mixer:** combine, subtract or intersect multiple keys before one downstream correction. - **Splitter/Combiner:** process red, green and blue channel branches separately. - **Compound:** nest a section of a large graph without changing its internal order. This page explains Color nodes. The complete correction workflow lives in [How to Color Grade in DaVinci Resolve](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/), and the [Color Grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/) organizes the wider learning path. Here the job is narrower: understand what the image and key signals do when you connect, reorder or mix nodes. ## What a Color Node Actually Contains A Corrector node can contain one or many Color page operations: primaries, curves, a qualifier, Power Windows, a LUT, Resolve FX and key controls. It receives an RGB image input, performs those adjustments in Resolve's internal order, and outputs a new image. The Node Editor turns the order between containers into a visible graph. Separating operations into nodes isn't a law. Blackmagic explicitly allows multiple adjustments in one node. Separate nodes are useful when they force a required order, isolate a volatile decision, or make later revisions easier. A practical convention is one clear purpose per labeled node, not because Resolve requires it, but because bypassing Balance, Skin Key or Look tells you immediately what changed. ## Read Green RGB Paths and Blue Key Paths Separately The green connections carry the image through the grade. Blue connections carry key data: the matte created by a qualifier, Power Window, Magic Mask or another isolation. A node can receive an image from one place and a key from another. That is why a Key Mixer isn't an image mixer, and why an Outside node needs both the RGB and key relationship to the source isolation. When a result makes no sense, trace one color at a time. First follow green from input to output and confirm the image order. Then follow blue and confirm which matte limits the selected node. Disable one node at a time; don't rebuild the graph until you know whether the unexpected result belongs to the image path, the key path or the mixing rule. ## Serial Nodes and Order of Operations Serial is the simplest and most common structure. Each node's RGB output becomes the next node's input, so node 03 never sees the untouched source, it sees the result of nodes 01 and 02\. That matters whenever a downstream tool samples image data. A qualifier placed after a strong desaturation, white-balance change or look transform is sampling a different image than the same qualifier placed before it. ![DaVinci Resolve Color page serial node signal flow from Balance to Sky Key and Look](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-serial-node-signal-flow.webp) A serial node receives the result of the node before it. The Sky Key is pulled from the image that reaches node 02, so changing the upstream balance can change that key. Use serial order deliberately. A balance can establish a neutral input for later work; a clean secondary can be pulled before a creative operation damages the separation it needs; an output trim can sit after the look. There's no universal seven-node recipe for every color-managed pipeline, so name the purpose rather than copying a diagram without its assumptions. ## How to Add and Label Color Nodes With a node selected, Color > Nodes exposes the same commands as the shortcuts. On macOS the manual uses Option; Windows layouts commonly present Alt for the equivalent modifier. Keyboard mappings are customizable, so the menu command is the authority if a shortcut has been changed. - **Add Serial after selected:** Option-S / Alt-S; Color > Nodes > Add Serial. - **Append Serial to the end:** Option-K / Alt-K; Color > Nodes > Append Node. - **Add before selected:** Shift-S; Color > Nodes > Add Before Current. - **Add Parallel:** Option-P / Alt-P; Color > Nodes > Add Parallel. - **Add Layer:** Option-L / Alt-L; Color > Nodes > Add Layer. - **Add Outside:** Option-O / Alt-O; Color > Nodes > Add Outside Node. - **Add Splitter/Combiner:** Option-Y / Alt-Y; Color > Nodes > Add Splitter/Combiner Nodes. To label a node, right-click it, choose Change Label, type the name and press Return. Resolve numbers nodes by creation order rather than by their current left-to-right position, so a newly inserted node may receive a higher number. A clear label prevents that numbering from becoming the only description of the grade. ## Parallel Mixer vs Layer Mixer A Parallel node normally receives the same upstream image as the selected branch. The branches feed a Parallel Mixer, which combines every input with equal processing priority regardless of vertical position. This is useful when several secondaries should start from the same image state. Their keys are independent of changes in sibling branches, but an adjustment before the shared input can still change all of them. A Layer Mixer looks similar but follows a priority rule: the lowest overlapping input has the greatest priority and can obscure adjustments above it. It also supports composite modes. Priority follows the input connection, not where you drag a Corrector on the canvas. Test it with two obvious overlapping Power Windows before using it on a subtle grade. ![DaVinci Resolve Parallel Mixer and Layer Mixer node graphs compared](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-parallel-vs-layer-mixer.webp) Parallel Mixer inputs share equal priority and blend overlaps; Layer Mixer inputs have priority, with the lowest overlapping input winning, and can use composite modes. Choose Parallel when equal-priority mixing from a shared source is the desired result. Choose Layer Mixer when an isolated correction must override another branch or when you need a composite mode. Right-click a Parallel Mixer and choose Morph Into Layer Mixer Node to convert it; on a Layer Mixer, use Morph Into Parallel Node. After converting, inspect every overlap: familiar wiring does not mean the result stayed the same. Equal priority does not lock every branch to full strength. Select a Corrector feeding either mixer, open the Key palette and lower Key Output Gain to reduce that branch’s contribution. Adjust the Corrector, not the mixer: Layer and Parallel Mixers have no Key-palette controls of their own. ## Outside Nodes and Key Mixer Select a node limited by a qualifier or Power Window, then use Color > Nodes > Add Outside Node. Resolve creates a Corrector after the selected node, connects the source image and key, and enables Key Input Invert. The new node therefore acts on the inverse region. If the original isolation changes, the Outside relationship follows that key; it isn't a separately drawn mask. Key Mixer solves a different problem. It accepts key outputs from multiple Correctors and creates one key output. Right-click the Node Editor background and choose Add Node > Key Mixer. Feed the source Correctors with the appropriate RGB image, connect their blue key outputs to the Key Mixer, then connect its blue output to the blue input of the Corrector you want to limit. The Key Mixer carries matte data, not the corrected RGB image. ![DaVinci Resolve Outside node with Key Input Invert and Key Mixer routing](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-outside-node-key-mixer.webp) An Outside node inverts the incoming key. A Key Mixer combines multiple blue key outputs and sends one composite key to a downstream Corrector. Use the illustration to follow the blue mask path, not as a complete wiring recipe. In Resolve, the destination Corrector also needs a separate green RGB input. Do not feed an RGB image into the Key Mixer or expect its blue output to replace the destination’s image connection. Try two overlapping window keys. Double-click the Key Mixer and open the Key palette to see Input Link 1 and Input Link 2\. The additive setup combines their selected areas. Turn on Key Input Matte for either input to keep only the intersection. To subtract the second key from the first, turn on both Key Input Matte and Key Input Invert for Input Link 2; use Input Link 1 instead to reverse the subtraction. Inspect the resulting matte before judging the correction. These are per-input controls, not an Add/Subtract/Intersect dropdown. ## Splitter/Combiner and Compound Nodes Color > Nodes > Add Splitter/Combiner Nodes creates a premade RGB structure. The Splitter sends red, green and blue through separate Corrector branches; the Combiner extracts those channels and rebuilds one RGB image. The structure is for channel-specific processing, such as alignment or a deliberate channel effect. It doesn't automatically split into YUV, HSL or Lab, and no channel should be assumed to be the noisy one without inspecting the actual footage. ![DaVinci Resolve Splitter and Combiner node graph routing red green and blue channel branches](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-splitter-combiner-v2.webp) Splitter/Combiner routes the red, green and blue channels through separate branches, then rebuilds one RGB image. Compound nodes are organizational containers, not channel mixers. Select nodes, right-click one and choose Create Compound Node. Double-click the compound or choose Show Compound Node to edit inside it; Decompose Compound Node returns its contents to the parent graph. Adjustments made on the compound itself run after its internal nodes and are lost when you decompose it. If you need to keep that finishing adjustment, copy it before decomposing and paste it onto a new serial node after the former contents. ## A Beginner Node Tree You Can Actually Debug Start with a short serial chain and add complexity only when the image asks for it. The following names describe responsibilities, not mandatory positions in every color-management setup: - **Balance:** exposure and neutral starting decisions. - **Contrast:** tone-shape work you may need to bypass separately. - **Subject key:** qualifier or window for the person or product. - **Background:** a separate environment correction when needed. - **Look:** creative treatment or a deliberately placed LUT. - **Output trim:** a final adjustment only when the pipeline calls for one. Where a LUT belongs depends on what it expects as input and what should happen before or after it. The dedicated [LUT workflow guide](https://davinciresolveclub.com/how-to-use-luts-in-davinci-resolve/) covers that boundary. The test here's simple: bypass one labeled node. If the result changes in more ways than its name promises, either rename it honestly or separate the responsibilities. ## Three Tests That Make Node Behavior Visible ### 1\. Prove serial order with a qualifier In node 01, make an obvious saturation change. In node 02, qualify one color and view the key highlight. Swap the nodes and inspect the matte again. The second position samples the result of the first, so the key can change even though its qualifier controls did not. Return the nodes to the useful order and label both. ### 2\. Prove mixer behavior with overlapping windows Create two branches from the same input, give each a large overlapping Power Window and apply unmistakably different tints. Compare a Parallel Mixer with a Layer Mixer. Parallel combines the overlaps with equal priority. In Layer Mixer, reconnect the branches to different inputs and watch the lowest overlapping input take priority. This is safer than learning the rule on a subtle skin correction. ### 3\. Prove key routing without changing RGB Create two window keys, send their blue outputs to a Key Mixer, and connect the mixed blue output to a third Corrector. Keep the Correctors connected to the RGB image path and give only the third one an exposure change. In the Key Mixer’s Key palette, compare the additive setup with Matte enabled on one input, then enable Invert on that same input for subtraction. The corrected image changes because its limiting matte changed; the Key Mixer itself never became an RGB image branch. ## How Many Nodes Do You Need? Resolve doesn't impose a node-count limit. The current manual notes that excellent work may use only three or four nodes, while other grades use ten to twenty or more. Neither range is a target. Footage, schedule, deliverables, reuse and revision needs determine the tree. Use as many nodes as the grade needs, no more and no fewer. A large graph isn't automatically advanced, and a small graph isn't automatically clean. Prefer visible signal flow, purposeful labels and a predictable bypass test. Use Compound nodes when a section is logically complete, not because the screen crossed an arbitrary node count. ## Resolve 21 Layer List Is a View, Not a New Processing Model Resolve 21 introduced Layer List as another view of the node graph. In the current 21.1 interface, its button is at the upper right of the node graph, beside the three-dot menu. The list displays the existing node order as a stack: Node 1 is bottom-most and later or rearranged nodes appear above it. It exposes preview thumbnails, tool icons and controls to enable, disable, lock, add or remove nodes. ![DaVinci Resolve 21 Graph View and Layer List View showing the same six Color nodes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/05-layer-list-view.webp) Layer List is a second view of the same Color node order. Node 1 sits at the bottom of the list; the underlying graph and processing order remain node-based. Layer List doesn't replace Graph View and it isn't the same thing as a Layer Mixer. Graph View shows the wiring; Layer List offers a compact management view of that graph; Layer Mixer is a node with a specific priority and compositing behavior. The original [Resolve 21 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) documents the interface addition, while the [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) remains the detailed source for node processing. The same Color node logic also applies to stills on the [Resolve 21 Photo page](https://davinciresolveclub.com/davinci-resolve-21-photo-page/). For the other changes in this release, see [What's New in DaVinci Resolve 21](https://davinciresolveclub.com/davinci-resolve-21-whats-new/). ## Color Nodes vs Fusion Nodes Both pages use connected nodes, but the node types are not interchangeable. Color nodes organize grading, keys, windows, LUTs and Color-page effects around a clip's grade. Fusion nodes build image-processing and compositing flows with MediaIn, Merge, masks, transforms, generators and MediaOut. The shared skill is reading connections; the tools, data flow and page behavior differ. If the task is a title, green-screen composite, tracked graphic or particle effect, use the [Fusion beginner tutorial](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/). Blackmagic describes nodes as the building blocks of Color correction on its current [Color page product overview](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com). The practical rule is even simpler: trace the image, trace the key, identify the mix rule, then change one connection at a time. ## DaVinci Resolve Nodes FAQ ### What is a node in DaVinci Resolve? A Color-page node is one part of a grade’s processing graph. A Corrector receives an image and applies adjustments; mixers combine images or keys, depending on their type. The connections determine processing order and branching. ### What is the difference between serial and parallel nodes? Serial nodes run one after another, so every downstream node sees the previous node's result. Parallel nodes normally read the same upstream image and feed a Parallel Mixer, which combines their adjustments with equal priority. Use serial for a deliberate sequence and parallel when multiple adjustments should start from the same image state. ### What is the difference between Parallel Mixer and Layer Mixer nodes? A Parallel Mixer combines input corrections with equal priority regardless of vertical position; Key Output Gain on each feeding Corrector can adjust its strength. A Layer Mixer gives priority to the lowest overlapping input and also supports composite modes. Use Layer Mixer when overlap priority or compositing is part of the intended result. ### What does an Outside node do in DaVinci Resolve? An Outside node is a Corrector with Key Input Invert enabled. When added from a node limited by a qualifier or Power Window, it receives the selected node's image and key paths and applies its adjustment to the inverse region. ### What is a Key Mixer used for? A Key Mixer combines key outputs from multiple Corrector nodes into one key. Select it and open the Key palette: per-input Matte and Invert controls let you intersect or subtract keys instead of adding them. Connect its blue output to the downstream Corrector’s blue key input. It mixes matte data, not RGB images. ### What does a Splitter/Combiner node do? Splitter/Combiner separates an RGB image into red, green and blue branches, lets you process those channel branches, and recombines them into one RGB image. Add the premade structure with Color > Nodes > Add Splitter/Combiner Nodes. ### What is a Compound node? A Compound node nests selected nodes inside one container to make a complicated graph easier to navigate. You can open it to edit the internal nodes, label it, nest compounds, or decompose it later. Adjustments made on the compound itself occur after its internal nodes. ### How many Color nodes should I use? There's no fixed number and Resolve doesn't impose a node-count limit. Use as many as the grade needs, then stop. A few well-labeled nodes can solve a clean shot; a difficult shot or reusable template may need many more. Readability and predictable order matter more than the count. ### How do I rename a node in DaVinci Resolve? Right-click the node, choose Change Label, enter the label and press Return. Labels such as Balance, Skin Key and Look communicate purpose more clearly than default node numbers. ### Did DaVinci Resolve 21 replace nodes with layers? No. Resolve 21 added Layer List as another way to view and manage the existing Color node graph. It shows nodes as a bottom-to-top list with previews and controls, but it doesn't replace Graph View or turn the grade into a different layer-based processing model. ### DaVinci Resolve Slow Playback URL: https://davinciresolveclub.com/davinci-resolve-slow-playback/ Last updated: 2026-09-12T09:46:48.000Z ## Start With One Repeatable Playback Test A laggy timeline feels random when every test uses a different clip or playhead position. Make the problem repeatable before touching preferences: choose a range that fails consistently, note the timeline frame rate, and keep the Viewer open so you can see the FPS readout. In Resolve 21, a green GPU status indicator means the current playback has processing headroom; red means it is running below real time. That indicator is a result, not a diagnosis. If the symptom turns out to be offline media, GPU memory, audio or export failure, use the [DaVinci Resolve troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/); this page stays focused on measurable real-time playback. 1. **Loop the same 10–20 seconds.** Use a section that contains the problem, not a random clean clip. 2. **Write down the symptom.** Does the entire range run slowly, does it skip frames, or does audio remain steady while the picture jumps? 3. **Record the exact source.** Codec, resolution, frame rate, bit depth and camera or screen-recording origin matter more than the file extension. 4. **Change one variable.** Replay immediately and keep every other setting unchanged. 5. **Keep only proven changes.** If the result is identical, return that control to its previous value before the next test. ![DaVinci Resolve viewer FPS status showing green real-time and red slow playback indicators](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-fps-status.webp) Use the viewer FPS indicator as a repeatable result, not a complete diagnosis: green shows playback headroom; red shows that the current range is below real time. The Viewer option Show All Video Frames helps separate two playback behaviors. With it off, Resolve prioritizes audio and can drop video frames when processing falls behind. With it on, Resolve presents every video frame sequentially, so playback may become slower than real time and audio can suffer. It's a diagnostic choice, not a performance boost. ## Slow Playback, Dropped Frames and Scrubbing Are Not the Same Continuous slow playback means Resolve can't finish the current workload at the timeline rate. Intermittent skipped frames can appear when audio is being prioritized. Choppy scrubbing is less useful evidence because scrubbing asks for non-sequential frames and may expose source-decoding or storage latency differently from normal playback. A clip that's smooth until a title, grade or Fusion composition begins points toward timeline processing; the same camera clip failing even in a clean timeline points toward source decoding or media access. If audio alone is missing, distorted or routed incorrectly, use the separate [DaVinci Resolve no-audio guide](https://davinciresolveclub.com/davinci-resolve-no-audio/) instead of rebuilding video cache. If the Viewer shows [Media Offline](https://davinciresolveclub.com/media-offline-davinci-resolve/), follow that diagnostic: missing files, storage access and decoding failures need different checks. Do not assume every offline frame means a file needs relinking. If the FPS display stays at the timeline rate but motion still looks uneven, render a short sample and compare it in another player. Check the source and timeline frame rates, plus any retiming. Repeated or interpolated frames can look choppy even when Resolve delivers every timeline frame; that needs a different test from below-real-time processing. ## Try Timeline Proxy Resolution Before Generating Files Choose Playback > Timeline Proxy Resolution > Half Resolution and replay the marked range. If the result is still below real time, try Quarter Resolution. Choose None to return to the current timeline working resolution. Resolve 21 treats this as an on-the-fly working-resolution control that's independent of Proxy Media. It doesn't replace your source files and it doesn't lower final delivered quality. ![DaVinci Resolve Timeline Proxy Resolution menu with None, Half and Quarter options](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-timeline-proxy-resolution.webp) Replay the same difficult range at Half and Quarter Resolution. A clear improvement means the working-resolution load matters; the setting does not lower final export quality. A large improvement at Half or Quarter Resolution is strong evidence that image processing at the current working resolution matters. It doesn't prove that the GPU is defective. Scaling, noise reduction, optical-flow retiming, Fusion, OFX and several color operations can all change the workload. For critical focus, texture or artifact decisions, switch back to None and inspect representative frames at full working resolution. Performance Mode is a second non-destructive working control under Preferences > User > Playback Settings. Automatic is the default. It can optimize sizing, decode quality and image processing for interactivity without reducing delivered output quality, although the computer-monitor preview may look different. Leave it on Automatic first; a manual combination is useful only when you know which preview tradeoff you're testing. ## If Only Certain Source Clips Lag, Test the Codec H.264 and H.265 are common suspects because many camera and phone variants use long-GOP compression, but the codec name alone isn't enough. Profile, bit depth, chroma sampling, frame rate, operating system and available hardware decoding all affect performance. Don't assume that an H.265 file is GPU-decoded, that Quick Sync removes the workload from every other component, or that Studio automatically supports every combination. Create proxy or optimized media for two or three representative clips, attach or enable it, and replay the same timeline range. If playback becomes reliable, the source-media workflow matters. That test alone does not isolate decoding: the generated file may also have a different resolution, bitrate or storage location. Keep effects and timeline settings unchanged, and note those file differences. If nothing changes, stop transcoding the whole project and isolate timeline effects or cache instead. For license-sensitive codec details, check the current [Resolve support documents](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) for your operating system and compare the exact media properties. The maintained [Free vs. Studio guide](https://davinciresolveclub.com/davinci-resolve-vs-studio/) explains the broader license boundary without pretending that one edition fixes every slow timeline. For supported camera RAW formats, reducing project decode quality can improve work playback; enable the Deliver option that forces highest-quality debayer when the workflow requires it. For a phone or screen recording, inspect [MediaInfo’s Frame rate mode](https://mediaarea.net/en/MediaInfo/Support/Fields?ref=davinciresolveclub.com) rather than guessing from the device. If the clip is variable frame rate and has jitter or audio drift, test a constant-frame-rate transcode of one sample. In HandBrake, choose a suitable frame rate and [Constant Framerate](https://handbrake.fr/docs/en/latest/technical/frame-rates.html?ref=davinciresolveclub.com); Same as Source with VFR preserves variable timing, and Peak Framerate is not the same as CFR. Keep the original and check duration, sync and color before converting the rest. A successful timing fix does not prove the new codec will be easy to decode. ## Proxy Media vs. Optimized Media: Choose by Job Both workflows make source media easier to play, but they solve different operational needs. Proxy Media creates portable, user-managed files that can move between machines and be relinked. Optimized Media is managed by Resolve for the current system and is convenient when the project stays on one workstation. Neither is the same as Timeline Proxy Resolution, which changes working resolution on the fly without generating media. Use the complete [DaVinci Resolve Proxy Workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) when you need to choose formats, attach existing proxies, hand media to another editor or reconnect originals. On this troubleshooting page, the useful move is smaller: generate one controlled batch, enable Playback > Use Optimized Media if Available or prefer the attached proxies, and compare the same failing range. ![DaVinci Resolve Project Settings for optimized media, render cache and cache file location](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-optimized-media-settings.webp) Set working-media resolution and format deliberately, then confirm that the cache location has enough free space for generated media. Project Settings > Master Settings controls the generated resolution and format. Pick a processor-friendly option available on your platform that preserves the quality your current task needs; there's no honest rule that ProRes belongs only on macOS or DNxHR only on Windows. Optimized media shares the cache-files directory. Confirm Cache files location and free space before generating hours of material. A small test batch is cheaper than discovering a full or slow destination after the entire project has been processed. Before final delivery, check Advanced Settings on the Deliver page. Use proxy media, Use optimized media and Use render cached images can make the export use those generated files. Leave them off when they are lower quality than the required master, and make sure the originals are online. This is separate from Timeline Proxy Resolution, which only reduces the working preview. ## Use Render Cache for Expensive Timeline Processing Render Cache helps when the timeline result, not merely the source file, requires too much work for real-time playback. Choose Playback > Render Cache > Smart for automatic decisions, User when you want to mark specific clips or outputs, and Off for a clean comparison. Smart and User aren't identical: User is primarily manual, with project settings that can allow selected automatic behaviors. Cache can build during playback or after the configured inactivity delay. The indicators sit along the bottom of the Timeline Ruler: red means the range is marked to be cached; blue means it has been cached. Wait until the problem range is blue, then replay exactly that range. If blue playback is smooth, pre-rendering that processing helps. If it's still slow, the cache file, its storage path or another system constraint may be involved. ![DaVinci Resolve timeline with red to-be-cached and blue cached render bars](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-render-cache-indicators.webp) Cache indicators run along the bottom of the Timeline Ruler: red still needs caching, while blue has been cached. Wait for blue, then replay the identical range. Don't delete all cache as a ritual. First confirm that cached playback behaves differently from the original. If a previously reliable cached range is now wrong, Playback > Delete Render Cache lets you remove and rebuild cache. Check available capacity and the cache format before regenerating. A cache format that's easy to decode can demand substantial sustained writes and space; a highly compressed format may trade storage for more processing. Also check whether Resolve is still generating proxies, transcribing or running a background render. If you enabled those jobs, let them finish or pause them, then repeat the same playback test. Studio’s background-render options include Pause background renders on foreground activity under Preferences > System > Background Tasks. Background rendering is disabled by default and has higher hardware requirements; enabling it is not a playback-speed fix. These background jobs are separate from the Smart/User Render Cache modes above. ## Isolate Fusion, OFX and Color Work When the clean source plays correctly but the range fails as soon as an effect begins, stop changing codec preferences. Temporarily bypass color grades and Fusion effects, then replay. If performance returns, re-enable the stack in stages. Noise reduction, optical-flow retiming, motion blur, demanding Resolve FX and complex Fusion compositions are common examples of work that should be measured at the actual timeline resolution rather than guessed from hardware model names. For a Fusion composition, cache its output or mark the relevant clip for cache instead of transcoding every source file. The [Fusion beginner guide](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) covers node-level troubleshooting. Once a heavy clip is genuinely locked, Render in Place can create new media that replaces that timeline instance. Decompose to Original restores the original editable clip, but it doesn't delete the rendered file, so keep storage and cleanup in mind. ## Check GPU Preferences Without Creating a New Problem Open Preferences > System > Memory and GPU. Most users should begin with GPU processing mode and GPU selection on Auto. If you have a specific reason to test manual mode, Resolve 21 documents Metal for macOS, OpenCL for AMD on Windows or Linux, and CUDA for Nvidia on Windows or Linux. Correct drivers still matter, but a generic instruction to force one mode or install a particular driver branch isn't a diagnosis. ![DaVinci Resolve Memory and GPU preferences with processing mode and GPU selection on Auto](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/05-gpu-preferences.webp) Start with GPU processing and selection on Auto. If you test a manual API or device selection, change one setting and replay the same range before drawing a conclusion. System monitors are clues, not verdicts. High CPU usage can accompany software decoding, high GPU usage can accompany effects or image processing, and low percentages can still hide a single saturated engine, memory pressure or waiting on storage. Change one Resolve control, replay the same range, and compare FPS and behavior. If Auto works, keep it. If a manual setting makes no measurable improvement, revert it. ## Storage, Power and Thermals: Test Conditions, Not Myths Resolve can read source media while writing cache, optimized media, waveforms and thumbnails. A nearly full destination, an unstable external connection or competing work on the same volume can make playback inconsistent. There's no universal SATA, NVMe or megabytes-per-second threshold for “6K editing”: the real requirement depends on codec data rate, stream count, cache format and concurrent effects. Measure sustained behavior with the exact project rather than shopping from one headline number. On a laptop, connect the intended power source, use a performance-appropriate operating-system mode, and test after the machine reaches a steady temperature. Thermal or power limits can change during a long session even when Resolve settings stay the same. Close unrelated heavy processes for the comparison, but don't claim that one Windows or macOS power setting is a universal fix. If the controlled tests still fail, compare the workload with the current [DaVinci Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). For export-only stalls or error codes, move to the [Render Failed guide](https://davinciresolveclub.com/davinci-resolve-render-failed/). Media, GPU-memory, startup and audio failures need their own diagnosis rather than more playback settings. ## Read the Test Result Before Choosing a Permanent Fix The winning test should determine the workflow. If Half or Quarter Timeline Proxy Resolution restores playback while the original source and effect stack stay unchanged, keep the lower working resolution while editing and return to None for full-resolution inspection. If only proxy or optimized media helps, build a source-media workflow for the affected codec. If bypassing effects helps but easier source media doesn't, cache or simplify the expensive timeline processing instead of transcoding the whole library. A blue cache bar that plays smoothly is evidence for caching that range; a blue range that still fails means the investigation must continue. Check the generated file location, space and system state before assuming the cache feature is broken. If none of the Resolve controls changes the result, reproduce the test in a new clean timeline with one representative clip. That separates project-specific processing from system-wide decoding or [hardware limits](https://davinciresolveclub.com/davinci-resolve-hardware-compatibility/) without destroying the original project. Keep a short record: source properties, timeline settings, active effects, FPS before and after, cache state and the single variable changed. That note is more useful than a screenshot of overall CPU or GPU percentage. It also gives support staff or another editor a reproducible case instead of a vague report that Resolve is laggy. ## The Ordered Slow-Playback Checklist 1. **Reproduce:** loop one failing 10–20 second range and record the Viewer FPS/status. 2. **Working resolution:** test Half, then Quarter Timeline Proxy Resolution; return to None for critical full-resolution inspection. 3. **Effects:** bypass color and Fusion/OFX work; re-enable the stack in stages. 4. **Source decode:** create proxy or optimized media for a few representative clips, not the whole library. 5. **Cache:** compare Off with Smart or a deliberately marked User-cache range; wait for blue before judging. 6. **Storage:** verify cache location, free space, connection stability and competing reads/writes. 7. **GPU:** start on Auto; test a manual processing API only when platform and driver support justify it. 8. **System state:** repeat under stable power and temperature with unrelated heavy processes closed. 9. **Upgrade decision:** change hardware or license only after the evidence identifies a persistent resource or capability limit. The [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) describes the playback controls and cache behavior used here. Keep the settings that measurably help your difficult range, then verify final output quality before committing to the workflow. ## DaVinci Resolve Slow Playback FAQ ### Why is DaVinci Resolve playback so slow? Slow playback can come from source decoding, timeline resolution, effects, cache generation, storage or the computer's power and thermal state. Replay one short failing range and change one variable at a time. Timeline Proxy Resolution tests working-resolution load; proxy or optimized media tests source-media load; bypassing effects and waiting for a blue cache bar tests timeline processing. ### What is the fastest safe setting to try for choppy playback? Choose Playback > Timeline Proxy Resolution > Half Resolution, then replay the same range. If it still misses real time, try Quarter Resolution. This changes the working preview resolution, not the source media or delivered export quality. ### What do the red and blue cache bars mean in DaVinci Resolve? The cache indicators appear along the bottom of the Timeline Ruler. Red means that section is marked to be cached; blue means the cache has been created. A blue bar doesn't guarantee every storage or system problem is solved, so judge it by replaying the same range. ### Should I use Proxy Media or Optimized Media for slow playback? Both can replace difficult source media with easier working files. Proxy Media is portable and suited to relinking or collaboration. Optimized Media is managed inside Resolve for the current system. Use the dedicated proxy workflow when files must move between machines; use a short optimized-media test to check whether easier source media helps. A change in resolution or storage location can also affect that result. ### Why is H.264 or H.265 footage choppy in DaVinci Resolve? Long-GOP H.264 and H.265 footage can be demanding to decode, but performance depends on the exact profile, bit depth, chroma sampling, operating system and available hardware decoding. Generate proxy or optimized media for a few representative clips and replay the same range before blaming the GPU or buying Studio. ### Does Render Cache always improve playback? No. Render Cache helps when Resolve can pre-render expensive source, color, Fusion or timeline processing, but it also needs time, storage space and a suitable cache location. Compare Off, Smart or a deliberately marked User-cache range instead of enabling every cache option at once. ### Will DaVinci Resolve Studio automatically fix slow playback? No. Studio can change some codec and GPU capabilities, but it can't repair a full cache drive, thermal throttling, an unsuitable power mode or a poorly chosen workflow. Identify the bottleneck first and check the current codec and system requirements before treating a license upgrade as a performance fix. ### When should I upgrade hardware for DaVinci Resolve? Upgrade when testing identifies a hardware limit in the work you actually need to do. If bypassing a required effect restores real-time playback, that is useful evidence, not a reason to rule out an upgrade. Record the source codec, timeline resolution, required effects and FPS, then compare suitable hardware against that workload. Rule out avoidable storage, power and workflow problems before spending money. ### DaVinci Resolve 21 AI Tools: Free vs Studio Breakdown URL: https://davinciresolveclub.com/davinci-resolve-21-ai-tools/ Last updated: 2026-09-12T16:49:05.000Z DaVinci Resolve 21 adds nine headline AI tools for media search, generated speech, synthetic focus, face work, slate metadata, sharpening and motion deblur. All nine require Studio. This guide explains what each tool does, what to install first and what to check before trusting the result. **Quick answer:** Resolve Studio is worth buying for AI only when one named tool removes a repeated bottleneck in your work. IntelliSearch can shorten logging, Speech Generator can produce licensed or permitted narration, and CineFocus or the face tools can reduce setup time. None of them removes the need to inspect the full clip, confirm consent and preserve the original. ## The Nine New Resolve 21 AI Tools Resolve 21 reached final release on June 3, 2026\. As of September 12, Blackmagic lists 21.1 build 14 as the current stable desktop release, dated September 8\. Check the [official Resolve support page](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) before following a beta-era tutorial: menu behavior and fixes can change between updates. This list covers the nine headline AI additions in Resolve 21, not every older Neural Engine feature. Magic Mask, Speed Warp and Voice Isolation are established tools. Studio 21.1 also adds a native MCP server for connecting AI assistants; that is an automation feature, separate from the image and audio tools below. - IntelliSearch: finds visual content after analysis, with separate searches for transcripts and existing metadata. - Speech Generator: creates a new spoken audio clip from text with a built-in or permitted custom voice. - CineFocus: builds a synthetic depth treatment for defocus, bokeh and animated focus changes. - Face Age Transformer: ages or de-ages a tracked face. - Face Reshaper: changes facial proportions after face detection and tracking. - Blemish Removal: targets facial and skin blemishes while retaining manual control over the result. - Slate ID: finds clapperboards and extracts slate information into clip metadata. - UltraSharpen: applies selective AI sharpening with a single amount control. - Motion DeBlur: renders new media intended to reduce motion-blur softness while preserving the original source. ## Are Resolve 21 AI Tools Free or Studio-Only? All nine tools above are Studio-only in the current [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com). The license headings explicitly cover IntelliSearch, Speech Generator, CineFocus, Face Age Transformer, Face Reshaper, Blemish Removal, Slate Finder and Slate ID, UltraSharpen and Motion DeBlur. A missing or greyed-out control is not evidence that a different Free build will unlock it. The core editor, Color, Fusion, Fairlight and the core Photo page remain useful in Resolve Free. The current US [DaVinci Resolve product page](https://www.blackmagicdesign.com/products/davinciresolve/?ref=davinciresolveclub.com) lists Studio at $295 as a one-time desktop license; organization rental and iPad licensing are separate paths. Use the complete [Resolve Free vs. Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) for output ceilings, codecs and non-AI differences. Don't buy Studio because a long feature list sounds impressive. Write down the recurring job, the media it affects, the current workaround and a pass/fail test. If the new tool doesn't save a measurable step or improve a deliverable on representative media, it isn't yet an upgrade reason. ## IntelliSearch: Analyze First, Then Search For visual searches, first open DaVinci Resolve > Extras Download Manager and install the Faster model, the Better model or both. Choose the installed mode in the Media Pool three-dot menu under IntelliSearch Mode. Select a small set of clips, open AI Clip Analysis and change its scope dropdown to selected clips—the default is all clips in the Media Pool. Enable Analyze for IntelliSearch, then click Analyze. Faster and Better refer to analysis tradeoffs. Both search quickly after analysis; Better uses a larger model, takes longer to analyze and is intended to return more accurate results. Starting with Faster on a sample bin is safer than analyzing an entire library before you know whether the queries fit your footage. - Use Search Visual Only for analyzed objects, people, colors and other visible content. Search Transcript Only looks through transcribed audio. Metadata Search reads filenames, timecode, keywords and other existing fields; those fields do not need visual analysis. Search All combines available analyses and entered metadata. Search In lets you restrict the results to selected bins. For visual or transcript matches, Full Clips returns the complete clip and Segments narrows it to the matching portion. Add as SmartBin saves the criteria in a dynamic bin. Enable Identify faces during analysis if you want to search for particular people. Then review the Face Gallery and correct names or grouping mistakes in Manage Faces. A plausible thumbnail is not enough: open the complete result and confirm the subject, context and usable duration. ![DaVinci Resolve 21 IntelliSearch UI with query, selected bin scope and matching clip](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-intellisearch-ui.webp) Analyze the media first, search inside the intended bins, then open the complete match instead of trusting one thumbnail. ## Speech Generator: Text to a New Audio Clip Open Timeline > AI Tools > Speech Generator after installing its model through Extras Download Manager. Enter a short sentence or paragraph, choose one of the four built-in licensed voices or a permitted custom voice, adjust speed, variation, pitch and Generation ID, then generate the audio into the Media Pool. It can also insert the result at the playhead on a chosen audio track. Generation ID behaves like a repeatable take: the same number preserves the same performance while other settings change. Punctuation affects timing, and the manual recommends shorter sentences or paragraphs. Break a long narration into manageable passages rather than treating one generation as a finished voiceover. Use a clean WAV recording for a custom voice. [Published hands-on tests](https://digitalproduction.com/2026/08/17/hearing-voices-what-can-ai-in-davinci-resolve-21-do-for-you/?ref=davinciresolveclub.com) have found WAV-only import restrictions, so do not assume an MP3 or AIFF sample will be accepted. The 21.1 manual asks for about 20 seconds of high-fidelity audio and says longer recordings are truncated to the first 20 seconds. Obtain permission and fairly compensate real voice talent before using their voice. Speech Generator is different from Voice Convert. Speech Generator creates a performance from written text; Voice Convert follows an existing audio performance with another analyzed voice model. For dialogue-to-text rather than text-to-speech, use the separate [Resolve 21 transcription guide](https://davinciresolveclub.com/transcribe-audio-davinci-resolve/). ![DaVinci Resolve 21 Speech Generator controls with text, voice settings and generated audio clip](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-speech-generator-ui.webp) Keep the input short, choose a licensed or permitted voice, adjust the performance controls and review the new Media Pool clip. ## CineFocus: Synthetic Depth and Bokeh CineFocus is a Studio Resolve FX tool that creates a virtual lens treatment from a 2D image. Add it to a Color-page node, let it generate the depth representation, choose a focus region, then adjust depth of field, aperture and bokeh. The focus value can be keyframed for an artificial rack focus. Version 21.1 adds More Natural Effect and Higher Precision options. Higher Precision costs performance; More Natural Effect can be faster or slower depending on the shot and hardware. It can't recover optical depth data the camera never recorded. Hair, transparent objects, foliage, overlapping limbs and fast motion are the places to inspect. Review a still frame for the mask edge, then play the complete shot at delivery resolution for pulsing or changing blur. Keep the effect on its own node so it can be bypassed or adjusted without disturbing the base grade. ![DaVinci Resolve 21 CineFocus controls with focus point, focus distance and before-after view](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-cinefocus-ui.webp) CineFocus builds synthetic depth from the image. Set the intended focus, then play the shot to inspect edges and changing blur. ## Face Age Transformer, Face Reshaper and Blemish Removal These are three different jobs, not one beauty filter. Face Age Transformer changes age-related attributes while following head position. Face Reshaper detects and tracks a face before adjusting proportions such as face, eyes, nose, mouth and eyebrows. Blemish Removal targets marks and texture problems rather than restructuring the face. Use small changes and review motion across the shot. A hero frame alone cannot reveal every tracking or continuity problem. The manual itself warns that Face Reshaper works best with subtle adjustments because viewers are sensitive to facial proportions. Correct a lost track manually, compare against the original, and check skin texture, eye and mouth movement, occlusions and shot-to-shot continuity. Approval and consent matter here too. A technically clean alteration can still misrepresent a person or violate a production agreement. Keep the original clip, effect settings, approved result and the relevant sign-off together. ![DaVinci Resolve 21 Face Reshaper tracking overlay and before-after face comparison](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-face-reshaper-ui.webp) Face Reshaper depends on a stable track. Review the complete shot and keep changes restrained enough to preserve natural motion. ## Slate ID, UltraSharpen and Motion DeBlur Download the Slate ID model through Extras Download Manager. In the Media Pool, select clips and right-click AI Tools > Analyze for Slate, or use Analyze for Slate in AI Clip Analysis with the selected-clips scope. Slate Finder marks the detected slate range; it does not finish the metadata job. Open the Slate ID icon in the Metadata pane, review the extracted fields, select the ones to keep and click Save. Verify scene, take, camera and date values before using them for bins or conform decisions. The [Slate Finder and Slate ID guide](https://davinciresolveclub.com/davinci-resolve-slate-finder-slate-id/) walks through both stages. UltraSharpen is a selective sharpening Resolve FX with one Sharpen Amount control. It may improve slightly soft material or low-resolution detail, but stronger is not automatically better. Inspect hair, text, high-contrast edges, noise and skin at the actual delivery size for halos or invented-looking texture. Motion DeBlur is separate. Install its model, select the source clips in the Media Pool and right-click AI Tools > Remove Motion Blur. Choose the output settings and render the new media; Resolve keeps the originals. Compare the result against the source for doubled edges, texture changes and motion artifacts. Severe blur or rapid motion may still be beyond repair. ![DaVinci Resolve 21 AI Clip Analysis with Analyze for Slate and extracted slate metadata](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/05-slate-id-ui.webp) Enable slate analysis and run it on selected clips, but verify every extracted field before using it for organization or conform. ## AI Tools on the Resolve 21 Photo Page The Photo page can use Resolve’s Studio AI and Resolve FX tools on stills; it doesn't create a separate free AI tier. IntelliSearch remains Studio-only, as do Magic Mask, CineFocus, Depth Map, Blemish Removal and UltraSharpen. The core Photo workflow for imports, albums, culling, RAW adjustments and Color-page nodes remains available in Free within Free’s documented output limits. For importing stills, moving albums into Color, Lightroom migration limits and Studio-only tethering, use the [Resolve 21 Photo page walkthrough](https://davinciresolveclub.com/davinci-resolve-21-photo-page/). ## Hardware and Performance: Test the Exact Workload There is no single performance prediction for all nine tools. Resolution, codec, clip duration, node complexity, operating system, GPU memory and background work all matter. In 21.1, AI tools can use proxy media when originals are offline if Always use full resolution media for AI Tools is disabled. Check which media is being analyzed; a proxy-based result is not a substitute for reviewing the final-resolution output. Use representative media before buying hardware: one long interview bin for IntelliSearch, one difficult moving edge for CineFocus, one tracked close-up for face tools and one genuinely blurred shot for Motion DeBlur. Record analysis time, cache or render time, memory pressure, stability and whether the delivered image actually passes review. The [Studio 21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) specify at least 16 GB of VRAM for advanced AI tools on Windows x86 and Linux, and at least 16 GB of system memory on Apple Silicon Macs. Windows ARM and background rendering have separate requirements. These are published requirements, not a promise of smooth playback or a claim that every smaller GPU will crash. Check your platform in the [Resolve 21 system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) before buying hardware. ## When Studio Is Worth Buying for AI - Buy for IntelliSearch when logging large documentary, archive or interview libraries is a repeated cost. - Buy for Speech Generator when permitted in-app narration replaces a real round trip and the consent workflow is defined. - Buy for CineFocus or face tools only after a difficult representative shot passes motion and artifact review. - Buy for Slate ID when slate metadata is common enough that verified automated extraction materially shortens ingest. - Don't buy for a hypothetical future use, a single marketing demo or a tool your current hardware cannot run reliably. AI is one part of Resolve 21\. The [DaVinci Resolve tutorial hub](https://davinciresolveclub.com/davinci-resolve-tutorial/) maps the wider learning path; for the Photo page, Edit, Color, Fusion and Fairlight changes plus the safe-upgrade sequence, see [what’s new in DaVinci Resolve 21](https://davinciresolveclub.com/davinci-resolve-21-whats-new/). ## DaVinci Resolve 21 AI Tools FAQ ### Are the new DaVinci Resolve 21 AI tools free? No. The Resolve 21.1 Reference Manual labels the nine tools in this guide Studio-only: IntelliSearch, Speech Generator, CineFocus, Face Age Transformer, Face Reshaper, Blemish Removal, Slate ID, UltraSharpen and Motion DeBlur. ### Is IntelliSearch free in DaVinci Resolve 21? No. IntelliSearch requires Studio. Its visual search needs a Faster or Better model and clip analysis; transcript search needs transcribed audio. Metadata Search reads existing fields such as filenames and timecode, rather than requiring visual analysis of those fields. ### Does CineFocus need camera depth data? No. CineFocus creates a synthetic depth treatment from a 2D image. That makes it camera-independent, but it also means you must inspect edges, occlusions and motion because the generated depth can be wrong. ### Does Speech Generator require a WAV voice sample? Use a clean WAV file for compatibility: published hands-on tests have found WAV-only import restrictions. The 21.1 manual asks for about 20 seconds of high-fidelity audio, but its format omission does not establish that MP3 or AIFF will work. Obtain permission before using a real person’s voice. ### What is the difference between UltraSharpen and Motion DeBlur? UltraSharpen selectively sharpens detail through a Resolve FX amount control. Motion DeBlur targets motion-blur softness and renders a new media clip without replacing the original. Test each on the actual failure it's designed to address. ### Can Resolve 21 AI tools run on the Photo page? Compatible Studio AI and Resolve FX tools can be used with stills, but they remain Studio-only. The core Photo workflow for imports, albums, RAW adjustments and node grading remains available in Resolve Free within Free’s documented output limits. ### How do I install Resolve 21 AI models? Open DaVinci Resolve > Extras Download Manager and install the model required by the tool. IntelliSearch has separate Faster and Better packages; Speech Generator, Slate ID and Motion DeBlur also require their documented model downloads. ### Is Resolve Studio worth $295 for AI tools? It's worth considering when one named Studio AI tool removes a repeated paid or manual step and passes a test on representative media. It isn't worth buying solely because nine tools exist or because a demo result looks convincing on one frame. ### DaVinci Resolve 21 Photo Page: Full Walkthrough URL: https://davinciresolveclub.com/davinci-resolve-21-photo-page/ Last updated: 2026-09-09T02:53:47.000Z DaVinci Resolve 21’s Photo page gives still images their own import, album, culling, adjustment and export workflow. Its strongest advantage isn't a Lightroom-shaped slider panel: it's the ability to send a native-resolution Photo Album into the [DaVinci Resolve color grading workflow](https://davinciresolveclub.com/davinci-resolve-color-grading/) or Fusion page and use nodes, scopes, masks and effects already familiar to video colorists. This guide follows one shoot from import to delivery and flags the Free/Studio limits before they cost you an export. ## What the Resolve 21 Photo Page Actually Adds This walkthrough covers Resolve 21, including the Photo changes in 21.1\. Blackmagic’s [official Photo page](https://www.blackmagicdesign.com/products/davinciresolve/photo?ref=davinciresolveclub.com) describes albums, source-resolution processing and access to the Color and Fusion toolsets. Stills now have their own route through those tools instead of being treated only as video-timeline media. If Resolve itself is unfamiliar, learn the page layout in the [beginner Resolve workflow](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) first. The page combines five jobs: importing stills, organizing them in bins and albums, culling with tags and ratings, making RAW or Photo adjustments, and exporting an album or selection. Lightbox view lets you compare multiple images while a selected grade updates. The Metadata panel exposes file and camera fields, while the Viewer can display EXIF details such as camera model, ISO, shutter speed, aperture and lens. The [Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) documents Canon CR3, Fujifilm RAF, Apple ProRAW, Nikon NEF, Sony ARW and Panasonic Lumix RW2 for Photo RAW controls. Treat that as a format list, not a guarantee for every camera model or compression mode. JPEGs can still be adjusted, but their RAW tab is disabled because the sensor data has already been processed. Test a file from your actual camera before committing a shoot. In the [21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com), Blackmagic adds camera controls for Fujifilm, Leica and Sony Alpha 7R VI, improves RAW post-decode sharpening and adds DNG support for lens distortion, aberration and shading. Camera control and RAW decoding are different capabilities: those notes do not establish support for every body, lens or operating system. ## Photo Page Workflow: Import to Export 1. Create a project for the shoot. Keep the original photos in a stable folder and back up both the source files and the Resolve project; the project stores your edits, not a replacement copy of the shoot. 2. Open the Photo page and use Import Media, Import Media Folder, Import From Photos on macOS, or File > Import > Lightroom Catalog. 3. Choose File > New Photo Album. Select photos in the Media Pool, right-click and choose Add Photo(s) to Album. Then cull: S marks a Good Take, X marks a Rejected Take, 1–5 adds stars and 0 clears the rating. 4. Use the RAW tab for supported camera RAW controls, the Photo tab for general adjustments, and Versions when you need alternative looks. 5. Open the album in Color for a full node grade or in Fusion for compositing, then return to Photo for review. 6. Export a small selection first. Check dimensions, color, compression, filename and metadata in the destination application before exporting the full album. ![DaVinci Resolve 21 Photo Album grid with current album and selected still](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-photo-album-ui.webp) Choose the current Photo Album, select a still, and switch the album view without leaving the Photo page. ## Importing Folders, Apple Photos and Lightroom Catalogs Import Media handles selected files; Import Media Folder brings in a folder. Import From Photos is macOS-only. The Media Pool itself shows still images in the Photo page, while bins remain the broader project organization layer. You can create as many albums as the project needs without duplicating the source files. Lightroom migration needs a clear warning. The manual’s File > Import > Lightroom Catalog command brings the photos into Resolve in their original state, without Lightroom presets or edits. Treat it as media migration, not edit migration, and compare a representative image before moving a live catalog. ## Culling and Organizing Photo Albums If imported pictures seem to be missing, check the active bin, album and filters first. The Photo Media Pool hides video and audio clips; it is not a view of every media type in the project. Keep files in their original folder, or use Relink Media if you deliberately moved them. A Photo Album is a curated set of stills, not a sequential video edit. Switch between Single View and Lightbox, then filter by good/rejected tags, rating, flags, color, keywords, graded state or other available metadata. Right-clicking the filter icons exposes the detailed criteria, such as a minimum star rating rather than one exact rating. Culling is faster once the shortcuts become muscle memory: S toggles Good Take, X toggles Rejected Take, 1 through 5 apply a star rating and 0 clears it. In Lightbox, use those marks to narrow the set before grading; don't make color decisions on every frame just because the full shoot is visible. ![DaVinci Resolve 21 Photo page Lightbox comparing stills with ratings and versions](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-lightbox-ui.webp) Lightbox puts the set on one screen. Ratings narrow the selection; the V1 label identifies the active image version. ## Grades, Albums and Versions Grades and effects on stills are applied at the source level. If the same source photo appears in several albums in one project, its grade is shared across those albums. That's useful for consistency, but it isn't a way to keep a social crop, print look and client alternative independent. Use Versions for alternatives. Right-click the photo in its album, choose New Version and name the alternative before trying a different look. Switch back through the version selector to compare. Only the currently selected version is exported by Quick Export or the Deliver page; other versions are ignored until selected. ## RAW, Photo and Node-Based Grading A supported RAW file activates the RAW Inspector tab. It includes decode and white-balance choices such as As Shot, Daylight, Cloudy, Shade, Tungsten, Fluorescent and Flash, plus temperature, tint, exposure and camera-dependent controls. The Photo tab covers general tonal and color work. Reset Camera Raw and Reset Photo are separate commands, which helps isolate where an adjustment came from. Do not confuse RAW Decode Quality with Photo Album Preview Resolution. A lower RAW decode setting reduces processing quality for speed; switch to a higher quality before final rendering. The separate album-preview control only reduces the working preview. In 21.1, the Inspector also has reset controls for individual RAW parameters, so you can undo one adjustment without clearing the rest. ![DaVinci Resolve 21 Photo page crop controls with aspect ratio and straighten field](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-crop-ui.webp) The crop overlay works at the photo's source resolution. Set the ratio, reframe with the handles, then check the angle and edges. For deeper work, open the Photo Album on the Color page. Photo-page adjustments become the image’s first node, then the normal node graph, qualifiers, Power Windows and scopes are available. Read those controls as a grading pipeline, not as a second copy of the Photo sliders: the Photo-page adjustment node and later Color-page nodes are separate parts of the image path. ![DaVinci Resolve 21 Color page grading Photo Album stills with primary controls and color wheels](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-color-tools-ui.webp) A Photo Album opens in Color with Resolve's normal grading controls; Photo-page adjustments become the image's first node. To reuse adjustments, copy the reference photo, select the destination photos and choose Edit > Paste Attributes. Enable only the attributes you want; Photo Attributes > Plugins includes effects. Middle-click copying is different: it does not copy applied effects, and RAW settings transfer only between files of the same RAW format. Check one destination before applying a look across the shoot. For responsive viewing, Playback > Photo Album Preview Resolution offers Auto, Full, Half and Quarter. Auto reduces photos over 4K to a 4K working preview. It does not set the requested export dimensions. Check a Full preview for fine detail, then verify the exported file rather than judging sharpness from a reduced preview. ## Which Photo Features Require Studio The core import, albums, culling, RAW/Photo adjustments, Color-page grading and standard export workflow is available without a Studio license. Blackmagic documents Free output as Ultra HD or lower (3840×2160 in its edition comparison), even though it can process larger source images. Do not assume Original bypasses that limit: check the actual pixel dimensions, especially for portrait and print delivery. Studio is the route to higher-resolution output. - Tethered Capture: Studio-only. Canon and Sony support is extended in 21.1 with Fujifilm, Leica and Sony Alpha 7R VI camera controls; model and platform checks still matter. - IntelliSearch: Studio-only. It can search analyzed media by people and objects after the required model is installed. - Magic Mask v2, Depth Map, CineFocus and Film Look Creator: Studio-only effects in the current Resolve 21 manual. - Blemish Removal and UltraSharpen: Studio-only. They can be useful for retouching or selective sharpening, but still need close inspection for artifacts. - Other Resolve FX: licensing varies by effect. Check the effect’s Studio label instead of assuming every item visible in the library is free. For the whole license boundary, output ceilings and current US price, use the [DaVinci Resolve Free vs. Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/). The [Resolve 21 AI tools guide](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/) covers setup and failure cases for the paid tools, while [what’s new in DaVinci Resolve 21](https://davinciresolveclub.com/davinci-resolve-21-whats-new/) explains changes across the rest of the application. ## Tethered Capture: Exact Support and Limits Tethering isn't part of Resolve Free. In Studio, Capture can transfer a shot into the Media Pool or a chosen Photo Album and exposes controls supported by the connected camera, including aperture, shutter speed, ISO, exposure compensation, focus controls and Live Preview. Unsupported controls are disabled rather than simulated. Enable the camera’s tethering mode according to its manual, connect it by USB and open Capture in Resolve. Choose the save Location and target bin or album, then take a test shot. If the camera is not detected, close other applications connected to it and try restarting Resolve. Check both image transfer and the controls you need before the client arrives. - macOS: Canon and Sony tethering are supported natively. - Windows: the manual documents native Canon support and additional Sony Imaging Edge Desktop software for Sony cameras. - Linux and iPad: tethering isn't supported. - Fujifilm and Leica: 21.1 adds camera control support. The release notes do not give a complete model-by-operating-system matrix. Verify your body and required software before a live session; RAW import support alone does not prove tethering support. For a tether-first job, compare your exact camera against Capture One’s [camera support table](https://support.captureone.com/hc/en-us/articles/360002718118-Camera-Models-and-RAW-Files-Supported-by-Capture-One?ref=davinciresolveclub.com): RAW decoding, tethered capture, Live View and wireless support are separate entries. Resolve makes sense when you need its Color/Fusion environment; choose the application that supports the complete capture workflow, not just the camera brand. ![DaVinci Resolve Studio 21 tethered Capture panel with camera exposure controls and live preview](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/05-tethered-capture-ui.webp) Studio tethering exposes the controls supported by the connected Canon or Sony body. Platform and model compatibility must be checked before the session. ## Quick Export and Deliver Settings Quick Export supports JPEG, PNG, HEIC and TIFF. Choose Entire Album or Selected Photos deliberately, then set the filename prefix, scale, quality or compression and bit depth where supported. Scale controls image dimensions; Resolution is a pixels-per-inch setting, not a way to recover detail. Include Metadata is optional and may include location data, so check what belongs in the delivered file. For more control, leave the Photo Album active and open Deliver. Choose the destination folder, format, size and Entire Album or Selected Photos. Size options include Original, Width and Height, Short Side, Long Side, Percentage and Megapixels. Quick Export calls the Apple-oriented format HEIC; the Deliver list calls it HEIF. Available controls depend on the chosen format. To keep a link to the source file, use the + menu or type % in the file-naming controls and select the source-name metadata field. Check the generated name in a test export. Click Add to Render Queue, repeat with different settings if you need another size or format, then click Render All. Selecting photos in the album does not replace choosing Selected Photos in the export settings. Before exporting the whole album, open a test file in the actual destination application. Compare crop, pixel dimensions, color, compression, filename and metadata. If colors differ, check the RAW interpretation, color-management settings and output profile before adding a corrective grade. If detail looks soft, check RAW decode quality and export size. A smaller JPEG file alone does not prove worse image quality; compare the visible result at the same dimensions. ## Where the Photo Page Fits Against Lightroom and Capture One Resolve’s clearest advantage is a shared color and compositing environment for a hybrid production. A Photo Album can open in Color or Fusion at native photo resolution, and the same project can hold the motion work. That's valuable when stills and video need one look or when a node-based grade matters more than catalog automation. Lightroom imports do not bring edits. Tethering still requires Studio and a supported camera/software combination, despite the extra brands in 21.1\. Resolve organizes photos inside projects rather than a Lightroom-style lifetime catalog. Try one complete job, including archive and delivery, before moving an established library. Photo Albums are not ordinary video timelines. The manual says Cut, Edit and Fairlight mainly display the album as a timeline because photos are non-temporal. To use a finished Photo-page image in a normal video edit, export it and import the rendered still as regular media. Color and Fusion are the direct album workflows. Large native-resolution photos, complex nodes and AI effects can pressure the GPU and memory even when the interface opens normally. Check the current [Resolve 21 system requirements and practical hardware guidance](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) before moving a large shoot. ## DaVinci Resolve 21 Photo Page FAQ ### Can DaVinci Resolve 21 edit RAW photos? Yes. The manual documents Canon CR3, Fujifilm RAF, Apple ProRAW, Nikon NEF, Sony ARW and Panasonic Lumix RW2\. Resolve 21.1 also improves RAW sharpening and adds DNG lens-correction support. Check an actual file from your camera; format support does not guarantee every model or compression mode. ### Is the Resolve 21 Photo page free? Yes. Albums, RAW/Photo adjustments, Color-page grading and standard export are available in Resolve Free. Blackmagic limits Free output to Ultra HD or lower; check exported pixel dimensions rather than assuming Original means unrestricted full resolution. Tethered Capture, IntelliSearch and named Studio effects require Studio. ### Does Resolve import Lightroom edits? No. Resolve can import a Lightroom catalog through File > Import > Lightroom Catalog, but the Resolve 21 manual says the images arrive in their original state without Lightroom presets or edits. ### Which cameras can tether to the Resolve Photo page? Studio supports Canon and Sony tethering, and 21.1 adds Fujifilm, Leica and Sony Alpha 7R VI camera controls. The manual documents native Canon/Sony support on macOS, native Canon on Windows and extra Sony Imaging Edge Desktop software on Windows. Linux and iPad tethering are not supported. Verify the exact model and setup, especially for the added brands. ### Do Photo page grades change the same photo in every album? Yes. Still-image grades and effects are applied at the source level and shared across albums in the project. Create named Versions when you need alternative looks; only the selected version exports. ### Which still formats can the Photo page export? Quick Export supports JPEG, PNG, HEIC and TIFF. The Deliver page lists HEIF, JPEG, PNG and TIFF and adds queue, naming and sizing controls. Enable Include Metadata when required, then inspect a test file outside Resolve. ### Can a Photo Album go directly into an Edit-page video timeline? Not as a normal edited still workflow. Photo Albums open directly in Color and Fusion, while Cut, Edit and Fairlight mainly display the non-temporal album as a timeline. Export the finished photo and re-import it as regular still media for a video edit. ### Does the Photo page replace Lightroom or Capture One? It can replace part of the workflow for hybrid creators who want Resolve’s nodes and a shared photo/video project. It does not import Lightroom edits, and tethering requires Studio plus compatible camera software. Test culling, RAW interpretation, export and archive with a complete job before switching. ### DaVinci Resolve 21: What's New, AI Tools, Photo Page and Upgrade Notes URL: https://davinciresolveclub.com/davinci-resolve-21-whats-new/ Last updated: 2026-09-12T16:09:35.000Z DaVinci Resolve 21 is the current major release. As of September 12, 2026, Blackmagic lists 21.1 build 14 for macOS, Windows, Windows ARM and Linux. Version 21 introduced the Photo page, Studio AI tools, deeper keyframe controls, a layer-list view for Color nodes, Krokodove graphics and Fairlight folders. The September 8 update adds Inspector presets, more multicam controls and Studio automation—but it also changes Python scripting access. Quick answer: upgrade when a new feature or documented fix solves a problem in your work. Back up the Project Library and export critical projects before opening them in 21.1\. A compatible library does not make an upgraded project backward-compatible. If you rely on Python scripts, check their 21.1 and Studio requirements before updating. ## DaVinci Resolve 21 Release Status and Latest Version Resolve 21 left beta on June 3, 2026\. Check the [live Blackmagic support feed](https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion?ref=davinciresolveclub.com) for the current installer and release notes; use the [official Resolve 21 What’s New page](https://www.blackmagicdesign.com/products/davinciresolve/whatsnew?ref=davinciresolveclub.com) for the feature overview. Search snippets and third-party download pages can lag behind a maintenance release. ### What Is New in Resolve 21.1? - Editing: save Inspector presets instead of rebuilding clip settings, use shortcuts to switch or cut up to 25 multicam angles, and work with the revised trim editor and timeline comparison controls. - Photo: additional supported Fujifilm, Leica and Sony cameras gain live preview, control and capture in Studio. The update also improves RAW-image controls and the Photo sidebar. - Color: relink missing LUTs and DCTLs. Studio MultiMaster adds individual Dolby Vision, HDR10+ and HDR Vivid trim passes, with per-trim output sizing and cache handling. - Fusion: new Krokodove shape and 3D tools, OpenPBR material shaders and updated Macro Editor handling expand the graphics workflow. - Automation: Studio gains a native MCP server for AI assistants and built-in Python console support. Blackmagic says Python scripting has moved to Studio; Python 2 support has been removed. Do not assume an existing script or integration will survive the update unchanged. The [Free 21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) and [Studio 21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) separate the two editions. If you use a subtitle script, integration or automation bridge, check that specific tool with its maintainer and test a copied project. The Python change does not mean that every plug-in is broken, or that every type of script has the same restrictions. Earlier, the August 5, 2026 maintenance release, 21.0.4, added proxy relinking across different formats, Sony FX-5 X-OCN support, APIs for timeline selection and render settings, and fixes for real-time playback on large cached timelines. Those are targeted maintenance items; they do not change the major Resolve 21 feature set. Blackmagic lists the complete fixes and platform requirements in the [official 21.0.4 release notes](https://www.blackmagicdesign.com/support/content/readme/f1b3986a11634684b538ff3d1d4b55d6?ref=davinciresolveclub.com). A point release is not a reason to skip testing. Plug-ins, scripts, codecs, GPU drivers and a specific project can expose problems that do not appear in a clean installation. ## Photo Page: the Largest Workflow Change The new Photo page imports and organizes stills in albums, searches a library, reframes at source resolution and carries images into Resolve’s Color and Fusion workflows. It's most useful for hybrid jobs that already need the same grades, effects, collaboration and delivery environment for stills and video. The core Photo page is available in Free. Capture is marked Studio Version Only in the current [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com), and Studio-only AI tools or Resolve FX keep that license boundary on stills. Tethering also depends on the camera model and platform: the manual excludes Linux and iPad from live capture. Check the supported-camera list and your camera setup before promising a tethered session. Don't call Photo a Lightroom replacement until it passes your own catalog, metadata, filename, batch-export and handoff tests. For the page layout, albums, Capture and export workflow, use the dedicated [Resolve 21 Photo page guide](https://davinciresolveclub.com/davinci-resolve-21-photo-page/). ![DaVinci Resolve 21 Photo page searching an album and returning matching still images](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-photo-page-ui.webp) The Photo page keeps library search, album selection and matching stills in one interface before grading or compositing. ## Resolve 21 AI Tools: What They Actually Do The headline Resolve 21 AI additions are Studio features. The Reference Manual marks IntelliSearch, CineFocus, Speech Generator, Slate Finder and Slate ID, Motion DeBlur, UltraSharpen, Face Age Transformer, Face Reshaper and Blemish Removal as Studio Version Only. This is a licensing fact, not a quality verdict: choose a tool only after its output survives your review. ![DaVinci Resolve 21 IntelliSearch UI with text query, selected bins and matching clips](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-intellisearch-ui.webp) IntelliSearch analyzes Media Pool content, then searches within all bins or a selected scope. It is a Studio feature and its models are separate downloads. - IntelliSearch: analyzes Media Pool clips, then searches people, objects, faces, transcript text and metadata. Faster and Better model packages are separate downloads. - CineFocus: creates a virtual depth and bokeh treatment and can keyframe a rack-focus effect. It can't recover optical detail that the camera never captured. - Speech Generator: creates narration from typed text using supplied or custom voice models. Custom voice use requires permission from the voice owner. - Face tools: age or reshape a tracked face, or reduce superficial blemishes. Check continuity between frames, consent and technical quality; these effects do not all use the same controls. - Motion Deblur and UltraSharpen: target blur or softness through different processes. Test on the problem shot and inspect artifacts at delivery resolution. - Slate ID: detects a clapperboard and extracts slate metadata after the corresponding model is installed. IntelliSearch has no Free exception in the current manual. Its Faster and Better model packages are downloaded through Extras Download Manager before analysis. The dedicated [Resolve 21 AI tools guide](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/) covers setup and failure cases; the [DaVinci Resolve Free vs. Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) covers the wider license boundary and current $295 US desktop price. ### Which Resolve 21 Changes Matter to Your Work - Long-form and documentary editors: IntelliSearch can reduce manual logging after its models are installed and the Media Pool is analyzed. - Photographers and hybrid crews: Photo albums, shared grades and tethered Studio capture can keep stills beside the video project. - Motion designers: Lottie, OGraf, Krokodove, Macro Editor changes and audio-driven Fusion animation reduce handoffs for repeatable graphics. - Colorists delivering variants: Studio MultiMaster trims, group versions and the layer-list node view improve organization across HDR and SDR outputs. - Dialogue and mix editors: Fairlight track folders, six-band clip EQ, EQ and level matching, and Chain FX reduce navigation and setup work. Start with the job: find one shot in 800 clips, generate a temporary voice, reshape bokeh, clean a blurred take or group 60 audio tracks. Record the current time or failure, run the Resolve 21 tool on representative media, then compare accuracy, correction time and final render. A feature that creates more cleanup isn't an upgrade for that job. ## Cut, Edit and Graphics Changes Cut and Edit gain stronger keyframe and curve controls, including Loop, Ping Pong and Relative modes, multi-clip adjustment and four-point Bezier easing. Fusion effects can be adjusted from the Cut and Edit keyframe editors, which reduces page switching for routine animation work. Resolve 21 also accepts supported OGraf HTML and Lottie graphics in the Media Pool with alpha. Text+ and MultiText add font previews, multilingual spell checking, emoji and character-level styling, while Smart Bin views become available in the Cut page. ![DaVinci Resolve 21 Edit page keyframe curve editor with repeat mode menu](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-keyframes-ui.webp) Resolve 21 expands curve editing with parameter selection and repeat modes including Loop, Ping Pong and Relative. ## Color, Fusion and Fairlight Changes Color adds Studio-only MultiMaster trim management for linked HDR and SDR trims, alongside a layer-list view of the node graph and group grade versions. The layer list is an alternate view of the grade, not a second copy: it can make a long correction chain easier to scan without changing node processing. ![DaVinci Resolve 21 Color page switching between node graph and layer list views](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-color-layer-list-ui.webp) The Color page can show the same correction structure as a node graph or a layer list; the view changes, not the grade. Fusion integrates the Krokodove toolset with more than 70 graphics and updates the Macro Editor, while Fairlight adds collapsible track folders, six-band clip EQ, EQ and level matching, and Chain FX. Track folders are organizational containers; closing one hides its children but doesn't merge the tracks. ![DaVinci Resolve 21 Fairlight timeline organizing dialogue and music tracks in folders](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/05-fairlight-folders-ui.webp) Fairlight folders group related tracks and can collapse dense sessions without flattening the tracks inside them. ## Free vs. Studio in Resolve 21 Free still covers the core Edit, Color, Fusion and Fairlight workflow, collaboration and mastering up to Ultra HD 3840 × 2160 at 60 fps. Codec support still depends on the platform and format. Studio adds the named AI tools above, more Resolve FX, higher frame-rate and resolution support, MultiMaster and additional delivery and automation features. Buy Studio for a feature you actually need. Photo albums and core grading may be enough in Free; IntelliSearch, tethered capture, MultiMaster or a Python-based workflow can make Studio necessary. Compare that need with the current $295 US desktop license price. The [cost and licensing guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) explains the purchase options; a useful new feature is not a promise that the upgrade will pay for itself. ## System Requirements: Check the Distribution You Install For Free 21.1, Blackmagic lists macOS 15 Sequoia or later, an Apple Silicon computer, and 8 GB of memory or 16 GB with Fusion. Studio has additional requirements for advanced AI and background rendering. Windows x86, Windows ARM and Linux have separate requirements too. Check your edition and platform in the [Resolve 21 system requirements guide](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) before downloading. A minimum requirement only answers whether the installer is supported. Codec, resolution, frame rate, temporal effects, Fusion complexity, VRAM, memory and storage throughput determine whether your timeline actually plays and renders comfortably. ## How to Upgrade to Resolve 21 Safely 1. Read the current 21.1 release notes for your edition and verify operating system, GPU driver, codec, plug-in and scripting compatibility. 2. Create a full Project Library backup from Project Manager. 3. Export a DRP for every irreplaceable active project and preserve the original media and license information. 4. Install Resolve 21 without deleting the previous installer or backups. 5. Open a copied project, then test playback, Fusion, audio routing, color, subtitles and every required deliverable. 6. Open production work only after the copied project renders, reopens and passes visual and audio QC. The [21.1 installer notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) name Resolve 20.3.2: the project library can remain accessible there, but an individual project created or opened in 21.1 cannot. Keep the pre-upgrade library backup and DRP exports untouched. Exporting a DRP after conversion does not turn it back into a Resolve 20 project, and a project export is not a substitute for backing up the source media. For the complete rollback, plug-in and copied-project sequence, follow [How to Update DaVinci Resolve Safely](https://davinciresolveclub.com/update-davinci-resolve-safely/). The [DaVinci Resolve tutorial hub](https://davinciresolveclub.com/davinci-resolve-tutorial/) maps the wider learning path; if the page layout itself is new, start with the [Resolve beginner tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) before judging the update by feature names. ## DaVinci Resolve 21 FAQ ### What is the latest DaVinci Resolve 21 version? As of September 12, 2026, Blackmagic lists DaVinci Resolve 21.1 build 14 for macOS, Windows, Windows ARM and Linux. The release is dated September 8, 2026\. Check the official support page again before installing. ### Is DaVinci Resolve 21 out of beta? Yes. The final Resolve 21 release arrived June 3, 2026, followed by maintenance updates and 21.1 on September 8\. A final release is not a guarantee that every project, plug-in or hardware combination is trouble-free. ### Is the Resolve 21 Photo page free? The core Photo page, album and grading workflow is available in Free. Studio is required for tethered capture and for Studio-only AI or Resolve FX used on photos. Live capture is not supported on Linux or iPad. ### Is IntelliSearch free in Resolve 21? No. The Resolve 21 Reference Manual labels IntelliSearch as Studio Version Only. Its Faster and Better model packages are downloaded separately through Extras Download Manager. ### Can Resolve 21 projects open in Resolve 20? Do not rely on backward compatibility after opening a project in 21.1\. Blackmagic says the library can remain compatible with 20.3.2, but an individual project created or opened in 21.1 is no longer accessible there. Keep backups and critical DRP exports made before the update. ### Does Resolve 21 work on Intel Macs? The current desktop 21.1 release requires Apple Silicon and macOS 15 Sequoia or later. Intel Mac users need a compatible earlier Resolve version or supported hardware; the current Mac installer is not an Intel build. ### Is DaVinci Resolve Studio 21 a subscription? The standard desktop Studio license is currently listed at $295 in the United States as a one-time purchase, not a monthly subscription. Check the license type before paying; Cloud Organization rentals and the iPad purchase are separate options. ### How to Save Work in DaVinci Resolve URL: https://davinciresolveclub.com/how-to-save-work-davinci-resolve/ Last updated: 2026-09-14T16:27:44.000Z Press Ctrl+S on Windows/Linux or Cmd+S on macOS to save your DaVinci Resolve project. Resolve stores the working project in a Project Library. Keep Live Save on for ongoing changes, enable scheduled backups for earlier versions, and export a DRP or DRA when you need a separate copy. For a first-project routine, use the [DaVinci Resolve tutorial path](https://davinciresolveclub.com/davinci-resolve-tutorial/). This guide covers saving and rollback. Library locations and migration have their own guide below. ## Where the saved project lives Resolve stores working projects inside a Project Library rather than asking you to save a normal project file for every session. A library can be local, networked or in Blackmagic Cloud, and each type has different storage and connectivity risks. Do not rely on a copied path from another computer. In Project Manager, open the Project Libraries sidebar and inspect the active library. For the on-disk details, use [Where DaVinci Resolve Projects Are Saved](https://davinciresolveclub.com/where-davinci-resolve-projects-saved/); if Project Manager itself is unfamiliar, start with the [DaVinci Resolve beginner tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/). For a local library, use its Back Up command rather than copying individual database files while Resolve is running. For a managed network library, use Resolve's tools or your administrator's backup procedure. Neither a library backup nor a DRP replaces a backup of your source media. ## How to Save a Project with Live Save Live Save incrementally saves changes without user action. The [Resolve 21 saving documentation](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) says it's enabled by default. Cut, Edit and Fairlight changes save as you make them; Fusion and Color changes save when you switch clips and periodically in the background. Collaborative projects keep Live Save on and don't allow it to be disabled. ![DaVinci Resolve 21 Project Save and Load preferences with Live Save and backups enabled](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-live-save-backups-ui.webp) Live Save protects the current state. Enable Project Backups and Timeline Backups for dated rollback, then choose retention and a backup location that fit the job. Check it under: 1. Open DaVinci Resolve > Preferences 2. Select User > Project Save and Load 3. Confirm Live Save is enabled 4. Click Save after changing the preference File > Save Project or Ctrl+S on Windows/Linux and Cmd+S on macOS still performs a manual save. With Live Save enabled, that shortcut is a confirmation habit, not a version history. For a separate working version in the same library, choose File > Save Project As and enter a unique name. If Resolve asks to overwrite an existing project, cancel and choose another name. This creates a project copy, not an independent media backup. Keep Live Save enabled for everyday editing. If you deliberately disable it, save manually before closing the project. File > Revert to Last Save Version discards unsaved changes, so don't use it as a substitute for loading a dated backup. The Edited indicator beside the project name marks unsaved work. ## Enable Project Backups and load an earlier version Live Save preserves the latest state; it can't take you back through a chain of already saved decisions. Project Backups create independent, dated copies for that job. ![DaVinci Resolve 21 Project Manager loading a dated project backup](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-project-backup-restore-ui.webp) Right-click the project, choose Project Backups, select a dated snapshot, and click Load. Resolve opens the backup as an independent project instead of overwriting the current one. Project Backups rotate through minute, hourly and daily retention. Older snapshots eventually expire; export a dated DRP for a milestone you want to keep. Each scheduled backup contains project data but excludes Gallery stills, LUTs and source media. Preserve those assets separately or choose an export option that includes the stills and LUTs. To enable Project Backups: 1. Open DaVinci Resolve > Preferences > User > Project Save and Load 2. Enable Project Backups 3. Set minute, hourly and daily retention for the project 4. Choose a writable backup location, preferably on storage independent of the active library 5. Click Save and later confirm that backups appear in Project Manager To restore, open Project Manager, right-click the project and choose Project Backups. Select a dated backup and click Load. Resolve opens it as an independent project instead of overwriting the original; rename it clearly before continuing work. Live Save and Project Backups operate independently and should normally run together: one protects the current state, while the other preserves earlier states. If the backup list is empty, confirm Project Backups is enabled, its destination is connected and writable, and you've edited long enough for the configured interval. Sitting idle doesn't create new useful generations. Click Refresh in the backup list. Turning backups on after a loss can't recreate earlier edits. For a Blackmagic Cloud library, check its separate [Cloud Project Server backup controls](https://help.cloud.blackmagicdesign.com/project-server/managing-project-libraries/?ref=davinciresolveclub.com). Open the library’s Backups tab and verify the dated backups there. Do not assume that enabling Project Backups in Resolve proves a Cloud project has a recoverable copy. Keep dated DRP exports outside the library too. ## Restore one timeline without replacing the current edit Timeline Backups use the same rotating schedule but preserve individual timelines. They're useful when one edit sequence is damaged and the rest of the project should remain untouched. ![DaVinci Resolve 21 restoring a timeline backup as a new timeline copy](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-timeline-backup-restore-ui.webp) Restore Timeline Backup works from the timeline in the Media Pool. The chosen snapshot returns as a new timeline with Backup appended, leaving the current timeline intact. Enable Timeline Backups in Preferences > User > Project Save and Load. Project and Timeline Backups share the interval fields and backup location. To restore, right-click the timeline in the Media Pool and choose Restore Timeline Backup. The selected snapshot returns as a new timeline with Backup appended, so the current timeline isn't overwritten. Resolve 21 can also compare a timeline with a backup from Compare with Timeline Backup. A Timeline Backup is not a replacement for a whole-project backup. Keep Project Backups enabled too. Before a major restructure, duplicate the timeline or right-click it in the Media Pool and choose Create Timeline Backup to make a named restore point. ## Export a DRP or archive the project with media Live Save and scheduled backups operate inside Resolve's project system. When a project must exist as a portable item outside the library, export a DRP or create a DRA archive. ### Export as DRP (DaVinci Resolve Project) A .drp contains the project structure, timelines, edits, grades, Fusion work and settings, but not source media. A normal export also omits Gallery stills and LUTs; choose Export Project With Stills and LUTs in Project Manager when those assets need to travel with the project data. With the project open, choose File > Export Project. From Project Manager, select Export or right-click the project and choose the required export variant. Save the resulting .drp somewhere outside the active library. Use a DRP for a project-data checkpoint or a handoff to someone who already has the media. To test it, drag the DRP into Project Manager and import it under a unique name, preferably in a test library. Open its timelines and relink missing clips to your separately preserved media. ### Export as DRA (DaVinci Resolve Archive) A .dra is a folder archive containing the project and the media you choose to include. For an original-media backup, select Media Files. Proxy Media contains generated editing copies; a proxy-only archive is not a substitute for your camera originals. In Project Manager, right-click the project and choose Archive (called Export Project Archive in some menus). Select a destination with enough free space. In the archive options, review Media Files, Proxy Media, Only include used media, Include Render Cache, Include LUTs and Include Gallery Stills before starting. Leave Only include used media off if you need unused Media Pool clips too. Resolve reports missing or offline media at the end. The [Resolve 21 archive options](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) list Proxy Media, not an Optimized Media checkbox. Keep an independently verified copy of irreplaceable originals even after an archive succeeds. A DRA does not automatically preserve every external dependency: fonts, plugin installers, licenses, third-party scripts, LUT installers, briefs and client documents need their own package. Resolve reports missing or offline media during archiving, so [fix Media Offline](https://davinciresolveclub.com/media-offline-davinci-resolve/) before treating the archive as a verified handoff. To test a DRA, first put the whole archive folder on the drive where its media should stay. Drag it into Project Manager, or use Restore/Restore Project Archive, and give the restored project a unique name. Open the timelines and check footage, audio, grades and effects. Restoring a DRA adds the project to the library but leaves its media inside the DRA folder. Don't delete that folder after restoring. A successful project open alone doesn't prove that every clip or external dependency is present. ## Save Settings You Should Configure Before Any Project Use this as a baseline, then adapt retention and storage to the value and duration of the work: - Live Save: on, then confirm the Edited indicator clears as changes are saved - Project Backups: on, with retention matched to the work and a verified backup location - Timeline Backups: on for active editing projects - Before a major timeline restructure: duplicate the timeline or create a named Timeline Backup - Before a Resolve or Project Library upgrade: back up the library and export important DRPs - For handoff or archive: create a DRA and test-restored copy; preserve fonts, plugins and documents separately Manual save is useful, but it isn't an additional backup generation. The stronger check is whether Live Save is on, scheduled backups are being written to the intended location, and a DRP or DRA can be restored on another system. An archive protects editable work; keep a separate finished deliverable using the [Resolve export workflow](https://davinciresolveclub.com/export-video-davinci-resolve/). ## Common Save Problems (and What's Actually Going On) ### My project isn't showing up in the Project Manager Open Project Manager and inspect the Project Libraries sidebar. Local, network and cloud libraries show different project sets, and a disconnected or signed-out library can make a project appear missing. Confirm the correct library before importing duplicates or moving folders. ### I Can't Save: Resolve Throws an Error Start with the exact error. Check free space and write access for a local library; for network or cloud libraries, also check the server connection, account and library availability. Preserve the current project and backup folders before attempting database repair. If the failure extends beyond saving, use the [Resolve troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/) to match the symptom before changing project data. ### I lost a project after a crash After a crash, reopen the existing project and inspect what Live Save preserved. If you need an earlier state, load a Project Backup from Project Manager. For timeline-only damage, restore a Timeline Backup. Keep both the original project and the recovered copy until you've checked the edit. If no usable scheduled backup exists, import the latest DRP or restore the DRA/library backup. A DRP cannot restore missing media, and a DRA can't restore dependencies that were never included, which is why the layers must be tested before a failure. ## Frequently Asked Questions About Saving Projects ### Does DaVinci Resolve save automatically? Yes. Live Save is enabled by default and incrementally saves changes. Verify it under Preferences > User > Project Save and Load. Enable Project Backups separately when you need dated states that can be loaded without overwriting the current project. ### Where does DaVinci Resolve save projects? Working projects live in the active Project Library. In Project Manager, inspect the Project Libraries sidebar and the selected local library's details. A DRP is a separate project-data export; a DRA can include selected media. Neither changes where your active library lives. ### What is the shortcut to save in DaVinci Resolve? In the default Resolve preset, use Ctrl+S on Windows/Linux or Cmd+S on macOS for Save Project. Ctrl+Shift+S or Cmd+Shift+S opens Save Project As. Use a unique name: choosing an existing name can prompt you to overwrite it. Check custom mappings in Keyboard Customization. ### What's the difference between a DRP and DRA file? A DRP carries project data but no source media. A DRA is a folder archive whose contents depend on the selected Media Files, Proxy Media, cache, LUT and stills options. A proxy-only DRA does not replace your original-media backup. Preserve external fonts, plugins, licenses and documents separately. ### Can I recover a DaVinci Resolve project after a crash? Start with Live Save, then load a dated Project Backup or restore a Timeline Backup when only one timeline is affected. If the library itself is unavailable, restore a library backup or import a known-good DRP/DRA. Keep the damaged original untouched until recovery is verified. ### Does DaVinci Resolve free version have autosave? Yes. Live Save, Project Backups and Timeline Backups are available in the free version as well as Studio. Project Backups and Timeline Backups must be enabled and need a writable backup location. ### How to Transcribe Audio in DaVinci Resolve 21 URL: https://davinciresolveclub.com/transcribe-audio-davinci-resolve/ Last updated: 2026-09-09T02:18:47.000Z Choose the output first: a searchable transcript for editing, or timed subtitles for viewers. In DaVinci Resolve 21, transcribe Media Pool clips to find dialogue and assemble selects. Use Create Subtitles from Audio to build a subtitle track. Both automated workflows require [DaVinci Resolve Studio](https://davinciresolveclub.com/davinci-resolve-vs-studio/); Free can import, edit and export subtitle files, but cannot generate them from speech natively. The menu names and limits below follow Blackmagic's latest [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com). Older tutorials often use shorter labels from previous releases, so match the full Resolve 21 paths when a command appears to be missing. For dialogue cleanup, routing, levels or audio-only delivery around this task, use the [DaVinci Resolve Fairlight Audio hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/); this page stays focused on speech-to-text, transcript editing and captions. ![DaVinci Resolve 21 Media Pool menu for transcribing selected audio clips](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/01-transcribe-clips-ui.webp) Select the source clips, then use AI Tools > Audio Transcription > Transcribe. This creates clip transcripts for search and text-based editing, not a timeline subtitle track. ## Choose the Right Transcription Workflow A clip transcript is attached to source media. It helps you find what was said and build an edit from selected words. A timeline transcript represents the edit and can drive changes to it. Timeline subtitles are separate caption clips for styling and delivery. Transcribing a clip does not automatically put captions on screen. - Need to search interviews or assemble selects? Transcribe source clips. - Need captions on a finished edit? Create subtitles from timeline audio. - Need a readable text record? Export the transcript as .txt. - Need timed captions? Export an SRT from the Transcription window, subtitle track or Deliver page. ![DaVinci Resolve 21 Transcription window searching and selecting interview text](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/02-search-select-transcript-ui.webp) Search across transcribed clips, select the words you need, then use the Transcription window's edit controls to place that source range in the timeline. ## How to Transcribe Audio Clips in DaVinci Resolve 21 1. Open the Media, Cut, Edit or Fairlight page and select one or more clips with speech in the Media Pool. 2. Right-click a selected clip and choose AI Tools > Audio Transcription > Transcribe. The Transcribe Audio toolbar icon starts the same analysis. 3. Wait for the Transcribing Audio window to finish. It reports clips remaining, analysis speed relative to real time and an estimated time remaining. 4. Open the Transcription window. Transcribed clips carry a speech-balloon icon in the Media Pool, and Resolve 21 also exposes a Transcription column in List view. 5. Click a word to move the source viewer to the end of that word. Drag across text to set a source range, then use Place on Top, Insert or Append to edit that range into the timeline. The Transcription window searches selected clips with Contains or Full Word matching. In source-clip mode, deleting text strikes it through: that range is excluded from transcript export and subsequent text-based edits, without erasing the recording. Use Undelete to restore it. Resolve marks detected silence with ellipses. Remove Silent Portions excludes those ranges when you assemble selected dialogue into a timeline. Listen to the joins afterward: a pause may contain a breath, reaction or room tone that the edit still needs. To change an existing edit through its transcript, duplicate the timeline first. Transcribe its source clips in the Media Pool, then click the Timeline mode icon in the Transcription window. Cut, Copy, Paste and Delete can now change the timeline itself. Verify the selected range and play the result after each edit. If a newly added clip says Transcription Pending, use Options > Transcribe Missing Clips in Timeline. ### Correct, Search and Export a Transcript Use Edit for spelling and proper-name corrections rather than rewriting whole paragraphs. Search and Replace is useful when the same name is wrong throughout several clips. Resolve warns that replacing a long passage with an unrelated summary can make text-based editing unpredictable because the words remain tied to source time ranges. The Export icon saves a .txt transcript. When speaker detection is enabled, Resolve Studio's transcript export includes speaker names and timecodes for speech blocks. The Options menu also provides Export Subtitles, which writes an SRT and asks for a caption preset, maximum characters per line, number of lines and gap between subtitles. ## How to Create Subtitles from Timeline Audio 1. Open the timeline on the Edit page. Set In and Out points if only part of the timeline needs captions; leave them unset to analyze the whole timeline. 2. Choose Timeline > AI Tools > Create Subtitles from Audio. 3. Choose the spoken language or Auto, select a Caption Preset, set Max Characters per Line, choose one or two lines, and set the frame gap. The documented default gap is 0 frames. 4. Click Create. Resolve adds the result to a subtitle track. If no subtitle track exists, it creates one; if several exist, it writes to the highest track. 5. Read every caption while watching the program. Correct words, cue timing, line breaks, speaker changes and non-speech labels before export. ![DaVinci Resolve 21 Create Subtitles from Audio dialog over an interview timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/04-create-subtitles-ui.webp) Set an In/Out range when only part of the edit needs captions, then check the language, preset, line length, line count and frame gap before clicking Create. Overlapping dialogue on multiple audio tracks is the failure case Blackmagic calls out explicitly. Mute any track that shouldn't be included in the analysis, generate the subtitles, then restore the mix. If dialogue and music are hard to separate, use the practical routing steps in [Mute and Split Audio in DaVinci Resolve](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/) before generating subtitles again. ### Edit and Style the Generated Subtitles Select a subtitle clip and use the Caption tab in the Inspector to correct its text. Track controls set the shared typeface, size, color, position and outline. Enable Customize Caption only when one subtitle or selected words need a local override; otherwise keep the track style consistent. Resolve 21 adds Find and Replace in the Subtitle Inspector and spell checking for text elements. Spell checking flags possible mistakes; it doesn't validate names, numbers, technical terms or whether the transcript matches the speaker. Those still require a listening pass. For word-level animated captions, Resolve 21 can analyze manually entered or imported captions. Select a subtitle and click Update Word Timings, or right-click a subtitle track header and choose Synchronize Word Timings. This retimes word highlighting; it doesn't repair the wording itself. ## Resolve 21 Transcription Changes That Matter Blackmagic's [Resolve 21 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) documents four relevant additions: background analysis for transcription, transcript search inside IntelliSearch, external subtitle word timing and the Media Pool Transcription column. Background Rendering is disabled by default. In DaVinci Resolve > Preferences > System > Background Tasks, enable background renders and the Transcription task. Leave it off when the machine is short of memory. Pause background renders on foreground activity lets interactive work take priority; background processing is not a free speed increase. IntelliSearch requires its own model download and media analysis. Search Transcript Only limits results to words found in audio transcripts; Search All can combine transcript, visual and metadata results. A clip transcript doesn't automatically mean its visual content has been analyzed for IntelliSearch. ## Languages and Speaker Detection Project Settings > Subtitle and Transcription > Transcription Setup controls the transcription language. The Resolve 21 manual lists 14 base language entries: Danish, Dutch, English, French, German, Italian, Japanese, Korean, Mandarin, Norwegian, Portuguese, Russian, Spanish and Swedish. Mandarin has simplified and traditional models. Auto lets Resolve select a model. The Extended AI Transcription Support Package in Extras Downloads Manager adds 43 more named languages, including Arabic, Finnish, Greek, Hindi, Polish, Romanian, Thai, Turkish, Ukrainian and Vietnamese. Create Subtitles from Audio uses the same base list except the manual names Chinese as Simplified Mandarin; the extended package supplies the additional list. Speaker Detection is project-specific. Enable it from AI Tools > Audio Transcription > Speaker Detection or from the Transcription window Options menu before transcribing. Resolve remembers detected voice signatures across clips in the project. Rename Speaker 1, Speaker 2 and later labels, or use Assign To when a segment is attributed incorrectly. Reset Speaker Data clears the saved project-level voice assignments. ![DaVinci Resolve 21 transcript with speaker labels and Assign To correction](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/03-speaker-detection-ui.webp) Enable Speaker Detection before transcription, rename the project-level speaker labels, and use Assign To when a dialogue block is attributed to the wrong person. Listen through the transcript rather than trusting a confidence impression. Check names, numbers, negations and speaker changes against the recording. Noise, accents, overlapping voices and microphone distance can change the result; choose the known language when Auto gets it wrong, then review the regenerated text. ## Why Transcribe Audio Is Missing or Produces Bad Results - The command is missing: confirm the installed application says DaVinci Resolve Studio, then use the exact AI Tools > Audio Transcription menu path on a Media Pool clip. - The transcript contains mostly ellipses: play the selected clip and confirm that audible dialogue is present on the source clip itself rather than only elsewhere in the timeline. - The wrong language appears: choose the language manually in Project Settings > Subtitle and Transcription > Transcription Setup, then clear and regenerate the transcription. - One speaker or track is ignored: check the actual source clip being transcribed. A timeline transcript analyzes underlying media; do not assume its input is identical to the finished audible mix. For captions, use the separate subtitle-generation workflow and test a short range. - Subtitle generation misses overlapping speech: mute the tracks Resolve should ignore and run Create Subtitles from Audio again, as Blackmagic recommends. - An imported transcript is not aligned: the SRT timecode must match the clip. Resolve 21 can also use AI Tools > Audio Transcription > Import and Detect Timing for a Media Pool clip. Before clearing or regenerating a corrected transcript, export a copy of its text and save the project. Clear Transcription removes the saved transcript, including your corrections; it does not delete the original recording. Diagnose the source, language and selected workflow before changing routing or channel formats. ## How to Export SRT Subtitles For a transcript attached to a clip, open the Transcription window Options menu and choose Export Subtitles. Resolve writes an SRT after you set the caption preset, line length, line count and gap. This is different from the Export icon, which saves a readable .txt transcript. ![DaVinci Resolve 21 Export Subtitles dialog for saving an SRT transcript](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/05-export-srt-ui.webp) Options > Export Subtitles writes a timed SRT. The separate Export icon at the top of the Transcription window saves plain transcript text as TXT. For a finished program, the Deliver page can export a separate subtitle file or burn captions into the rendered video. Choose the method required by the destination, render a short test, and open the exported file before the full delivery. The complete subtitle-track workflow, import formats and styling controls are covered in [DaVinci Resolve Subtitles and Captions](https://davinciresolveclub.com/davinci-resolve-subtitles-captions/); final video settings are covered in the [Resolve export guide](https://davinciresolveclub.com/export-video-davinci-resolve/). ## Resolve Transcription vs. Premiere Pro Both applications can assemble edits from transcripts, but captions remain a separate delivery step. [Premiere's Text-Based Editing guide](https://helpx.adobe.com/premiere/desktop/edit-projects/edit-video-using-text-based-editing/overview-of-text-based-editing.html?ref=davinciresolveclub.com) documents transcript editing, filler-word handling and speaker filtering. A list of supported languages does not establish accuracy for your speakers. Check wording, speaker overlap and export requirements in the same sample before choosing an editor. Licensing, collaboration, color and handoff differences are covered in the [DaVinci Resolve vs. Premiere Pro comparison](https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/). ## DaVinci Resolve 21 Transcription FAQ ### Is audio transcription available in free DaVinci Resolve? No. Native audio transcription, text-based editing and Create Subtitles from Audio require DaVinci Resolve Studio. In Free, create captions manually or generate a timed SRT with an external transcription tool, then import and review it on a subtitle track. Importing an SRT does not unlock Studio text-based editing. ### Can I transcribe one clip instead of the whole timeline? Yes. Select the source clip in the Media Pool and choose AI Tools > Audio Transcription > Transcribe. To work with an existing edit, select its timeline in the Media Pool and transcribe it. Create Subtitles from Audio is a separate command for a subtitle track. ### How many languages does Resolve 21 transcription support? The manual lists 14 base language entries, with simplified and traditional Mandarin models, plus 43 named languages in the optional Extended AI Transcription Support Package. Choose the known source language manually when Auto selects the wrong model. ### Can Resolve identify multiple speakers? Yes. Speaker Detection assigns project-level speaker labels and remembers voice signatures across clips. Rename labels and correct wrong segments with Assign To. Overlapping voices still require careful review. ### Can I export a Resolve transcript as SRT? Yes. In the Transcription window Options menu, choose Export Subtitles. For a finished timeline, export the subtitle track or use the Deliver page. The separate Export icon writes a .txt transcript instead. ### Why is Create Subtitles from Audio missing? It's a Studio-only command. Confirm the installed app is DaVinci Resolve Studio, open a timeline on the Edit page, and use Timeline > AI Tools > Create Subtitles from Audio. ### Does Resolve transcription need internet access? Native transcription is processed on your computer by the DaVinci Resolve Neural Engine. Download any required language or IntelliSearch packages before going offline. This is not a promise that the whole application never connects: licensing, cloud projects, shared storage and third-party tools have their own network requirements. ### How to Mute and Split Audio in DaVinci Resolve URL: https://davinciresolveclub.com/mute-split-audio-davinci-resolve/ Last updated: 2026-09-14T16:00:28.000Z To mute one audio clip in DaVinci Resolve, select only its audio item and press D. For a whole track, click the M button in that track's header. To remove a few seconds of unwanted sound, split the audio at both ends and disable the middle piece; use volume keyframes when you want a gradual level change instead. This guide uses Resolve 21 menu names. If the task grows from one mute into dialogue cleanup, buses or delivery, use the [DaVinci Resolve Fairlight hub](https://davinciresolveclub.com/davinci-resolve-fairlight-audio/) for the next stage. The basic mute, link and manual split controls covered here are available in both Free and Studio. ## How to Mute One Audio Clip If you're new to the Edit page workflow, the [DaVinci Resolve beginner's guide](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) covers the interface before you start here. On the Edit page, Option-click the audio item on macOS or Alt-click it on Windows. Check that only the intended audio is highlighted, then press D. Alternatively, right-click that item and toggle Enable Clip, or choose Clip > Enable/Disable Clip. A normal click with Linked Selection on can select both picture and sound, so check the selection before you disable anything. A disabled item turns gray, stays in place, and doesn't play or render. Older Fairlight versions called this Mute Clip. The [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) documents this selection behavior, the Enable Clip label, the D toggle, and the difference between permanent linking and temporarily suspending Linked Selection. ![Selecting an audio waveform item independently of its linked video in Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-mute-split-audio-select-v2.webp) Select only the audio item before pressing D. AI-assisted close-up based on Blackmagic’s interface; this locates the item, not an already-disabled state. Tap to enlarge. If the clip should stay audible at a lower level, drag its Volume overlay down or adjust Volume in the Inspector. Disable the item when it should be excluded altogether. D is a toggle, not an unconditional 'turn off' command. If you select a mixture of enabled and disabled clips, it can switch them in opposite directions. Work on the intended audio item, or assign the explicit Disable Clip command in Keyboard Customization for a repeated task. On Fairlight, the menu route is Clip > Enable Clip; older instructions may call it Mute Clip. ## How to Mute an Entire Audio Track Click the M button in the audio track header or Audio Mixer to silence that track. Blackmagic’s [Fairlight controls overview](https://www.blackmagicdesign.com/products/davinciresolve/fairlight/?ref=davinciresolveclub.com) identifies the track mute and solo controls. Unlike monitor mute, track mute affects both playback and the delivered mix. Solo lets you listen to chosen tracks while suppressing others. Before delivery, clear temporary Solo states and restore any tracks you muted only while checking the mix. Leave an intentional mute in place if that track should stay out of the finished file. M here means the visible track-header or mixer button, not an instruction to press the M key. If you use a custom keyboard preset, check its assignments in Keyboard Customization. The visible M and S states are the quickest way to see what is currently excluded from the mix. ![DaVinci Resolve track M button beside Solo for muting track audio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-mute-split-audio-track-v2.webp) Click the track’s M button, not the M key. Track mute affects the exported mix; the separate monitor speaker control is for listening. AI-assisted control locator based on Blackmagic’s interface. Tap to enlarge. ## Mute Part of a Clip or Lower It with Keyframes For complete removal of a cough or unwanted word, make two audio-only cuts and disable the piece between them. On Edit, temporarily turn off the chain-link Linked Selection button, press B, and click the audio at the start and end of the unwanted section. Press A, select only the middle audio piece, and press D. Re-enable Linked Selection when finished. This leaves the timeline duration unchanged; do not ripple-delete the gap. For a softer reduction without extra edit points, use four Volume keyframes. Make the track tall enough to see its gain line. On Fairlight, enable Fairlight > Show Clip Gain Line if needed. Then: 1. Option-click (macOS) or Alt-click (Windows) directly on the audio clip's gain line just before the reduction should begin. 2. Add a second keyframe at the point where the reduced level should be reached. 3. Add a third where that reduced section should end, then a fourth a little later to restore the surrounding level. 4. Drag the gain-line segment between the second and third keyframes down. Keep the outer keyframes at the levels you want outside the reduction. 5. Play across both transitions, then listen again with the rest of the mix. Adjust the depth and spacing until the change sounds right. Keep the keyframes at separate time positions. Changing a parameter on an existing keyframe changes its value; it does not create two simultaneous gain values at that frame. Short sloping transitions help avoid an abrupt level jump. A quieter waveform is not proof of complete silence. Use the disabled middle piece when the sound must be excluded. Fairlight also lets you highlight a range with the Edit Selection tool and adjust the Clip Gain line; Resolve creates keyframes at the boundaries automatically. Zoom around neighboring words before adjusting the range. Clip gain changes that item, not the entire track's mixer fader. ![Four audio gain keyframes lowering a section with transitions in DaVinci Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-mute-split-audio-gain-v2.webp) The inner segment lowers the level; the surrounding keyframes define the transitions. This example does not demonstrate complete silence. AI-assisted annotation based on Blackmagic’s clip-adjustment interface. Tap to enlarge. ## Separate Audio from Video Keep picture and its associated audio linked for normal edits. Temporarily suspend Linked Selection for an audio-only change; unlink the items only when you actually need to break their relationship. Neither method should be used as a shortcut for repairing an existing sync error. ### Option 1: Unlink Clips (Permanent Until You Re-link) Select the associated items and choose Clip > Link Clips, or use Option+Command+L on macOS / Alt+Ctrl+L on Windows with the default mapping. The chain indicators identify linked items. To link them again, first make sure picture and sound are correctly aligned, select both items, and use the same command. Linking does not move mistimed audio back into sync. ### Option 2: Alt/Option Key (Temporary Override) Hold Option on macOS or Alt on Windows while clicking the audio item to select it without its linked picture. Check the highlight before editing. For several audio-only cuts or trims, temporarily turn off the chain-link Linked Selection button instead, then restore it afterward. This changes how the items are selected; it does not delete their stored link. ### Option 3: Extract Audio (Separate File) In Media Storage, right-click the source video and choose Extract Audio, choose a destination, then click Extract. Resolve writes the channels to a standalone WAV file. Import that WAV into the Media Pool if the project needs it. Extract Audio creates a file on disk and doesn't change the link between existing timeline items. Use it for an external audio file or handoff, not as a substitute for Linked Selection during routine editing. ## Split or Cut Audio Clips For a cut at the playhead on the Edit page, select the intended audio item and choose Timeline > Razor, or use Cmd+B on macOS / Ctrl+B on Windows in the default keyboard mapping. Confirm that its linked picture is not selected if the cut must affect sound only. B by itself is different: it enters Blade Edit Mode so you can click the cut location. For several audio-only cuts, temporarily disable Linked Selection, press B, and click the required points on the audio item. Press A to return to Selection mode, inspect the new boundaries, then restore Linked Selection. Do not assume a Blade click can never cut the linked picture; the linking state matters. Timeline > Split Clips (Cmd+backslash on macOS / Ctrl+backslash on Windows) is the separate playhead split command. Before a track-wide cut, clear unwanted clip selections and check the red destination-track controls and track locks. The [Resolve 20.2 track-control update](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20.2%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) moved the former Auto Track Selector role to the red right-hand controls; the blue source controls are different. Sync Lock governs ripple participation separately. On Fairlight, select the required tracks and use Timeline > Split Clip or Timeline > Razor. Check the active page and keyboard preset rather than assuming every cut command has identical scope. If a clip should be audible but isn't, stop editing and use the no-audio troubleshooting path: follow the signal from clip and track meters to the bus and monitor output before changing links or making more cuts. ## Fix the Common Mute and Split Mistakes ### The video turned gray when you pressed D If the same items are still selected and all were enabled before the mistake, press D again to restore them. Otherwise, check their individual Enable Clip states. Then Option-click or Alt-click only the audio item and disable that. You do not need to unlink a synchronized pair just to make one temporary selection. ### Split Clips cut the wrong tracks Undo immediately. Check the actual clip selection, red destination-track controls and track locks before trying again. For one audio item, disable Linked Selection and use a deliberately targeted Blade click, then restore the linking state. The [dedicated split-video guide](https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/) covers through edits, ripple behavior, and separate A/V cuts in more depth. ### Audio moved out of sync with picture Undo the independent move, restore the matching position, and confirm the chain and sync-offset indicators before continuing. Linked Selection protects normal edits only while it's active; permanent Link Clips defines which items belong together. ### The clip is silent but no mute state is visible Follow the signal instead of cutting again. Check clip gain, track Mute and Solo, the mixer, the main bus, and monitoring. The [Resolve no-audio checklist](https://davinciresolveclub.com/davinci-resolve-no-audio/) separates an intentional disabled clip from a routing, device, or media problem. ## Before You Export or Keep Mixing Clear temporary Solo states and check every track and clip that should reach the final mix. Keep intentional mutes. The monitor speaker control and DIM change your listening level; track Mute, Solo, disabled clips and clip gain change the mix being delivered. Render a short check and listen to the exported file, not just timeline playback. For a sound-only deliverable, follow the [audio-only export workflow](https://davinciresolveclub.com/export-audio-davinci-resolve/) to choose the format, codec and output bus. You do not need to mute video tracks to export an audio file. ## Frequently Asked Questions ### How do I mute all audio in a DaVinci Resolve timeline? For a silent exported file, disable Export Audio on the Deliver page. For timeline playback only, use the toolbar audio Enable/Disable control; it doesn't change the mix sent to delivery. Track Mute and disabled clips do affect output, so don't use them as monitoring-only controls. ### Why can't I find the mute option when I right-click an audio clip on the Edit page? Resolve 21 labels the clip command Enable Clip. Select the audio item and press D or toggle Enable Clip to disable it. Older guides and Fairlight versions may call the same idea Mute Clip. Lowering the Volume overlay is a separate gain adjustment. ### Does muting affect the exported video? Track Mute, Solo states, disabled clips and lowered clip gain affect delivery. The toolbar audio Enable/Disable and DIM controls affect what you hear in the room, not the rendered mix. Check both track and clip states before adding a render job. ### Can I mute audio without splitting the clip? For the whole clip, yes: select its audio item and press D. To reduce only part without adding cuts, place four Volume keyframes at separate positions and lower the segment between the inner pair. Leave space for the transitions. That is a gain adjustment, not proof of complete silence; split and disable the middle item when the sound must be excluded. ### What's the difference between unlinking and extracting audio in DaVinci Resolve? Link Clips changes the relationship between timeline items; it creates no new media. Extract Audio reads a source clip from Media Storage and writes its audio channels to a standalone WAV file on disk, which must be imported if you want it in the project. ### How do I re-link audio and video after separating them? Align the matching audio and video, select both, and choose Clip > Link Clips. The default shortcut is Option+Command+L on macOS and Alt+Ctrl+L on Windows. Check the chain indicators and sync before moving either item; linking alone does not correct a timing offset. ### How to Export Video in DaVinci Resolve 21 URL: https://davinciresolveclub.com/export-video-davinci-resolve/ Last updated: 2026-09-13T10:39:56.000Z For a normal MP4 video, open Deliver, choose Custom Export, set Format to MP4 and Codec to H.264, and use Single Clip. Check picture, audio and range before adding the job to the queue. Quick Export is faster when a preset already fits the job. For YouTube settings, audio-only output, transparency, captions or render errors, use the [DaVinci Resolve export settings hub](https://davinciresolveclub.com/davinci-resolve-export-settings/) to open that focused guide; stay here for the complete Quick Export and Deliver workflow. ## Quick Export: the fast path File > Quick Export is the shortest route to a local file or supported upload service. The [DaVinci Resolve 21 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) says it's available across Resolve pages. On the Cut, Edit, Fusion or Color page, timeline In and Out marks limit the export; with no marks, Quick Export renders the entire timeline. [![DaVinci Resolve 21 Quick Export window annotated from preset selection to export](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-export-video-quick-export-v2.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-export-video-quick-export-v2.webp?ref=davinciresolveclub.com) Annotated Quick Export reference: 1 open File > Quick Export; 2 choose a preset; 3 check its details, then use Export on the right. The cyan outline locates the button, not its enabled state. AI-assisted annotation correction. Tap to enlarge. Choose File > Quick Export, select one of the presets available in your installation, click Export, choose the folder and filename, then click Save. Blackmagic currently lists presets for H.264, H.265, ProRes masters and services such as YouTube, Vimeo and TikTok; the exact set varies with platform, version and configured accounts. Treat a service preset as a fast starting point, not proof that a high-stakes delivery meets a client or broadcaster specification. Check the resulting resolution, frame rate, audio and file before upload. For a review copy, the speed is usually the point; for a master, use a written delivery spec. Quick Export honors timeline In and Out marks, so it can make a partial export. It doesn't expose the Deliver page's full manual bitrate and audio controls, Individual Clips options or multi-job Render Queue. Use Deliver when those controls matter. To reuse your own MP4 settings, configure a Single Clip job on Deliver first. In the Render Settings three-dot menu, choose Save as New Preset, enter a name, check Add to quick export and save. That preset appears in Quick Export; Individual Clips settings cannot be saved this way. ## The Deliver page in seven steps For a basic export, work from left to right: Render Settings, the timeline and viewer, then the Render Queue. You can queue a master, review copy and upload file with different ranges or settings, check every job, and render them in sequence. [![DaVinci Resolve 21 Custom Export and Single Clip controls annotated for a finished video](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/custom-export-resolve21.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/custom-export-resolve21.webp?ref=davinciresolveclub.com) Expanded preset menu and separate render-mode detail: 1 choose Custom Export; 2 set name and location; 3 Single Clip makes one program; 4 Individual Clips is for a planned handoff. The open menu obscures other settings. Annotated interface reference; tap to enlarge. 1. Open Deliver with the rocket icon at the bottom of the workspace. 2. Choose Custom Export, then enter a filename and choose the Location folder. 3. Choose Single Clip for one finished video and enable Export Video. 4. For a compatibility-first web file, set Format to MP4 and Codec to H.264 where supported. Use a different format when the destination requires it. 5. Set the required resolution and frame rate. Do not change frame rate merely to imitate a preset. 6. Enable Export Audio, choose the required codec and output track or bus, and check that it carries your mix. 7. Choose Entire Timeline or In/Out Range. Click Add to Render Queue, review the saved job, then use the queue’s render button. Add to Render Queue does not start encoding. To inspect a saved job, use its pencil icon: that restores the job’s settings and range. Make any correction, then click Update Job; changing controls without updating the job does not fix the queued copy. Show Job Details in the queue’s three-dot menu helps you compare resolution, format, frame rate, audio and duration. MP4 and QuickTime/MOV are containers; H.264 and H.265 are video codecs. Choosing H.264 does not by itself guarantee an MP4 file. If a saved job still produces MOV, edit that job with the pencil, change Format to MP4, and click Update Job. Renaming the extension does not change the container. Before starting, check which jobs are selected. A selection restricts rendering to those jobs; with none selected, the queue can render all jobs. Click an empty part of the queue to clear a selection when you want the full batch. The button may be labelled Start Render or Render All depending on the build and selection. [![DaVinci Resolve 21 Render Queue annotated for job checks and offline media warning](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-queue-preflight-resolve21.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/render-queue-preflight-resolve21.webp?ref=davinciresolveclub.com) Render Queue reference: inspect the job, use its pencil icon to edit, and start rendering only after checking the saved settings. The separate offline-media warning is a reason to cancel and repair the source. Annotated interface reference; tap to enlarge. The MP4/H.264/AAC path is not universal across operating systems. In particular, Linux has separate H.264/H.265 licensing and GPU requirements and does not list native AAC encoding. Check the [platform-specific codec table](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com) rather than copying a Windows or Mac preset blindly. ## YouTube export settings: official SDR bitrates As checked on September 13, 2026, YouTube's [recommended upload encoding settings](https://support.google.com/youtube/answer/1722171?ref=davinciresolveclub.com) publish target bitrates rather than minimums. Use the row that matches both resolution and frame-rate band, and keep the source frame rate instead of converting only to chase a different number. | YouTube SDR target | Format / codec | Recommended video bitrate | Audio | | --------------------- | ------------------------ | ------------------------- | ----------------------- | | 1080p, 24–30 fps | MP4 / H.264 High Profile | 8 Mbps | AAC-LC stereo, 384 kbps | | 1080p, 48–60 fps | MP4 / H.264 High Profile | 12 Mbps | AAC-LC stereo, 384 kbps | | 2160p (4K), 24–30 fps | MP4 / H.264 High Profile | 35–45 Mbps | AAC-LC stereo, 384 kbps | | 2160p (4K), 48–60 fps | MP4 / H.264 High Profile | 53–68 Mbps | AAC-LC stereo, 384 kbps | Uploading 4K is not a way to choose the codec every viewer receives. Check the uploaded picture after YouTube finishes processing, rather than promising a particular VP9 or AV1 result. The values above are YouTube's recommended SDR upload bitrates, not minimums and not a guarantee of final playback quality. Match the source frame rate, use progressive scan, High Profile H.264 and BT.709 for SDR. The [dedicated YouTube export settings guide](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/) covers GOP, bitrate and upload-specific checks; for Instagram, TikTok or a client portal, use that destination's current specification instead. ## Audio settings you should not skip Audio has its own controls in Render Settings. A timeline that sounds correct can still render silently if Export Audio is off, the wrong output track or bus is selected, or a required clip, track or main output is muted. Open the Audio panel in Render Settings and enable Export Audio. Then choose the audio format, codec, sample rate and output source required by the destination. Watch the timeline's main output meter once before queuing the job. If the meter or delivered file is silent, follow the [no-audio signal-path checklist](https://davinciresolveclub.com/davinci-resolve-no-audio/) before changing codecs. [![Audio-only WAVE export controls and the project-specific output bus menu in Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/export-audio-panel.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/export-audio-panel.webp?ref=davinciresolveclub.com) Audio-only WAVE/PCM example, not the MP4 audio panel: 1 enable audio; 2 choose format and codec; 3 match the delivery sample rate; 4 choose the bus carrying your mix. Bus names depend on the project. Annotated interface reference; tap to enlarge. - AAC-LC for a web upload. YouTube's current recommendation for stereo is 384 kbps; use the platform's own specification for other destinations. - Linear PCM for a lossless master or handoff when the delivery specification calls for PCM. Container, bit depth, sample rate and channel layout must match that specification. - Output track or bus: choose the main program output or the explicitly requested stem. A correct codec can't repair the wrong source selection. ## Single Clip vs Individual Clips This setting answers a structural question: should the selected range become one finished program or a set of media files for conform, VFX or handoff? It isn't a quality switch. Single Clip combines the selected range into one output and bakes most timeline effects into that program. Individual Clips creates one file per timeline clip, preserves source-oriented timecode and frame-rate behavior, and exposes options such as Render Timeline Effects and Render at Source Resolution. Those options make it useful for round trips, but they must be configured for the handoff rather than assumed. Choose Single Clip for a completed edit, client review file, social upload or normal master that must play as one program. Choose Individual Clips only when the receiving workflow explicitly needs separate files and tells you how to handle effects, source resolution, handles, filenames and audio. ## Free vs Studio export limits As checked on September 13, 2026, Blackmagic's [Free and Studio feature comparison](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) puts the free-version ceiling at Ultra HD 3840 × 2160 and 60 fps. Studio supports higher resolutions up to 32K and frame rates up to 120 fps, plus accelerated H.264/H.265 hardware encoding and additional professional 10-bit workflows. Resolution limits and codec availability are separate: the exact format, profile and acceleration path still depends on operating system, hardware and container. UHD 4K isn't a Studio-only export: the free version reaches 3840 × 2160 at up to 60 fps. The upgrade boundary appears when the required raster is wider than UHD, the frame rate exceeds 60 fps, or the requested codec, bit depth or hardware-encoding path is unavailable in the free build on that platform. The [Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) separates those limits from unrelated Studio features. ## Four export problems to check first When a render or delivered file is wrong, isolate the symptom before changing presets. These four checks cover the range, signal and quality choices most likely to explain the result. Export has no audio. Confirm Export Audio is enabled, then check the selected output track or bus in Render Settings. In Fairlight, verify that the audible tracks reach the intended main output and that clips, tracks, Solo/Mute states and the main output aren't excluding the mix. Individual Clips is a different workflow, not a universal explanation for silence. The file is much larger than expected. Check the codec before the bitrate: ProRes and DNxHR masters are meant to be substantially larger than H.264 review files. For bitrate-controlled H.264, compare the Quality setting with the destination's recommended range and confirm that the number is entered in the unit Resolve displays. Colors look different after export. For SDR YouTube delivery, keep the pipeline and output tagged consistently as BT.709/Rec.709, then compare the file in the actual target player. Rec.709-A changes how Apple-oriented workflows interpret gamma; it isn't a universal fix. Don't change tags until you know whether the mismatch comes from color management, output tags, the player or the display. The render is slow. First identify the expensive clip or effect and confirm Resolve is using the intended GPU. To reuse cached pictures in the final render, the job must enable Use Render Cached Images. Use it for final output only when the cache codec and resolution are suitable for that delivery. If the job stops or reports an error, switch to the [render-failed diagnostic](https://davinciresolveclub.com/davinci-resolve-render-failed/) instead of changing several export settings at once. ## Export only part of a timeline For Deliver, use Single Clip, mark the required section with I and O, then choose In/Out Range before adding the job. Check the displayed first frame, last frame and duration. Individual Clips snaps the range to clip boundaries, so it is not the mode for an exact partial-clip excerpt. Quick Export also honors timeline In and Out marks; clear the marks when you want the whole timeline. For a long or expensive timeline, queue a short representative range first. Check picture, audio, captions, color tags and playback in the target application, then queue the full program with the verified settings. ## Find the finished export The Location field is the destination of the current job, not automatically the project library or source-media folder. Set it before adding the job and include the destination in your queue check. After rendering, right-click the completed job and use the file-location command available in your build: Reveal in Finder on macOS or Open File Location on Windows. Reveal in Media Storage opens it in Resolve’s media browser. You can also open the saved Location folder directly. If the destination is shared or removable storage, confirm it's mounted and writable before starting. A clear folder plus a versioned filename is safer than trying to reconstruct the path after the queue finishes. Open the completed video outside Resolve. Check the beginning and end, duration, resolution, picture, audible channels and captions in the player or service that will receive it. For an important delivery, watch the whole file. A completed job tells you the render finished; it does not prove you chose the right content or settings. ## Frequently Asked Questions ### How do I export an MP4 from DaVinci Resolve? On Deliver, choose Custom Export and Single Clip. Enable Export Video, set Format to MP4 and Codec to H.264 where supported, match the required resolution and frame rate, and enable Export Audio with the correct output source. Check the range, add the job to the queue and start rendering. Linux has different codec and audio support, so check its support table before choosing this combination. ### Can the free version of DaVinci Resolve export 4K? Yes. The free version exports up to Ultra HD 3840 × 2160 at 60 fps. DCI 4K 4096 × 2160 is wider than that free-version limit; resolutions above UHD and frame rates above 60 fps require Studio. ### Why does my DaVinci Resolve export have no audio? Enable Export Audio, select the intended output track or bus, then follow the signal in Fairlight from audible clips and tracks to the main output. Clear unintended Mute or Solo states and confirm the main output meter moves before adding a new render job. ### What's the best export format for YouTube? YouTube recommends H.264 in an MP4 container, High Profile, progressive scan, the same frame rate as the source and BT.709 for SDR. Its current SDR video recommendations are 8 Mbps for 1080p at 24–30 fps, 12 Mbps for 1080p at 48–60 fps, 35–45 Mbps for 4K at 24–30 fps and 53–68 Mbps for 4K at 48–60 fps. ### How do I export only part of my timeline? Mark the timeline with I and O. On Deliver, use Single Clip and choose In/Out Range before adding the job. Quick Export uses the timeline marks automatically; clear them for the entire timeline. Check the displayed duration before rendering. ### Does DaVinci Resolve export ProRes and DNxHR on Windows? Yes. Blackmagic lists both Apple ProRes and DNxHR encoding for Windows. For ProRes, choose QuickTime as the container and an available Apple ProRes profile; DNxHR is another intermediate option, not a workaround you always need. Check the container, profile and installed build against the [codec support table](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com) before accepting a delivery specification. ### How to Split a Video in DaVinci Resolve URL: https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/ Last updated: 2026-09-13T10:01:23.000Z To split a video in DaVinci Resolve, press B on the Edit page and click the clip where you want the cut, then press A. For a cut at the playhead, use Timeline > Split Clips: Cmd+\\ on Mac or Ctrl+\\ on Windows in the default preset. Check which clips are selected and whether linked audio should be cut too. Splitting adds an edit point; it does not remove frames or create separate media files. If the page layout is still new, start with the [DaVinci Resolve learning path](https://davinciresolveclub.com/davinci-resolve-tutorial/); here, the focus is cutting without losing track of linked audio or ripple scope. Choose the method by the scope of the edit: - Blade Edit Mode (B): click the cut position on a clip; linked audio can follow - Split Clips (Cmd+\\ / Ctrl+\\): cut at the playhead, with selection and track scope checked first - Razor (Cmd+B / Ctrl+B): another cut command, not the same as pressing B alone - Track locks: protect material that must stay untouched - Linked Selection: choose whether linked picture and audio are selected together - Scene Cut Detection: recover cuts from a flattened finished video ## How to Split a Video in DaVinci Resolve Using the Blade Tool Use the Blade tool when pointing at the cut is easier than placing the playhead. It cuts where you click. Keep Linked Selection on for a normal picture-and-sound edit; do not assume that clicking the video leaves its linked audio untouched. [![Edit timeline with Blade tool and the playhead marked for two cutting methods](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-split-video-blade-playhead-v2.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-split-video-blade-playhead-v2.webp?ref=davinciresolveclub.com) 1: Blade cuts where you click. 2: Split Clips cuts at the playhead. Check selection and linked audio first. AI-assisted annotations on a Resolve interface reference; tap or click to enlarge. On the Edit page: 1. Open the Edit page and locate the clip. Lock unrelated tracks that must not change. 2. Press B to enter Blade Edit Mode. 3. Click the required frame on the clip. Check the new boundary in both picture and linked audio. 4. Press A to return to Selection mode before moving or trimming pieces. If you're working through your first project, our [DaVinci Resolve beginner tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) covers the full Edit page interface before you start making cuts. Use J, K and L to find the frame, then zoom only when the visual or audio transition needs closer inspection. The Blade cursor cuts where you click, not automatically at the playhead, so watch the blade indicator before committing the edit. For a one-sided cut, decide what should happen to the audio before using the blade. Temporarily turn Linked Selection off when you need the picture cut without its linked sound, and inspect the remaining link relationship afterwards. For a synchronized cut through several tracks, the playhead method below is easier to control. ## How to Split a Video with a Keyboard Shortcut There are three controls worth separating. B changes the pointer to Blade Edit Mode. Cmd+B on Mac or Ctrl+B on Windows invokes Razor in the standard preset; [Blackmagic’s editor training](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com) uses it after selecting a timeline clip. Cmd+\\ or Ctrl+\\ invokes Split Clips at the playhead. If you have imported another editing application’s preset, check the assigned command rather than assuming these keys still match. 1. Press A for Selection mode and click the timeline clip you want to cut. Keep Linked Selection on if its picture and audio should stay together. 2. Move the playhead inside that clip to the cut frame. 3. Choose Timeline > Razor, or press Cmd+B on Mac / Ctrl+B on Windows. 4. Inspect the new boundaries before moving or deleting either piece. For Split Clips, use Timeline > Split Clips or its Cmd+\\ / Ctrl+\\ shortcut. A manual clip selection can narrow the operation: it is not safe to assume the command always cuts every enabled track. To work by track scope instead, deselect clips first and set the track controls as described below. A selected clip can leave its first half selected after the split, so explicitly select the piece you want to change next. If a shortcut does nothing, click the timeline to give it keyboard focus, make sure the playhead is inside a clip rather than in a gap, and check the track lock. Look for a selected clip elsewhere in the timeline. Then open DaVinci Resolve > Keyboard Customization and search for Split Clips, Razor or Blade Edit Mode. Those are separate actions; a different preset or keyboard layout can explain why a shortcut from a tutorial does not work. ## How to Cut Multiple Tracks at Once For a track-wide cut, clear any manual clip selection, position the playhead and enable only the timeline tracks that should participate. In current Resolve, the red destination track selectors handle this selection role. They are not the blue source-patching controls, and they are not Sync Lock. [![Red timeline track selector, ordinary track lock and Sync Lock identified in Resolve](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-split-video-track-controls-v2.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-split-video-track-controls-v2.webp?ref=davinciresolveclub.com) 1: Red destination track selector. 2: Track lock. 3: Sync Lock. Selection, editing protection and ripple participation are different controls. AI-assisted interface annotations, not a completed edit; tap or click to enlarge. To split stacked clips at the same frame: - Deselect clips by clicking an empty area of the timeline. - In the track headers, enable the red destination controls for the video and audio tracks you want to cut; disable the others. - Lock any track that must not be edited, such as a finished music bed. - Place the playhead at the cut and choose Timeline > Split Clips. - Check every intended boundary. Restore the track controls when you finish. An ordinary track lock protects its clips from editing even when that track is otherwise targeted. Muting a track only changes playback; it is not editing protection. The toolbar’s Position Lock is another control again, so use the individual track padlock when you need to protect a track from cuts. Following an older tutorial? Resolve 20.2 replaced the old Auto Track Selector icon with the red timeline track controls. Sync Lock now independently governs whether a track follows a ripple edit on another track. Turning a red selector off is therefore not a promise that its clips will stay put during a later ripple delete. Blackmagic explains this change in its [track selection and Sync Lock update](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20.2%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com). ## Delete the middle section without moving the wrong clips On the Edit page, a split leaves both pieces in place. To remove a section, cut at its start and end, return to Selection mode and click the unwanted middle piece. Confirm that the correct audio is selected with it. Use Delete or Backspace for a lift edit that leaves a gap; use Forward Delete when you want later material to move left and close the gap. Before a ripple delete, check Sync Lock on the other tracks. It controls their participation in another track’s ripple edit; it does not prevent an edit made directly on that track. Lock material that must be protected. Play across the join afterwards and check picture, speech and any music cue, not just the empty space disappearing. ## How to Split Audio and Video Separately Imported picture and production audio are normally linked, and Linked Selection is on. For an ordinary cut, keep that relationship intact so both sides stay in sync. [![Linked Selection chain button identified above associated video and audio clips](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-split-video-linked-selection-v1.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-split-video-linked-selection-v1.webp?ref=davinciresolveclub.com) 1: Linked Selection. 2: Option-click on Mac or Alt-click on Windows selects one side. The chain toggle does not relink separate pieces. AI-assisted annotations on an interface reference; tap or click to enlarge. Most one-off audio edits don't require permanent unlinking. Hold Option on macOS or Alt on Windows while selecting the audio or video side to suspend linked selection for that selection, or toggle the chain-link button temporarily. With only the intended item selected, place the playhead and choose Timeline > Razor to cut it. Check the result, then restore Linked Selection when finished. The [audio splitting guide](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/) covers the next cleanup steps without breaking sync by default. To change the link relationship permanently: 1. Select the linked clip items and toggle Link Clips from the contextual menu 2. Cut or move the audio and video sides independently 3. Select the matching items and toggle Link Clips again when they should travel together Unlinking changes which items Resolve treats as associated; it does not fix or restore sync for you. After separate cuts or moves, check that the intended picture and audio are still aligned before linking them again. Turning the toolbar chain button back on does not create a missing link between unrelated pieces. For J-cuts and L-cuts, keep the media linked, suspend Linked Selection and trim only the audio or video edit point. That changes where one side begins or ends without breaking the underlying link. ## How to Split Clips on the Resolve Cut Page The Cut page doesn't use the Edit page's Blade cursor. Put the playhead on the frame and use one of its Split Clips controls instead. On the Cut page, choose any of these equivalent routes: 1. Choose Edit Actions > Split 2. Right-click the top playhead handle and choose Split 3. Press Cmd+\\ on macOS or Ctrl+\\ on Windows 4. Click the Split Clips scissors button in the Cut page toolbar The Split Clips controls fit the Cut page's fast assembly workflow. Blackmagic's [Cut page overview](https://www.blackmagicdesign.com/products/davinciresolve/cut?ref=davinciresolveclub.com) explains Source Tape, the dual timeline and the page's one-click editing model. For detailed track-level work, switch to the Edit page. The Cut page is efficient for fast assembly, while the Edit page exposes the track headers, link controls and through-edit tools more clearly. ## How to Automatically Split Clips Using Resolve Scene Cut Detection Scene Cut Detection solves a different problem: recovering edit points from one flattened, already edited video. Don't run it on ordinary source clips just to make manual cuts. Resolve 21 provides two scene-detection workflows: Media page workflow: In Media Storage, select the file before adding it to the Media Pool, then right-click and choose Scene Cut Detection. Click Auto Scene Detect, then review the detected transitions in the dedicated window, remove false cuts, add missed cuts, and only then add the resulting clips to the Media Pool. This is the older pre-timeline workflow. **Timeline version (**[**DaVinci Resolve Studio**](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) **only):** Put the flattened file on a timeline. Lock other video tracks, and set In and Out points if only part of it needs analysis. Then choose **Timeline > Detect Scene Cuts**. The DaVinci Neural Engine splits the clip directly on the timeline. This is a Studio-only feature. See the [free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) if the Neural Engine features are a factor in your upgrade decision. Step through the detected boundaries rather than trusting the first result. If a flash or transition produces a false cut, select that through edit and delete it. Add a missed cut with Split Clips at the correct frame. Detection finds candidate boundaries; it does not reconstruct the original editor’s project, transitions or source files. ## Frequently Asked Questions ### What is the keyboard shortcut to split a clip in DaVinci Resolve? Use Cmd+Backslash on Mac or Ctrl+Backslash on Windows for Timeline > Split Clips in the default preset. Cmd+B / Ctrl+B invokes Razor. B alone enters Blade Edit Mode, where you click the cut position. Check manual clip selection, track targeting and linked audio before cutting; custom presets can assign different keys. ### How do I split a clip on the DaVinci Resolve Cut page? Place the playhead on the frame, then use Cmd+Backslash on macOS or Ctrl+Backslash on Windows, choose Edit Actions > Split, right-click the top playhead handle and choose Split, or click the scissors button. The Cut page doesn't have the Edit page's Blade cursor. ### How do I delete a section after splitting in DaVinci Resolve? On the Edit page, make a cut at the start and end of the unwanted part, then select that middle piece. Delete/Backspace performs a lift that leaves a gap. Forward Delete performs a ripple delete that closes it. Check Sync Lock and protected tracks first, because a ripple can affect other tracks. ### Can I split audio and video separately in DaVinci Resolve? Yes. Temporarily turn Linked Selection off, or use Option-click on Mac / Alt-click on Windows to select one side, then make the intended edit. Check that only the required piece changed. Link Clips changes the underlying relationship; turning Linked Selection back on does not relink pieces that are no longer associated. ### Is Scene Cut Detection available in the free version of DaVinci Resolve? The classic Media page Scene Cut Detection workflow is available before importing the file into the Media Pool. Timeline > Detect Scene Cuts is the Studio-only Neural Engine workflow. Both are for recovering edit points from a flattened program, not for making ordinary manual cuts. ### How do I rejoin two split clips in DaVinci Resolve? If the two halves are still continuous source media, select the dotted through edit and press Delete, or right-click it and choose Delete Through Edit. On the Cut page, Join Match Edit Clips rejoins matching continuous halves. Unrelated source clips can't be joined this way. ### DaVinci Resolve vs DaVinci Resolve Studio: Which Do You Need? URL: https://davinciresolveclub.com/davinci-resolve-vs-studio/ Last updated: 2026-09-12T12:29:41.000Z **Quick answer:** start with DaVinci Resolve Free. Buy Studio only when a current project needs a documented paid capability: video noise reduction, Magic Mask or another named AI tool, a supported hardware-codec path, multiple GPUs, advanced HDR or immersive delivery, or output above Ultra HD 3840 x 2160 at 60 fps. Free and Studio share the same core Edit, Fusion, Color, Fairlight and Deliver workflow. Studio doesn't make an ordinary 1080p or Ultra HD edit look better by itself. It removes specific limits. Name the blocker, test it with real media, then decide whether the current $295 US desktop license removes enough recurring work to justify the purchase. To check every feature and limit in the no-cost edition, use the [Resolve 21 Free feature inventory](https://davinciresolveclub.com/davinci-resolve-free-version-features/). For desktop, Cloud rental, iPad and hardware-bundle licensing details, use the [current Resolve price and licensing guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/). Here, the useful question is whether Studio removes a tested blocker in your work. ## Free vs Studio at a Glance Use the table to find the limit that affects your work. The 32K/120 ceiling is not a playback promise; a supported codec path still depends on your computer. | Requirement | Free | Studio adds | Decision test | | ------------------------ | ------------------------------------------------------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------ | | Desktop price | $0 | $295 US list price | Check current regional checkout | | Maximum output | Ultra HD 3840 x 2160 at up to 60 fps | Up to 32K at 120 fps | Use the delivery specification, not the largest preset | | Video formats | Supported profiles vary by OS; not a universal 8-bit-only rule | Additional professional profiles and delivery paths | Check OS, container, codec, profile, decode and encode | | Color | Core node grading, curves, qualifiers, windows, tracking and HDR grading | Temporal/AI spatial NR, Magic Mask, advanced HDR and extra FX | Test the difficult shot | | AI and text | Core manual workflows | Neural Engine, text-based editing and named AI tools | Confirm the exact command in the current release | | GPU and codecs | One processing GPU on Windows and Linux in 21.1 | Multiple processing GPUs; additional platform-dependent codec acceleration | Benchmark the real media on the finishing machine | | Collaboration | Included | Included, with paid processing and delivery additions | Choose the edition from team requirements, not collaboration alone | | Audio and delivery | Core Fairlight workflow | More Fairlight FX, immersive audio, Dolby Vision and HDR10+ | Start from the required mix and master | | Python scripting in 21.1 | Requires Studio | Python and advanced scripting | Check your automation tool’s supported builds | [![Official Blackmagic Resolve 21 page showing the Free download and $295 Studio desktop purchase](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/official-studio-pricing-hero.png)](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) Blackmagic's current US page lists Resolve 21 Free at $0 and Studio 21 at $295\. This capture was checked again on August 25, 2026; regional prices and tax can differ. Blackmagic's [current US Studio page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) lists Resolve 21 Free at $0 and Studio at $295\. Tax, regional currency and reseller totals can differ. The standard desktop Studio path is a purchase rather than a required consumer subscription. [Blackmagic Cloud rental licenses](https://help.cloud.blackmagicdesign.com/license-manager/logging-in-to-davinci-resolve/?ref=davinciresolveclub.com) can be used through a personal profile or managed by an organization; the separate iPad purchase is another licensing path. ## What Stays the Same in Free and Studio The core project architecture stays familiar after an upgrade. Media, Cut, Edit, Fusion, Color, Fairlight and Deliver work on the same project; Resolve 21 also includes the Photo page. Free is a separate edition, not a time-limited Studio trial. Work using only Free-supported native tools has no general application watermark. Blackmagic’s [Resolve 20 beginner guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Beginners-Guide.pdf?ref=davinciresolveclub.com) documents the exception: Studio-only Resolve FX display a Studio watermark in Free. Remove that effect or use Studio, then test the affected range. Third-party trial plug-ins have their own rules. For editing, both editions provide the normal timeline, trimming, tracks, titles, keyframes and page workflow. Studio adds paid processing and effects around that foundation. A locked effect in a tutorial doesn't mean the entire editing task requires Studio; there's often a manual or included route that solves the same practical need. [![Official DaVinci Resolve Studio 21 Edit page with media bins source viewer timeline mixer and metadata](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-edit-page-official-1.webp)](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) Free and Studio use the same core Edit-page architecture. This official Studio 21 frame maps the workspace; it does not mean every effect visible in a Studio installation is included in Free. Multi-user collaboration is also included in Free. This is a common comparison error. A facility may still need Studio for a paid codec, remote monitoring, advanced master or AI process, but collaboration alone is not the edition boundary stated on Blackmagic's [Resolve overview](https://www.blackmagicdesign.com/products/davinciresolve?ref=davinciresolveclub.com). ## Color: The Paid Differences That Change Real Work Free includes the core node-based Color page: primary corrections, curves, qualifiers, Power Windows, tracking, scopes and HDR grading. Those tools can finish controlled SDR work and many client projects. Studio adds specialist controls rather than replacing the grading foundation. [![Official DaVinci Resolve Studio 21 Color page with clip strip node graph HDR wheels ColorSlice and scopes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-core-color-page-official.webp)](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com) Resolve 21 Free includes the core node-based Color page. This official Studio 21 screen is a workspace reference, not a claim that every visible Studio control is unlocked in Free. The clearest Studio boundary is video noise reduction. Blackmagic names temporal and AI spatial noise reduction, including UltraNR, among Studio additions. Magic Mask and advanced HDR tools are other paid capabilities. Their usefulness depends on the shot: judge the corrected moving image, not the feature name or one successful demonstration. [![Official Blackmagic Studio advanced video noise reduction before and after comparison on a motocross helmet](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/studio-video-noise-reduction-official.webp)](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) Blackmagic uses this before-and-after example for Studio's advanced video noise reduction. Test a moving shot from the real camera; one promotional frame cannot predict detail retention or render cost. Test a representative moving shot, not one paused frame. Watch fine texture, hair, motion edges and compression artifacts, then measure render time. If careful exposure, lighting and the Free toolset already produce the required master, noise reduction is not a reason to buy a license for that job. ## Resolution, Frame Rate and Codec Support Free can finish video at up to 60 fps and Ultra HD 3840 x 2160, the consumer format commonly called 4K. DCI 4K is 4096 x 2160, so it exceeds that documented width. Check the delivery dimensions rather than relying on the 4K label. Studio’s published ceiling is 32K at 120 fps, with broader professional-format support. Input and output are separate limits: the Free 21.1 notes say it can handle unlimited-resolution media while limiting mastering and output to Ultra HD or below. A larger source file may therefore fit a UHD edit, provided its codec is supported. It does not unlock DCI 4K or 8K output in Free. Codec support depends on the container, codec, profile, bit depth, operating system and whether you are decoding or encoding. Blackmagic’s [supported-codec table](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com) is the July 2025 Resolve 20 matrix, not a new 21.1 matrix; it remained the latest listed matrix in the support catalog on September 12, 2026\. Read it alongside the release notes and test one real source clip and the required export. The platform rows matter. Windows lists OS-supported 8-bit H.264 and 8/10-bit H.265 profiles, with additional profiles and GPU acceleration in Studio. macOS lists accelerated H.264/H.265 paths without a blanket Studio-only restriction. The Rocky Linux H.264/H.265 rows require Studio. None of those rows guarantees every camera profile, GPU or 21.1 configuration. ## Performance: Studio Can Remove a Bottleneck, Not Every Bottleneck Free uses GPU image processing too. Blackmagic’s 21.1 notes limit Free to one processing GPU on Windows and Linux, not universally on macOS. Studio supports multiple GPUs and additional hardware-codec paths, but codec acceleration has the OS-specific exceptions above. Test the actual source, effects and export: an upgrade cannot guarantee that storage, memory or a particular stream stops being a bottleneck. Build a short representative timeline with the hardest source, the actual grade, one heavy effect and the final preset. Record playback stability and export time before and after the proposed change. The maintained [Resolve 21 system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) help screen the machine, while the test determines whether Studio removes this project's bottleneck. ## AI, Text and Tracking Tools Studio includes the DaVinci AI Neural Engine, text-based editing and Magic Mask. Resolve 21 also introduced and revised AI-assisted tools, but edition boundaries can change between releases. Don't assume that every command with AI in its name has the same license or that an older Resolve 19 comparison still applies. For a tool-by-tool breakdown, use the [Resolve 21 AI tools guide](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/). For this buying decision, name the task first: find clips by content, build a text-based rough cut, isolate a subject, reframe a shot, clean dialogue or generate speech. Verify that exact command in the current Blackmagic page or manual, then test its output and correction time. A license unlocks the tool; it doesn't guarantee an acceptable result or real-time playback. Masks can need edge repair, transcription can need correction, and generated or separated audio requires listening review. Include that review time when deciding whether the paid shortcut saves work. If you use automation, check the build before updating: the [21.1 Free release notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) move Python scripting to Studio and say advanced scripting now requires Studio. [Studio 21.1](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) also adds native MCP integration. This does not mean every Fusion macro or title template has become paid. Confirm how your particular tool connects to Resolve and which builds its developer supports. ## Fairlight and Professional Delivery Free contains the core Fairlight editing and mixing workflow, including track processing, routing and automation needed for many YouTube, podcast, documentary and client jobs. Studio adds more Fairlight FX and current AI-assisted audio tools, plus immersive-audio capability. Upgrade when the required cleanup or delivery calls for the paid tool. Voice Isolation, Music Remixer and Dialogue Separator can solve narrow problems; Dolby Vision, HDR10+ and immersive formats are delivery requirements, not badges for an ordinary stereo web master. Start with the client's specification and monitoring path. Studio does not include every third-party delivery license. Advanced Dolby Vision trim controls require a separate Dolby license; encrypted DCP requires EasyDCP licensing. The codec matrix also lists a Dolby software license for rendering Dolby Atmos formats. Check the exact format, platform and client specification rather than assuming every IMF or DCP operation is unlocked by buying Studio. ## Licenses, Updates and Hardware Bundles Do not buy Studio on a promise of free upgrades forever. In an [April 2021 official forum response](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=140333&ref=davinciresolveclub.com), Blackmagic staff said the company did not formally commit to that. Buy for the capabilities available now, and check the release notes before changing a working installation. The current [Speed Editor technical specification](https://www.blackmagicdesign.com/products/davinciresolve/techspecs/W-DRE-08?ref=davinciresolveclub.com) lists a DaVinci Resolve Studio activation key under What’s Included. For used hardware, older stock or a reseller bundle, get written confirmation of the exact SKU and included key before buying. [![Official Blackmagic Speed Editor specification listing a DaVinci Resolve Studio activation key in the box](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/official-speed-editor-included.png)](https://www.blackmagicdesign.com/products/davinciresolve/techspecs/W-DRE-08?ref=davinciresolveclub.com) The current Speed Editor specification lists a Studio activation key under What's Included. Used units, old stock and regional bundles still need exact-SKU confirmation. Other Blackmagic cameras, panels and bundles vary. Compare the exact SKU and What's Included section rather than subtracting $295 from every hardware price. If the editing controls aren't useful, a bundle isn't automatically better value than the software license alone. ## Who Should Buy Studio **Stay on Free** when the camera originals decode correctly, the needed grade and audio work fit the included tools, and the final master stays within Ultra HD 60\. This includes many beginner, YouTube, education and paid client workflows. Free is the correct edition whenever it completes the specification. Buy Studio when a repeated, tested blocker maps to a documented paid capability: video noise reduction, Magic Mask or another required AI tool, an unavailable codec profile or hardware path, multiple processing GPUs, output beyond Ultra HD 60, Python scripting in 21.1 or a required advanced delivery feature. Confirm any additional license the deliverable needs. **Don't upgrade yet** when the problem is vague. Slow playback may be storage, cache, GPU memory or source-codec related. A failed render may come from one clip or effect. Diagnose the actual failure before treating the edition as the cause. If you are still choosing an editor, start with the [Resolve comparison hub](https://davinciresolveclub.com/davinci-resolve-comparisons/). The [Premiere Pro comparison](https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/) covers the Adobe workflow and subscription decision; the [Final Cut Pro comparison](https://davinciresolveclub.com/davinci-resolve-vs-final-cut-pro/) covers the Mac alternative. Keep that choice separate from deciding which Resolve edition you need. ## Free vs Studio FAQ ### Is DaVinci Resolve Free enough for most editors? Yes, when the source media works, the needed tools are included and the master stays within Ultra HD 3840 x 2160 at 60 fps. Start with Free and test a representative project before paying for Studio. ### How much does DaVinci Resolve Studio cost? Blackmagic currently lists the desktop Studio 21 license at $295 in the United States. Regional currency, tax and reseller totals can differ. ### Is DaVinci Resolve Studio a one-time purchase? The standard desktop Studio license is sold for $295 rather than as a required consumer subscription. Blackmagic Cloud rental licenses can be used through a personal profile or an organization, and the separate iPad in-app purchase is another licensing path. ### Which version is better for YouTube? Free is enough for most YouTube work that fits Ultra HD 3840 x 2160 at up to 60 fps. Studio becomes useful when the footage needs paid noise reduction, a Studio-only AI tool, a supported hardware-codec path, or output beyond that ceiling. ### Can I upgrade from Free to Studio without losing projects? Yes, the editions share the Resolve project system, but changing versions needs care. Back up both the Project Library and individual projects first. Blackmagic warns that projects created or opened in 21.1 cannot be reopened in 20.3.2, even though the library remains compatible. Test a copy and verify media, plug-ins and output before switching production work. ### Does DaVinci Resolve Free include noise reduction or Magic Mask? The current Blackmagic product comparison assigns temporal and AI spatial video noise reduction plus Magic Mask to Studio. Free still includes the core Color page, trackers, qualifiers and node workflow. ### Does DaVinci Resolve Speed Editor include Studio? Blackmagic's latest Speed Editor technical specification lists a DaVinci Resolve Studio activation key under What's Included. Confirm the exact SKU and key status for used hardware, old stock or reseller bundles. ### Does DaVinci Resolve Free include collaboration? Yes. Blackmagic explicitly lists multi-user collaboration in the Free edition. Studio may still be required for paid processing, monitoring or delivery capabilities used by the team. ### Are future DaVinci Resolve Studio upgrades free? Do not assume future major upgrades are guaranteed free. Blackmagic staff explicitly declined a formal commitment in an April 2021 forum response. Check the current terms and release notes, and buy for features available now. ### How Much Does DaVinci Resolve Cost? URL: https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/ Last updated: 2026-09-09T01:52:48.000Z DaVinci Resolve is free. The standard Studio desktop license costs **$295 US as a one-time purchase**. Blackmagic Cloud documents a separate **$30/month rental** in its US example. Apple sells the Mac App Store edition for **$299.99**, while iPad Studio is a separate **$94.99 in-app purchase**. Check the platform before paying: these licenses are not interchangeable. Prices checked **September 9, 2026**. The [Blackmagic Studio product page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com), [Cloud rental guide](https://help.cloud.blackmagicdesign.com/license-manager/renting-davinci-resolve-studio-licenses/?ref=davinciresolveclub.com) and Apple listings below are the reference points. Regional tax, currency and reseller totals can differ. Buy for the features available today. Blackmagic currently sells Studio 21 for $295 and provides its current Studio installers without a separately listed upgrade charge. That continues its no-fee-upgrade history; it is not a promise that every future major release will be free. ## DaVinci Resolve Pricing: Free vs Studio at a Glance Free includes the core Edit, Color, Fusion and Fairlight workflows; Studio adds paid processing and delivery capabilities. Use the [Resolve Free feature guide](https://davinciresolveclub.com/davinci-resolve-free-version-features/) for the full no-cost boundary and the [Free versus Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) for feature-by-feature buying decisions. The dividing line is the required source, tool and output, not whether the editor is a beginner or professional. On a narrow screen, swipe a table sideways to see all columns. With a keyboard, focus the table and use the arrow keys. | Item | Free | Studio | | --------------------------------------------- | ------------------------------ | ----------------------------------------------------------------------- | | US desktop list price | $0 | $295 one-time | | Desktop output ceiling | Ultra HD 3840 × 2160 at 60 fps | Up to 32K at 120 fps | | Core Edit, Color, Fusion, Fairlight | Included | Included | | Multi-user collaboration | Included | Included | | Temporal and AI spatial video noise reduction | No | Yes | | Text-based editing and Magic Mask | No | Yes | | Multiple processing GPUs | No on Windows/Linux | Yes on supported systems | | Dolby Vision and HDR10+ grading/rendering | No | Yes | | Cloud rental | Not applicable | $30/month per license in the current US example; separate from purchase | Studio also adds over 45 additional Resolve FX, immersive-audio features, professional HDR scopes and supported H.264/H.265 hardware decode and encode paths. Exact format support varies by operating system, container, codec, profile and bit depth. ## Free Version: What You Actually Get Free includes Cut and Edit, node-based Color tools, Power Windows, curves, qualifiers, scopes, Fusion compositing and Fairlight audio. It is a free edition rather than a time-limited trial. Ordinary Free workflows export without a Blackmagic watermark, but using [Studio-only effects in Free can add one](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=88158&ref=davinciresolveclub.com). Remove the paid effect or use a properly licensed Studio installation before delivering that shot. [![Official Blackmagic DaVinci Resolve Studio 21 page showing Free download and $295 Studio purchase options](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/official-studio-pricing-hero.png)](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) Blackmagic's current US Studio page lists Resolve Free at $0 and Resolve Studio 21 at $295\. The August 16 browser capture was rechecked on August 25, 2026; tax, currency and reseller totals can differ. The published desktop output ceiling is Ultra HD 3840 x 2160 at 60 fps. Source decoding and output resolution are separate limits, so footage above 4K does not automatically require Studio. Test your actual camera file. Also check the [current Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/): Studio 21.1 has additional memory requirements for advanced AI and background tasks. Paying for the license does not make an under-equipped computer meet them. ## Studio Cost: Is the $295 Worth It? Pay for Studio when a specific capability removes enough work or solves a delivery requirement to justify $295\. A tutorial calling Free limited is not a reason to buy, and neither is a camera recording above 4K by itself. The reasons to consider an upgrade are: - You repeatedly need Studio video noise reduction or a named paid AI tool - A client requires output above Ultra HD 60 or a Studio-only HDR/package format - Your exact codec and supported hardware benefit from Studio acceleration - A Windows or Linux workstation can use multiple processing GPUs for the real workload Stay on Free when your source files open correctly, the grade and audio work don't need paid tools, and the final master fits Ultra HD 60\. Collaboration and standard HDR grading are already included in Free, so neither is a reason to upgrade by itself. Some specialist deliverables add another license cost. Blackmagic lists Dolby Vision support in Studio, but advanced Dolby Vision trim controls require a separate Dolby license. Encrypted DCP creation requires a separate EasyDCP license. Confirm those costs if your client needs that exact deliverable; ordinary editing does not require either add-on. [![DaVinci Resolve Free, $295 desktop Studio, $30 cloud rental and $94.99 iPad Studio access paths](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/purchase-paths-20260825-v2.png)](https://help.cloud.blackmagicdesign.com/license-manager/renting-davinci-resolve-studio-licenses/?ref=davinciresolveclub.com) Four separate paths: Free desktop, the $295 US desktop purchase, a $30/month per-license Blackmagic Cloud example for personal or organization profiles, and the separate $94.99 US iPad purchase. In the Free card above, no watermark refers to ordinary Free tools. A Studio-only effect can still add a watermark. The Mac App Store purchase is an additional, separate path, covered below. ## Studio Rental Licenses The current [License Manager guide](https://help.cloud.blackmagicdesign.com/license-manager/renting-davinci-resolve-studio-licenses/?ref=davinciresolveclub.com) lets you rent Studio from a personal or organization profile. Its official example shows five licenses totalling $150 per month, which is $30 per license per month. Treat that as the documented US example and confirm the live total in the profile that will own the rental. At $30 per month, ten billed months total $300, slightly more than the $295 standard desktop list price. The licenses differ: a personal activation key covers two devices used by one person, while [each rental activates one computer](https://help.cloud.blackmagicdesign.com/license-manager/logging-in-to-davinci-resolve/?ref=davinciresolveclub.com). Rent when short-term access or team assignment fits the job better than a purchase. The rental licenses Studio running on your computer; it does not turn Resolve into a browser editor or include every Cloud service. Before renting, check the owner profile, seat count, renewal date and cancellation terms. Personal profiles can rent licenses too. Cloud project libraries and storage are separate services, so budget for them only if your workflow uses them. ## Hardware Bundles That Include Studio The current [Speed Editor technical specification](https://www.blackmagicdesign.com/products/davinciresolve/techspecs/W-DRE-08?ref=davinciresolveclub.com) lists the hardware at $435 in the United States and explicitly includes a DaVinci Resolve Studio activation key. Other cameras, panels, reseller bundles, used hardware and regional inventory must be checked by exact SKU. | Purchase | Current public price | License rule | | --------------------------------- | -------------------- | ------------------------------------------------------------------------ | | DaVinci Resolve Studio 21 desktop | $295 US list price | One-time purchase; cloud rental is separate | | DaVinci Resolve Speed Editor | $435 US list price | Current official specification includes a Studio activation key | | Blackmagic camera or panel | Varies | Check the exact product's What's Included section | | Used hardware or reseller bundle | Varies | Require written confirmation of the included license and transfer rights | At those list prices, Speed Editor costs $140 more than Studio alone. That difference is useful only if you want the controls. For a new bundle, verify the exact SKU and included activation key before checkout. For used hardware, get written confirmation of exactly which license is included and that the seller is entitled to pass it on. A key that worked once is not proof that the seller has stopped using it or kept no copy. If a listing is ambiguous, price the hardware as hardware only; do not assume a missing or shared key can be replaced for free. [![Official Blackmagic Speed Editor specifications listing the included DaVinci Resolve Studio activation key](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/official-speed-editor-included.png)](https://www.blackmagicdesign.com/products/davinciresolve/techspecs/W-DRE-08?ref=davinciresolveclub.com) The current Blackmagic Speed Editor technical specification explicitly lists a DaVinci Resolve Studio activation key under What's Included. Verify the exact SKU and reseller box contents before paying. ## Mac App Store Studio: A Separate $299.99 Purchase The [US Mac App Store listing](https://apps.apple.com/us/app/davinci-resolve-studio/id900392332?mt=12&ref=davinciresolveclub.com) sells Studio for $299.99\. This is the Mac-only App Store edition, tied to your Apple account, rather than a $295 activation key for the installer from Blackmagic. The App Store purchase cannot activate the standard Blackmagic download, and a standard key, dongle or Cloud rental cannot activate the App Store edition. Blackmagic also warns in the listing that some external panels and third-party OpenFX or VST plugins are unsupported or may be incompatible. If those tools are essential, check the standard desktop version before buying. The two channels can also publish updates on different dates. ## Resolve for iPad: Cost and App Store Purchases DaVinci Resolve for iPad is free to download. The [US App Store listing](https://apps.apple.com/us/app/davinci-resolve-for-ipad/id1581363826?ref=davinciresolveclub.com) currently shows the Studio in-app purchase at $94.99\. That purchase is separate from the standard desktop activation key, dongle and Mac App Store license; regional App Store prices can differ. Check the current App Store description and your iPad model for the features you need, then confirm the in-app price on that device. Do not assume that a tool available on desktop works identically on your iPad. Budget desktop and iPad separately. Blackmagic's [explanation of the three installation and purchase channels](https://forum.blackmagicdesign.com/viewtopic.php?p=1041977&t=200521&ref=davinciresolveclub.com) distinguishes standard desktop licensing, Mac App Store purchases and iPad in-app purchases. One payment does not unlock all three. ## Resolve vs Premiere Pro: What You Pay Over Time Adobe's [US Premiere plan page](https://www.adobe.com/products/premiere.html?ref=davinciresolveclub.com) lists the individual app at $22.99 per month on an **annual plan billed monthly**. Thirteen payments at that rate total $298.87 before tax, but that is arithmetic, not a 13-month cancel-anytime offer. Compare the annual commitment and cancellation terms too. The [Resolve versus Premiere comparison](https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/) covers the editing and handoff differences. That arithmetic isn't the complete cost comparison. Premiere also includes services such as Frame.io and Adobe Express, and Creative Cloud Pro may already be required for After Effects, Photoshop or other applications. Resolve can reduce recurring software spend, but hardware, storage, plugins, training and handoffs still belong in the budget. Compare the same region, commitment, seats and included services over the period you expect to use the software. Add storage, hardware, plugins and the time needed to move projects. A lower license price can be the wrong saving if the change makes each delivery slower. ## Resolve vs Final Cut Pro: One-Time Purchase or Creator Studio Apple offers a $299.99 one-time Final Cut Pro purchase and Apple Creator Studio at $12.99 per month or $129 per year in the US. The [current Final Cut Pro pricing FAQ](https://www.apple.com/final-cut-pro/?ref=davinciresolveclub.com) keeps both options available. The subscription includes other creative apps and some premium content. Resolve's standard $295 desktop license supports macOS, Windows and Linux; the Mac App Store purchase does not cover those other operating systems. Don't compare $12.99 with $295 as if the products and access periods were identical. Compare the apps included, platform, ownership period and the workflow your team will actually run; the one-time Final Cut and Resolve prices are only $4.99 apart before tax. A price table can't decide between editing models. Run one representative job through the applications you're considering, including graphics, color, audio, one revision and export QC. ## Resolve 21: What's New and Still $295 Resolve 21 is still the $295 Studio offering on Blackmagic's US product page. The [Studio 21.1 readme](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) describes a current Studio update, not a new subscription requirement. Keep your activation key or dongle secure, and do not treat the upgrade history as a contractual promise about future releases. ![DaVinci Resolve workflow cost including license, hardware, media storage and production time](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/workflow-cost-v1.webp) Compare the same job across software access, hardware, media storage and production time. A one-time license can still sit inside an expensive workflow. Resolve 21 adds the Photo page, IntelliSearch, CineFocus, AI Speech Generator and other tools documented in the current [Resolve 21 release guide](https://davinciresolveclub.com/davinci-resolve-21-whats-new/). Many headline AI tools require Studio. Buy for a recurring task, not for the number of features in a launch list. If you are still choosing an editor rather than a license, use the [comparisons and buying guides](https://davinciresolveclub.com/davinci-resolve-comparisons/) to narrow that decision. Then verify the exact purchase channel and local total before checkout. ## Frequently Asked Questions About Resolve Cost ### Is DaVinci Resolve really free? Yes. Blackmagic offers Resolve 21 Free at $0\. It includes the core Edit, Color, Fusion and Fairlight workflow, multi-user collaboration and output up to Ultra HD 3840 x 2160 at 60 fps within the documented format limits. ### How much is DaVinci Resolve Studio? The standard US desktop license is $295\. The separate US Mac App Store edition is $299.99, and iPad Studio is a $94.99 in-app purchase. Tax, currency and reseller pricing can change the checkout total. ### Is DaVinci Resolve Studio a one-time purchase? Yes. The standard desktop path is a one-time $295 purchase and does not require a Cloud rental. Blackmagic also offers a separate rental whose documented US example is $30 per month per license. Mac App Store and iPad purchases are separate channels. ### Are future DaVinci Resolve Studio upgrades free? Blackmagic currently provides Studio 21 updates without a separately listed upgrade charge. That continues its no-fee-upgrade history. Do not read it as a published guarantee that every future major version will be free. ### Is the Studio upgrade worth $295? It's worth paying when a required Studio-only tool, codec path or delivery format removes a recurring blocker. Stay on Free when the tested media, processing and final master fit its limits. ### Is there a student discount for DaVinci Resolve Studio? Blackmagic does not list a universal public student price for the individual desktop Studio license. Institutions and regional promotions may differ, so verify any education offer directly. ### Does the Speed Editor include DaVinci Resolve Studio? The current US Speed Editor technical specification lists a DaVinci Resolve Studio activation key under What's Included. Verify the exact SKU and written reseller listing because used hardware, regional inventory and older stock can differ. ### How much is DaVinci Resolve Studio for iPad? The US App Store currently lists the iPad Studio in-app purchase at $94.99\. It's a separate purchase from the standard desktop activation key or dongle, and regional App Store pricing can differ. ### Can I use DaVinci Resolve Studio on multiple computers? [Blackmagic Design staff explain](https://forum.blackmagicdesign.com/viewtopic.php?p=1118230&t=215459&ref=davinciresolveclub.com) that a personal activation key is intended for two devices used by the same person, not two users. A dongle works on the computer where it is connected. A Cloud rental activates one computer and can be reassigned through License Manager. Mac App Store purchases follow their separate Apple-account licensing path. ### DaVinci Resolve vs Premiere Pro (2026) URL: https://davinciresolveclub.com/davinci-resolve-vs-premiere-pro/ Last updated: 2026-09-12T13:16:05.000Z **Quick answer:** Choose DaVinci Resolve when color, Fusion, Fairlight and delivery should stay inside one project, or when the Free edition already covers the job. Choose Adobe Premiere when After Effects, Photoshop, Frame.io, shared Adobe assets or an established Premiere team define the recurring workflow. The better editor is the one that creates fewer fragile handoffs for your real work. Checked September 12, 2026 against Resolve 21.1 release notes and Adobe’s stable Premiere 26.5 documentation. Beta features are identified separately. This is a workflow comparison, not a timed performance benchmark. Don't decide from a winner badge. Use one representative job with the same source files, edit brief, revision and delivery. Count relinks, application switches, rebuilt effects and QC failures. That test captures the cost a feature table usually misses. ## Resolve vs Premiere: The Practical Difference - **Resolve 21** combines Edit, Color, Fusion, Fairlight and Deliver in one project. Free is substantial; Studio is currently a $295 US one-time license. - **Premiere 26.5** is a subscription editor with direct value when Adobe applications, Frame.io, templates and Premiere-based collaborators already surround the project. - **Resolve has the deeper dedicated color-finishing architecture**, but that doesn't make every grade better by default. - **Premiere has the broader Adobe application path**, but linked applications are useful only when the project actually needs them. - **Performance has no universal winner**. Codec profile, operating system, CPU, GPU, effects, application version and Resolve edition can all change the result. ## Price and License Cost in 2026 Blackmagic currently lists [DaVinci Resolve Studio 21 at $295](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) in the United States as a one-time license. Resolve Free includes editing, node-based color, Fusion, Fairlight and output up to Ultra HD 3840 x 2160 at 60 fps within Blackmagic's documented format limits. Studio adds the Neural Engine, paid AI tools, video noise reduction, more Resolve FX, multiple-GPU support, broader professional format paths and higher delivery ceilings. Adobe lists the individual [Premiere plan at $22.99 per month](https://www.adobe.com/products/premiere/plans.html?ref=davinciresolveclub.com) in the United States on an annual commitment billed monthly, before tax. The advertised plan includes 100 GB of cloud storage, Frame.io and Adobe Express Premium, not After Effects, Photoshop or Audition. Those applications need their own entitlement or a suitable multi-app plan. Desktop Premiere has no perpetual license. At that list price, 13 months of Premiere totals $298.87 before tax, slightly above the $295 Studio license. That's arithmetic, not a universal break-even. Promotions, regional checkout, cancellation terms, credit use and the value of included services can move the decision in either direction. Recheck both product pages before purchasing. License cost is only the visible part. A Premiere subscription can be rational when shared After Effects compositions, Frame.io approvals or Adobe libraries remove work. Resolve can be less expensive when one editor can finish picture, color and audio without extra applications. If you have already chosen Resolve, the [Resolve pricing guide](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) explains purchase costs, while the [Free versus Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) helps you decide whether a paid feature is worth the upgrade. ## Editing Workflow, Timelines and Teams Both applications support professional track-based editing, multicam, proxies, captions, keyboard trimming and long-form timelines. The difference isn't whether a trim exists. It's how the edit connects to motion graphics, color, audio, review and the final master. [![Official DaVinci Resolve Studio 21 Edit page with media bins dual viewers Inspector mixer and a layered timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-edit-page-official-1.webp)](https://www.blackmagicdesign.com/products/davinciresolve/edit?ref=davinciresolveclub.com) Blackmagic's current Resolve 21 product image shows the Edit page in Studio. The page layout is shared with Free, but individual AI controls visible in the Inspector can require Studio. Resolve provides Cut and Edit pages. Cut favors rapid assembly and source-tape browsing; Edit supplies the conventional timeline, trim tools, multicam, deep keyframing and large-project controls. Editors moving from Premiere need time to rebuild shortcuts and habits, but unfamiliarity isn't evidence that the Edit page is less capable. [![Official Adobe Premiere timeline with video and audio tracks playhead time ruler work area and zoom controls](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/premiere26-timeline-official.webp)](https://helpx.adobe.com/premiere/desktop/edit-projects/change-clip-sequence/navigation-controls-in-the-timeline.html?ref=davinciresolveclub.com) Adobe's current Timeline navigation guide labels the time ruler, work area, playhead, playhead position and zoom controls. This is a real Premiere interface, not a generated mockup. Premiere’s track model, Productions and Team Projects suit teams already exchanging Adobe projects. In stable 26.5, Paper Edit can assemble a sequence from selected transcript lines, while Object Mask gains smoothness controls. Adobe’s [current release notes](https://helpx.adobe.com/premiere/desktop/whats-new/release-notes.html?ref=davinciresolveclub.com) also distinguish the accepted source formats for Generative Extend from the format of the generated extension. Check both before adding it to a delivery workflow. [Team Projects](https://helpx.adobe.com/premiere/desktop/collaborate-with-others/collaborate-using-team-projects/when-to-use-team-projects-and-when-to-use-productions.html?ref=davinciresolveclub.com) stores shared project metadata in the cloud; Productions divides large jobs into smaller project files. Neither arrangement removes the need to give editors access to the source media. Choose the collaboration setup around storage, project ownership and the people making revisions. [Dynamic Link](https://helpx.adobe.com/premiere/desktop/use-premiere-with-other-apps/working-with-other-adobe-applications/share-assets-between-after-effects-and-premiere-using-dynamic-link.html?ref=davinciresolveclub.com) connects Premiere with After Effects without an intermediate render, but Adobe requires matching major versions. A complex linked composition can still slow playback; Render and Replace is one fallback. Fusion keeps compositing inside Resolve. Inventory the motion templates, plug-ins, artists and revision path you actually need, rather than assuming either connection is automatically faster. For difficult camera media, create the same proxy test in both editors. The [Resolve proxy workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) explains the Resolve side. Measure reconnection, relink portability, one real revision and first-playback smoothness. ## Color, Motion Graphics and Finishing Resolve's Color page is built around a node graph, qualifiers, tracked Power Windows, grouped grades, versions, galleries, scopes and color-managed finishing. That architecture is a meaningful advantage when the job needs complex secondary work, many grade versions, HDR finishing or a dedicated colorist. Those controls cannot choose a look or repair a wrong color transform for you. For practical walkthroughs, use the [Resolve color-grading hub](https://davinciresolveclub.com/davinci-resolve-color-grading/). [![Official DaVinci Resolve Studio 21 Color page with clip strip node graph HDR wheels ColorSlice and RGB parade scopes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-color-page-official-1.webp)](https://www.blackmagicdesign.com/products/davinciresolve/color?ref=davinciresolveclub.com) Blackmagic's current Studio 21 Color interface illustrates Resolve's dedicated finishing architecture. It does not imply that every visible Studio control is included in the Free edition. Premiere includes Lumetri controls, curves, masks, scopes and color management for log and wide-gamut media. Adobe’s [September update](https://blog.adobe.com/en/publish/2026/09/08/generate-create-directly-in-your-timeline-with-new-ai-powered-innovations-in-premiere-after-effects?ref=davinciresolveclub.com) still identifies the new Color mode as beta, not the stable 26.5 workflow. That distinction matters when promising a client a particular workflow; it does not make current Lumetri unusable for editorial correction or branded content. Resolve becomes the clearer choice when finishing is a large part of the job. Premiere can remain the better operational fit when the grade is modest and the edit depends on Adobe graphics, templates and approvals. Test the required camera formats, monitoring path, transform order and delivery before choosing from screenshots. A Premiere edit and Resolve grade can work well, but it creates a conform. Simplify or render unsupported effects where necessary, preserve source timecode and reel metadata, send a reference movie, relink original media and compare the conformed timeline shot by shot. Decide which application owns the final export before the round trip begins. ## AI Features: Stable Tools, Credits and Limits Both editors now use AI for search, masking, speech, audio and image work. Counting every feature carrying an AI label isn't useful. Compare the exact task, edition or plan, processing location, output constraints and review time. Stable Premiere includes media intelligence, Object Masking and [Generative Extend](https://helpx.adobe.com/premiere/desktop/edit-projects/edit-with-generative-ai/generative-extend-faq.html?ref=davinciresolveclub.com). Adobe documents up to 2 seconds of generated video or 10 seconds of ambient audio. It can't create or extend spoken dialogue, clips containing music aren't eligible, and availability can depend on region and account type. Generative Extend consumes credits according to resolution and frame rate. Adobe’s [current generative-credit table](https://helpx.adobe.com/creative-cloud/apps/generative-ai/generative-credits-faq.html?ref=davinciresolveclub.com) lists 25 monthly credits for individual single-app subscriptions started on or after June 17, 2025; older eligible subscriptions have a different allocation. A small included balance is not unlimited generation. Check your account, the chosen model and the displayed charge before relying on AI for recurring work. The [Generative Media Tool](https://helpx.adobe.com/premiere/desktop/edit-projects/edit-with-generative-ai/generative-media-tool-overview.html?ref=davinciresolveclub.com) is now part of stable Premiere 26.5: it can generate video and sound effects in the timeline from prompts. Available models, credits and account access still matter. Do not confuse it with Generative Extend, which fills a short timing gap, or with the separately announced beta music, soundscape and audio-cleanup features. Resolve 21 adds IntelliSearch, CineFocus, Face Age Transformer, Face Reshaper, AI Speech Generator and other assisted tools. Blackmagic's [Resolve 21 feature page](https://www.blackmagicdesign.com/products/davinciresolve/whatsnew?ref=davinciresolveclub.com) documents the current set. Many headline tools, including IntelliSearch, Magic Mask, text-based editing, Voice Isolation and AI Speech Generator, require Studio. Premiere's tools may solve missing frames, media search and object masks inside an Adobe edit. Resolve Studio spreads paid AI across media organization, editing, color and audio. Neither description predicts the result on your footage. Include result review, failed attempts and correction time in the test. Automation can also decide the edition choice. [Resolve 21.1](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) moves Python scripting to Studio and requires Studio for advanced scripting; its [Studio release](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) adds native MCP integration. That is not a blanket ban on Free Fusion macros or title templates. Check how a specific third-party tool connects before upgrading an established workflow. ## Fairlight vs Premiere Audio Premiere includes clip and track mixing, effects, automation, speech tools, captions and Essential Sound workflows. Audition is optional when a team needs its dedicated restoration or multitrack environment. A straightforward YouTube or corporate mix doesn't require leaving Premiere simply because Audition exists. Fairlight is a dedicated audio-post page inside Resolve, with clip and track EQ, dynamics, buses, automation, ADR, loudness tools and delivery in the same project. Studio adds paid tools including Voice Isolation, Music Remixer, Dialogue Separator and immersive-audio capabilities; those aren't all included in Free. Resolve can reduce application handoffs when the same editor or team finishes picture and audio in one project. Premiere can fit better when an Audition mixer, shared Adobe assets or an existing Frame.io approval path already defines the handoff. Measure revision rework and media relinking instead of assuming that integrated always means faster. ## Performance and System Requirements There's no honest universal performance winner. Playback and export depend on the codec profile, bit depth, chroma sampling, operating system, CPU, GPU or media engine, storage, effects and application version. Resolve Free and Studio can also expose different supported hardware-codec paths. Adobe’s [current Premiere requirements](https://helpx.adobe.com/premiere/desktop/get-started/technical-requirements/adobe-premiere-pro-technical-requirements.html?ref=davinciresolveclub.com) include 26.5\. Blackmagic publishes Resolve minimums in each release note. Read the exact operating-system and hardware row for the build you will install; being available on Mac or Windows does not mean every older machine is supported. Requirements are a floor, not a guarantee for your footage and effects. Heavy Resolve color nodes, Fusion compositions and video noise reduction can be GPU- and memory-intensive. Heavy Premiere effects, third-party plugins and linked compositions can shift the bottleneck elsewhere. Compare the [Resolve 21 system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) with Adobe's page, then test one representative source file before buying hardware. ## Head-to-Head Decision Table | Decision | DaVinci Resolve 21 | Adobe Premiere 26.5 | What to test | | -------------- | ------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------------ | | License | Free; Studio $295 US list price | $22.99/month US individual annual plan, billed monthly | Region, tax, term, credits and included services | | Editing | Cut and Edit pages | Track-based edit, Productions and Team Projects | Rough cut, multicam, relink and one revision | | Color | Dedicated node-based finishing page | Lumetri and current color-management tools | Camera format, shot matching, monitoring and master | | Motion and VFX | Fusion inside the Resolve project | After Effects connection when required | Templates, plugins, render boundaries and revisions | | Audio | Fairlight page; some AI tools require Studio | Built-in tools; Audition when required | Cleanup, routing, captions, mix and revision handoff | | AI | Studio tools across search, edit, color and audio | Object Masking, media intelligence and Firefly tools | Plan, region, credits, output limits and review | | Collaboration | Blackmagic Cloud and multi-user projects | Productions, Team Projects and Frame.io | Existing users, storage, ownership and approval path | | Performance | Codec-, GPU-, effect- and edition-dependent | Codec-, hardware-, effect- and version-dependent | Same source media, timeline, effects and export preset | ## Run One Controlled Project Test A defensible choice needs one completed job in each editor. Use identical inputs and write the delivery specification before opening either application. ![Controlled Resolve and Premiere project test using the same media edit brief delivery and five workflow measures](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/same-job-scorecard.webp) Use identical source media, brief and delivery. Record elapsed time, handoffs, relinks, revision rework and export QC without inventing a benchmark winner. 1. Use the same camera originals, including the longest-GOP or highest-bit-depth clip that causes concern. 2. Build the same rough cut, one multicam or caption task if relevant, one motion/VFX task, one grade and one audio cleanup. 3. Send the same review, apply one realistic revision and export the same master. 4. Record elapsed time, manual handoffs, relinks, revision rework and whether the exported file passes QC. 5. Don't count learning time as a permanent product defect, but do record the training and shortcut migration the switch requires. For a beginner or YouTube channel, this test is more useful than a generic score. The [Resolve beginner learning path](https://davinciresolveclub.com/davinci-resolve-tutorial/) supplies the Resolve route; use Adobe’s current training for an equivalent Premiere run. If your priority is a template-led social edit rather than a full finishing workflow, the [Resolve versus CapCut comparison](https://davinciresolveclub.com/davinci-resolve-vs-capcut/) covers that different choice. ## Which Editor Should You Choose? **Choose Resolve** when the same project should carry editing, grading, Fusion, Fairlight and delivery, when the Free edition already meets the brief, or when a substantial finishing pass is central to the work. Confirm the exact Free boundary in the [Resolve 21 Free feature guide](https://davinciresolveclub.com/davinci-resolve-free-version-features/) before assuming a codec or AI feature is included. **Choose Premiere** when recurring work depends on After Effects compositions, Photoshop or Libraries assets, Frame.io review, Adobe templates, or collaborators who exchange Premiere projects. Generative Extend can solve a narrow timing problem, but its duration, credit, media and regional limits must fit the deliverable. **Choose a hybrid workflow** when Premiere remains the editorial center and Resolve's color finish justifies a conform. Keep the untouched Premiere project, agree on handles and source metadata, export a reference movie and name the application that will create the final master. Don't switch solely to escape a monthly fee if the move breaks client templates, plugins or team exchange. Don't keep paying solely because Premiere is familiar if Resolve Free completes the same recurring work with fewer handoffs. If neither editor fits your work, browse the other [DaVinci Resolve comparisons](https://davinciresolveclub.com/davinci-resolve-comparisons/). ## Moving a Premiere Project to Resolve Safely Premiere 26.0 added OpenTimelineIO import and export. [Final Cut Pro XML](https://helpx.adobe.com/premiere/desktop/render-and-export/export-files/export-a-project-as-a-final-cut-pro-xml-file.html?ref=davinciresolveclub.com) is another common interchange route: Adobe warns that some effects and audio decisions do not transfer accurately. Neither format promises to turn every title, nest, plug-in or mix into native Resolve data. For XML, inspect the FCP Translation Results log as well as the imported timeline. 1. Duplicate the locked Premiere sequence and leave the original untouched. 2. Flatten or simplify nests, unsupported transitions and graphics; render elements that can't be reconstructed safely. 3. Preserve source timecode, file names and reel metadata, then export XML or a supported OTIO interchange plus a reference movie. 4. Import into Resolve, relink the original camera media and compare start frame, duration, framing, speed changes and transitions shot by shot. 5. Check audio track layout, muted clips and sync, then decide whether Resolve or Premiere owns the final export. A clean conform is a controlled transfer, not a one-click conversion. If repeated round trips erase the advantage of the color pass, finish the recurring job in one application or redesign the handoff. Before updating Resolve for a conform, back up the Project Library and individual projects. Blackmagic warns that a project created or opened in 21.1 cannot be reopened in 20.3.2, even though the library remains compatible. Keep an installer for the old version and untouched project backups until the new workflow is checked. ## Resolve vs Premiere FAQ ### Is DaVinci Resolve really free? Yes. Resolve 21 Free includes the Cut, Edit, Fusion, Color, Fairlight and Deliver pages, plus collaboration and output up to Ultra HD 3840 x 2160 at 60 fps within Blackmagic's documented format limits. It is a separate edition, not a time-limited Studio trial. Work built only with Free-supported tools has no general application watermark, but a Studio-only Resolve FX can show a DaVinci Resolve Studio watermark until that paid effect is removed or the project is opened in Studio. ### Is DaVinci Resolve better than Premiere for color grading? Resolve has the deeper dedicated finishing architecture: node graphs, tracked Power Windows, grouped grades, versions, galleries and advanced monitoring workflows. Premiere can handle editorial correction and many single-editor grades. The stronger architecture doesn't guarantee a better image without a sound color pipeline and a skilled operator. ### Which is better for beginners, DaVinci Resolve or Premiere? Resolve is the lower-risk starting point when the Free edition supports the footage and delivery. Premiere can be the faster practical choice when a class, employer, collaborator or template library already uses Adobe. Beginners should complete the same short project in both rather than choose from interface screenshots alone. ### Is DaVinci Resolve or Premiere better for YouTube? Resolve Free is usually the lower-cost choice for YouTube work up to Ultra HD 60 and keeps color and Fairlight in one project. Premiere may fit better when After Effects templates, Frame.io review, Adobe assets or Generative Extend are recurring requirements. Test the channel's actual camera format, captions, revision and upload master. ### Does Premiere have a one-time purchase option? No. Adobe's current desktop Premiere FAQ lists it as a membership product. The observed US individual price is $22.99 per month on an annual commitment billed monthly, before tax. Promotions, regions, cancellation terms and included generative credits can change, so verify the checkout before comparing totals. ### Does DaVinci Resolve work on Windows? Yes. Resolve runs on Windows, macOS and Linux, while Premiere desktop runs on Windows and macOS. Codec support, GPU acceleration, operating-system minimums and hardware recommendations differ by platform and version, so platform availability alone doesn't predict equal playback or export performance. ### Can I move a Premiere project to DaVinci Resolve? Yes, but treat it as a conform rather than a native project conversion. Duplicate and simplify the Premiere sequence, export XML or a supported OTIO interchange plus a reference movie, relink original media in Resolve, then verify framing, retimes, transitions, effects and audio shot by shot. Unsupported effects and plugins may need rendering or rebuilding. ### DaVinci Resolve Free Version Features: What You Lose Without Studio URL: https://davinciresolveclub.com/davinci-resolve-free-version-features/ Last updated: 2026-09-12T12:00:50.000Z DaVinci Resolve 21 Free can take a project from organizing footage through editing, color, Fusion effects, Fairlight audio and export. The limits matter when your job needs a particular codec, paid effect or output format, not when you reach some arbitrary professional skill level. Here is what to check before you build a project around the free edition. Blackmagic's [current Resolve product page](https://www.blackmagicdesign.com/products/davinciresolve?ref=davinciresolveclub.com) gives Free a clear headline ceiling: virtually all 8-bit video formats, up to 60 fps, at resolutions as high as Ultra HD 3840 x 2160\. That sentence is a product summary, not a substitute for the platform-specific codec table. A 10-bit source, an H.265 export or a camera format must be checked by operating system, container, codec, profile and direction. Studio is listed at $295 on Blackmagic’s US website. This guide inventories the Free edition’s features and restrictions; use the [Free versus Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) for the wider buying decision. The checks below include the scripting change introduced in Resolve 21.1. ## What DaVinci Resolve 21 Free Actually Includes Free is a separate edition, not a time-limited Studio trial. Normal work built only with Free-supported tools has no general application watermark. Blackmagic’s [Resolve 20 beginner guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Beginners-Guide.pdf?ref=davinciresolveclub.com) documents the important exception: Studio-only Resolve FX can be previewed in Free with a DaVinci Resolve Studio watermark. Remove the paid effect or use a licensed Studio installation; third-party trial effects have their own rules. Free includes the core page workflow: Media for organizing sources, Cut and Edit for building timelines, Fusion for compositing and motion graphics, Color for grading, Fairlight for audio, Deliver for output and, in Resolve 21, the Photo page for still-image work. - **Editing**: Cut and Edit pages, tracks, trimming, transitions, titles, keyframes and the normal timeline workflow. - **Color**: node-based grading, primary and secondary corrections, curves, qualifiers, Power Windows, tracking, scopes and LUT workflows, without claiming every Studio control is included. - **Fusion**: the integrated node-based compositor for titles, tracking, keying and visual-effects work, while some advanced tools and Resolve FX remain paid. - **Fairlight**: editing, mixing, EQ, dynamics, automation and standard audio post tools; Studio adds named AI and immersive capabilities. - **Photo**: Resolve 21's still-image workspace, with the Free edition's output ceiling still relevant to large finished photographs. - **Collaboration and HDR**: Blackmagic explicitly includes multi-user collaboration and HDR grading in Free. [![Official DaVinci Resolve Studio 21 Color page showing clips nodes HDR controls ColorSlice and scopes](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve21-core-color-page-official.webp)](https://www.blackmagicdesign.com/products/davinciresolve?ref=davinciresolveclub.com) Blackmagic's current product page uses this Resolve Studio 21 Color interface to show the shared workspace. Free includes the core Color page, but the frame is not a promise that every visible control or effect is available in Free. For a first project, pair this inventory with the [beginner project walkthrough](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) and the current [Resolve 21 system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). Edition and performance are separate questions: a feature can exist in Free and still run poorly on a particular codec, GPU or storage setup. ## The Resolution and Frame-Rate Boundary Free can master and output Ultra HD 3840 x 2160 at up to 60 fps. That covers common 2160p deliveries at 24, 25, 30, 50 or 60 fps. It doesn't mean every format labelled 4K fits. DCI 4K is 4096 x 2160, so its width already exceeds the documented Ultra HD ceiling. That is an output limit, not a ban on importing larger source files. Blackmagic’s 21.1 Free release notes say it can handle unlimited-resolution media while limiting mastering and output to Ultra HD or below. Whether a particular file opens and plays smoothly still depends on its codec and your computer. Studio supports resolutions beyond 4K, and Blackmagic's Studio page currently states up to 32K at 120 fps. Those numbers are capability ceilings, not recommended defaults. A platform upload, broadcast specification, cinema package or client master should determine the timeline and output, not the largest option in the menu. The Photo page needs a separate check. In a May 2026 beta test, [PetaPixel reported a 4K-or-below Free export limit](https://petapixel.com/2026/05/11/you-can-edit-photos-in-resolve-but-should-you/?ref=davinciresolveclub.com) for both Photo and Deliver and said Blackmagic confirmed it. That is dated testing, not a new measurement of 21.1\. The current Free release notes still state an Ultra HD-or-lower output limit but do not separately define every Photo export option. Before moving a catalog, export a sample and inspect its pixel dimensions. The [Resolve 21 Photo page guide](https://davinciresolveclub.com/davinci-resolve-21-photo-page/) covers the full still-photo workflow. ## Why 10-Bit and Codec Claims Need a Platform Check The sentence \`Free is 8-bit only\` is too broad. Blackmagic's product page says Free works with virtually all 8-bit video formats, but the maintained supported-codec table is organized by macOS, Windows and Linux, then by container, codec, profile, decode and encode. Those columns are the evidence that matters for a real file. Separate three questions. Can Resolve open the source? Can it play that source at a usable rate on this machine? Can it encode the required master? A file may decode but lack the desired encoder, or it may be technically supported yet too heavy for smooth playback. Bit depth by itself can't answer all three. Inspect the file with MediaInfo or another reliable stream inspector. Record the container, video codec, chroma sampling, bit depth, profile, frame size and frame rate. Then consult Blackmagic’s [supported-codec table](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com). On September 12, 2026, its support catalog still listed the July 2025 Resolve 20 matrix as the newest codec table. Read its OS-specific rows alongside the release notes for your installed build; it is not a newly issued Resolve 21 matrix. The matrix shows why a single “10-bit supported” answer is misleading. Its Windows H.264 rows list 8-bit OS-supported profiles; Windows H.265 rows include 8/10-bit OS-supported profiles, with more profiles and GPU acceleration in Studio. macOS lists accelerated H.264/H.265 paths without a Studio-only label. The Rocky Linux H.264/H.265 rows require Studio. These are the published matrix’s distinctions, not a guarantee for every camera profile or GPU. For specific containers and audio streams, use the [supported codecs and formats guide](https://davinciresolveclub.com/davinci-resolve-supported-codecs-formats/). A MOV or MP4 extension tells you the container, not whether every stream inside it is supported. ![DaVinci Resolve Free project test from camera originals through grade audio and external master review](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/test-free-with-real-media.webp) Test the actual source media, the difficult scene, the required grade and track layout, then export the required master and open it outside Resolve. Run this test before buying or promising a workflow. Import camera originals, edit the difficult section, build the required grade and audio layout, export the actual master, then open that file outside Resolve. Record the first blocked step. A spec sheet can't reveal a broken plugin, an unusual stream profile or a system bottleneck by itself. ## Studio AI Tools and the DaVinci Neural Engine Studio includes the DaVinci AI Neural Engine. Blackmagic’s [Studio feature page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) names Magic Mask, Super Scale, Speed Warp, Smart Reframe, object removal and facial-recognition workflows. The [Resolve 21 manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci%5FResolve%5F21%5FReference%5FManual.pdf?ref=davinciresolveclub.com) also labels audio transcription and text-based editing Studio-only. Use the [Resolve 21 AI tools guide](https://davinciresolveclub.com/davinci-resolve-21-ai-tools/) for individual tool and edition checks, including newer features. Do not read “AI” as a reliable edition label by itself. Check the named command: a tutorial using Magic Mask or text-based editing needs Studio, while ordinary masks, tracking and manual captions are different workflows. Free still offers manual and non-Neural alternatives for many tasks: Power Windows, qualifiers, standard tracking, Fusion masks, ordinary reframing and non-Speed-Warp retiming. Those alternatives aren't identical replacements, but neither are they absent. The buying question is whether the paid tool removes a repeated, measured bottleneck in the work you actually do. ## Video Noise Reduction and Extra Resolve FX Temporal video noise reduction, AI spatial video noise reduction and UltraNR are Studio features. Free doesn't provide those Color-page video-noise-reduction controls. This is one of the clearest edition boundaries for footage that must be denoised inside Resolve. [![Blackmagic Studio advanced video noise reduction before and after comparison on a motocross helmet](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/studio-video-noise-reduction-official.webp)](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) Blackmagic's current Studio page uses this before-and-after example for advanced video noise reduction. It illustrates the problem class, not a guaranteed result on every clip. Temporal processing compares information across frames; spatial processing works within a frame. Either can soften detail or create artifacts when pushed too far. The official comparison illustrates the intended problem, but it does not prove that every noisy clip will become clean. Test representative motion, fine texture, skin and shadow detail before treating Studio as an automatic repair. Keep video and audio noise separate. Fairlight includes audio cleanup and mixing tools, while Studio adds named AI audio tools such as Voice Isolation, Music Remixer and Dialogue Separator. A page or plugin called noise reduction may be solving an entirely different signal problem. Studio also adds Film Look Creator, Patch Replacer and clip lens-distortion correction. Free retains many effects and the core grading, Fusion and Fairlight tools. Check the exact effect name in your version, particularly when importing a template. Third-party OpenFX plug-ins have their own licenses and may add their own watermarks. ## GPU Acceleration and Performance Free uses the GPU too. Do not confuse GPU image processing with a codec’s hardware decoder or encoder. Blackmagic’s 21.1 Free release notes specify one processing GPU on Windows and Linux; they do not state that as a universal macOS restriction. Studio supports multiple GPUs, but that alone does not promise a faster result on your machine. Hardware H.264/H.265 acceleration is also platform-dependent. Supported macOS hardware paths are not universally Studio-only. On Windows, the codec matrix distinguishes OS-supported profiles from the additional profiles and GPU acceleration offered in Studio. Check both the stream profile and your hardware rather than buying an upgrade solely because someone said Free runs on the CPU. Performance depends on the source codec, bit depth, effects, temporal processing, timeline resolution, cache, storage and available GPU memory. A second GPU helps only when the operating system, hardware, workload and feature can use it. Apple Silicon also uses unified memory, so a discrete-GPU buying rule from Windows cannot be copied directly to a Mac. If Free stutters, first test a short source clip without effects. Then compare proxy, optimized-media or cache behavior, and inspect whether the bottleneck is decode, effects, storage or GPU memory. Buying Studio can unlock a supported hardware path, but it will not restore a missing source or repair a corrupt file. Use the [slow-playback diagnostic](https://davinciresolveclub.com/davinci-resolve-slow-playback/) to find the bottleneck before deciding whether an upgrade would help. ## Python Scripts and Automation Changed in 21.1 If a Python-based tool worked in Free before an update, check this first: Blackmagic’s [21.1 release notes](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) move Python scripting to Studio and say advanced scripting now requires Studio. This is not a claim that every Fusion macro, title template or plug-in has become paid. Check how the particular tool integrates with Resolve and which builds its developer supports. One concrete example is [PugetBench for DaVinci Resolve](https://www.pugetsystems.com/pugetbench/creators/davinci-resolve/?ref=davinciresolveclub.com): its developer says Free 21.1 is no longer supported because of the scripting change, while its published Free compatibility range is 20.0–21.0\. That is a benchmark compatibility limit, not a statement that normal editing stops working. Back up projects and project libraries before changing versions to recover an automation workflow. ## HDR, Cinema Delivery, Audio and Collaboration Free includes HDR grading and multi-user collaboration according to the current product page. Those inclusions are often lost in simplified comparison tables. They don't make every HDR or collaboration requirement free, because delivery metadata, monitoring, cloud services and facility workflows can add separate constraints. Studio adds advanced Dolby Vision and HDR10+ workflows, immersive audio and additional cinema-delivery capabilities. Do not turn that into “every IMF or DCP operation needs Studio”: the codec matrix distinguishes native decoding, encoding formats, resolution thresholds and licensed options. Check the exact deliverable rather than the acronym alone. Studio also does not include every third-party license. Blackmagic says advanced Dolby Vision trim controls need a separate Dolby license, and encrypted DCP support needs a separate EasyDCP license. Confirm the platform, required renderer and licensing before accepting the job; the codec matrix also lists separate licensing for rendering Dolby Atmos formats. For ordinary web delivery, use the platform's current requirements and test the result after upload. The maintained [YouTube export settings](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/) cover that specific master. Don't buy Studio for a broadcast or cinema acronym that never appears in the brief. ## Free Edition Limits at a Glance | Requirement | Free | Studio adds | What to verify | | ---------------------------- | ------------------------------------------------------ | -------------------------------------------------------------------------- | ----------------------------------------------------------------- | | Maximum output | Ultra HD 3840 x 2160 at up to 60 fps | Up to 32K and 120 fps | Confirm the actual master dimensions and frame rate | | Common video formats | Blackmagic says virtually all 8-bit video formats | Broader 10-bit and professional format support | Check OS, container, codec, profile, decode and encode separately | | H.264 and H.265 acceleration | Platform-dependent; macOS has supported hardware paths | Additional supported profiles and hardware paths, depending on OS | Test the exact source profile and delivery preset | | AI and text tools | Core non-Studio workflows remain available | Neural Engine, text-based editing, Magic Mask and named AI tools | Confirm the exact tool in the current Studio page | | Video noise reduction | No Color-page temporal or AI spatial NR | Temporal NR, AI spatial NR and UltraNR | Test representative noisy motion, not one still frame | | GPU scaling | One processing GPU on Windows and Linux in 21.1 | Multiple-GPU support | Check workload, OS and supported hardware | | HDR and cinema delivery | HDR grading | Advanced Dolby Vision/HDR10+ and additional cinema-delivery capabilities | Check exact format, resolution, platform and separate licenses | | Audio | Core Fairlight editing and mixing | Immersive tools plus Voice Isolation, Music Remixer and Dialogue Separator | Define the mix and delivery format first | | Python scripting in 21.1 | Requires Studio | Python scripting and advanced automation | Check the tool developer’s supported builds | Use this table to find the restriction that affects your job. For codec or delivery questions, check the OS-specific row and your installed build before treating a feature name as a yes-or-no answer. ## When Free Is Enough and When Studio Is Justified Free is enough when the actual source opens, the timeline performs acceptably, the needed effect exists, and the required master stays within the documented Free boundaries. That can cover beginner work, YouTube videos, many corporate edits, short films and client jobs, but the project specification decides, not the category label. Studio is justified when a confirmed requirement blocks the tested workflow: output above Ultra HD or 60 fps, an unavailable codec profile or hardware path, temporal or AI spatial video noise reduction, a named Neural Engine tool, Python scripting in 21.1, or a required advanced delivery feature. Verify the specific limitation and any additional license before paying. 1. Write the required source formats and master specification before opening the project. 2. Test the longest or most difficult source, not a convenient sample. 3. Name the missing Studio capability and confirm it on the current page. 4. Measure the blocked time or failed deliverable instead of guessing at a speed benefit. 5. Check the current [Resolve price and license details](https://davinciresolveclub.com/how-much-does-davinci-resolve-cost/) before purchasing or assuming future upgrade terms. If every part of the test works in Free, keep editing. If one part fails, name the missing capability first. That gives you a useful upgrade decision instead of a list of impressive features you may never use. ## DaVinci Resolve Free Version FAQ ### What features are missing from the free version of DaVinci Resolve? Studio adds named Neural Engine tools, text-based editing, temporal and AI spatial video noise reduction, extra effects, output beyond Ultra HD or 60 fps, broader professional-format support and advanced delivery features. Python scripting also requires Studio in 21.1\. GPU limits depend on the OS: do not assume Free lacks every hardware-accelerated codec path. ### Can DaVinci Resolve Free export 4K? It can master and output Ultra HD 3840 x 2160 at up to 60 fps. That's the consumer format commonly called 4K UHD. DCI 4K is 4096 x 2160, which exceeds the documented Free ceiling, as do higher resolutions and frame rates above 60 fps. ### Can DaVinci Resolve Free edit or export 10-bit video? There's no safe universal yes-or-no answer based only on bit depth. Support varies by operating system, container, codec, profile and whether Resolve is decoding or encoding. Inspect the exact file with a media-information tool and check the current supported-codec table for that platform and direction. ### Does DaVinci Resolve Free have a watermark or time limit? Blackmagic distributes Free as a separate free edition, not a time-limited Studio trial. Normal work built only with Free-supported tools has no general application watermark. However, Studio-only Resolve FX can be previewed in Free with a DaVinci Resolve Studio watermark; remove the paid effect or open the project in Studio to clear it. Third-party trial plugins can impose their own marks or license limits. ### Is DaVinci Resolve Free enough for YouTube or client work? Yes when the source media decodes correctly, the needed effects exist in Free, the system can process the timeline, and the required master stays within Free's format, Ultra HD and 60 fps boundaries. Test the actual camera file and delivery preset before promising a client workflow. ### Does DaVinci Resolve 21 Free include the Photo page? Yes. Resolve 21 includes the Photo page. PetaPixel’s May 2026 beta test reported Free Photo and Deliver exports limited to 4K or below; that is not a fresh 21.1 measurement. The current Free notes still specify Ultra HD-or-lower output. Export a sample and check its pixel dimensions before relying on Free for full-resolution photographs. This guide belongs to the [DaVinci Resolve Comparisons hub](https://davinciresolveclub.com/davinci-resolve-comparisons/). Start there to move between Free versus Studio, current cost, competing editors and other edition or buying decisions. ### DaVinci Resolve Tutorial for Beginners URL: https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/ Last updated: 2026-09-13T09:17:18.000Z Don't try to learn every page before making anything. Build a 30 to 60 second video with three to eight clips, one title and a simple audio mix. That small project forces the useful decisions in the right order: setup, import, selection, trimming, sound, color and export. Fusion, advanced Fairlight mixing and elaborate grading can wait until the first file plays correctly outside Resolve. This walkthrough uses Resolve 21 and the Edit page. Blackmagic's latest interface also includes the Photo page, but a first video doesn't need it. The goal here is a finished edit, not a tour of every button. Think of pages as workspaces, not levels you must unlock. Media organizes sources, Cut and Edit build the story, Fusion creates composites, Color corrects the picture, Fairlight handles deeper sound work, and Deliver creates output. Resolve 21 also has Photo for still-image work. Your video-editing work stays in the same project as you switch workspaces. Photo uses albums for stills; it is not another step required for this video. ## 1\. Choose Free or Studio, Then Check the Machine For a first project, start with the free edition unless you already know which Studio-only tool or delivery requirement you need. As checked on September 13, 2026, Blackmagic's US product page lists [DaVinci Resolve 21 as free and Studio at $295](https://www.blackmagicdesign.com/products/davinciresolve?ref=davinciresolveclub.com). Studio adds AI, advanced effects, broader professional workflows and other high-end capabilities; it doesn't change the basic import-to-export route in this tutorial. Before downloading, compare the computer, operating system, GPU memory and driver with the maintained [Resolve 21 system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/). Do not judge performance from RAM alone. Source codec, bit depth, timeline size, effects, storage and cache state can matter as much as the headline specification. Keep the first exercise light: a short 1080p project is easier to diagnose than a long 4K timeline full of effects. If one plain source clip already stutters, solve that before building the edit. If a plain clip plays but an effect-heavy section doesn't, **Playback > Render Cache > Smart** can build a temporary playable result for complex sections. Let the cache finish, then test the same range again. Cache is a performance aid, not a repair for missing files, unsupported streams or an undersized GPU. If basic source playback still fails, use the [slow-playback diagnostic](https://davinciresolveclub.com/davinci-resolve-slow-playback/). ## 2\. Plan One Small Video Choose a concrete result: a 30-second travel sequence, a short product demonstration, or a talking-head answer with B-roll. Put the camera originals, music, voice recording and graphics in one stable project folder before opening Resolve. Moving those files later can break the stored path and create Media Offline frames. Write a six-line paper edit before touching the timeline: opening shot, context, main action, detail, result, ending. This gives every clip a job. The first cut becomes selection and ordering instead of random dragging. - **Picture**: three to eight useful clips, not an entire card dump. - **Sound**: one clear voice or natural-sound track plus optional music. - **Text**: one title that the viewer can read at normal playback speed. - **Delivery**: decide landscape or vertical, resolution and intended frame rate before import. ## 3\. Create the Project Before Import Open Project Manager and double-click **Untitled Project** or click **New Project**. Give the project a specific name. Once it opens, click the gear at the lower right and check **Project Settings > Master Settings**. Choose the project Timeline frame rate before adding media. Resolve can offer to match an empty project's rate when the first clips arrive, but that project-wide setting locks after import. Read the prompt instead of clicking through it. You can still create a new timeline with a different rate: choose File > New Timeline, uncheck Use Project Settings and set the rate under Format before adding clips. That creates a separate timeline; it does not change the timing of an existing edit. Start timeline resolution from the intended delivery, then consider reframing and performance. A 4K source doesn't force a 4K editing timeline when the deliverable is 1080p; conversely, a 4K master or significant reframing may justify the larger timeline. The delivery requirement wins, not a universal preset. Frame rate describes timing, not image quality. Match normal-speed material to the intended playback rate; treat high-frame-rate clips intended for slow motion as a separate creative choice. Resolution describes the pixel canvas. Keeping those decisions separate prevents the common mistake of choosing the largest number in both menus without understanding the result. [![Project Master Settings with timeline resolution and frame rate marked for the first edit](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-beginner-settings-v1.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-beginner-settings-v1.webp?ref=davinciresolveclub.com) AI-assisted annotations on an interface reference. Choose the delivery size and project rate before import; the pictured 1080p and 24 fps values are examples, not a required preset. Tap or click the image to enlarge. Use fast storage with enough free space for cache and renders. Keep camera originals in a stable location that will still be mounted tomorrow. An SSD helps, but the correct storage plan depends on source bitrate, project size and backup needs. ## 4\. Import and Organize the Media Pool Stay on Edit, open Media Pool, right-click an empty area and choose Import Media. Select the files and click Open. If you prefer browsing drives inside Resolve, switch to the Media page and drag files from its Media Storage browser into the Media Pool. These are two different import routes; Edit does not have the same Media Storage browser. Create only the bins the exercise needs: **A-roll**, **B-roll**, **Audio** and **Graphics**. Bins organize project references; they do not move the camera originals on disk. Preview each source, remove obvious misses from the working selection, and confirm that picture and sound decode before editing. If the source frame rate differs from the empty project, Resolve may ask whether to change the project. Choose deliberately. A 60 fps slow-motion source inside a 24 or 30 fps story does not automatically mean the whole project should run at 60 fps. Before leaving import, open several clips from different cameras or phones. Confirm orientation, duration, audio channels and smooth decoding. One successful clip doesn't prove that every file with the same extension carries the same codec or profile. ## 5\. Build the Rough Cut on the Edit Page The Cut and Edit pages can both create a complete timeline. Cut is optimized for fast, action-based assembly; Edit exposes a traditional Media Pool, source viewer, timeline viewer and track layout. This tutorial uses Edit because those relationships remain visible. [![Resolve Edit page with numbered Media Pool, source viewer, timeline viewer and timeline](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-beginner-edit-v1.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-beginner-edit-v1.webp?ref=davinciresolveclub.com) 1: Media Pool. 2: Source viewer. 3: Timeline viewer. 4: Timeline. AI-assisted annotations on Blackmagic Design’s Studio example. Tap or click the image to enlarge. Create a timeline from the selected clips or drag the first clip into the empty timeline area and name the timeline. Then build the paper edit in order. Don't trim every frame yet. First make sure the story has a beginning, useful middle and ending. 1. Open a source clip and mark the useful section, or drag the clip to the timeline and trim it there. 2. Place the main story on Video 1\. Put B-roll above it on Video 2 only when the overlay should cover the picture below. 3. Use Selection mode for moving and edge trimming. To split inside a clip, switch to Blade Edit mode, click the required frame on the clip, then return to Selection mode before moving pieces. 4. Play the complete rough cut without stopping. Remove repetition before adding effects. For a precise split, use the full [clip-splitting guide](https://davinciresolveclub.com/how-to-split-a-video-in-davinci-resolve/). The important beginner distinction is simple: trimming changes an edge; splitting creates a new edit point inside the clip. Use Space to play and stop, then make decisions while watching motion and hearing sound. Zooming into individual frames too early encourages busy editing. First remove shots that do not advance the idea; then tighten pauses and trim distracting starts or endings. ## 6\. Add One Title, B-Roll and Only Necessary Transitions Click **Effects** at the top left to open the Effects Library. Open Titles, drag a simple Text title above the picture, select it, and edit wording, font, size and position in Inspector. The focused [text tutorial](https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/) covers title controls without turning this page into a typography manual. Use B-roll to show what the voice is discussing or to bridge an awkward picture edit. Keep the main audio running underneath when continuity matters. An opaque picture on a higher video track covers the picture below while it overlaps; it doesn't automatically replace the lower clip's audio. Start with straight cuts. Add a Cross Dissolve only when it communicates a soft change and both clips have enough unused frames for the overlap. The dedicated [Resolve transitions guide](https://davinciresolveclub.com/davinci-resolve-transitions/) explains handles and placement if Resolve refuses the transition. ## 7\. Make a First Audio Pass Play the timeline with your eyes off the picture. Dialogue should stay intelligible, edits shouldn't create abrupt clicks, and music should support rather than mask speech. Adjust a clip with the level line on the audio clip or the Volume control in Inspector. Use track faders when the whole track needs a change. Don't chase one universal meter number for every delivery. Listen on headphones and speakers, watch the meters for clipping, and compare several passages. If a music bed fights the voice, lower the music first; compression and sidechain routing belong in a later Fairlight pass. Check every edit where sound changes. Add a short audio fade when a cut clicks or a room tone ends abruptly. If the voice comes from one channel of a stereo recording, diagnose the channel layout rather than simply turning the clip louder. The waveform is a navigation aid; your ears and meters decide whether the mix works. If a clip should be silent or its picture and sound need separate treatment, follow the [mute and split-audio workflow](https://davinciresolveclub.com/mute-split-audio-davinci-resolve/). Save before making structural changes, and keep project backups configured using the [Resolve save and backup guide](https://davinciresolveclub.com/how-to-save-work-davinci-resolve/). ## 8\. Make a Restrained Color Check Open Color after the edit and audio structure are stable. Select one representative clip. For a first pass, correct obvious exposure and white-balance problems, compare adjacent shots, and watch a scope so the display isn't your only reference. Do not copy one grade across unrelated shots and assume the job is finished. For ordinary display-ready footage, start in Primaries > Color Wheels. Use the master controls beneath Lift, Gamma and Gain for broad shadow, midtone and highlight balance; their ranges overlap. Temp and Tint help correct an unwanted warm/cool or green/magenta cast. Make small adjustments while watching the viewer and a waveform or parade. Preserve intentional shadows and highlights rather than trying to fill the entire scope. Log, HDR, camera RAW and mixed-camera color management need a defined input, timeline and output transform. Don't assign a color science from the file extension alone. Use the maintained [beginner color-grading workflow](https://davinciresolveclub.com/how-to-color-grade-davinci-resolve/) when the source isn't ordinary display-ready footage. After balancing one shot, move to its neighbor and match the obvious exposure and color differences by eye and scope. Leave stylized looks until the shots cut together cleanly. A consistent sequence is more useful than one dramatic thumbnail surrounded by mismatched clips. ## 9\. Export and Play the File For the fastest first check, choose **File > Quick Export** and select an appropriate local preset. For control over format, codec, filename, audio, range and queue, open Deliver. A broadly compatible starting file is MP4 with H.264, the intended resolution and the timeline frame rate, but the platform or client specification always overrides a generic preset. On Deliver, choose Custom Export, set a filename and location, and select Single clip for one finished video. In Video, enable Export Video and choose MP4/H.264 where available; check the output resolution and frame rate. In Audio, enable Export Audio and select the bus carrying your finished mix. Choose Entire Timeline for the complete edit, or deliberately set a shorter range. Click Add to Render Queue, then Render All. The complete [Deliver-page export guide](https://davinciresolveclub.com/export-video-davinci-resolve/) covers format and queue choices; the [YouTube export settings](https://davinciresolveclub.com/davinci-resolve-youtube-export-settings/) guide covers YouTube-specific choices. [![Render Queue with output path and an unfinished job at 56 percent, annotated with file-review steps](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-beginner-export-v1.webp)](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/davinci-beginner-export-v1.webp?ref=davinciresolveclub.com) AI-assisted annotations on Blackmagic Design’s Render Queue example. This job is still rendering. Once your job finishes, open its output file and check the whole video outside Resolve. Tap or click the image to enlarge. Play the rendered file outside Resolve from beginning to end. Check the first and last frame, picture orientation, audio, titles, transitions and any section that used a cache or effect. An export progress bar reaching 100 percent proves that encoding ended, not that the delivered file is correct. ## What to Learn After the First Project Repeat the same small project once without looking at the instructions. On the second pass, learn one improvement: cleaner trims, better dialogue, a controlled grade or a more deliberate export. Avoid collecting unrelated effects before the base workflow feels routine. Blackmagic provides [free official project-based training](https://www.blackmagicdesign.com/products/davinciresolve/training?ref=davinciresolveclub.com). Its current structured beginner book is labeled Resolve 20, while the current application and reference manual are Resolve 21, so expect some interface differences. Use the site's [DaVinci Resolve learning path](https://davinciresolveclub.com/davinci-resolve-tutorial/) to move from the first edit into editing, color, Fairlight, Fusion and delivery without creating disconnected skill gaps. ## Beginner FAQ ### Is the free version enough for a beginner? Yes for a normal first editing project. Blackmagic offers Resolve 21 as a free application, while Studio adds extra AI, effects, format, HDR and performance capabilities. Start with free unless a named Studio-only feature or delivery requirement is already part of your job. ### Should a beginner use the Cut page or the Edit page? Either can make a complete edit. The Cut page favors fast, action-based assembly; the Edit page exposes a traditional timeline and more controls. This tutorial uses Edit because its Media Pool, viewers, tracks and timeline make the underlying editing model easier to see. ### Why does playback stutter after I import clips? Stutter can come from the source codec, timeline effects, cache or proxy state, storage speed, drivers, available GPU memory, or the machine itself. Test one short clip without effects first. Use the dedicated slow-playback checklist if the source still can't play smoothly. ### Can I change the timeline frame rate after importing media? The project-wide Timeline frame rate locks after import, but a new timeline can use another rate. Choose File > New Timeline, uncheck Use Project Settings and choose the rate under Format before adding clips. Keep the original edit and a project backup; moving an edit to another rate requires checking cuts, effects and audio sync again. Creating that timeline does not unlock the project setting. ### Do I need transitions on a first edit? No. Start with straight cuts and add a transition only when it communicates a change in time, place, mood or viewpoint. A centered dissolve between two clips needs unused frames beyond their trimmed edges. If handles are missing, shorten or reposition the transition, or keep a straight cut rather than accepting an unwanted freeze. ### Why did my first export have no sound? Confirm the timeline plays through the intended main mix, then verify that audio export is enabled and the correct output bus or track is selected. Render a short test and play the file outside Resolve before committing to a long export. ### Media Offline in DaVinci Resolve: How to Fix It URL: https://davinciresolveclub.com/media-offline-davinci-resolve/ Last updated: 2026-09-12T15:25:46.000Z A red “Media Offline” frame doesn't identify one universal problem. First decide whether Resolve lost the camera original, only proxy or cached playback is missing, the source can't decode, or the timeline event points to the wrong clip. Relink only the path failures; test the other branches before changing media. Blackmagic's [Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com) is the primary reference for relinking and current command names. Its latest dedicated [supported-codec reference](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FSupported%5FCodec%5FList.pdf?ref=davinciresolveclub.com) is still labeled Resolve 20 as of this review, so confirm the platform, container, codec and profile instead of trusting .mp4 or .mov alone. For a different failure, start with the [Resolve troubleshooting map](https://davinciresolveclub.com/fix-davinci-resolve/). ![DaVinci Resolve Media Pool file path and timeline checks for Media Offline clips](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/media-offline-diagnose-source-v2.webp) Start by checking whether the original is offline in the Media Pool, what path Resolve recorded, and whether the same failure exists in the timeline. ## Find Every Offline Clip First in Resolve 21 Large projects are easier to diagnose when every offline source is visible in one place. Resolve 21 can build that view automatically; it does not relink or repair anything for you. Open DaVinci Resolve > Preferences > User > Editing > Automatic Smart Bins and enable Automatic smart bin for offline clips. The [Resolve 21 New Features Guide](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F21%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com) confirms that this Smart Bin gathers offline clips from across the project. On the Color page, the matching Offline Clips filter provides the same kind of focused list. Use the list to count the affected media and select a representative clip before choosing the path, proxy, cache, codec, or timeline branch below. ## If Resolve Lost the Source Path, Relink the Right Files Resolve stores a source relationship for each clip. If a folder moves, a filename changes, a drive mounts at a different location, or a project opens on another machine, that relationship can break. The Resolve 21.1 Reference Manual documents Relink Selected Clips for reorganized media and Change Source Folder when a new root keeps the old subfolder structure. Start with the smallest reversible check: Relink a changed-path case in four steps: 1. Open the **Media Pool** on the Edit or Cut page. 2. Select the offline clips you need, or select the bin that contains them. 3. Right-click a selected clip and choose **Relink Selected Clips**. For a selected bin, use **Relink Clips for Selected Bin**. 4. Choose the narrowest folder containing the camera originals and click OK. Relink Selected Clips uses filename and timecode as its primary matching criteria. Resolve searches the selected directory structure and can offer a deeper search when the quick pass fails. A successful search is not the final check: open several matches and compare the actual picture, duration, start timecode, frame rate and audio before continuing. If filenames changed, restore the original names from a backup or relink carefully and compare filename, duration, start timecode, frame rate, and audio channels. Don't use Replace as a blind batch fix: attaching the wrong file can preserve an apparently healthy timeline while changing the edit underneath it. ![DaVinci Resolve Relink Selected Clips menu and source folder selection](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/media-offline-relink-selected-v2.webp) Select the offline originals, choose Relink Selected Clips, then choose the narrowest folder containing those files. Verify name, duration and timecode after matching. ## When an external drive mounts at a different path On Windows, an external drive can mount with a different drive letter. If footage was on E: yesterday and the same volume mounts as F: today, clips stored under that root can appear offline even though the files haven't moved inside the drive. Start with relinking in Resolve or Change Source Folder below; neither requires changing your Windows drive configuration. Restoring the old letter is an optional alternative only for a dedicated media volume that contains neither Windows nor installed apps, and only if that letter is available. [Microsoft warns that changing a letter](https://learn.microsoft.com/en-us/windows-server/storage/disk-management/change-a-drive-letter?ref=davinciresolveclub.com) can stop apps finding their files. With the required administrator rights, use Disk Management > Change Drive Letter and Paths > Change, select the available old letter and confirm. Then check several clips in Resolve; restoring a path does not repair damaged or unsupported media. If the root changed but the folder structure did not, select the affected Media Pool clips and choose Change Source Folder. In the Relink Media window, click Browse beside Change To, select the new location and click Open, then Change. This avoids a broad disk search and is useful for a moved drive or shared-storage root. To reduce repeat failures on Windows, assign a stable drive letter to a dedicated media volume and avoid letters frequently taken by removable devices. Record the chosen letter in the project handoff notes; the exact letter matters less than keeping it consistent. On macOS, the drive-letter variant doesn't apply, but changing a volume name or mount path still breaks the stored relationship. Confirm that the expected volume is mounted and readable before relinking. ## If the files exist and the stored path is correct If the source path is correct, test the camera original without generated media. Note your current playback settings, then make these three changes: 1. **Playback > Proxy Handling > Disable All Proxies** 2. **Playback > Use Optimized Media if Available: uncheck it** 3. **Playback > Render Cache > None** Replay the same failing range. If it works, re-enable one option at a time to identify whether the proxy, optimized media or cache triggers the failure. Restore your chosen settings after the test. If the original still fails, investigate access, damage or decoding instead. Treat cache as a controlled test, not the default cure. If the failure returns only when Render Cache is enabled, clear the affected clips first. Cache changes cannot repair a moved original or add support for an unreadable stream. Run the smallest cache test: 1. Select the affected timeline clip or clips. 2. Choose **Playback > Delete Render Cache > Selected Clips**. 3. Keep **Playback > Render Cache > None** while you retest the camera original. 4. Regenerate cache only after original-media playback is stable. If original playback returns, regenerate cache for the affected range. If the original remains offline, return to path, permissions, storage health and codec checks. If the clip is online but merely stutters or drops playback frames, use the [slow-playback diagnostic](https://davinciresolveclub.com/davinci-resolve-slow-playback/) instead of treating it as missing media. Proxy media is a separate source relationship. Disable All Proxies selects camera originals, whereas Prefer Camera Originals can fall back to proxies. With optimized media and render cache also disabled for the test, a missing original will show Media Offline even if its proxy exists. Follow the [Proxy Media relink checklist](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) when the fault is confined to proxies; do not change a correct camera-original path. ![DaVinci Resolve Proxy Handling and Delete Render Cache controls for offline media](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/media-offline-proxy-cache-v2.webp) Disable proxies to test camera originals; clear only the selected clip's cache when the symptom follows cached playback. Neither test repairs a moved source. ## When import fails, inspect the actual codec A container extension isn't a codec diagnosis. Two MP4 files can carry different codecs, profiles, chroma sampling, bit depths, frame-rate modes and audio streams. Read the problem clip with [MediaInfo](https://mediaarea.net/en/MediaInfo?ref=davinciresolveclub.com), then compare those fields with Blackmagic's latest posted dedicated codec table for your OS and edition. That document is currently labeled Resolve 20, so also check the release notes for your installed Resolve 21 build. If the clip appears in the Media Pool but has audio without picture, or it fails immediately on import, follow the [MP4 stream-check workflow](https://davinciresolveclub.com/davinci-resolve-wont-import-mp4/). Test one short transcode before processing a folder; the actual constraint may be the codec, profile, bit depth, chroma sampling, OS decoder, GPU path, or a damaged file. On Windows, Microsoft's [HEVC extension guidance](https://support.microsoft.com/en-us/windows/apps/photos/photos-app-video-editor-error-can-t-view-this-file-type?ref=davinciresolveclub.com) can restore HEVC playback for Windows apps that rely on the OS component, but it isn't a universal Resolve fix and doesn't override Blackmagic's edition, profile, or hardware limits. Check the supported-codec table before buying or installing anything. When the exact source stream is unsupported or unstable, preserve the original and create one editing intermediate with a codec your installation supports. Keep the source frame rate, frame size, audio layout, and timecode when the transcoder allows it. - **DNxHR HQ or HQX**: choose HQX when the source and encoder need a 10-bit-capable intermediate; don't add bit depth the source never had. - [ProRes 422 family](https://support.apple.com/en-us/102207?ref=davinciresolveclub.com): choose LT, 422 or 422 HQ for the quality, generation count, storage budget and delivery needs of the job. LT is more compressed than 422; HQ uses a higher data rate. Do not treat HQ as automatically necessary. - **A short test first**: import the test beside the original and verify picture, audio, timecode, duration, levels and sync before batching. Intermediate files are usually much larger than long-GOP camera originals. That's the tradeoff for predictable decoding, not evidence that every H.264 or H.265 clip needs conversion. Keep supported sources native when they're stable. DaVinci Resolve Studio broadens professional-format and accelerated H.264/H.265 support, as Blackmagic's [Studio feature page](https://www.blackmagicdesign.com/products/davinciresolve/studio?ref=davinciresolveclub.com) explains. It can't repair corrupt media or reconnect a missing drive. If the stream is supported but native playback still fails, compare the machine and driver with the current [Resolve system requirements](https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/) before buying around one codec symptom. ## When red frames point to variable frame rate Phones, meeting tools, game capture, and screen recorders can produce variable-frame-rate media. VFR is a useful suspect when the clip imports but shows intermittent red frames, drifts against audio, or behaves differently while seeking. It isn't proof: storage interruptions, damaged frames, and decoder failures can look similar. Check Frame rate mode in MediaInfo. If the symptom follows one VFR source, preserve the original and make one CFR test. HandBrake's [official frame-rate documentation](https://handbrake.fr/docs/en/latest/technical/frame-rates.html?ref=davinciresolveclub.com) says Constant Frame Rate with Same as Source converts variable portions to a constant rate without casually choosing a different cinematic frame rate. Verify duration and audio sync after conversion. Do not assume every phone, GoPro, OBS, or Cinematic-mode file is VFR, and don't assume every VFR clip will fail. Read the actual file, test the exact failing section, and convert only when the controlled CFR comparison removes the symptom. ## If relinking does not find the correct media The relink didn't work. You pointed Resolve at the right folder, it ran its search, and the clips are still showing offline. A few things can cause this. First verify that the file opens outside Resolve and that the current user can read the drive or folder. Compare the path recorded for the offline clip with the real location. In Resolve 21, **Preferences > System > Media Storage** defines the scratch location, attached-media access, path mapping, proxy location and default cache locations. Adding a location there isn't a substitute for relinking a broken source relationship. For synced storage, verify a complete local file rather than a cloud placeholder. In OneDrive, an online-only file can appear in File Explorer without being stored on the PC. Use [Always keep on this device](https://support.microsoft.com/en-us/office/save-disk-space-with-onedrive-files-on-demand-for-windows-0e6860d3-d9f3-4971-b321-7092438fb38e?ref=davinciresolveclub.com) for the required media and wait for the download to finish. Open the file locally, then compare its local path with Resolve before relinking. A cloud item still being present does not prove that the old local path remains valid. If the source plays in the Media Pool but a timeline event is wrong or offline, check whether that event is connected to the intended Media Pool clip. Conform Lock With Media Pool Clip changes that relationship; it is not a general missing-file repair. Work on a duplicate timeline and verify the source first. The source must be at least as long as the selected timeline clip. Resolve uses matching timecode to align it; if timecode does not match, it can align the clips at their first frames instead. Check the resulting in/out frames and sync rather than trusting that an online event is the right take. ## Prevent the same failure on the next project The cleanest habit: set your folder structure before you import anything into Resolve. Once a clip is in the Media Pool, treat its location on disk as permanent. Don't reorganize, rename, or move it unless you're ready to relink. For a dedicated media drive on Windows, assign and document a stable, available drive letter before importing the job; do not change the letter of a Windows or application volume. On macOS, keep the volume name stable. For collaboration, agree on a folder structure and use Resolve’s path-mapping or relink tools when machines cannot share identical roots. [Export important projects as DRP files](https://davinciresolveclub.com/how-to-save-work-davinci-resolve/) and keep project-library backups, but remember that a DRP doesn't contain camera originals. For a portable handoff, use Media Management or export a Project Archive and choose the media, proxies and cache the handoff actually requires. Before [exporting video](https://davinciresolveclub.com/export-video-davinci-resolve/), disable proxies, optimized media and render cache for a short camera-original playback test. Inspect the first and last frame of relinked clips and render a representative range. Playback settings do not determine every Deliver setting. For this original-media test render, leave Use proxy media, Use optimized media and Use render cached images unchecked in Render Settings. For the final export, choose deliberately whether to use those generated files and verify their quality. A green Media Pool thumbnail does not prove that every timeline event points to the intended take. If Deliver stops on a processing error rather than showing an offline source, continue with the [render-failed checklist](https://davinciresolveclub.com/davinci-resolve-render-failed/). ## Media Offline FAQ ### Why does DaVinci Resolve say media offline when my files are there? A stored path can be wrong even when the files still exist, but path is only one branch. Compare the recorded path with the real location, confirm drive access, then test the original with proxies, optimized media and render cache disabled. If the clip also fails on import, inspect its codec and stream fields. ### Why can media show offline during import or after reopening a project? If the clip fails immediately on import, check whether the source is readable and supported: inspect it with MediaInfo and compare its stream with Blackmagic’s codec table for your OS and edition. After reopening, first check that the expected drive or network share is mounted and cloud media is available locally. Cache persists between sessions, so repeat the original-only playback test instead of assuming that closing the project cleared it. ### Does deleting the render cache fix media offline errors? Only when the symptom follows generated cache playback. First test the original with proxies, optimized media and render cache disabled, then re-enable each separately. Clearing cache cannot repair a moved source, unavailable drive, unsupported stream or damaged file. ### Can I fix media offline without relinking every clip manually? Yes. Select the relevant offline clips or bin and use Relink Selected Clips or Relink Clips for Selected Bin, then point Resolve to the folder containing the originals. Inspect several matches before accepting a large relink. ### What's the difference between Relink and Replace in DaVinci Resolve? Relink is for reconnecting an offline source relationship, normally to the same media at a new location. Replace deliberately swaps the source for another file. Use Replace only when a source substitution is intended and you have checked duration, timecode, audio, and framing. ### Why do only a few frames show Media Offline in DaVinci Resolve? Intermittent red frames do not prove a broken path. Test the camera original with proxies, optimized media and render cache disabled, check whether the same frames fail outside Resolve, and inspect the stream for damage or variable frame rate. Preserve the original and make one constant-frame-rate test only when the symptom follows that source. This guide is part of the [Fix DaVinci Resolve troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/). If your issue is Media Offline, slow playback, render failure, no audio, or project recovery, start there. ### DaVinci Resolve System Requirements (2026) URL: https://davinciresolveclub.com/davinci-resolve-system-requirements-2026/ Last updated: 2026-09-09T00:18:15.000Z **DaVinci Resolve 21.1 has different minimums by platform.** The Windows list specifies 16 GB RAM, or 32 GB with Fusion, and a 4 GB GPU. The Mac list specifies Apple Silicon, macOS 15 Sequoia or later, and 8 GB memory, or 16 GB with Fusion. Linux lists Rocky Linux 8.6, 32 GB RAM and a discrete 4 GB GPU. The Windows-for-Arm list names Windows 11, Snapdragon X Elite and 16 GB RAM, or 32 GB for 4K or Fusion. [Studio advanced AI and background rendering have higher requirements](#studio-ai-and-background-rendering-requirements); do not use the 4 GB base GPU figure for those features. Those are compatibility floors for the current build, not a promise of smooth playback. Source codec, resolution, frame rate, simultaneous streams, Color and Fusion processing, AI tools, cache format and delivery settings decide which component becomes the bottleneck. Checked against Blackmagic's separate [Resolve 21.1](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) and [Studio 21.1 release readmes](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com), both updated September 8, 2026\. Before updating a working machine, check the exact installer, operating system and driver combination. The illustration below records the earlier 21.0.4 baseline; use the current tables and Studio-specific limits in this text for 21.1. ![Official DaVinci Resolve 21.0.4 minimum system requirements for Windows macOS Windows Arm and Linux](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/resolve-21-0-4-official-floor.webp) Blackmagic's Resolve 21.0.4 compatibility floors as checked August 12, 2026\. Driver versions are build-specific, so recheck the readme before updating. ## DaVinci Resolve System Requirements for Windows These are the base Windows requirements. Studio's advanced AI and background-rendering limits are listed separately below. Scroll sideways to see all three columns. | Windows component | Official Resolve 21.1 minimum | What to verify | | ----------------- | ------------------------------------------ | -------------------------------------------------------------------- | | OS | Windows 10 Creators Update | Current updates and supported drivers | | Memory | 16 GB; 32 GB with Fusion | Leave headroom for the OS and other apps | | GPU | Integrated or discrete, at least 4 GB VRAM | Codec, effects and timeline workload | | GPU API | OpenCL 1.2 or CUDA 12.8 | API supported by the selected GPU | | NVIDIA | Studio driver 581.57 or newer | Exact floor for this build | | AMD/Intel drivers | Official drivers from the GPU manufacturer | Check support for your exact GPU and OS | | Desktop Video | 12.9 or later for monitoring | For Blackmagic monitoring hardware, not an ordinary computer display | A 16 GB Windows machine can meet the requirement and still have little headroom once the operating system, browser, background services and Resolve share memory. Judge it with representative media and effects rather than an empty project. Fusion has a separate 32 GB official floor because composites can add substantial system-memory demand. If this is a first editing setup, the [Resolve beginner workflow](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) shows the pages and tasks the machine will actually run. For Resolve 21.1, Blackmagic lists NVIDIA Studio driver 581.57 or newer on Windows. That number is build-specific. Before updating Resolve or the driver, open the [current Blackmagic support readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com), record the working versions, and keep a rollback path. Blackmagic still lists Windows 10 Creators Update as the software minimum. That is not a security-support recommendation: [standard Windows 10 Home and Pro support ended on October 14, 2025](https://learn.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro?ref=davinciresolveclub.com). Check your Windows edition and update coverage separately; Resolve compatibility alone does not establish that an OS installation is supported. ## System Requirements for macOS Blackmagic's [Resolve 21.1 readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) lists macOS 15 Sequoia or later, 8 GB system memory or 16 GB with Fusion, and an Apple Silicon computer. Resolve 21 therefore doesn't support Intel Macs. If you must keep an Intel Mac in service, stay on a compatible earlier Resolve build and verify that build's own readme before changing macOS. Scroll sideways to see all three columns. | macOS component | Official Resolve 21.1 minimum | Practical check | | --------------- | ----------------------------- | ------------------------------------------ | | OS | macOS 15 Sequoia or later | Resolve 21 does not support Intel Macs | | Memory | 8 GB; 16 GB with Fusion | Test the intended media and effects | | Computer | Apple Silicon | Choose memory for the complete workload | | Desktop Video | 12.9 or later for monitoring | Needed with Blackmagic monitoring hardware | Apple Silicon uses [unified memory shared by the CPU and GPU](https://www.apple.com/newsroom/2020/11/apple-unleashes-m1/?ref=davinciresolveclub.com). That avoids a separate VRAM pool, but it doesn't make 16 GB unified memory equivalent to a fixed amount of Windows system RAM or discrete VRAM. Resolve, macOS, the GPU and other applications all draw from the same capacity. Buy and test for the full workflow, not a cross-platform memory slogan. The 8 GB Mac figure is an application baseline, not a recommendation for every 4K job. Fusion needs 16 GB, and Studio publishes additional AI and background-work requirements. Larger composites, high-resolution media and simultaneous streams can need more headroom; test the intended workload before committing the machine to paid work. ## System Requirements for Linux and Windows ARM Resolve 21.1 lists Rocky Linux 8.6, 32 GB system memory, a discrete GPU with at least 4 GB VRAM, OpenCL 1.2 or CUDA 12.8, and NVIDIA Studio driver 580.119.02 or newer when using NVIDIA. For AMD GPUs, use the manufacturer's official drivers. Blackmagic monitoring hardware needs Desktop Video 12.9 or later. CentOS isn't listed in this build's Linux minimums. Treat the OS and driver lines as build-specific support requirements. ![DaVinci Resolve computer requirements mapped to decode, GPU, memory, storage and delivery workload](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/workload-model-v1.webp) Describe the real job before sizing hardware: resolution, frame rate, camera media, effects and delivery all change the bottleneck. The Windows-for-Arm minimum section names Windows 11 for Arm and a Qualcomm Snapdragon X Elite series processor, with 16 GB memory or 32 GB for 4K or Fusion. Resolve 21.1 also adds native support for NVIDIA RTX Spark systems on Windows. That separately named support does not mean every Snapdragon or other Arm laptop qualifies; check the exact build and machine instead of treating "Arm" as a compatibility guarantee. Linux can fit managed facility pipelines, but it isn't automatically faster or more stable than Windows or macOS. Codec support, GPU drivers, storage, monitoring hardware and the surrounding pipeline matter. Choose it when the whole configuration is supported and tested, not because of a blanket platform claim. ## Studio AI and background rendering requirements The [Studio 21.1 readme](https://www.blackmagicdesign.com/support/content/readme/baf7c071c0524fbf8ccc961925c9f443?ref=davinciresolveclub.com) adds these feature-specific memory requirements. Meeting the ordinary application minimum does not meet every Studio feature minimum. Scroll sideways to see all three columns. | Platform | Advanced AI tools | Background work | | ----------------- | ---------------------------- | ---------------------------------------------------------- | | Apple Silicon Mac | At least 16 GB system memory | At least 32 GB for background rendering and analysis | | Windows x86 | At least 16 GB VRAM | At least 32 GB RAM and 12 GB VRAM for background rendering | | Linux | At least 16 GB VRAM | At least 32 GB RAM and 12 GB VRAM for background rendering | The Windows-for-Arm section does not publish equivalent advanced AI/background limits. Do not apply the x86 discrete-VRAM table to an Arm system by assumption. On Mac, the listed memory is shared system memory—not a separate discrete-VRAM allocation. ## CPU and Laptop Requirements: What Blackmagic Does Not Specify Blackmagic's Resolve 21.1 readme doesn't name a universal Intel or AMD processor model, clock speed or core count for x86 Windows or Linux. It does name Apple Silicon for macOS and Snapdragon X Elite for Windows on Arm. Treat any Core i5 or Ryzen 5 minimum you see elsewhere as third-party shorthand, not an official Resolve 21 requirement. Choose the CPU by the media and task. Long-GOP H.264/H.265 decoding, RAW processing, Fusion and export don't stress the same parts of a system, and more cores alone don't settle the choice. [Puget Systems' current Resolve CPU guidance](https://www.pugetsystems.com/solutions/video-editing-workstations/davinci-resolve/hardware-recommendations/?ref=davinciresolveclub.com) recommends comparing tested workload performance instead of buying from core count. [A laptop can run Resolve](https://davinciresolveclub.com/best-laptop-for-davinci-resolve/) when it meets the build's OS, memory, GPU/API and driver floor, but test the intended codec, effects and power mode on that exact machine before assuming smooth 4K work. ## GPU Requirements: What 4 GB VRAM Actually Gets You Four gigabytes of VRAM is the base Windows and Linux figure for Resolve 21.1, not a 4K recommendation. Studio's advanced AI tools have a separate 16 GB VRAM minimum on Windows x86 and Linux. Timeline resolution, frame format, simultaneous streams, Fusion, temporal effects and noise reduction all affect the memory your actual project needs. Build a short stress timeline from your own camera media. Include the heaviest grade, Fusion composition, retime, titles and delivery codec you expect to use. Check playback, cache completion, GPU memory, export and reopening. A simple node can be expensive and a long node tree can be light, so node count alone is not a hardware metric. A one-minute sample can reveal a bottleneck; it does not validate every long render or sustained thermal load. Keep [PugetBench's Windows prerequisites](https://www.pugetsystems.com/pugetbench/creators/davinci-resolve/?ref=davinciresolveclub.com) separate from application and feature requirements: - **Basic preset:** a discrete GPU with 6 GB VRAM; the preset can run in Free or Studio. - **Standard/Extended presets:** a discrete GPU with 8 GB VRAM, and DaVinci Resolve Studio. These are requirements for running benchmark presets. They do not override Resolve 21.1's higher advanced AI requirements or certify your own 4K project. For a separate workstation-planning reference, [Puget's current GPU guidance](https://www.pugetsystems.com/solutions/video-editing-workstations/davinci-resolve/hardware-recommendations/?ref=davinciresolveclub.com) recommends 12 GB VRAM for a 4K timeline. That is independent advice, not a Blackmagic minimum—and 12 GB still falls below Studio 21.1's 16 GB advanced AI line on Windows x86 and Linux. Compare results from the same benchmark version, edition and preset, then check the exact card's codec support, power and cooling. The free Resolve 21.1 build supports one processing GPU on Windows and Linux; Studio adds multi-GPU support. That doesn't mean every Studio workflow benefits equally from a second GPU. Use the [Free vs Studio comparison](https://davinciresolveclub.com/davinci-resolve-vs-studio/) to identify the tools the project needs, then check current benchmarks before buying hardware around one edition difference. ## RAM Requirements for Real Workflows The base system-memory figures are 16 GB on Windows, or 32 GB with Fusion; 8 GB on Apple Silicon Mac, or 16 GB with Fusion; and 32 GB on Linux. The Studio table above adds feature-specific requirements. More RAM can help larger projects and multitasking, but it cannot compensate for every decoder, GPU or storage bottleneck. Separate memory pressure from storage and GPU pressure before spending money. Reproduce the slow section, close unrelated applications, observe system and GPU memory, then repeat with the [Resolve proxy workflow](https://davinciresolveclub.com/davinci-resolve-proxy-workflow/) or a lighter effect branch. If only the decode path changes the result, adding RAM may not address the real bottleneck. A cautious planning ladder: - **Meet the official floor first:** use the exact operating-system and Fusion minimum for the current build. - **Add workload headroom:** allow for other applications, longer timelines, larger frames and simultaneous streams. - **Test the worst minute:** include the real codec, grade, Fusion, Fairlight and export settings. - **Keep an upgrade path:** memory that can't be upgraded later deserves extra planning at purchase time. Low-memory symptoms can resemble slow storage, difficult codecs and GPU pressure. Use the operating system's memory view together with Resolve playback, cache and export tests. If the machine already meets the build floor but playback is failing, follow the [slow-playback diagnostic](https://davinciresolveclub.com/davinci-resolve-slow-playback/) before treating RAM as the answer. One metric or one smooth empty timeline isn't enough to size a production machine. ## Storage Requirements and Drive Setup Start with media throughput and free space, not a fixed number of drives. ![One-minute DaVinci Resolve system test with native media, multicam, grade, effects, Fusion and audio](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/one-minute-system-test-v1.webp) Measure playback, cache, memory, export and reopen behavior on one representative minute using the planned Resolve version and driver. Resolve may read source media while writing cache or proxies. Separating active media and generated cache can reduce competing I/O and makes capacity management easier, but three drives aren't a universal requirement. One sufficiently fast, healthy drive can handle modest work; high-bitrate or multi-stream jobs need measured throughput and enough free space. A practical layout to test: - **OS and applications:** the system drive, with enough free space for updates and temporary files. - **Cache and proxy media:** a fast location with monitored free space; separate it when the workload benefits. - **Camera originals:** reliable storage fast enough for the codec, resolution and number of streams, with a separate backup. Don't infer required storage speed from resolution alone. Compressed camera media, RAW, image sequences, multicam and cache formats can have radically different data rates at the same frame size. Measure the real media stream and leave margin for simultaneous reads and writes; use RAID or network storage only when capacity, redundancy and shared access justify the added complexity. ## Before upgrading to Resolve 21.1 The [21.1 release readme](https://www.blackmagicdesign.com/support/content/readme/59dd4eef1f4941c29fb8dc48b33f5c87?ref=davinciresolveclub.com) distinguishes project-library compatibility from project compatibility: a library can remain accessible to 20.3.2, but an individual project created or opened in 21.1 will no longer open in 20.3.2\. Back up the full project library and individual projects before opening them in the new version. Keep a record of the working Resolve, OS and driver versions, with a usable rollback path. If a supported machine stops launching or rendering after an update, use the [Resolve troubleshooting hub](https://davinciresolveclub.com/fix-davinci-resolve/) to separate launch, media, GPU-memory and render failures before buying replacement hardware. ## System Requirements FAQ ### What CPU does DaVinci Resolve 21 require? Blackmagic's 21.1 minimum list does not name an Intel or AMD x86 processor model or core count. It names Apple Silicon for Mac and Snapdragon X Elite in the Windows-for-Arm section; the release notes also add native NVIDIA RTX Spark support on Windows. For x86 Windows or Linux, compare workload benchmarks instead of treating a generic Core i5 or Ryzen 5 label as an official minimum. ### Can DaVinci Resolve run on 8 GB RAM? The Resolve 21.1 Mac baseline lists 8 GB, but requires Apple Silicon and macOS 15 or later. Fusion and Studio advanced AI need at least 16 GB on Mac; Studio background rendering and analysis need at least 32 GB. Windows starts at 16 GB, or 32 GB with Fusion, and Linux at 32 GB. ### Does DaVinci Resolve work on integrated graphics? The 21.1 Windows minimum list permits an integrated or discrete GPU with at least 4 GB VRAM and OpenCL 1.2 or CUDA 12.8 support. That baseline does not guarantee smooth 4K or meet Studio's separate advanced-AI requirements. Linux's list specifies a discrete GPU. ### What NVIDIA driver does DaVinci Resolve 21 require? For Resolve 21.1, Blackmagic lists NVIDIA Studio driver 581.57 or newer on Windows and 580.119.02 or newer on Linux. These are build-specific floors; verify the readme for the installer you use. ### Do DaVinci Resolve Free and Studio have different hardware requirements? They share the base platform requirements, but the Studio 21.1 readme adds higher limits for advanced AI and background work. Advanced AI needs at least 16 GB memory on Mac or 16 GB VRAM on Windows x86/Linux. Background rendering needs at least 32 GB memory on Mac, or 32 GB RAM plus 12 GB VRAM on Windows x86/Linux. Free supports one processing GPU on Windows and Linux; Studio adds multi-GPU support. ### Does DaVinci Resolve run on Windows ARM? Yes. The 21.1 Windows-for-Arm minimum section lists Windows 11, Snapdragon X Elite and 16 GB memory, or 32 GB for 4K or Fusion. The release notes separately add native NVIDIA RTX Spark support on Windows. Neither statement is blanket approval for every Arm laptop; check the exact system and build. ### What macOS version does DaVinci Resolve 21 require? Resolve 21.1 requires macOS 15 Sequoia or later and an Apple Silicon computer. Intel Macs are not in the supported 21.1 Mac baseline; check an earlier Resolve build's own readme before changing an Intel Mac's installation. ### How much storage does DaVinci Resolve need? Blackmagic's minimum-system list does not prescribe a universal project-drive capacity. Allow space for the application, originals, proxies, cache, exports and backups, then measure the real media data rate. Separate generated cache when testing shows an I/O or capacity benefit. For driver, codec and machine-specific questions, use the [Hardware & Compatibility hub](https://davinciresolveclub.com/davinci-resolve-hardware-compatibility/). To compare a configuration against the listed baseline, try the [Resolve PC checker](https://davinciresolveclub.com/davinci-resolve-pc-checker/); it uses the values you enter and does not scan your computer. ### How to Add Text in DaVinci Resolve URL: https://davinciresolveclub.com/how-to-add-text-in-davinci-resolve/ Last updated: 2026-09-13T08:33:52.000Z On the Edit page, open Effects > Toolbox > Titles, drag Text above your footage, select the title clip and type in Inspector > Title > Rich Text. Trim the title to the time you want it on screen. That is enough for a name, label or opening title; you do not need to build a Fusion composition first. For motion, several text layers or timed dialogue, choose the appropriate tool below. If you are learning the rest of the editor, the [DaVinci Resolve learning path](https://davinciresolveclub.com/davinci-resolve-tutorial/) connects this step to the rest of your first edit. ## DaVinci Resolve Text Tools: Which One to Use A title becomes part of the video picture. A subtitle track can also deliver a separate timed caption file. Choose accordingly: - Text: quick titles, credits and lower thirds with rich-text styling - Text+: layered shading, Character Level Styling, path layouts, Write On and deeper animation - MultiText: several independently editable text layers inside one Text+-based title - Fusion Titles: prebuilt animated templates whose exposed controls vary by template - Subtitle track: timed captions for SRT/VTT export, separate delivery, embedding or burn-in Text+ isn't a strict replacement for Text. Text handles mixed formatting directly in Rich Text. Text+ can change selected characters through its Character Level Styling modifier, then adds layered shading, shape and path layouts, Write On controls and deeper Fusion animation. MultiText is the better choice when several separately editable text layers belong inside one title. ## How to Add Text Using the Basic Text Tool Open the Edit page, then Effects > Toolbox > Titles. Drag Text to a video track above the footage for an overlay, or onto an empty section for a title over black. If the page layout is still unfamiliar, start with the [DaVinci Resolve beginner tutorial](https://davinciresolveclub.com/davinci-resolve-tutorial-beginners/) before styling the title. ![Text title tile, title clip above footage and Rich Text field with three numbered annotations](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/basic-text-annotated-v1.webp) AI-assisted annotation of title controls using a Cut-page reference. On Edit, open Effects > Toolbox > Titles; on Cut, open Titles. Select the title clip before changing Rich Text. Select the title clip and open Inspector > Title. Enter the copy in Rich Text, select any words that need separate styling, then set font family, face, color, size, alignment, stroke, drop shadow or background. Title clips default to five seconds unless Standard generator duration has been changed in User Preferences; trim the clip edges to set the real screen time. For the original Text generator, park the playhead over the title and click its text in the Timeline Viewer to reveal on-screen transform controls. Drag to position it, use the Inspector for exact values, or double-click the visible text to edit characters directly. OpenFX Overlay is for OpenFX controls, not the Text title's position handle. If the title is invisible, first park the playhead inside its duration and check that it sits above the footage, not underneath an opaque video clip. Confirm the title track is enabled. Test a plain Text title before adding a complex template; that separates placement problems from styling or template problems. Text, Text+ and MultiText use fonts available on the workstation. Resolve 21's Font Browser can search, filter and preview installed families. If a project opens without a Text+ font, Resolve shows a missing-font overlay; install the intended family and face or choose a deliberate substitute, then check line wraps and spacing again. Text remains useful for mixed-style lines, fast credits and simple lower thirds. Its Inspector also includes stroke, drop shadow and a flexible rectangle or rounded-rectangle background. Move to Text+ for layered shading, Write On, path layout or character-, word- and line-level motion. ## Text+ and MultiText: More Control Use Text+ when the design needs deeper styling or motion. Blackmagic introduced MultiText in [DaVinci Resolve 20](https://documents.blackmagicdesign.com/SupportNotes/DaVinci%5FResolve%5F20%5FNew%5FFeatures%5FGuide.pdf?ref=davinciresolveclub.com). The [Resolve 21 text update](https://www.blackmagicdesign.com/products/davinciresolve/whatsnew?ref=davinciresolveclub.com) improves MultiText positioning, pivot, alignment and CSV import, while adding a font browser, multilingual spell checking, emoji and broader color-font support to Text+ and MultiText. For per-character formatting in Text+, apply Character Level Styling and select the characters in the Fusion viewer, then change their attributes in the Modifiers controls. Selecting letters in the modifier's text-entry box is not the same operation. ![DaVinci Resolve 21 Text+ Inspector with spell checking active beside the title in the viewer](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/text-plus-real-ui.webp) Text+ keeps typography, layout, transform and shading controls together; Resolve 21 also flags spelling in the viewer and Inspector. Drag Effects > Toolbox > Titles > Text+ to the timeline and select it. Its title controls are organized into Text, Layout, Transform and Shading panels, with common clip controls in Settings. Type in the text box on the Text tab, settle the layout and shading, then animate only the properties the shot needs. Text+ is a Fusion title available from the Edit page. Select the title and switch to the Fusion page when you need its node graph. In the Edit-page viewer, choose Fusion Overlay to edit and move Text+ on screen. Layout can place text at a point, in a frame or circle, or along a path. Shading separates fill, outline, shadow and glow-like treatments into layers. Each enabled element has its own appearance and transform controls. Build the simplest stack that produces the design, because extra shading elements and blur can increase Fusion render work. Use MultiText when one title needs several independently editable layers, such as a headline, name and role that must stay together. Its Inspector keeps every layer in a persistent Text List. The Text+-based tool supports Point, Text Box and Circle layouts, plus CSV import for column-aligned text. Keep separate timeline title clips when the elements need different timing rather than forcing unrelated animation into one MultiText object. When the design needs a reusable rounded panel behind several text elements, build the fill with a Fusion Background node and Rectangle mask instead of forcing every layer into Text+ shading. The [rounded-corners guide](https://davinciresolveclub.com/round-corners-davinci-resolve/) walks through that panel setup, including its rounded edges and transparency. ## Fusion Titles: Pre-Built Motion Graphics Fusion Titles are prebuilt Fusion compositions in the Titles browser. Turn Hover Scrub Preview on, move across a thumbnail to inspect its animation, then drag the chosen template to the timeline and open the Inspector. The Inspector exposes only the controls the template author published. Check the available text fields, colors and timing controls before committing to a look; two templates can expose very different options even when their thumbnails seem similar. If a required property isn't exposed, select the title and open the Fusion page to inspect its nodes. Duplicate the title before structural changes so the original remains an easy fallback. The [Fusion beginner guide](https://davinciresolveclub.com/davinci-resolve-fusion-tutorial-for-beginners/) explains the MediaIn, Merge and MediaOut flow before you edit a template graph. To reuse a finished title in this project, drag it from the timeline into the Media Pool, then drag a fresh copy back to the timeline when needed. Change the wording and check its duration and animation again. For timeline copies, follow the [clip duplication guide](https://davinciresolveclub.com/duplicate-clip-davinci-resolve/) so the copy goes to the intended track without overwriting footage. ## Subtitle Track: Right Tool for Captions Subtitle tracks store timed caption items. They can be exported as SRT or VTT, delivered as separate files, burned into video, or embedded in supported formats. Text, Text+ and MultiText titles are video graphics and can't later be exported as ordinary timed subtitle data. Use the [subtitles and captions guide](https://davinciresolveclub.com/davinci-resolve-subtitles-captions/) when import, formatting and delivery are the main job. ![DaVinci Resolve subtitle track and Captions Inspector with timed English and French subtitle lines](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/08/subtitle-track-real-ui.webp) Use a subtitle track when the words need timing, track-level styling and caption-file export rather than becoming a video graphic. Right-click any timeline track header and choose Add Subtitle Track. You can also drag a Subtitle generator from Effects > Titles onto the subtitle area. Name the track by language or use because the track name is used during export and encoding. Select the subtitle destination track and place the playhead where the line starts. Right-click the track and choose Add Subtitle. In Inspector > Captions, Create Caption starts an empty track; Add New adds another item once captions exist. Enter the line and trim its edges to the spoken phrase. Select the subtitle track header and open its Track Style controls in the Inspector to set a consistent font, background and position. The caption view pictured in this section uses Use Track Style to inherit those settings. The manual also uses the labels Track and Customize Caption. Check which controls your build shows rather than looking for a checkbox that is not there. Keep the track style for ordinary lines; override it only where the caption needs a different treatment. ## Auto Captions: What You Actually Need Create Subtitles from Audio is Studio-only in Resolve 21\. The free version can create, import, edit, style and export subtitle tracks manually, but it does not include Blackmagic's native AI transcription command. Follow the [Resolve transcription workflow](https://davinciresolveclub.com/transcribe-audio-davinci-resolve/) for speaker review and caption cleanup. Blackmagic documents the Studio requirement in its [subtitle instructions](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveReferenceManual.pdf?ref=davinciresolveclub.com). In Studio, open the Edit page and choose Timeline > AI Tools > Create Subtitles from Audio. Select an In/Out range first if only part of the timeline should be transcribed. In the dialog, choose Language, Caption Preset, Max Characters per Line, one or two Lines, and Gap Between Subtitles, then click Create. Resolve writes to the highest subtitle track, or creates one when none exists. Review every caption for names, punctuation, line breaks and timing before delivery. When dialog overlaps on several audio tracks, mute the tracks that shouldn't be analyzed before running transcription. Don't change the timeline start timecode solely because an SRT is being exported. Export the subtitle track, open the file in a text editor or the destination platform, and verify the first, middle and last cues against picture. Move subtitle items only when a real offset is present. ## How to Animate Text Select the title clip, open Settings > Transform and put the playhead at the frame where motion should begin. For a small scale-up, leave linked Zoom X and Y at 1.000 and click the diamond beside Zoom. Move the playhead later in the title and change the linked Zoom values to 1.100\. Resolve adds a keyframe there; play the interval to judge the speed. These are example values, not a preset you must use. ![Title Zoom keyframes at two different frames, with linked values of 1.000 and 1.100](https://storage.ghost.io/c/a9/29/a929429b-cfab-4467-b902-a0cd9c90feac/content/images/2026/09/title-keyframes-v2.webp) Annotated example based on the Transform controls: set a Zoom keyframe, move to another frame and change the value. The two markers represent different times, not two playheads. A short fade, vertical move or scale change is usually enough. Keep the title inside safe areas, preview at delivery resolution and leave enough time for the viewer to read the full line. For a fade, animate Composite opacity instead. Text+ also has a Write On range control for revealing or removing characters; animate that range when you want a type-on effect. The Follower modifier handles staggered character animation. These title controls have their own animation settings: the common Settings panel does not globally enable keyframing for Text+. For more complex title animation, use the node tree for timing curves, motion paths and layered effects. Continue with the [Fusion learning map](https://davinciresolveclub.com/davinci-resolve-fusion/) when the task has moved beyond an Edit-page title clip. ## Frequently Asked Questions (FAQ) ### Why can't I use my custom font in DaVinci Resolve? These tools use fonts available on the workstation, but a family or face may be missing, unsupported or different on another computer. Use Resolve 21's Font Browser to confirm the exact family and face. When Text+ reports a missing font, install the correct font or choose a documented substitute, then check line wraps and spacing again. ### What is the difference between Text, Text+ and MultiText in DaVinci Resolve? Text is the quick Edit-page generator for ordinary rich-text titles. Text+ uses the Character Level Styling modifier for selected characters, then adds layered shading, Write On controls, shape and path layouts, and Fusion animation. MultiText is built on Text+ and keeps several independently editable text layers inside one title. ### How do I add lower thirds in DaVinci Resolve? For a fast two-line lower third, try the built-in L, M or R Lower 3rd generator; each provides separate rich-text lines and position controls. Use Text+ or a Fusion Title when the design needs layered shading or animation, and keep the text inside the title-safe area. ### Can I export subtitles from DaVinci Resolve as an SRT file? Yes. Choose File > Export Subtitle, or right-click the subtitle track header and choose Export Subtitle, then select SRT or VTT. Text, Text+ and MultiText overlays are video graphics, so they can't be exported as a timed subtitle file. Verify several cues after export instead of changing timeline timecode by default. ### Is auto captioning in DaVinci Resolve free? No. Resolve 21's Create Subtitles from Audio command is a Studio feature. The free version can still add captions manually, import supported subtitle files, style subtitle tracks, and export SRT or VTT. ### How do I position text precisely in DaVinci Resolve? For the standard Text generator, click the visible title in the Timeline Viewer to reveal its on-screen transform controls, or enter exact Position values in the Inspector. For Text+, choose Fusion Overlay in the viewer. OpenFX Overlay controls OpenFX filters and isn't the correct overlay for either title workflow.