📄️ Getting started
Depending on the use case, there are multiple ways to integrate the Web SDK.
📄️ Configuration
Use these guides for the most common Web SDK configuration topics:
📄️ Autoplay
Some browsers allow autoplay with audio; some allow autoplay without audio, while some do not allow autoplay at all.
📄️ Authentication
Authentication for Vindral Live is done using the secret provided for you in Vindral Portal and using
📄️ Timed metadata
Vindral Live has support for sending timed metadata, also called cue points or out-of-band data.
📄️ Google Cast (Chromecast)
Vindral Web SDK supports Google Cast (a.k.a. Chromecast) devices, making it easy to build globally scalable, in-sync, second-screen experiences.
📄️ Fullscreen and PiP
While Vindral Live player has support for running in fullscreen mode and Picture-in-Picture (PiP) mode, there are some caveats to be aware of.
📄️ Vindral Player
Vindral Player is our ready-to-go web component-based player for easy integration into your web applications. It is ideal for customizing controls or when the embed solution is not sufficient.
📄️ WebCodecs & Offscreen Renderer
Vindral Web SDK supports low-level browser video decoding via the WebCodecs API and, when supported, off-main-thread rendering via an offscreen renderer backed by OffscreenCanvas. Together these can unlock a lower-latency, lower-overhead playback pipeline compared to the traditional MSE path, where drift management is harder to achieve. Whether hardware or software decoding is used is configurable — see Hardware acceleration and decoder latency.
📄️ API Reference
Use the reference that matches your integration layer: