Video.js 10 Release Roadmap and Current Status
Video.js 10 is in Release Candidate as of September 2026. The latest release is v10.0.0-rc.4 (Sep 26, 2026), which means the API is close to final and the project encourages adoption in real projects. General Availability (GA) is targeted for Fall 2026. If you need a stable, long-term-supported player today, the practical decision point is whether you can tolerate pre-GA churn until GA lands; if not, wait for the GA release.
Roadmap at a Glance
| Stage | Target | What it means for adopters |
|---|---|---|
| Tech Preview | Oct 2025 | Early look; not for production |
| Beta | Mar 2026 | Experimental adoption in real projects |
| Release Candidate | Sep 2026 | Close to stable; adoption in real projects encouraged |
| GA | Fall 2026 | Stable APIs; feature parity with Media Chrome, Vidstack, Plyr |
| Core Feature Parity | End of 2026 | Video.js core and contrib plugins migrated |
The current release, v10.0.0-rc.4, sits in the Release Candidate window. The project describes this phase as "close to stable" and explicitly encourages real-project adoption, but it is not yet the GA milestone.
What GA Will Deliver
Two commitments define the GA target:
- Stable APIs — the interface surface stops shifting, so upgrades stop breaking integrations.
- Feature parity with Media Chrome, Vidstack, and Plyr — Video.js 10 aims to match the capabilities of these comparable players at GA.
After GA, the roadmap extends to end of 2026 for core feature parity, at which point Video.js core and contrib plugins will have been migrated.
Why v10 Is a Ground-Up Rewrite
Video.js 10 is not an incremental update. The project rebuilt the player for modern development and performance, with two structural changes that matter for planning:
- UI separated from the media renderer. Every component is independent and connects through open API contracts, so you can swap or extend pieces without touching the renderer.
- Built for modern bundlers. The project supports tree-shaking and intelligent code splitting, so you start with a small player and add only what you need.
The performance claim is concrete: on a slow 4G connection, the site reports VJS 8 loading at 3.25s / 164kB versus VJS 10 at 1.01s / 51kB. If bundle size or startup time is a constraint in your project, that difference is the main reason to plan a v10 migration rather than staying on v8.
How to Decide When to Adopt
- Adopt now (RC) if you are building something new, can absorb occasional breaking changes, and want the smaller bundle and modular architecture. The project encourages real-project adoption at this stage.
- Wait for GA (Fall 2026) if you need stable APIs and a support commitment before committing production traffic.
- Wait for end of 2026 if your integration depends on specific core or contrib plugins, since plugin migration completes after GA.
Governance Note
The project is stewarded by a Corporate Shepherd elected by the Video.js Technical Steering Committee. That role is currently held by Mux, which took over from Brightcove in 2025. Mux was founded by Steve Heffernan, the creator of Video.js. This matters for adoption planning because it indicates who is funding ongoing development through the GA and plugin-migration milestones.