Tripo: Refine Draft model

Tripo's early drafts look like a first guess: the idea is there, but the geometry is rough, the surfaces wobble, and you wouldn't put it in a portfolio. Tripo: Refine Draft model is the cleanup step that turns that first pass into something presentable - with one very specific asterisk attached to the whole concept.

Here's the asterisk, and it's the thing you need to remember about this node: it only works on draft models created by Tripo v1.4. Not v2.x, not v3.x, not P1. The input's own tooltip is blunt about it - "Must be a v1.4 Tripo model." If you generate with the default v2.5 model and feed this node the task ID, you'll get an error, and it's not you doing it wrong. It's by design. Refine is a v1.4-era workflow, kept alive because that version's drafts genuinely benefit from a second pass.

Like the rest of the partner/3d family it's built into ComfyUI core with nothing to install, and it runs on Tripo's cloud: you log in with a ComfyUI Account, pay out of prepaid credits, and the node polls Tripo's servers while the refinement job runs. It's also a slow one - the polling is set to expect a long job, so budget for it sitting there with a progress bar.

Inputs and outputs

The input list is as minimal as it gets: a single model_task_id socket. That's it. No prompt, no settings, no quality dial. Refine is a black box that takes a v1.4 draft and returns the cleaned-up version.

Outputs are the standard Tripo trio: the model_file string, a model task_id for the refined model, and the GLB. The new task_id is what you'd chain forward - into Tripo: Texture, Rig, or Convert - since the refinement produces a fresh asset you can build on. Wire the GLB into Preview 3D & Animation or Save 3D Model to get it out of ComfyUI.

How to actually use it

There's exactly one workflow shape that makes sense here:

1. Generate with Tripo: Text to Model or the image/multiview variants, explicitly set to model_version v1.4.
2. Feed that run's task ID into this node.
3. Chain the refined task ID onward.

Since the modern Tripo models don't support it, you're making a real choice when you pick v1.4: older model, but access to the polish step. For some asset types the v1.4-plus-refine combo still gives results people prefer over a raw v2.5 pass - but it's a taste thing, and you'll know quickly which camp you're in.

The honest take

This node exists because Tripo kept a compatibility path for its v1.4 workflow. If you're not deliberately building on v1.4, ignore it entirely - it'll only ever error out on your modern drafts. If you are on v1.4, it's the difference between shipping a sketch and shipping an asset. Just don't let its one-input simplicity trick you into thinking it works on everything.