How to Update DaVinci Resolve Safely

My rule is simple: the new build must never touch your 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 one of those recovery layers is missing, the update waits.

The installer is rarely the dangerous part. The risky moment comes when you open a project in a newer version and find out that an older build, a plug-in, a GPU driver or a collaborator's workstation can't reproduce it anymore. A safe update builds a rollback path before Resolve changes any project data.

Keep this maintenance checklist next to the DaVinci Resolve workflow guides. It's about changing an existing installation safely, not a first-install walkthrough or a guide to finding lost projects.

How to Update DaVinci Resolve: The Short Version

Here's the whole route on one screen. The sections below explain each backup layer and what to do when a step fails.

1. Export a DRP of every active project and back up the Project Library from Project Manager. Keep both outside the live library.
2. Choose DaVinci Resolve > Check For Updates. As the Resolve 21.1 Reference Manual puts it, Resolve notifies you about new versions and downloads them when they're available. You can also get the installer for your edition and platform from Blackmagic's support page. A Mac App Store copy updates through the App Store instead.
3. Quit Resolve and run the new installer. You don't have to uninstall first: Blackmagic support's long-standing advice on its forum is to install the new version over the current one.
4. Launch Resolve and open Project Manager. If a library shows an upgrade warning, click Upgrade Project Library only once the backup from step 1 exists. The manual's Project Library section notes that a whole-version jump usually needs this upgrade, while a dot release may or may not.
5. Choose DaVinci Resolve > About DaVinci Resolve and confirm the version number on the splash screen it opens.
6. Import a copy of one DRP under a new name and test it before you open live work.

Moving from Resolve 20 to 21 follows the same route. When Blackmagic announced Studio 21 on its forum on April 13, 2026, it said the release was available at no charge for existing customers. Studio 21 downloads still need a Studio license dongle, a Blackmagic Cloud license or an activation code, so grab the Studio installer if that's the license you own; the Free build is a separate download. The one-way part is the project: once 21 opens it, Resolve 20.3.2 can't open it anymore.

Check the Exact Release Before Opening Projects

Blackmagic's official stable-download feed returns DaVinci Resolve 21.1.2, build 10, posted October 27 as the second maintenance update to 21.1 from September 8. The 21.1.2 pre-install notes say Blackmagic has taken efforts to keep Project Libraries compatible with Resolve 20.3.2. Individual projects created or opened in 21.1.2, though, are no longer accessible in 20.3.2. Library access and project compatibility are two different checks, and that one sentence is the reason this guide exists.

So the only copy of a live Resolve 20 project is the last place I'd test that boundary. Export a pre-update DRP, make the full library backup, and install 21.1.2 only after both are verified. Then import the DRP under a new test name and open that copy. The untouched pre-21 project and backup stay put as your rollback source.

Recheck the build and edition on the official Resolve support page on the day you update. This guide follows 21.1.2, which won't stay the newest build forever. Read the pre-install notes for the exact download in front of you, because a point release can still affect project or library compatibility.

DRP, Project Library Backup, and DRA Are Not Interchangeable

The current Resolve 21 Reference Manual keeps these recovery layers apart. A normal DRP carries no source media and leaves out Gallery stills and LUTs. Export Project With Stills and LUTs adds those project assets, but still not the camera originals. A library backup and a DRA cover different scopes again, so one never stands in for another.

When to Delay an Update

I wouldn't change Resolve, the operating system, the GPU driver and your core plug-ins in the same maintenance window. If something breaks, you've got 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 OpenFX, audio plug-in, control panel, script or codec you haven't verified;
• another editor has to keep using the older version or a shared library;
• the exact update doesn't fix 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 it away from the delivery path. Scripts deserve their own look this time: the 21.1 notes say advanced scripting now requires DaVinci Resolve Studio, and Blackmagic moved Python scripting to Studio. If a Free-edition pipeline leans on scripts, that alone is a reason to wait.

Record the Working Baseline

Before you change anything, make a short reference render and write a plain checklist with:

• Resolve edition, full version and build number;
• operating system version and hardware architecture;
• GPU model, VRAM and driver version where they apply;
• the 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;
• the fonts, LUTs, DCTLs, macros, title templates, Power Bins and keyboard presets the job uses.

Keep Studio activation codes, passwords and license secrets out of screenshots and 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 on by default and saves changes incrementally as you work. Project Backups have to be turned on separately; they save complete project files at periodic intervals but leave out stills and LUTs to save space. By default those files land in a ProjectBackup folder on your scratch disk, and the Browse button moves them somewhere safer.

Loading a Project Backup opens it as an independent project, so the original is never overwritten. Timeline Backups are yet another switch: use them when you want restore points for one timeline, and in 21.1 a restored timeline backup keeps its backup history. Still, don't count them as a backup of the full project or library.

None of these replaces a manual export. The guide to saving work in DaVinci Resolve explains how manual saves, Live Save, Project Backups and DRP exports differ.

Live Save will faithfully preserve a bad change, and automatic backups stored on a failed system drive can vanish with it. Point the backup destination at independent, reliable storage with enough space, then make and test the DRP and library backup anyway.

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, the Resolve version it works in and the date, for example Documentary_R20.3.2_pre_R21.1_2026-09-15.drp.
5. Save it outside the live Project Library, ideally 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 you update. Check that it opens and holds the bins, timelines, grades, Fusion comps and Fairlight structure you expect.

If the job depends on Gallery stills or LUTs, use Export Project With Stills and LUTs and verify those too. A file that's never been imported is an unverified backup, however reassuring its size looks.

Back Up the Entire Project Library

For a Local or Network library, close the open project and show the Project Libraries sidebar in Project Manager. Select the exact library, click the circled "i" details icon and choose Back Up, then save the .resolve.backup file away from the live library. The Restore button at the top of the sidebar brings a backup back; give the test library a new name and location, and inspect its projects before you retire the old setup. For a managed Network library, coordinate with its administrator; the Project Server application has its own Back Up and Restore.

A library backup protects projects you forgot to export one by one and keeps library-level organization intact. The .drp exports still earn their place: they're small, direct recovery units if the library itself becomes unhealthy.

Cloud libraries back up somewhere else entirely. The Cloud backup procedure in the Resolve 21.1 manual has you open the Cloud library's Details in Project Manager, click Back Up and wait for a dialog confirming the backup was made to the cloud. Details > Restore lets you pick a version from the Backups list and give the restored library a new name. Have the owner or administrator check a separate restored copy, and keep exported DRPs and media outside the Cloud library too. A Cloud library backup isn't a downloaded .resolve.backup file.

Never delete a library, swap database internals or overwrite the original just to make room for an update. Restoring to a new name and location keeps both recovery paths open.

Not sure which library holds the project? The guide to where Resolve projects are saved walks through Local, Network and Cloud libraries without nudging you into manual edits inside them.

Protect Media and Custom Assets

Original camera files, audio, graphics and deliverables should already exist independently of Resolve. Confirm that backup instead of assuming proxy, cache or optimized-media folders are the originals.

For a portable critical project, right-click it in Project Manager and choose Archive; some sections of the 21.1 manual still call this Export Project Archive. Tick Media Files when camera originals must travel with it. Proxy Media on its own carries proxies, falling back to the original only for a clip that has no proxy. Add Render Cache only when you need it. Resolve 21.1 adds archive options for stills, LUTs and used media, so read every option in your installed build instead of trusting an older dialog.

A DRA is a folder, and it's no substitute for plug-ins, fonts, licenses or every other external dependency. Use Restore Project Archive to bring back a separate copy under a unique name, and inspect its media before you rely on it as cold storage. Restoring doesn't move the .dra folder, so put it on storage you'd edit from.

Back up custom dependencies separately:

• LUTs and DCTLs;
• Fusion macros, scripts, templates and third-party toolsets;
• fonts and title packages, along 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 details, without exposing credentials.

Download the Correct Installer

Download from Blackmagic's support page, not a mirror. Match three things: the operating system and architecture, DaVinci Resolve Free versus DaVinci Resolve Studio, and the exact stable build you plan to test.

Inside Resolve, DaVinci Resolve > Check For Updates looks for a newer build and downloads it when one is available. Go to the support page when you need a specific edition, platform or older installer. Blackmagic lists packages for macOS, Windows, Windows for Arm and Linux; pick the one that matches the exact system you tested.

Resolve can also look on its own. The manual's General preferences list two checkboxes in DaVinci Resolve > Preferences > System > General: Automatically Check for Updates, and Automatically opt-in for new beta program notifications, which tells you when a public beta comes out. I'd leave the first one on and the beta opt-in off on any machine that delivers client work, because a beta notice is an invitation to run a build nobody else on the job uses. For an installer older than the current one, the guide to DaVinci Resolve old versions covers Blackmagic's archive.

Keep the previous working installer in the recovery folder. Read the minimum requirements and release notes before installing, especially the GPU and operating-system lines. For 21.1 through 21.1.2 the Mac line starts at macOS 15 Sequoia on Apple silicon, and NVIDIA cards on Windows need Studio driver 581.57 or newer. The current Resolve system requirements help spot a machine that shouldn't move to the new build yet.

On a Mac, keep the distribution channel consistent. Update a Mac App Store installation through the App Store, and use Blackmagic's installer for the direct-download edition. Blackmagic's direct download and the US Mac App Store's Studio edition carry 21.1.2, both dated October 27; the Store's Free edition can trail the direct build, so check the version line on its listing before you compare.

Matching version numbers don't make the distribution channels or licenses interchangeable. The official Studio App Store listing warns that some control panels and third-party OpenFX or VST plug-ins may not be supported. A Store purchase is also a separate license, not an activation key for the direct installer; Blackmagic's September 2026 feature matrix for 21.1 says App Store licenses aren't interchangeable with other desktop or cloud licenses. Check your purchase channel before you switch distributions.

If the installer also offers control-panel components, change them only when the release notes and your hardware workflow call for it. One maintenance variable at a time keeps a rollback understandable.

The 21.1.2 notes say what the Resolve package adds: the application itself, utilities for setting up hardware control panels, Blackmagic RAW Player and Blackmagic Proxy Generator. Desktop Video comes from a separate download. If you monitor through Blackmagic video hardware, the same notes ask for Desktop Video 12.9 or later from Blackmagic's support center, so put its current version in the baseline note before deciding whether it needs to change at all.

For direct downloads, unpack the package and run its DaVinci Resolve installer. On macOS, open the disk image and double-click the installer icon; don't swap in a drag-to-Applications step. On Windows, run the extracted installer. On Linux, run the supplied installer on a supported system. The 21.1 platform installation instructions say to follow the onscreen prompts on all three platforms. Finish the backup and the restore test before you approve installation.

Install, Then Test an Imported Copy

1. Close Resolve and any dependent plug-in managers or Project Server administration tools.
2. Install following Blackmagic's instructions for that 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 under a name that clearly marks it as the Resolve 21 test.
6. Open only that copy first.

On a Network or Cloud library, one person should own the update, and the team should agree on the target Resolve build before anyone opens production projects. Not every version difference blocks a connection, but matching builds across the team rules that problem out. Match plug-ins, fonts and media access as well.

Creating a Cloud library includes choosing which Resolve version it's compatible with, and library upgrades happen in Resolve, not in the web interface. The manual's own rule of thumb: a whole-version jump usually needs a library upgrade, while a dot release may or may not. So follow the Cloud project-library instructions 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 apart: the Resolve application, the Project Library schema and the database engine behind 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 isn't an instruction to migrate a working database engine during the app update. Let the administrator plan any server migration on its own schedule.

Run a Real Post-Update Test

Opening the project without an error is only the first checkpoint. Test a representative timeline that contains 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, license state included;
• 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 your usual delivery codec;
• control panels, audio interfaces, and monitoring output.

Render the same short range you saved before the update and compare picture, audio, duration, frame rate and file properties. Then 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. Keep the logs and screenshots of the exact error, then separate the failure:

• Application won't launch: check the OS and GPU requirements, then follow Blackmagic's platform-specific uninstall/reinstall guidance.
• Project doesn't open: go back to the older application and the untouched pre-update .drp or a restored library copy.
• Plug-in is missing: check vendor compatibility and licensing before you replace the effect in a duplicate.
• Media is offline: reconnect storage and paths, and 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 isn't a rollback asset for Resolve 20.3.2. A safe downgrade starts from the untouched pre-update project, the verified DRP and the Project Library backup. If GPU memory or decoding turns out to be the failure point, work through the GPU memory troubleshooting guide before you change several system components at once.

Removing a newer direct-download build follows the routes in the 21.1.2 notes. On macOS, double-click the Uninstall Resolve icon. On Windows, open the Programs and Features control panel, select DaVinci Resolve and click Uninstall. On Linux, run the installer and choose its uninstall option. Then reinstall from the installer you kept, and I'd go back to the exact build in the baseline note, because the reference render came from that build. The fix for "A newer version of Resolve is already installed" explains why an older installer stops while the newer copy is still there.

Resolve Free vs Studio Updates

Free and Studio are separate downloads, so install the edition you already use. Replacing Studio with Free by accident can make Studio-only effects and codecs look unavailable even though the project data is still there.

Studio can be licensed with an activation code, a dongle or an assigned Blackmagic Cloud license. Keep the licensing material secure and within reach before maintenance, and never put activation details in a project note, screenshot or support post.

Common Update Problems

Projects are missing after the update

Open Project Manager and check which Project Library is connected. Reconnect the original library or import a .drp; don't start creating 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 the individual DRP exports exist. A library that stays connectable in 20.3.2 doesn't 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 and a compatible plug-in build, architecture and license. Test on a duplicate before removing or replacing nodes.

Resolve crashes after updating

Keep the logs, check the exact release notes and requirements, and work out whether the problem is application launch, GPU initialization, a plug-in, or one project. The broader Resolve crash guide keeps those branches apart.

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. Don't rebuild any settings until you've found the first mismatch.

Check For Updates doesn't offer the new build

If Resolve came from the Mac App Store, look for the update in the App Store, where the Free listing can trail the direct download. Otherwise compare the version on the About DaVinci Resolve splash screen with the build on Blackmagic's support page. When the support page is ahead, download that installer and run it over the current version; the menu check is a shortcut, not the only way in.

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.

I'd only update for a specific feature, fix or compatibility need. The Resolve 21 changes guide helps you decide whether that benefit is worth opening a maintenance window right now.

Once the update passes the test project, go back to the DaVinci Resolve tutorial roadmap and verify the editing, Fairlight, Fusion and export workflows you really depend on.

Safe Resolve Update FAQ

Will updating Resolve delete my projects?

An update shouldn't delete projects, but libraries can disconnect, project compatibility can change, and failures do 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 count on it. Blackmagic's Resolve 21.1 notes say a library can stay accessible in Resolve 20.3.2, but any project created or opened in 21.1 is no longer accessible in 20.3.2. Keep a pre-update DRP and a Project Library backup before you open the project.

Can I upgrade from DaVinci Resolve 20 to 21 for free?

Yes. The Free edition costs nothing in any version, and when Blackmagic announced Studio 21 on April 13, 2026, it said the release was available at no charge for existing customers. The Studio installer still asks for your license dongle, Blackmagic Cloud license or activation code.

Should I uninstall the old version first?

No, not as a routine step. Blackmagic support's advice on its forum is to run the newer installer over the current version. Keep the previous installer and verified backups first, and uninstall only when a clean reinstall is part of troubleshooting or the release notes for your platform ask for it.

How do I check which version of DaVinci Resolve I have?

Choose DaVinci Resolve > About DaVinci Resolve. The splash screen it opens shows the installed version, so compare that number with the build you meant to install before you open live projects.

Where should I store backups?

Outside the live Project Library, and preferably off the system drive. Important work should have one more copy on independent storage.

Should I update during an active project?

Only when the update fixes a blocking problem and there's time to test and roll back. Otherwise, finish the delivery on the build you know.

Jason Miller I run DaVinci Resolve Club, an independent publication. My guides explain editing, color, Fairlight, Fusion and delivery, with clear Free vs Studio limits.