Content model
Episode, season, series, and library: four content levels
A single video file is not the same thing as an episode, a season, a series, or a managed content library.
Direct answer: An episode is a release unit; a season groups episodes; a series carries the continuing story and shared assets; a library is the larger collection used for programming and operations.
What to keep clear
- Use episode for timing, subtitles, audio, and delivery checks.
- Use series context for characters, terminology, rights, and reusable decisions.
- Use library-level views for catalog, territory, language, and performance planning.
These levels answer different operational questions. A file can be playable while still being attached to the wrong episode or language. A series can be complete while a delivery package is missing one episode. A library can contain several versions of the same story with different rights and release states.
Keeping the levels separate helps Studio and API workflows attach the right review and delivery state to the right object. It also prevents a project conversation from collapsing into an ambiguous request to process a folder.
Related theme: Short-drama format and economics
Sources and scope. Weydub public Studio and delivery documentation. Checked 2026-08-25. This entry defines a working concept; it is not a universal legal, market, or performance claim.