Tripo Segmentation: The Essentials
Last updated: November 10, 2026
Tripo Segmentation takes a finished 3D mesh and splits it into separate, editable parts, so a single fused model becomes a set of components you can select, texture, rig, or swap on their own. This is the step between generating a 3D asset and actually working with it in a production pipeline.
This article covers Tripo Segmentation v2 (currently in preview), a semantic model that splits the mesh along meaningful components, with controllable granularity and optional reference-image guidance. The earlier, geometry-based Tripo Segmentation v1 is retiring: it is no longer in the model catalog and stops working on December 1, 2026. Workflows, apps, and API integrations that already use v1 keep working until then; switch them to v2 before that date. Segmented models you already made with v1 stay in your library.
Which Model Should I Use?
Model | ID | Method | Best for |
|---|---|---|---|
model_tripo-segmentation-v2 | Semantic, with granularity and reference image | All part separation: a hands-off split with the defaults, or control over how many parts and where they split | |
Tripo Segmentation v1 (retiring) | model_tripo-segmentation-v1 | Geometry-based, no settings | Nothing new: stops working on December 1, 2026. Switch to v2. |
Use v2 for all segmentation. Upload a mesh and run it with the defaults for a quick, hands-off split, then adjust the granularity or add a reference image when you need more control over how the mesh is divided. If a workflow, app, or API integration still calls v1 (model_tripo-segmentation-v1), point it at model_tripo-segmentation-v2 before December 1, 2026: v2 takes the same 3D Model input, with the same 150 MB limit.
Parameters
Tripo Segmentation v2 (preview)
v2 adds semantic segmentation plus controls for how the mesh is divided.
Parameter | Required | Default | Range / Options | Notes |
|---|---|---|---|---|
3D Model | Yes | None | GLB, OBJ, FBX | The mesh to split into parts. Maximum file size 150 MB. |
Granularity | No | Balanced | Simple / Balanced / Detailed | How finely to divide the model. Simple gives a few large parts; Detailed breaks it into many smaller ones. Overridden when a reference image is provided. |
Split By Connectivity | No | true | true / false | Also separates pieces that are not physically joined, treating each disconnected chunk as its own part. |
Reference Image | No | None | Image | Optional image that guides how the model is divided into meaningful parts. When provided, it takes over from the Granularity setting. |
How It Works
Upload a 3D mesh and Tripo Segmentation v2 identifies its meaningful components (limbs, accessories, mechanical pieces) and returns the same model with those parts separated into individual components, ready to be selected and edited on their own. Because the split follows what the parts are rather than geometry alone, the boundaries come out sharp, and the parts stay compatible with rigging, texturing, and export.
Granularity sets how finely the mesh is divided: Simple yields a few large parts, Balanced (the default) sits in the middle, and Detailed breaks the model into many smaller parts. Split By Connectivity additionally separates pieces that are not physically joined. A Reference Image can guide the split and overrides the Granularity setting when supplied.
The segmentation is structural: the parts are split in the model data, but a normal render still shows the original textured model. To see and select the individual parts, open the segmented asset in the Scenario 3D viewer. Open each example on Scenario to rotate it and inspect the parts produced at each level.
Robot crab, v2 at Detailed granularity · Open on Scenario
See each granularity level on Scenario: Simple (chair), Balanced (fox), and Detailed (robot crab).
Earlier Results from Tripo Segmentation v1 (Retiring)
These examples were made with the geometry-based Tripo Segmentation v1, which stops working on December 1, 2026, from meshes generated with Tripo P1, Tripo 3.1, and Hunyuan 3D 3.1 Pro. They stay here for comparison; for new work, run the same kind of mesh through v2.
A robot crab (generated with Tripo P1), segmented by v1. Open on Scenario to rotate the mesh and inspect the separated parts.
Robot crab · Open on Scenario
A swordsman statue (generated with Tripo 3.1), segmented into figure and sword and armor pieces.
Swordsman statue · Open on Scenario
A table scene with props (generated with Hunyuan 3D 3.1 Pro), where each object becomes its own part.
Table with props · Open on Scenario
Use Cases
Rigging prep: separate limbs, joints, and accessories so a character mesh is ready to weight and rig.
Part-based texturing: isolate a component to retexture or recolor it without touching the rest of the model.
Model customization and swapping: break a character or prop into parts so pieces can be replaced, hidden, or mixed and matched.
Hard-surface and mechanical assets: split robots, vehicles, and machines into their mechanical components for editing or animation.
3D printing: divide a model into printable pieces that can be produced separately and assembled.
Modular asset pipelines: turn a single generated mesh into a kit of reusable parts.
Tips for Better Results
Start from a clean mesh. Models with well-defined, distinct parts (clear limbs, separate accessories) segment more cleanly than smooth, fused shapes.
Keep files under 150 MB. That is the hard input limit; decimate or retopologize very dense meshes first if needed.
Inspect parts in the Scenario viewer. A flat render looks unchanged, so open the segmented asset to confirm the parts split where you expect.
Start with the defaults, then tune the granularity. If the Balanced split is too coarse or too fine for your model, re-run it at Detailed or Simple, or add a reference image to guide where it splits.
Segment before rigging or texturing. Doing the split first gives you the separate components those later steps depend on.
Known Limitations
Tripo Segmentation v1 is retiring. It is no longer in the model catalog and stops working on December 1, 2026, after which v1 generations fail. Move any workflow, app, or API integration that uses it to v2 before then.
v2 is in preview. Its behavior and results may still change while it is in preview.
A reference image overrides Granularity. When you supply one, the Granularity setting no longer applies, so leave the image out when you want to compare Simple, Balanced, and Detailed.
Parts are not color-coded in a standard render. The segmentation is structural, so a normal preview looks like the original model. Open the asset in the Scenario 3D viewer to see and select the parts.