> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/models/video-models/seedance-by-bytedance.md).

# Seedance (by Bytedance)

### **Overview**

ByteDance's video family. **Seedance 2.5** is the current flagship (text, image, and reference-to-video with audio). **2.0** / **2.0 Fast** / **2.0 Mini** sit below it. **1.5 Pro** and **1.0 Pro** remain available for cheaper or shorter clips.

***

### **Quick facts**

* **Modes:** Text → Video · Image → Video · Reference → Video (2.0 / 2.5).
* **Default clip length:** 5 seconds (2.5 goes longer; 1.x is 3s–12s)
* **Aspect ratios:** 21:9, 16:9, 4:3, 1:1, 3:4, 9:16
* **Training / licensing:** Proprietary model by Bytedance, licensed for commercial use within FLORA

***

### **What it’s great for**

* Multi-shot narrative sequences and longer-form short clips.
* High-coherence motion and smooth playback.
* Storytelling use cases requiring multiple shots.

***

#### **Copy-and-paste prompts**

```
Three-shot sequence: establish city skyline, mid shot of protagonist walking, close-up face — cinematic pacing — 10s total
```

```
Image→Video: animate product spin across three cuts, consistent lighting and reflections
```

```
Single-shot 1080p: slow crane up from street to rooftop, ambient city ambience
```

***

### **Parameters**

| Name           | Type   | Default | Notes                                        |
| -------------- | ------ | ------- | -------------------------------------------- |
| `Prompt`       | Text   | —       | Required                                     |
| `Duration`     | Select | 10s     | 3s–12s options (higher values increase cost) |
| `Resolution`   | Select | 1080p   | 480p, 720p, 1080p                            |
| `Seed`         | Seed   | Random  | Optional                                     |
| `Fixed Camera` | Select | No      | Yes, No                                      |

***

### **Modes**

| Mode                      | Estimated time | Required inputs | Typical use                    |
| ------------------------- | -------------- | --------------- | ------------------------------ |
| Text → Video (multi-shot) | \~2 minutes    | Prompt          | Narrative multi-shot sequences |
| Image → Video             | \~2 minutes    | Image, Prompt   | Animate assets across shots    |

***

### **Output options**

| Option     | Values / notes                            |
| ---------- | ----------------------------------------- |
| Resolution | 1280×720, 1920×1080                       |
| Duration   | 3s, 4s, 5s, 6s, 7s, 8s, 9s, 10s, 11s, 12s |
| Formats    | MP4 (H.264 + AAC)                         |
| Notes      | Designed for narrative and smooth motion  |

***

### **Prompt tips**

* Break multi-shot intent into clear shot descriptions (shot 1:, shot 2:, shot 3:).
* Use pacing terms like “slow”, “cut-to”, “dolly”, and exact durations.

***


---

# 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.flora.ai/models/video-models/seedance-by-bytedance.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.
