Tripo
Tripo H3.1
tripo-h3.1/multiview-to-3d
Tripo's high-detail 3D generation model, supporting the generation of textured 3D assets from text prompts, a single image, or multiple views, with adjustable polygon count and texture quality and PBR material output, suitable for asset creation such as game props and product visualization
Try tripo-h3.1/multiview-to-3d
Input
Upload different views of the same object in order: front (required), left side, back, right side, at least 2 and at most 4 images; only JPG, PNG, and WEBP are supported.
Output
Pricing
tripo-h3.1/multiview-to-3d per model
+ $0.290 finer geometry
Positioning Overview
A multi-view-to-3D model generation tool that accepts 2 to 4 multi-angle images of the same object and outputs a 3D asset with geometric structure. Input images are provided in front, left, back, and right order. It suits game artists, product visualization professionals who have product photos or turntable footage, quickly turning real objects or design drafts into 3D models that can be further edited, rendered, or exported.
Core Highlights
- Multi-view constrained geometry — 2 to 4 images of the same object from different viewpoints can be used together for modeling, constraining the silhouette more fully than a single image.
- Adjustable geometry and texture fidelity — Both geometry quality and texture quality can be set to standard or detailed, trading off speed against detail according to use.
- Flexible material and face count control — Textures and PBR materials can be enabled or disabled, and a target triangle count from 1,000 to 1.5 million (2 million for detailed geometry) can be specified.
- Style and reproducibility control — Orientation can be set to align with the input images, and geometry and texture each have their own random seed for pinning down results.
Capability Description
Multi-view image modeling: Pass in 2 to 4 HTTPS images describing the same object in front, left, back, and right order to generate the corresponding 3D model asset.
Textures and PBR materials: Textures and PBR materials are generated by default; both can be disabled together to keep only a pure geometry mesh. Texture quality can be set to standard or detailed.
Face count cap control: A target triangle count from 1,000 to 1.5 million (2 million for detailed geometry) can be specified; if left blank, the model decides adaptively, making it easy to match downstream pipeline budgets.
Orientation and alignment: When orientation is set to align_image, it automatically rotates to match the input images; texture alignment can be set to the original image or the geometry.
Random seed reproducibility: Set integer seeds separately for geometry and texture to help reproduce generation results under the same inputs and settings.
Use Cases
- Product turntable photos to 3D assets — E-commerce or product teams use multi-angle product photos as input to get textured 3D models for web-based 3D display or marketing imagery.
- Game and scene art prototypes — Artists generate mid-poly meshes from multi-view design drafts of characters or props, importing them into engines as close-up props or proof-of-concept assets.
- Scan asset cleanup and retopology reference — Digital asset teams generate textured reference models from multi-view scan images to serve as comparison base meshes for manual reconstruction or material creation.
Limitations and Selection Advice
Images must be HTTPS addresses, and each request must provide 2 to 4 views of the same object; missing or exceeding this range prevents submission. The target triangle count is limited to between 1,000 and 1.5 million (2 million for detailed geometry); higher face counts place greater demands on downstream processing performance. Textures and PBR materials can be disabled together, after which only a pure geometry mesh is output; detailed quality adds detail while extending processing time. Random seeds only help with reproducibility and do not guarantee identical results across multiple generations.
What's new
View changelog →- New model tripo-h3.1/multiview-to-3d is live: Tripo H3.1 Multiview to 3D
- New model tripo-h3.1/text-to-3d is live: Tripo H3.1 Text to 3D
- New model tripo-h3.1/image-to-3d is live: Tripo H3.1 Image to 3D
Frequently asked questions
View all FAQs →-
What is the face count upper limit? Can it reach 2 million?
Yes, the face_limit upper bound is 2 million triangles, but 2 million is only actually supported when geometry_quality is set to detailed; under standard, it is recommended to set it within 1.5 million. If face_limit is not passed, the model adaptively determines the face count.
-
How do I get just a geometry without textures first?
Set both texture and pbr to false. When pbr is true, textures are forcibly generated. If you need textures but not a PBR material, set texture to true and pbr to false.
-
Should high-density geometry have its own separate parameter?
Setting geometry_quality to detailed adds finer mesh detail and is also the prerequisite for the polygon count to reach 2 million; if you need more refined textures, set texture_quality to detailed. Both default to standard, so enable them only as required by the close-up needs of the target asset.
-
How can I reproduce generation results so it's easy to compare different parameters?
Geometry and textures each have their own fixed seed: model_seed controls geometry, texture_seed controls textures, and text-to-3D additionally has image_seed to control the concept image. When comparing parameter settings, first fix the seeds and change only one parameter, so you can tell which item the difference comes from.
Create a generation task
https://api.hiapi.ai/v1/tasks Headers
AuthorizationstringRequiredAccount API key. Required on every request. Example: Bearer YOUR_HIAPI_API_KEY. Get your API key
Content-TypestringOptionalThe request body is always parsed as JSON; when sent, only application/json (optionally with charset) is accepted — any other value returns 415. Example: application/json.
Idempotency-KeystringOptionalIdempotency key, up to 255 bytes. Retries with the same key from the same account create the task only once; replays return the original taskId.
On network timeouts or client retries, the same key creates the task only once — no double charges (scope: the API key's account). Use a business-unique identifier as the key (e.g. "order-42"); replays return the original taskId, and keys expire 24 hours after the first request. See the Unified Async API overview for the full scenario matrix.
Body
modelstringRequiredCurrent fixed value: tripo-h3.1/multiview-to-3d
routestringOptionalCurrent fixed value: default
inputobjectRequired
Business parameters for tripo-h3.1/multiview-to-3d and route default — see the parameter table below.
pbrbooleanOptionalDefault: trueWhether to generate PBR material textures; when true, texture maps are also produced. Default is true.
texturebooleanOptionalDefault: trueWhether to generate textures for the model. Default is true. Note that when pbr is true, textures are forced to be generated; only when both texture and pbr are set to false is a pure geometry mesh output.
face_limitintegerOptionalmin 1000max 2000000Target number of triangles, as an integer, range 1000–1500000 (up to 2000000 when geometry_quality=detailed); if omitted, the model adaptively determines the face count, and the file is usually large—around 50000 is recommended for web display.
image_urlsarrayRequiredminItems 2maxItems 4An array of HTTPS URLs of 2–4 view images of the same object, ordered front, left, back, right; the first image must be the front view.
Array [ string ]
model_seedintegerOptionalRandom seed for geometry generation, as an integer, used to reproduce the same geometry result.
orientationstringOptionalDefault: "default"Model orientation setting, as a string; when set to align_image, the model is automatically rotated to align with the input image. Default is default.
defaultalign_imagetexture_seedintegerOptionalRandom seed for texture generation, as an integer, used to reproduce the same texture result.
texture_qualitystringOptionalDefault: "standard"Texture quality tier, as a string; the detailed tier generates higher-resolution textures. Default is standard.
standarddetailedgeometry_qualitystringOptionalDefault: "standard"Geometry quality tier, as a string; the detailed tier provides finer mesh details. Default is standard.
standarddetailedtexture_alignmentstringOptionalDefault: "original_image"Alignment method of the texture with the input image, as a string. Default is original_image.
original_imagegeometrycallbackobjectOptional
Terminal-state notification config. When omitted, no callback is delivered — poll the task yourself. See the callback note below.
Provide callback.url when creating a task and HiAPI POSTs to your service once the task reaches a terminal state — no polling needed. The callback payload mirrors the task detail structure; signature verification, delivery retries and idempotency are documented on the Unified Async API overview page.
urlstringRequiredRequired when callback is present. A POST is sent to this URL once the task reaches a terminal state; must be a valid http(s) URL.
whenstringOptionalDefault: "final"Only final is supported today — notified on both success and fail.
finalstoragestringOptionalDefault: "temp"Artifact storage tier: temp (default, retained about 7 days) or persistent (long-term, billed by size). Insufficient balance or exceeding the storage cap silently downgrades to temp; the effective tier is shown in the task detail response.
temppersistentRequest examples
# Submit an async task; returns a taskId immediately (no waiting for generation)
curl -X POST "https://api.hiapi.ai/v1/tasks" \
-H "Authorization: Bearer $HIAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "tripo-h3.1/multiview-to-3d",
"input": {
"pbr": true,
"texture": true,
"image_urls": "…",
"orientation": "default",
"texture_quality": "standard",
"geometry_quality": "standard",
"texture_alignment": "original_image"
}
}' const res = await fetch("https://api.hiapi.ai/v1/tasks", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.HIAPI_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
model: "tripo-h3.1/multiview-to-3d",
input: {
"pbr": true,
"texture": true,
"image_urls": "…",
"orientation": "default",
"texture_quality": "standard",
"geometry_quality": "standard",
"texture_alignment": "original_image"
}
}),
});
const task = await res.json();
// { code: 200, message: "success", data: { taskId } } import os, requests
res = requests.post(
"https://api.hiapi.ai/v1/tasks",
headers={"Authorization": f"Bearer {os.environ['HIAPI_API_KEY']}"},
json={
"model": "tripo-h3.1/multiview-to-3d",
"input": {
"pbr": True,
"texture": True,
"image_urls": "…",
"orientation": "default",
"texture_quality": "standard",
"geometry_quality": "standard",
"texture_alignment": "original_image"
}
},
)
print(res.json()) # { code, message, data: { taskId } } 200 OK
{
"code": 200,
"message": "success",
"data": {
"taskId": "tk-hiapi-01HZTQ8BX2N3GM3YFK4Z9D7VQR"
}
} 400 Bad Request
{
"code": 400,
"message": "invalid request",
"data": null,
"error_code": "INVALID_REQUEST"
} Get task detail
https://api.hiapi.ai/v1/tasks/:id Response fields
taskIdstringRequiredTask ID, always prefixed with tk-hiapi-.
modelstringRequiredResolved full model name. Tasks submitted with the route parameter return base@route (e.g. gpt-image-2/text-to-image@ext); otherwise identical to the name passed at creation.
routestringOptionalPresent only when the task was submitted with an explicit route parameter; echoes the submitted value.
statusstringRequiredTask status.
queued Queued, not started yet.
handling Being processed.
archiving Processing finished, artifacts being prepared.
success Terminal: completed, artifacts available (output returned).
fail Terminal: failed (error returned).
After submission, check status: success and fail are terminal, everything else is non-terminal. Poll every 1–3 seconds until terminal. On success, download artifacts from output[].url and transfer them before expireAt; pass storage: "persistent" at creation time when long-term retention is needed.
creatednumberRequiredTask creation time (Unix seconds).
completednumberRequiredUnix seconds when the task reached a terminal state; fixed to 0 while not terminal.
outputarrayOptional
Present only when status == success. Artifact list — always an array; a single task may return multiple types at once (e.g. video + first_frame).
Array [ object ]
Array items
urlstringRequiredArtifact URL, directly downloadable.
typestringRequiredCurrent possible values: video, image, audio, first_frame, last_frame, thumbnail; more may be added later.
expireAtnumberRequiredUnix seconds until which the artifact remains accessible; download or transfer before it expires.
errorobjectOptional
Present only when status == fail.
codestringRequiredBusiness error code.
messagestringRequiredError description.
Response examples
Success
{
"code": 200,
"message": "success",
"data": {
"taskId": "tk-hiapi-01HZTQ8BX2N3GM3YFK4Z9D7VQR",
"model": "happyhorse-1-0",
"status": "success",
"created": 1777282033,
"completed": 1777282099,
"output": [
{
"url": "https://cdn.hiapi.ai/tasks/.../video.mp4",
"type": "video",
"expireAt": 1777886899
}
]
}
} Processing (non-terminal)
{
"code": 200,
"message": "success",
"data": {
"taskId": "tk-hiapi-...",
"model": "happyhorse-1-0",
"status": "archiving",
"created": 1777282033,
"completed": 0
}
} Failed
{
"code": 200,
"message": "success",
"data": {
"taskId": "tk-hiapi-...",
"model": "happyhorse-1-0",
"status": "fail",
"created": 1777282033,
"completed": 1777282099,
"error": {
"code": "TASK_FAILED",
"message": "task failed"
}
}
} Articles
View all articles →-
Tutorial
Tripo H3.1 Practical Application Scenarios: 5 High-Value Use Cases and Implementation Essentials
From text-to-3D to multiview reconstruction: choosing the right mode and parameters by business scenario
-
Guide
Tripo H3.1 Getting Started Guide: Choosing Among Three Input Modes, Parameters, and Pricing
A practical guide for developers on 3D generation integration decisions and cost control
-
Comparison
Tripo H3.1 Side-by-Side Comparison and Selection Guide: How to Choose Among Three 3D Generation Paths and How to Save
A developer-oriented trade-off between pricing and capability, starting from input form, geometric refinement, and PBR/texture switches