h265web.js is built for real browser video delivery: HEVC/H.265, AVC/H.264, AV1, WebRTC, live and VOD, VR360 viewing, ZLMediaKit / PyMKUI integration, WebCodec, WASM decode, MediaInfo, snapshots, fullscreen and multi-instance playback.
Built and refined continuously since 2017, h265web.js PRO delivers mature browser playback with broad feature coverage and strong performance.
Ready-to-use integration and troubleshooting skills, including stable volume and experimental SDR super resolution. Start here even if you have not read the docs.
Download the SDK repository. Keep both complete folders under skills/, including templates and references.
Get the skills on GitHubCodex: ask $skill-installer to install the two GitHub skill directories, or copy them into your project’s .agents/skills/. Other assistants use their own skill import.
Step-by-step installation and examplesUse h265web-bootstrap for new players and app integration. Use h265web-troubleshoot for black pictures, missing audio, loading errors or inactive SR. Provide your framework, media and SDK location.
Use $h265web-bootstrap to integrate h265web.js into my React project. Add play/pause, stable-volume and experimental SDR super-resolution switches. SR should start one available step up, with Automatic as an option. Read my project’s SDK/media configuration, handle cleanup and verify actual playback.
Replace React with your framework. Select the installed skill in your assistant, or invoke it by name; this prompt goes into a conversation, not a terminal.
The point of this homepage is not to compare marketing slogans. It is to show where browser-native playback stops, where the old open-source branch stops, and where the current free PRO branch keeps going.
Show the current h265web.js PRO capability set in one focused matrix.
Independent switches during playback, actual processing states and clear reload actions. Both effects default to off.
These logos are not there to decorate the page. They are there to show this SDK has already been pushed through real browser playback scenarios.
The number matters because this project is not just a demo player. It is already serving repeated playback demand in production-style environments.
Whether you are evaluating browser playback, integrating the SDK, or comparing live and VOD paths, these are the fastest ways to reach the project and the maintainer.