Blender Output Save Glb

If your workflow generates 3D output - mesh generation, 3D-from-image, a texture bake that lands back on geometry - BlenderOutputSaveGlb is how the result gets out of ComfyUI and back into Blender. It's the pack's wrapper around ComfyUI's native SaveGLB node: it writes the incoming mesh to the server's output folder as a GLB and surfaces it to the add-on so the file shows up for import in your Blender session. In the "generate a mesh, drop it in the viewport" pipeline, this is the handshake at the end.

The source is about as minimal as a node gets: it subclasses SaveGLB, keeps the parent's schema - including the mesh input that accepts any 3D file type the ecosystem knows (GLB, GLTF, OBJ, FBX, STL, USDZ, PLY, splat/point-cloud formats) - and overrides just the filename_prefix default to 3d/blender. Everything else is the native save path.

Inputs and outputs

• mesh - the 3D output to save. The type list on this socket is deliberately broad because the pack doesn't want to break when your mesh-generating workflow hands it a file path rather than a true mesh tensor - it accepts a range of FILE_3D_* types plus raw mesh and point-cloud kinds.
• filename_prefix - where the GLB lands, default 3d/blender. Keep the 3d/ part or change it; it's just the prefix under output/.

It's an output node - no data outputs, because its job is done when the file is written and reported to the add-on.

Installing it

Whole-pack routine. 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 and the README says latest is required (the save-3D support depends on it). 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

The file lands on the server's output folder, and the add-on fetches it - on a remote ComfyUI that means the network path, and a server started without --listen won't be reachable at all. Second, this node is specifically the GLB/bridge saver; if your workflow's 3D pipeline saves through some other dedicated node, the add-on won't pick it up - match the output node to what the bridge expects. Third, the broad mesh socket accepts file-path inputs, so don't be surprised when a "mesh" wire is really a path string - the node is built to swallow both. And the standing flow rules apply: export in API format, import into the add-on, run once in ComfyUI to confirm. 3D generation is heavy, and when Blender shares the GPU it's competing for the same memory the mesh pipeline wants.