Captions app 10-minute captions vs Sume's 60-second inline cap

Captions processes videos up to 10 minutes. Sume's inline avatar captions reject estimates above 60 seconds; standalone video-captions is a separate job.

4 min readSume
All posts

The Captions app release notes say caption processing supports videos up to 10 minutes. In Sume, the limit depends on the route: inline captions on an avatar video are rejected when the estimated duration is above 60 seconds, and the standalone caption job is a separate endpoint.

Captions facts are from its release notes (an undated list); Sume facts from Generate avatar video and Video captions, read 2026-10-01.

What is Sume's inline caption limit?

Inline captions are an optional captions object on the avatar talking-video request. They burn into the final MP4 after generation, and the docs state that an estimated duration above 60 seconds is rejected. Avatar scripts are already limited to a 4-60 second estimate, so the two limits meet at 60.

Length ceilings, read 2026-10-01.
RouteDocumented ceiling
Captions app, caption processingUp to 10 minutes (release notes)
Sume inline captionsRejected above 60 s estimate
Sume standalone POST /v1/video-captionsNo maximum stated; priced at $0.20 for videos up to 60 s

How do I caption an existing longer clip?

Use the standalone job. POST /v1/video-captions takes a public HTTPS video_url and returns a job-backed captioned video. The page prices a standalone job at $0.20 for videos up to 60 seconds and states no maximum length, so test with your clip and read the job's status before you rely on a length. For the long-clip pattern, see add captions to a long video.

Do inline captions cost extra?

Inline captions do not create a separate billed video-caption job, but the docs describe a fixed $0.20 caption add-on included in the avatar-video estimate when enabled. A caption-stage failure soft-fails, so the avatar job can still succeed with a clean video_url and captions.status=failed.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume