Better xCloud userscript for browser-based Xbox gaming

What Better xCloud changes in the browser

Better xCloud targets a narrow part of the Xbox ecosystem: the browser experience at xbox.com/play. The repository describes it as a userscript that improves Xbox Cloud Gaming and also allows Remote Play to be used on the xCloud website. That distinction matters because the project is not presented as a replacement console, a separate game installer, or a general-purpose Xbox client. It modifies or augments a web experience that already depends on Xbox services and browser compatibility.

The supported-platform list is broad. Windows, macOS, Linux, SteamOS, Steam Deck, Android, Android TV, Meta Quest VR headsets, iOS, and iPadOS are all named in the README. Android support is linked to the separate redphx/better-xcloud-android repository, so the exact implementation for that platform should not be inferred from the main TypeScript project. The core audience is therefore players who reach xCloud through a browser and want additional controls or behavior around the gaming session.

The README does not present a complete feature matrix. It specifically calls out mouse controlling, custom touch controls, bug fixes, and an IPv6-related idea acknowledged from another project, but it does not explain the settings, feature flags, or browser behavior for most of these features in detail. The official homepage is identified as the place for full documentation. A prospective user should distinguish the broad platform statement from confirmed control availability on each platform. Touch controls and mouse controlling may not mean that every supported device receives the same interface.

The userscript architecture and repository workflow

The repository is primarily TypeScript and uses a browser userscript model rather than a conventional server application. The package metadata identifies src/index.ts as the module entry point, declares ES modules, and includes a browserslist target of Chrome >= 80. The build-related files include build.ts, build.sh, and a dist directory, which indicates that source code is compiled or packaged into a browser-consumable artifact before release.

The repository also includes resources, scripts, and src directories, along with TypeScript, ESLint, and Stylus tooling in package.json. Those entries support the view that the project contains browser-side code plus styling or generated resources. They do not, by themselves, reveal the runtime order of individual features or the exact injection point on xbox.com/play. The README does not document those implementation details, so this article does not claim that Better xCloud uses a specific DOM selector, browser API, or transport protocol.

The build configuration is relevant to maintainers rather than ordinary players. A development workflow can be inferred from the package metadata and build files, but the README provides no installation or contribution commands for contributors. It also restricts accepted pull requests to custom touch controls and bug fixes. That narrow contribution policy suggests that feature work outside those categories is not part of the normal contribution path.

Installing Better xCloud on a supported device

The README directs users to the official project homepage for device-specific installation instructions. It does not include a direct install command, userscript-manager name, browser extension command, or copy-and-paste configuration block. That omission means there is no confirmed command that can be reproduced safely from the README.

Start at the official homepage:

https://better-xcloud.github.io

Follow the instructions shown there for the device and browser combination you use. The README identifies the supported platform families, but it does not map each platform to a particular userscript manager or browser. After installation, open xbox.com/play and check whether the Better xCloud controls or behavior appear. The repository does not document a visible success marker, a settings menu, or a troubleshooting procedure, so the safest first check is the project homepage's own installation guidance followed by the Xbox web page itself.

Do not download the userscript from `betterxcloud.net` or another unofficial site. The README explicitly warns that Better xCloud is provided only through the official repositories and identifies `betterxcloud.net` as a fake website. It also says to report bugs through the repository Issues area or its Telegram channel rather than the `/r/xcloud` subreddit. These are specific project instructions, not general security recommendations.

Using Remote Play through the xCloud website

Remote Play is the second major capability named by the repository. The README states that Better xCloud allows Remote Play on the xCloud website, which means the userscript is intended to bring an Xbox Remote Play use case into the browser-based xCloud page rather than require users to locate a separate supported flow.

The README does not state whether Remote Play requires an Xbox account, a supported controller, a particular network configuration, or a separate service entitlement. It also does not give a browser-specific compatibility matrix. That makes account and controller verification part of the adoption decision. A user should confirm that Remote Play is available to their account and that their chosen input method is supported before treating the script as a complete Remote Play solution.

Mouse controlling is acknowledged as inspired by the Mouse spinning feature in the Yuzu emulator, while custom touch controls are one of the two accepted pull-request categories. Those references identify areas of development interest, but the README does not claim feature parity with Yuzu or explain how mouse spinning behaves in Better xCloud. Users who need detailed latency, touch mapping, or controller behavior should consult the official documentation rather than infer it from the acknowledgements.

Practical limits of a browser userscript

The main constraint is dependence on the browser page and its surrounding Xbox service. A userscript can improve a page, but it cannot remove account eligibility, server availability, network requirements, or game compatibility. The project is therefore the wrong tool for someone who needs a guaranteed standalone Xbox streaming client or a solution that works without the xbox.com/play page.

There is also a feature-availability gap. The README lists many platforms, but it does not state that every feature works identically on each one. Mouse support on a desktop browser, touch controls on Android, and Remote Play behavior on a headset are different paths. The separate Android repository is another sign that platform integration has more than one layer.

Better xCloud is released under the MIT license, which permits use and modification under that license's terms, but this article does not provide legal advice. The repository's disclaimer says to use the project at your own risk and notes that it is not affiliated with Xbox. The README also warns that pull requests are limited to custom touch controls and bug fixes. These limits matter when planning a fork or local modification.

Release cadence, maintenance, and upgrade work

The repository is not archived. Its last push was on 2026-10-04, and the recent release history includes v6.7.12 on 2026-07-14, v6.7.11 on 2026-07-01, and v6.7.10 on 2026-05-19. These records show that versions were published during 2026, while the TypeScript default branch indicates that source-level development is organized around that language.

For players, an upgrade likely means replacing the installed userscript with the version obtained through the official installation documentation or release process. The README does not document automatic updates, update notifications, rollback, or compatibility migration steps, so none should be assumed. For contributors, the presence of a lockfile, build files, TypeScript configuration, and generated distribution files indicates that adopting a newer source revision may involve the project's build workflow rather than editing a single browser file. The exact build command is not documented in the README.

The project uses a donation link and a Crowdin translation process, but those details do not change the technical adoption boundary. The concrete maintenance check is the official repository and homepage: users should confirm that the version offered there matches the page they use, and contributors should read the repository's build configuration before modifying source code.

Editorial conclusion

Better xCloud is suitable for players who specifically want a userscript-based improvement to xbox.com/play or Remote Play in a supported browser. It is not a suitable standalone Xbox client, and users should first confirm their device and browser support, follow the official homepage installation instructions, and review the MIT license and own-risk disclaimer before adopting it.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. redphx/better-xcloud on GitHub
5. Releases