> For the complete documentation index, see [llms.txt](https://docs.darcyiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darcyiq.com/core-features/artifacts/motion-videos.md).

# Motion Videos

Darcy Motion turns your own text, numbers, and charts into short animated videos you watch build scene by scene, then export as MP4.

**Darcy Motion** creates short animated videos: explainers, motion graphics, animated charts, logo stings, and all-hands segments. Darcy builds them in code from your own material, so every word, number, and timing can be changed by asking. You watch the video take shape in a live player, then export an MP4 when it's ready.

{% hint style="success" %}
**From report to video in one conversation**: "Turn this quarterly report into a 30-second video for the all-hands" gives you a scene-by-scene animation of your actual numbers, on brand, that you can review frame by frame and download as an MP4.
{% endhint %}

## What It's For

Motion Videos animate **your own material**: text, numbers, charts, diagrams, shapes, screenshots, logos, and images you provide.

| Good fit                                          | Not what it does                          |
| ------------------------------------------------- | ----------------------------------------- |
| Animated explainers that teach an idea in steps   | Generated live-action footage             |
| Launch and promo clips                            | AI-generated people or avatars            |
| Animated charts and key-metric reveals            | Narration or music you didn't supply      |
| Social clips (vertical) and presentation segments | Long-form video. Aim for 10 to 60 seconds |

## Creating a Motion Video

Ask Darcy in chat:

* "Make an animated explainer of how our onboarding works"
* "Turn these Q3 numbers into a 30-second motion graphic"
* "Animate this chart for the board deck"
* "Create a vertical social clip announcing the launch"

For a new video, Darcy first asks a few quick questions: what kind of video it is, who will watch it and how, how fast it should feel, and roughly how long it should run. Answer them, or tell her to just go ahead.

{% hint style="info" %}
**Motion Videos run on Darcy's cloud computer.** Darcy builds and renders the video in her [DarcyOS](/core-features/darcy-os.md) workspace, so a cloud computer needs to be available in the conversation.
{% endhint %}

## Watching It Build

Darcy plans the video as a list of scenes, then builds it two or three scenes at a time. The Motion Video artifact updates each time, so you watch it come together in the player:

* **Scene strip.** Every planned scene appears as a card with a short label. Built scenes show a thumbnail; click one to jump to it. Scenes still to come show as pending.
* **Player.** Play, pause, and scrub through the whole video. Changes Darcy makes show up immediately.
* **Full screen.** Expand the player to full screen for a proper look. Playback and comments keep working, and **Esc** exits.
* **Quality check.** Before handing off, Darcy runs a check covering layout, motion, and text contrast. If it fails, the artifact shows a badge with the summary.

Darcy plans for **reading speed**. Each scene holds long enough for its text to be read comfortably, and if the copy doesn't fit the length you asked for, she cuts words rather than speeding up the video, and tells you what she dropped.

## Requesting Changes

Ask for changes in chat: "make the title bigger", "swap scenes 2 and 3", "hold the revenue number for longer".

Or **click the player** to comment on the exact spot. Click a point, or drag to outline an area, type what should change, and choose **Send to Darcy**. Darcy gets the scene, the time, and the element you pointed at, and changes only that. If Darcy is still working, the comment waits until she finishes.

## Rendering and Downloading the MP4

The player is how you review the video. The MP4 is an export you ask for when it's ready.

{% stepper %}
{% step %}
**Click Render MP4** It's in the artifact toolbar, and it's enabled once every scene is built and Darcy has finished her current step.
{% endstep %}

{% step %}
**Watch the progress** The button shows a percentage and the current stage while the video renders on the cloud computer. Rendering can take a minute or more.
{% endstep %}

{% step %}
**Get the file** When the render finishes, the MP4 downloads automatically, and a **Download MP4** button stays on the artifact for later.
{% endstep %}
{% endstepper %}

After you change the video, the button becomes **Re-render**, and if the MP4 is older than the latest changes it says so. You can also ask in chat, for example "fix the title, then render it".

## Branding

Motion Videos follow your [Design Standards](/settings-and-configuration/design-md.md). When the video represents your company, Darcy uses the selected brand's colors, fonts, and logo. Pick a brand from the composer before you ask.

## Export Options

Motion Videos swap the usual copy, download, save, and share actions for render and MP4 actions.

| Option        | How                                                    |
| ------------- | ------------------------------------------------------ |
| **MP4 video** | **Render MP4**, then **Download MP4** from the toolbar |


---

# 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://docs.darcyiq.com/core-features/artifacts/motion-videos.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.