Podia video cap by plan: 500, 1,000 or unlimited lessons

Podia counts video files per plan: Mover 500, Shaker 1,000, Earthquaker unlimited. Join a Sume intro bumper into each lesson render so it is one file, not two.

4 min readSume
All posts

On Podia the number that limits a big course is the count of video files: the Mover plan lists 500 videos, Shaker 1,000, and Earthquaker unlimited. If you add an AI-made intro bumper or sale trailer as its own upload for every lesson, you spend that quota twice, so join the bumper into the lesson in one Sume timeline render and upload a single file.

What Podia counts

Podia's video limits page (read 2026-10-10) lists the per-plan counts and says that other file types, such as PDFs, images and audio files, do not count toward the limit. It also says extra video capacity is not available as a separate add-on, so the only way to raise it is a plan upgrade. The page does not state a per-file size or duration in that article; those sit on Podia's separate format guidelines page.

Podia video count by plan, read 2026-10-10 from help.podia.com
PlanVideos allowedLessons if every lesson also uploads a separate bumper
Mover500250 lessons
Shaker1,000500 lessons
EarthquakerUnlimitedNo count to manage

The right-hand column is arithmetic: two files per lesson halves the number of lessons you can host. Add a trailer, a welcome video and a few sale-week variants and a Mover-plan school reaches 500 sooner than the lesson count suggests.

One file per lesson with the timeline

Timeline 1.0 takes up to 200 video slots and renders one MP4 up to 1800 seconds. Put the generated bumper in video[0] and the lesson footage after it, with a short fade transition between them (transition duration at most 1 second). Because the render uses one audio spine, build that spine from the bumper sound and the lesson narration with audio.parts[], which accepts up to 20 gapless slices, so the join needs no extra text-to-speech.

To make the bumper, pick a model from the Video Router catalog. seedance-2.5 accepts 4 to 30 seconds at 480p, 720p or 1080p, and wan-3.0 accepts 2 to 30 seconds. Read capabilities from GET /v1/video-router/models because every model has its own envelope.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: course-bumper-001" \
  -d '{
    "model": "seedance-2.5",
    "prompt": "Clean title-card style opener for an online course, soft light, slow push-in",
    "resolution": "720p",
    "duration": 5,
    "aspect_ratio": "16:9",
    "mode": "async"
  }'

Cost of the join

The timeline charges $0.10 per output minute, rounded up, with no model inference (Timeline 1.0 docs). A 9-minute lesson with a 5-second bumper is 9 minutes and 5 seconds of output, so it rounds to 10 minutes and costs $1.00. Plan around that rounding: if the lesson is 9:57, a bumper pushes the render into the next minute.

  • Reuse one generated bumper file across all modules and join it per lesson.
  • Keep the sale trailer as one upload and the lessons as one upload each.
  • Run the free plan endpoint first to read billable minutes before you render.

Re-check Podia's page before you size a catalogue, since the plan counts are Podia's to change.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume