> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/canvas/groups-and-cards.md).

# Groups and cards

How the canvas is laid out: groups of cards for your uploads, references, scenes, shots and renders, what each card's toolbar does, and how to move around.

Everything in a project lives on the canvas as a card, and cards sit in groups. The layout reads left to right the way a project moves: what you brought, what was made from it, and what came out.

![The canvas of a finished project zoomed out, left to right: Sources, Groups (Blue Bugatti Veyron, Attack Drone, NYC Avenue), Storyboard and Visualizations](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-8bf641f34c4b1f62de1ea8ae6789890912d87a81%2Fcanvas-groups-01.png?alt=media)

## The groups

| Group              | What is in it                                                                                                                                                                                        |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Brief**          | The plan the agents write for the project. See [The brief](https://help.intangible.ai/canvas/the-brief.md)                                                                                           |
| **Sources**        | Images, files, 3D models and worlds you added or generated that are not in a group yet. Images you add on Home or in the chat land here first. The **Sources** title shows once the column has cards |
| **Groups**         | Named media groups, such as references for one subject. The agents make these when they sort your images; you can make your own                                                                      |
| **Storyboard**     | One group per scene, holding the scene card and its shot cards                                                                                                                                       |
| **Visualizations** | Every image and video rendered from your shots, newest first. Select a scene or shot card and it narrows to that scene's or shot's renders                                                           |
| Asset pack groups  | One per pack, titled with the pack's name, if you made any. See [Asset packs](https://help.intangible.ai/canvas/asset-packs.md)                                                                      |

Double-click a scene or media group's title to rename it. A card for a grouped 3D object shows a collage of the models in it.

A group works like a folder one level deep: it holds cards, not other groups.

### Narrow and size Visualizations

Select a scene card and Visualizations shows only that scene's renders; select a shot card and it shows only that shot's. The group title and its search follow along. Clicking one of those renders keeps the view narrowed. Click the scene or shot card again, select another card, or click the empty canvas to see everything.

The arrows beside the Visualizations grid add or remove a column, from three to seven. The count is remembered for you, across projects and devices.

## Cards

Cards stay quiet until you need them. At rest a card shows its type icon. Hover it and a chip shows its name, or **Untitled** if it has none, and a little more, such as a shot's or video's duration. Click it to select it: it gets a white outline and a toolbar.

Every render and generation is named as soon as its card appears, and the chip, the details panel, the chat and the download all use that name. A render from Visualize is named after its scene and shot with a version number, such as `Street · Hero · V3`, or `Scene 1 · Shot 1 · V3` while they keep their default names; a shot's images and videos share one count. An image or video generated on the canvas is `Image 4` or `Video 2`, counted across the project. Uploads keep their file name. Rename a card in the details panel or ask the chat, and the new name shows everywhere.

To heart an image, video, 3D model or world card, hover it and click the heart in its lower right. The heart stays filled when you move away; click it again to take it off. It is the same heart as a render's in Visualize, so a render hearted in either place shows hearted in both, and a collaborator's hearts show up too. Scene, shot and group cards, style presets, cards inside an asset pack, and cards still rendering or failed have no heart.

Each kind of card has its own toolbar:

| Card                                  | Toolbar                                                                                                                                      |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Scene**                             | Edit in Build · Add shot · Batch visualize · Details · Delete                                                                                |
| **Shot**                              | Edit in Compose · Visualize · Details · Delete                                                                                               |
| **Image or video render**             | Edit in Visualize · Edit image (or Edit video) · Group · Details · Download · Delete                                                         |
| **Uploaded image or reference sheet** | Edit image · Group · Details · Download · Delete                                                                                             |
| **Media group**                       | Generate into group (+) · Upload into group · Add from media library into group · Download group · Delete group                              |
| **3D model**                          | Edit · Details (on a model placed in a scene) · Download · Delete                                                                            |
| **World**                             | Edit · Details · Download · Delete                                                                                                           |
| **Style preset**                      | Edit · Delete                                                                                                                                |
| **Failed image or video**             | Retry (when the request can be sent again) · Delete                                                                                          |
| **Asset pack**                        | Delete asset pack, with Generate and Download in the pack card's header. See [Asset packs](https://help.intangible.ai/canvas/asset-packs.md) |

**Details** shows the card's name and description in place of the toolbar. On a 3D model placed in a scene, **Details** (its tooltip reads **Edit Model Details**) also holds its reference images: pick image cards with **Select from Canvas** (click the cards, then the tick; a render you pick is copied into Sources), add them from the **Media Library**, upload or paste them, or click **Generate Reference Sheet**, and remove one with the × on its thumbnail. These are the same references the object carries in Build. Removing a model's last reference takes its card off the canvas; the model stays in the scene. On a 3D model card, **Edit** opens the asset library at that model's category so you can swap it. A 3D model card shows the model itself; its reference images each have their own card. **Edit in** opens the card in that mode, so you can go from a scene card straight into Build to change the set. **Group** puts the card in a new group: a card in **Sources** moves there, and a render picked from Visualizations is copied, so the original stays where it was. See [Batch visualize](https://help.intangible.ai/canvas/batch-visualize.md) and [Edit media](https://help.intangible.ai/canvas/edit-media.md).

A shot card's **Visualize** panel makes images only. For video, see [Keyframes to video](https://help.intangible.ai/canvas/keyframes-to-video.md).

## While a card renders

While an image or video renders, its card shows an animated cube of dots and a label with the card's name and the time since the job started, for example `shot 04 · 12s`. Past a minute the time reads like `1:05`. A rendering card can't be selected and has no toolbar, so you keep working around it.

When the render is ready, the dots gather into the picture and the image fades in over them, which takes about four seconds. Then the card works like any other, with its toolbar.

If a render fails, its card reads **Didn't finish**. Click **Retry** on the card to send the same request again. Retry shows when the original request was saved, as it is for an image or video made with **Generate**. Select the failed card for **Retry** and **Delete** in its toolbar.

With **Reduce motion** set to **Enabled** in Settings > General, every rendering card holds a still cube, and the image fades in when it is ready. On **System**, the canvas follows your computer's setting. See [Account](https://help.intangible.ai/learn-more/reference/account.md).

![An image card rendering in a media group: the point cube with the card's name and the seconds elapsed](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-51aabcd13a6a2f6a886af0deadadaeb287600c05%2Fcanvas-card-rendering-01.png?alt=media)

![Visualizations with a failed card reading Didn't finish beside two finished renders](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-09a631678611cf551b9def1dd886d8ea72ab379c%2Fcanvas-card-failed-01.png?alt=media)

## Delete a card

Deleting a shot, or a scene that has anything in it, asks you to confirm first (**Delete shot**, **Delete scene**). **Delete group** asks too, and does not delete the items inside it.

A 3D model or world can sit on the canvas in two ways, and the two cards look the same. One is the library asset, such as a model or world you made with **Generate** in the bottom toolbar. The other is that asset placed as an object in a scene. **Delete** asks a different question for each, so read the dialog title before you confirm.

| Card                                | Dialog                      | What Delete does                                                                                                                                            |
| ----------------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Library 3D model or world           | **Delete from project?**    | Removes that one card from this project. The asset stays in your team's library, keeps showing in the team's other projects, and you can add it again later |
| 3D model or world placed in a scene | **Remove from this scene?** | Removes that one object from the scene. The library asset stays available                                                                                   |
| Style preset                        | **Delete from library?**    | Deletes the preset itself. It is removed for every project that uses it, and this can't be undone                                                           |

Deleting a library card removes only the card you selected; other cards for the same asset stay. On a 3D model, the toolbar gives one more clue: only a model placed in a scene has **Details**.

{% hint style="warning" %}
**Delete from library?** on a style preset deletes it for your team in every project that uses it, not just on this canvas. It can't be undone.
{% endhint %}

**Delete** is off on an object that is locked in its scene. Unlock it in Build first. See [Working with objects](https://help.intangible.ai/build/working-with-objects.md).

![The Delete from project? dialog a library 3D model or world card asks: it removes the card from this project, and the asset stays in your team's library so you can add it again later. Cancel and Confirm](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-49e3941ce296a95cab02d2818ecb5c631b3e6978%2Fcanvas-delete-from-project-01.png?alt=media)

![The Remove from this scene? dialog: it removes the object from this scene and the library asset stays available. Cancel and Confirm](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-2f5f38804a785e4980107929a66a614d6550ac81%2Fcanvas-remove-from-scene-01.png?alt=media)

![The Delete from library? dialog a style preset asks: it deletes the library asset, not a copy on the canvas, removes it for every project that uses it, and can't be undone. Cancel and Confirm](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-ed399e623d2c6c99b6a4a35ce304f13e2b3b7459%2Fcanvas-delete-library-01.png?alt=media)

## Upload into a group and download a group

* **Upload into group** adds files from your computer straight into that group: images, videos, 3D models and splats.
* **Download group** saves the group's media. One card downloads as a plain file; more than one downloads as a ZIP named after the project and the group. A file takes the name the card shows, after the project name, such as `my-project_street_hero_V2.png` for the render named `Street · Hero · V2` or `my-project_image-4.png` for a canvas image. It covers media cards only, so a group's other cards stay out of the file.
* **Download** on a single render, 3D model or world saves that one file. A world downloads as the splat file it was stored as.

To hand over renders, references and models as one ZIP, make an [asset pack](https://help.intangible.ai/canvas/asset-packs.md) and drag them onto it.

## See where a card came from

Click a card and everything outside its lineage dims. Click a render and you see the shot it came from, the scene that shot belongs to, and the style preset it used. Click a scene and you see its shots, its objects with their reference images, and its renders.

## Look closer

Double-click an image or video card to open it full size over the canvas. A video plays there, with its controls; cards themselves do not play. Press **Esc**, click outside it, or click the close button to go back.

To skim a video on the card itself, see [Keyframes to video](https://help.intangible.ai/canvas/keyframes-to-video.md).

## Move renders around

Renders stay in their group, but you can drag one out into **Sources** or any media group. That makes a copy; renaming, regrouping or deleting the copy leaves the original alone. You cannot drop cards into Visualizations.

## Reorder Storyboard scenes

Storyboard scenes run top to bottom. When the order is wrong, move a scene:

1. **Press the scene's name**, or the empty area around its cards.
2. **Drag it up or down.** The other scenes slide aside to show where it will land.
3. **Drop it between two scenes.** Press **Esc** before you let go to cancel.

The scene keeps its name, and the move can be undone. Pressing a card inside the scene still moves only that card.

Only editors and owners can reorder. For a viewer, dragging a scene pans the board as before. For an editor, dragging a scene's empty area now reorders instead of panning; hold **Space** and drag to pan from there.

## Move around the canvas

* **Opening view.** The first time you open a project in a session, the canvas centers on the **Storyboard**, at a zoom that fits every group. Once you pan, the canvas keeps your view for the rest of the session. A project with no storyboard opens with its groups at the top of the screen.
* **Zoom** by scrolling, or pinch on a trackpad. Zoomed far out, card details hide and group titles stay.
* **Pan** by dragging the empty canvas, a column title such as **Storyboard**, or the empty inside of a group (except a Storyboard scene, which an editor [drags to reorder](#reorder-storyboard-scenes)). Anywhere on the board, including over a card, drag with the right or middle mouse button, or hold **Space** and drag; the cursor turns to a grab hand while **Space** is down.
* **Switch modes** with the mode switcher at the top, which names the mode you're in, or press **0** for the canvas and **1**, **2**, **3** for Build, Compose and Visualize.

## Add to the canvas

The toolbar at the bottom of the canvas adds things: a new empty group, a new scene, generated media, 3D models and worlds, uploads from your computer, media from your library, and an asset pack. See [Create on the canvas](https://help.intangible.ai/canvas/create-on-the-canvas.md).

## Related

* [The canvas](https://help.intangible.ai/canvas/canvas.md)
* [The brief](https://help.intangible.ai/canvas/the-brief.md)
* [What Intangible agents build](https://help.intangible.ai/canvas/what-intangible-agents-build.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/canvas/groups-and-cards.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.
