> 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/workflows/apply-pbr-to-your-own-model.md).

# Apply PBR to your own model

The fastest way to add PBR materials to an asset you already have. This is what an **Individual** project opens with.

This is a **single-asset route**. If you want a whole environment rather than one object, see [Generate a scene](/marso-studio/scenes/generate-a-scene.md).

**Nodes:** 3D Model Upload → Generate PBR Textures

### When to use this

You already have a textured mesh — a scan, a purchased asset, something out of your own pipeline — and you want I2M to predict its material stack.

### Steps

1. Create a **new project** and choose the **Individual** workflow. You land on 3D Model Upload → Generate PBR Textures.
2. In **3D Model Upload**, upload your `.glb`, `.usdz` or `.fbx`. Uploading is free — you're only charged when you generate.
3. Run **Generate PBR Textures**. Usually a few minutes.
4. **Preview** in the 3D viewer — switch HDRIs and compare against the original to check the prediction.
5. **Export** the textured asset and its individual maps.

### What you get

**Albedo, metallic, roughness and IOR**, as individual maps and as a textured mesh. *(Normal map prediction is in active development.)*

### Tips

* **Bring a clean, base-colour asset.** Assets that already carry PBR work against the prediction — strip existing material data first.
* **Check your UVs before you spend the credits.** I2M enhances materials; it can't fix overlapping UVs or broken geometry.
* **Keep files under 100 MB.**

See [3D file support](/marso-studio/preparing-your-assets/3d-file-support.md) for the full input rules, the [Nodes reference](/marso-studio/reference/nodes-reference.md), and [Credits & billing](/marso-studio/reference/credits-and-billing.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.m-xr.com/marso-studio/workflows/apply-pbr-to-your-own-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.