> 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/welcome-to-marso-studio-by-m-xr.md).

# Welcome to Marso Studio by M-XR

Marso Studio is M-XR's node-based web app for building production-ready 3D assets and giving them physically-based materials grounded in real-world measurement.

Describe an environment and Marso Studio breaks it into its individual objects, builds each one as a separate 3D asset, and predicts a full PBR material stack for every one of them. Or bring a single mesh you already have and texture just that. Both routes run in the same node editor, in your browser.

### Scene generation

**Scene generation is the main route through Marso Studio.** A favela street, a teenage bedroom, a mechanic's workshop — you start from one scene image and finish with every object in it as a separate, textured, production-ready asset.

The scene isn't generated as one enormous mesh. It's **decomposed into objects**, and each object is reconstructed on its own — so an object half-hidden behind something else in the scene still comes out as a complete asset:

1. **Scene Generation** — describe the environment and get a scene image
2. **Detect Objects** breaks it into its individual objects
3. **You choose what to keep** — everything is selected by default, and nothing expensive runs until you confirm
4. **Reference images, 3D models and PBR** run across every object you selected
5. **Export** the whole scene, or any object on its own

Scene generation is the **Bulk** workflow — pick it when you create a project and the starting nodes are already there. Start with [Generate a scene](/marso-studio/scenes/generate-a-scene.md).

### The material model

At the heart of Studio is **I2M (Image-to-Material)** — M-XR's foundational material model. Give it a textured mesh and it predicts a complete PBR material stack in minutes: **albedo, metallic, roughness and IOR**.

I2M is trained on Marso Measure's measured material data rather than hand-authored guesswork, so its predictions are physically grounded and drop straight into a production pipeline. *(Normal map prediction is in active development.)*

### The node editor

Every route is built from nodes, and you can assemble your own pipeline from any of them:

* **Scene** — describe an environment with **Scene Generation**, break it into objects with **Detect Objects**, then build per-object references with **Generate Reference Images**
* **Images** — generate an image from a prompt, create a multi-view turntable, or edit an existing image
* **3D** — turn an image into a mesh with **Generate 3D Model**, or bring your own with **3D Model Upload** (GLB, USD or FBX)
* **Materials** — run **Generate PBR Textures** to predict and attach a full material set with I2M
* **Preview & export** — inspect the result in the 3D viewer, then download the textured asset and its individual maps

When you create a project you choose a **workflow**, and the starting nodes are placed for you:

* **Bulk** — Scene Generation → Detect Objects, for a whole environment
* **Individual** — 3D Model Upload → Generate PBR Textures, for a single asset

### Who it's for

Marso Studio is built for teams and creators who need realistic 3D assets at volume — AAA/AA game studios, VFX houses, fashion and product visualisation, cultural heritage, and solo artists. If you understand meshes, UVs and PBR workflows, you'll be productive in minutes.

### What you'll need

* An idea for a scene, an image, **or** a textured 3D asset — **GLB**, **USD** or **FBX**
* An M-XR account

If you're bringing your own mesh, it's worth a two-minute read of[ Preparing your assets](/marso-studio/preparing-your-assets/sourcing-and-preparing-assets.md) so your file isn't rejected at the door.

### How it's charged

Marso Studio runs on **credits** — each generation step spends a set number, and your balance is always shown at the top of the screen. Scenes are charged per object, so what a scene costs depends on how many objects you choose to keep.

You get free credits to start with, and more on any day you open the app. See [Credits & billing](/marso-studio/reference/credits-and-billing.md) for the full breakdown.

### Early access

Marso Studio is in **early access** and improving quickly. You may hit rough edges — the web renderer is still being refined, and some predictions are stronger than others depending on your input. Your feedback directly shapes the product. See the [Early access brief](/marso-studio/getting-started/early-access-brief.md) for what to expect and how to report issues.

***

**New here?** Start with [How Marso Studio works](/marso-studio/getting-started/how-marso-studio-works.md), then run your first scene through the [Quickstart](/marso-studio/getting-started/quickstart.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/welcome-to-marso-studio-by-m-xr.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.
