> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/nodes/3d-node/text-to-3d.md).

# Text to 3D

Generate a textured 3D model from a written description

Text to 3D builds a model from your prompt alone—no reference image needed. Describe the object, pick a model that accepts text input, and the node returns a textured 3D asset you can stage, capture, and export.

## How It Works

1. Add a 3D Node and pick a model with text input (see [3D Models](/models/3d-models.md)).
2. Type a description directly into the node, or connect a text node to its prompt input.
3. Click **Run**. Most generations take around 5 minutes.

Some models (for example **Tripo P2** and **Tripo H3.1**) also accept a **negative prompt** and per-stage seeds so you can steer away from unwanted details and reproduce a result.

## Prompting Tips

* **Describe one object** — text-to-3D models produce a single asset; scenes with several subjects tend to merge or drop elements
* **Name material and style** — "matte ceramic", "brushed steel", "low-poly cartoon" translate directly into textures and geometry
* **Keep the pose neutral** — front-facing, symmetric descriptions reconstruct more cleanly than dynamic action poses
* **Iterate on 2D first** — if a look needs several passes, refine it with an image model and switch to [Image to 3D](/nodes/3d-node/image-to-3d.md)

## Models

Not every 3D model supports text input; the model picker only offers compatible models once a prompt is the sole input. Visit [3D Models](/models/3d-models.md) for the full list with descriptions and supported inputs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flora.ai/nodes/3d-node/text-to-3d.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.