Light Speed Future

DOCUMENTATION

Frequently Asked Questions

On this page

12.1 How should I choose Native, Production or Flash?

Choose Native for native Seedance controls and optional Draft-to-Final previews; Production for finished video with flexible delivery controls; and Flash for fast video generation. Use the output options listed for each product. A Production or Flash output resolution is not a claim that the Native model supports the same resolution.

12.2 How is LSF Seedance 2.5 Production different from LSF Video Enhancement?

Use LSF Video Enhancement to improve a video you already have. Use LSF Seedance 2.5 Production to create a new finished video from a prompt and supported references. Both use the public video task endpoints, with product-specific request fields.

12.3 Do I submit tool_version for every product?

Select LSF Seedance 2.5 Production Lite / Standard / Pro and LSF Seedance 2.5 Flash Fast / Standard using the alias supplied by LSF. Do not send tool_version or engine to either product. LSF Video Enhancement Standard / Professional use one alias with tool_version; Lite uses a separate alias.

12.4 Does a still image count as video-input seconds?

No. Only video inputs contribute input-video seconds. A last-frame still image is different from a short tail-video reference.

12.5 Why can the final charge differ from the initial estimate?

For Production and Flash, the delivered video can be longer than requested. Final output seconds are rounded up, and any measured reference-video seconds are added without whole-second rounding. The accepted effective rate remains fixed. Native uses its separate usage-based billing rules; see the relevant product chapter.

12.6 Does omitted fps force 120fps?

No. Production defaults to 24 FPS when fps is omitted. For Video Enhancement, omission retains the source FPS; the initial estimate uses the highest FPS price band and the final charge uses actual output FPS. Production and Flash have no additional FPS surcharge. See each product chapter for its output controls.

12.7 Does return_last_frame request a first/last-frame generation constraint?

return_last_frame requests an image of the finished video, not a first/last-frame generation constraint. Production and Flash do not support it for MOV, 6K or 8K; omit it or set false. Other supported MP4 profiles require enabled extraction. Standalone Video Enhancement does not accept this field at all. Native Seedance has its separate controls in section 5.

12.8 Will repeated polling advance or charge the workflow again?

No. LSF Seedance 2.5 Production and LSF Seedance 2.5 Flash advance in the background. Repeated GET reads the existing task and does not create a new generation or duplicate billing.

12.9 Can I use either asset library without verification?

No. Use the authorized library path for the asset. Real-human assets still require the corresponding verification and rights.

12.10 Can I cancel, list or delete video tasks through this guide?

No. The documented video endpoints support creation and retrieval. Asset Library list/delete paths are separate asset operations.

12.11 Can I expose the API key in the website?

No. Keep it on your backend. The website may display example placeholders and product information; it should not embed customer credentials.

12.12 Can I request MOV from LSF Seedance 2.5 Production or LSF Seedance 2.5 Flash?

Production Standard and Pro 6K/8K deliver MP4, as do the documented Flash outputs. Standalone Video Enhancement Professional 6K supports ProRes 10-bit MOV with its own request schema. Do not transfer that format to Production. Native Seedance has its separate output_format control in section 5.

12.13 Can I request another account's asset or task?

Only your authorized assets and task context are available. Knowing an identifier is not authorization.

12.14 How do I access a product or output option?

Use the model alias and product permissions assigned to your account. Contact LSF to add a product or output option. The supported settings are listed in the corresponding product chapter.

12.15 What is Seedance 2.5 Draft Mode?

It is a two-stage Native Seedance 2.5 workflow: first create and review a 480p Draft, then create a separate 1080p Final, or a 4k Final, from that completed Draft. It uses the same Seedance 2.5 model alias supplied by LSF and the normal video task endpoints.

12.16 Is the Final step included in the Draft charge?

No. Draft and Final are independently billed tasks. Draft uses the applicable Native Seedance 2.5 480p pricing for its original request inputs. Final uses the applicable 1080p or 4k pricing class determined by whether the original Draft request included video input; the generated Draft preview itself does not force video-input pricing or add its duration as input video.

12.17 Can Final use a different API key, model alias or creative inputs?

A valid replacement key for the same LSF organization and account may create Final from an eligible Draft, subject to current product access permissions. Use the same Seedance 2.5 model alias. Final inherits the Draft’s prompt, references, duration, ratio, audio choice and Omni task type; do not resend or change them. Set supported Final output controls as described in section 5.8. Final is a new task charged to the submitting key; the Draft charge is unchanged.

12.18 How long can I keep a Draft before creating Final?

Create Final after the Draft completes successfully and before 7 days have elapsed from its original creation time.

12.19 How do I select Standard or High bitrate for Native Seedance?

Set metadata.bitrate_mode to "standard" or "high" on a supported Native request. It is available for the Seedance 2.0 series and Seedance 2.5, including 2.5 Draft / Final with MP4 / MOV. Omission leaves the field unspecified; set it explicitly if needed. An omitted Final value is not assumed to inherit the Draft value.

12.20 Can I force Native Seedance to output H.264 or H.265?

No. Native Seedance codec selection is not exposed as a customer request control. Do not send metadata.codec. The delivered codec and bit depth depend on the native model, resolution and output profile; verify playback compatibility for your target environment.

12.21 Which product supports a reviewable preview before the final video?

Use Native Seedance 2.5 Draft Mode for a reviewable preview followed by a separately requested Final. Flash delivers a finished video through one task and does not offer a separate preview step.

12.22 Does LSF Seedance 2.5 Flash require client_request_id?

Yes. Generate and save it before the first POST. Use a different ID for an intentionally new job and retain the original key, ID and body for retries. Do not reuse one video ID across products on the same key.

12.23 Can I choose a codec for LSF Seedance 2.5 Flash or LSF Seedance 2.5 Production?

Flash does not expose a codec selector. Production Pro 6K/8K uses metadata.codec="h265" with bit_depth=10 and MP4; Standard omits codec and bit_depth. Section 6.1 lists Production formats and playback requirements.

12.24 Does a named 1080p output always have exactly 1920 by 1080 pixels?

It identifies an output resolution band. Actual width and height depend on the source, aspect ratio and processing profile. For example, a portrait result can have a height slightly different from 1920. Validate the returned media for strict downstream pixel requirements.

12.25 Are quoted minutes a one-minute minimum for LSF Video Enhancement?

No. A per-minute rate is a display unit. Billing uses the reported output duration rounded up to whole seconds and the applicable FPS band. A per-second quote is already in the billing unit; do not divide it by 60 again.

12.26 Why can two accounts or two products have different effective prices?

Prices can reflect account-specific commercial terms. Use the agreed effective rate for the selected product, tier, resolution and input mode. These terms are applied by LSF, not chosen through a request parameter. Accepted tasks retain their original pricing terms.

12.27 How do I request Native Seedance 2.5 4K?

Use your existing Native Seedance 2.5 alias and the ordinary POST /v1/videos endpoint with metadata.resolution="4k". The same Native Seedance 2.5 account permissions apply. Draft previews remain 480p; a Final can request 4k using the completed Draft. No separate 4K alias or customer application is needed.

12.28 Does a lower per-token rate make 4K cheaper than 1080p?

Not necessarily. Native 4K uses USD5.64 per million completion tokens without video input and USD3.48 with original video input at the published standard rates. Higher resolution generally uses more tokens. Compare the total expected token usage and your applicable rate, rather than the unit price alone. Actual task usage determines the final charge.

12.29 Is Native Seedance 2.5 Flash the same as LSF Seedance 2.5 Flash?

No. Native Flash is the separate 480p/720p native model in section 5A, with completion-token billing and no Draft-to-Final or higher-resolution output. The existing LSF Flash in section 7 retains its Fast/Standard workflow, output options and per-second billing. Use the separately enabled Native Flash API alias. Native Flash is not available in Light Speed Future for ChatGPT.

12.30 Can I read an accepted Native Flash task after my key allowance is exhausted?

Yes, provided the key is still valid and authorized for that task. Query and original-file download do not require new generation allowance. Revoked, disabled, expired, deleted, model-restricted or IP-disallowed credentials remain subject to access checks. Use an authorized same-account, same-organization replacement key if needed, retain the original task ID, and do not repeat the POST with a new key. New task creation still requires sufficient allowance and an enabled product.

Search documentation

Search pages and headings. Use Tab or arrow keys to move through results.

NEWSEEDANCE 2.5

Native Seedance 2.5 4K

Invite-only access on BytePlus
Available to you through LSF

Explore Native 4K