BlueStacks has no Linux build, so on Linux use Waydroid, which runs Android in a container on your own kernel. To test apps, use Android Studio’s emulator, or Genymotion if you want a commercial tool.
Table of Contents
Install and run Waydroid
Waydroid is a container, not an emulator: its docs say it uses Linux namespaces to run a full Android system, a LineageOS-based Android 13 image. Steps below: Ubuntu and Debian.
- Check your session and kernel. Waydroid needs a Wayland session; the install page says to make sure it is enabled (Ubuntu 22.04+).
echo $XDG_SESSION_TYPEprints wayland on Wayland and x11 on Xorg (Wayland vs Xorg on Ubuntu). The essential-information page says it is important that your kernel supports binder and either ashmem or memfd, and gives this check:grep -i -e android -e memfd -e ashmem "/boot/config-$(uname -r)"If support is missing, it suggests a supported kernel or the patched anbox-modules.dkms.
- Add the repository if your release needs it. The docs say Debian 14+ and Ubuntu 26.10+ have Waydroid in the official repository and Debian 13 (Trixie) in backports; older releases need the third-party one:
sudo apt install curl ca-certificates -y curl -s https://repo.waydro.id | sudo bashI read that script without running it; it adds an apt source and a signing key.
- Install the package.
sudo apt update sudo apt install waydroid -yThe docs then say to start Waydroid from the applications menu.
- Initialize the image. The Debian and Ubuntu section skips this step. The command-line page defines
waydroid initas “Set up waydroid specific configs and install images”; its test-build example runs:sudo waydroid initIts
-s SYSTEM_TYPEoption takes VANILLA, FOSS or GAPPS (default VANILLA). The docs print no GAPPS example, so add the option yourself; I have not run it. - Start the container and the session. On systemd the container runs as the
waydroid-container.serviceunit, which the docs check withsudo systemctl status waydroid-container.service. I found nothing in the docs about enabling it at boot; systemctl shows whether it is. Without systemctl, start the container, then the session in a new terminal tab, without sudo:sudo waydroid container start waydroid session startOnce you see “Android with user 0 is ready”, it is safe to launch an app from the applications menu.
- Open the Android UI in full-screen mode:
waydroid show-full-ui - Install an APK.
waydroid app install xyz.apkThen launch it from the application menu. The docs warn that APKs found online often have only ARM support and then do not work on x86_64, and suggest F-Droid for a graphical app store.
- Use the Play Store. The docs say it needs a GAPPS image. On first launch Android reports the device is not certified for Google Play Protect. Follow the on-screen steps or use the docs’ shortcut, which prints the device’s Android ID:
sudo waydroid shell -- sh -c "sqlite3 /data/data/*/*/gservices.db 'select value from main where name = \"android_id\";'"Register that number at google.com/android/uncertified, wait a few minutes, then restart with
waydroid session stop.
If you have an Nvidia GPU, check which GPU is active: the docs’ VM page says its fix, running without GPU acceleration, “also applies to any unsupported GPU’s as well (like nVidia)”.
Waydroid is active: on 2026-10-05 the latest release was still 1.6.3 and the last push was 2026-09-26. My earlier check:
$ curl -s https://api.github.com/repos/waydroid/waydroid/releases/latest | ...
tag: 1.6.3 | published: 2026-05-28T20:12:19Z
$ curl -s https://api.github.com/repos/waydroid/waydroid | ...
archived: False | pushed_at: 2026-08-01T20:26:52Z | license: GPL-3.0
I read these steps in the docs on 2026-10-05 and checked the GitHub API and the BlueStacks, Genymotion and Google pages with curl on a Mac (macOS 26.6), but I did not run Waydroid or any of these commands on Linux.
What BlueStacks’ own pages say about Linux
BlueStacks’ download page, requested with a Linux user agent:
$ curl -s -A 'Mozilla/5.0 (X11; Linux x86_64) ...' https://www.bluestacks.com/download.html \
-o bs.html -w 'HTTP %{http_code} %{size_download} bytes\n'
HTTP 200 282112 bytes
$ grep -oi 'linux' bs.html | wc -l # 0
$ grep -oi 'ubuntu' bs.html | wc -l # 0
$ grep -o 'Windows' bs.html | wc -l # 22
$ grep -o 'macOS' bs.html | wc -l # 4
$ grep -o '<title>[^<]*</title>' bs.html
<title>Download BlueStacks - App Player on PC - Windows and Mac</title>
The page never mentions Linux, and its title says “Windows and Mac”. On 2026-10-05 the same request returned 284,463 bytes and the same counts. The BlueStacks 5 requirements list “OS: Microsoft Windows 7 and above” as the minimum and “Microsoft Windows 10 and above” as recommended. Searching the BlueStacks help center for “Linux” finds only Hyper-V articles about the Windows feature “Windows Subsystem for Linux”. I put these checks in a script you can run: /verify/bluestacks-linux-android-installation.sh counts the same four words and looks up the Waydroid, Anbox, Genymotion and Google Play Games sources, with only GET and HEAD requests.
Running BlueStacks inside a Windows virtual machine
Installing VirtualBox, then Windows, then BlueStacks has three problems. You need a Windows license. BlueStacks runs Android in its own virtual machine, so you would need nested virtualization, which VirtualBox lets you enable by ticking “Enable Nested VT-x/AMD-V”. And the result is a Windows Android runtime with two extra layers, not a Linux one.
Anbox: unmaintained since 2023
Anbox’s README says since 2023 that it is no longer actively developed:
"It's development has however stalled in the past years and it's only fair to say
that now in 2023 it's no longer actively developed."
"If you're looking for a solution to run Android on your Linux desktop: Waydroid is
rebuilding the original idea behind Anbox..."
$ curl -s https://api.github.com/repos/anbox/anbox | ...
archived: True | pushed_at: 2024-02-06T22:17:24Z
$ curl -sI https://anbox.io/ | grep -Ei 'HTTP/|last-modified'
HTTP/2 200
last-modified: Fri, 03 Feb 2023 13:25:24 GMT
The repository is archived and anbox.io was last modified in February 2023: a historical note, not an option.
Two other options: Android Studio emulator and Genymotion
Android Studio’s emulator is for testing an app rather than using one. Google’s acceleration doc says Linux gets acceleration through KVM; without it the emulator still runs, only slower:
egrep -c '(vmx|svm)' /proc/cpuinfo # non-zero means the CPU supports virtualisation
sudo kvm-ok # "INFO: /dev/kvm exists"
sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils
Some of its system images run ARM binaries (release notes), while Waydroid’s docs say ARM-only APKs do not work on x86_64.
Genymotion Desktop still ships a Linux build: its download page lists genymotion-3.11.0-linux_x64.run for Ubuntu, Debian and Fedora, and its install docs say it uses QEMU on KVM by default there. The pricing page lists a free personal-use edition at $0 with no technical support.
Google Play Games on PC is Windows-only too: its requirements list Windows 10 (v2004), not Linux.
BlueStacks alternatives for Linux compared
| Option | Runs on Linux | Type | Needs | Best for | Status |
|---|---|---|---|---|---|
| BlueStacks | No | Android emulator, VM-based | Windows 10+ (latest version), or macOS 11+ on Apple Silicon (BlueStacks Air) | Mobile games on Windows or Mac | No Linux build |
| Waydroid | Yes | Container, not an emulator | Wayland session; kernel with binder and ashmem or memfd | Android apps on Linux desktops | Release 1.6.3, last push 2026-09-26 |
| Android Studio emulator | Yes | Emulator | VT-x or AMD-V; KVM for acceleration | Testing apps across API levels | Emulator 37.2.11 (Sep 29, 2026) |
| Genymotion | Yes (x86_64) | Emulator, QEMU on KVM by default | VT-x or AMD-V; officially supported on Ubuntu, Debian, Fedora | Testing with hardware profiles | 3.11.0 on 2026-10-05; free edition has no support |
| Anbox | Yes, unmaintained | Container | Snap support and kernel support | Nothing new; use Waydroid | Repository archived |
Which one to use
To use Android apps on a Linux desktop, I would use Waydroid, which Anbox’s README points to. To test an app, use Android Studio’s emulator. Choose Genymotion for a commercial product with hardware profiles.