📱 A whole phone inside a window — seven free ways, iPhone included

Tutorials & Methods
, ,

AI-generated summary

:bullseye: What you get: Run a complete Android or iOS phone directly inside a desktop window without hardware emulators.

:white_check_mark: Start here:

  • scrcpy — mirrors your physical Android to your desktop with zero lag.
  • Waydroid — runs Android inside a Linux container like a native app.

:toolbox: Also useful:

  • docker-android — streams Android inside a web browser via Docker.
  • vphone-aio — sets up an iOS virtual machine test environment.
  • UTM — runs full computer operating systems inside an iPhone.

:warning: Watch out:

  • Disable USB debugging on your phone after mirroring sessions to prevent unauthorized device access.
1

A whole phone inside a window — even an iPhone. :mobile_phone:

No device, no cable, no cloud bill. Seven free ways, grouped by what you are actually after.

┌───────── a window ─────────┐
│  📱 android 15              │
│     running in a tab        │
│  🔋 nothing to charge       │
└─────────────────────────────┘

Android, for real
:robot: Waydroid · 12.4k★ — real Android in a Linux container. Opens like an app instead of grinding like an emulator.
:spouting_whale: docker-android · 16.0k★ — Android in Docker, watchable in the browser over noVNC. One command per version, all at once.
:cloud: redroid · 7.0k★ — Android in the cloud, multi-arch, GPU on. Built for dozens of instances on one host.
:older_person: Anbox · 9.0k★ — the original, and still the lightest. Kind to old machines.

The phone you already own
:mobile_phone_with_arrow: scrcpy · 153k★ — mirror your real Android on the desktop. Five seconds, no root, no lag.

iOS, the honest version
:red_apple: vphone-aio · 7.9k★ — one script → a rooted iOS 26 virtual machine. A lab, not a daily driver.
:laptop: UTM · 36.5k★ — the reverse trick: full computers running inside an iPhone or iPad.

Why a container beats an emulator

The one fact worth remembering: an emulator pretends to be hardware and eats a core. A container runs the real Android userspace on your real kernel — which is exactly why Waydroid feels instant and an emulator feels like 2014.

:pushpin: Own an Android? scrcpy first, it is the five-second win. Want a second phone for free? Waydroid.

7 curtidas
2

Start with scrcpy if you already own an Android phone, because it gives you a real device with your own apps and accounts instead of a fresh virtual setup. Before you mirror anything, enable USB debugging only for that session and turn it off afterwards, since leaving it on widens access to your phone. If you want a second phone for testing, try Waydroid on Linux first, and keep test apps separate from your banking and messaging apps. For browser-based testing, use a disposable account and avoid signing into anything sensitive, because a shared virtual device is easier to leave logged in by accident. Finally, check screen size, touch input, and file transfer in a short trial run before you rely on any of these setups for daily work.

3

This grouping helped a lot — I kept mixing up emulators and mirroring before, and now the choice feels clearer. If I already own the phone, mirroring it makes the most sense for a quick test, because I get my real apps and settings without setting up a second device. For a clean test phone, the container route sounds like the lighter path, especially on an older machine. My practical tip: do a five-minute trial first for touch, keyboard and file transfer, so you find out early if the setup fits the job you actually want it for.