Browse documentation
Start with the workspace hierarchy
A workspace is your private working area. Collections group related work inside it, while videos retain their source, playback assets, player configuration, publication, and analytics context.
Tags belong to the workspace and can be assigned across its videos. They cannot cross workspace boundaries.
- Workspace: the private working area
- Collection: the working library
- Video: the durable media record
- Assets and tags: the supporting material
Move from a source to ready playback
A custom upload is stored as an immutable private original. Background processing prepares hosted adaptive playback and public visual derivatives such as posters and previews without sending public media through the application server.
A YouTube-backed record follows a different source path while remaining organized in the same library and publication workflow.
- 1 Create the video record
- 2 Add or connect the source
- 3 Wait for playback readiness
- 4 Review the generated visual assets
Configure first, publish deliberately
Playback readiness does not automatically make a hosted player public. Player settings, approved website origins, and publication are explicit choices.
Publishing creates the stable public identity used by the script or iframe install. Update settings in the dashboard instead of replacing anonymous snippets across every page.
Operate the video after launch
The product keeps viewing activity and quality-of-experience signals attached to the video that produced them. This makes it easier to distinguish a content problem from a slow start, buffering issue, or incorrect publication setting.
- Playback and engagement activity
- Startup and buffering context
- Upload and processing visibility
- Plan and usage context
Still looking for the missing step?
Browse the Help Center for concise answers, or send us the page and result you are trying to produce.