Android cloud phones: real Android in a browser tab
An Android cloud phone is a complete Android device that runs in a datacenter and streams to your browser. DeviceFarm cloud phones run Android 10 to 16 on ARM phone hardware, not an emulator on a PC: install apps or your own APK, set the GPS position, attach a proxy, and use ADB on Android 11 to 16.
Last updated
No credit card required
What Is an Android Cloud Phone?
An Android cloud phone is an Android device you operate over the internet: it runs in a datacenter, and its screen streams to your browser, so you use it without holding it. Each DeviceFarm cloud phone runs Android 10 to 16 on ARM phone hardware with its own persistent device identity and proxy slot, on plans from $39.99 for 20 phone slots plus runtime.
The phone sits in a datacenter; its screen streams to your browser, and your clicks and keystrokes travel back as taps and typing. Apps run on the phone itself, not on your computer, so they use none of your laptop’s memory or processor.
DeviceFarm runs real Android on ARM phone hardware, not an emulator. Each phone is an isolated Android device with its own persistent identity (IMEI, Android ID, MAC and Bluetooth MAC, Wi-Fi BSSID, serial, model, timezone and locale) and its own proxy slot, which you fill with a proxy of your choice.
One naming trap: in business telephony, a "cloud phone" or "cloud phone system" means a VoIP line. An Android cloud phone is not a phone line. It has no SIM card and no carrier number; it is an Android device you operate remotely.
A real Android phone, kept in our datacenter
Each DeviceFarm phone is real Android running on ARM servers in our datacenter. It works like the Android phone you have at home, except you open it in your browser instead of holding it.
Real Android, on ARM servers
A complete Android system, Android 10 to 16, running natively on ARM servers: the same chip architecture as the phone in your pocket. Not an emulator, not an Android VM on a PC.
Used like the phone in your hand
Install apps from the catalog or your own APK, sign in, tap, swipe and type. Apps run on it natively, the way they run on an Android phone.
Kept in our datacenter
It stays on when you close the tab, keeps its own identity and proxy slot, and you control it from your browser on devicefarm.io. It has no SIM card, so no calls or carrier SMS.
Why use an Android cloud phone?
Because it gives every account a real Android phone of its own, without a single handset on your desk. What that changes in practice:
- Every account stays separate. Each phone keeps its own persistent identity (IMEI, Android ID, MAC, serial, model) and its own proxy, so the accounts you run never share a device or an IP.
- A real phone without buying one. Real Android on ARM servers in our datacenter, ready in under 60 seconds, with nothing to buy, charge, update or replace when it breaks.
- It keeps working when you log off. The phone stays on in the datacenter after you close the tab, so sessions and scheduled tasks carry on around the clock.
- One account or thousands, same dashboard. Plans go from 20 to 6,000 phones; move up a tier whenever you need, and watch up to 24 phones live side by side.
- Your whole team on the same phones. Invite unlimited members at no extra cost and assign phones per member, with no passwords passed around.
- The repetitive work done for you. With the Automation add-on ($99 a month), scheduled automations run on TikTok, Instagram, Facebook, YouTube, Reddit, Threads, X, Pinterest, Gmail and Telegram, and you can drive phones from code through the REST API or from Claude through the MCP server.
And everything you would do by hand on a phone is there: install apps from the catalog or your own APK (up to 512 MB), open an ADB shell on Android 11 and newer, set the GPS position, language and location, rotate a proxy IP on demand, and clone, start or stop phones in bulk.
Which Android versions and device models are available?
DeviceFarm phones run Android 10, 11, 12, 13, 14, 15 or 16, chosen when you create the phone. Each version comes with its own catalog of device brand and model profiles, and the profile you pick stays with the phone for its whole life, alongside its IMEI, Android ID, MAC and Bluetooth MAC, Wi-Fi BSSID, serial, timezone and locale. The device fingerprint entry explains which of these values apps can actually read.
The version also decides what tooling you get. ADB access works on Android 11 and newer, not on Android 10, so create the phone on Android 11 or later if you plan to script it.
Is an Android cloud phone a real phone or an emulator?
DeviceFarm phones are real Android running natively on ARM servers, so ARM apps run without a translation layer and each phone keeps one identity across sessions. That matters because an Android emulator is easy to spot: it runs on an x86 PC, carries emulator files and drivers, and does not pass Google’s device integrity check, which Google’s Play Integrity documentation reserves for real Android devices. Some cloud phone services are emulators on x86 servers. Our guide to what a cloud phone is compares the three architectures sold under the name and shows how to check which one you are getting.
How do you use a cloud phone from your browser?
There is nothing to install. Sign in, open a phone, and its screen streams into the tab; your mouse and keyboard become taps and typing. Multi-view tiles up to 24 phones on one screen when you need to supervise a fleet.
Automations keep running when you close the tab, because the work happens on the phone, not in your browser. A phone you opened by hand that nobody is watching and that has no automation running is stopped automatically after about 10 minutes, so a forgotten tab does not keep billing runtime.
What can't an Android cloud phone do?
- Receive calls or SMS on a carrier number. There is no SIM card and no eSIM, so verification codes have to come from a number you hold elsewhere.
- Make tap-to-pay payments over NFC.
- Run fast action games well. Every frame travels over the network, and that delay shows in twitch gameplay.
- Run iOS apps. These are Android devices only.
- Replace an automated test lab. For running one test suite across many device models in CI, AWS Device Farm or BrowserStack is the better fit.
How much does an Android cloud phone cost?
Phones come in fleets: a 30-day plan starts at $39.99 for 20 phone slots ($2.00 per slot before runtime) and falls to about $0.14 per slot at 6,000. Runtime is billed only while a phone runs: $0.012 a minute, capped at $2.10 per phone per day, and every paid plan includes 60 free minutes a month, shared by the whole account. Built-in automations, the REST API and the MCP server come with the Automation add-on, at $99 a month on top of the plan.
In practice, one phone running an hour a day adds $0.72 a day in runtime. The full tier ladder is on the pricing page, and worked examples for a 20-phone fleet are on phone farm rental. Comparing providers? See why teams running accounts choose DeviceFarm over Redfinger and LDCloud: one plan for a whole fleet, a separate identity and proxy slot on every phone, unlimited team seats and direct support.
Is there a free Android cloud phone trial without a credit card?
Yes. Creating an account needs no card, and the trial gives you a phone with a few runtime minutes. Spend them on the checks that matter for your work:
- Install the app you plan to run, from the catalog or as your own APK.
- Attach your proxy and confirm the phone reaches the internet from that IP.
- Judge the stream from where you sit: open the phone and scroll an app feed.
- If you script, create the phone on Android 11 or later, enable ADB and run one command.
Who is an Android cloud phone not for?
- Someone who wants one free phone to leave a game running. Plans start at 20 phones, so a single gaming phone makes no sense here.
- Anyone who needs iPhone or iOS devices.
- Teams running automated tests across many device models in a CI pipeline; DeviceFarm vs AWS Device Farm explains the difference.
- Workflows that depend on a SIM card or a carrier phone number inside the device.
If you need many phones for many accounts, the cloud phone farm page covers running a fleet, and antidetect cloud phones covers how device identity and proxies fit together.
Built on real hardware, run from your browser
Apps and your own APKs
Add apps from the built-in catalog or upload .apk and .xapk files up to 512 MB, then choose which ones install automatically on your phones.
ADB on demand
Turn ADB on for a running phone and connect from your terminal with two commands. Available on Android 11 to 16.
GPS, language and location
Set the GPS coordinates apps read, and choose language and location at creation so the phone's settings match the account's market.
A proxy slot per phone
SOCKS5, HTTP or HTTPS, one per phone, with an optional refresh URL to rotate the IP whenever you need a new one.
Stops itself when forgotten
A phone opened by hand that nobody is watching and that runs no automation is stopped after about 10 minutes, so it stops billing runtime.
API and Claude control
With the Automation add-on ($99 a month), create, start, script and delete phones from your own code through the REST API, or describe the task to Claude through the MCP server.
Why a Cloud Phone Beats an Android Emulator
An Android emulator is software imitating a phone on a PC. Apps can tell, and Google’s Play Integrity check does not count an emulator as a real Android device. A DeviceFarm cloud phone is real Android running natively on ARM servers, used from your browser.
| Android emulator on a PC | DeviceFarm Android cloud phone | |
|---|---|---|
| What apps can detect | Emulator traits: an x86 processor translating ARM apps, emulator files and drivers, and device values generated by the software | Real Android running natively on ARM, with no emulator software and no x86 translation layer |
| Google Play Integrity | Fails the device integrity check: Google keeps its emulator label for Google Play Games on PC, so apps that require a real device can refuse to run | Runs as an Android device on ARM servers, not as emulator software on a PC |
| Device identity | Generated by the emulator and often identical across copies of the same software, so separate accounts look alike | A unique, persistent identity per phone (IMEI, Android ID, MAC, serial, model), kept across sessions |
| Network | Every instance shares your home or office IP unless you set up proxies one by one | Its own proxy slot per phone, set from the dashboard |
| Where it runs | On your computer: each instance eats RAM and CPU and stops when the PC sleeps | In our datacenter, around the clock; all you need is a browser tab |
| Scale | As many instances as one machine can carry | Fleets of 20 to 6,000 phones, up to 24 live on one screen |
| Team access | Whoever sits at that computer | Unlimited teammates at no extra cost, from any desktop browser |
| Cost | Free software, paid for with your computer, power and time | From $39.99 for 20 phones per 30 days, plus runtime capped at $2.10 per phone per day |
How to Get an Android Cloud Phone in Four Steps
- 1
Create a free account
Sign up in your browser with no credit card. The trial includes a phone and a few runtime minutes.
- 2
Choose version and profile
Pick Android 10 to 16, a device brand and model profile, a language and a location. The phone is live in under 60 seconds.
- 3
Add a proxy and apps
Attach a SOCKS5, HTTP or HTTPS proxy, then install apps from the catalog or upload your own APK.
- 4
Use it your way
Operate it by hand in the browser or script it over ADB. With the Automation add-on, use the REST API or hand the task to Claude through MCP.