
Live Save preserves current changes; it is not the same decision as retaining an earlier checkpoint. If you need to return to a previous edit, inspect the available project or timeline backups and confirm that the required time is represented. Do this before assuming yesterday's cut is recoverable.
Key Takeaways
- Saving current work and keeping earlier versions serve different purposes.
- Check backup settings and available checkpoints before major revisions.
- Load a recovery candidate separately and compare it with the intended reference.
Define the recovery point you need
“Yesterday's edit” can refer to the cut before a scene was removed, the version a client watched, or a later unapproved revision. Use a review filename, timestamp or change note to identify the target.
A current project can be perfectly saved while no longer containing the earlier editorial state you want. Do not keep editing while treating an uncertain recovery point as a confirmed backup.
Inspect the actual backup options
Blackmagic's Resolve 20 training guide places Live Save and backup controls in User Preferences under Project Save and Load. It distinguishes Live Save from incremental Project Backups and describes opening available project backups from the Project Manager.
Check your current settings and the backups that actually exist. An enabled setting today does not prove it was enabled yesterday or that an older checkpoint remains available. This guide follows the Resolve 20 training material; verify the equivalent controls in your installed version.
Before a substantial revision, retain a clearly identified checkpoint through the project's supported workflow. Record what the checkpoint represents, rather than using several files all named “final.”
Inspect a recovery candidate separately
In Project Manager, right-click the project and choose Project Backups. Select a backup whose time and context plausibly match the target, then load that backup. Resolve prompts for a project name and does not overwrite the current version; use a clear name such as Ceremony_recovered_review so the recovered state can be compared separately. Avoid replacing the current working project before you know which state the backup contains.
Compare several editorial landmarks: the beginning, a recently revised scene and the ending. A single familiar frame is not enough to establish that you recovered the correct cut.
For example, a hypothetical client-approved version may have the same opening as today's revision but a different narration order in the middle. The matching opening proves very little; the changed scene is the useful acceptance check.
Make future rollback concrete
Record the recovered checkpoint's identity and the differences that matter. Keep media availability as a separate concern: a restored project state still needs its referenced assets.
Use a clear approved-version handoff for review decisions. For the finished delivery, include an approval scope record that identifies the actual exported movie, so “the saved project” is not confused with the file a client approved.
Source: Blackmagic's Resolve 20 Beginner's Guide, printed pages 402–403.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- What Does Approved Mean for an AI Project: Concept, Story or Final Master?
Sources and scope
- The Beginner's Guide to DaVinci Resolve 20, Project Save and Load: Printed402-403 distinguishes Live Save, timeline backups and Project Backups; recovery access via Project Manager.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.