Tripo3D H3.1 Image To 3D (Official Edition)

Everything else in this pack makes video. This one is the odd one out, and it's great for it: Tripo3D's H3.1 Image-To-3D node turns a flat image into an actual 3D asset you can orbit, texture, and drop into a game or render pipeline. Concept art in, mesh out.

What this node does

BizyTRD_Tripo3d_H3_1_Official_I23D_API takes one or more images and reconstructs them as a 3D model on Tripo's servers. Give it a single character turnaround or a few reference angles, and it bakes geometry plus a texture from the source images. This is the kind of task your local rig can do now, but only with a heavy pipeline and a lot of waiting; the cloud route is a one-node affair.

And like everything in BizyAirPlus, it's remote: flip the BizyAirPlus button ON, upload your images, and Tripo's GPU farm does the reconstruction while ComfyUI streams back the result. No model files on your disk, no VRAM pressure.

The inputs that matter

• images - the reference image(s), via the autogrowing list. One clean, well-lit shot is a fine start; multiple angles help geometry and texture.
• geometry_quality / texture_quality - both default to detailed. Drop to a lighter setting for fast iteration or game-ready budgets.
• texture - on by default; turn it off if you just want the bare mesh.
• quad - off by default. Quad meshes are friendlier for game engines and rigging than the default triangle soup, so flip it if you're taking the asset into a DCC tool.
• pbr - on by default: physically-based rendering materials (roughness/metalness maps) instead of a flat albedo bake.
• orientation and texture_alignment (default original_image) - tune how the model is oriented and how the texture sits relative to the source.
• auto_size - off by default; enable to let the service normalize the model scale for you.

Plus the shared BizyAir pair: api_config (override endpoint/key per request) and skip_error (placeholder output instead of aborting the workflow on a cloud error).

Outputs - note the difference

• image - yes, this node returns an IMAGE, not a video: the preview render of the generated model. It's an output node, so wire it into a preview or save node.
• request_id - the cloud task ID.
• urls - the hosted asset URLs. This is where your actual 3D file (the mesh/GLB) lives - grab the download link from here. Don't treat the preview image as the deliverable.

How to install

cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAirPlus.git
cd BizyAirPlus
python -m pip install -r requirements.txt

Restart ComfyUI (or install "BizyAirPlus" through ComfyUI Manager). Dependencies are bizyair-cloudberry and bizytrd - no model downloads. First run: account at bizyair.ai → API key → enter it when the ON button prompts (Settings > BizyAirPlus > API Key works; key stored at ~/.BizyAirPlus/apikey.ini).

Where people get burned

The most common stumble is expecting the image output to be the 3D file. It's a preview. The model itself comes through urls, so if you're building a pipeline that consumes the mesh, grab it from there.

Also remember this is cloud-billed: geometry_quality/texture_quality on detailed plus PBR is the priciest combination, so for quick sanity checks drop the quality knobs and skip PBR until you're happy. And the usual pack note: BizyAir's malware reputation is leftover from a 2025 ComfyUI Manager auto-install bug - it's a legitimate SiliconFlow pack. If you ever remove it, pip uninstall bizyair-cloudberry bizytrd rather than just deleting the folder.