> 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/overview/get-started/viewport-navigation.md).

# Move the camera

After this you'll be moving the camera around the scene like you've worked in 3D before. The viewport is where you'll spend most of your time, and the controls are not what your hands are going to guess if you came from Blender, Maya, or Unreal. Sort it out now and the rest of Build mode falls into place.

![Empty Compose-mode shot with the orbit / pan / zoom gesture overlay visible as dotted arcs during the drag motion](/files/neWNV5tsQJu8cES6Cov6)

## What's getting in the way

The mental model trips people first. Your 3D viewport is not a camera – it's the space you move yourself around in to build. The **shot cameras** you place later in Compose mode are the ones that get rendered; you snap in and out of those. Moving around in Build mode is just repositioning your own view of the scene, not setting up a shot.

The controls lean on cinematographer verbs rather than a DCC's mouse conventions: you orbit, pan, dolly, strafe, and boom. Once that clicks, the rest of Build mode falls into place.

Direct quote from the user-testing notes that captures the early friction: *"Moving the camera felt like a chore."* It stops feeling that way once the bindings below are in your hands.

## How to do it

For the scene camera in Build mode:

1. **Orbit.** Left-click and drag.
2. **Pan.** Hold `Shift` and left-click-drag.
3. **Dolly in and out.** Scroll the wheel, or use `W` / `S` (the up / down arrows do the same).
4. **Strafe and boom.** `A` / `D` strafe the camera left and right; `Q` / `E` boom it up and down.
5. **Frame an object.** Click the object, then press `F`. The camera moves to fill the frame with it. Use this any time you've drifted off and lost the scene.

For larger sets – a city populator, a tropical-forest populator, anywhere you're navigating across hundreds of meters – speed the camera up with the `,` and `.` keys. The default speed is tuned for a single set the size of a living room and feels slow on bigger environments.

The full binding list lives in [Keyboard shortcuts](/overview/reference/keyboard-shortcuts.md), or open the in-app shortcuts panel from the help icon in the top-right.

## Common mistakes

* **Reaching for another DCC's bindings.** If orbit isn't responding, you're probably right-click-dragging out of Blender habit – orbit is a plain left-click-drag here. Pan is `Shift` + left-click-drag.
* **Fighting a slow camera on a big set.** The camera feels syrupy across a large environment until you bump the speed with `,` and `.`.

## Related

* [The three modes](/overview/concepts/the-three-modes.md)
* [Compose mode camera controls](/compose/camera-controls.md)
* [Keyboard shortcuts](/overview/reference/keyboard-shortcuts.md)
* [Working with objects](/build/working-with-objects.md) – the next step once you can move the camera.
* [Selection and grouping](/build/selection-and-grouping.md) – multi-select once you have things to select.
* [Build mode](/build/build.md) – the section landing page for the rest of the art-department workflow.


---

# 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://help.intangible.ai/overview/get-started/viewport-navigation.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.