Every article tag can be clicked to get a list of all articles in that category. Every article tag also has an RSS feed! You can customize an RSS feed too!
We do often include affiliate links to earn us some pennies. See more here.

Steam for Chrome OS is here. For real this time, they've actually released it, unlike when they claimed it was released during their recent developer event. Now though it's here at an "alpha-quality" level, meaning prepare for bugs and other weirdness.

Not only will this help those using Chromebooks do some gaming but Linux gaming as a whole too. Chrome OS is powered by Linux, and the Steam client on Chrome OS is the Linux version inside their special container — it works for both native Linux games and Windows games run with Steam Play Proton. Although, you do need to enable Steam Play manually (same as on a normal Linux desktop).

Starting with Chrome OS version 14583.0.0 which is in the "Dev" channel, here's what Chromebooks are currently supported for it (as long as they don't have an i3 CPU or less than 8GB RAM):

  • Acer Chromebook 514 (CB514-1W)
  • Acer Chromebook 515 (CB515-1W)
  • Acer Chromebook Spin 713 (CP713-3W)
  • ASUS Chromebook Flip CX5 (CX5500)
  • ASUS Chromebook CX9 (CX9400)
  • HP Pro c640 G2 Chromebook
  • Lenovo 5i-14 Chromebook

There's a number of issues to begin with like anti-cheat not working with Proton games (even those with it turned on for Linux), Windows games using DirectX 12 don't start and more. You can see the list of issues, some tested games and instructions on their "Steam on Chrome OS Alpha" website.

Article taken from GamingOnLinux.com.
Tags: Google, Misc, Steam
22 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
The comments on this article are closed.
6 comments

Linas Mar 22, 2022
View PC info
  • Supporter Plus
The architecture of Chrome OS is really overcomplicated. They insist on running everything in those "containers", which are actually more like a full blown VM's, because not even the kernel is shared with the host. That is why everything is in constant alpha, and takes forever to integrate into the system. Just seems so counter-productive to me.
Purple Library Guy Mar 22, 2022
Quoting: LinasThe architecture of Chrome OS is really overcomplicated. They insist on running everything in those "containers", which are actually more like a full blown VM's, because not even the kernel is shared with the host. That is why everything is in constant alpha, and takes forever to integrate into the system. Just seems so counter-productive to me.
All for the purpose of deliberately crippling the OS so nobody can do anything much except run the browser. It's not bad to use . . . until you want to do something exotic, like save a word processing document to your thumb drive.
Eike Mar 22, 2022
View PC info
  • Supporter Plus
Quoting: Purple Library GuyAll for the purpose of deliberately crippling the OS so nobody can do anything much except run the browser. It's not bad to use . . . until you want to do something exotic, like save a word processing document to your thumb drive.

That's so nineties, though!



;)
gradyvuckovic Mar 22, 2022
Awesome. That's another place where any game compatible with Proton will run. (Once it's out of alpha of course. seems to have plenty of issues for now, but that will change fast.)

The more places you can buy, run and play games that are compatible with Linux, the more incentive there is to make games that you can buy, run and play on Linux. It'll help, even if just a little bit, boost the marketshare a bit further, eventually.
Vulphere Mar 23, 2022
Chromebooks/ChromeOS support for Steam would provide a good boost for Linux gaming
Samsai Mar 23, 2022
Quoting: LinasThe architecture of Chrome OS is really overcomplicated. They insist on running everything in those "containers", which are actually more like a full blown VM's, because not even the kernel is shared with the host. That is why everything is in constant alpha, and takes forever to integrate into the system. Just seems so counter-productive to me.
Some people have been suggesting it's because this separation would allow them to swap out the system underneath if they want to. So, they could swap out the underlying Linux kernel with Fuchsia for instance and not affect the containers running on top. Who knows if that will ever materialize or if Google does the Google thing and just throws Fuchsia away, but at least the explanation would make sense.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.