How to Set Up Kameleo for Android Profiles on Desktop

Is There Still a Kameleo App for Android?

No — nothing installs on a phone. The native Kameleo Android app stopped working on 28 September 2025, and support for physical mobile profiles was removed permanently. Kameleo for Android now means an emulated Android profile created in Kameleo Desktop on Windows or macOS: a Chromium-based session that reports mobile values to websites and cannot run Android apps.

What “Kameleo for Android” Means Today

The native app was retired, not paused

Kameleo’s end-of-support notice gives the date and the outcome: on 28 September 2025 the Android app stopped working, and support for physical mobile profiles was removed permanently. Users were told to rebuild their profiles as emulated mobile profiles in the desktop app. Any walkthrough that still describes an APK download, a QR pairing step or a phone-to-desktop bridge is documenting a product that no longer exists.

So the phrase covers two different questions. “Can I run Kameleo on my phone?” — no. “Can I run an Android-shaped browser profile from a laptop?” — yes, through emulation. The rest of this guide handles the second question, because that one has a working answer.

Emulated mobile profiles are the replacement

You build one in the desktop app: New Profile → Device: Mobile → Android (Chrome) or iOS (Safari) → Save & Start. The profile runs inside Chroma, Kameleo’s Chromium-based engine, carrying mobile values for canvas, WebGL, AudioContext, screen size, user agent, hardware specs and locale, drawn from a library of Android and iOS configurations.

What you don’t get is a phone. There is no Android runtime, no Play Store and no native app. If the work depends on an app-only feature — push notifications, an in-app inbox, a seller dashboard that exists only in the app — an emulated profile won’t supply it. For anything that renders in a mobile browser, the emulation covers what a site can actually read.

How Mobile Emulation Works Under the Hood

No website sees “a phone”. It sees the values a browser reports and the behaviour it exhibits. An emulated mobile profile lines up five surfaces:

• User agent and client hints — the UA string plus the hints naming platform, device class and browser brand.
• Viewport, screen and pixel ratio — CSS viewport width, screen dimensions, orientation and device pixel ratio, which together decide the responsive breakpoint you land on.
• Touch and input — whether the browser reports touch points and fires touch events instead of mouse events.
• Rendering surfaces — canvas, WebGL and AudioContext output, which differ between mobile GPU classes and desktop ones.
• Hardware and locale — reported core count and memory class, plus the language and timezone pairing that should match where the profile claims to be.

Kameleo applies these inside the engine rather than through a plugin, which is why the mobile type is baked in at creation and can’t be edited afterwards. Two engines do the work: Chroma, Chromium-based, handles desktop and mobile profiles and is the default for new ones; Junglefox, Firefox-based, serves Firefox-style profiles and supports Playwright. The current Chroma build is based on Chromium 157.0.8103.27 and ships alongside Chrome and Firefox releases — worth tracking, because a profile reporting a browser build many major versions behind is itself an inconsistency, whatever its device values say.

Server-side checks split into two families, and it helps to know which one you are fighting. User-agent sniffing reads the UA string and client hints; responsive design reads the viewport the browser reports. Both are fixed at profile launch, which is why a wrong value means restarting the profile rather than reloading the page. If a site serves you a desktop layout from a profile you built as mobile, compare the UA string first and the reported viewport width second — those two account for most of the gap.

Emulation stops at the browser boundary. Fingerprint values live inside Chromium; the IP address doesn’t. A carefully built Android profile leaving through a datacenter IP in a country that contradicts its locale is still mismatched, and that is the mismatch most people create for themselves.

Who Needs an Emulated Android Profile — and Who Doesn’t

Three groups get real value from one:

• Agencies and social media managers checking how a post, story or landing page renders at phone width, with each client’s session kept separate from the next.
• QA and support teams reproducing layout bugs and broken checkout flows that only appear on a small viewport, without passing a handset around the office.
• Sellers and marketplace teams verifying a listing, promo page or checkout on mobile before a campaign, on accounts they own or manage for a client.

What it doesn’t do is change what a platform allows. If a site caps how many accounts one person or business may hold, a mobile profile doesn’t move that cap. Amazon requires approval for an additional seller account, and Meta routes agency access through Business Manager roles and permissions. A profile manager makes authorised parallel work manageable; it doesn’t create permission you never had.

If the real need is “twenty Android phones running our app”, book a device farm or a cloud phone service. Neither Kameleo nor Send.win loads an APK, and no browser profile manager will.

Step-by-Step: Building a Working Android Profile

This is the checklist I’d hand to someone creating their first mobile profile.

1. Check the desktop app installs. Kameleo ships Windows and macOS builds, with macOS 13 or newer required since version 5.4.0; Linux runs through the official Docker images for Linux and Windows containers.
2. Choose the platform before anything else. Android pairs with Chrome, iOS with Safari. The type is locked at creation, so decide once.
3. Create the profile. Set Device to Mobile, pick Android (Chrome), then Save & Start. Take the generated fingerprint unless you’re targeting a specific handset class, in which case adjust screen size, hardware or locale first.
4. Attach a proxy that matches. Enter an HTTP, HTTPS, SOCKS5 or SSH proxy on the profile. Kameleo supplies no proxy traffic, so the exit IP is your responsibility; keep country, timezone and language consistent, and follow a walkthrough to set up a Kameleo proxy if this is your first one.
5. Verify before you log in. Load a page that echoes your user agent, viewport width, device pixel ratio and touch support. If the numbers don’t match the device you chose, fix them now rather than after an account has seen the profile.
6. Fix click behaviour if it breaks. If taps land in the wrong place on an emulated screen, the deviceScaleFactor launch option overrides the fingerprint’s pixel ratio so coordinates line up with what you actually see.
7. Write the profile’s details down. Name it by client and platform — acme-android-eu — and record the device class, the proxy country and the date you verified it. When three people share one desktop, that note is what stops two of them opening the same account at once.

Two minutes of checking after the first launch saves a rebuild later. Open a page that reports navigator.userAgent, window.innerWidth, devicePixelRatio and navigator.maxTouchPoints, and compare all four with the device class you picked. If the UA says Chrome on Windows while the viewport says 390px, the profile launched without its mobile layer and nothing downstream will be consistent.

Plans, Limits and the Costs Around Them

Emulated mobile slots are where the tiers diverge, so pick a plan around how many mobile profiles you need running at once.

Two costs sit outside the subscription. Local profiles are unlimited on every plan, so cloud profile counts don’t cap desktop work. Proxy traffic is never included — Kameleo accepts HTTP, HTTPS, SOCKS5 and SSH proxies but sells no bandwidth, so a proxy provider is a separate budget line. Local API rate limits also scale by tier at 60, 120, 600 or 1,200 requests per minute, which matters if people on your team write their own checks. Tier names and numbers have shifted repeatedly, so sanity-check the current grid on Kameleo’s four plan tiers before you budget.

If you’re upgrading, version 5.4.0 removed the Fingerprint Inspector launch option, its DevTools panel and the browser-extension guide, replaced the automated profile-count fields with a single total, and added a paged POST /profiles/search endpoint. Puppeteer users also had to move from pyppeteer to pyppeteer-ng.

Common Mistakes With Kameleo for Android Profiles

Hunting for the APK

Guides written before October 2025 still send people looking for a download that was withdrawn. There is no Kameleo client for Android and no supported way to put one on a handset.

Treating an emulated profile as a device

An emulated profile renders a mobile browser, nothing more. Teams that assume it will open an app, receive a push notification or expose a device ID end up rebuilding the workflow somewhere else.

Assuming you can switch platform in place

The mobile type is locked at creation. Changing Android to iOS or the reverse means a new profile, a new fingerprint and a fresh login on every account inside it.

Leaving the network behind

A mobile fingerprint exiting through a datacenter IP in the wrong country is an obvious mismatch, and no amount of canvas tuning fixes it. Match the proxy to the locale you chose, not the other way round.

Assuming the free plan carries a project

The free tier gives you 300 browser minutes a month, two concurrent browsers and two emulated mobile browsers. Layout testing eats that in an afternoon. Read what the €0 plan includes before you plan around it.

Where Send.win Fits — and Where It Doesn’t

Send.win is a browser profile manager, not a mobile emulator. Be precise about the split: if you need an Android user agent, a 390px viewport and touch events, that is Kameleo’s emulation or a physical device, and Send.win does not do it. If you need isolated desktop profiles for client accounts — each with its own cookies, storage, session, fingerprint settings and proxy — that is exactly what Send.win does, in the Sendwin Browser desktop app for Windows 10/11, macOS 12+ and Linux, or in the cloud browser running on Send.win’s EU server in Helsinki.

Each profile keeps its own consistent fingerprint — canvas, WebGL, audio, fonts, hardware — handled inside the browser engine, so profiles don’t share one browser identity. Residential proxies are included on Pro and Team with metered bandwidth, and timezone, locale, WebRTC and geolocation follow the proxy’s exit IP automatically, which removes the network mismatch that undermines otherwise careful setup work. For teams, share a profile with a paid teammate and it opens already signed in; cloud sync carries logins across devices. Pro covers 6 seats and 150 saved profiles, Team 16 seats and 500, and both allow up to 50 profiles open at once. It is a manual tool by design — you open a profile and work in it — so treat it as the home for day-to-day account work, not for mobile layout checks. If you’re still weighing the field, this Kameleo alternatives comparison covers the rest.

Frequently Asked Questions

Is there a Kameleo app for Android I can install on my phone?

No. The native Android app was discontinued on 28 September 2025, and support for physical mobile profiles was removed permanently. Nothing installs on a handset today. Mobile work happens through emulated mobile profiles in the Kameleo Desktop app on Windows or macOS.

How Send.win Helps With Kameleo For Android

Send.win is a browser profile manager for professionals and teams: every account gets its own isolated browser profile.

• Isolated profiles – separate cookies, storage and sessions per profile
• Fingerprint protection – each profile keeps its own consistent browser fingerprint, so profiles never share one browser identity
• Desktop app + cloud browser – native app for Windows, macOS and Linux, or run profiles in the cloud with no install
• Residential proxies included – on Pro and Team, with timezone and locale matched to the proxy
• Team sharing – share a signed-in profile with a teammate without sharing the password

Try the free cloud demo — no install — or download the desktop app. Paid plans start at $19/month, and your first card purchase is covered by a 7-day money-back guarantee (see pricing).

Can Kameleo emulate an Android phone on a desktop?

Yes. Choose Mobile under Device, select Android (Chrome), then Save & Start. The profile runs in the Chromium-based Chroma engine with mobile values for canvas, WebGL, AudioContext, screen size, user agent, hardware and locale taken from a library of Android and iOS configurations.

Does Kameleo mobile emulation run Android apps?

No. Emulated profiles run in a browser environment, so they have no access to device hardware or native Android apps. Anything app-only — push notifications, in-app inboxes, mobile-only dashboards — needs a real device, a device farm or a cloud phone service instead.

Can I change an emulated profile from Android to iOS later?

No. The mobile type is fixed when the profile is created, so switching platforms means building a new profile with a new fingerprint and logging into each account again. Decide the target platform before you store any credentials in a profile.

Does Kameleo have a free plan or a trial?

There is a free plan rather than a time-limited trial. It includes two concurrent browsers, 100 cloud profiles, 300 browser minutes a month, two emulated mobile browsers, three team members and Local API access at 60 requests per minute. Paid plans start at Startup, €59 per month or €45 per month billed annually.

Does Kameleo include proxies?

No. Profiles accept HTTP, HTTPS, SOCKS5 and SSH proxies, but Kameleo supplies no proxy traffic of its own. Budget for a separate proxy provider and keep the exit IP’s country consistent with the profile’s timezone and language.

Why do clicks land in the wrong place inside a mobile profile?

Usually the pixel ratio. The profile reports a device scale factor that doesn’t match the screen size you selected, so a tap at one coordinate registers somewhere else. Start the profile with the deviceScaleFactor option to override the fingerprint’s ratio, or rebuild the profile on a handset class whose screen dimensions and ratio agree.

Can I automate Kameleo mobile profiles with Selenium or Playwright?

Yes. The Local API listens on http://localhost:5050 by default and exposes a WebDriver endpoint there, and Selenium attaches with the kameleo:profileId capability. Python, JavaScript and C# SDKs are documented through OpenAPI, with request limits of 60, 120, 600 or 1,200 per minute depending on your tier.

Related Products & Resources

• Download
• Demo Browser
• Pricing
• Fingerprint Checker
• Canvas Fingerprint Test