One Seedance 2.5 clip in 9:16 and 16:9: Timeline fit blur or cover

Re-generate for each ratio, or reframe a finished clip? Timeline 1.0 fit modes cover, contain, stretch and blur, with output sizes, on Sume.

5 min readSume
All posts

If one Seedance 2.5 clip has to ship as both 9:16 and 16:9, you have two options on Sume: generate it twice with a different aspect_ratio, or reframe the finished clip through Timeline 1.0. Reframing is a fraction of the cost of generating again, but it crops or pads; a fresh generation composes for the new frame. For a quick cutdown where the subject sits near the center, reframing usually works. For wide establishing shots, regenerate.

The two routes

The ratios in the first row of the last line come from the video docs' Seedance 2.0 catalog example; check supported_aspect_ratios for seedance-2.5 itself.

Generate twice versus reframe, per the Sume docs, read 2026-10-05
QuestionGenerate each ratioReframe with Timeline
Composition fits the new frameYes, the model composes for itOnly what the crop or fit leaves
Same take in bothNo, separate generationsYes, same pixels
CostA generation per ratio$0.10 per output minute, rounded up
TimeModel queue and renderWorker ffmpeg
Seedance 2.5 ratiosSix listed in the docs for Seedance models, such as 21:9, 16:9, 4:3, 1:1, 3:4, 9:16Output width and height are your choice, even integers 256 to 2160

Fit modes

Each video[] slot takes a fit value: cover (default) fills the frame and crops the overflow; contain keeps the whole picture and pads; stretch distorts to fill; blur fills the padding with a blurred copy of the clip. For a 16:9 clip going to 9:16, blur keeps the whole picture visible over a soft background, and cover crops to the center.

  • Subject is centered and the sides do not matter: cover.
  • Whole composition matters, such as a product beside text: blur or contain.
  • Never use stretch for people or products.

A vertical reframe

output.width and output.height must be even integers between 256 and 2160. The default output is 1080 by 1920. If you omit output.fps, the render follows the source rate, which avoids the judder the docs warn about when a rate is resampled.

curl -X POST https://api.sume.com/v1/timeline-1.0/render \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: reframe-9x16-001" \
  -d '{
    "audio": { "mode": "silence", "duration_seconds": 30 },
    "video": [
      { "source_url": "https://media.sume.com/artifacts/artf_demo/wide.mp4", "start": 0, "duration": 30, "fit": "blur" }
    ],
    "output": { "width": 1080, "height": 1920 }
  }'

Safe areas and text

Reframing breaks anything that sits near the edges. If your original has captions, logos or a price badge in a corner, a cover fit may crop it off. Burn text in after reframing, not before, or keep key elements near the center during generation. The compose route can overlay a still plate on a clip, so a logo or date plate can be added after the reframe.

Check the result at the final size: a clip that looks fine at 1920 wide may be unreadable at 1080 by 1920 on a phone.

  • Add text after the reframe.
  • Keep subjects near the center when you know a cutdown is coming.
  • Review at the final size.

A decision rule

If the ratios are close, such as 16:9 to 4:3, reframe. If the ratios are opposite, 16:9 to 9:16, reframe with blur for a social cutdown, but regenerate for a hero placement where the subject must fill the frame. Reframing a wide shot to vertical with cover shows only the middle third, which is rarely the best third.

For a 16:9 output from a vertical clip, set width 1920 and height 1080 and use blur the same way. Use the unbilled plan call first to confirm the compile. Seed's launch page (read 2026-10-05) is the vendor reference for the model itself.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume