Runway Edit Studio 30 s edits vs Sume's Omni edit
Runway's Aleph 2.0 edits up to 30 s at 1080p in Edit Studio. Sume edits video with gemini-omni-flash-1.1 and a video_url. Compare them, with an API call.

Runway's Aleph 2.0, launched May 21, 2026 inside Edit Studio, edits clips up to 30 seconds at 1080p in a web interface. Sume offers prompt-based video editing through the API with gemini-omni-flash-1.1, which takes a video_url and a prompt that describes the change.
What Runway announced
According to Runway's announcement, Aleph 2.0 edits up to 30 s at 1080p, lets you show a frame of the desired edit, supports multi-shot edits across cuts, and is available on all paid plans on desktop web.
| Item | Runway statement |
|---|---|
| Launch date | May 21, 2026 |
| Edit length | Up to 30 s at 1080p |
| Edit guidance | Show a frame of the desired edit |
| Multi-shot | Edits across cuts |
| Availability | All paid plans, desktop web |
How Sume's edit mode works
In the Video Router catalog, gemini-omni-flash-1.1 routes by request shape. Sending video_url selects video_to_video: the prompt describes the edit, resolution is optional with a 720p default, and aspect_ratio and duration are not sent. The model is documented at 3 to 10 seconds across 360p to 4K.
The docs do not publish a separate length cap for the edit source, so test your clip length before you plan a workflow around it. video_url is the edit source, not a reference, and cannot be combined with image_url, end_image_url or any reference_*_urls. Native audio is always on, and billing is the provider list price times 1.25 per output second by resolution.
curl -X POST https://api.sume.com/v1/video-router/generate \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: video-router-edit-001" \
-d '{
"model": "gemini-omni-flash-1.1",
"prompt": "Replace the bottle with an apple. Keep everything else the same.",
"video_url": "https://example.com/clip.mp4",
"resolution": "720p",
"mode": "async"
}'Which one to pick
Pick Edit Studio when you want to work interactively on a long single clip and your plan covers it. Pick the API route when edits are part of a pipeline: you get an async job, an idempotency key and a result you can fetch from the job endpoints.
For clips longer than the model envelope, cut the source into pieces first. Sume documents a separate trim job for range cuts, and the edited pieces can be joined afterwards.
Sources
Related posts
More in Comparisons
- Gen-4.5 true HDR (BT.2020) vs a Sume MP4 finish
Runway documents Gen-4.5 HDR output graded into BT.2020. Sume's docs describe MP4 outputs and a Timeline render, with no HDR claim. Plan the finish accordingly.
- Runway product_ad recipe: 200 credits for 4 s vs a Sume product clip
Runway's product_ad recipe lists 200 credits ($2.00) for 4 seconds at 720p plus 36 per extra second. A 10 s ad is $4.16. Sume Wan 3.0: $1.25 for 10 s.
- Runway product_campaign_image at 36 credits vs Sume's image rows
Runway lists product_campaign_image at 36 credits ($0.36) per 1080p image: $4.32 for 12. Sume rows run $0.0375 to $0.1875, so 12 images cost $0.45 to $2.25.
- Seedance 2.5, Wan 3.0 and Omni Flash: where each one is sold
Runway lists seedance2_5, wan3 and gemini_omni_flash_1.1 as API ids, Luma hosts Seedance 2.5, and Sume routes all three. How to compare.
Written by Sume