Android (mobile) profiles
Set a profile's operating system to Android and it opens as a phone: phone screen, touch, and a mobile user agent.
On this page
Some sites only show their full features to phones, and some accounts look wrong if they've only ever been used from a desktop. An Android profile makes one profile read as a phone: the screen size, pixel ratio, touch, orientation and user agent all come from the handset you pick.
The window still opens on your computer. This is a real desktop browser reporting itself as a phone, not an Android emulator.
📱 Make a profile Android#
- Open the profile's editor (row ⋯ → Edit), or click New Profile.
- On the Overview tab, under Operating system, pick Android.
- A Phone box appears. Pick the handset:
- Google Pixel 8 — 412×915 @2.625x
- Google Pixel 9 — 412×923 @2.625x
- Samsung Galaxy S23 — 360×780 @3x
- Samsung Galaxy S24 — 360×780 @3x
- Samsung Galaxy A54 — 412×892 @2.625x
- Click Save changes (or Create profile).
The browser window opens at the phone's width, so it looks like a tall narrow strip on your monitor. That's correct: the page is being told it's on that screen.
Chromium only
Android profiles run on the Chromium engine. Don't set Browser engine to Firefox on an Android profile — the Firefox engine has no Android identity to present, so the profile shows up as Windows instead.
🔍 What the phone choice sets#
Picking a handset pins everything a site reads to tell a phone from a laptop:
| Trait | From the handset |
|---|---|
| Screen size and window size | Its CSS size, for example 412×915 |
| Device pixel ratio | 2.625 or 3, as the phone reports |
| Touch | 5 touch points, touch events, coarse pointer, no hover |
| Orientation | Portrait |
| Graphics chip | The phone's real GPU, such as Adreno 750 or Mali-G715 |
| Model | Travels in the client hints, as on a real Chrome for Android |
| User agent | Chrome for Android's frozen string |
Everything else works as on any profile: the proxy, the time zone that follows it, cookies, extensions and Flows.
Pair a phone profile with a mobile proxy
An Android profile exiting from a datacentre IP is a phone on an office network, which is unusual. If you have an Android phone spare, use it as the proxy. See Use an Android phone as a mobile proxy.
🧪 Check it looks right#
Open the profile's Fingerprint check (row ⋯ → Fingerprint check). Android profiles get extra rows for touch points, touch events, pointer and hover, pixel ratio, orientation, viewport and the mobile client hint, so you can see the phone identity is consistent. See Check a profile's fingerprint.
❓ Common questions#
Does this run Android apps?
No. It's a desktop browser presenting itself as Chrome on a phone. Sites see a phone. There's no Play Store and no APKs.
Can I pick any phone model?
Only the five listed. Each one is a real device whose screen, pixel ratio, GPU and model number are known to match, which is the point — a made-up phone is a contradiction a site can spot.
Can I change the screen size of a phone profile?
No. The size comes from the handset, along with everything that has to agree with it.
Can I drag the window bigger?
You can resize the window, but the page keeps being told the phone's screen size. Leave it at the size it opens at for the most convincing result.
How much RAM and how many cores does it report?
8 cores, and 8 GB of memory — which is what Chrome on Android reports even on a phone with more.
Do Flows work on Android profiles?
Yes, the same as any Chromium profile. See What Flows are and what they can do.
ℹ️ Good to know#
- To make a batch of phone profiles, set Operating system to Android in Settings → Profile defaults first, then use Add multiple profiles. See Default settings for new profiles.
- Switching an existing profile between Android and a desktop operating system rebuilds its fingerprint. To a site that's a different device, so do it before the profile has accounts in it.
- If you pick Android without choosing a handset, LoginDeck picks one for you and keeps it.