What media providers and streaming formats does Vidstack Player support?
Vidstack Player supports audio, video, and blob sources; adaptive streaming via HLS and DASH; and third-party providers including YouTube, Vimeo, and Remotion. It also lists extensive live streaming support and server-side rendering (SSR). The exact provider set you can use depends on your framework and bundler setup, since Vidstack ships framework-specific entry points (for example, audio.tsx, video.tsx, hls.tsx, dash.tsx, youtube.tsx, vimeo.tsx, remotion.tsx).
Core source types
Vidstack's provider list starts with the basics you'd expect from a web media player:
- Audio — audio-only playback.
- Video — standard video playback.
- Blob — media loaded from a
Blob/object URL, useful for locally generated or in-memory media.
These are the foundation; the adaptive and third-party providers below build on the same player architecture.
Adaptive streaming: HLS and DASH
For adaptive bitrate streaming, Vidstack lists dedicated providers:
| Provider | Typical use |
|---|---|
| HLS | HTTP Live Streaming sources (commonly .m3u8) |
| DASH | Dynamic Adaptive Streaming over HTTP (commonly .mpd) |
Both are listed as first-class providers, so you can point the player at an HLS or DASH manifest and let the provider handle the streaming logic rather than managing segments yourself.
Third-party providers
Beyond raw media files, Vidstack lists providers for hosted platforms:
- YouTube
- Vimeo
- Remotion
This means you can embed media from these platforms through the same player component and API surface, instead of switching to each platform's own embed.
Live streaming
Vidstack states it has extensive live streaming support and API. If your use case is live rather than on-demand, this is the relevant capability to check — the provider list above (HLS/DASH in particular) is what typically carries live streams.
Server-side rendering (SSR)
Vidstack lists SSR support, which matters if you're building with a framework that renders on the server. Combined with the bundler plugins (Vite, SvelteKit, Nuxt, and others), this affects how you wire up providers in a given project.
How to choose a provider
- Self-hosted files → audio, video, or blob.
- Adaptive/live streams you control → HLS or DASH.
- Media already hosted on a platform → YouTube, Vimeo, or Remotion.
- Server-rendered app → confirm SSR support and use the matching framework/bundler plugin.
The provider you pick determines which source file/entry point you import (for example, hls.tsx vs youtube.tsx), so match the provider to your source type before styling or composing components.