Skip to main content

Seedance Video Workflows

Seedance is a video model family in Redbit’s current registry. In the dashboard, Seedance-specific controls appear when the active card is a video card and the selected model is seedance or a doubao-seedance-2.0* variant. Seedance workflow diagram showing prompt input, four reference modes, validation, and provider output.

Who Should Read This

Read this page when a workflow needs Seedance-specific reference roles, when video generation is slow or failing, or when you need to decide whether a reference image, first/last-frame setup, or multi-reference setup is appropriate.

Before You Read

Confirm provider access in Models and Provider Configuration. Seedance requests may go through direct provider settings or a compatible relay, and generation can be slower than image generation because the provider may queue, poll, and post-process video jobs.

Current Variants and Output Settings

SettingCurrent values in the codebase
Model IDseedance
Variantsdoubao-seedance-2.0, doubao-seedance-2.0-fast
Ratios9:16, 16:9, 1:1, 4:3, 3:4, 21:9
Durations4, 5, 6, 8, 10, 15 seconds
Resolutions480p, 720p, 1080p
Default output options720p, audio enabled, web search disabled unless changed in the card settings
Reference media rolesfirst frame, last frame, reference image, reference video, reference audio

Modes

ModeRequired inputUse for
Text to VideoPrompt onlyPrompt-led motion ideas with no source frame
Image to VideoA first-frame imageAnimate from a selected starting image
First/Last FrameFirst-frame and last-frame imagesGuide a transition between two fixed visual anchors
Multi-ReferenceAt least one image, video, or audio referenceLet multiple media references influence the video task
Use first-frame or first/last-frame modes when the opening or ending visual must be controlled. Use multi-reference when the task needs broader guidance from image, video, or audio examples, and accept that the provider may weigh references differently from prompt text.

Reference Rules

Seedance reference handling is stricter than generic video reference handling:
  • text-to-video does not use references;
  • image-to-video requires a first-frame image;
  • first/last-frame mode requires both a first-frame and a last-frame image;
  • multi-reference mode requires at least one reference asset;
  • frame mode references cannot be mixed with free multimodal references in one task;
  • reference tokens such as @image1 or @video1 can be inserted into prompts after references are collected.
1

Configure provider access

In Settings, configure Seedance direct credentials or a compatible relay. Seedance’s registry entry currently lists wavespeed and other as relay options.
2

Create a video card

Open the Video tab, select Seedance, and confirm the variant, ratio, duration, resolution, and audio setting.
3

Choose the mode

Use text-to-video for prompt-only work, image-to-video for a start frame, first/last-frame for a transition, or multi-reference for mixed media guidance.
4

Attach references

Upload assets or select them from Asset Dock/SmartPicker. Check that the assigned roles match the selected mode.
5

Generate and review

Video generation may take longer than image generation because providers often queue, poll, and post-process results.

Troubleshooting

SymptomLikely causeWhat to check
Missing first-frame errorImage-to-video mode has no first-frame referenceAttach an image and keep its role as first_frame
Missing last-frame errorFirst/last mode has only one endpoint frameAttach both first and last frame images
Reference mix errorFrame references and free references are mixedUse either first/last frame roles or multi-reference roles, not both
Provider errorCredentials, relay capability, endpoint, quota, or model variant mismatchRe-check Settings and provider console
Slow generationProvider queue or long video settingsTry shorter duration, lower resolution, or fast variant where appropriate

Next Step

Use Operational Checklists for video failure triage, or FAQ and Troubleshooting for customer-facing explanations of slow video, model differences, and provider failures.