Microdramas on YouTube: 6.5B views, TV up 90%. What to plan

YouTube says microdramas on the platform surpassed 6.5 billion views in the first half of 2026, with watch time up over 50% year over year and TV views of microdrama content up over 90% year over year. The same post calls the format mobile-first and says creators can now structure Shorts into seasons and episodes, with custom thumbnails and sequential playback across web, mobile and TV.

Those figures are from YouTube's blog post on Shorts Series and living-room features, read on 2026-10-03. They tell you the format is growing, and that TV is part of how it is watched. They do not tell you how a vertical Short is shown on a TV screen, and this post does not guess. Below, what the numbers support, what they leave open, and how to plan a season on Sume.

What do the numbers actually say?

Three growth figures and one note on where people watch. Over half of YouTube's top 100 creators have TV as their most watched interface, per the same page, which is a claim about those creators' audiences and not about microdramas in particular.

The page does not give a base for the 90% growth or a count of TV microdrama views, so do not turn it into a forecast. It names two creators using episodic multi-part storytelling with Shorts and gives no results for them.

Does TV change how I should shoot?

The post does not say. It does not name an aspect ratio for TV playback of Shorts, and the Shorts help page I read gives a 3-minute maximum and a 1080p maximum resolution but no TV guidance. Until YouTube states one, test it: upload one private episode and watch it on a TV before you commit a season to a format.

Keep the episode inside the limits you do know. A Short is up to 3 minutes and up to 1080p per the Shorts help page, so plan each episode under 180 seconds.

How do I plan a season on Sume?

Timeline 1.0 assembles one audio spine plus ordered video slots into one MP4, with up to 1800 seconds of audio and 1 to 200 slots, and its default output is 1080 by 1920. The plan route, POST /v1/timeline-1.0/plan, is unbilled and returns the duration and an estimated cost before you render, so you can check each episode's length first. Render costs $0.10 per ceil output minute at the public rate; confirm in GET /v1/catalog.

Episodes that share a cold open or a recap card can reuse the same clip through video[].source_in. Video trim cuts a range from a longer clip for $0.02 per job.

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/ep1-voice.wav", "duration_seconds": 150},
    "video": [
      {"source_url": "https://media.sume.com/artifacts/artf_demo/cold-open.mp4", "start": 0, "duration": 12},
      {"source_url": "https://media.sume.com/artifacts/artf_demo/scene-1.mp4", "start": 12, "duration": 138}
    ]
  }'

What should I check before I commit?

• Run the plan call for every episode and confirm each duration_seconds is under 180.
• Upload one private episode and watch it on a TV, since the post gives no TV format rule.
• Read the series rules in seasons and episodes before you name anything.
• Batch the season with episode-length batch production.
• For the build itself, how to make a microdrama as a Shorts series goes step by step.

What should I not conclude from the growth figures?

Do not conclude that any microdrama will reach TV audiences, or that a Short with a TV viewer earns more. The post gives growth rates for a category, not a result for an individual series, and it names no revenue figure for microdramas at all.

Do not conclude that vertical is the wrong format for TV either. The post calls the format mobile-first and says TV views are growing, which means vertical episodes are being watched on TVs today. What it leaves out is how they are framed there, and you can only answer that with a test upload.

What you can plan is the part you control: consistent episode length, a recap or cold open that earns the first seconds, and a season structure that a viewer can binge. Sume's timeline handles the assembly, and the numbers above are context rather than a promise.