Multilogin X now offers Android profiles! Currently, they are available via our API, and a UI version is coming soon.

Understanding Android profiles

What are mobile profiles?

Mobile profiles in Multilogin X are browser profiles that simulate an Android device. Instead of appearing as a desktop user, you’ll look like someone browsing from a smartphone, making them ideal for activities where mobile-like behavior is required.

Why use mobile profiles?

They’re perfect for testing, managing accounts, or automating tasks that require a mobile device’s fingerprint. Mobile profiles help you blend in as a mobile user and interact with websites designed for smartphones.

Can I convert an existing desktop profile to a mobile profile?

No, mobile profiles must be created as new profiles. They cannot be converted from desktop profiles.

Can I install mobile apps on mobile profiles?

No, Android profiles in Multilogin do not function as actual mobile devices, so installing mobile applications is not supported.

Using Android profiles via API

Creating and updating

To manage mobile profiles, use the following API endpoints:

• Profile Create: For creating mobile profiles
• Profile Update and Profile Partial Update: For making changes to existing profiles
• Start Quick Profile v3: For starting quick mobile profiles

Default settings

Note that the following flags cannot be set to "Real" when creating or updating profiles:

• fonts_masking
• graphics_masking
• media_devices_masking
• navigator_masking
• screen_masking

These settings ensure optimal performance and stability for Android profiles.

Recommended settings

First, we recommend that you set the chosen URL(s) to open on every launch. Here's the code example:

{
    "parameters": {
        "flags": {
            "startup_behavior": "custom"
        },
        "custom_start_urls": [
            "https://app.multiloginapp.com/WhatIsMyIP"
        ]
    }
}

Then, stick to the following values for best results:

• Screen resolution: Masked (default)
• Media devices: Masked
• WebGL + WebGPU metadata: Masked
• WebGL graphics: Noise
• Canvas graphics: Real
• AudioContext: Noise
• Font data: Masked (default)

Max touch points

This parameter determines how many simultaneous touch-points the Android device can support.

• Parameter: max_touch_points
• Acceptable values: 1–10 (default is 5 if not provided)
• Example: "max_touch_points": 2 means the device supports two touch-points.