Stremio Community v5: a WebView2 shell around the Stremio web UI
🐚 WebView2 and Qt6-based shell, desktop app for Stremio with latest web ui support
At a glance
- What is it?
- Stremio Community v5 is a Windows desktop shell that renders the Stremio web interface in WebView2 and hands playback to an integrated MPV player, adding upscaling, HDR, Discord status and autoupdate on top. It ships as a beta build, is licensed GPL-3.0, and Linux and macOS builds are still marked as coming soon.
- Who is it for?
- Use Stremio Community v5 if you are on Windows and want the Stremio web interface with a native MPV pipeline behind it, especially for upscaling, HDR, hardware decoding and subtitle styling that the plain web UI does not offer. Skip it if you need Linux or macOS today, since the README lists those builds as coming soon, or if a GPL-3.0 application is not acceptable in your environment.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 83 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 22, 2026, and from our analysis. They are not legal advice.
Editorial analysis
A WebView2 shell around the Stremio web interface
The project is not a fork of Stremio's own client. The README describes it as a Stremio Desktop app with the latest Stremio web UI v5, built with WebView2, and the repository description calls it a WebView2 and Qt6-based shell. The primary language is C++, and the repository ships a CMakeLists.txt, a src directory, a deps directory and a .gitmodules file, so the application is compiled from source and its dependencies are pulled in as submodules.
Two details in the repository state are worth more than they first appear. The default branch is named webview-windows, which tells you that the WebView2 path is the active line of development. And the release list is still on the 5.0.0 beta numbering, with 5.0.0-beta.22 published on 2026-08-01 as the newest release.
The reason a shell exists at all is that a web interface on its own leaves some things to the browser. Rendering Stremio Web v5 inside a WebView2 window gives the app a real window title bar, a taskbar entry, a native file dialog and a place to hook an external player. The README claims the payoff in one line, always up-to-date with Stremio Web v5, because the interface comes from the web app rather than from a copy of it maintained in this repository.
MPV handles decoding, the web view handles the interface
The feature list is really a description of what MPV can do, exposed through a shell that also loads addons. Native playback is credited to an integrated player for native 4K playback, hardware decoding, and fast video performance, and the full MPV support entry names the specific knobs: any hwdec, gpu-api or gpu-context, with d3d, opengl and vulkan given as examples. Full HDR support and Dolby Atmos support are both attributed to the same underlying player.
Upscaling is a separate feature entry rather than a general claim, and the README points to a dedicated section for the upscalers it knows about, listing Anime4k and noting that it is included by default. Video upscaling support is scoped to anything MPV supports, and the comparison screenshots in the README are labelled as an Anime4k plus auto HDR versus official Stremio v5 comparison, with the caveat that HDR looks over-exposed in screenshots. That is a small honesty note in a project that otherwise sells on picture quality, and it is worth reading the images as approximate rather than as a verdict on the official client.
The thumbnail preview entry is narrower than it sounds: it is ThumbFast support, and the README says it works best on local files, with the size adjustable. Local file playback covers anything MPV and ffmpeg support, using open with stremio or drag and drop, and local subtitles can be added by drag and drop while a video plays, with styling through MPV configuration.
Scoop and winget are the install paths that are actually maintained
The README's installation section lists five routes for Windows x64 and x86, and two of them are package managers with copy-and-paste commands. The winget route is the shortest:
# Install
winget install Zaarrg.StremioCommunity
# Update
winget upgrade Zaarrg.StremioCommunity
# Uninstall
winget uninstall Zaarrg.StremioCommunityThe scoop route adds a bucket first, because the package lives in a bucket maintained by the project author rather than in the default collection:
# Install
scoop bucket add zarg https://github.com/zaarrg/scoop
scoop install stremio-desktop-v5
# Update
scoop update zarg
scoop update stremio-desktop-v5
# Uninstall
scoop uninstall stremio-desktop-v5The scoop sequence matters for an unattended setup: the bucket add step has to succeed before the install, and an update that only runs scoop update stremio-desktop-v5 will not refresh the bucket definition itself.
The third package manager is the problem child. The README marks Chocolatey with a struck-through heading and puts a warning inside the command block: Chocolatey is not updated, use scoop or another installation method. The commands are still shown, choco install stremio-desktop-v5 -y and the matching upgrade and uninstall lines, but the warning is the actual guidance.
Two manual routes round out the list. The installer is described as the recommended one, with stremio-5.0.0-x64.exe and stremio-5.0.0-x86.exe, and the archive route gives stremio-5.0.0-x64.7z and stremio-5.0.0-x86.7z to extract and run stremio.exe from. The portable version is a fully portable package that includes WebView2, which matters on a machine where the WebView2 runtime is not present. The README also carries a warning to uninstall stremio-desktop v4.x.x first, because otherwise there might be issues.
Addons install the v4 way, while the interface stays on v5
The compatibility story is stated in one feature entry: easy addon install, just use the install button like stremio v4, no need to copy paste urls. That is a deliberate split. The interface is the v5 web UI, and the addon workflow deliberately keeps the older, button-based flow, which means a user arriving from the v4 desktop app does not have to learn a new way of adding sources.
What the shell adds on top of the web interface is mostly integration with the desktop. Discord Rich Presence reports what you are watching on your Discord profile, with the README showing live activity states such as Discovering, Watching and Paused. App settings cover CloseOnExit, PauseOnMinimize and PauseOnLostFocus, and more of the same kind of behaviour switches. A built-in autoupdater removes the need to keep downloading from GitHub, which pairs sensibly with the frequent release line of this project.
Picture in Picture mode and Windows dark mode support are listed as well. Note the platform scope of both: dark mode is described as Windows dark mode support, and the whole application, from the WebView2 runtime to the Win32 resource file in the repository root, is built for Windows.
What you can actually stream is decided by the addons a user adds, not by this repository. The repository contains the application code and the installer scripts, and the addon URLs live outside it, which means the project is a player and a shell rather than a content source.
The release line is still on beta numbering and the last push was on 2026-08-01
Three releases are recent enough to describe, and the gaps between them are the interesting part. Version 5.0.0-beta.20 was published on 2025-10-08, 5.0.0-beta.21 on 2025-12-07, and 5.0.0-beta.22 on 2026-08-01. The last push to the repository was on 2026-08-01 as well, so the newest release and the newest source change are the same day. Between the first two of those dates sit two months, and between the second and the third sit about eight months, so this is not a project with a metronomic release cadence.
The version scheme deserves a word. The names on the releases are 5.0.0-beta.22 with the bracketed form Stremio Community 5.0.22, and the installer filenames use stremio-5.0.0-x64.exe, so the beta counter and the marketing version move separately. If you pin versions in an automation script, pin the package version, not the tag.
Cross-platform support is the other open question. The installation section covers Windows x64 and x86, and then says Linux and macOS are coming soon, with a note that a Linux and Mac release will take considerable time because they need their own build with OS specific technologies. The description mentions Qt6 alongside WebView2, which suggests the shell code is not tied to the Windows web view, but the README gives no timeline and no build instructions for those platforms.
The source tree shows a CMake build with vendored dependencies
The top-level listing of the repository describes the build without needing a line of prose. It contains .gitmodules, .idea/, CMakeLists.txt, LICENSE.md, README.md, build/, deps/, docs/, extensions/, images/, src/, stremio.rc, utils/ and version/.
Several of those entries carry information. A .gitmodules file means the dependencies are not vendored directly but referenced as submodules, and the deps directory holds the checked-out copies, so a first build has to initialise submodules before it can compile. A CMakeLists.txt at the root confirms a CMake build rather than a project-specific script. The stremio.rc file is a Windows resource script, consistent with the icon and version metadata of a native executable, and the version/ directory is a natural place for the version string that the release names reflect.
The extensions/ directory is worth a second look for anyone evaluating the addon model, since it suggests the shell can register or ship its own extensions, and the utils/ and docs/ directories indicate helper code and documentation kept alongside the main sources.
Licensing is straightforward to state. The project is licensed GPL-3.0, and LICENSE.md sits in the repository root next to the README, so the terms are available without leaving the project. For a GPL-3.0 program, the practical points for an organisation are that distributing a modified binary carries the same licence obligations, and that the source for those modifications has to be offered. This is not legal advice; it is the reason to read LICENSE.md and consult whoever handles licence compliance before shipping this binary to users.
Where this shell is the wrong choice
The most obvious case is any machine that is not Windows. There is no macOS or Linux build, and the README is direct that those need their own build with OS specific technologies, so an evaluation today has to accept a Windows-only tool or wait.
The second case is a team that wants a stable, auditable dependency. The releases carry beta in their names, the release gaps are uneven, and the guarantee that the interface matches Stremio Web v5 is a moving target: the shell is deliberately downstream of a web application that changes on its own schedule. There is no statement in the README about how the shell reacts when the upstream web interface changes shape, and no published compatibility matrix for the beta series.
The third case is a review process that needs to read the code before running it. This repository does have sources, and the licence is clear, which puts it ahead of a closed binary. But the dependencies arrive as submodules from their own repositories, and the build environment for a WebView2 plus MPV application is not described anywhere in the README, so a source review means reconstructing a build that the project does not document.
And then there is the comparison the README makes itself, in the screenshots labelled Anime4k plus auto HDR versus official Stremio v5. The argument for this shell is the extra layer around the web interface, native playback through MPV, upscaling, and desktop integration. If none of that is what you are after, the first-party client is the simpler path, and this repository offers no advantage over it beyond those additions.
Editorial conclusion
Use Stremio Community v5 if you are on Windows and want the Stremio web interface with a native MPV pipeline behind it, especially for upscaling, HDR, hardware decoding and subtitle styling that the plain web UI does not offer. Skip it if you need Linux or macOS today, since the README lists those builds as coming soon, or if a GPL-3.0 application is not acceptable in your environment. Before installing, check the release tag you pick, because the latest published build is still 5.0.0-beta.22, and confirm that the winget package Zaarrg.StremioCommunity or the scoop bucket zarg points at the version you intend to run.
Frequently asked questions
How do I install Stremio Community v5 on Windows?
The README lists winget, scoop, Chocolatey, an installer executable and a portable archive. The maintained package manager route is scoop, which needs the bucket added first with scoop bucket add zarg, then scoop install stremio-desktop-v5, while winget uses Zaarrg.StremioCommunity.
Does Stremio Community v5 work on Linux or macOS?
Not yet. The installation section covers Windows x64 and x86, and the README says Linux and macOS are coming soon, noting that a release will take considerable time because it needs its own build with OS specific technologies.
Which video player does Stremio Community v5 use?
An integrated MPV player. The README credits it for native 4K playback, hardware decoding, any hwdec, gpu-api or gpu-context such as d3d, opengl and vulkan, full HDR support, Dolby Atmos, upscaling, picture in picture and subtitle styling through mpv configuration.
What licence is Stremio Community v5 released under?
GPL-3.0, with a LICENSE.md file in the top-level directory of the repository. Any modified binary you distribute carries the same obligations, so read that file before redistributing it.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/zaarrg-stremio-community-v5)Was this useful?