Save First Frame Image

This one is exactly what it says: a save node that writes an image to disk and - the useful twist - hands you back the file path as a string. The intended job is captured in its display name, "Save First Frame Image": you use Qwen-Image-Edit to prepare a starting frame, save it here to verify it looks right, and get its path so a downstream step (a Wan video pass, another workflow) can pick it up. It's the bridge half of "QwenImageWanBridge" made literal - edit a first frame in Qwen, then feed it forward.

Nothing fancy, but the path output is what separates it from the stock Save Image node. A normal save node is a dead end; this one lets the rest of a pipeline know where the file landed.

How it works

It's an output node - the terminal kind that actually writes files, not one you chain conditioning through. You give it an image and a filename prefix; it saves to your ComfyUI output directory and returns the resulting path. That path string is the point: it turns a saved frame into something a later node or an external process can reference by location, which is how you'd hand a Qwen-edited first frame off to a Wan image-to-video run.

The inputs and outputs that matter

• image (required) - the frame to save, typically the decoded output of a Qwen-Image-Edit pass.
• filename_prefix (default qwen_first_frame) - the name stem for the saved file. Set it to something you'll recognize if you're saving several.

Output: file_path (STRING) - where the file was written. Wire it into whatever needs to know the location. Because this is an output node, it also finalizes that branch of the graph.

How to install it

ComfyUI Manager: search ComfyUI-QwenImageWanBridge, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/fblissjr/ComfyUI-QwenImageWanBridge

then restart. No model needed - it's a file-writer.

Common issues & troubleshooting

You can't find the saved file. It goes to ComfyUI's standard output folder under your filename_prefix. The file_path output tells you exactly where - read it if you're unsure, rather than hunting through directories.

The path output isn't reaching the next node. Confirm file_path is actually wired onward. The whole reason to use this over a plain Save Image node is that path string; if you're not consuming it, a normal save node would do the same job.

You expected a preview, not just a save. This node's role is to write-and-report, aimed at handing a verified first frame to a later stage. If you just want to eyeball the result in the UI, pair it with a Preview Image node; the saver's contribution is the on-disk file and its path.