Why Mainstream Tech Media Still Calls ChromeOS a Browser-Based OS (When It Hasn't Been for 8 Years)

Published on by

A modern Chromebook on a wooden desk, screen split between a Chrome browser tab and a Linux terminal running apt install, warm editorial lighting

I was watching a ChromeOS platform critique on YouTube this week when the reviewer said something that made me pause the video. Talking about why Google has struggled to sell premium Chromebooks, he explained: “I think efforts to break into the premium segment have been really tough for Google as high-end hardware can’t really be fully utilized on a browser-based operating system.” He moved on to complain about Adobe not being available. He never once mentioned that every modern Chromebook runs Android apps from the full Google Play Store and can run Linux desktop and terminal apps from the Debian package archive: GIMP, Inkscape, Blender, Audacity, Kdenlive, and the rest of the catalog. The review I was watching in April 2026 could have been written in 2015 and nothing would have changed.

This isn’t one reviewer having a bad day. It’s a pattern. If you read the flagship “best Chromebook” buyer’s guides on the biggest English-language tech sites right now, you will find the same framing repeated like a mantra: ChromeOS is a browser-based operating system, it can’t run native software, Android apps are a nice bonus, and if you need anything serious you should buy a Windows laptop or a Mac. This is the 2011 story about Chromebooks, and the 2011 story stopped being true eight years ago.

The Smoking Guns Are Not Hard to Find

Engadget’s “Best Chromebook you can buy in 2026” opens by explaining what Chromebooks are to readers who might not know. “Chrome OS is based on Google’s Chrome browser, which means most of the programs you can run are web based,” Engadget writes. A few paragraphs later they deliver the warning line: “Not being able to install native software can be a dealbreaker if you’re a video editor or software developer.” Chromebooks have been able to run a full web development environment since Linux shipped in ChromeOS 69 back in 2018. We published a YouTube walkthrough in 2024 showing exactly how to set one up on a Chromebook: VS Code, Node, Git, a local dev server, the whole loop. So the “software developer” example Engadget reaches for in 2026 is a scenario Chromebooks have quietly handled for years; a reviewer who spent ten minutes actually checking would have known that. The guide does mention Android app support as a capability expansion. It does not mention the Linux development environment that ships with every modern Chromebook. Not once. A Chromebook buyer reading Engadget in April 2026 walks away believing the platform literally cannot install native software. That reader has just been told something factually wrong by a flagship tech publication.

TechRadar’s buyer’s guide tells the same story with slightly different words. “ChromeOS relies heavily on cloud computing, allowing it to offload processing to the cloud and run smoothly even on lower-end hardware,” the article explains. Later it delivers the hammer: “Chrome OS simply can’t run a large chunk of the installable software you’d find on a Windows laptop or a MacBook.” Android apps get a paragraph, with the now-ritual warning that you “shouldn’t expect them to be great for gaming.” The Linux development environment that Google ships with every modern Chromebook is not mentioned at all. A reader walks away with the same conclusion: this is a browser, with some Android stuff bolted on, and if you need real software you are out of luck.

Tom’s Guide is a little gentler but ends up in the same place. “If the majority of your work, study or entertainment revolves around being on a browser, then a Chromebook will take you far.” The implication is clear. If your work happens outside the browser, this is not the machine for you. No Linux. The full Debian package archive that can run on the laptop you are reviewing is, once again, a secret.

It isn’t just the giants. Search for “chrome os review” and near the top of the results sits a 2021 explainer from Dignited titled, and I am quoting the headline verbatim, “Chrome OS Review for Beginners: Is It More Than a Glorified Browser?”. Read the article and you will find a reasonable, fair summary that acknowledges Android apps and Linux support. But the headline has already done its work. A hypothetical review titled “Is macOS More Than a Glorified File Manager?” would be ridiculous on its face. The only reason the ChromeOS version sounds like a legitimate question is that the stereotype is so deeply baked in that even articles trying to refute it reach for the frame reflexively.

Chart comparing what mainstream reviews say about ChromeOS versus what ChromeOS actually runs in 2026

The Timeline Mainstream Reviewers Seem to Have Missed

Here is what has actually happened to ChromeOS since the original “it’s just a browser” story was written, cross-checked against Wikipedia’s ChromeOS timeline and Google’s own release notes.

Timeline showing ChromeOS app support milestones from May 2016 to April 2026

In May 2016, at Google I/O, Google announced that the Play Store and Android apps were coming to Chromebooks. The first three devices to receive the rollout in mid-June that year were the Acer Chromebook R11, the Asus Chromebook Flip, and the Google Chromebook Pixel (2015). The original 2013 Pixel never made the cut. Google explicitly ruled it out at the time, which is its own small footnote in the “Google does not market this well” story. Within a year most new Chromebooks shipped with full Android app support, and “it only runs web pages” stopped being true.

In May 2018, at Google I/O, Google announced that Chromebooks would get an official Linux development environment (internally codenamed Crostini, though Google’s own documentation simply calls it “Linux”) that would let users install real Linux desktop software directly on ChromeOS. In October 2018, it shipped in ChromeOS 69 stable, albeit flagged as beta. In May 2021, the Linux development environment officially left beta as part of ChromeOS 91 and became a stable, first-class platform feature. That was five years ago. When Engadget wrote that Chromebooks can’t install native software, the ability to install and run Linux desktop and terminal apps on ChromeOS had been shipping in stable for seven and a half years and out of beta for nearly five.

And this is not some obscure technical curiosity. With Linux turned on, a user can install GIMP for image editing, Inkscape for vector graphics, Blender for 3D, Audacity and Ardour for audio, Kdenlive and OpenShot for video, VS Code and IntelliJ for development, LibreOffice for documents, the full GNU toolchain, every Docker container, and approximately the entire open-source software ecosystem. That is not “some Linux stuff.” That is a serious desktop computing platform. Our own guides on using a Chromebook for music production, for running AI development workflows, and even turning an old Chromebook into a Linux home server all exist because this layer of the platform is real.

Why Google Deserves a Healthy Share of the Blame

I want to be careful here, because it would be easy to make this article a lazy media takedown. It is not really fair to hand the entire story to reviewers and let Google off the hook. The truth is that Google has fought this stereotype about as hard as I fight a nap after lunch. There are several reasons the framing has survived, and most of them are Google’s doing.

The first reason is that the original framing was correct for five solid years. ChromeOS shipped on the Cr-48 in late 2010, the first retail Chromebooks arrived in 2011, and until mid-2016 Chromebooks really were browser-only machines. That is long enough for an entire generation of tech journalists to learn what a Chromebook is. First impressions harden into defaults, and defaults in tech media get copy-pasted into every subsequent buyer’s guide until someone notices.

The second reason is that the Linux development environment is hidden. To turn it on today, you go to Settings, then About ChromeOS, then Developers, then “Linux development environment,” and flip the toggle. The word “Developers” in the menu path quietly tells every non-developer that this is Not For Them. Out of the box, a brand-new Chromebook presents itself as a Chrome browser with a Play Store tab, and a reviewer who opens the laptop and starts clicking will never stumble across the Linux setting by accident. The feature is gated behind a verb (“enable”) that implies risk. Most Chromebook buyers, and almost certainly most reviewers doing a “best of” roundup, never flip the switch.

The third reason is that Google has never marketed Linux support to mainstream buyers in any way that matters. The Chromebook Plus launch in October 2023 came with a marketing campaign built around “2x more processing power, 2x more memory, 2x more storage.” That was the slogan. “2x more processing power than the last generation” is a fine specs claim, but it does exactly nothing to tell a Photoshop-curious buyer that a premium Chromebook can run Blender, GIMP, and VS Code natively on the same afternoon. There was no “your laptop can run real Linux apps too” billboard. There was no I/O segment aimed at creative professionals. Google shipped a deeply capable feature and then never told the people who would actually care about it.

The fourth reason is that reviewers are optimizing for a different audience. The readers most likely to benefit from Linux on ChromeOS (developers, creatives, tinkerers) were pushed toward MacBooks and Linux laptops years ago, long before the Linux development environment existed. The remaining Chromebook audience that reviewers imagine is students and casual home users, and a “best Chromebook for a college freshman” roundup has very little reason to spend word count on the Debian package archive. So the capabilities keep showing up, and the coverage keeps not catching up.

The fifth reason is that every Google branding reshuffle gives mainstream media another reason to reach for the old shorthand. Chrome OS quietly became ChromeOS (one word). In 2022, Google introduced ChromeOS Flex as a separate version of the OS for old PCs and Macs, built on the CloudReady codebase Google had acquired two years earlier. In October 2023, Google launched the Chromebook Plus tier for higher-spec hardware with a whole new marketing line. The platform is now merging with Android into Aluminium OS in 2026. These are not all the same kind of move: one is a spelling change, one is a sibling product for different hardware, one is a hardware tier, and the last one is a genuine OS merger. But to a reviewer writing a yearly buyer’s guide, each one is a fresh excuse to re-explain the platform from scratch, and each fresh re-explanation reaches for the only framing the audience reliably understands, which happens to be the oldest and most wrong one. “ChromeOS was always basically a browser” becomes a convenient retrospective summary of a platform that is being folded into something new, even though the real reason for the merger is that Chromebooks got capable enough that Google wants one operating system for both phones and laptops.

A Fair Counterpoint

None of this means ChromeOS does everything a Mac or a Windows laptop does. It doesn’t, and I have written at length about the real limits. Adobe still refuses to ship native creative software for ChromeOS, so Photoshop, Premiere, Illustrator, and After Effects are genuinely off the table. AutoCAD, SolidWorks, MATLAB, Final Cut Pro, and Logic Pro are not available. Google announced in August 2025 that Steam on Chromebooks would be discontinued on January 1, 2026, so AAA gaming is dead outside of cloud streaming. These are real, specific software gaps, and I am the first person to tell a Photoshop professional to buy a MacBook.

But “ChromeOS can’t run Photoshop” and “ChromeOS is a browser-based operating system” are not the same claim. The first one is a narrow, accurate observation about a specific vendor’s product strategy. The second one is a sweeping architectural statement about an entire platform, and it is wrong. The frustration is not that reviewers point out real limitations. The frustration is that they collapse a long list of specific vendor gaps into a lazy one-liner that misrepresents the platform itself.

What would a fair review look like? It would say something like this: “ChromeOS in 2026 runs web apps, Android apps from the Play Store, and Linux desktop and terminal apps from the Debian package archive, which between them cover most of what a typical user or even a technical user needs. The platform has specific, well-known gaps in proprietary creative software, professional CAD, and AAA native gaming. If your workflow depends on those categories, buy a different laptop. If it doesn’t, you are probably looking at the most secure, lowest-maintenance laptop platform available.” That is thirty seconds more work than the current boilerplate. It is also accurate.

The last time I enabled Linux on a review Chromebook, it took me about ninety seconds. The last time I read a mainstream “best Chromebook” guide, it took me about fifteen minutes to realize the reviewer almost certainly hadn’t. The gap between those two numbers is the whole story.