Blender Output Download 3D

Where BlenderOutputSaveGlb writes a mesh and lets the add-on fetch it, BlenderOutputDownload3D is the variant that takes a 3D file path from anywhere in the workflow and pushes it straight back to Blender as a downloadable result. Think of it as "this file, to Blender, now" - the output-side counterpart to BlenderInputLoad3D, and the node you reach for when your 3D result isn't a native mesh tensor but a path some other node produced.

The mechanism is refreshingly explicit. The node takes a model_file string (marked force-input, so it has to come from upstream rather than being typed), and its execute splits the path into filename and subfolder, then returns a websocket message announcing a 3d output to the frontend - the same channel ComfyUI uses to surface outputs. The add-on sees that message and offers the file for download into Blender. It's a deliberate, small piece of plumbing, and it's the only node in the pack that hand-rolls its own result message instead of leaning on a native saver.

Inputs and outputs

• model_file - the 3D file path to send to Blender. It's force-input, meaning you wire it from upstream - typically the path output of a 3D-generation node or something like a BlenderInputLoad3D's path passed through.

It's an output node with no data outputs. Its whole job is the file transfer.

Installing it

Standard for the pack. ComfyUI side, ComfyUI Manager → search "ComfyUI-Blender", or:

cd ComfyUI/custom_nodes
git clone https://github.com/alexisrolland/ComfyUI-Blender

Restart ComfyUI. No extra Python dependencies, but you need a current ComfyUI - schema v3 nodes won't load on older builds. The Blender add-on is the other half, a ZIP from the latest release installed via Edit > Preferences > Add-ons > Install from Disk.

Where people get burned

Because the input is force-input, a beginner sees an input socket they can't type into and assumes the node is broken - you have to wire a path into it from upstream; that's by design. Second, this node reports the file to Blender but doesn't save anything by itself: if your workflow's 3D generator only creates the file when some save node runs, make sure that save happens before this node hands the path over, or Blender gets a path to a file that doesn't exist yet. Third, the file needs to be somewhere the add-on can reach - the output folder, in practice - and on a remote server that means --listen and a reachable network path. And the pack's standing rules apply: API-format export, import into the add-on, run once in ComfyUI to confirm. It's a narrow tool, but when you need "this exact file, back in Blender," it's the one.