> 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/publish/scene-to-video.md).

# Scene to video

Export the greybox animatic from the Scene Timeline as a video. Useful for blocking review and structural sign-off before any renders are produced.

Export the greybox animatic from the [Scene Timeline](https://help.intangible.ai/compose/timeline.md) as a video file. The output is the 3D scene's blocking played out across the timeline – the structural framing of every shot, captured as motion, before any AI rendering happens.

{% hint style="info" %}
Three adjacent paths exist for non-AI or wireframe video exports. Pick by scope:

* **Scene to video** (this page) – per-scene animatic from the Scene Timeline in Compose.
* [**Direct Render**](https://help.intangible.ai/visualize/direct-render.md) – per-shot wireframe, Visualize mode. The same job as Compose's [Export Render](https://help.intangible.ai/publish/export-video.md#compose-mode-wireframe-export-render); different surface.
* [**Scene Videos**](https://help.intangible.ai/publish/export-video.md#how-to-export-a-whole-scene) – per-scene cut of the AI-rendered videos, Visualize mode. Generative, not wireframe.
  {% endhint %}

![A greybox animatic playing from Compose's Sequence tab: the playhead runs through the Animatic scene's Wide, Arc and Car pass shots, and the viewfinder cuts between their cameras as the car drives up the street](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-de9543d30a64ed12bd6a2531cbf992a50e552f75%2Fexport-scenes-01.gif?alt=media)

## What it does

Before any AI rendering, the Scene Timeline already contains the blocking: camera framings, lens choices, shot lengths, animated subjects and cameras. Scene to video captures that animatic as a video file – useful for reviewing the structural cut, sharing blocking with a director, or producing a low-cost preview before committing to AI render credits.

## How to use it

1. **Switch to Compose mode** and open the Scene Timeline.
2. **Open the scene-to-video export action** from the scene's controls.
3. **The job runs** and the output is a video of the greybox animatic across the scene's shots in their authored order.
4. **The file downloads automatically** to your local download directory when complete. H.264 30fps MP4.

## When to reach for it

* **Blocking review.** Walk a director or producer through the structural cut before committing to renders.
* **Pre-render preview.** Confirm the sequence reads at all before spending credits on Visualize.
* **Reference handoff.** Hand a downstream artist a video of the blocking they can match their work against.

When not to reach for it:

* **Final delivery.** The greybox animatic isn't a rendered shot. For finished output, render each shot in Visualize and use [Export Video](https://help.intangible.ai/publish/export-video.md) or [Export shot video](https://help.intangible.ai/publish/export-shot-video.md).
* **The 3D scene itself.** If the downstream tool needs the 3D geometry, use [Export formats](https://help.intangible.ai/publish/export-formats.md) for GLTF or USD instead.

## Limits and known issues

* **No transitions, no audio.** The animatic is a structural pass; there's no per-shot audio and no cross-shot mixing.
* **No format choice.** H.264 30fps MP4.

## Related

* [Export Video](https://help.intangible.ai/publish/export-video.md)
* [Export shot video](https://help.intangible.ai/publish/export-shot-video.md)
* [Export formats](https://help.intangible.ai/publish/export-formats.md): for 3D scene exports (GLTF, USD).
* [Timeline](https://help.intangible.ai/compose/timeline.md)
* [Publish tab](https://help.intangible.ai/publish/publish-tab.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/publish/scene-to-video.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.
