Sonder Save Bridge
Let any save node write into your project, then claim the results
- project
- output_dir
- filename_prefix
Sonder Save Bridge is the "bring your own save node" outlet in Sonder Editor. The pack has its own Sonder Save Video for the standard path, but sometimes you want a different save node to do the writing - a specialized exporter, an external tool's save format, a node that does its own post-processing. The Bridge creates a prompt-isolated output directory inside the project cache, external save nodes write there, and after the prompt settles the Bridge registers whatever appeared as proper Sonder assets. Files land in your gallery with tracked metadata, not in an orphaned folder you'll forget.
The key phrase in the docs is "prompt-isolated." Every run gets its own directory inside the project, so a queue of jobs can't stomp on each other's outputs. When the run finishes, the Bridge picks up the files and renames them to the configured stem before registering them.
How it works
Wire the project from a Sonder Editor in. Then:
target_folder- an optional asset-folder label. Reuse an existing label or let a new one be created on registration.prefix- optional filename prefix prepended to all outputs. Empty means skip.mark_queue_complete- when on, the Bridge completes the active Sonder queue job after successfully registering one or more files. This is how a third-party save path participates in the render queue.
Two outputs, and which one you use depends on the save node:
output_dir- an absolute path for save nodes that expect a folder. Files written here get renamed to the stem on registration.filename_prefix- a ComfyUI-relative prefix for native save nodes that honorfilename_prefix(SaveImage and friends). They produce names like<stem>_00001_.extdirectly.
Install and the practical bits
Standard pack install: ComfyUI Manager search Sonder Editor, or git clone https://github.com/SonderSaid/ComfyUI-Sonder-Editor.git into custom_nodes, pip install -r requirements.txt, restart.
A couple of things to keep in mind. The Bridge's finalization is deliberately deferred - the README warns against toggling the External Project Links setting while a Save Bridge job is in flight, because the pending finalization safely waits until the path is trusted again. And "after the prompt settles" is doing real work there: registration happens post-execution, so the asset's metadata reflects the finished run rather than a half-written file. If your save node writes multiple files with different extensions, that's fine - the Bridge registers them as a group and names them consistently.
It's the node to reach for when Sonder Save Video's presets aren't what you need but you still want everything in the gallery. The "takes and gallery" workflow keeps working even when the writer is someone else's node.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| project | SONDER_PROJECT | The project that owns the bridge output directory. | |
| target_folder | COMBO | Optional asset folder label. Existing labels may be reused and new typed labels are created on registration. | |
| prefix | STRING | Optional filename prefix prepended to all outputs. Leave empty to skip. | |
| mark_queue_complete | BOOLEAN | false | When enabled, the bridge completes the active Sonder queue job after it successfully registers one or more files. |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| output_dir | STRING | Absolute prompt-isolated directory for save nodes that expect a folder path. Files written here are renamed to the configured stem on registration. |
| filename_prefix | STRING | ComfyUI-relative filename prefix encoding the configured stem. Native save nodes that honor filename_prefix (SaveImage et al.) produce filenames like <stem>_00001_.ext directly. |