6K formats for delivery and editing: Standard delivers H.264 8-bit MP4; Professional delivers ProRes 10-bit 4:2:2 MOV for compatible editors. Use a source up to 2K (short side ≤1440 pixels and long side ≤2560 pixels); output preserves its aspect ratio. Keep source FPS or choose 15–120 FPS. Supported clip length depends on the source file and processing requirements. Other supported resolutions remain available. See the Video Enhancement API reference and current prices.
AI video generation is only one part of a delivery workflow. Teams may already have a generated clip, product video, campaign asset or archive file that needs a cleaner high-resolution output.
A Video Enhancement API processes that existing source without asking the generation model to create a new scene. Through Light Speed Future, developers can submit a source video, choose an enabled enhancement route and retrieve the completed result through the same asynchronous video-task pattern used across the LSF platform.
When to use Video Enhancement
Use Video Enhancement when:
- The source video already exists.
- You want enhancement without generating a new scene.
- The application needs explicit resolution, FPS or bitrate controls.
- You need to compare Standard and Professional processing.
- Enhancement should remain a separate step in your product interface.
If the application needs to create a new finished video up to 8K from a prompt and supported references, use LSF Seedance 2.5 Production.
Lite, Standard and Professional tiers
LSF exposes three Video Enhancement tiers.
Lite
Lite uses a dedicated model alias. It supports the common resolution, FPS and bitrate controls for a streamlined enhancement workflow. It does not use tool_version="fast" and does not accept Standard- or Professional-only controls.
Standard
Standard uses the shared Standard/Professional alias with tool_version omitted or set to standard. It supports scene and enhancement-style controls.
Professional
Professional uses the same shared alias with tool_version="professional". It supports professional enhancement style and established output-depth controls.
Lite supports outputs through 4K. Standard and Professional support outputs through 8K when enabled, with available tiers and resolutions listed on the Pricing page. The enabled resolutions and advanced media options are product- and customer-specific. Do not assume every combination is available until it has been confirmed.
Core request fields
A Video Enhancement request uses POST /v1/videos and supplies an existing source through metadata.video_url. Provide the source-video duration in metadata.duration.
Common controls include:
metadata.resolutionfor an enabled named output such as 1080p, 2K or 4K.metadata.fpsfor a target between 15 and 120 FPS.metadata.bitrate_levelfor low, medium or high.metadata.bitratefor an explicit supported bitrate.metadata.scenefor Standard scene treatment.metadata.enhance_stylefor Standard or Professional.metadata.bit_depthfor supported Professional output.metadata.client_request_idfor safe identical-request replay.
For Professional 6K ProRes, use codec="prores", bit_depth=10 and output_format="mov". Omit bitrate, bitrate_level and scene for this format. Standard 6K uses H.264 MP4 and omits codec and bit_depth. See the Video Enhancement field reference for the complete settings.
Standalone Video Enhancement rejects return_last_frame even when false. Omit it entirely. Choose resolution or resolution_limit, never both. Short-side limits 2161–3456 use the 6K price tier; 3457–4320 use 8K.
The source must have finite positive duration and finite FPS greater than 0 and no more than 120; asset:// input is not supported. The source URL must be a direct public HTTP or HTTPS address that remains accessible during validation and processing. A URL that plays in a browser may still fail if it requires cookies, private headers, unstable redirects or anti-bot access.
Resolution and FPS affect the final cost
Video Enhancement is billed from the actual enhanced output duration, selected output profile and FPS band. The output duration is rounded up to a whole second.
| Actual output FPS | Multiplier |
|---|---|
| Up to 30 FPS | ×1 |
| More than 30, up to 60 FPS | ×2 |
| More than 60, up to 120 FPS | ×4 |
If the request omits FPS, processing preserves the source FPS and the initial estimate uses the highest FPS price band. Final billing uses the actual output FPS. Omitting FPS does not force the video to 120 FPS.
At up to 30 FPS, Standard 6K is $3.12 per output minute ($0.052/second) and Professional 6K is $31.20 per output minute ($0.520/second). Convert a minute rate to seconds once, apply the FPS multiplier once and round output duration up once. Source duration is not added separately, and there is no one-minute minimum. Your agreed account rate applies.
Design for asynchronous delivery
An accepted create response means that the job entered processing; it does not mean the final video is ready. Store the returned task ID and retrieve the same task through GET /v1/videos/{task_id} until it reaches a terminal state.
For reliable integration:
- Validate the source before submitting it.
- Store the exact request and
client_request_id. - Poll the original task every 30 seconds or longer.
- Do not create another task because a status request was interrupted.
- Read the actual output duration, resolution and FPS from the completed result.
- Copy the temporary output into customer-controlled storage.
Video Enhancement vs Production
Video Enhancement expects a source video and returns an enhanced version of that source. Production starts with a prompt and supported references and returns a new finished video up to 8K through one task.
Their billing models also differ. Video Enhancement uses an FPS multiplier; Production currently does not. Production may count measured reference-video duration together with rounded output duration, while Video Enhancement bills the enhanced output under its own contract.
Add video enhancement to your product
Use Video Enhancement when your users bring an existing video. Use LSF Seedance 2.5 Production when they want to create and finish a new video through one managed workflow.
View current pricing or contact Light Speed Future to confirm available tiers and output combinations.
Plan a representative test
A video upscaling API can fit an existing generation pipeline. Test supported 4K video upscaling against representative source clips; results depend on source quality and selected settings. Keep the original for comparison and check playback compatibility before publishing.
Compare current pricing, check the relevant API reference, or talk to LSF about your output and expected usage. New customers can request $20 in test credit.