The last major release of Streamlike was in June 2018. Its ongoing evolution (72 updates have been released, or about 9 per year) demonstrates the soundness of the V5’s design at launch and its durability. However, the time had come for a major overhaul.
Over the past eight years, business needs and requirements have diversified, usage patterns have evolved, and the technological landscape, integration tools, and distribution infrastructures have changed. AI has also become a major part of the platform’s development and functionality.
In six bullet points, Streamlike’s V6 offers:
- enhanced eco-design: more efficient and faster encoding, a streamlined console and player, and 0 bytes loaded before a click
- accessibility and multilingual support: multitrack media, automatic multilingual subtitling (including for live streams), closed captions (CC), and audio description
- modernized players (THEOplayer/OptiView and now HLS.js), as well as an audio player with a clickable waveform
- improved console usability without disrupting user habits: faster navigation, a new design scheme, and new graphics
- completely rewritten online documentation with improved search functionality
- easier integration via a kit for AI assistants (Claude skill and Gemini gem) and comprehensive documentation of the 42 API endpoints.
Eco-Design
In line with our responsible streaming approach, which we launched in 2019, we have redesigned our encoding processes to adapt to the nature of the content. At the same resolution, we use less bandwidth for screencasts or webinars and more for more dynamic videos. Bandwidth is also optimized based on the frame rate and the output resolution. Finally, users retain the option to adjust a complexity setting for a specific video or as a default—for example, to increase their level of digital frugality by one notch. Greater frugality should be a choice, not an imposition.
Encoding speed has been greatly increased through parallel processing, which also results in reduced machine usage time… without using a GPU ;-).
To minimize the number of transcodings and make the most of each codec’s strengths, x264 is used up to high definition (1080p), and x265 is added starting at that resolution. Devices capable of decoding x265 will benefit from a bitrate reduction of at least 30% while maintaining the same quality, starting at high definition.
Compare the encoding quality at different bitrates by zooming in on this video. And if you have time, look for Charlie 😉
On the streaming side, the “audio-only” mode—which streams only the audio when a video isn’t being watched—has been redesigned for even greater lightness and efficiency.
At the application level, we’ve reduced the scripts loaded by the player by 74% and those loaded by the console by 25%.
Accessibility and Multilingualism
The updates fall into two categories: audio and metadata.
On the audio side, standard videos can now be converted into multilingual videos directly from the console. The added audio tracks can be alternative languages (dubbing, translation, etc.) or audio descriptions (a narrated version intended for the visually impaired). A video can therefore have multiple language tracks and an equal number of audio description tracks. The nature of each track is clearly indicated in the player. The default track can be selected during embedding or in a shared link.
A video with audio description for the visually impaired, which you can turn
on or off using the button that looks like a pair of headphones.
Multitrack videos are a type of content that can be grouped separately in the media library.
In terms of metadata, automatic multilingual subtitling is available for both live and VOD content. The real innovation is the introduction of CC subtitles for the hearing impaired, which include additional text to describe what cannot be understood from the video alone. These subtitles are indicated by a CC symbol in the player’s control bar.
In summary, a video can have two types of audio tracks (normal and “AD”) and two types of subtitles (normal and “CC”) per language.
A video with closed captions (CC) for the hearing impaired, which you can turn
on or off using the captions button.
Player Updates
The most noticeable change will be the introduction of an audio player with an interactive waveform, similar to SoundCloud, featuring customizable colors. Segments and highlights, color-coding for the currently playing section and when hovering over it, click-to-move functionality… The waveform is calculated during encoding, track by track for multitrack media. It offers a new experience for listening to podcasts.
Shift gears up and down with the new audio player!
As for video players, HLS.js is replacing video.js alongside OptiView (formerly Theoplayer). Both players function identically, support the same configuration settings (including the new “picture-in-picture” mode), respond to the same control commands from our API, and are fully customizable with “skins.” The code for both players is significantly more compact, and no video data is downloaded before the user clicks.
So why still have two players? To avoid putting all our eggs in one basket. The players evolve in parallel with the platform. Redundancy means greater security.
Console Usability
The visual redesign is noticeable, but we haven’t revolutionized anything. The menus remain in their usual places, but the page layout is clearer and navigation is smoother. Thanks to the streamlined code, information loads and refreshes faster. The messages are more explicit.
Progress on encoding is now visible. A video is now online within seconds of being uploaded, while it is still encoding.
The typography has been standardized, lists update automatically, drag-and-drop functionality has been rewritten, and the media details page has been redesigned.
The functionality remains the same; the interface has evolved.
Online Documentation
Given the small number of questions we’ve received over the past eight years from the hundreds of daily users of the platform, one might wonder whether online documentation is really necessary. The answer is yes. The features, configuration options, and solutions for improved productivity are growing in number. You might stumble upon them by chance or miss them entirely, but documentation is essential for getting the most out of the platform. A reference page may be less engaging but is quicker to consult than a 10-minute video tutorial. And if you feed the content to an AI, you’ll immediately get answers tailored to your specific use case.
Now, the search function identifies relevant sections and highlights the terms found. Screenshots are annotated, and optional services are indicated. Each user sees only the documentation corresponding to their permissions.
All user documentation is available in French and English.
Guided Integration
The online documentation for the API and web services has been completely rewritten. The expected objects and values for 1,529 fields have been described in detail. A “sandbox” allows you to test each “endpoint” or service.
Streamlike’s GitHub now includes a JavaScript SDK and SDKs for the API, web services, and StreamChat. Most importantly, it offers an integration kit for AI assistants (the Claude skill and the Gemini gem) that frees developers from having to know our endpoints, security rules, or player settings. Now, coding an app for Streamlike takes just a few prompts!
Launching September 14, 2026
It might sound like an oxymoron to a car enthusiast, but this Monday, September 14, our V6 is in-line 😉