Can't upload past 15 minutes? Verify your account, then re-upload

To upload a video longer than 15 minutes, you first verify your Google Account. YouTube's help page says to start an upload in the mobile app, choose a video longer than 15 minutes, finish the details, tap Next, and follow the steps to get a verification code by text message or an automated voice call. After that, the maximum is 256 GB or 12 hours, whichever is less.

If you make long videos with Sume, there is one more limit on our side: a single Timeline render is capped at 1800 seconds, so 30 minutes. The table below shows both.

What happens after I verify?

The first thing to know, per the page, is that you have to upload the video again. If you verified but the video still won't play, sign in to YouTube Studio, select Create and upload it again.

To check whether you are already verified, go to Feature eligibility. If you are verified, you see "Enabled" in the box for features that require phone verification.

Why can't I upload long videos if I verified?

The page names one cause: if you could previously upload long videos and no longer can, check your account for copyright claims and strikes. It also covers a file that is larger than 256 GB. Its advice is to compress the video in editing software first, using the H.264 codec to reduce file size while keeping quality.

It also says YouTube has changed upload limits in the past, so you may see older videos that run longer than 12 hours.

How long can a video I make with Sume be?

A Timeline 1.0 render can run up to 30 minutes with up to 200 ordered video slots. The public rate is $0.10 per ceil output minute, and the reserve is ceil(audio.duration_seconds / 60) minutes, so a full-length render reserves 30 minutes, which is $3.00 at that rate. Confirm the rate in GET /v1/catalog.

That is above YouTube's unverified 15-minute line, so a 20-minute talk assembled in Sume needs a verified account to upload. If your finished video is longer than 30 minutes, render it in parts and join them in your editor, since one Timeline job will not.

Can I check the length before I upload?

Yes. A plan call compiles the timeline without creating a job, reserving credits or downloading media. It returns duration_seconds, segment_count, billable_minutes and estimated_cost_usd_micros. It cannot predict warnings about short sources that get padded or looped, so read warnings[] on the real render. All source URLs must already be this workspace's media.sume.com files; import with POST /v1/media-imports first.

curl -X POST https://api.sume.com/v1/timeline-1.0/plan \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "audio": {"url": "https://media.sume.com/artifacts/artf_demo/talk.wav", "duration_seconds": 1200},
    "video": [
      {"source_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4", "start": 0, "duration": 1200}
    ]
  }'

What should I do first?

Verify before the day you need the upload, since the code arrives by text or voice call and you must upload again afterward. Then plan the render, make the file, and upload from Studio. If it fails after verification, look at copyright claims first, as the page advises.