> For the complete documentation index, see [llms.txt](https://docs.m-xr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.m-xr.com/marso-studio/quickstarts/generate-a-pbr-3d-model.md).

# Generate a PBR 3D Model

Describe an object, or give an image, and get a textured 3D asset with PBR maps.

**You need:** any plan. Downloads need a paid plan or the trial. See [Plans](https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md#plans).

## Make it

1. Click **Quickstart** in the left sidebar and choose **Generate PBR Asset**.
2. Give it one input:
   * **Text**: describe one solid object, such as *A weathered wooden treasure chest with iron bands*. A fruit bowl or a loaded shelf is several objects, and fails.
   * **Image**: one object that fills most of the frame. PNG, JPG or WebP, up to 20 MB.
3. Press **Generate**, and keep the tab open until the run is done.

It makes the image (from text), then the 3D model, then the PBR textures.

## What you get

A textured 3D asset with albedo, metallic, roughness, IOR and normal maps, in your Library.

## If the model comes out wrong

* **The object is too small in the image.** It's the most common cause of a failed 3D model. Crop tight, or describe the object alone.
* **Try another generator before another image.** Open **Advanced** and change **Model**. See [Choosing a generator](https://docs.m-xr.com/marso-studio/reference/nodes-reference.md#choosing-a-generator).

## What it costs

Up to **80** credits from text, **70** from an image. The exact figure shows beside **Generate**.

## Next

* Already have the mesh? [Add PBR to Your 3D Model](https://docs.m-xr.com/marso-studio/quickstarts/add-pbr-to-your-3d-model.md)
* Build the same route by hand: [Nodes reference](https://docs.m-xr.com/marso-studio/reference/nodes-reference.md)


---

# 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.m-xr.com/marso-studio/quickstarts/generate-a-pbr-3d-model.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.
