Screenbox wraps VLC's engine in a UWP shell for Windows and Xbox
LibVLC-based media player for the Universal Windows Platform
At a glance
- What is it?
- Screenbox is a LibVLC based player built on the Universal Windows Platform, so the interface is Fluent and gesture driven while the playback engine comes from VLC. Format support, settings and portability are all left undocumented.
- Who is it for?
- Screenbox is a reasonable choice on a Windows 10 build 1903 or newer machine, or on an Xbox console, when you want VLC's engine behind a Fluent interface with gesture seeking and Chromecast. It is not a fit if you need macOS or Linux, if you need a documented codec list, or if you need to build it without Visual Studio 2026 and its UWP workload.
- 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 received new commits within the last day.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- huynhsontung/Screenbox4,699 ★ · +267
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| huynhsontung/Screenbox | 4.4k | 4.7k |
267 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
UWP decides which machines you can run it on
The platform decision sits upstream of everything else. Screenbox is built on LibVLCSharp and the Universal Windows Platform, and the targets it names are Windows 10 version 1903 and up, Windows 11, and Xbox consoles. Xbox is the detail that surprises people: the same app is expected to run on a television. The consequence for anyone outside that set is plain. There is no macOS, Linux or Android build in this repository, and because the app is UWP rather than a plain Win32 executable, the minimum Windows build number decides whether the package installs at all. If you are choosing a player to carry across several operating systems, this repository only answers for Windows.
winget and the Store take different paths to the same app
There are two install routes and they are not equivalent in practice. The recommended one is the Microsoft Store, because installing through the store ensures the app stays up to date automatically. You do not need a Microsoft account to download apps from the store, which removes the usual objection to that route. The second route is winget, and the command names its source explicitly.
winget install screenbox -s wingetThe `-s winget` flag is what makes this work without the store front end, and that line is the only install command in the repository. What the two routes do not settle is what happens to updates afterwards. Automatic updating is attributed to the store install and nothing is said about winget updates, so a winget install needs its own update habit. The store identifier in the download link is 9NTSNMSVCB5L.
Building it needs Visual Studio 2026 and a .slnx solution
Contributors need a heavier toolchain than users do. The prerequisite is Visual Studio 2026 with the UWP development workload, then a clone, then a build.
git clone https://github.com/huynhsontung/Screenbox.gitAfter cloning you open `Screenbox.slnx` and build the solution with Ctrl+Shift+B, then set the platform to x64 and start debugging with F5. The solution file name is worth noticing, since it uses the newer `.slnx` format rather than the older `.sln`. The root also carries `Screenbox.sln.DotSettings` for shared IDE settings and `Directory.Build.props` for MSBuild properties. The documented debug path is x64 only. New contributors are pointed at `CONTRIBUTING.md` and at `docs/PROJECT_STRUCTURE.md` for the architecture overview.
Number row hotkeys and a YouTube style layout
The input model is where this player sets itself apart. Seeking and volume respond to gestures. Window resizing is bound to the number row, keys `1` through `4`, and the rest of the layout follows what the README calls a YouTube inspired hotkey layout. Playback is not confined to the main window either: picture-in-picture mode keeps the video out of the way, and saving the current video frame as an image is a direct action rather than a screen capture. Casting pushes the picture elsewhere through Chromecast support, and browsing and playing media over the network means sources are not limited to local files. What none of that settles is which containers and codecs LibVLC opens on a given build, since no format list appears in the README.
Six project directories and one architecture doc describe the layout
The file tree says more about how the app is arranged than the README does. Six project directories sit at the root: `Screenbox/` for the app itself, then `Screenbox.Core/`, `Screenbox.Core.Tests/`, `Screenbox.Lively/`, `Screenbox.UI/` and `Screenbox.VideoView/`. Names like `Screenbox.VideoView` and `Screenbox.Lively` imply a separated video rendering surface and a Lively related component, but the README does not say what either one contains, so that stays inference until you read `docs/PROJECT_STRUCTURE.md`, which it calls a detailed codebase architecture overview. The rest of the root is build and policy scaffolding: `Directory.Build.props`, `Screenbox.sln.DotSettings`, `ResXManager.config.xml`, `nuget.config`, `crowdin.yml`, `AGENTS.md`, `NOTICE.md` and `PRIVACY.md`. The licence is GPL-3.0, and `NOTICE.md` and `PRIVACY.md` are present but never summarized in the README.
Localization lands in the next minor update
Translation has two routes and one shared destination. Crowdin is the recommended tool, translations are automatically synced to GitHub, and they are published in the next minor update, which means a translation can sit in the repository for a release cycle before users see it. The source language is English, United States, and every localizable source file lives in the `Screenbox\Strings\en-US` directory. Two file types matter, `.resw` and `.md`, so documentation ships in the same translation unit as the UI strings. Folder names use IETF language tags, with `fr-FR` for French (France) and `es-ES` for Spanish (Spain) as the examples given, and each folder holds translated copies of the `en-US` originals. The local route bypasses Crowdin entirely: fork and clone, create your language folder under `Screenbox\Strings` if it is missing, copy over any missing files from `en-US`, translate the `.resw` and `.md` files, then commit, push and open a pull request.
No codec list, no settings reference and no portable build
Several things a player shopper would ask are simply absent, and each gap has a cost. There is no codec or container list, so the format support you inherit is whatever LibVLC gives you on that Windows build, with nothing in the documentation to tell you which build that is. There is no settings reference and no default for gesture sensitivity, and picture-in-picture and Chromecast are named without any description of how they behave. There is no statement about a portable or standalone executable: the documented paths are the Store and winget, and a sideloaded build is not one the README acknowledges. The feature list itself closes by promising more to come rather than laying out anything you can plan against. What you can check quickly is the release cadence, with v0.22.0 on 2026-09-12, v0.23.0 on 2026-10-04 and v0.24.0 on 2026-10-26.
Editorial conclusion
Screenbox is a reasonable choice on a Windows 10 build 1903 or newer machine, or on an Xbox console, when you want VLC's engine behind a Fluent interface with gesture seeking and Chromecast. It is not a fit if you need macOS or Linux, if you need a documented codec list, or if you need to build it without Visual Studio 2026 and its UWP workload. Before switching, check which release you actually get: v0.22.0, v0.23.0 and v0.24.0 shipped inside seven weeks, so the packaged build moves fast, and read PRIVACY.md in the repository root, which the README never summarizes.
Frequently asked questions
How do you install Screenbox?
The recommended route is the Microsoft Store, because installing through the store keeps the app up to date automatically and no Microsoft account is needed to download from it. The alternative is winget, using `winget install screenbox -s winget`. Screenbox needs Windows 10 version 1903 or newer, Windows 11, or an Xbox console.
Is Screenbox better than VLC?
Screenbox is built on LibVLCSharp, so the playback engine underneath is VLC's. What differs is the shell: a Fluent design interface, gesture seeking and volume, window resize hotkeys on the number row `1` to `4`, a YouTube inspired hotkey layout, picture-in-picture and Chromecast support. The README does not compare the two on performance.
Is Screenbox open source?
The repository is licensed GPL-3.0, with `LICENSE`, `NOTICE.md` and `PRIVACY.md` at the root. The playback engine is not part of this codebase: it comes from LibVLCSharp, and the app ships as a Store package or through winget.
Is Screenbox free?
The source is published under the GPL-3.0 licence. The README names two install routes, the Microsoft Store and winget, and describes no paid tier, subscription or paid edition, though it also does not state a price either way.
How does Screenbox compare with mpv?
The repository does not mention mpv anywhere. It describes Screenbox as a LibVLC based player with a Fluent interface, gesture support, picture-in-picture and Chromecast support, available on Windows 10 version 1903 and up, Windows 11 and Xbox consoles.
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/huynhsontung-screenbox)Star history chart for your README
[](https://hysenlabs.com/projects/huynhsontung-screenbox)Was this useful?