Kapwing Pro 120-minute export vs Sume Timeline 30-minute cap
Kapwing Pro lists 120-minute exports at $24 a month. Sume Timeline accepts 1 to 1,800 seconds per render at $0.10 per output minute. Which fits a long edit?

Kapwing Pro handles the longer edit: its page lists a 120-minute export length at 4K with no watermark, while one Sume Timeline render stops at 1,800 seconds, which is 30 minutes. For anything between 30 and 120 minutes in a single file, Kapwing Pro is the fit. For a short or mid-length assembled video that you build from code, Sume Timeline costs $0.10 per output minute and needs no subscription.
The two are different kinds of tool. Kapwing is an editor where a person arranges clips on a canvas; Sume Timeline takes a JSON document and returns an MP4.
| Item | Kapwing | Sume Timeline 1.0 |
|---|---|---|
| Longest single export | Free 4 minutes; Pro and Business 120 minutes | audio.duration_seconds 1 to 1,800 (30 minutes) |
| Resolution | Free 720p; Pro and Business 4K | Output edges 256 to 2160; default 1080 by 1920 |
| Watermark | Free yes; Pro and Business no | Not mentioned in the Timeline doc |
| Price | Pro $24/month, or $16/month billed annually ($192/year) | $0.10 per ceil(output minute) |
| Slots | Editor timeline | 1 to 200 video slots per render |
Arithmetic for the 30-minute case
A 30-minute Sume render is 30 billable minutes, $0.10 times 30 = $3.00. A 12-minute render rounds up to 12 minutes, $1.20. A 61-second render rounds up to 2 minutes, $0.20, because the rate is per ceil minute. You can call POST /v1/timeline-1.0/plan first: it is unbilled and returns billable_minutes and estimated_cost_usd_micros without creating a job.
On that arithmetic, Kapwing Pro at $24 is the price of 240 Sume output minutes, so a team that renders about four hours of finished video a month with no human editing at all would break even. Below that, per-job is cheaper; above it, the subscription is cheaper per minute.
What each side needs from you
Sume Timeline expects its inputs ready. Every URL must already be an artifact or asset in your workspace on media.sume.com, so you import files first, and you send an Idempotency-Key with each render. The audio spine is one file or up to 20 gapless parts, and the video slots are ordered with optional fade, wipe, slide or dissolve transitions of up to one second.
Kapwing's page does not describe an API in the part I read, so I make no claim either way about automation there.
- Use Sume Trim at $0.02 per job to cut ranges before they go into slots.
- Use Audio detach at $0.01 per job to lift a spine from a recorded clip.
- Keep renders at or under 30 minutes, or split a longer program into parts for a person to join.
Verdict
Long single files and hand editing: Kapwing Pro. Programmatic assembly of up to 30 minutes, billed by the output minute: Sume Timeline. If you mix both, assemble the repetitive sections on Sume and finish the long cut in an editor.
Sources
Related posts
More in Comparisons
- Kling 3.0 Omni is 9th for video editing at 1,000 Elo: Kling 3 on Sume
Kling 3.0 Omni (1080p Pro) is ninth on the AA video-editing board at $10.91 a minute. Sume lists kling-3 for generation: $8.40 or $12.60 a minute, 4 to 15 s.
- LinkedIn video ad vs Page video: which numbers differ
LinkedIn video ads and Page video use different limits for length, size and ratio. Both lists read on 2026-10-08, with the Sume tool that fixes each mismatch.
- Scene logs for 20 reference ads: by hand vs $0.30 per analysis
Sume's legacy video-analyses call returns typed scenes for $0.30 an ad: $6.00 for 20 ads. Caps, caveats and why new work should use video inspect.
- Longest ad video: Pinterest 15 min, LinkedIn 30 vs Sume 900 s trim
Pinterest ads reach 15 minutes, LinkedIn video ads 30, LinkedIn Pages 10. Which of those a Sume trim (900 s) or Timeline (1,800 s) render can produce.
Written by Sume