# Customizable Video Player for OTT Platforms | White Label | Vodlix **Source:** https://vodlix.com/features/customizable-video-player **Summary:** A branded video player built for web, mobile and TV. Quality and speed controls, multiple audio tracks, next episode, casting and subtitles, carrying your identity. **Publisher:** Vodlix --- Customizable video player with adjustable look and feel, and full playback controls across every device. - **Feature Plan:** 2 - core-platform - front-end - mobile-app - tv-app ## The Player Is the Product Everything else on your platform exists to get somebody to press play. From that moment on, the player is the entire experience, and it carries your brand rather than ours. ### Where Your Audience Actually Spends Their Evening A viewer might spend two minutes browsing your catalogue and two hours inside the player. That ratio is worth remembering, because it means the player is not a component of your service, it is the part people will remember. A rough one loses you subscribers no amount of good content will win back: audio that will not switch, a scrubber that fights the remote, a spinner where the next episode should be. Vodlix ships a player built for long sessions on the devices your audience really uses, and it wears your identity rather than a vendor logo. #### Your logo, your colours The player takes your brand rather than announcing ours. Nothing in the frame tells a viewer which platform you built on, which is the whole point of running white label. #### Quality, speed and audio Viewers pick their resolution, run playback from a quarter speed to double, and switch between the audio tracks you published. Controls sit where people expect them rather than buried in a submenu. #### Straight into the next episode A series keeps its momentum. The next episode surfaces as the current one ends, so a viewer carries on watching instead of being returned to a menu to find it themselves. ### Under a Remote Control A player that feels natural with a mouse can be miserable with a directional pad, which is why the television build is laid out separately rather than scaled up from the web. Controls are large, focus is always visible, and the common actions sit where a thumb expects them without hunting. Seeking, switching audio, opening subtitles and jumping to the next episode all work from the remote alone. It is the same player and the same catalogue as everywhere else on your [TV apps](/features/tv-apps), simply arranged for the distance people actually sit from the screen. - mx-auto ### And in One Hand On a phone the player has to cope with interruptions, a rotating screen and a thumb doing all the work. In your [mobile apps](/features/mobile-apps) it handles portrait and landscape, keeps the position when a call arrives, and puts play, seek and settings inside easy reach rather than at the top of a tall screen. Downloads, casting to a television and picture in picture are all reachable from the same place a viewer is already looking. - mx-auto ### The Settings Behind the Player How the player behaves is configured once and applies everywhere it runs. Playback defaults, quality handling and the controls a viewer is offered are set in the admin area rather than per platform, so the experience on a television matches the one on the web without anybody maintaining two sets of rules. - mx-auto ### Everything the Player Plugs Into A player is only as good as what feeds it. Vodlix wires yours into the rest of the platform rather than leaving each piece to be solved separately. Your [subtitles and captions](/features/subtitles-and-captions) appear in the settings menu in every language you published. [Preview thumbnails](/features/thumbnail-preview) ride along the scrubber so seeking is aimed rather than guessed. [Adaptive streaming](/features/hls-mpeg-dash) shifts quality with the connection instead of stalling, and [DRM](/features/drm) protects the stream without the viewer ever meeting it. Where you run advertising, breaks play in this same player with their own progress and countdown, which is covered on the [advertising page](/features/advertisements). And because playback position is stored against the account, closing the player is never the end of a session, only a pause, as [watch history](/features/watch-history) picks it up on whatever they open next. **Q: Can the player carry our own branding?** Yes. The player takes your logo and colours, and nothing in it identifies Vodlix to a viewer. That is the point of a white label platform, and it applies to the player as much as to the rest of the storefront. **Q: What playback controls do viewers get?** Play and pause, seeking, volume, resolution, playback speed from a quarter through to double, audio track selection, subtitles, picture in picture and fullscreen. On a series the player also surfaces the next episode and the episode list. **Q: Does the next episode play automatically?** The next episode is surfaced as the current one finishes, so a viewer continues without going back to a menu to look for it. That single behaviour is responsible for a large share of the watch time any series catalogue produces. **Q: Can viewers choose their video quality?** They can, and adaptive streaming also shifts quality on its own as the connection changes. Where you want an upper limit, for instance reserving the highest resolution for a premium tier, that ceiling is set on the plan rather than left to the viewer. **Q: Does the player support multiple audio tracks?** Yes. Any audio tracks you publish against a title appear in the player settings, so the same film can carry an original language and one or more dubs without a separate upload for each. **Q: Can viewers cast to a television?** Yes. Casting from the mobile apps to a connected television is built into the player, so a viewer who starts on a phone can move it to the big screen without leaving the app. **Q: Is the same player used on every platform?** The same player and the same catalogue, arranged differently for each. The television build is designed around a remote rather than scaled up from the web, and the mobile build is built for one hand, because a single layout on all three ends up poor on all three.