Tripo: Import model

Every node in this pack is built around model_info - the cloud handle to a mesh on Tripo's servers. But what if the mesh you want to texture, rig, stylize, or complete is one you already own? That's what TripoImportModel is for: it uploads an existing 3D file to Tripo, gets you a model_info, and suddenly every other node in the pack can operate on your asset instead of only on things Tripo generated. It's the "bring your own mesh" doorway, added to the pack in 2026.

This is the node to reach for when you have a scan, a downloaded model, or a mesh from another generator and you want Tripo's texture, rigging, segmentation, or completion power applied to it. Import first, then chain whatever you need.

What it takes

The inputs are a bit different from the rest of the pack because there's no generation happening - nothing gets produced locally, so there's no model_file output. You get back exactly one thing: model_info, ready to wire into any other Tripo node.

There are three ways in, and you pick one:

• model_url - paste a direct URL to a model file and Tripo downloads it (the newer import path; supported formats include GLB, GLTF, OBJ, FBX, STL, PLY, and zip archives).
• model_file - a dropdown listing 3D files already in ComfyUI/input/. Drop your model in that folder, refresh, pick it.
• Upload button - the pack ships a tiny frontend extension that adds an "Upload Model File" button to the node, so you can push a file from your disk straight into ComfyUI's input directory without touching the filesystem.

The required apikey field works like everywhere else - leave it blank to fall back to TRIPO_API_KEY or config.json.

Install

The pack install covers this node; the frontend upload button comes along automatically:

cd ComfyUI/custom_nodes
git clone https://github.com/VAST-AI-Research/ComfyUI-Tripo
cd ComfyUI-Tripo && pip install -r requirements.txt

Or "Tripo for ComfyUI" in ComfyUI Manager.

The honest part

Import is where the "your file, their servers" reality of this pack gets explicit: importing means uploading your mesh to Tripo's cloud. Fine for your own assets; worth a second thought if the model isn't yours to share. Also note the drop-down only sees files present at node-creation time - if you drop a new .glb into ComfyUI/input/, reload the workflow or re-add the node so it rebuilds the list. And import itself produces no local file, which confuses people the first time: nothing's missing, the node's job is done the moment you have model_info. From there the pipeline is normal.