# Chromeless UI on Web

A chromeless player provides playback capabilities without rendering a user interface. Your application is responsible for creating every control, displaying player state, and connecting interactions to the OptiView Player API.

Choose this approach when you need complete control over the UI and UX, cannot use Open Video UI components, or are targeting an environment that requires a fully bespoke implementation.

Building from scratch requires a solid understanding of playback states, events, media tracks, accessibility, error handling, and platform-specific behavior.

Some features are implemented on top of the default UI and are unavailable in a chromeless player. For example, the [Up Next](https://docs-preview.optiview.dolby.com/pr-873/theoplayer/how-to-guides/web/miscellaneous/up-next.md) feature and API depend on the default UI.

Continue with [Getting started](https://docs-preview.optiview.dolby.com/pr-873/theoplayer/how-to-guides/web/ui/build-chromeless-ui.md) to create a `ChromelessPlayer` and map the first controls to the Player API.