Many users wonder where their DaVinci Resolve projects actually live and how to manage backups without losing progress. Resolve does not save projects as loose files; instead, every project exists inside a project library (a database) that Resolve manages on your system. By default, Resolve stores this library in your user directory, and the design has implications for backups, portability, and collaboration.
Where Resolve keeps your projects by default
Resolve’s projects are stored inside a project library, which is a database. The default library path is the Resolve Disk Database, typically located within your system user directory. On Mac, Windows, and Linux, the structure differs, but the concept remains the same: a single library contains multiple projects, and the actual media stays separate from the project data. In practice, you won’t find a single .drp file for a project unless you export one; instead, you’ll interact with the database through the Project Manager.
What to export if you need a portable, OS-visible file
When you need a portable version of a project, you export a .drp file from the Project Manager. The .drp contains timelines, edits, grades, and settings, but not your media. This makes it ideal for handoffs or transferring a project to another machine while keeping media in its original location. Exporting a .drp provides a traditional destination path, which is not the default behavior for regular saves inside the Resolve database.
Understanding the database design and its implications
Two key ideas drive Resolve’s design:
- The project database (library) holds the project structure, timelines, renders, and settings; media files reside separately in your storage locations.
- The database can be a single local library or a PostgreSQL-based network library for collaboration; this affects how backups and access work across machines.
In Resolve, there is a distinction between a local library and a shared, networked library. A local library is stored on a disk, while a PostgreSQL-based library is managed by a server for multiple users. When working solo, most users interact with the local Resolve Disk Database. When collaborating across a shop, the DaVinci Resolve Project Server (PostgreSQL) handles the shared libraries, backups, and restores.
Backups: how to protect your work
Project backups are rolling snapshots of the project you’re currently working on. They can be enabled in Preferences > User > Project Save and Load, where you can set the backup intervals and the location for those backups. Library backups, which cover the entire library (all projects within it), require a manual action in the Project Manager. You must show the project libraries sidebar, select your library, and click the backup icon to create a disk-based backup file (.diskdb). Forます local libraries, it’s wise to periodically copy the Resolve Disk Database folder to another drive when Resolve is closed. If you work with a team on a shared library, backups are handled through the Project Server, with its own backup controls and no built-in scheduler. Regular, manual backups are essential to prevent loss of your editing history and projects.
Where to look on disk for the relevant folders
Resolve stores its data in a folder structure under the OS. On Mac, it’s typically under the user’s Library folder; on Windows, under AppData/Roaming; on Linux, under ~/.local/share. These are hidden by default in many setups, so you may need to reveal hidden folders to locate them. The key point is that the actual project data lives in a database folder rather than as discrete project files next to media. The media used in your projects is stored separately and should be organized alongside your other media in your project folders.
Practical guidance for organizing your media and projects
Two practical notes help keep things organized:
- Cache and gallery directories are hidden by default and can occupy significant space. If a drive fills up mid-project, these are good places to check, along with the Working Folders settings per project to point caches to fast scratch storage.
- When you need to move projects or work between machines, consider copying the Resolve Disk Database (or migrating the PostgreSQL library) rather than attempting to relocate individual project files. Remember that media must be relinked if you move it; keeping a consistent folder structure helps relinking succeed.
Table: key concepts and practical actions
| Concept | Description | Practical Action |
|---|---|---|
| Project database | Where projects live as records in a library | Back up the library; use Export Project for portable handoffs |
| Project Library vs. Disk Database | Library: collection of projects; Disk Database: local storage path | Locate via Preferences; back up or copy the library folder |
| Backups | Project backups are per-project snapshots; library backups are entire libraries | Enable per-project backups; run library backups manually |
| Media storage | Media is stored separately from the project database | Organize media in your main project folders; ensure relinking remains possible |
Putting it together: how to manage saves and backups effectively
Resolve saves projects inside a project library, not as loose files. If you want a traditional OS destination for a snapshot of a project, export a .drp from the Project Manager. For full portability and backup, regularly copy the Resolve Disk Database folder (or manage a PostgreSQL-based library with your Project Server) and keep your media in well-organized folders that mirror your editing projects. Reading the manual and related tutorials helps new users grasp the database-based storage model, and practical forum discussions reinforce the importance of disciplined backups and clear folder structures.
