GuideGetting Started
Browser support
Which browsers Video.js 10 supports, what looks different in older versions, and how to build the skins for your own browser targets
Video.js 10 supports current versions of the major browsers, back to the versions below. The Compat skin goes further back in Chrome, Edge, and Firefox. This page covers which versions we support, what looks different in older ones, and what to change when you build the skin CSS yourself.
Supported browsers
Default and Neutral reach 91.5% of global web usage, and Compat reaches 93.2%, according to caniuse-lite 1.0.30001810. These figures update when we update that data.
We test in and fix bugs for these versions. To reach older Chrome, Edge, or Firefox versions, use Compat. Its older versions apply to the packaged Compat skins, not to skins from the Shadcn registry.
Why these versions
Each minimum is the first version that has something the skin can’t work without:
Compat sets its colors with plain values, so it doesn’t need the newer color functions. Newer JavaScript APIs are feature-detected, so they don’t raise any minimum.
Default and Neutral need every CSS feature in this table, and none of them has a fallback. Compat needs only @layer; without the others, it loses a few layout details:
We don’t test browsers older than these minimums. In them, the skins break in the ways the last column describes.
What looks different in older versions
Every supported browser plays media and shows every control. A few CSS features the skins use arrived after the minimums. Browsers with them get the full design, and older ones get a fallback:
The skins keep each newer declaration inside an @supports check, so browsers that have the feature still use it.
Compat’s older versions also lack three features the other skins require:
Choose Compat for older browsers
Compat supports the oldest browsers, as the supported browsers table shows. It also leaves out two details that Default and Neutral add, which depend on browser support:
Compat still gets the popover and color fallbacks in the first table. See Skins to compare the skins in full.
Skins from the Shadcn registry
Packaged skins don’t use @scope: our build rewrites it into :where() selectors. Skins you add as source through the Shadcn registry keep it, because it reads more clearly in files you edit. That raises the minimums for one style:
Build the skin CSS yourself
We build the packaged skins for the supported browsers, so most projects need no changes. Your own build only matters when it processes the skin CSS.
Skins are stylesheets you import, such as @videojs/react/video/skin.css, so your bundler’s CSS pipeline processes them.
Turn off two Lightning CSS rewrites
Vite minifies CSS with Lightning CSS. When your browser targets include older versions, it rewrites two features the skins already handle, in every browser rather than only the older ones:
Exclude both:
Flatten @scope in registry skins
Lightning CSS leaves @scope alone. To support browsers without it, add a small PostCSS plugin that rewrites each @scope block into ordinary selectors, the same way we build the packaged skins. Most bundlers, including Vite and Next.js, run PostCSS before Lightning CSS.
Install PostCSS and its selector parser:
Add the plugin to postcss.config.mjs:
Flattened rules apply in source order instead of by @scope proximity, the same as in the packaged skins. Keep the Lightning CSS setting above so the colors still work.
Other environments
Related pages
Guides
- SkinsPackaged player designs that include both UI components and their styles.
- Customize skinsStyle a packaged Video.js skin or add its source to change controls, layout, styles, and interactions
- InstallationInstall Video.js packages and build an accessible, customizable video player with composable controls
- BundlersBundler requirements for Video.js package exports, CSS, and wrapper libraries