> 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/library-and-collections.md). # Library & collections Everything you upload to Marso Studio, and everything it generates for you, goes into your **Library**: images, reference images, multi-view sets, 3D models and PBR results. There's nothing to save by hand. Open it from **Library** in the left sidebar. Collections let you gather assets from any project into named sets of your own. ### Browsing your library The Library's home page starts with your **Collections** and your **Projects**, each with **View all**, and your assets below them. The assets open on your **PBR** results, newest first, grouped by when they were made. Open **Filters** to see the rest: * **All**, **PBR**, **3D** (models) or **2D** (images and multi-view sets) * **Favorites only**, for the assets you've starred You can also group the Library by **Time** or by **Project**, sort it **Newest** or **Oldest** first, change the size of the cards, and switch between a **Grid** of cards and a **List**. It remembers your choices in this browser. The left sidebar lists your **Collections** and **Projects**. The arrow beside one lists the assets in it, and clicking an asset opens it. Click a project to see only its assets, and click it again to see everything. With a project open, **Open project** takes you to its canvas and **Download** downloads its assets. Its menu has **Details**, to rename it, and **Delete**. ### Searching your library Search sits at the top of the Library, and at the top of the Library panel on the canvas. It always covers your whole library, whatever project or collection you have open. * **By text:** type what you're after in **Search library** and press Enter. * **By image:** **Search by image** finds assets that look like a picture of yours. Choose one, or drop it on the search bar: PNG, JPEG or WebP, up to 10 MB and 4,096 pixels a side. * **By asset:** **Search by a library asset** shows your newest assets, so you can pick one and find assets like it. **Find similar** in a card's menu, and **Similar** in an asset's close-up, do the same. Search finds 3D models that have had PBR textures made on them, and their PBR results. Images, and 3D models that have never been textured, don't appear in the results. Results come closest first, up to 20 at a time, and **Filters** don't apply to them. **Search settings**, on the search bar, sets how close a result has to be to show, with a **Text search threshold** and an **Image and asset search threshold**. While the settings are open, every result shows with its **Relevance**, and red marks the ones a threshold would leave out. The same settings are in **Settings → Preferences**, under **Library search**. ### An asset's close-up Click a card to open the asset: a large preview, with its information beside it. For a 3D asset, **View 3D** turns the preview into the 3D viewer, and you can go fullscreen. **Similar** finds assets like it: see [Searching your library](#searching-your-library). * **Details** — what the asset is, when it was made, its file size and, for a PBR result, its polygon count and dimensions. Once a PBR result is sim-ready, it also has a summary, a category and the materials it's made of. It shows which model generated the asset, and under **Project owner** the project it belongs to: click the project for **Open in node graph**, to find it on the canvas, or **Open in library**. * **Controls** — the viewer settings: lighting, the PBR comparison and more. See [Previewing & exporting](/marso-studio/reference/previewing-and-exporting.md). * **Share** — a public link to the asset. See [Sharing an asset](#sharing-an-asset). Below them, **Family** shows the asset's lineage as a tree: what it was made from and what was made from it, each asset under the one it came from. **Also in this project** shows the rest of its project. **Download** gives you the asset's file. For a PBR result it offers **Textures** or **3D model with embedded textures**, and the `.usdz` is named after the asset: an asset called Office Chair downloads as `Office_Chair.usdz`. A 3D model downloads as it is, without PBR textures, even once PBR textures have been made on it. Its close-up then shows *This model has no PBR textures*, and clicking it, *Open its PBR version*, opens the PBR result. Downloading needs a paid plan or the trial: see [Plans](/marso-studio/reference/credits-and-billing.md#plans). ### The Sim-ready badge When PBR textures are made on a 3D model, Marso Studio also prepares a simulation-ready version of its `.usdz`. The result's card shows **Enriching** while that's under way and **Sim-ready** once it's done. If no badge appears, the download is the standard `.usdz`. For what the sim-ready file contains, see [Simulation-ready USD](/marso-studio/reference/previewing-and-exporting.md#simulation-ready-usd). ### Collections A collection is a named set of assets from your library, from any project. An asset can be in as many collections as you like. Taking an asset out of a collection, or deleting a collection, never deletes the asset: it stays in your library. #### Making a collection Click **New collection** at the top of the Library, or the **+** beside **Collections** in the sidebar, and give it: * **Name** — required, up to 100 characters. * **Tags** — optional. Up to 20, each up to 32 characters. Separate several with commas. * **Header image** — optional. If you don't set one, the first asset you add provides it. **Details** in a collection's menu changes these later. There, the header can be an image you upload (**Upload header**, under 5 MB), one generated from the collection's first assets (**Generate**), or one of its assets (**Use an asset**). #### Adding assets * **From the Library:** tick the assets you want (the box appears when you hover a card, and Shift-click selects a range), then press **Add to collection** in the selection bar and pick a collection, or **New collection** to start one with them. * **From an asset's close-up:** its **Collections** section lists the collections it's in, and **Add to collection** adds it to another. * **With Manage:** choose **Manage** in a collection's menu, or at the top of an open collection. The collection opens beside your library and every card gets an **Add** button. Press **Done** when you've finished. * **From the canvas:** **Add to collection** on a **Generate Reference Images (Group)**, **Generate 3D Models (Group)** or **Generate PBR Textures (Group)** node adds every object in it. **Add to collection** in a card's menu adds just that one. A collection that already holds everything you've picked shows a tick, and picking it again takes them back out. An asset made a few moments ago may not have reached your library yet; the app tells you how many it couldn't add. #### Finding and managing collections Your collections are on the Library's home page and in the sidebar. Click one to open it. **View all** shows every collection, and you can filter them by **Tags** (a collection must have every tag you enter) and by the **Date** they were created or updated. A collection's menu has **Download**, **Manage**, **Details** and **Delete**, and an open collection has **Download** and **Manage** at the top. Deleting asks first, and the assets stay in your library. ### Using library assets on the canvas The toolbar on the left of the canvas has **Add**, which opens the add-node menu, **Library** and **Tidy**, which lays your nodes out neatly. **Library** opens your library over the canvas, on the project you're in. To see everything, click **Library** at the start of its breadcrumb. Add an asset to the project with the **+** on its card, or **Add to project** in its close-up. To add several, tick them and add them together from the selection bar, up to 25 at a time. * An image arrives as a **Load Image** node. * A 3D model arrives as a **Load 3D Model** node. Several assets arrive as separate nodes, side by side. PBR results and multi-view sets can't be added to a canvas. Assets go on the main canvas, so the **Library** button is greyed out while a sub-graph is open, such as a reference image's own canvas. Close it first. **View in library** opens a node's asset in its close-up, in the Library over your canvas. It's on the toolbar of the image nodes and of **Load 3D Model**, **Generate 3D Model** and **Edit 3D Model**, which open it with the 3D viewer up, and in the menu of a reference image's card. On **Generate PBR Textures**, and in the menu of a 3D model or PBR card, it's **View 3D**. To try Marso Studio on one of our assets instead of your own, use **Example Assets** in an empty **Load 3D Model** node. See [Sourcing & preparing assets](/marso-studio/preparing-your-assets/sourcing-and-preparing-assets.md). ### Sharing an asset You can share a 3D asset with anyone through a link. In its close-up, open **Share** and press **Create share link**. Anyone with the link can open the asset in their browser, with no account needed. Copy the link, or post it with **Share on X** or **Share on LinkedIn**. **Stop sharing** turns the link off, and anyone who has it loses access. ### Through the API The Marso Studio API reads your library and manages collections too. See [Library](https://docs.m-xr.com/marso-studio-api/getting-started/library) and [Collections](https://docs.m-xr.com/marso-studio-api/api/collections) in the Marso Studio API docs. --- # 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/library-and-collections.md?ask=&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.