Fuser

Node Presets

Save a node's inputs as a reusable snapshot, then apply it to any compatible node — same type or different.

A preset is a saved snapshot of a node's input values. Configure a node once, save the preset, and you can apply it later to that same node type for an exact restore — or to a different node type, where Fuser copies over whichever fields actually fit.

Presets are personal by default. When you're working inside a workspace, you can also save them at the workspace level so everyone on the team can reuse them.

Saving a Preset

Configure the node first

Fill in the inputs on the node you want to capture — prompts, sliders, dropdowns, the lot. The save action snapshots the node's inputs at the moment you save, so configure it the way you'd want it restored.

Open the save dialog

Right-click the node and pick Save as preset… from the Presets submenu, or open the Properties panel and click the bookmark button at the top.

Name and (optionally) describe it

Give the preset a clear name. A description is optional — but a single sentence about what makes this configuration useful goes a long way when you come back to it weeks later.

Pick a scope

Inside a workspace, the dialog shows two pills: Personal and Workspace. Personal presets are visible only to you. Workspace presets are visible to everyone on the team. Outside a workspace, only Personal exists, and the picker is hidden.

Applying a Preset

The Properties panel header on every node has a preset picker — click the dropdown to open it.

The picker has three controls:

  • Search — type to match across every preset you can see. While searching, the filter row steps out of the way and the search runs across both same-type and compatible presets.
  • Same-type chip — locked on. Shows the live node's icon and name so you always know what you're filtering against; you can't deselect this.
  • Compatible toggle — off by default. Turn it on with the + chip to widen the list to presets saved from other node types whose fields can also apply here. See Understanding Compatibility.
  • Scope filter — visible only inside a workspace. Switch between All, Personal, and the workspace itself to scope the list.

Click any preset to apply it. The picker also shows up in the right-click Presets submenu, with the same Same-type and Compatible lists.

Inputs already driven by a connection are left alone

If a node input has an incoming edge from another node, the preset won't overwrite it. That input keeps reading from its connection, and the toast tells you which fields were preserved.

Understanding Compatibility

Presets are compared per field, not per node. When you apply a preset to a node, Fuser walks the preset's inputs and tries to copy each one onto the live node. A field is copied only if the live node has an input by the same name and the value would actually fit:

  1. If the live input is a dropdown with a fixed set of options, the preset value must be one of those options.
  2. If both sides expect the same kind of input (both sliders, both prompts, both images), the value is trusted.
  3. Otherwise the live input's validator gets the final say.

Empty values in the preset (blank text, no media, no selection) are skipped silently — they don't count as incompatible. Fields the live node doesn't have are reported as incompatible.

The visualizer below shows the same preset applied to two different targets — the source node type, and a different one — so you can see what gets copied, what stays connected, and what's left out.

Apply Outcomes

After every apply you get a toast. The shape of the toast depends on how much fit:

OutcomeWhat happenedToast type
All appliedEvery non-empty preset field had a home on the live node.Success
Partial applySome fields applied; others were connected or didn't fit.Success
No fields fitThe preset had nothing in common with this node.Warning

A partial-apply toast pairs the title Applied "Editorial portrait" with a description like 2 of 4 fields set · 1 kept connected (steps) · 1 incompatible (output_format) — the count and the affected field names. A failed apply leaves the node untouched: no field is changed, and the picker doesn't mark the preset as active.

Managing Personal vs Workspace Presets

Personal presets are only visible to you. They follow your account, not a project — every project you open shows the same personal library.

Only the creator can edit or delete a personal preset. Other people don't see them at all.

Workspace presets are visible to every member of the workspace you saved them in. They're the right choice for house styles — the prompt patterns, default parameters, and model settings your team has agreed on.

Editing and deleting a workspace preset is allowed for:

  • The person who created it
  • Admins and Owners of the workspace

A workspace preset only appears in the picker when you're working inside its workspace. Switch to Personal context (or another workspace) and it's hidden.

Updating and Deleting

Once a preset is applied to a node, the right-click Presets submenu shows Update "<name>" and Delete "<name>" alongside Save as preset…. The same actions are available from the Properties panel — the edit pencil next to the picker updates the applied preset to the node's current inputs.

Update and Delete are only offered when you're allowed to perform them. If you can't edit a workspace preset, the options aren't shown.

Updating overwrites the preset for everyone who can see it

A workspace preset is shared. When you update it, the next time a teammate opens the picker they'll see your new values. If you want to fork the configuration, save a new preset instead of updating.

Which Nodes Support Presets

Presets are available on standard tool nodes — image, video, text, chat, mesh, and so on. They're not offered on these node types, which either have no inputs to capture or carry per-instance state that wouldn't restore meaningfully:

  • Compositor nodes
  • Default nodes
  • Creative Code nodes
  • Group nodes

On unsupported nodes the Presets entry is omitted from the right-click menu and the Properties panel doesn't show the picker.

What's Next?

On this page