I’d resist rebuilding the graph until I knew what had actually gone missing. A blank-looking Fusion page can mean the graph is off-screen, the wrong clip is selected, or Resolve opened an older project state. As of October 2026, Blackmagic Design lists DaVinci Resolve 21.1 documentation, so check the manual for your installed version if a control or menu label differs.

Why do DaVinci Resolve Fusion nodes disappear after reopening?

When nodes seem to disappear after reopening DaVinci Resolve, first verify that you’re looking at the same project, timeline, clip, and Fusion composition you edited. If those match, check whether the graph is merely outside the visible node-editor area before assuming the project lost data.

A Fusion node graph is the connected set of image-processing tools in a composition. Blackmagic describes Fusion as a node-based interface where you connect image-processing tools to create effects. That distinction matters: an empty-looking editor is not, by itself, proof that the graph was erased. (Source: Blackmagic Design Fusion.)

Start with what you can verify, not with a repair. A project can contain multiple timelines, and each timeline can contain many clips or compositions. The Fusion page shows the composition for the selected item. If Resolve reopened a different project, timeline, or clip, Fusion can show a different node tree even though the original tree remains elsewhere.

Use this quick triage:

Those are diagnostic clues, not guaranteed diagnoses. The point is to avoid changing the project before identifying which state you’re viewing.

Write down the project name, timeline name, clip name, and any composition name you remember. If you can still see the clip on the Edit page, note its position and approximate duration. Then return to Fusion and inspect whether the node editor contains any nodes at all. A familiar Media In and Media Out pair, for example, doesn’t establish that you’re in the exact composition you edited. It tells you what the current editor is displaying.

There’s another distinction worth keeping clear. A node graph can be intact while the output appears different because a connection changed, a node is bypassed, or the viewer is showing another node. Conversely, a viewer can still show an image from a different point in the graph than the final output. Check the graph and the output separately.

The project can also be correct while your mental picture of the edit is not precise enough to identify the item. Perhaps you worked on a Fusion Composition from the Media Pool, then later selected a clip on the timeline. Perhaps two shots use similar names. Those are ordinary navigation problems, not evidence of project damage.

A blank Fusion node editor does not prove that your composition has been deleted.

How do I check that I reopened the same project and clip?

To check that Resolve reopened the same work, confirm the project in Project Manager, open the intended timeline, select the edited clip or composition, and then inspect its Fusion page. Matching all four is a stronger check than relying on the project title alone.

Use this sequence:

1. Check the project name in Project Manager. If you manage multiple project libraries or similarly named projects, confirm the project you meant to open. A familiar title may belong to a duplicate, an older backup, or a copy created during a previous recovery.
2. Check the timeline name. Open the timeline where you created the effect. A project can hold alternate cuts, work timelines, and backup timelines. If the expected clip isn’t in the open timeline, you may have the wrong timeline active.
3. Find the actual clip. Select the timeline item you remember editing. If you used a Fusion Composition from the Media Pool, verify that you opened that composition rather than a different timeline clip.
4. Open Fusion from that selection. Inspect the graph for recognizable tools, labels, or connections. If you can’t identify the item by name, compare its position and neighboring clips with what you remember.
5. Check the viewer and timeline. Confirm whether the expected composite is visible at the relevant playhead position. The graph and the timeline result answer different questions, so inspect both.

If the clip or composition isn’t in the current timeline, don’t start rebuilding nodes in a substitute clip. That risks creating a new effect in the wrong place. Go back to the timeline and identify the object you originally worked on before making edits.

A familiar project name is useful, but it isn’t conclusive. The strongest check combines the project, timeline, selected item, and expected output. Keep a note of those names when a project has many versions. That makes the next reopening less ambiguous.

If the timeline looks right but your original clip seems absent, inspect whether it’s inside a compound clip or another nested timeline structure. Don’t decompose, replace, or delete the container just to search for the graph. First locate the exact item and see what Resolve displays when it’s selected.

Also consider whether you have more than one copy of the project in different libraries. That can happen after moving a project, importing a project export, or making a recovery copy. Use distinct names for separate versions, such as a current working copy and a recovery copy, rather than saving both under nearly identical labels.

A simple inventory can help when the project is complicated:

These notes don’t need to be formal. Even a short record like “project X, timeline Y, shot after the outdoor wide” is better than relying on the project name alone.

Once the same project, timeline, and item are confirmed, move on to the node-editor view. If the expected graph is still missing, you’ve ruled out the easiest-to-miss navigation mistake without changing project data.

How do I tell whether Fusion nodes are off-screen rather than missing?

If the correct clip is selected but the Fusion editor looks empty, first check the node graph’s visible area and layout. A graph that’s panned away or spread outside the current view can look missing even when its nodes remain in the composition.

Blackmagic documents node-view bookmarks as a way to save the position and scale of a view in the Node Editor. That makes bookmarks useful for moving between parts of a large graph, but they are not backups of the graph itself. The Fusion manual also describes a Node Navigator for moving around the node tree. (Source: Fusion 20.3 Reference Manual.)

Try these non-destructive checks:

1. Look across the whole node-editor region. If the editor is narrow, partially covered, or divided by a panel splitter, the graph may sit outside the area you can see.
2. Fit or reframe the graph using the editor’s available view controls. The precise control and label can vary by Resolve version and workspace layout. Use the current Fusion page’s visible controls rather than guessing a shortcut.
3. Pan around the node editor. Move through the canvas in more than one direction. A graph can sit well away from the area where the editor first opens.
4. Check for a bookmark or alternate view. If you used bookmarks, visit the relevant view and compare what appears. A bookmark changes where you look, not which project state is loaded.
5. Inspect the editor layout. If a vertical layout or changed panel arrangement is active, look for the node editor in the alternate area. Restore a familiar workspace arrangement only if you can do so without changing the project itself.
6. Check whether the graph is spread out. A long chain, branching composite, or 3D setup may occupy more canvas than you expect. Reframing the view can help distinguish a distant graph from an empty one.
7. Inspect the Navigator if available. A miniature overview of the graph can make a distant cluster easier to locate than panning randomly.

If the graph reappears after panning or fitting it into view, save the project and reopen it once more to confirm the editor can find it again. That second check is helpful, but don’t treat it as proof of a software fault if the view changes again. Record what you did and whether the nodes remained in the composition.

Don’t confuse a graph outside the visible area with a graph that has no meaningful connections. A node might be visible but disconnected from the output. Another node might be present but bypassed. The first issue is navigation; the second is composition logic. Keep those diagnoses separate.

If the editor remains blank, confirm the clip selection again. Then compare the current graph against a known-good project or composition backup, if one exists. Avoid deleting preferences, cache folders, or project-library files as an early step. Those actions are difficult to reverse and don’t establish whether the graph was saved.

A practical check is to select a different clip, then reselect the intended clip and return to Fusion. If the graph appears, the original problem may have been selection or view state. If it remains absent, continue to save and recovery checks rather than treating a layout fix as certain.

One exception: a large node graph may be split into sections connected by long wires, with nodes positioned far from the part of the canvas you usually inspect. In that case, a single fit-to-view operation can make everything tiny. Use the overview to find the graph, then zoom in on the relevant group. A view that is too wide can be as unhelpful as one that is too close.

Fusion bookmarks help you navigate a node tree; they do not restore a deleted or unsaved node tree.

Did Resolve save the Fusion composition before I closed the project?

To find out whether your Fusion work was saved, compare the current project with a backup or a separate copy, and confirm that the expected nodes are present in the composition. A project reopening successfully does not prove that every recent graph change was saved.

Resolve has separate save and backup concepts. Live Save concerns saving changes during work, while project and timeline backups provide earlier states when those options are configured and available. The DaVinci Resolve 21.1 Reference Manual is the current version-specific reference as of this article’s update date. The DaVinci Resolve 20 Editors Guide describes timeline backups and project backups, including loading a backup under a project name instead of overwriting the current version. Check the manual for your installed release because control names and locations can differ.

First protect what you have now:

1. Keep the current project open if it contains recent work you may need.
2. Make a separate project copy or export through Resolve’s project-management controls.
3. Give the copy a clear name that distinguishes it from the current project and any recovery version.
4. Reopen the copy, not the only current project, when you want to test a recovery candidate.
5. Don’t overwrite the current project until you have checked the candidate’s graph and timeline.

If the project has a recent backup, open that candidate as a separate recovery project when Resolve offers that option. Compare the same timeline and clip in both versions. Does the candidate contain the expected nodes? Is the timeline otherwise current enough to use? Does the composition produce the intended image? Record what differs before copying work or adopting the backup.

A backup that opens is not automatically the right backup. The newest available state may already lack the graph, while an older one may predate other work you want to keep. Choose by inspection, not by timestamp alone.

What can each save or backup option do?

The exact behavior and available options depend on your Resolve version and project setup. Check the installed version’s manual before following a remembered menu path. Don’t assume a control’s default or location from an older release applies unchanged to Resolve 21.1.

If you made changes after opening a recovery copy, save that copy under a new, identifiable name. This preserves the original and makes it possible to compare states without guessing which project contains the better graph.

A backup is useful only after you verify its graph and timeline.

How can I recover missing Fusion nodes without overwriting the project?

Recover missing nodes by first creating a protected copy, then inspecting candidate project or timeline backups in Resolve, and finally confirming that a candidate contains the intended composition. Keep the current project untouched until the candidate has passed that check.

A reliable recovery process separates discovery from replacement. You’re not trying to guess which file is correct. You’re trying to locate the last intact state, verify it, and preserve both the current project and the useful recovery point.

1. Preserve the current state

Create a separate project copy or export before loading a backup. Use a distinct name, such as Project_current_before_Fusion_recovery, and store the copy somewhere you can find. If you have a shared or cloud library, confirm the copy is in the right library before proceeding.

Blackmagic Design DaVinci Support staff member Dwaine Maggart recommended project exports for important long-term projects, writing: “In fact, for important long term projects, I'd recommend you do this at the end of each workday on the project.” The advice concerns project exports and protecting the project, not a guarantee that a particular export contains a missing graph. (Source: Blackmagic Design Forum: Restore a Project Library.)

A project export is useful because it gives you a separate project copy to import and inspect. It isn’t a reason to delete the project-library version. Keep both until you know which one contains the work you need.

Before making more changes, write down the project and library you’re working in. If the current project is shared, ask collaborators whether anyone has edited it since you last opened it. A recovery process that ignores recent work from another person can solve one problem while creating another.

2. Look for timeline backups

If the issue appears limited to one timeline, inspect timeline backups first. The Resolve 20 Editors Guide explains timeline backup and recovery as a way to return to an earlier timeline state. The current version’s manual is the reference for exact controls and behavior.

A timeline backup is a sensible first place to look when the timeline itself has changed. But a missing Fusion graph may be tied to a composition or clip state rather than a timeline edit. Open the candidate, select the relevant item, and inspect Fusion before deciding it solved the problem.

Use a comparison rather than an immediate restore:

• Open the timeline backup as a separate or clearly identified candidate where possible.
• Confirm the same timeline name and the same clip or composition.
• Check for the expected nodes and the connections between them.
• Compare the viewer output at the same playhead position.
• Note which later edits are missing from the backup.

If you find the graph in a timeline backup, keep the current timeline available. The older timeline may contain the needed composition but lack newer edits, so decide whether to continue from it, copy a specific change, or rebuild only the missing portion after checking what is safe.

3. Inspect project backups

If timeline backups don’t contain the expected composition, check the project’s available backups in Project Manager. The Resolve 20 guide describes loading a backup project under a separate project name, which helps preserve the existing version while you inspect an earlier state.

Open a candidate under a recovery name if prompted. Then navigate to the same timeline and clip. Compare:

• The project’s timeline list.
• The relevant timeline and clip.
• The Fusion node graph and its connections.
• The viewer output at the same playhead position.
• Other edits you made after the backup’s date.
• Whether required media is online or whether the project points to media that is unavailable on this system.

If the candidate has the nodes but lacks other recent work, don’t immediately replace the current project. Keep both versions. You may be able to copy or recreate only the needed composition or timeline section, but validate the result carefully. If the candidate’s structure differs substantially, getting help from Blackmagic support or a Resolve specialist may be safer than editing project data outside Resolve.

One useful comparison method is to record the graph’s visible node names and broad structure, then compare the candidate with the current project. Don’t assume two graphs are equivalent because they both contain nodes named Transform or Merge. The connections, settings, masks, animation, and media inputs all affect the result.

4. Check cloud library recovery separately

If you’re using a Blackmagic Cloud project library, its library backup and a project-level backup are different recovery options. Blackmagic’s Cloud guide says restoring a library backup creates a new project library rather than overwriting the current one. That provides a safer place to inspect the restored state, but it doesn’t automatically restore one particular Fusion composition. (Source: Blackmagic Cloud Guide: Managing Project Libraries.)

Before restoring, identify the library and backup you intend to inspect. Name the restored library clearly, then open the project and find the same timeline and clip. Keep the existing library available until you’ve confirmed what the restored library contains.

Don’t confuse the project library with the media storage location. A restored library can contain a project state while the footage it references remains somewhere else. If the project opens with offline media, that is a separate relinking problem. It doesn’t by itself prove that the Fusion node tree is missing.

If you collaborate, tell the team which library is the original and which one is the restored copy. Ask people not to make edits in the recovery library until you decide how to use it. Otherwise, two similar libraries can create a new version-confusion problem.

5. Use the smallest safe recovery

Prefer the narrowest recovery that restores the missing work:

• If a timeline backup contains the graph, inspect the relevant timeline state while keeping the current project.
• If a project backup contains the intended composition, continue in a clearly named recovery project or transfer the necessary work after checking compatibility.
• If only a separate Fusion composition export contains the node tree, import it into a safe copy of the project and inspect the result before using it in the working project.
• If no candidate contains the graph, stop before altering project-library files. Look for another exported project, cloud backup, archive, or manually saved composition.

Don’t move or edit Resolve’s internal project-library files with a text editor or file manager as a first-line recovery method. Resolve’s own project and backup controls provide a clearer way to compare states. A direct file edit can make it harder to know what changed and can damage a project you still need.

After a recovery candidate looks right, save it under a new name, close it, and reopen it. Verify the same graph and timeline result again. Only then decide whether to use it as the working version.

What should I do if the backup contains the graph but not the latest edit?

Don’t choose between “restore everything” and “give up” before comparing the two project states. The current project may contain useful later work while the backup contains the missing Fusion composition. Keeping both copies lets you decide whether a narrow transfer is possible.

Start with a simple comparison table:

If you transfer nodes manually, work in a copy. Fusion composition import can replace the current composition in the Node Editor, according to the Fusion manual. That makes it especially important to select a safe copy and confirm what the import will replace before proceeding. If you want to combine node trees rather than replace one, the manual describes a copy-and-paste workflow for selected nodes, followed by connecting the pasted tree into the existing composition. Use the instructions for your installed version and inspect the result.

A transfer may not be clean if the composition references media, tools, or settings that aren’t present in the current project. Keep the source and destination project open as separate copies where your workflow allows, and verify the graph after transfer. Check that all inputs resolve, the output is connected, and the timeline result matches the intended shot.

If you’re uncertain about replacing or merging a graph, don’t experiment in the only copy. Save the recovery project and ask for help with a small, sanitized example if possible. The goal is not to prove you can recover nodes by trial and error. It’s to preserve the best available state.

Should I export a Fusion composition or a Resolve project?

Export a Resolve project when you need to preserve the wider project, and export a Fusion composition when you need an additional copy of a specific node tree. They serve different purposes, so neither is a complete substitute for the other.

Blackmagic’s Fusion manual explains that compositions made in Resolve’s Fusion page are saved as part of the Resolve project, and that you can also export a composition file from the Fusion page. The exported composition contains the node tree created in Fusion, not clips that weren’t added to the Node Editor. The manual also warns that ResolveFX added to a composition won’t translate to Fusion Studio, and describes how Media In and Media Out nodes are converted during interchange. (Source: Fusion 20.3 Reference Manual.)

For a disappearing-node problem, consider both copies after you’ve recovered the graph:

1. Export the project to preserve the broader Resolve project state. Use the Project Manager’s project export option and save it somewhere identifiable.
2. Export the Fusion composition if you want a separate interchange copy of that node tree. From the intended composition in Fusion, use the export command and save the resulting composition file.
3. Name both clearly. Include the project or composition name and date in the filename. Avoid names like final2 that don’t tell you what the file contains.
4. Reopen or re-import a copy to verify it. A file existing on disk is not proof that it contains the graph you wanted.
5. Keep the original project. Treat exported copies as additional recovery points, not permission to delete or overwrite the source.

There’s an important import caution. The Fusion manual says that importing a composition into a Resolve Fusion page replaces the existing composition in the Node Editor. That is not the same as adding a few nodes to an existing graph. If you want to keep the existing comp, work in a duplicate and follow the manual’s supported method for copying selected nodes and connecting the pasted tree. Confirm the destination composition before importing.

When moving a composition between Resolve and Fusion Studio, compatibility details matter. Some nodes and effects are converted or may not translate. Treat a composition file as an interchange copy whose contents should be checked after import, not as a perfect duplicate of the complete project.

These exports also don’t replace media management. A project file and a composition file may reference media that lives elsewhere. If you’re preparing a move to another computer, follow Resolve’s project archive and media guidance rather than assuming either export contains every source file.

A practical routine is to preserve both forms after a significant Fusion milestone: a project export for the whole edit and a composition export for a critical node tree. Keep them somewhere separate from the only working copy. That gives you two ways to inspect or rebuild the effect if the current project state becomes confusing.

What if my Fusion graph is there but the effect looks missing?

If the graph is visible but the effect seems gone, inspect the node connections, node state, and viewer before restoring a backup. The graph can contain the expected tools while the output path no longer passes through them.

Check these items in order:

1. Follow the image path. Find the source node and trace the connections toward the output. If a node is disconnected from that path, it may not affect the final image.
2. Select a known node and inspect its controls. Confirm the selected node is the one you intended to adjust. Resolve’s Inspector shows controls for the current selection, so a different node can display different parameters. If the controls themselves are missing, see how to troubleshoot Fusion node controls that aren’t showing.
3. Check the viewer assignment. Fusion can display an individual node for inspection. Make sure you’re judging the final output and not an intermediate node.
4. Check whether a node is disabled or bypassed. A visible node may be present but not contributing to the result.
5. Move the playhead to a frame where the effect should be visible. A tracker, animation, or timed change may produce a result only at certain frames.
6. Check media and inputs. If a source is offline or an input changed, the graph may look different even though its node structure remains.
7. Compare the expected and current output at the same frame. Otherwise, a change in shot content or animation can make a valid graph appear incorrect.

These are graph-reading checks, not proof that Resolve lost or restored data. If the effect is correct on one frame but missing on another, inspect animation and keyframes. If the entire output is different, compare the final output node and the connections feeding it.

When nodes are present but the graph is complex, don’t disconnect several wires at once. Change one thing, observe the viewer, and undo if the result moves in the wrong direction. If you don’t know what a node does, write down its name before changing it. That small record can help you compare the recovered graph with a tutorial, manual, or support response.

A common trap is to judge the graph from the viewer alone. The viewer may be showing an intermediate node, or you may have moved the playhead to a frame where the effect is not obvious. Another trap is to judge the nodes alone: the graph can look familiar while a connection or input has changed. You need both pieces of evidence.

You can compare the result with a backup copy. Open the same clip at the same playhead position in the candidate project and note the nodes and output. If the backup has the same graph but a different image, the issue may be a connection, parameter, frame, or media state rather than a missing node tree.

If you’re unsure which node controls the visible result, pause before editing the graph. A clear diagnosis is safer than a series of guesses, especially in a composition with trackers, masks, or 3D elements.

A visible node can still be disconnected, bypassed, or outside the output path.

Why do nodes disappear only after I close and reopen Resolve?

If a graph appears during one session but not after reopening, compare the saved project state with the state you saw before closing. The difference may be an unsaved change, a different project copy, or a different clip selection; the reopen symptom alone doesn’t identify which one.

Use a small, reversible test in a copy of the project:

1. Duplicate or export the project so the original stays untouched.
2. In the copy, open the intended timeline and select the intended Fusion item.
3. Make a harmless, identifiable change, such as adding a temporary node label if that control is available.
4. Save the project using Resolve’s normal save method.
5. Close the copied project, reopen it, and select the same item.
6. Confirm whether the label and graph remain.

The point of this test is not to assume a particular save mechanism. It checks whether a known change survives the same close-and-reopen path. If the test change persists in the copy, the original incident may involve the earlier project, selection, or saved state. If it doesn’t persist, note the Resolve version, operating system, project-library type, and exact steps before changing preferences or installing another build.

A test in a copy won’t tell you why an earlier change vanished, and it won’t recover that change by itself. It does help separate a repeatable save problem from a one-time navigation mistake. Keep that distinction in mind when deciding whether to investigate project settings or search backups.

What should I record during the test?

Make the test easy to repeat. Note:

Avoid changing several variables at once. If you update Resolve, move the project, change save preferences, and switch libraries before testing, you won’t know which change affected the result.

Check whether you switched applications or versions between sessions. Resolve 21.1 has its own manual and release information, and Blackmagic’s Support Center lists version-specific resources. If you work across systems, verify that each installation is opening the same project library and compatible project copy. Don’t assume a project in the recent list is the same copy stored on another drive or cloud library.

If the project is shared, check with collaborators before restoring or replacing a timeline. A backup or recovery operation might affect the version other people expect to use. Blackmagic Cloud offers separate library-management and backup operations, so confirm whether you’re dealing with a cloud library or a local project before following recovery steps. (Source: Blackmagic Cloud Guide: Managing Project Libraries.)

If a clean test repeatedly loses a harmless change, capture the exact steps and share them with Blackmagic Design support or the community forum. Avoid sending a client project publicly unless you have permission and have removed sensitive media or information.

Could a different project library or cloud backup explain the missing graph?

Yes. Resolve can show projects from different libraries, and a cloud library can have its own backups. If you switch libraries or restore a library backup, you may be looking at a valid but different project state.

Start by identifying the library in Project Manager. Write down whether it’s local, networked, or a Blackmagic Cloud project library. If there are two similarly named libraries, don’t assume the one currently selected is the one you edited most recently. Check the project list and the date or state of the project you intended to open.

For a cloud library, Blackmagic’s guide documents manual and automatic library backups and says a restored library is created as a new library rather than overwriting the current one. That’s useful for safe inspection. It also means the restored library may appear beside the original, so give it a clear recovery name and avoid editing in both without a plan. (Source: Blackmagic Cloud Guide: Managing Project Libraries.)

If a library is disabled, inaccessible, or missing from the list, don’t conclude that the project itself was deleted. The guide explains that disabling a library removes its projects from the Project Manager window until it is enabled again. Confirm the library’s status and account profile before attempting a recovery.

A cloud library restore and a project export solve different problems. A library restore brings back a library-level state into a new library. A project export gives you a project copy that can be imported into a Resolve project library. Neither automatically proves that the Fusion nodes in a particular composition are present. Open the right project, timeline, and item, then inspect the graph.

If you’re not sure which library is the source of truth, pause and ask the project owner or collaborator. Restoring from a backup while another editor is working can create competing versions. Preserve the original library and any exports while you identify the correct state.

When should I stop troubleshooting and contact support?

Contact Blackmagic Design support or the community forum when the correct project, timeline, and clip are confirmed, the graph remains missing after view checks, and no backup contains the expected composition. Include enough detail for someone to assess the situation, but don’t publish confidential project material.

A useful report states:

• Your Resolve version and build, taken from the application’s About screen.
• Your operating system and whether the project is local or in a shared or cloud library.
• The project, timeline, and clip or composition names, with sensitive names replaced if needed.
• Whether the node editor was blank, showed a partial graph, or showed the wrong composition.
• Whether the issue happens only after reopening or also in a new session.
• Which project or timeline backups you checked, without attaching private media by default.
• Whether a project export or composition export reproduces the issue on another system, if you can test safely.
• What changed shortly before the problem, such as moving the project, switching libraries, or changing Resolve versions.

Keep the report factual. “The nodes vanished” is a useful symptom, but the project name, selection path, and recovery checks help distinguish a missing graph from a different timeline or saved project. If you can provide a small, sanitized test project, ask before sharing it and remove anything you don’t have permission to disclose.

Blackmagic lists its community forum and software documentation through the Support Center. Use the official forum for a public troubleshooting discussion; use the available direct support route appropriate to your edition and situation.

Don’t delete the project library, edit its database, or repeatedly overwrite the current project while waiting for help. Keep a protected copy and preserve the candidate backups. If the issue began after a version change, mention the old and new versions and whether the project was opened or saved in each.

If you’re posting publicly, describe the symptom without sharing client names, confidential footage, account details, or complete project files. A short screen recording of a blank editor may help, but check it for private information before sharing. A screenshot or recording should show enough context to establish the project, selected item, and Fusion page without exposing material you don’t own.

How do I prevent Fusion nodes from disappearing again?

To reduce the chance of losing Fusion work, save deliberately, keep project backups, and export a separate project copy before major changes or version moves. A backup routine won’t prevent every problem, but it gives you recovery points to inspect.

Use a routine like this:

• Keep Live Save available and check its status. Resolve’s save preferences can vary by version and setup. Confirm the current setting in your installed release rather than relying on a remembered menu path.
• Enable project backups if they fit your workflow. Check where Resolve stores them and whether that location is available to your system.
• Use timeline backups where appropriate. They can help recover timeline states, but inspect the Fusion composition too.
• Export important projects at meaningful milestones. Blackmagic Design support staff recommend project exports for important long-term work, with copies stored away from the system drive.
• Export critical compositions separately. A composition export adds a copy of the Fusion node tree, but it isn’t a substitute for a project export.
• Name copies so you can tell them apart. Include a project or shot identifier, date, and reason for the copy.
• Test recovery without replacing your working version. Open candidates under new names and verify the expected graph before committing to one.
• Back up before updating Resolve. Review the applicable update guidance and keep a recoverable project copy before changing software on important work.
• Keep a short record of critical compositions. A note with the shot name, expected output, and any unusual media dependency can speed up a later comparison.

A simple naming scheme can prevent confusion:

These are example names, not Resolve-generated naming rules. Adapt them to your team’s file conventions.

For cloud libraries, distinguish the library backup from an individual project or timeline copy. Blackmagic’s guide explains that restoring a library backup creates a new library, which can help keep the current one intact during inspection. Confirm that the restored library contains the project and composition you need before treating it as a recovery.

A backup routine should also include a test. Export a project copy, confirm you can locate it, and learn how to inspect a backup on a duplicate project. Don’t wait until the graph looks empty to find out that an export went to an unfamiliar folder or that your recovery plan depends on unavailable media.

If you work with multiple people, agree on who creates recovery copies and how they’re named. A team can avoid confusion by marking the current working project clearly and treating backups as read-only until someone verifies them. This matters especially when two libraries or timelines use nearly identical names.

If you want on-screen guidance while locating the relevant Resolve controls, TryUncle can guide you through this task on Mac and Windows. You stay in control and make the changes yourself.

What is the safest next step if the nodes are still gone?

If the correct Fusion composition still has no expected nodes after checking the selection and graph view, stop changing the original project and inspect a protected backup copy. Recover only after you can see the expected graph in that candidate.

Use the order that matches your situation:

• Wrong project, timeline, or clip: reopen the right item and inspect Fusion again.
• Graph not visible: reframe the node editor and check the layout or bookmarks.
• Graph visible but not affecting the output: inspect connections, node state, viewer, and playhead position.
• Only one timeline seems affected: inspect timeline backups in a separate recovery copy.
• The composition appears to have reverted: compare project backups and composition exports without overwriting the current project.
• A cloud library may be involved: identify the library first and inspect a restored backup as a separate library.
• No backup contains the graph: preserve what you have, document the version and steps, and contact Blackmagic Design support or the community forum.

When the graph is recovered, save the recovery copy under a new name, close it, reopen it, and verify the same nodes and output. If it survives that check, you have a known-good working state to build from. If it doesn’t, keep the recovery copy and seek help before making further changes.

The safest recovery is the verified copy that restores the graph without replacing the only project you have.

When you’re unsure, preserve first and diagnose second. Check the project, timeline, selected item, and graph view; then inspect backups in copies. Don’t rebuild or overwrite the only project until you know whether the nodes were hidden, saved elsewhere, or truly missing.