> 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/compose/camera-controls.md).

# Camera controls

Free cam, fine-tune, game-controller support. Two camera-control modes per shot.

The Compose-mode camera has two control modes – free cam and fine-tune – plus optional game-controller support. Free cam is for getting roughly there; fine-tune is for nailing the framing.

## Watch

<https://www.youtube.com/watch?v=BbS5ml0Uzx4>

![Compose mode with the satellite view on: the main viewport shows the orbital view with the camera frustum drawn in, and the picture-in-picture in the top-left shows what the camera sees](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-cd799559190d9554bd6e4cacf4ae4696781f7b0e%2Fpip-overview-01.png?alt=media)

## What it does

A previs DP needs two kinds of camera moves: get from "I have no idea where I am" to "I'm roughly looking at the action" in three seconds (free cam), and then nudge that framing by single-degree increments until it's right (fine-tune). Stuffing both into one control mode means one of them feels broken. Compose mode separates them into two explicit states with a toggle in the bottom-left.

## How to use it

The mode toggle sits in the bottom-left of the Compose viewport.

1. **Free cam.** Click the free-cam icon. Drag to rotate; Shift+drag to pan or elevate; scroll to zoom. Same bindings as Build mode. Use this when you're hunting for an angle.
2. **Fine-tune.** Click the fine-tune icon. Drag the on-screen rosette handles for incremental dolly, truck, pedestal, pan, tilt, and roll. Use this when the angle is roughly right and you need to land it precisely.
3. **Frame an object.** Select the object in the scene outliner or in the overhead satellite view, then press `F`. The camera moves to fill the frame with the object. Faster than dragging when you need to start from a known good angle. You can't select objects inside the picture-in-picture inset itself; select in the outliner or the satellite view.
4. **Picture-in-picture.** Click the button in the top-left of the Compose viewport to toggle the satellite view. The main viewport swaps to an orbital "God's-eye" view of the scene with the camera frustum drawn in, while the picture-in-picture inset shows what the camera sees. Click the button again to return to the through-the-lens view. Useful when you need to see where the camera sits in the world while you adjust. In Build, double-click a shot's picture-in-picture to jump to Compose, looking through that shot's camera.
5. **Game controller.** Plug in an Xbox or PlayStation controller and the left stick maps to translation, right stick to look, shoulder buttons to elevation. Better for long crane moves or for users who set up shots while standing.

### The camera settings panel

The camera settings panel appears in both Build and Compose, and is the quickest route to most of the above. **Show Camera Settings** opens it. In Build it behaves like the navigation tips panel and can be collapsed; its buttons stay hidden until you hover. In Compose it sits with the shot gate.

It carries four things.

**Navigation Mode.** A dropdown with **Orbit Controls** and **Freelook Controls**, plus a third entry, **Camera Controls**, when you are inside a shot. Outside a shot the dropdown has two entries, not three. This is the same choice as the bottom-left toggle described above, in one place with the rest of the camera settings.

![The Camera Settings panel with the Navigation Mode dropdown open, showing Orbit Controls ticked and Freelook Controls below it](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-b8e6853855ebaf96ef9db9e5f5b59b9718df6e2c%2Fcamera-settings-panel-01.png?alt=media)

That capture was taken in Build, outside a shot, so its dropdown shows the two-entry form.

**Framing.** **Frame Selected** (`F`), **Frame All**, and **Move Camera Inside** (`G`). Frame All is unavailable while you are in Pose Edit Mode.

**Set Orbit Point.** Picks the point the camera orbits around, rather than orbiting whatever the app last decided on.

**An axis gizmo.** Click an axis to snap the camera square onto it, for a clean front, side or top view. While you are editing a camera, clicking an axis also switches to an orthographic view, which is what you want when you are laying out a set and perspective is getting in the way.

![Inside a shot in Compose, the Navigation mode menu has three entries: Orbit Controls (ticked), Freelook Controls and Camera Controls](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-a9558c0b47d8f559490f870d337b618238491c4c%2Fcamera-settings-in-shot-01.png?alt=media)

### Hide guides you don't need

Dense scenes fill up with group markers and motion paths. The **UI Visibility** panel, just above Camera Settings at the bottom left of Build and Compose, hides them. Click the eye (**Show UI Visibility**) to open it, then click a toggle: **Groups**, **Motion Paths** or **Relationship Lines**. A filled button is shown; an outline is hidden. **Groups** and **Relationship Lines** start hidden and **Motion Paths** starts shown.

Hidden groups and motion paths still appear when you select them or something related to them. Your choice is remembered in this browser for every project.

![The UI Visibility panel at the bottom left of Build, at its defaults: Groups and Relationship Lines in outline (hidden), Motion Paths filled (shown), above the Camera Settings button](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-53ae571b8a6f7322543fd4f19f05b33093ca0e20%2Fui-visibility-01.png?alt=media)

### When to use which

| You want to...                            | Use                                        |
| ----------------------------------------- | ------------------------------------------ |
| Find a rough angle on a moving subject    | Free cam                                   |
| Place a static establishing shot          | Fine-tune                                  |
| Match a specific framing from a reference | Fine-tune                                  |
| Sweep across a large scene to scout       | Free cam (or controller)                   |
| Get into someone's POV                    | Frame the subject, then fine-tune to nudge |

## Details

| Control | Free cam                 | Fine-tune                |
| ------- | ------------------------ | ------------------------ |
| Rotate  | Drag                     | Pan rosette handle       |
| Pan     | `Shift` + drag           | Dolly + truck handles    |
| Elevate | `Shift` + drag           | Pedestal handle          |
| Roll    | n/a                      | Roll handle              |
| Speed   | Tied to scroll-zoom rate | Fixed-increment per drag |

## Limits and known issues

* **Free cam can drift through walls.** It doesn't collide with scene geometry. If you're looking through a building exterior, you didn't crash – you're inside.
* **Fine-tune is slower for big moves.** Don't use it to cross the scene; that's free cam's job.
* **The mode switcher quietly affects the viewport.** Switching to Build or Visualize while a shot is active swaps you back to that mode's camera; your shot's framing is preserved when you return.

## Related

* [Shots](https://help.intangible.ai/compose/shots.md)
* [Lenses](https://help.intangible.ai/compose/lenses.md)
* [Aim Camera and Target](https://help.intangible.ai/compose/aim-camera-and-target.md)
* [Move the camera (in Build mode)](https://help.intangible.ai/get-started/take-control/viewport-navigation.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/compose/camera-controls.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.
