DaVinci Resolve 17 Public Beta. Should you use it? How to update safely.

upcoming davinci resolve zoom workshops, autumn 2021.

I publish this series of free article and tutorials as a complement to my upcoming Online DaVinci Resolve Workshops, hosted in Zoom.

SPECIAL LIMITED OFFER: if you register in any of my workshops before September 10th, you pay only 95 Euros. This is a 100 Euros discount! After that date, prices will go back to the regular 195 Euros. So, don’t skip this opportunity!

Next DaVinci Resolve Zoom workshops are:

Time Zone: Central European Time (Berlin).


You heard the news: DaVinci Resolve 17 is here

DaVinci Resolve 17 is still free, with some limitations, and the paid Studio version keeps the same price (300 Euros).

Remember: if you pay for the Studio version, you get all future updates. It’s a one-time-only payment. Example: if you paid for DaVinci Resolve Studio 16, now you can have DaVinci Resolve Studio 17.

It all sounds very good, but should you install and use version 17 just yet?

First, we need to understand that what we have right now is the first Public Beta version of the software.


So, yes, you can download and use the Public Beta, here.

But, what is a Beta version exactly?

It basically means version 17 is not finished yet, and so, it can have bugs, errors, and be a little problematic.

And this is all normal.

All computer programs release Beta versions, to test them, and solve potential problems.

Same thing happens with Avid Media Composer, Premiere Pro, and Final Cut Pro X. The difference is, with this programs they release Beta versions in a more “private” way, through a selected group of users and Beta programs.

Blackmagicdesign offers Beta versions of DaVinci Resolve to the whole public, so we can get familiar with it, learn it, test it, try the new tools, etc..

And obviously, it’s important to understand we should NOT use the Beta version in any serious project. It’s just not ready for that!

Maybe in personal projects, with no deadlines, and being very careful, we could make and exception, but I can’t recommend this to everybody.

I’m already using DaVinci Resolve 17 in my workshops, because it just makes sense to study and know the new stuff, but in this particular case stability and bugs are not so relevant.

We’re just doing a workshop!


Now: DaVinci Resolve 17 is working well enough for me right now.

Yes, it can eventually crash con close. I would never use it just yet in a commercial project. But in my workshops, is behaving quite well!


Event considering all this, and all possible warnings, internet and social networks are now full of complaints about the new version.

And I don’t get it.

I just can’t understand how some users are updating to DaVinci Resolve 17, and then they’re having problems, and some of them are loosing work, and then they complain really loud about it.

Funnily enough, some users in Facebook event got to the point of requiring me, personally, to offer them solutions!

That’s just how the Internet is…

From now on, they will publish new and improved versions of the Beta, more stable, and probably with even more functions. The latest the Beta version, the better it will work.

Once more: we should NOT use a Beta version of any software in real, commercial, projects.

If you edit and grade non-commercially, or have a separate computer, or just wish to take the risk, there’s a couple of things you should do, to do the transition the safest possible way.

But if you do, please don’t complain later.

If something really bad happens, it’ll be your fault!


Keep reading to find out how to play with the Beta with caution.

IMG_9364 (1)



Let’s do it.

We can’t wait and really really really want to use the new version right away.

Please read what follow, and proceed with caution!

Back-up your databases.

If you don’t know what databases are, it’s very important you read this first.

Now: databases created in DaVinci Resolve 16 need to be updated to open in DaVinci Resolve 16.

Once databases are updated to version 17, they can’t be opened in version 16 any more.

Scary, right?

To avoid problems, and before installing DaVinci Resolve 17, we create backups of our databases.

That way, if there are problems when updating, we could re-install version 16, and restore databases as needed.

Steps to backup our databases:

  • Select database, and click in Backup, the icon shown in the image below:

ScreenClip [5]

  • Select a location to save the backup, and click Save:

ScreenClip [6]

And that’s it!

Super simple.

This creates a file with the extension .diskdb (Disk Database), that we could use to restore from in the previous version, by clicking on the Restore icon:

ScreenClip [7]

Important: you need to do this will all databases you wish to update, one by one.

Install DaVinci Resolve 17, and upgrade your databases.

Now that we have backups of our databases, we can download and install DaVinci Resolve 17.

It’s important to understand that when installing version 17, version 16 is automatically uninstalled.

Keep that in mind. If you need to go back, you’ll need to download it and install it again.

To simplify this, I keep the installation files of a couple of the latest version, so I can quickly reinstall when needed.

Note: someone published a method to install DaVinci Resolve 17 and keep version 16 in the system. I’m not sure I can recommend this, as it can be even more confusing for some users, but feel free to experiment.

Now: after installing version 17, we just open it.

When doing so, we will see the options to upgrade databases. All we have to do is click on the button “Upgrade Database”:

ScreenClip [8]

After upgrading, the database opens, and we can access it normally.

Activate Live Save and Project Backups.

DaVinci Resolve 17, in Beta, will crash and close unexpectedly.

To avoid loosing work, it’s very important we active the automatic saving options, not active by default.

To do so, we go to the DaVinci Resolve Menu, and click on Preferences.

Then we click on User, and then Project Save and Load:

ScreenClip [9]

As shown in the image above, we active Live Save and Project Backups.

Live Save saves automatically everything we do, the moment we do it, and in the background (similar to what Final Cut Pro X does).

If DaVinci Resolve 17 crashes and closes, we would just open it again, and we would find the project exactly the same way we left it, including the last action.

Project Backups creates additional copies of the project, and we can set how frequently and where we want to save the extra copies.

If we have problems, we can restore a previous version of the project. This is: we could “travel back in time”.

To restore from Project Backups, in the Project Manager, we just right click on the project, and click on Project Backups. This opens a list with all versions saved. We select the one to restore, and click on Load.

If we active these two options, we should, in theory, never loose work in the software misbehaves.

Never update in the middle of a project.

This is a mantra we repeat and repeat in the world of editing and postproduction: we should never update to a new version of any software in the middle of a project.

This is also true if we use Avid Media Composer, Premiere Pro, or Final Cut Pro X.

Check frequently if there are new Beta versions.

As I explained above, newer Beta versions will work better.

If we use version 17, it’s important to check often if there’s a new Beta release, and in general, updating will be recommended.

New Beta releases are publish, again, in the Support site of Blackmagicdesign:



Different users are having different experiences with the Beta version.

Write a comment below if you wish to share your personal story with DaVinci Resolve 17.


One thought on “DaVinci Resolve 17 Public Beta. Should you use it? How to update safely.

  1. So I DIDNT wait…which I thought was fine…now the beta has become too unstable – I know – my fault – is there ANY hack to go back to opening it in a 15? Thanks


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.