Cloud Phone Technology Product Update | Introducing Multilogin Cloud Phones

Multilogin cloud phones are real Android devices hosted in the cloud — actual ARM hardware running Android 10 through 16, with their own device ID, hardware fingerprint, and session history. You control them from your computer through a live interactive stream. To Instagram, TikTok, WhatsApp, or any other mobile-first platform, each cloud phone looks and behaves exactly like a real person’s phone — because at the hardware level, it is one.

This guide covers everything: what cloud phones are, how they work, how to create and set up your first one, and how to use every feature in the interface.

What is a Multilogin cloud phone?

A cloud phone is a cloud-based Android environment that runs remotely on real ARM hardware. You don’t hold a physical phone — you open the cloud phone inside Multilogin and control it from your desktop through a live screen stream. Apps and platforms see it as a genuine Android device, not a virtual machine or desktop emulator.

With Multilogin cloud phones, you get:

• Real ARM-based Android environments accessible from your desktop
• Separate, isolated cloud phones for different accounts, clients, or tasks
• Unique device fingerprints and system properties per phone
• Dynamic sensor, battery, carrier, and network data that behaves like a real device
• No physical hardware to buy, charge, update, or maintain
• Built-in residential proxies included — 30M+ IPs across 150+ countries

This makes cloud phones the right tool for any mobile workflow where apps expect real phone-like signals: managing multiple Instagram or TikTok accounts, running WhatsApp for multiple clients, mobile ad verification, or any task where a desktop browser simply doesn’t produce the right device fingerprint.

How Multilogin cloud phones work

Real Android environments, not desktop emulators

Cloud phones run Android remotely in the cloud on actual ARM hardware. When you open one in Multilogin, you control a live Android screen from your computer. Apps work inside a genuine mobile Android environment — not a desktop browser pretending to be mobile, and not a physical phone connected to a server somewhere.

This matters because platforms like Instagram and TikTok check device signals at the hardware level. Emulators produce signals that differ from real hardware and get flagged. Multilogin cloud phones are built on ARM hardware following real mobile device standards, so the device setup looks natural to every app you run on it.

ARM-based hardware that matches real device standards

Each cloud phone runs on an ARM-based Android environment with hardware specifications that match real-world phone logic:

• Device model and brand (Samsung, Google Pixel, Xiaomi, OPPO, and more)
• CPU and GPU matching the selected device
• RAM consistent with the device model
• Android system version (Android 10–16)

These combinations are drawn from real-world phone data, so the hardware profile looks exactly like a genuine device to any app checking system properties.

How fingerprints and device identifiers work

Each cloud phone gets its own unique fingerprint. Even if two cloud phones use the same brand and model, they have different hardware-level identifiers — just like two real Samsung Galaxy S24s are not identical. Same family, different identity.

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

• Android ID
• IMEI
• GAID (Google Advertising ID)
• Build properties
• Device model and brand
• System properties

Apps like TikTok and Instagram read these values as part of the device environment. Identifiers stay consistent for the lifetime of a cloud phone — if you delete or reset the device, new identifiers are generated based on the device brand, model, and Android version.

What you can’t manually change: IMEI, serial number, Android ID, Build ID, bootloader status, and other device identifiers are generated automatically based on real device data mapping. These values cannot be edited manually.

Sensors, battery, and network data

Cloud phones simulate the background signals that apps check to determine whether a device is real. These include:

• Sensors: Accelerometer, gyroscope, and magnetometer values change dynamically — they don’t stay frozen at one position, which is a clear emulator signal that platforms detect.
• Battery: Battery level changes based on usage time. Cloud phones simulate normal charging and discharging states, so the battery never stays locked at the same percentage.
• Carrier and location: By default, carrier and phone number information match the configured IP region. If you use a US IP, the system assigns a US carrier (such as AT&T) and aligns GPS location with that region — so the device environment, carrier data, and IP all point to the same place.

What cloud phones can’t do

Cloud phones are built to look and behave like real Android devices. A few things are not supported:

• SMS codes and phone calls: Cloud phones cannot send or receive SMS verification codes or make or receive phone calls. If you need SMS verification, use a virtual phone number from an SMS provider — read How to complete SMS verification using Multilogin cloud phones.
• eSIM: eSIM is not supported.
• Manual device identifier editing: IMEI, Android ID, serial number, and Build ID are generated automatically. They cannot be changed manually.
• Local proxies: Cloud phones run on remote servers, so they cannot connect to local proxies like 127.0.0.1 or 192.168.x.x. Use a public proxy that works online.
• Root access: Root access is off by default. Contact support to check if it can be enabled for your use case.

Why use cloud phones instead of a physical phone farm?

Managing multiple Instagram or TikTok accounts on physical phones means buying hardware, maintaining SIM cards, managing charging and updates, and dealing with device failures. When a phone dies, that account loses its IP consistency and session history.

Multilogin cloud phones give you the same isolation — each account on its own real Android hardware identity, its own IP, its own session — without any of the physical overhead. Scale up by adding profiles, not by buying phones. See the full comparison: cloud phone vs physical phone farm.

How to create a Multilogin cloud phone

Creating a cloud phone is fast. Most settings come pre-filled — you name the phone, check the proxy, and click Create.

1. Go to the Profiles tab in the top menu
2. Select Mobile from the left-side selector
3. Click Create, or use the dropdown next to it to create phones in bulk

Profile name

Only you and your team can see profile names — apps and websites cannot. Name profiles in a way that makes them easy to find and manage. A few tips:

• Be specific: include the platform or purpose (e.g. “IG_Client_A” or “TikTok_Brand_UK”)
• Keep it short: 2–4 words max
• Use a naming convention if working in a team — so everyone can find what they need fast

Number of profiles

You can create one or multiple cloud phones in a single setup. When creating multiple at once, Multilogin generates clones of the same configuration — same device settings, proxy setup, network type, tags, and notes.

• You can create up to 100 phones in one batch
• Your plan limit applies — if your plan allows 10 profiles, you can only have 10 active at once
• After creation, you can edit each phone individually

Use case

Choose an app for the phone to make it easier to recognise in your profile list. With a large app library, you can quickly match each phone to its intended purpose at a glance.

Tags

Add up to 10 colour-coded tags per phone to group, filter, and find profiles fast. Tags are workspace-wide — a tag created in the mobile section also appears for browser profiles. Use them for clients, platforms, warm-up stages, or anything that fits your workflow.

Notes

Add short notes to individual phones or entire folders. Perfect for login details, account status, warm-up stage, client instructions, or handover context for team members. Maximum 1,500 characters per note.

Folder

Organise phones into custom folders by client, project, or status. Cloud phones and browser profiles use separate folder systems — they are not shared or synced between the two profile types.

Proxy settings for cloud phones

Every cloud phone needs a proxy to go online and keep its IP, location, and network signals consistent. Cloud phones cannot function without a proxy. There are three ways to assign one:

Multilogin built-in proxy

Every paid Multilogin plan includes built-in residential proxy traffic — access to 30M+ premium residential and mobile IPs across 150+ countries. This is the fastest setup: select Multilogin proxy, choose a location, and you’re done. See the full Multilogin proxy guide for details on included traffic and options.

Custom proxy

Connect any HTTP, HTTPS, or SOCKS5 proxy from your preferred provider. Password authentication and IP authentication are both supported. You’ll need the proxy type, IP, port, and login credentials if required. See how to use custom proxies in Multilogin.

Proxy template

Save your proxy settings as a reusable template and apply them to multiple profiles or phones in seconds. Useful for teams managing large numbers of accounts with consistent proxy configurations. See the proxy template manager guide.

Note on device info: The device information shown for a cloud phone is based on the proxy IP at the time of profile creation. If you change the proxy later, the device info display stays the same — this is display-only and does not affect actual proxy masking or performance. To match device info with a new proxy location, create a new cloud phone profile with the desired proxy.

Device settings

OS version

Choose the Android version your phone runs on (Android 10–16).

• Android 14–16: best for modern apps and ad accounts
• Older versions: only if a specific app requires it

Device brand and model

Choose the manufacturer and exact model for your cloud phone. The default is Random — Multilogin selects a popular, real-world brand and matching model automatically. You can also choose manually.

Available brands include Samsung, Google, Xiaomi, OPPO, Redmi, OnePlus, vivo, HONOR, Motorola, realme, Infinix, and TECNO. Models are drawn from real devices and sorted from strongest to weakest for each brand — pick a model closer to the top of the list for heavier tasks.

Extra settings

Network type

The network type defines how your cloud phone appears to connect to the internet.

Phone number

Cloud phones cannot send or receive SMS codes or calls. Choose what works for your setup:

• Auto-generated number: use this if you’re managing existing accounts or don’t need verification
• Custom number: enter a real or virtual number from a provider — you’ll receive verification codes on your actual device or in your provider dashboard. Apps can read this number as part of the phone environment.

Location

Set where the device appears to be from: use the proxy IP location, or choose a country manually. For example, your device can be configured as coming from Singapore while the proxy IP is in London. This gives you flexibility when setting up profiles for specific regions.

How to use cloud phone features

When you start a cloud phone in Multilogin, a live phone screen opens and a tool menu appears on the right side. Here is what each tool does:

• Connection: checks your proxy connection status in real time
• Timer: tracks how long the cloud phone has been active — useful for monitoring usage, since cloud phones are billed per minute
• Rotate: switches the screen between portrait and landscape — helpful for apps or games that work better sideways
• Screenshot: captures the current screen and saves it to the phone’s memory. Find it in Files → Images → Pictures or Files → Downloads
• Upload: transfers files from your computer to the cloud phone — for uploading creative assets, content, or media files
• Export: downloads files (not folders) from the cloud phone back to your computer
• Camera: functions like a real phone camera — use it for scanning QR codes or verification tasks. You can also stream your PC camera to the cloud phone, or upload a pre-recorded .mp4 file as a camera stream
• Apps: install, update, and uninstall apps. See how to install apps on cloud phones
• Mirror (in More): shows a QR code and link so you can continue using the cloud phone from your mobile browser

To open the phone’s app menu, scroll up on the phone screen: click the screen, drag upward, then release.