# How to Duplicate a DaVinci Resolve Project Before Experimenting

> **Quick answer:** To duplicate a DaVinci Resolve project before experimenting, open the Project Manager, right-click the project, choose Duplicate Project, and give the copy a clear name. Open the duplicate and confirm it appears as a separate project before making changes. For extra protection, export a .drp file or enable Project Backups; neither replaces a media-inclusive project archive.

*Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.*
*Updated 2026-11-03 · DaVinci Resolve 21.1 (October 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-duplicate-project-before-experimenting*

I used to treat a finished edit as if it were made of glass: touch the wrong setting and the whole thing might crack. A separate experiment copy makes that fear easier to manage, but only if you know what kind of copy you made and what it does not protect.

As of October 2026, this guide follows the DaVinci Resolve 21.1 reference manual. Menu labels can move between versions, so if your screen differs, check the manual for your installed release before using a file-management workaround.

## How do I duplicate a DaVinci Resolve project before experimenting?

To duplicate a project, open the Project Manager, right-click the project, choose **Duplicate Project**, and give the new copy a name that says what you plan to test. Open the duplicate, verify it is the active project, and make your changes there, not in the original.

A duplicate is a separate project entry in your project library. It gives you a working branch: a place to test a different color grade, rebuild a section of the edit, try a new delivery setup, or learn an unfamiliar tool without treating the original as disposable.

Follow this sequence:

1. **Save the project you mean to protect.** If it is open, save it first. If you have several projects with similar names, check the title at the top of the Resolve window before going further.
2. **Open the Project Manager.** Use the Project Manager button in Resolve to leave the open project and return to the screen that lists your projects. Do not delete or rename anything from Finder or File Explorer.
3. **Find the project and open its context menu.** Right-click the project you want to copy. On a Mac trackpad, use the equivalent secondary click if right-click is not enabled.
4. **Choose Duplicate Project.** If your installed version shows a duplicate command, select it and enter a distinct name when prompted. Avoid a name like “Copy” that gives you no clue which version contains the experiment.
5. **Open the new project.** Check the displayed project name before editing. Resolve should show the duplicate as a separate project entry in the Project Manager.
6. **Make one small, easy-to-check change.** This confirms that you are in the branch you intended. Do not begin with a long chain of destructive edits.
7. **Return to the Project Manager and confirm both entries remain.** The original should still be available alongside the experiment copy.

For example, if the original is called `North Shore Interview`, use a name such as `North Shore Interview - warm grade test - 2026-10-24`. The date and the purpose make the copy easier to identify later. This is a naming example, not a requirement imposed by Resolve.

**A named experiment copy is safer than relying on memory to undo a long chain of edits.**

Resolve’s project management is organized around project libraries, rather than treating every project as a file you routinely open from any folder. Blackmagic’s Resolve 21.1 manual describes projects as items managed in the Project Manager and documents separate ways to save, export, and archive them. That distinction matters when you want a reversible experiment: duplicating the project gives you another managed project, while exporting creates a file outside the library. See [Blackmagic Design’s DaVinci Resolve 21.1 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_21.1_Reference_Manual.pdf) for the current project-management procedures.

A good check is boring by design. You should be able to see the original name and the experiment name, open the experiment name, and know which one is active without relying on a mental note like “I think this is the copy.” If the Project Manager does not show two distinct entries, stop and resolve that uncertainty before editing.

This workflow is useful whether you are changing a handful of clip settings or making a large creative change. You do not need to decide in advance whether the experiment will work. You only need to make sure the version you want to preserve is not the one you are changing.

## Why should I duplicate a DaVinci Resolve project before experimenting?

A duplicate gives you a named branch to work in, while the original stays available for reference or recovery. It is especially useful when an experiment affects many parts of a project or when you are not yet sure which version you will keep.

An experiment can be as modest as testing a new title style. It can also change a project-wide setting, rearrange an edit, alter color management, replace media, or change how a timeline is built. These changes do not all carry the same risk. The value of a copy rises when the change is broad, hard to reverse, or likely to affect work you already consider finished.

Think of a duplicate as a decision tool. You can compare two versions side by side, show a collaborator the alternate direction, or discard an experiment without having to reconstruct the previous state from memory. It does not make every change harmless, and it does not replace a proper backup. But it creates a clear point from which to explore.

A few questions help decide whether to branch:

- **Could this affect more than one clip or timeline?** If yes, a project-level copy is easier to reason about than a single undo.
- **Would I need to spend significant time recreating the current state?** If yes, preserve it before changing anything.
- **Am I testing a workflow I have not used before?** A copy gives you room to learn without making the original your practice file.
- **Will someone else review or continue this project?** A named alternate version is clearer than a collection of unexplained edits.
- **Do I need to compare the original and the new result?** Two projects can represent separate directions, although a pair of timelines inside one project may be more convenient for a narrow edit comparison.
- **Is the source media valuable or difficult to replace?** A project copy alone does not bundle that media, so you may need an archive or an independent storage backup as well.

A copy is not automatically a safety net for every part of post-production. Project state, source files, generated media, stills, LUTs, and external assets can have different storage and linking behavior. If the experiment depends on files outside Resolve, confirm that those files remain available. If you are moving the project to another computer or making a long-term copy, read [how to archive a DaVinci Resolve project without losing media](https://tryuncle.com/learn/davinci-resolve/how-to-archive-a-davinci-resolve-project-without-losing-media).

A small, local experiment may not need a full project duplicate. If you only want to compare two edits, a duplicate timeline can keep the alternatives together. If you are testing a change that reaches into project-wide settings, media organization, or multiple timelines, a separate project offers a broader boundary. There is no one copy method that is best for every change.

Colorist Abbas Khaleeli describes how practice helped him learn: “Mostly through experimentation and repetition. I spent countless hours in DaVinci Resolve trying new workflows.” Khaleeli also says he learned from colorists, educators, and Blackmagic Design’s training resources in an interview with [LBBOnline](https://lbbonline.com/news/Developing-Creative-Judgement-in-Colour-Grading-with-Abbas-Khaleeli). A separate copy can make that kind of testing easier to do deliberately, because it gives the experiment a place to live.

**Experimenting is more useful when you can compare the result with a version you trust.**

## Should I duplicate the project or just duplicate the timeline?

Duplicate the project when you want a separate project-level branch; duplicate the timeline when you only need an alternate edit inside the same project. A timeline copy is often the lighter choice for comparing cuts, while a project copy offers clearer separation for broader changes.

These methods answer different questions. “Can I try a new cut without losing this one?” points toward another timeline. “Can I test a different project setup without changing the working version?” points toward another project. Neither approach bundles all your original footage, and neither should be confused with an archive.

| What you want to test | Better starting point | Why it fits | What to check |
|---|---|---|---|
| A different cut of one sequence | Duplicate the timeline | Keeps the alternate edit within the project | Confirm the duplicate timeline is selected before editing |
| A project-wide color or settings experiment | Duplicate the project | Separates the experiment from the main project entry | Confirm the copy’s name in the Project Manager |
| A version for review while work continues | Duplicate the project or timeline, depending on scope | Creates a clearly named alternate | Make the name and intended use clear to reviewers |
| A portable project file to import elsewhere | Export a project as `.drp` | Creates a project file you can store or transfer | A `.drp` is not the same as a media-inclusive archive |
| A copy intended to include media | Export a project archive | Designed for packaging a project with its media | Check archive contents and destination storage |
| Recovery from a past point | Project Backups or Timeline Backups | Uses Resolve’s recovery features when enabled | Check the correct backup list and load it as a new item when offered |

For a timeline-only experiment, name the alternate with a useful suffix, such as `Interview v2 - shorter opening`. Then make sure the timeline selector shows that alternate before trimming or rearranging clips. A duplicated timeline can still contain changes to shared project-level settings, so it is not a wall between every kind of change. Use a separate project if that distinction matters.

When you need both versions to remain easy to inspect, consider whether opening two project entries is actually necessary. A pair of timelines can be quicker to switch between, but they can also make the project more crowded. Two project entries can be easier to identify as distinct versions, but you must keep their names and storage context clear. The right choice is the smallest branch that contains the experiment safely.

The Resolve 21.1 manual also describes Dynamic Project Switching, which lets you keep multiple projects open in memory and switch among them. That feature can help when you need to copy or compare material across projects, but it is not required just to create a duplicate. The manual warns that loading multiple or very large projects can affect performance if the workstation does not have enough RAM. Treat switching as a convenience for a specific workflow, not as a substitute for making a safe copy.

## What is the difference between Duplicate Project, Save Project As, and Export Project?

**Duplicate Project** creates another managed project entry, **Save Project As** saves the current project state under a new name, and **Export Project** writes a project file you can store or import. Choose the method based on whether you need a working branch inside Resolve, a newly named current state, or a portable project file.

Resolve’s menu names can look similar even though the results serve different purposes. When the project is open, **File > Save Project As** is a documented way to save its current state under another name. The Resolve 21 reference manual lists the shortcut as **Command-Shift-S** on macOS. For a portable project file, use the Project Manager’s export option. A `.drp` project file can be imported into Resolve, but exporting it does not mean that the original camera files have been copied into it.

| Method | Where you start | What you get | Good for | Main caution |
|---|---|---|---|---|
| Duplicate Project | Project Manager | A second project entry | Making a working branch before a broad experiment | Name the branch clearly and open the right entry |
| Save Project As | An open project | A copy of the current project state under a new name | Creating a renamed version from the project you have open | Confirm the new name and active project before editing |
| Export Project | Project Manager | A `.drp` project file | Storing or transferring the project file | It is not a media-inclusive archive |
| Export Project Archive | Project Manager | An archive intended to collect a project and its media | Moving or preserving a project with media | Check destination capacity and archive contents |
| Project Backups | Resolve preferences and Project Manager | Periodic project recovery versions, when enabled | Recovering a saved earlier state | They are not a deliberately named experiment branch |

The manual says a `.drp` file can be imported from the Project Manager, including by using the Import command or dragging the file into the Project Manager window. That makes export useful when you want a copy outside the current library, or need to bring a project into another library. For a project intended to travel with its media, use the archive workflow instead. The distinction is covered in more detail in [the guide to archiving a DaVinci Resolve project without losing media](https://tryuncle.com/learn/davinci-resolve/how-to-archive-a-davinci-resolve-project-without-losing-media).

**A project export is not a media archive, and neither is the same thing as a recovery backup.**

If you choose **Save Project As**, check the project name after saving. Resolve’s manual notes that if you use the name of an existing project, Resolve presents an overwrite confirmation. That prompt is a reason to pause, not to click through quickly. A typo or ambiguous name can turn a routine save into an unwanted overwrite.

If the command you expect is missing, do not improvise by copying database folders in Finder or File Explorer. Project libraries have their own organization, and manual folder changes can leave Resolve unaware of a project or library. Use documented Project Manager commands, or consult the manual for your installed Resolve version. When you are unsure whether you have made a separate project or merely renamed the active one, stop and inspect the Project Manager before proceeding.

## How should I name an experiment copy so I do not edit the wrong project?

Use a name that identifies the original project, the experiment, and, when useful, the date or version. A clear name makes the Project Manager safer to use and makes a later comparison easier to understand.

A project name is part of the safety workflow. “Copy,” “Copy 2,” and “New Project” may be technically distinct, but they leave you guessing when you return after a break. Name the reason for the branch, not just the fact that a copy exists.

A practical pattern is:

`[project name] - [change being tested] - [date or version]`

Examples:

- `North Shore Interview - alternate opening - 2026-10-24`
- `Kitchen Promo - warmer grade test - v02`
- `Fundraiser Cut - vertical delivery experiment`
- `Wedding Film - new music structure - review`

These are illustrative names, not Resolve requirements. Pick a pattern your team can read at a glance. If a collaborator will see the project, avoid private shorthand or abbreviations that only make sense to you. If the test is temporary, you can say that in the name, but do not count on remembering to clean it up later.

Before the first edit, perform a three-part check:

1. Read the project name at the top of the Resolve interface.
2. Confirm that the Project Manager lists the original separately from the copy.
3. If the two versions are easy to confuse, close the project and reopen the experiment by selecting its named entry.

This check catches a common human error: making the copy correctly, then returning to the original without noticing. It also helps when you have several variations. If you make a new grade test from a project that already contains another test, say so in the name or notes. Otherwise, you may mistake a branch of a branch for the untouched source version.

You can also write a short note explaining what the copy is for: “Testing a warmer look on interview shots; original remains the approved cut.” In Resolve 21, the reference manual documents Project Notes as a scratch pad associated with a project. A note is useful context, but it does not replace a clear project name or a separate backup.

Keep the original visibly distinct. For example, avoid calling both versions `Final`; use names such as `Main - approved review` and `Experiment - warmer grade`. If you later promote the experiment as the new working version, record that decision instead of deleting the original immediately. The original may be useful for comparison, but an old branch is not automatically the right branch forever.

## Does a duplicate project copy my footage, stills, and LUTs?

No. A project duplicate is not the same as a media-inclusive archive. It may contain project information while still depending on media files stored elsewhere, so check where the footage and other assets live before moving, deleting, or disconnecting them.

This is one of the most important distinctions in the workflow. A project can appear complete in Resolve while its source footage remains on an external drive, a shared storage volume, or another folder on the same computer. A second project entry does not by itself mean Resolve has made another copy of every source file.

The Resolve 21.1 manual describes project backups as complete project files **excluding stills and LUTs**. It separately distinguishes exporting a project from creating a project archive. This means you should not assume a duplicate, an exported `.drp`, or an automatic project backup contains every asset needed to reproduce the work on another machine. For a move or preservation copy, follow the archive procedure and check what is included.

Use this decision test:

- **Are you experimenting on the same computer with the same media still connected?** A project duplicate may be enough for the project-level experiment.
- **Are you moving to another workstation?** Use an archive workflow or another deliberate media-transfer method, then confirm that Resolve can find the media.
- **Are stills or LUTs important to the look?** Check those assets separately. The manual’s description of project backups explicitly excludes them.
- **Are you saving only a `.drp` file?** Treat it as a project file, not proof that footage has been copied.
- **Are the files on a shared drive or removable disk?** Keep that location available and avoid changing its folder structure during the experiment.

A missing-media warning in the copy does not necessarily mean the project duplicate itself failed. It may mean Resolve cannot locate the referenced source file from the current computer or storage configuration. Before relinking, check whether the drive is mounted and whether the folder path changed. Avoid relinking a large set of files to the wrong duplicate or proxy location just to clear a warning.

Keep source media outside your experiment unless changing that media is part of the test. If the new project is intended for someone else, explain which media locations it expects and whether they need to use the archive. A clear handoff prevents the next editor from opening what looks like a full project and discovering that the important clips are offline.

Project archives also need a destination with enough space. Camera originals, optimized media, proxies, and generated media can make a package much larger than the project entry itself. Do not guess at the size: check the storage available at the destination, then inspect the archive options and the result before removing any source files.

## How do Project Backups and Timeline Backups fit into an experiment?

Project Backups and Timeline Backups are recovery tools, not substitutes for a deliberate experiment branch. Enable them for additional protection, but make a named duplicate or timeline copy when you want to test a specific change and compare it with the working version.

In Resolve 21.1, the Project Save and Load preferences include controls for Live Save, Project Backups, and Timeline Backups. Live Save records changes as you work. Project Backups preserve periodic project versions when enabled; Timeline Backups preserve versions of individual timelines. Their purposes overlap with safety, but they do not all answer the same question.

| Protection method | What it protects or records | Useful when | Remember |
|---|---|---|---|
| Live Save | Saves changes to the current project as you work | You want routine saving without repeatedly pressing a key | It does not create a named alternate branch |
| Project Backups | Stores periodic project versions when enabled | You need a recovery point from earlier work | You may need to wait for a backup interval and select the desired version |
| Timeline Backups | Stores versions of a timeline when enabled | You want to recover or compare a prior timeline state | This applies to timelines, not every part of the project |
| Duplicate Project | Creates a separately named project branch | You want to make an intentional project-level experiment now | It does not package all media |
| Duplicate Timeline | Creates an alternate edit within the project | You want to compare two versions of one sequence | Project-wide settings can still be shared |

The manual documents Project Backups under **DaVinci Resolve > Preferences > User > Project Save and Load**. Enable the checkbox, choose how many backups to maintain and where they go, then save the preferences. Its default schedule includes backups every 10 minutes during the recent working period, with hourly and daily retention settings. Resolve rotates backups on a first-in, first-out basis. These are documented defaults, so check your installed version and settings rather than assuming your system uses the same schedule.

The timing has a practical consequence: the backup you want may not exist yet. If you make a risky change and immediately regret it, do not assume a scheduled backup captured the state from a few minutes ago. A manual project duplicate is more deliberate. Project Backups add recovery depth over time; they do not replace the copy you create before the experiment.

The manual also says that opening a project backup loads it as a new project rather than overwriting the original project. That is useful, but recovery still takes care. Confirm the date and project name in the backup list. Load the version you mean to inspect, compare its contents, and avoid deleting the current project until you understand which state the backup represents.

Timeline Backups can be useful when you want to restore or compare an earlier edit. Resolve’s manual describes restoring a timeline backup as bringing the selected version into the Media Pool as another timeline. It also documents a timeline backup comparison view. Those features can help you inspect a change without turning every small adjustment into a separate project entry.

For routine protection, combine methods in proportion to the risk. Live Save handles ordinary work. Project Backups add earlier project states. A named duplicate gives you an explicit branch for a planned experiment. An archive helps when the work needs to travel with its media. None of these alone is a complete storage strategy for irreplaceable source footage.

**Automatic backups help you recover; a named copy helps you choose what to change.**

## What should I test in a duplicate, and how do I compare the result?

Make the copy for one specific experiment, test a small representative section first, and compare the result with the original before deciding whether to keep the change. A copy is most useful when you can explain what you changed and what success would look or sound like.

Give the experiment a question. “Try things out” is too broad to evaluate later. “Does the warmer grade preserve the skin tone while making the background feel less cool?” gives you a way to compare. So does “Does the shorter opening reach the interview sooner without removing the context a viewer needs?”

A controlled test helps you learn what caused the result. If you change the grade, title, soundtrack, and timeline structure at the same time, you may like the outcome without understanding which change helped. When you can, change one group of related settings at a time and note what you changed.

A useful test sequence is:

1. **Write the goal in one sentence.** Be specific enough that you can judge the outcome.
2. **Choose a representative section.** Pick a sequence that includes the conditions your change is meant to handle.
3. **Make the change in the duplicate.** Confirm the active project name before you begin.
4. **Check an edge case.** If the effect should work on several shots, inspect at least one shot where the lighting, motion, framing, or audio differs.
5. **Compare against the original.** Use the same part of the footage and the same playback conditions where possible.
6. **Record the decision.** Keep, revise, or discard the experiment. If you keep it, identify which branch becomes the new working version.

For a grade experiment, compare representative shots rather than judging one attractive frame. Check whether the look remains coherent across changes in lighting and skin tone. For an edit experiment, compare pacing and story information, not just the total duration. For an effect or transition, test a short section with the kind of footage that will actually use it. These are evaluation suggestions, not claims that a particular setting will produce a guaranteed result.

If the copy is for a collaborator, make the comparison easy to follow. State which version is the original, which contains the experiment, and what you want them to judge. Avoid sending two exports called `final.mp4` and `final2.mp4`. Names such as `roughcut-original-review` and `roughcut-shorter-opening-test` communicate intent more clearly.

A useful test can still fail. That is not a reason to undo the safety step. The point is to make the failure cheap to inspect and easy to abandon. You can keep a failed experiment temporarily if it teaches you something, but mark it clearly so it does not get mistaken for the approved version.

If you decide the experiment is better, do not rush to overwrite or delete the original. First confirm the new version opens correctly, the media is online, expected timelines are present, and the result is the one you meant to promote. Then decide how the project should be named for future work. A careful handoff matters more than preserving a long list of unexplained copies.

## What if Duplicate Project is missing, the copy looks identical, or media is offline?

If you cannot find the duplicate command, your copy has an unclear name, or media appears offline, stop before making more changes and identify which project and library are active. Use the Project Manager and documented Save As, export, or archive options instead of manually moving project-library folders.

Some Resolve screens or versions may present controls differently. The DaVinci Resolve 21.1 manual is the best reference for that version, and the Blackmagic Design support page lists current manuals and software updates. If the Project Manager does not match this guide, check the reference manual for the release you have installed rather than relying on an old tutorial’s screenshots or menu labels.

Work through these checks in order:

| What you see | What to check | Safer next step |
|---|---|---|
| No Duplicate Project command | Confirm you are in the Project Manager and selected the intended project | Use the documented Save Project As route from the open project, or consult the manual for your installed version |
| Two entries with nearly identical names | Check the active project name and rename the branch if needed | Close the project and reopen the clearly named experiment |
| The copy appears to have the same media | Remember that the project can reference the same source files | Do not delete or move source media until you have made and checked an archive |
| Media is offline in the copy | Check whether the drive is connected and whether its folder path changed | Restore the correct media connection before relinking |
| The duplicate seems to have replaced the original | Stop editing and inspect the Project Manager entries and project names | Do not save over either version until you understand which one is open |
| You cannot see a recent Project Backup | Check whether Project Backups were enabled and whether the schedule has run | Create a deliberate copy now; do not assume a backup exists |
| The project is in a shared library | Check the library and collaboration context before branching or changing access | Coordinate with collaborators and use the project’s sharing rules |

A duplicated project can look almost identical to its original because it may point to the same media and contain the same timelines and settings at the moment it was copied. That is expected for a working copy. The useful test is not whether its thumbnails look different; it is whether Resolve lists it separately and shows the name you assigned.

Shared project libraries deserve extra care. A local experiment in a shared environment can confuse collaborators if they mistake the branch for the approved project. A clearly named copy helps, but also follow your team’s rules for who can edit, where review versions belong, and how an approved version is promoted. Blackmagic Cloud documentation describes project-library management and backup controls, but your own collaboration workflow still determines how people should use those projects.

Do not rename, move, or delete hidden database folders to force a duplicate. Resolve’s Project Manager and library controls are the intended places to manage projects. If a project or library is missing, consult the official manual and Blackmagic support resources before changing files behind the application.

If the same button remains hard to find, [TryUncle](https://tryuncle.com/) is the on-screen assistant for DaVinci Resolve on Mac and Windows; ask in plain words and Uncle points at the exact control on your screen. The assistant can guide you through what is visible while you work, but you still perform the actions and should verify that the correct project is open.

## Is a duplicate project enough protection for client or long-term work?

A duplicate is a useful experiment branch, but it is not a complete backup plan for client work or long-term storage. Keep separate protection for the project, the source media, and any assets the project depends on, then verify that the intended recovery path actually works.

For important work, think in layers. A separate project copy protects a working decision. Project Backups can preserve earlier Resolve states when enabled. A project archive can package the project with media for transfer or retrieval. A separate storage backup can protect against problems that affect the computer or drive holding the project and original footage.

These layers solve different problems:

- **The project copy** helps you work on an alternate version.
- **Resolve’s Project Backups** help recover an earlier project state if the feature is enabled and has created a useful backup.
- **Timeline Backups** help recover or compare a timeline version.
- **An archive** helps collect the project and media for a handoff or later retrieval.
- **A separate storage copy** helps if the working storage fails or becomes unavailable.

Do not call a copy a backup simply because it has a new name. If both project entries rely on the same external drive and that drive fails, the project branches do not replace the missing footage. If a backup folder lives on the same storage that fails, it may not provide independent protection. The exact storage plan depends on how the work is stored and who needs access to it.

For a client handoff, make the state legible. Identify the project version being delivered, the archive location if you created one, and any external media or LUT dependencies that are not included. If another editor will open the work, ask them to verify that the project loads and the media is online before you consider the handoff complete.

If this is a recurring workflow, create a repeatable checklist rather than relying on memory. You might record the approved project name, the experiment branch, the archive date, and the destination where the archive is stored. That is a workflow suggestion, not a claim that Resolve enforces a particular naming scheme.

A Resolve project can be technically intact and still be difficult to hand off if no one knows which version is current. Keep one clearly designated working version, name experiments by purpose, and avoid treating every temporary test as a new “final.” When you finish the experiment, either discard it, retain it with a clear label, or promote it deliberately.

**A duplicate protects a decision; a verified archive protects a handoff.**

## What is the safest next step before I experiment?

Save the current project, make a clearly named duplicate, open that copy, and verify the active project name before changing anything. If the work needs to move or survive a storage failure, add an archive or independent backup instead of assuming the duplicate includes the media.

The first experiment does not need to be large. Pick one change with a clear purpose, make it in the copy, and compare the result with the version you meant to preserve. If the experiment works, promote it deliberately. If it does not, return to the original branch without rebuilding the edit from memory.

If you regularly start projects from the same base, a reusable template can reduce setup work, but it serves a different purpose from a one-time experiment copy. See [how to create a project template in DaVinci Resolve](https://tryuncle.com/learn/davinci-resolve/how-to-create-a-project-template-in-davinci-resolve). And if you want to improve your wider recovery habits, [how to prevent DaVinci Resolve project corruption](https://tryuncle.com/learn/davinci-resolve/how-to-prevent-davinci-resolve-project-corruption) covers protection beyond a single duplicate.



## FAQ

### How do I duplicate a DaVinci Resolve project before experimenting?

Open the Project Manager, right-click the project, choose Duplicate Project, name the copy clearly, and open that copy before changing anything. Confirm the original and duplicate appear as separate projects.

### Does duplicating a DaVinci Resolve project copy the video files too?

A project duplicate or exported .drp file is not the same as a media-inclusive archive. The project can continue to refer to source media at its existing file locations. Use Export Project Archive when you need to collect the project and media together.

### What is the difference between a duplicate project and a duplicate timeline?

A project duplicate creates another project-level working copy. A duplicate timeline creates an alternate edit inside the same project. Choose the project copy when you want wider separation; choose a timeline copy when you only need to test a different edit.

### Are DaVinci Resolve Project Backups the same as a duplicate?

No. Project Backups create periodic recovery copies when enabled. A manually named duplicate gives you an intentional branch to experiment in now. Use both for important work, and remember that backups do not replace an archive or a separate storage backup.

## Sources

- [DaVinci Resolve 21.1 Reference Manual, Managing Projects and Project Libraries](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_21.1_Reference_Manual.pdf)
- [DaVinci Resolve 21.1 Manual, Blackmagic Design Support Center](https://www.blackmagicdesign.com/support)
- [DaVinci Resolve 21.1 Release Notes](https://www.blackmagicdesign.com/support/)
- [Managing Project Libraries, Blackmagic Cloud Guide](https://help.cloud.blackmagicdesign.com/project-server/managing-project-libraries/)
- [Developing Creative Judgement in Colour Grading with Abbas Khaleeli](https://lbbonline.com/news/Developing-Creative-Judgement-in-Colour-Grading-with-Abbas-Khaleeli)