Seedance 2.5 60 FPS on Dreamina: is there a frame-rate field?
Dreamina's plan page lists frame-rate improvements up to 60 FPS and resolution upgrades. Sume's video request has no fps field; here is what it takes instead.
Dreamina's plan page lists video length extension, resolution upgrades and frame-rate improvements up to 60 FPS as plan features. Sume has no frame-rate parameter on POST /v1/videos, so you cannot request 60 FPS from the API; resolution is a field, and an upgrade is a new request.
What Dreamina lists
Source: Dreamina pricing plans, read 2026-10-02.
| Feature on the plan page | What it is on Sume |
|---|---|
| Frame rate up to 60 FPS | No request field. The frame rate is whatever the model returns. |
| Resolution upgrades | Send a new request with a higher resolution. |
| Video length extension | A new request; seedance-2.5 accepts 4 to 30 seconds. |
| Watermark removal on downloads | Not a Sume feature to compare; see the watermark post. |
The Sume request fields
The video request documents model, prompt, duration, resolution, aspect_ratio, size, frame_images, input_references, generate_audio, seed, callback_url and provider. There is no fps field. Two of the others are narrower than they look: seed is rejected by every v1 model, and provider.options entries are rejected rather than ignored.
Resolution values run from 480p up to 4K as a vocabulary, but each model advertises a subset. seedance-2.5 lists 480p, 720p and 1080p.
If you need a higher frame rate
Check the file you receive, not the marketing. Download the clip, read its frame rate with a tool such as ffprobe, and decide whether it is enough. If you need a different rate, a frame-interpolation step in your own editing tool is the usual route, and it is a separate step from generation.
Do not assume the output of a Seedance clip matches the frame rate shown on a plan page.
- Use
GET /v1/videos/modelsto see supported resolutions and durations. - Draft at 480p, then re-request the chosen take at 1080p.
- Measure the delivered file before you promise a frame rate to a client.
Where Sume stands
Sume does not claim 60 FPS output for Seedance 2.5, and its docs do not list a frame-rate control. If your workflow depends on one, that is a gap to plan around.
Sources
Related posts
More in Developers
- Seedance 2.5 first frame plus references in one request: 400
On Sume's Video Router, image_url plus reference_*_urls returns 400 for seedance-2.5. Pick image-to-video or reference-to-video; /v1/videos lets frames win.
- Seedance 2.5 references: input_references or reference_image_urls?
POST /v1/videos takes frame_images and input_references for seedance-2.5; the Video Router takes image_url and reference_*_urls. The wrong shape gets 400.
- Seedance 2.5 reference audio alone returns 400: add an image
On Sume's Video Router, reference_audio_urls with no reference image or video returns 400. Pair the audio with an image or clip, within 3 audio and 12 total.
- Seedance 2.5 seed, size and provider options: why Sume returns 400
Sume rejects seed, size and non-empty provider.options on seedance-2.5 with 400 instead of dropping them. What to send to repeat a clip or fix the frame size.
Written by Sume