Longest video per plan: Fliki, Vidnoz, Kapwing vs Sume's 30-minute cap
Fliki goes 5, 15 and 40 minutes by plan, Vidnoz 3 then 60, Kapwing 4 then 120. Sume Timeline renders up to 1,800 seconds per job. The numbers side by side.

The longest single video differs a lot by plan: Fliki allows 5 minutes on Free, 15 on Standard and 40 on Premium; Vidnoz lists 3 minutes on Free and 60 on its paid plans; Kapwing lists 4 minutes on Free and 120 on Pro. Sume's Timeline render takes up to 1,800 seconds, which is 30 minutes, per job. Longer programs are built by rendering parts and joining them.
What are the limits side by side?
All vendor numbers come from each company's pricing page as fetched on 2026-10-12. Sume's figure comes from the Timeline contract in the Sume API.
| Tool | Entry plan | Top listed plan | Notes |
|---|---|---|---|
| Fliki | Free: 5 minutes | Premium: 40 minutes | Standard is 15 minutes |
| Vidnoz | Free: 3 minutes | Starter and Business: 60 minutes | Enterprise is custom |
| Kapwing | Free: 4 minutes | Pro and Business: 120 minutes | Free also capped at 720p |
| Sume Timeline | Same on every plan that can render | 1,800 seconds (30 minutes) per job | Concurrency differs by plan |
Why does Sume cap at 30 minutes?
Sume's Timeline job is a declarative assembly: you send clips, audio and captions, and the render is reserved per output minute. The contract states a maximum of 1,800 seconds, and all media URLs must be Sume-hosted. The cap applies to a single job, not to a project, so an hour-long program is two jobs of 30 minutes or three of 20.
The cap does not scale with the price of the plan. What the plan changes is how many jobs run at once: 1 on Free, 4 on Pro, 8 on Startup and 20 on Scale, so a long program split into parts finishes sooner on a higher tier.
When does the limit matter?
For most short-form work none of these caps is a constraint. They matter for webinars, lectures, podcasts with video, and course modules.
- Under 15 minutes: every paid plan above fits.
- 15 to 30 minutes: Fliki Standard is too short; Fliki Premium, Vidnoz paid, Kapwing paid and one Sume Timeline job all fit.
- 30 to 60 minutes: Sume needs two jobs; Fliki Premium needs a part split too, while Vidnoz paid fits in one render.
- Over 60 minutes: only Kapwing's 120-minute export fits in one file among these four.
How would you split a long program on Sume?
Cut at scene or chapter boundaries, render each part as its own Timeline job, and keep the same captions style and canvas size in every request so the parts match. Join them afterwards with a second pass if a single file is needed. Submitting the parts together is cheap in time on Pro or above, because several can run at once; on Free they run one after another.
Sources
Related posts
More in Comparisons
- Lovart credits reset monthly, top-ups last 366 days: Sume's wallet?
Lovart's FAQ: plan credits reset each billing cycle, no rollover; top-ups last 366 days. Sume top-ups last 365 days; its plans carry no credits.
- Magnific credits last a year with no monthly reset: Sume top-ups too?
Magnific says plan credits are valid for 1 year with no monthly resets. Sume top-up credits carry a 365-day expiry. How the two compare, with plan prices.
- Topview 180-second avatar videos vs Sume 60-second jobs: cost
Topview lists a 180 s avatar cap on every plan; Sume jobs run 4 to 60 s. Three chained Standard jobs for a 180 s script cost $33.12 without a product image.
- Sume vs Argil: AI avatar video and video agents compared
Argil makes AI-avatar and story videos with a chat agent, Director; Sume is a video agent with a multi-model API. Avatars, API, pricing, and limits compared.
Written by Sume