Skip to main content

tripo/h3.1/text-to-3d

Tripo H3.1 Text to 3D turns a written object description into a 3D asset, normally a GLB with textures. It first creates a reference picture, then builds the object from that picture. The additional `image_seed` belongs to that first visual step, while the geometry and texture stages have their own seeds.

From $0.288/request

Workbench

Input

Text to 3D
127/1024
Text-driven reconstruction: Required object description, at most 1,024 characters; include complete shape, material, colour, style and scale. at least 1 characters · at most 1024 characters
Textureaffects price
Text-driven reconstruction: On by default; adds colour textures, and a plain mesh requires generate_pbr to be off as well.
PBR materialsaffects price
Text-driven reconstruction: On by default; PBR materials enable texturing even when generate_texture is off.
Texture qualityaffects price
StandardDetailed8KFast
Text-driven reconstruction: standard is the default; detailed and extreme (8K) add quality charges; fast uses v3.5 at the standard rate; no quality charge without textures.
Geometry qualityaffects price
StandardDetailed
Text-driven reconstruction: standard or detailed; detailed adds surface-geometry processing and its own charge.
Quad mesh (FBX)affects price
Text-driven reconstruction: Produces quad topology in FBX instead of GLB; ignored and not charged with generate_parts.
Low Polyaffects price
Text-driven reconstruction: Handcrafted-style low-poly processing; a face_limit no higher than 20,000 is recommended and a dedicated add-on applies.
Generate Partsaffects price
Text-driven reconstruction: Separates the object into untextured triangular parts; texture and quad settings are ignored and their charges replaced by the parts add-on.
Safety checkerOff

SpicyAPI does not run a safety checker on this model. Your prompt and media go to the model as written, and the model itself decides what comes back.

Checking your account before enabling submission and pricing.

Output

Ready for a new run
Loading 3D model…
Example result

Missing the model you need?

TRIPO H3.1 API

Build detailed 3D objects from a reference image or a written idea.

Key numbers

Textured by default
PBR
Base colour, metal-roughness and normal maps embedded in the GLB.
Face count
1K–2M
Set face_limit for a light web asset or leave it empty for full detail.
Processing time
~3 MIN
167 seconds for a textured boot at the default settings in our run.

Before you spend

Image to 3D
  • Without face_limit the mesh is very dense: our default-settings boot came back with 1.47 million triangles in a 45.8 MB file. Set face_limit when the model is meant for a browser or a phone.
  • The model sees only the side in the picture and infers the rest. It placed the heel loop on the correct side of a boot shot from the front, but hidden detail is still a guess.
  • There is no prompt and no rigging: the result is a static mesh, or a set of untextured parts with generate_parts. Every paid option adds to the price, so the cheapest request is a plain untextured mesh.
Text to 3D

Fox elements appear only in part: the orange glazed teapot has a small fox head on the spout, with pointed ears, a nose and eyes, plus orange ear- or tail-like protrusions on the back. The curled sleeping-fox body and tail-shaped handle were not achieved; the handle is an ordinary tall loop.

What it does

Rear three-quarter render of the Tripo H3.1 boot model on a grey backdrop, with the heel loop at the back and the lace hooks on the front, where they belong.

Reads the hidden side well

The heel loop lands at the back

From a straight front photo of a boot, Tripo H3.1 put the heel loop, lace hooks and tread on the correct sides instead of mirroring the front.

Pay only for the stages you use

Priced add-ons, free controls

Side render of the textured Tripo H3.1 boot model on a grey backdrop, with leather, stitching, red laces and the heel loop coming from the PBR maps.

Textures, HD or 8K textures, detailed geometry, quad topology, low-poly topology and separate parts each add a fixed amount; face count, scale, orientation, alignment, texture version, lighting removal and seeds cost nothing extra.

Made with Tripo H3.1

  • Photo in, mesh out: the front-on boot photo sent to Tripo H3.1 beside the tan leather model it returned, turned to a three-quarter view.
  • Photo in, mesh out: the toy astronaut picture sent to Tripo H3.1 beside the 97,834-triangle model it returned, turned to a three-quarter view.

Where it fits

  • Game and AR props

    Cap the face count and switch on quad topology to get an FBX that an engine or a modelling tool can take without a separate remeshing step.

  • Product pages and configurators

    Turn a packshot into a textured model for a 3D viewer; detailed textures keep printed labels and stitching legible up close.

  • Untextured meshes for printing

    Switch both texture options off to get a cheaper plain mesh for 3D printing, sculpting or your own texturing pass.

Model reference

Tripo H3.1 API reference

How to call the Tripo H3.1 API

  1. Send one picture

    Upload a JPEG, PNG or WebP of one subject on a plain background; a three-quarter angle helps most.

  2. Set the options you need

    Keep the textured default, add texture_quality or geometry_quality: detailed if needed, and set face_limit for web or mobile use.

  3. Collect the file

    Poll the task for about three minutes and download a GLB, or an FBX if you turned quad_mesh on.

The short version

Start H3.1 with image_url for an existing reference or prompt for a described object. Select the finish and mesh options, wait for the task result and inspect the downloaded asset from every angle.

Tripo H3.1 API questions

All Tripo models3

Related comparisons