What is a cloud phone?

A cloud phone is a cloud-based Android environment that runs remotely.

You don’t hold a physical phone in your hand. Instead, you open the cloud phone in Multilogin and control it from your computer through a live interactive stream.

Cloud phones help when your task needs a mobile Android setup, not a desktop browser pretending to be mobile.

With cloud phones, you get:

• Android environments you can access from your desktop
• Separate cloud phones for different tasks or accounts
• Device fingerprints and system properties
• ARM-based Android setup
• Dynamic sensor, battery, carrier, and network data
• Less hardware to buy, charge, update, and protect from coffee

This makes cloud phones useful for mobile workflows where apps expect a real phone-like setup.

What cloud phones can and can't do

Cloud phones are built to look and behave like real Android devices. Still, some things are not manually editable or supported.

You can't manually change:

• IMEI
• Serial number
• Android ID
• Build ID
• Bootloader status
• Other device identifiers

These values are generated automatically based on real device data mapping.

You also can't use cloud phones to:

• Send or receive SMS codes
• Make or receive phone calls
• Use eSIMs

If you need SMS codes or phone calls for account verification, use an SMS service provider. Read the article How to complete SMS verification using Multilogin cloud phones for more info.

How cloud phones work

Cloud-based Android environment, not a desktop emulator

Cloud phones run Android remotely in the cloud.

When you open one in Multilogin, you control a live Android screen from your computer. Apps work inside a mobile Android environment, not a regular desktop browser setup.

Cloud phones are also not physical phones connected to a server. You get a remote Android environment that behaves like a mobile device, without managing physical hardware yourself.

ARM-based hardware

Cloud phones run on an ARM-based Android environment.

That means the hardware setup follows real mobile device standards, including:

• Device model
• CPU
• GPU
• RAM
• Android system version

These combinations match real-world phone logic, so the setup looks natural to mobile apps.

Native mobile rendering

Apps and websites render inside a real Android environment.

This helps mobile-first platforms see the device as a phone, with phone-like system properties, hardware details, and behavior signals.

How fingerprints and identifiers work

Each cloud phone gets its own fingerprint.

Even if two cloud phones use the same brand and model, they still have different hardware-level identifiers. Just like two real iPhones or Android phones are not identical twins. Same family, different personality.

Cloud phones generate device data based on real brand, model, and Android version rules, including:

• Android ID
• IMEI
• GAID
• Build properties
• Device model
• Brand
• System properties

Apps such as TikTok and Instagram can read these values as part of the device environment.

Sensors, battery, and network data

Cloud phones also simulate small background signals that apps may check. These details help the device feel less “empty” and more like a real phone in daily use.

Sensors

Cloud phones simulate dynamic sensor data, including:

• Accelerometer
• Gyroscope
• Magnetometer

This means sensor values are not frozen in one place. They change in the background to better match natural phone behavior.

Battery

Battery level changes based on usage time. Cloud phones also simulate normal battery states, such as charging and discharging.

This helps avoid fixed battery data, where a device always shows the same percentage or state. Real phones do not stay at 87% forever. Cloud phones don't either.

Carrier and location

By default, carrier and phone number information match the configured IP region.

For example, if you use a US IP, the system can assign a US carrier such as AT&T and align GPS location with that region.

This helps the device setup look more consistent because the phone environment, carrier data, GPS location, and IP region point to the same place.

FAQs

Are Multilogin cloud phones real phones or emulators?

Cloud phones are cloud-based Android environments.

They aren’t physical phones connected to a server, and they aren’t regular desktop emulators running on your computer. You control them through a live interactive stream in Multilogin.

In simple words: you get an Android phone-like workspace in the cloud, streamed to your screen.

Can I manually edit IMEI, Android ID, serial number, or build ID?

No. Device information can't currently be modified manually. Cloud phones generate these values automatically based on real device data mapping.

Do identifiers stay consistent?

Yes. Identifiers stay consistent while the cloud phone exists. After you delete or reset the device, the system creates new identifiers based on the device brand, model, and Android version.

Do different cloud phones share the same fingerprint?

No. Each cloud phone has a unique fingerprint. Even devices with the same brand and model have different hardware-level identifiers.

Can cloud phones pass emulator or integrity checks?

Cloud phones are built to run as native Android environments, not regular desktop emulators.

Still, detection results can depend on the app, Android version, proxy, account history, and usage pattern.

Financial apps may use stricter checks, including Google Integrity. For these cases, use the Android version recommended by Multilogin support.

Do cloud phones support camera injections?

Yes, that feature is available in the “Camera” tab. There is an option to stream the camera of your PC to the cloud phone. Or you can upload .mp4 file instead as a pre-recorded stream.