> 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.

### The 3D viewer

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

* **Multiple HDRIs** — switch between lighting environments to see how the materials respond.
* **Rotate the lighting** — spin the environment to catch reflections and highlights from different angles.
* **Show albedo** — view the base colour with the materials stripped back.
* **Compare PBR vs non-PBR** — toggle between the original asset and the textured result.

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 still being refined during early access. If something looks off in the viewer, download the maps and check them before assuming the result is wrong.

### Export options

You can download either:

* **Textures only** — the individual PBR maps as **PNG** files (albedo, metallic, roughness, IOR).
* **3D mesh with embedded textures** — the full asset with its materials packed in, ready to drop into your pipeline. Files will be output as a USD file.

### 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.

You can download:

* **The whole scene** — every completed object in one download.
* **A single object** — any individual asset on its own.
* **Textures only** — the PBR maps for the objects you select, without the meshes.

Objects that didn't complete are skipped rather than exported empty. If part of a scene is missing from the download, check the group for failed objects and retry them — see [Working with scene results](/marso-studio/scenes/working-with-scene-results.md).

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