[cdpfleet](https://cdpfleet.com/) / [Android & iOS](https://cdpfleet.com/mobile) / Android

Phones · Android · early access · hardware

# Android browsers on *real phones*.

Real Android phones — hardware, not emulators — with the browsers people actually use on them. Drive Chrome and Samsung Internet with Playwright's `connectOverCDP` or Puppeteer, and reach the in-app WebView and Custom Tabs that apps embed.

[Sign up free](https://cdpfleet.com/app#sign-up)[Phones overview](https://cdpfleet.com/mobile)

-   **6**browsers and in-app engines
-   **CDP**Playwright · Puppeteer
-   **3–4**threads per session

## Browsers on the phones

| Browser | How you drive it |
| --- | --- |
| Chrome | Playwright (`connectOverCDP`), Puppeteer |
| Chrome Custom Tabs | In-app Chrome, as apps open links |
| Samsung Internet | Playwright (`connectOverCDP`), Puppeteer |
| Opera | Puppeteer |
| Android WebView | The in-app WebView most Android apps embed |
| Firefox | Firefox's remote debugging protocol |

## Why hardware

-   The page runs on a real phone, in the browser build the phone ships — not a desktop browser with a phone user agent.
-   **In-app engines too:** the WebView that apps embed and Chrome Custom Tabs, next to the Chrome app itself.
-   **Country presets** match the phone's locale, timezone and GPS to your exit IP, so the phone doesn't contradict its own network.

## Connecting

Android sessions speak CDP: connect Playwright's `connectOverCDP` or Puppeteer to the session's endpoint, exactly as with [desktop browsers over CDP](https://cdpfleet.com/docs/cdp). A WebView session takes 3 [threads](https://cdpfleet.com/threads), a full browser such as Chrome 4.

## Early access

Android sessions are in early access. [Write to us](#contact) and tell us which browsers and countries you need.

For layout checks today, [device emulation](https://cdpfleet.com/docs/examples#device-emulation) runs on every Chromium-based browser on the fleet.

## Related

Cases, recipes, posts and comparisons about this — updated as new ones are published.

### Reference docs

The details, options and errors.

-   [CDP & Puppeteer](https://cdpfleet.com/docs/cdp)Connecting over the Chrome DevTools Protocol.
-   [Mobile device emulation](https://cdpfleet.com/docs/examples#device-emulation)Phone viewports on desktop engines.
-   [Proxies](https://cdpfleet.com/docs/proxies)Residential exits from Android devices (`-os-android`).

### Cases 1

Real problems solved end to end, run on production in five languages.

-   [Case 2: Emulating an iPhone on real Chrome: what changes, and what gives you away](https://cdpfleet.com/docs/cases/mobile-emulation)Playwright device descriptors fix the viewport, touch and user agent — and leave five tells a site can read.[Code on GitHub](https://github.com/cdpfleet/cdpfleet/tree/main/cases/02-mobile-emulation)

### Browser comparisons 2

Measured side by side on the fleet.

-   [WebKit vs the Safari it claims to be](https://cdpfleet.com/docs/compare/webkit-vs-safari-claims)Playwright's WebKit 26.4 sends a Mac Safari 26.4 user agent, but reports Linux x86\_64, sets navigator.webdriver, offers only HTTP/1.1, renders with Linux fonts and…
-   [WebKit vs Chromium](https://cdpfleet.com/docs/compare/webkit-vs-chromium)Playwright's WebKit 26.4 claims a Mac in its user agent but reports Linux, sets navigator.webdriver and speaks HTTP/1.1 through a proxy. Where it beats Chromium…

## Read next

[Android & iOS →](https://cdpfleet.com/mobile)[iOS WebView →](https://cdpfleet.com/iphone)[Browsers →](https://cdpfleet.com/browsers)

---
Source: https://cdpfleet.com/android · Markdown: https://cdpfleet.com/android.md · All docs for AI tools: https://cdpfleet.com/llms.txt