ChromeOS vs Waydroid vs now.gg: Pre-2019 Locked Out [2026]

Type “android emulator for chromebook” into Google and you will find years-old advice that no longer matches how ChromeOS works in September 2026. Some guides still point readers toward BlueStacks or LDPlayer, both of which are Windows programs that were never built to run on ChromeOS hardware. Others assume every Chromebook has the Google Play Store, which is not true for ChromeOS Flex or for machines released before 2019. The result is a lot of wasted downloads and a lot of confused readers stuck on a Crostini terminal screen.

There are really three workable paths to running Android apps on a Chromebook in 2026: the operating system’s own built-in Android support, a manual Waydroid install through Linux, and browser-based cloud emulation through a service like now.gg. Each one solves a different problem, and picking the wrong one wastes an afternoon. This comparison walks through what each option actually requires, what it costs, how it performs, and which Chromebook owners should use which method, based on official ChromeOS documentation, the Chromium Projects device list, and current 2026 market data from Mordor Intelligence and About Chromebooks.

·

Google · Preferred Sources

Don't miss new tech stories on Google

Add Tech Insider once in the Google app and our stories appear in your news suggestions.

Add Now

Why “Best Android Emulator for Chromebook” Isn’t One Answer in 2026

Most Android emulator comparisons assume a Windows PC. That assumption breaks down on a Chromebook for two structural reasons. First, ChromeOS is not Windows and cannot install a native Windows .exe installer, so BlueStacks, LDPlayer, MEmu Play, NoxPlayer, and GameLoop are off the table by default, no matter how much RAM the machine has. Second, a large share of Chromebooks run on ARM processors rather than x86 chips, which rules out even unofficial workarounds that depend on Intel VT-x or AMD-V virtualization.

According to chipset data compiled by About Chromebooks, x86 chips from Intel and AMD powered 70.95 percent of Chromebook shipments in 2025, while ARM silicon from MediaTek and Qualcomm accounted for 29.05 percent and is forecast to grow more than twice as fast through 2031. MediaTek has become the leading ARM Chromebook chip supplier, a trend tracked in detail by Starry Hope’s 2026 analysis of the MediaTek-Qualcomm rivalry. On an ARM Chromebook, a Windows-only x86 emulator simply has nothing to run on.

Chromebook adoption itself keeps climbing. Mordor Intelligence puts the 2026 Chromebook market at 22.94 million units, up from 22.11 million in 2025, with growth projected to reach 27.56 million units by 2031 at a 3.74 percent compound annual growth rate. That is a lot of devices where “just install BlueStacks” is not an option, which is exactly why native ChromeOS support, Waydroid, and cloud emulation each carved out a real user base instead of one clear winner emerging.

ChromeOS Native Android Support: How ARC++ and ARCVM Actually Work

The default and generally best option, when it is available, is the Android runtime Google already built into ChromeOS. Older Chromebooks ran this through ARC++, a container that shared more of the underlying ChromeOS kernel. Newer devices increasingly run ARCVM, which isolates Android inside a lightweight virtual machine for better security separation. Either way, the experience for the user is the same: open the Play Store, sign in, and install apps like any Android phone.

Not every Chromebook gets this. Google’s own support documentation is blunt about it: open Settings, then Apps, then Manage Google Play preferences. If that menu item is missing, the device does not support Android apps, full stop. The Chromium Projects compatibility list gives the general rule of thumb: unless a specific model is called out as an exception, Chromebooks that launched in 2019 or later support Android apps. Anything older needs to be checked individually, and support can also be withheld on managed school or enterprise devices even when the hardware is capable.

ChromeOS itself keeps moving fast. The stable channel reached OS version 16765.51.0 with browser version 152.0.7977.132 on September 25, 2026, according to Google’s own Chrome Releases blog. The Google Play Store client on Android was separately updated to version 53.3 on September 21, 2026, per 9to5Google’s coverage of the September system updates. Both of these ship independently of each other and independently of the specific ARC++ or ARCVM build a given Chromebook runs, so there is no single Android version number that applies to every device. That detail matters if you are trying to run an app that requires a specific Android API level: check the actual device, not a blanket claim about what “ChromeOS” runs.

The Convergence Question: Is ChromeOS Becoming Android?

Google has been pushing ChromeOS and Android closer together for years, and 2026 brought a concrete data point rather than just speculation. Google confirmed it is transitioning its Google Meet hardware line from ChromeOS to Android, a shift reported by 9to5Google’s ongoing ChromeOS coverage. That is a hardware-category move, not proof that consumer Chromebooks have been replaced or that ChromeOS is going away in the near term. Existing Chromebooks with native Android support are not affected by this transition, and Google has given no fixed timeline for retiring ChromeOS as the consumer laptop platform. For anyone deciding how to run Android apps on a Chromebook today, the native Play Store path remains the supported, documented route, whatever direction Google’s roadmap eventually takes.

Waydroid on ChromeOS Flex and Crostini: The Power-User Route

Waydroid is an open-source Android container built for Linux systems running the Wayland display protocol. It is not a ChromeOS product and Google does not officially support it, but it has become the closest thing to a workaround for two groups of Chromebook owners: people running ChromeOS Flex, which never shipped with Play Store support, and people on a standard Chromebook that falls outside the 2019 Android-support cutoff.

Getting there requires stacking several layers. A Chromebook needs Crostini, Google’s Linux development environment, turned on first. Inside that Debian-based container, Waydroid needs its own Android images, a working Wayland compositor, and functioning binder and graphics passthrough between the Linux container and the host. The official Waydroid project on GitHub documents the process for general Linux systems, but none of it is written with Chromebook-specific quirks in mind, so expect to debug driver and permission issues that a phone or a native ChromeOS install never surfaces.

On ChromeOS Flex specifically, this is even more of an experiment. Flex was designed to repurpose old Windows and Mac laptops as ChromeOS-like machines, and it deliberately ships without the ARCVM Android stack. Installing Waydroid there means asking a Linux container inside a repurposed laptop to do a job Google never engineered ChromeOS Flex to do. It can work, and plenty of forum threads document successful setups, but hardware acceleration, Google Play Services availability, and update stability are all inconsistent from one machine to the next. This is not a route for someone who wants Android apps working in the next ten minutes.

now.gg and Cloud Android Emulation: Zero Install, All Streaming

The third option skips local emulation entirely. Services like now.gg run the actual Android instance on remote servers and stream video back to whatever browser tab you have open, while your keyboard, mouse, or touchscreen input gets sent back up to the server. Because the client is just a browser tab, this is the only one of the three approaches that works identically on every Chromebook, including ARM models, pre-2019 devices, and ChromeOS Flex machines with no Play Store at all.

The tradeoff is that performance now depends on the network connection instead of the Chromebook’s own CPU and GPU. A fast Chromebook on a weak Wi-Fi signal can feel worse than a budget Chromebook on a strong, low-latency connection, because the local hardware barely matters once the app itself is rendering somewhere else. That makes cloud emulation a good match for casual, touch-based, and turn-based titles, and a rougher match for anything that needs tight input timing. It also means offline use is off the table by definition: no connection, no app.

Cloud gaming for full PC and console titles on Chromebooks, through services like Xbox Cloud Gaming or GeForce Now, follows the same streaming logic but is a separate setup from Android app emulation, covered in our Chromebook cloud gaming setup guide. The core now.gg catalog is free and ad-supported, which keeps the barrier to entry low for exactly the audience that needs it most: owners of Chromebooks that cannot run native Android apps at all. That’s a meaningfully different value proposition from a Windows desktop cloud emulator, where the competition is BlueStacks or LDPlayer running locally for free. On unsupported ChromeOS Flex hardware, cloud emulation isn’t competing with a better local option. It’s often the only option.

Why BlueStacks, LDPlayer, and MEmu Don’t Run on Most Chromebooks

It’s worth being precise about why the household names in Android emulation are dead ends on ChromeOS, because the reasons go beyond “it’s not Windows.” LDPlayer’s official system requirements, last updated with its September 23, 2026 release of version 14.0.29.0, call for an Intel or AMD x86 processor, Intel VT-x or AMD-V virtualization enabled in firmware, a minimum of 2GB of RAM, and 36GB of free disk space, scaling up to a recommended 16GB of RAM and a GTX 1660 Ti-class GPU, according to LDPlayer’s own release notes and requirements page. None of that maps onto a ChromeOS device, which does not run Windows drivers and, on ARM models, does not have an x86 instruction set to virtualize in the first place.

MEmu Play, which shipped version 9.5.7.1 on September 16, 2026 according to its official download page, has the same fundamental dependency on x86 virtualization even though its published minimum specs are lighter. BlueStacks, whose current product line is documented at bluestacks.com, requires Windows 10 or later and at least 8GB of RAM on the host machine. A Chromebook cannot satisfy that requirement because it does not run Windows, regardless of how much RAM is physically installed. Any site or forum post claiming you can “just install BlueStacks on a Chromebook” is either describing a browser-based BlueStacks X-style stream, which is a different product category entirely, or describing an unsupported hack layered on top of Linux virtualization that the vendor never tested or endorsed. For a full rundown of how BlueStacks, LDPlayer, and the rest of the Windows emulator field actually compare to each other on the hardware they were designed for, see our separate best Android emulators for PC breakdown.

Google Play Games for PC deserves a separate mention because the name causes real confusion. It is Google’s own Windows gaming client with a curated catalog, and it is a completely different product from the Android runtime built into ChromeOS. Installing “Google Play Games for PC” is not a path to more Android apps on a Chromebook. The built-in ChromeOS Play Store already covers that job on supported devices.

Android Emulator for Chromebook: Full Specs Comparison

The table below lines up the three real options side by side, along with why the mainstream Windows emulators are excluded from the running entirely.

Factor	Native ChromeOS (ARC++/ARCVM)	Waydroid (Crostini/Flex)	now.gg (Cloud)	BlueStacks/LDPlayer (Windows)
Works on ARM Chromebooks	Yes, on supported models	Experimental, hardware-dependent	Yes	No
Works on x86 Chromebooks	Yes, on supported models	Experimental	Yes	No, not natively on ChromeOS
Works on ChromeOS Flex	No, Flex excludes ARCVM	Yes, unofficially	Yes	No
Play Store access	Full, on supported models	Not automatic, varies by setup	App-catalog dependent	N/A
Install required	None, built in	Yes, multi-step Linux setup	None, browser only	Not installable on ChromeOS
Offline use	Yes, once installed	Yes, once working	No, requires a live connection	N/A
Setup difficulty	Low	High	Low	N/A
Local hardware dependence	High	High	Low, network matters more	N/A
Device eligibility	Generally 2019-or-newer models	Any Crostini-capable or Flex device	Any device with a modern browser	N/A
Official vendor support	Yes, Google-supported	Community project, unsupported on ChromeOS	Yes, for the now.gg client	N/A on ChromeOS
Best for	Everyday app and light gaming use	Testing, sideloading, power users	Unsupported or older hardware	Windows PCs only

The pattern is consistent across every row: native support wins whenever the device qualifies, Waydroid is a fallback for people willing to trade setup time for offline capability, and cloud emulation is the universal option precisely because it asks nothing of the local hardware.

Buying a Chromebook for Android Apps: What to Check Before You Order

If you’re shopping for a new Chromebook specifically to run Android apps, the spec sheet on a retail listing will not tell you what you need to know. Retailers rarely advertise Android app compatibility as a headline feature, and the 2019-or-newer rule from the Chromium Projects list is a guideline, not a guarantee for every single model in every configuration. Before buying, look up the exact model number on Google’s own support pages or the Chromium compatibility list rather than trusting a listing title.

Chip architecture matters more than most buyers assume. An Intel or AMD Chromebook Plus model, which together made up 70.95 percent of 2025 shipments according to About Chromebooks’ chipset data, tends to have wider software compatibility and often more RAM headroom for running several Android apps alongside ChromeOS tabs. A MediaTek Kompanio or Qualcomm Snapdragon ARM model, the 29.05 percent segment growing fastest, usually wins on battery life and fan-free design, but Android app performance is more tied to the specific chip generation than to the architecture label alone. Neither architecture blocks native Android support outright. Both run ARCVM on supported models, and the RAM overhead of that runtime is one reason Chromebook buyers should treat 4GB configurations as a minimum rather than a target, a tradeoff explored in more detail in our BlissOS vs Waydroid vs Android Studio Emulator RAM comparison. The practical difference shows up in how well demanding apps and games perform once installed, not in whether they install at all.

For buyers specifically choosing between a standard Chromebook and a ChromeOS Flex device, such as a school district converting old Windows laptops, the calculation is different again. A standard Chromebook from a major manufacturer released in the last two to three years is close to guaranteed to support Android apps natively. A Flex conversion never will, no matter how new or powerful the underlying laptop hardware is, because Flex’s Android support gap is a software decision by Google, not a hardware limitation. If Android apps are a requirement rather than a nice-to-have, that single fact should end the debate before it starts.

Common Setup Problems and How to Fix Them

Even when a Chromebook is eligible for native Android support, the Play Store sometimes refuses to appear or apps fail to install. The most common cause is a managed device policy: schools and workplaces frequently disable Android apps at the administrator level even on otherwise-capable hardware, so if Manage Google Play preferences is missing on a work or school-issued Chromebook, check with IT before assuming the device itself is unsupported.

On personal devices, a missing Play Store option after a ChromeOS update sometimes clears up after a restart, since the ARCVM container occasionally needs a fresh boot to reinitialize after a system update lands. If that doesn’t work, checking storage space is worth doing next. Android apps, ARC++/ARCVM’s supporting files, and cached data can eat into a Chromebook’s often-limited local storage faster than users expect, and low storage can silently block new app installs.

Waydroid users run into a different category of problems, almost always tied to graphics acceleration. A Waydroid session that starts but renders as a black screen, or that runs at a noticeably lower frame rate than expected, is typically a sign that GPU passthrough between Crostini and the host isn’t working correctly. This is precisely the kind of device-specific quirk the Waydroid project’s GitHub issue tracker gets filled with, and checking there for your specific Chromebook model before spending hours troubleshooting blind is usually the faster path.

Cloud emulation problems almost always trace back to the network rather than the app itself. Choppy video, input lag, or dropped sessions on now.gg or a similar service point to Wi-Fi congestion, a weak signal, or a network that’s throttling video-streaming traffic, rather than anything wrong with the Chromebook. Switching to a 5GHz Wi-Fi band where available, moving closer to the router, or testing on a wired or mobile hotspot connection isolates whether the Chromebook or the network is the actual bottleneck.

Pricing Breakdown: Free vs Subscription Costs

Cost is one area where none of the three consumer-facing Chromebook options will put a dent in your wallet, at least for casual use. Native ChromeOS Android support comes with the device and costs nothing extra. Waydroid itself is free and open source, though it demands time rather than money, and it depends on Crostini, which is also a free built-in ChromeOS feature. now.gg’s core catalog runs on a free, ad-supported model, funded by advertising and optional in-app purchases on specific titles rather than a mandatory subscription for basic access.

The pricing picture changes if you step outside casual use and into professional QA or automated testing, where cloud Android infrastructure is a paid line item rather than a convenience. Genymotion Cloud, aimed at developers who need repeatable virtual Android devices rather than a gaming experience, charges $0.06 per minute per running virtual device on a pay-as-you-go basis, $219 per month per device for unlimited use billed monthly, or $179 per month per device billed annually, according to Genymotion’s official Cloud pricing page. arm64 instances run separately at roughly $0.60 per hour, excluding platform fees. That is a meaningfully different cost structure from a free consumer cloud emulator, and it is the right comparison point for a Chromebook-based tester running Appium or Selenium suites against Android builds rather than someone just wanting to check Instagram.

Option	Base cost	Extra cost triggers	Best audience
Native ChromeOS Play Store	Free with device	None, standard app purchases only	General consumers on eligible devices
Waydroid on Crostini/Flex	Free, open source	Time cost of setup and maintenance	Linux power users, testers
now.gg cloud emulation	Free, ad-supported	Optional premium features on select titles	Unsupported or older hardware
Genymotion Cloud (automation)	$0.06/minute pay-as-you-go	$219/month unlimited, or $179/month billed annually	QA engineers and CI/CD pipelines

Performance Benchmarks: What Actually Changes Between Methods

There is no single, controlled lab test that runs native ARC++, Waydroid, and now.gg on the exact same Chromebook hardware and reports matching FPS numbers, and it would be misleading to invent one. What the available evidence supports is a structural comparison of where each method spends its resources, and that structural difference is often more decisive than any specific frame rate.

Native ChromeOS Android support renders locally, using the Chromebook’s own CPU and GPU, the same way a phone would. That gives it the lowest input latency of the three when it is available and working correctly, because there is no round trip to a remote server for every tap or swipe. The tradeoff is that a budget MediaTek Chromebook is still a budget chip, and native support cannot make a graphically demanding game run smoothly on hardware that was never built for it.

Waydroid running through Crostini adds a virtualization layer on top of whatever the Chromebook’s chip can do, which introduces overhead before the app even starts drawing a frame. Whether that overhead is noticeable depends heavily on whether graphics acceleration is passing through correctly, which the Waydroid project’s own documentation flags as configuration-dependent rather than guaranteed. In practice, this makes Waydroid a stronger fit for apps that don’t need to render much, like productivity tools or messaging apps, and a weaker fit for action games.

Cloud emulation flips the entire equation. The Chromebook’s CPU and GPU barely factor in, because the actual Android instance is rendering on a remote data center server. What determines the experience is round-trip network latency, connection stability, and the video encoding quality the service applies. That is precisely why the same MediaTek Chromebook that struggles with a locally rendered 3D game can run smoothly through a cloud service on a solid Wi-Fi connection: the bottleneck moved from the chip to the router.

Setup Complexity Compared: Native vs Waydroid vs Cloud

For most readers, setup time matters as much as raw performance. Native support is close to zero-effort: open Settings, confirm Manage Google Play preferences is present, sign into the Play Store, and start installing apps. If that menu option doesn’t appear, the device simply isn’t eligible, and no amount of troubleshooting in Settings will change that.

now.gg sits close to native support on the effort scale. Open a browser tab, sign in if the title requires an account, and start playing. There’s no download, no container to configure, and no dependency on the Chromebook’s chip architecture.

Waydroid is the outlier. A basic path looks like this on a Crostini-capable Chromebook:

1. Settings > Advanced > Developers > Turn on Linux development environment
2. Open the Linux terminal and update packages
3. Add the Waydroid project repository and GPG key
4. sudo apt install waydroid
5. sudo waydroid init
6. sudo systemctl start waydroid-container
7. waydroid session start
8. waydroid show-full-ui

That sequence assumes every step succeeds cleanly, which is not guaranteed on ChromeOS Flex or on a Chromebook whose Linux kernel or graphics driver doesn’t line up with what Waydroid expects. Realistically, budget an evening for a first attempt, not ten minutes, and be prepared to search community forums for device-specific fixes since neither Google nor the Waydroid project officially supports this combination.

5 Real-World Scenarios and Which Option Wins

Abstract comparisons only go so far. Here’s how the decision plays out for specific, common situations.

• A student with a 2022 education Chromebook running Duolingo, Kahoot, and a school-issued Android app. The device almost certainly qualifies for native support under the 2019-or-newer rule, so the Play Store is the obvious and only necessary choice.
• An IT department deploying ChromeOS Flex on repurposed 2016-era Windows laptops for a call center. Flex has no native Play Store, so the choice is between a Waydroid install per machine, which multiplies maintenance overhead across a fleet, or standardizing on a cloud service like now.gg that needs zero per-device configuration.
• A QA engineer testing a mobile web app’s Android behavior from a Chromebook. Waydroid can work for occasional manual checks, but for repeatable, scriptable testing tied into a build pipeline, a paid service built for automation, such as Genymotion Cloud, is the more reliable tool, since it’s designed around ADB and CI integration rather than casual app use.
• A remote worker on a 2018 Chromebook that falls just outside the native-support cutoff and needs an Android-only banking or authenticator app. now.gg’s zero-install browser model solves this immediately without touching Crostini at all.
• A gamer on a budget MediaTek Chromebook who wants to play a graphically demanding Android title the local chip can’t handle smoothly. Cloud streaming moves the rendering workload off the weak local GPU entirely, trading local hardware limits for a network dependency.
• A developer who wants offline access to a sideloaded APK not available through the Play Store, on a Chromebook that does support native Android apps. Waydroid, run alongside native support rather than instead of it, gives more flexibility for sideloading than the locked-down native Play Store environment allows.

Migration Guide: Switching Between Native, Waydroid, and Cloud

Moving between these three approaches is more about matching the method to the device than performing a technical migration, since none of them share app data or accounts by default.

1. Confirm eligibility first. Check Settings > Apps > Manage Google Play preferences before assuming you need a workaround at all.
2. If native support exists, sign into the same Google account used on your phone to sync app purchases and, where supported, some app data.
3. If native support is missing and you’re on standard ChromeOS, enable the Linux development environment under Settings > Advanced > Developers before attempting Waydroid.
4. If you’re on ChromeOS Flex, weigh the setup cost of Waydroid against simply using a cloud service, especially for a one-off need rather than daily use.
5. For cloud emulation, create an account directly with the service rather than through a third-party wrapper site, to avoid ad-injection or credential risks from unofficial mirrors.
6. Export or note any in-app data you rely on before switching methods, since Waydroid and native ARCVM do not share storage, and cloud sessions typically reset between logins unless the app itself saves progress to a cloud account.
7. Re-test performance-sensitive apps after switching, since network-bound cloud performance and locally-rendered performance behave differently enough that an app that felt fine on one method can feel different on another.
8. Keep a fallback method in mind. If Waydroid breaks after a ChromeOS update, which does happen since it’s unsupported, cloud emulation is the quickest way to keep working while you fix or reinstall it.

Security and Data Privacy Differences

Each method carries a different trust boundary. Native ChromeOS Android support runs inside Google’s own sandboxed runtime, patched through the same update channel as the rest of the operating system, and benefits from Google’s standard Play Protect scanning. It’s the option with the most institutional security review behind it.

Waydroid is a community-maintained open-source project. That openness is valuable for transparency, since the code is publicly auditable on GitHub, but it also means there’s no vendor SLA, no guaranteed patch cadence, and no official ChromeOS integration testing. Running it inside Crostini does add a layer of container isolation from the rest of ChromeOS, which limits the blast radius if something inside the Android container misbehaves.

Cloud emulation shifts the privacy conversation entirely. Your inputs and the app’s video output travel over the network to a third-party server, meaning you’re trusting that provider’s infrastructure and data-handling practices rather than keeping everything local. For most casual apps, that’s a reasonable tradeoff for convenience. For anything involving sensitive financial or personal data, it’s worth checking a cloud provider’s specific privacy policy rather than assuming it matches what a locally-run Play Store app would do.

Pros and Cons of Each Approach

Native ChromeOS Android Support

• Pro: Zero setup, Google-supported, lowest latency, full Play Store access.
• Pro: Works offline once apps are installed.
• Con: Not available on ChromeOS Flex or on many pre-2019 devices.
• Con: Performance is capped by whatever chip the Chromebook actually has.

Waydroid on Crostini/Flex

• Pro: Free and open source, works offline once configured, flexible for sideloading.
• Pro: Fills the gap on ChromeOS Flex where native support doesn’t exist at all.
• Con: Multi-step, technical setup with no official ChromeOS support.
• Con: Can break after ChromeOS or Crostini updates with no guaranteed fix timeline.

now.gg Cloud Emulation

• Pro: Works on any Chromebook regardless of chip, age, or ChromeOS Flex status.
• Pro: No install, no Linux setup, free ad-supported access to the core catalog.
• Con: Requires a live, stable network connection at all times.
• Con: Input latency depends on the network, not the device, which can hurt fast-paced games.

The Verdict: Which Android Emulator Fits Your Chromebook

For the roughly 22.94 million Chromebooks shipping in 2026, the honest answer is that native ChromeOS Android support should be the first thing you check, not the last. If Manage Google Play preferences shows up in Settings, use it. It’s free, it’s the fastest to set up, and it has Google’s own engineering and security review behind it in a way neither of the alternatives can match.

If that menu option isn’t there, because the device is running ChromeOS Flex or predates the 2019 support cutoff, the decision comes down to how much setup time you’re willing to spend versus how badly you need offline access. Waydroid is the better fit for a single device you’re willing to tinker with and that needs to work without a network connection. now.gg, and cloud emulation generally, is the better fit for anything that needs to work immediately, across multiple unsupported machines, or on hardware too weak to render demanding apps locally regardless of chip architecture. Neither BlueStacks nor LDPlayer belongs in this conversation at all on ChromeOS, no matter how often older guides suggest otherwise. They were built for Windows, they require x86 virtualization, and a Chromebook, ARM or x86, was never their target platform.

FAQ: Android Emulators for Chromebook in 2026

Can I install BlueStacks or LDPlayer on a Chromebook?

No, not as their standard Windows desktop products. Both require Windows 10 or later plus x86 hardware virtualization, neither of which ChromeOS provides, and most Chromebooks run ARM chips that can’t run x86 Windows software regardless. Use ChromeOS’s built-in Play Store, Waydroid, or a cloud service instead.

Does ChromeOS Flex support the Google Play Store?

No. ChromeOS Flex, which Google designed to repurpose old Windows and Mac laptops, does not ship with the ARCVM Android runtime or Play Store support. Owners of Flex devices who want Android apps need to use Waydroid or a cloud emulation service.

Which Chromebooks support Android apps natively?

The Chromium Projects compatibility list states that, unless a device is specifically excluded, Chromebooks launched in 2019 or later support Android apps. Anything older should be checked individually through Settings > Apps > Manage Google Play preferences on the device itself.

Is Waydroid safe to use on a Chromebook?

Waydroid’s code is open source and publicly auditable, and running it through Crostini keeps it isolated in a Linux container separate from the rest of ChromeOS. That said, it is a community project without official Google or ChromeOS support, so there is no vendor guarantee about patch timing if a security issue surfaces.

Does now.gg cost money to use on a Chromebook?

The core now.gg catalog is free and ad-supported. Some titles offer optional premium features, but a subscription is not required to access the basic browser-based Android experience.

Can I use Google Play Games for PC on a Chromebook?

No. Google Play Games for PC is a separate Windows-only gaming client with its own curated catalog, distinct from ChromeOS’s built-in Android runtime. Chromebook owners already get Android app support through the standard Play Store on eligible devices, not through the Google Play Games for PC product.

Will ChromeOS eventually merge into Android?

Google has confirmed moving its Google Meet hardware line from ChromeOS to Android as of September 2026, which signals deeper convergence between the two platforms. There is no official announcement confirming a full consumer Chromebook merger or a retirement date for ChromeOS, so native Android support on existing Chromebooks remains the current, documented path for now. Anyone who remembers Microsoft’s own attempt at this convergence should recognize the pattern: our Windows Subsystem for Android alternatives guide covers what happened after Microsoft discontinued WSA and pushed Windows users toward the same three-way choice Chromebook owners face today.

What Android version does ChromeOS run in 2026?

There is no single Android version shared across every Chromebook, since the ARC++ or ARCVM build depends on the specific device, board, and ChromeOS branch. The Google Play Store client itself was updated to version 53.3 on September 21, 2026, but that is a separate number from the underlying Android runtime version, which should be checked per device.