Interface language
An Android cloud phone is a remote Android device that runs in a datacenter and you control from your browser. It can be a virtual machine or, like ours, a real physical phone. The heavy work happens there, not on your desk — your screen gets a live video stream, and your taps go back the other way.
"Cloud phone" collides with four unrelated product categories and one adjacent one — same words, different industries. Here is what people mean by it, and what we do not.
A cloud phone system is business telephony — it routes voice calls over the internet for companies that need extensions and call queues. An Android cloud phone is a device, not a calling service.
An emulator runs on your computer and translates ARM app code for an x86 desktop chip. A cloud phone inverts that: Android runs on real ARM hardware elsewhere, and your machine only draws the picture.
Cloud gaming streams one game from a server built for it — no OS, nothing to install, the session ends when you stop. A cloud phone streams an entire Android device you hold the keys to.
There are budget handsets sold under names like Cloud Phone and Cloud Mobile — real plastic-and-glass devices. They share nothing with remote Android beyond an unlucky name collision.
Mirroring and remote desktop project a device you already own onto another screen — the phone stays in your hand, burning its own battery. A cloud phone is a device you never physically possess.
A cloud phone works by running Android on real hardware in a datacenter and shipping the screen to you as a low-latency video stream, while sending your inputs back over the same connection. There is no app to install — the whole thing happens in a browser tab. Five parts do the work.
A physical ARM Android board in a rack, powered and networked in the datacenter. One tenant at a time.
The device's screen is captured and encoded to H.264 in real time, at a preset you pick — 360p, 720p, 1080p, or 2K, running roughly 1500 to 8000 kbps.
The stream travels over WebRTC, peer-to-peer where the network allows, falling back to a relay when a firewall or carrier NAT blocks the direct path. WebRTC encrypts media in transit as part of the protocol.
The browser decodes through WebCodecs, which skips the jitter buffer a normal video player uses — the buffer that makes ordinary streaming feel spongy. Removing it is what makes a remote device feel like it responds to your finger.
Multi-touch, keyboard, clipboard sync, two-way audio, and file transfer all travel the return path, so the device is genuinely operable rather than merely watchable.
The heavy work sits at the datacenter end. Your device needs a browser and a stable connection — that is the whole requirement list.
Yes and no — it depends on the provider. Many services run a virtualized Android instance on a shared ARM server; ours give each tenant a dedicated physical device. On our fleet, a cloud phone is a real phone board, not a virtual machine.
ARM app code runs on an ARM chip. Nothing is converted at runtime — which is where emulator performance and compatibility problems come from.
The device presents genuine hardware characteristics because they are genuine, not synthesised by a hypervisor.
Between rentals each device is wiped through Android recovery and a storage clear, with a verification step before it returns to the pool. If it fails, it does not come back — recovered like a phone, because it is one.
We name the chip family and the specs; we do not name the handset brand.
People rent Android cloud phones for jobs that need a phone to stay on when their own cannot. The pattern behind almost every use case is the same: separate the work from the hardware you carry.
The most common reason by far. Mobile is where gaming actually happens — Newzoo's 2025 report counts about 3.0 billion mobile players, roughly 84% of all gamers, with 1.9 billion of them in Asia-Pacific, and a large share of those games are built around progression and long idle grinds that reward uptime, not reflexes. A cloud phone gives you that uptime without leaving your own handset plugged in and cooking overnight.
A demanding title runs on the datacenter device; your side only decodes video. That makes an old laptop or a low-RAM phone a viable way to play — and the gap is widening: IDC expects global smartphone shipments to fall 12.9% in 2026, the steepest drop on record, as an AI-driven memory shortage pushes prices up.
No thermal throttling, no battery cycles burned on a game, no storage consumed. For anyone who keeps a phone for three or four years, this is the quiet argument.
A clean device with its own storage and hardware identity, kept apart from your daily phone. The platform supports changing device information, mock GPS, and assigning your own proxy per device.
A real ARM Android target you can reach from anywhere — useful when you need actual hardware behaviour rather than an emulator's approximation.
An emulator runs Android in software on your computer. A cloud phone is an actual Android device in a datacenter. The difference shows up in the things you notice most.
| What matters | Cloud phone — real device | Emulator on your PC |
|---|---|---|
| Hardware | Real ARM silicon (Exynos-class) | ARM emulated in software on an x86 CPU |
| Your computer | Uses none of your machine's resources | Eats your CPU/RAM/GPU; a weak PC stutters |
| When your PC is off | Keeps running for the paid period | Stops with your machine |
| Several devices at once | Each phone is its own device; assign your own proxy | Several windows on one computer |
| Device identity | Real device information, editable per phone | Virtual-machine traces, often identical across instances |
| Upfront cost | No hardware to buy — rent by the period | Needs a powerful PC |
A real device keeps account-ban risk low simply because it is a real phone. We do not sell, and do not promise, any way to interfere with the checks a platform or game publisher runs.
A cloud phone rental is prepaid by block of time — an hour, a day, a week, or 30 days up front — and the device runs for exactly the period you bought. The effective hourly cost drops sharply on the longer blocks.
Thirty days of uptime — the lowest effective hourly rate.
See full pricingShorter bar, cheaper hour — the fair way to compare the four cycles.
Prices come live from our sales system. Test the whole thing first with a free 2-hour trial — no card required, credited automatically when you sign in with Google.
A cloud phone has real limitations, and the honest ones are structural rather than fixable. If any of the following is a dealbreaker, a cloud phone is the wrong tool — and you should know that before you pay.
No internet, no phone. A cloud phone is unusable on a plane, on patchy mobile data, or during an outage. A physical phone degrades gracefully; this just stops.
Every input makes a round trip to a datacenter. For idle games, turn-based games, most RPGs, and general use, you won't notice. For competitive twitch play, it is a real handicap no provider can engineer away.
Prepaid blocks stop when they expire, and the device is wiped between tenants. Anything you want to keep has to be backed up or tied to an account you can sign back into.
No SIM, no calls, no camera, no in-person 2FA. Banking apps and services that check device integrity may refuse to run. Treat it as an extra device with a job.
Anti-cheat and platform-integrity systems vary by game and change without notice. Real ARM hardware avoids the emulator signatures some systems flag — but that is not a guarantee, so check the rules of anything you care about.
There is no XCloudPhone app to download. Everything runs in a browser tab — convenient on desktop, workable on mobile, but you are subject to your browser's behaviour.
No. An emulator runs Android on your own computer by translating app code for a desktop processor. A cloud phone is a physical ARM Android device in a datacenter that you reach through a browser — your machine only receives video.
It can be either, depending on the provider — many cloud phones are virtual machines sharing an ARM server. On our fleet it is a real phone: a physical ARM board with its own chip, memory, storage, and hardware identity, wiped through Android recovery between rentals the way a physical device is.
Yes. It runs in a browser, so any device with a modern browser and a stable connection works — Windows, macOS, Linux, Android, or iOS. There is no app to install.
Yes, for as long as the rental period you paid for. The device is powered in the datacenter and does not depend on your machine being awake. When the paid block ends, the device stops — there is no auto-renew.
Rentals are prepaid by block — hourly, daily, weekly, or 30-day — and the effective hourly rate falls on longer blocks. There is a free 2-hour trial that requires no card. See the pricing page for current rates.
It depends entirely on the game, and it can change without notice. Real ARM hardware avoids the emulator fingerprints some anti-cheat systems look for, but no provider can guarantee any particular game will allow a remote device. Check the terms of the games that matter to you.
The device is wiped. Each device gets a factory reset through recovery plus a storage clear, verified before it returns to the rental pool. Back up anything you need, or keep it tied to an account you can sign into again.
Yes. You assign your own proxy to a device — we do not sell, supply, or resell proxies.
Spin up a real Android cloud phone on the same fleet as a paid rental — no card required. Sign in with Google and the two hours are credited automatically.
