> 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/reference/previewing-and-exporting.md).

# Previewing & exporting

When a generation finishes, inspect the result in the 3D viewer and then download it in the format you need.

### Previewing on the canvas

Hover over a 3D or PBR node, or a card in a group, and click **View preview**, or double-click it. The result opens in a floating viewer beside your graph:

* Drag its title bar to move it, and drag an edge or corner to resize it. It stays square.
* It stays open while you work. Preview another result and it shows in the same viewer.
* **Focus the node** finds the result's node on the canvas, **View in library** opens it in your library, and you can go fullscreen.
* The sun button on its title bar picks the HDRI that lights the model, and the button beside it switches on a camera light that follows your view. On a material made from an image, the camera light becomes the main light: the HDRI dims and its light rig goes off, so the relief of the maps shows as you move the cursor.
* **Controls** on its title bar opens the viewer settings beside the model, the same settings as **Controls** in the Library. Click it again to close them. While they're open, the HDRI, camera light and path tracing buttons are hidden. On a narrow window, **Controls** isn't shown.
* **Close preview**, or Esc, closes it.

For a PBR result, a bar along the bottom of the viewer lets you go back to the finished look with **Beauty Mode**, choose **Normals only**, **No albedo** or **Wireframe** from **Render mode**, click a map's thumbnail to see that map on its own on the model, rate the result with **Good result** or **Poor result**, and download it.

If the model you started from has see-through parts, such as glass, the viewer keeps them see-through on the PBR result. Parts that glow keep their glow too.

A material made from an image shows on a sphere. **Sphere** and **Plane**, at the top left of the viewer, switch the shape, and the plane takes the shape of the map, so a map twice as wide as it is tall shows on a plane twice as wide as it is tall. **Tiled** uses the plane.

A material made from an image with **Displacement** has a displacement layer too. It shows as a grey image you can preview. On the sphere or the plane, **Displacement Height**, on the **Favourites** tab of **Controls**, sets how far the displacement moves the surface, from 0 to 1.

### The full viewer

**View 3D** opens the result's close-up in the Library, over your canvas, with the 3D viewer and its **Controls**. It's on the toolbar of **Generate PBR Textures**, and in the menu of a card in **Generate 3D Models (Group)** or **Generate PBR Textures (Group)**. **Load 3D Model**, **Generate 3D Model** and **3D Retexture** have a library icon instead, **View in library**, which opens the same close-up with the viewer up. See [Library & collections](https://docs.m-xr.com/marso-studio/reference/library-and-collections.md).

Before you export, use the controls to check the result:

* **Selected HDRI** — switch between lighting environments to see how the materials respond.
* **Rotation** and **Auto Rotate** — turn the environment to catch reflections and highlights from different angles.
* **PBR Textures** — **On** shows the textured result and **Off** the model you started from, in its own base colour. **Compare** puts the two side by side.
* **Show Normal Map** — on by default. Turn it off to see the model without its normal map.

On a scene, you can open any object in the viewer as soon as it finishes — you don't have to wait for the whole group.

> The web viewer is a preview. If something looks off in the viewer, download the maps and check them before assuming the result is wrong.

### Export options

Downloads need a paid plan or the trial. On the Free plan, a download button opens **Plans** instead. The 3D viewer works on every plan. See [Plans](https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md#plans).

Download a PBR result with **Download Textures** on its **Generate PBR Textures** node, the download button in the viewer, or **Download** in its close-up in the Library. You can download either:

* **Textures** — the individual PBR maps as **PNG** files: albedo, metallic, roughness, IOR and normal. A material made from an image also has displacement when you chose it.
* **3D model with embedded textures** — a single `.usdz` model with the textures baked in, ready to drop into your pipeline. It comes in a zip with a 256 × 256 thumbnail that USD asset browsers can show. Downloaded from the Library, the `.usdz` is named after the asset, for example `Office_Chair.usdz`.

A material made from an image offers **Textures** or **USD**: a sphere with your material and textures in a `.usdz` package. A displacement map comes connected, at a strength of 0.1. Older materials made from an image may offer **Textures** only. PBR results made before 12 October 2026 may not have a normal map, and nor may materials made from an image before 9 November 2026.

Before PBR, **Download 3D model** on a **Generate 3D Model** node, or **Download** in a 3D model card's menu, gives you the mesh as a `.glb` file. On a **3D Retexture** node, **Download 3D model** gives you the model in the format you gave it, `.glb` or `.usdz`.

### Simulation-ready USD

When PBR textures are made on a 3D model, Marso Studio also prepares a simulation-ready version of its `.usdz`. Once it's ready, it's the file that **3D model with embedded textures** gives you. On top of the model and its textures, it has:

* real-world size, in metres, with Z up
* a rigid body with an estimated mass
* a collider
* physics material values: density, friction and restitution
* semantic labels for what the object is and what it's made of

The result's card in your [Library](https://docs.m-xr.com/marso-studio/reference/library-and-collections.md#the-sim-ready-badge) shows **Enriching** while the file is being prepared and **Sim-ready** when it's done. A download made before then is the standard `.usdz`, so download it again once the badge shows. If no badge appears, the standard `.usdz` is the one you get.

The [Isaac Sim](https://docs.m-xr.com/marso-studio/integrations/isaac-sim.md) puts sim-ready assets straight onto an Isaac Sim stage.

### Exporting a scene

A scene exports as a set of individual assets, not as one merged mesh. Each object keeps its own material set, so you can place, swap and reuse them independently once they're in your DCC.

* **Every object:** **Download PBR group** on **Generate PBR Textures (Group)** offers the same choice, **Textures** or **3D model with embedded textures**, one `.usdz` per object. You get one zip with a folder per object, and each `.usdz` is named after its object, with its thumbnail.
* **One object:** **Download** in the object's card menu.
* **Earlier stages:** **Download selected 3D models** on **Generate 3D Models (Group)** and **Download selected reference images** on **Generate Reference Images (Group)** download the objects you've ticked.

Objects that didn't complete are skipped rather than exported empty, and if a file can't be fetched the app tells you how many it skipped. If part of a scene is missing from the download, check the group for failed objects and retry them. See [When some objects fail](https://docs.m-xr.com/marso-studio/reference/scene-generation.md#when-some-objects-fail).

> Scene downloads can be large. A scene with many objects packages every mesh and every map, so give it time and check you have the disk space before you start.


---

# 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/reference/previewing-and-exporting.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.
