> 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/learn-more/concepts/projects-and-scenes.md).

# Projects, scenes and shots

How projects, scenes, and shots nest. Three nouns, three different jobs.

A project is the top-level container for a piece of work. A scene is a 3D space inside the project. A shot is a camera framing of that space at a moment in time. Three nouns, three different jobs.

## Why it exists

Real productions have all three concepts already. A commercial is a project. The kitchen interior and the parking-lot exterior are scenes. The over-the-shoulder reaction and the wide establishing are shots. The nesting is what lets a director say "let's reuse the parking-lot scene from the last spot" without it meaning the same camera angles.

Intangible mirrors that nesting. The thing that catches a new user is that **scenes** in Intangible are spatial – they're sets, locations, environments – not narrative beats. If you're coming from Premiere or Final Cut, the word "scene" carries a different meaning; here it's closer to "set" or "location" in the production-design sense.

## What it looks like in the product

You create a project on Home: type a prompt and create it, or click **New Project** to start from an empty canvas. On the canvas, each scene is a group in the Storyboard. Inside a mode, the current scene's name sits at the top left, under the project's file name; click it to open the scene switcher, where you switch between scenes or create a new one.

![The scene switcher open under the project's file name, listing 2 Scenes with a + for a new one: Manhattan city street with 2 shots, and Scene 1 with none](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-b561039ffe648a5909512e46ca9244ea6ad5cd56%2Fscene-switcher-40px-01.png?alt=media)

A scene is a 3D environment with its own assets, populators, environment settings, and lighting. Switching scenes switches the entire 3D viewport content. A project can hold as many scenes as the work needs – think of a commercial spot with three locations as three scenes.

A shot belongs to a scene. The agents add shots for you on the canvas. To add one yourself, use **Add shot** on the scene card, or the camera **+** below the viewport in Compose (see [Shots](https://help.intangible.ai/compose/shots.md)). Each shot has its own camera and lens, and covers a window of the scene timeline.

## How it connects to the rest

* **Projects** are what get shared. The email-share flow ([Sharing and collaboration](https://help.intangible.ai/learn-more/reference/sharing-and-collaboration.md)) shares the whole project, not a scene.
* **Scenes** are where Build mode lives. Sun position, populators, asset placements, the scene outliner – all per-scene.
* **Shots** are where Compose mode lives. A shot binds its camera to one scene; you can't have a shot that crosses scenes (that's an edit, and edits live in the [Sequence Timeline](https://help.intangible.ai/compose/timeline.md)).
* **The auto-prompt** assembles its scene context from the active scene plus the active shot's camera. Switch scenes and the prompt rebuilds.

## When to reach for it

The signal is what's changing in your story. New environment? New scene. Same environment, new angle? New shot. New project? You've changed what you're making.

One sequencing thing worth knowing: name your scenes and your shots. The auto-prompt feeds those names into the model when it constructs the prompt – "the Lamborghini in the Manhattan city street scene" is more useful than "the Lamborghini in scene-2".

## Related

* [How Intangible works](https://help.intangible.ai/learn-more/concepts/how-intangible-works.md)
* [Shots](https://help.intangible.ai/compose/shots.md)
* [Animation and shot time](https://help.intangible.ai/learn-more/concepts/animation-and-shot-time.md)
* [Sharing and collaboration](https://help.intangible.ai/learn-more/reference/sharing-and-collaboration.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/learn-more/concepts/projects-and-scenes.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.
