TikTok 60-minute videos: API cap is 10 minutes, Sume renders 30

TikTok's developer docs list 10 minutes for API posts; Sume Timeline renders up to 1,800 seconds per job at $0.10 per minute. Plan a long cut around both.

5 min readSume
All posts

Short answer

TikTok's media transfer guide says all creators can post videos up to 3 minutes, some creators can post 5 or 10 minutes, and that the Content Posting API accepts videos up to 10 minutes. We could not find a TikTok page we could read that confirms a 60-minute upload, so this post does not treat 60 minutes as a published limit. Check the length the creator account you post from can use.

On the Sume side, one Timeline 1.0 render can run up to 1,800 seconds (30 minutes) of audio, billed at $0.10 per rounded-up output minute. A 30-minute master therefore costs $3.00 to render, and a 60-minute piece would need two renders.

The limits side by side

The table puts the vendor numbers next to the Sume caps so you can see which one binds first.

Length limits that apply to a long TikTok upload (read 2026-10-03)
LimitValueSource
In-app upload, all creators3 minutesTikTok media transfer guide
In-app upload, some creators5 or 10 minutesTikTok media transfer guide
Content Posting API videoup to 10 minutesTikTok media transfer guide
Timeline render, one jobaudio.duration_seconds 1-1800Sume Timeline docs
Video Trim, source fileup to 1800 secondsSume Video Trim docs
Video Trim, output0.2-900 secondsSume Video Trim docs

What this means for a plan

If you post through the API, the 10-minute ceiling is the number that matters, whatever the app shows a given creator. A 30-minute Timeline render is a master for your own site or for YouTube; the TikTok version is a cut of it.

Video Trim is the tool for that cut. It takes a source up to 1800 seconds and returns 0.2 to 900 seconds, so a 10-minute segment (600 seconds) fits comfortably. Each trim job is $0.02.

  • Render the long master once with the plan endpoint first: POST /v1/timeline-1.0/plan is unbilled and returns duration_seconds, segment_count and estimated_cost_usd_micros.
  • Cut the TikTok version with Video Trim using start and duration, and leave precision on exact unless you only need a stream copy.
  • If a source is longer than 1800 seconds, split it before it reaches Video Trim; the doc caps the source at 1800 seconds.

Cost of a long piece

Two 30-minute renders for a 60-minute program cost $3.00 each, so $6.00, plus $0.02 per trim. These are the public rates from the Sume docs; your plan's rate card is the final word.

For the byte side of the same question, see how the 4 GB file cap constrains bitrate and what a 30-minute render costs.

Before you rely on any length

Platform limits move. Treat the TikTok developer page as the check you rerun before each campaign, and treat the Sume plan endpoint as the check for cost and duration. Neither replaces looking at the creator account that will publish.

A practical workflow

Start from the destination, not the render. Decide whether the long piece lives on TikTok at all. If the answer is yes for a given creator account, confirm the length that account can post in the app, then confirm the API's 10-minute ceiling for anything you publish programmatically. Write both numbers into the brief before anyone opens an editor.

Next, build the master. Timeline 1.0 takes between 1 and 200 video slots and an audio track of up to 1,800 seconds, with fades and transitions as options. The render defaults to async mode, needs an Idempotency-Key header, and accepts only media.sume.com URLs from your workspace, so import external footage first with POST /v1/media-imports.

Finally, cut and publish. Run Video Trim on the master with a start and a duration of at most 900 seconds, check the returned duration, and upload the result. Keep the master; if the platform later raises its limit you can re-cut without re-rendering.

  • Confirm account length in the app.
  • Confirm the API ceiling on the developer page.
  • Plan, render, trim, upload, in that order.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume