models

ByteDance: Seedance 2.0 Fast

Markdown · JSON

ByteDance: Seedance 2.0 Fast

ByteDance Seedance 2.0 Fast creates audio-video scenes from text, images, video and sound references. Its speed-oriented edition supports motion and style transfer, video edits and forward or backward extensions, with documented 480p and 720p output.

About the model

This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.

Seedance 2.0 Fast is ByteDance Seed’s speed-oriented edition of the Seedance 2.0 family. It supports joint video and audio generation and a multimodal brief built from text, images, video and sound. Its creative capabilities include new reference-led scenes, edits to existing footage and extensions of a scene, while its documented output levels are 480p and 720p.

Multimodal reference: assigning roles to the material

An image can supply a character, product, composition or visual treatment. A reference video can supply action, camera movement or an effect. Reference audio can supply voice timbre, musical melody or dialogue content. Explain which part of each source you want to carry into the new scene; a reference is more useful when it has a specific creative role.

For example: “Use the ceramic lamp in Image 1 as the product. Follow the slow camera orbit from Video 1, but place the lamp in a quiet reading corner. Use Audio 1 for the musical mood.” The intended output is a new scene combining the chosen appearance, motion and sonic direction, rather than an unspecified imitation of every detail in the references.

The documented combinations include images with audio, images with video, video with audio, and all three together. Text with audio alone, and audio-only input, are not supported. The model also supports text-to-video and image-led generation from a first frame or a first-and-last-frame pair. When an exact endpoint is central to the brief, use the dedicated endpoint workflow; describing a reference image as an endpoint in an omni-reference prompt is indirect control.

Editing an existing video

The model can add, remove or modify elements, replace a subject and redraw or repair parts of a scene. Identify the source video, the object to change and the elements that should stay. For an addition, describe where it appears and when. For a removal, identify the object consistently across the clip.

A practical edit brief might replace a plain bottle in a demonstration with the bottle from Image 1, while asking to preserve the hand movement, background and camera path of Video 1. Review both the replacement and the areas meant to remain stable. Clear preservation instructions make the intended edit easier to evaluate than a general request to “improve” the footage.

Extending and connecting clips

Seedance 2.0 Fast supports forward or backward extension and connecting two or three clips with generated transitions. For an extension, state whether the new action happens before or after the supplied video and describe that action. For a connection, give the clips in their intended order and explain the visual event that joins them.

A simple extension usually returns the newly developed continuation around the original footage rather than assuming the entire source clip is repeated. If the output should contain the original segment, say so in the brief. When filling a transition between two or three videos, the documented workflow can combine original and newly generated content. This is useful for linking a wide product view to a detail shot through a purposeful camera move.

Output and edition differences

The documented Fast output is MP4 at 24 fps, with 480p or 720p, 8-bit color depth and 4–15-second clips. Supported ratios are 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. The standard Seedance 2.0 edition separately lists 1080p and 4K output; those levels are not part of the Fast specification. The 2.0 family supports returning the last generated frame, but does not support the separate Draft preview mode.

Audio can be generated with the footage or omitted for a silent clip. Generated audio is mono. Documented prompt languages include English, Spanish, Indonesian, Portuguese and Japanese. Keep the spoken language consistent within a dialogue; the guide advises against mixing languages except for proper names. For a spoken scene, name the speaker and put the line in quotation marks, then specify the delivery and relevant sound effects. Keep the required performance appropriate to the selected clip length.

Preparing references and observing input limits

The documented reference limits are up to nine images, three videos and three audio clips. Direct reference-image or video uploads containing real human faces are not accepted in this documented producer profile; portrait work uses its supported portrait-asset workflow. Each video or audio clip must be 2–15 seconds long; the combined video duration is at most 15 seconds, and the combined audio duration is separately at most 15 seconds. Video references use MP4 or MOV, at 24–60 fps, and must not exceed 200 MB each. Audio references use WAV or MP3 and must not exceed 15 MB each. The listed image formats are JPEG, PNG, WebP, BMP, TIFF, GIF, HEIC and HEIF. Images must be smaller than 30 MB each; the total request-body limit is 64 MB. In the documented reference-input profile, image width and height must each be strictly between 300 and 6,000 pixels, with a width-to-height ratio strictly between 0.4 and 2.5. Reference videos allow 300–6,000 pixels in each dimension and ratios of 0.4–2.5, inclusive, with 407,696–8,295,044 total pixels. MP4 or MOV videos use H.264/AVC or H.265/HEVC video and AAC or MP3 audio.

Order the assets and refer to them consistently as Image 1, Video 1 or Audio 1. Use the visible subject’s name or distinguishing feature as well as the asset number. Match endpoint-image framing to the intended video ratio, since a mismatch can crop the image or produce a jarring change in framing. Keep the brief focused on the features to transfer, the event to generate and what should remain unchanged; a long prompt can scatter the instructions and leave secondary details unresolved.

Shot planning, text and known behaviours

Organize a complex brief as Shot 1, Shot 2 and Shot 3, with a clear subject, action, position and sound for each. The guide recommends one camera movement per shot and says precise per-shot timestamps are unstable. Give each character a stable label and a few distinguishing features; use a separate clear headshot and full-body reference rather than a combined character-turnaround sheet when facial identity matters.

The model can generate common text, including slogans, subtitles and speech bubbles, with directions for its color, style, position and entrance. Common characters are preferred to rare characters or special symbols. Check the letters in motion. Unwanted subtitles, logos and duplicate characters are documented behaviours; explicit constraints and clean references can reduce them, but do not guarantee their absence. More than four reference people is reported as a stability risk, not a hard file-count limit.

Repeated extensions can compound image-quality loss, and an extension join can jump or roll back. Limit stacked continuations and inspect the join in the edit. Referenced voice timbre may drift, narration can end with a click, and Chinese polyphonic or uncommon characters may be mispronounced. Check the spoken line and ending audio; a short audio fade can help with a cutoff. These checks are part of preparing the creative result, especially when speech or character continuity carries the story.

Ailoot Ultra · Video POST /v1/videos bytedance/seedance-2.0-fast

bytedance/seedance-2.0-fast

ByteDance /bytedance/seedance-2.0-fast

Overview

ByteDance Seedance 2.0 Fast creates audio-video scenes from text, images, video and sound references. Its speed-oriented edition supports motion and style transfer, video edits and forward or backward extensions, with documented 480p and 720p output.

Accepted inputs
Text · Images · Audio
Results
Video

Available in Ailoot · inputs & methods

Ailoot Ultra · Video POST /v1/videos
Input types
text, image, audio
Output types
video
Output format
original MP4 bytes; no normalization/transcode
FieldTypeRequirementValues & limitsDefault
FieldmodelTypestringRequirementRequiredValues & limits
bytedance/seedance-2.0-fast
Default—
FieldpromptTypestringRequirementRequiredValues & limitsDefault—
FielddurationTypeintegerRequirementRequiredValues & limits
4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
Minimum: 1
Maximum: 600
Default—
FieldresolutionTypestringRequirementOptionalValues & limits
480p, 720p
Default—
Fieldaspect_ratioTypestringRequirementOptionalValues & limits
1:1, 3:4, 9:16, 4:3, 16:9, 21:9, 9:21
Default—
Fieldgenerate_audioTypebooleanRequirementOptionalValues & limits
false, true
Conditions: Omitting generate_audio selects the audio-enabled price; false selects the no-audio price. Check has_audio in the result to see whether an audio track was returned.
Default—
Fieldframe_imagesTypearrayRequirementOptionalValues & limits
Minimum items: 1
Maximum items: 2
Input content: Array of frame objects. Each has type=image_url, image_url containing url and frame_type=first_frame or last_frame. Each role appears once at most. Use public HTTPS URLs.
Exact keys: type, image_url, frame_type
Conditions: These keys apply to each frame object. Omit frame_images for a text-only request.
Default—
Fieldinput_referencesTypearrayRequirementOptionalValues & limits
Input content: Array of image or audio reference objects. Set type to image_url or audio_url, and supply the matching URL object containing url. Video references remain unpriceable.
Conditions: Omit frame_images to use reference mode. Use public HTTPS URLs.
Default—
FieldsizeTypestringRequirementOptionalValues & limits
480x480, 480x640, 480x854, 640x480, 854x480, 1120x480, 720x720, 720x960, 720x1280, 720x1680, 960x720, 1280x720, 1680x720
Pattern: ^[1-9][0-9]*x[1-9][0-9]*$
Default—
FieldseedTypeintegerRequirementOptionalValues & limits
Minimum: -9,223,372,036,854,775,808
Maximum: 9,223,372,036,854,775,807
Default—
Fieldcallback_urlTypestringRequirementOptionalValues & limits
Pattern: ^https://
Default—
Fieldsession_idTypestringRequirementOptionalValues & limitsDefault—
FieldtraceTypeobjectRequirementOptionalValues & limitsDefault—
FielduserTypestringRequirementOptionalValues & limitsDefault—
Input material combinations

Text to video · A written prompt. · Required: model, prompt, duration

Provide a text prompt and a supported whole-second duration. Use an exact listed size, or a resolution and aspect ratio that resolve to listed dimensions.

model: Type: string · bytedance/seedance-2.0-fast

prompt: Type: string · Maximum UTF-8 bytes: 10,000 · Non-whitespace required: Yes

Image to video · A written prompt and a frame image. · Required: model, prompt, duration, frame_images

frame_images is an array of objects with type=image_url, image_url containing url, and frame_type. Use a public HTTPS image URL; first_frame and last_frame may each appear once. Use a listed output size or compatible dimensions. Do not add video references.

Exact keys: type, image_url, frame_type

model: Type: string · bytedance/seedance-2.0-fast

prompt: Type: string · Maximum UTF-8 bytes: 10,000 · Non-whitespace required: Yes

Reference to video · A written prompt and image or audio references. · Required: model, prompt, duration, input_references

input_references is an array. Each object has type=image_url or type=audio_url and a matching URL object containing url. Use public HTTPS links. Omit frame_images to select reference mode. Video references cannot be priced.

model: Type: string · bytedance/seedance-2.0-fast

prompt: Type: string · Maximum UTF-8 bytes: 10,000 · Non-whitespace required: Yes

Method parameters and lifecycle
ParameterContract
Parametercontent_typeContractapplication/json
ParameterrequiredContractmodel, prompt, duration
Parametermaterial_typesContracttext, image, audio
Parameteradditional_propertiesContractfalse
Parameteroptional_controlsContractresolution, aspect_ratio, generate_audio, frame_images, input_references, size, seed, callback_url, session_id, trace, user

Lifecycle: submit_once_poll_original

GET /v1/videos/{public_id}

GET /v1/videos/{public_id}/content

Pricing

How the final charge is calculated

The displayed rates estimate the cost before generation. The final charge is calculated from the cost recorded for the original generation. Measured output duration and forecast quantities are not the final billable quantity.

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode
Not specified When fast mode is selected
Flex mode
Not specified When flex mode is selected
Maximum reasoning effort
Not specified When maximum reasoning effort uses the default adjustment

Estimated rates for comparison

Prices by configuration

Match each charge to the conditions shown. Use one rate for each set of alternative configurations.

ConfigurationRate scheduleForecast quantityBilling unitBilling conditionsCharge
ConfigurationBase token ratesRate scheduleBase rateForecast quantity—Billing unit—Billing conditions—Charge
Input · Input tokens · Estimate for comparison only — / 1K tokens
Output · Output tokens · Estimate for comparison only — / 1K tokens
Input · Cache read · Estimate for comparison only — / 1K tokens
Input · Cache write · Estimate for comparison only — / 1K tokens
Input · Cache write, 1 hour · Estimate for comparison only — / 1K tokens
ConfigurationVideo-token priceRate schedule—Forecast quantity—Billing unitper 1,000 video tokensBilling conditionsNo additional condition is declared in this pricing key.Charge
Output · Video-token price · Estimate for comparison only $0.0084 per 1,000 video tokens

The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge.

ConfigurationVideo-token priceRate schedule—Forecast quantity—Billing unitper 1,000 video tokensBilling conditionsinput: with_video_inputCharge
reference · Video-token price · Estimate for comparison only $0.00495 per 1,000 video tokens

The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge.

ConfigurationVideo-token priceRate schedule—Forecast quantity—Billing unitper 1,000 video tokensBilling conditionsaudio: without_audioCharge
Output · Video-token price · Estimate for comparison only $0.0084 per 1,000 video tokens

The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge.

ConfigurationEstimated generation costRate schedule—Forecast quantityone generation estimateBilling unit—Billing conditions—Charge
Output · Estimated generation cost · Estimate for comparison only $0.18144 estimate before generation

This estimate is not an additional charge or a fixed rate for the completed generation.

Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →

Reference tariff details

Model-level reference schedules do not change method selection, quotes or charges. Active charges use the selected Ailoot method rates.

Video configuration price references

Prices by configuration

Match each charge to the conditions shown. Use one rate for each set of alternative configurations.

ConfigurationBilling conditionsCharge
ConfigurationVideo-token priceBilling conditionsNo additional condition is declared in this pricing key.Charge
Output · Video-token price $0.0084 per 1,000 video tokens

The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge.

ConfigurationVideo-token priceBilling conditionsaudio: without_audioCharge
Output · Video-token price $0.0084 per 1,000 video tokens

The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge.

ConfigurationVideo-token priceBilling conditionsinput: with_video_inputCharge
reference · Video-token price $0.00495 per 1,000 video tokens

The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge.

Example requests

Ailoot Ultra · Video

curl · create video
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_REQUEST'
from pathlib import Path
Path('request.json').write_text('{"model":"bytedance/seedance-2.0-fast","prompt":"A serene mountain landscape at sunset","duration":4,"resolution":"480p","size":"480x480","generate_audio":false}', encoding='utf-8')
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/videos \
  -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.json
python3 - <<'PY_RESULT'
import json
from pathlib import Path
r=json.loads(Path('result.json').read_text())
print(json.dumps(r,ensure_ascii=False,indent=2))
print('Keep the complete JSON and response headers; do not resubmit an unknown creation.')
PY_RESULT

Receive and save results

Ailoot Ultra · Video

signed owned content URLs

  • GET /v1/videos/{public_id}
  • GET /v1/videos/{public_id}/content
Check job status
GET original status
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_STATUS_URL'
import json
from pathlib import Path
from urllib.parse import quote
r=json.loads(Path('result.json').read_text())
if not isinstance(r.get('id'),str) or not r['id']:raise SystemExit('Keep the original response and headers for reconciliation; no returned ID')
Path('status-url.txt').write_text('https://api.ailoot.ai/v1/videos/'+quote(r['id'],safe=''))
PY_STATUS_URL
curl --fail-with-body --silent --show-error "$(cat status-url.txt)" \
  -H "Authorization: Bearer $AILOOT_API_KEY" -D status-headers.txt -o status.json
python3 - <<'PY_RESULT'
import json
from pathlib import Path
r=json.loads(Path('status.json').read_text())
print(json.dumps(r,ensure_ascii=False,indent=2))
print('Keep the complete JSON and response headers; do not resubmit an unknown creation.')
PY_RESULT
Other content reads
Save every completed owned output
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
export AILOOT_API_KEY
python3 - <<'PY_ASSETS'
import json,os,subprocess
from pathlib import Path
from urllib.parse import urljoin,urlsplit
r=json.loads(Path('status.json').read_text())
if r.get('status')!='completed':raise SystemExit('Keep the original ID and read its status; never recreate an unknown job')
if not isinstance(r.get('data'),list) or not r['data']:raise SystemExit('Keep the complete original status; no completed outputs supplied')
urls=[]
for i,u in enumerate(r.get('data',[])):
    if not isinstance(u,str):raise SystemExit('Keep the original response; unexpected asset shape')
    urls.append((str(i),u))
for label,path in urls:
    u=urljoin('https://api.ailoot.ai',path);z=urlsplit(u)
    if z.scheme!='https' or z.netloc!='api.ailoot.ai' or z.username or z.password:raise SystemExit('Use the actual returned Ailoot owned content URL')
    target=Path('owned-'+label+'.bin')
    subprocess.run(['curl','--fail-with-body','--silent','--show-error',u,'-H','Authorization: Bearer '+os.environ['AILOOT_API_KEY'],'-D',str(target)+'.headers','-o',str(target)],check=True)
print('All returned owned URLs saved; complete metadata, timing and usage remain in the JSON.')
PY_ASSETS
Keep all completed results

Save every completed video or returned file; retrieve every actual returned asset URL.

Keep every actual owned output and its returned measured metadata.

If the original response needs checking

503 result_pending_check + originalid + X-Should-Retry:false; never replay original

Response fields
FieldTypeMeaning
FieldindexTypeintegerMeaningZero-based position of this video in the outputs list.
Fieldcontent_urlTypestringMeaningSigned HTTPS download URL for this completed video.
Fieldsha256Typestring | nullMeaningSHA-256 digest of the original video bytes; null if unavailable.
Fieldsize_bytesTypeinteger | nullMeaningSize of the original video file in bytes; null if unavailable.
Fieldduration_msTypeinteger | nullMeaningMeasured video duration in milliseconds; null if unavailable.
FieldwidthTypeinteger | nullMeaningVideo width in pixels; null if unavailable.
FieldheightTypeinteger | nullMeaningVideo height in pixels; null if unavailable.
Fieldvideo_codecTypestring | nullMeaningVideo codec identifier; null if not recorded.
Fieldhas_audioTypeboolean | nullMeaningWhether the video contains an audio track; null if not measured.
Fieldaudio_codecTypestring | nullMeaningAudio codec identifier; null when no identifier is recorded.
Errors and next steps
ResponseConditionNext step
Response404 · not_found_errorConditionVideo access is unavailable, or this video ID was not found.Next stepCheck video access. For an existing video, use its original public ID and the same API key.
Response401 · authentication_errorConditionThe API key does not match the authenticated account.Next stepCheck your API key and account access before submitting.
Response400 · invalid_request_errorConditionThe request could not be read, or the download index is invalid.Next stepCorrect the request body. For a download, choose an output index returned by the original task.
Response422 · price_unavailableConditionThe selected video configuration cannot be priced.Next stepChoose a supported video configuration and complete its required options before submitting a corrected request.
Response422 · invalid_request_errorConditionA video input or original continuation task is invalid.Next stepUse valid HTTPS inputs. For continuation, use your completed original public video ID with the same API key.
Response402 · billing_errorConditionThe available balance or limits do not allow a reservation.Next stepCheck your available balance and limits before sending a new request.
Response503 · server_errorConditionVideo verification, storage or service access is temporarily unavailable.Next stepWait for service availability. If you already have a video ID, check that original task instead of creating another generation.
Response503 · result_pending_checkConditionThe original video result and charge need checking.Next stepKeep the returned video ID and check that task. Do not send a replacement generation request while it is being checked.
Response503 · owned_result_unavailableConditionThe existing video download is temporarily unavailable.Next stepCheck the same video task later and download its existing output. A new generation creates a separate operation.
Response409 · video_not_readyConditionThe video content has not been published.Next stepCheck the original task status. Download after it reports completed; if it reports failed, follow its charge-check notice.

Aliases

Model aliases

Ailoot Ultra bytedance/seedance-2.0-fast

Method path aliases

Use the method paths shown above.

Related caller IDs

bytedance/seedance-2.0-fast

FAQ · ByteDance: Seedance 2.0 Fast
What inputs and results are available?

POST /v1/videos · bytedance/seedance-2.0-fast: text, image, audio → video

Which fields does the request use?

POST /v1/videos · bytedance/seedance-2.0-fast: model, prompt, duration, resolution, aspect_ratio, generate_audio, frame_images, input_references, size, seed, callback_url, session_id, trace, user

What limits apply?

POST /v1/videos · bytedance/seedance-2.0-fast: duration.minimum: 1; duration.maximum: 600; frame_images.max_items: 2; frame_images.min_items: 1; seed.minimum: -9223372036854775808; seed.maximum: 9223372036854775807

More details

Connect Ailoot to Claude Code, OpenCode, Hermes or your own app.

The company and its project portfolio

The company and its project portfolio: millions of customers; monthly sales in the billions.

Buy tokens at a discount.

Subscription discounts for regular use. Promo codes offer up to 50% off token purchases.

Subscription
Choose a discounted plan for your regular requests.
Promo code: up to 50% off
Enter your code at checkout. The price updates to reflect the current promotion.
Spending in your history
The model, tokens and amount are recorded for each request.

Choose a subscription · View model prices

Connect the API to a product you sell.

Use Ailoot in SaaS, apps and bots under its official service offer and licence agreement. Request a reseller licence for resale.

Commercial application
Add text, image, video and audio generation to paid features in your service.
Reseller licence
Send a description of your project and how you provide access. Request written terms for use and resale.
Documents on the website
The service offer, licence agreement and data processing policy are available before you connect.

Request a reseller licence · Service offer and licence agreement