> ## Documentation Index
> Fetch the complete documentation index at: https://support.myapps.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# CamView

> Block shots in 3D and use your phone as a camera

**CamView** lets you set up a shot in 3D before generating it. Place objects and figures, position cameras, keyframe movement — then generate from a camera angle you actually chose rather than one you hoped a prompt would imply.

## Why it exists

Prompting a specific camera angle is unreliable. "Low angle, subject to the left, camera pushing in" is a sentence a model may or may not honor. CamView makes it geometry instead of a description.

## What you work with

| Piece                 | What it's for                            |
| --------------------- | ---------------------------------------- |
| **Objects & figures** | Blocking — what's in the scene and where |
| **Mannequin**         | Pose a figure to define body position    |
| **Cameras**           | Where the shot is taken from             |
| **Keyframes**         | Camera and figure movement over time     |
| **Timeline**          | Sequence the keyframes                   |
| **Shots gallery**     | Shots you've set up in the scene         |
| **Environment**       | The surrounding context                  |
| **Templates**         | Start from a prepared scene              |
| **Coach**             | Guidance while setting up                |

## Setting up a shot

<Steps>
  <Step title="Block the scene">
    Add objects and figures and place them. Pose the mannequin if body position matters.
  </Step>

  <Step title="Place the camera">
    Move to the view you want and set the camera there. You can also aim the camera at a selected object.
  </Step>

  <Step title="Keyframe movement">
    Add camera keyframes for a move; keyframe figures for animation. Sequence them on the timeline.
  </Step>

  <Step title="Render">
    Generate from the scene. The result becomes a normal Pixio generation.
  </Step>
</Steps>

## Phone as camera (VCam)

VCam turns your phone into the camera with a **live viewfinder** — move the phone and the shot moves. Physical framing instead of dragging a 3D camera with a mouse. Connect via the VCam option in CamView.

<Info>
  VCam controller pairing and live sensor streaming are app-only — they can't be driven through the API. Scene documents themselves are scriptable.
</Info>

## Saving

Scenes are documents, saved as you work.

* Leaving with unsaved changes prompts you first
* If a scene changed elsewhere, reload before saving so you don't overwrite the newer version
* **Reset** clears objects, cameras, and keyframes — your last save is kept
* **Clear** removes objects and figures but keeps cameras and keyframes

<Warning>
  Reset and Clear differ in an important way: Clear preserves your camera work, Reset doesn't. If you've spent time on camera moves, use Clear.
</Warning>

## Credits

Blocking, posing, camera work, and keyframing are free — you're arranging a scene, not generating. Credits are spent when you render.

<Tip>
  That's the whole economic argument for CamView: iterate on framing for free, then pay once for the shot you chose.
</Tip>

## Where it fits

* **[Cinema Studio](/create/cinema-studio)** — plan the sequence of shots; VCam and keyframed cameras appear there too
* **[Video Agent](/create/video-agent)** — generate a full episode
* **[Generate](/generate)** — a single clip, prompt-driven