Getting Multilogin installed and running your first browser profile takes under 20 minutes if you follow the steps in the right order. I have set this up across Windows, Mac, and Linux environments for client operations — the process is consistent across platforms once you know what to expect.
This guide covers downloading Multilogin X (the current version), installing it on your OS, creating your first browser profile with a solid fingerprint configuration, and connecting a proxy. If you hit a snag along the way, the troubleshooting section at the end covers the errors I see most often.
What you need before you start:
- A Multilogin account (free trial or paid plan)
- A computer running Windows 10/11, macOS 10.15+, or Ubuntu 18.04+
- A proxy if you are running multiple accounts (optional for initial setup, required for multi-account operations)
Download Multilogin and start your trial
System Requirements & Platforms
Multilogin X runs as a desktop application with a local agent process. The agent handles the browser fingerprint injection and profile isolation on your machine; the dashboard (where you manage profiles, teams, and settings) runs in your regular browser and connects to the local agent.
This architecture means Multilogin is not purely cloud-based — you need the agent installed and running on any machine where you want to launch browser profiles.
Windows
Minimum requirements:
- Windows 10 64-bit (build 1903 or later) or Windows 11 64-bit
- 4 GB RAM (8 GB recommended for running multiple profiles simultaneously)
- 2 GB free disk space for the application; additional space per profile
- Stable internet connection
Notes for Windows users: The .exe installer requires Administrator privileges during installation. Windows Defender may flag the installer on first download — this is a common false positive for browser automation software. You can verify the download hash on the Multilogin website before proceeding. If your organization uses endpoint protection software, whitelist the Multilogin application directory after install.
Mac
Minimum requirements:
- macOS 10.15 Catalina or later
- Intel or Apple Silicon (M1, M2, M3) — native ARM support included
- 4 GB RAM (8 GB recommended)
- 2 GB free disk space
Notes for Mac users: On first launch after installing the .dmg, macOS Gatekeeper will typically block the app with a message that it is from an unidentified developer. Go to System Settings > Privacy & Security, scroll down, and click Open Anyway next to the Multilogin entry. This is standard procedure for any professional software not distributed through the Mac App Store.
Apple Silicon Macs run Multilogin natively — there is no Rosetta translation overhead. Performance on M-series hardware is noticeably snappier than on equivalent Intel hardware.
Linux
Minimum requirements:
- Ubuntu 18.04 LTS or later (20.04 and 22.04 are the most tested)
- Compatible Debian-based distributions (Linux Mint, Pop!_OS, etc.)
- Red Hat-based systems (Fedora, CentOS, RHEL) via the .rpm package
- 4 GB RAM (8 GB recommended)
- 2 GB free disk space
Notes for Linux users: The Multilogin agent runs as a background service after installation. On Ubuntu, it installs a systemd service that starts automatically on boot. For headless server environments, Multilogin X requires a display (real or virtual via Xvfb) because the browser profiles need a rendering context — it is not designed for fully headless CLI-only servers.
Downloading & Installing Multilogin
Step 1: Log In to Your Multilogin Account
Go to multilogin.com and log in. If you do not have an account yet, sign up for the trial — you will need an account before you can download the installer, as Multilogin authenticates the local agent against your account credentials on first launch.
Step 2: Navigate to the Downloads Page
Once logged in, look for the Downloads section in the dashboard navigation or in your account settings. Multilogin X provides OS-specific installers:
- Windows:
.exeinstaller (64-bit only) - Mac:
.dmgdisk image (universal binary for Intel + Apple Silicon) - Linux:
.debpackage (Debian/Ubuntu) and.rpmpackage (Red Hat/Fedora)
Download the installer for your OS. The files are typically 200–400 MB.
Step 3: Run the Installer
Windows:
- Double-click the
.exefile. Accept the UAC prompt for administrator permissions. - The installer extracts files and installs the Multilogin agent and the browser engines (Mimic and Stealthfox are downloaded as part of first-run setup, not bundled in the installer — expect an additional 300–500 MB download on first launch).
- The installer creates a start menu shortcut and optionally a desktop shortcut.
- Launch Multilogin X from the start menu.
Mac:
- Open the
.dmgfile. Drag the Multilogin app to your Applications folder. - Launch from Applications. If Gatekeeper blocks it, go to System Settings > Privacy & Security and click Open Anyway.
- Multilogin will request permission to run in the background as a local agent — allow this.
Linux (Ubuntu/Debian):
sudo dpkg -i multilogin-x_*.debOr install via your package manager if you have added the Multilogin repository. After installation, the agent starts automatically. Check its status with:
sudo systemctl status multiloginStep 4: Log In to the Local Agent
After launch, Multilogin X opens a local dashboard in your default browser (usually at localhost:35000 or similar). Log in with the same credentials you use on the Multilogin website. The local agent will authenticate against Multilogin’s servers and pull your account data, including any profiles you have previously created.
On first login, the agent may download the Mimic (Chromium) and Stealthfox (Firefox) browser engines if they are not already installed. This takes 2–5 minutes depending on your connection speed.
Once the login completes and the engines are downloaded, you are ready to create your first profile.
Creating Your First Browser Profile
A browser profile in Multilogin is an isolated browser environment with its own fingerprint, cookies, storage, and optionally its own proxy. Profiles do not share data with each other or with your regular browser — that isolation is the core function of the tool.
Choose Your Browser Engine
When creating a new profile, the first decision is which browser engine to use:
- Mimic — Chromium-based. Best choice if you are managing accounts on platforms that work best in Chrome (Google Ads, Facebook Ads Manager, most SaaS tools). Renders and behaves like a recent version of Chrome.
- Stealthfox — Firefox-based. Useful for diversifying your fingerprint pool across a large account operation, or for specific platforms where Firefox presents a lower-risk fingerprint. Less common choice for most operators but worth having in the mix for high-volume work.
For a first profile and for most multi-account use cases, start with Mimic.
Configure the Profile Fingerprint
Click New Profile in the Multilogin dashboard. You will see a profile creation form with fingerprint configuration options. Here is how to handle each setting:
Profile name: Use a naming convention that makes sense for your operation — the platform name, account identifier, or client name. You will accumulate profiles quickly; good naming saves time later.
OS fingerprint: Match the OS fingerprint to your actual operating system or a realistic alternative. If you are on Windows and create a profile with a macOS fingerprint, the fingerprint is internally consistent, but mixing OS fingerprints across a large account set tied to the same IP can look unusual. For most operators, keeping the OS fingerprint matching your actual OS is the safest default.
Screen resolution: Set a resolution common for your target OS. For Windows: 1920x1080 or 2560x1440 are both realistic and common. Avoid unusual resolutions that appear infrequently in real-world browser traffic.
Timezone: Match the timezone of your proxy’s exit location. If your proxy exits in New York, set the timezone to America/New_York. Mismatched timezones between IP geolocation and browser timezone are one of the most common fingerprint consistency errors I see in client setups.
Language: Set the browser language to match the locale of your proxy exit. A US IP with a browser set to ru-RU is a fingerprint red flag.
WebGL and Canvas noise: Multilogin automatically applies noise to WebGL and Canvas rendering to make the fingerprint unique and prevent cross-profile correlation. Leave these on the default noise settings for most use cases. Disabling them makes profiles easier to correlate.
Fonts: Multilogin randomizes the font list within realistic parameters. The default settings are fine; advanced operators can customize font sets per OS if they need tighter control.
User agent: Automatically generated to match the selected browser engine and OS. You can override it manually, but auto-generated user agents that stay current with Multilogin’s update cycle are generally more realistic than manually crafted ones.
Save and Launch the Profile
Click Save (or Save & Open to launch immediately). The profile appears in your profile list. To launch it, click the Start button next to the profile name. Multilogin opens an isolated browser window using the engine and fingerprint you configured.
You can verify the fingerprint by visiting a fingerprint testing site like BrowserLeaks or Whoer from within the profile. The reported values should match what you configured, and the browser should appear as a standard Chrome or Firefox browser with no obvious automation markers.
Adding a Proxy & Troubleshooting
Proxy Setup in Multilogin
For any multi-account operation, you need one dedicated proxy per profile. Sharing a single IP across multiple accounts defeats the purpose of fingerprint isolation — platforms that track account networks can correlate accounts by shared IP regardless of how clean the fingerprints are.
Multilogin supports:
- HTTP/HTTPS proxies — the most common type; works with most residential and datacenter proxy providers
- SOCKS5 proxies — supports UDP traffic in addition to TCP; useful for certain platforms and more versatile for advanced setups
To add a proxy to an existing profile:
- In the profile list, click the three-dot menu next to the profile name and select Edit.
- Navigate to the Proxy tab in the profile settings.
- Select your proxy type (HTTP, HTTPS, or SOCKS5).
- Enter the proxy host (IP address or hostname) and port.
- If the proxy requires authentication, enter the username and password.
- Click Check Proxy — Multilogin will test the connection and display the detected IP, country, and timezone. Verify these match what you expect from your proxy provider.
- If the check passes, click Save.
To add a proxy during profile creation:
The Proxy tab appears in the New Profile form. The steps are identical to editing an existing profile. I recommend setting the proxy before finalizing other fingerprint settings, so you can match the timezone and language to the proxy’s exit location in one step.
Proxy types for multi-account work:
| Proxy Type | Best For | Notes |
|---|---|---|
| Residential rotating | High-volume scraping, ad verification | New IP each request; not ideal for persistent account sessions |
| Residential static (ISP) | Social media accounts, ad accounts | Same IP across sessions; best for account trust |
| Datacenter | Research, low-risk platforms | Cheaper; more likely to be flagged on trust-sensitive platforms |
| Mobile | Highest-trust accounts, mobile-heavy platforms | 4G IPs carry high organic traffic; expensive |
For most client account management work — managing ad accounts, social profiles, or marketplace seller accounts — residential static (ISP) proxies are the right tool. The IP stays consistent across sessions, which platform trust algorithms associate with normal human behavior.
Set up your first Multilogin profile
Common Errors and How to Fix Them
“Agent is not running” or dashboard fails to load:
The Multilogin local agent is not started. On Windows: look for Multilogin X in the system tray or start it from the Start menu. On Linux: run sudo systemctl start multilogin. On Mac: relaunch the application from the Applications folder.
Browser engine download stuck or failing: On first setup, Mimic and Stealthfox download separately after the main app installs. If the download stalls, check your internet connection and firewall — some corporate firewalls block large binary downloads. Try pausing and resuming from the dashboard. If it continues to fail, download the browser engines manually from the Multilogin downloads page and install them locally.
Proxy check fails with “Connection refused”: Verify the proxy host and port are correct. Check with your proxy provider that the proxy is active and the credentials have not expired. Some proxy providers require IP whitelisting on their end — make sure your machine’s outbound IP is whitelisted in your proxy dashboard. SOCKS5 proxies sometimes require enabling UDP support separately.
Profile fingerprint flagged on BrowserLeaks: Usually caused by a timezone mismatch between the proxy IP and the browser timezone setting. Open the profile settings, run the proxy check to confirm the proxy’s detected country and timezone, then update the browser timezone in the fingerprint settings to match. Save and re-test.
“License limit reached” error when launching profiles: Your current Multilogin plan has a cap on simultaneously running profiles. Close profiles you are not actively using. If you routinely need more concurrent profiles, review your plan tier on the Multilogin pricing page — higher tiers increase the concurrent profile limit.
Profile launches but websites immediately log out or block access: This is rarely a Multilogin configuration issue — it is usually a proxy quality issue. Low-quality datacenter proxies are blocked by most major platforms. Switch to a residential or ISP proxy for the affected accounts. Also verify the cookies in the profile are not corrupted; if a profile was previously used with a different proxy, clear the cookies and start a fresh session with the new proxy.
What to Do After Your First Profile Is Running
Once you have the agent installed, a profile created, and a proxy connected, the core setup is complete. A few things that improve day-to-day operations:
Organize profiles with tags and folders. Multilogin lets you tag profiles and group them into folders. For any operation with more than ten profiles, set up a folder structure from the start — by client, by platform, or by account type. Reorganizing 200 profiles later is tedious.
Test fingerprint consistency before launching accounts. For any accounts that carry significant value, take five minutes to test the profile on BrowserLeaks.com and check that the IP, timezone, language, and WebGL all return realistic, consistent values. This investment pays off in lower account loss rates.
Use the Multilogin API for automation. If you are running large-scale operations, Multilogin X exposes a local REST API that lets you start and stop profiles programmatically, integrate with Puppeteer or Playwright, and build automation workflows without touching the UI. The API documentation is in the Multilogin developer docs.
Review the browser engine update cadence. Multilogin updates Mimic and Stealthfox regularly to track Chromium and Firefox releases. Running outdated engines is a fingerprinting risk — a browser claiming to be Chrome 120 when Chrome 130 is current stands out. Check for and apply engine updates monthly.
For a deeper look at how Multilogin stacks up against other anti-detect browsers, see the best anti-detect browser for multi-accounting comparison. If you are evaluating whether Multilogin fits your specific workflow, the full Multilogin review covers real-world testing across multiple account types and platforms.
Frequently Asked Questions
How do I download Multilogin?
Go to multilogin.com, log in or create an account, navigate to the Downloads section, and choose the installer for your operating system — .exe for Windows, .dmg for Mac, or .deb/.rpm for Linux. Run the installer, launch the Multilogin X agent, and log in with your account credentials to get started.
Is Multilogin available for Mac?
Yes. Multilogin X supports macOS 10.15 (Catalina) and later, including both Intel and Apple Silicon (M1/M2/M3) Macs. Download the .dmg installer from multilogin.com, open it, drag the app to your Applications folder, and launch it. You may need to approve the app in System Settings under Privacy & Security on first launch.
Does Multilogin work on Linux?
Yes. Multilogin X supports Ubuntu 18.04 and later and compatible Debian-based distributions. Download the .deb package from multilogin.com and install it with dpkg -i or via your package manager. RPM packages are also available for Red Hat-based systems. The local agent runs as a background service; you interact with it through the Multilogin dashboard in your regular browser.
How do I create a profile in Multilogin?
After logging in to the Multilogin dashboard, click New Profile. Choose your browser engine — Mimic (Chromium-based) or Stealthfox (Firefox-based) — then configure the fingerprint parameters including OS, screen resolution, timezone, language, and WebGL settings. Give the profile a name, optionally assign a proxy, and click Save. The profile now appears in your profile list and can be launched with one click.
How do I add a proxy to Multilogin?
Open the profile settings for an existing profile (or set the proxy during profile creation). Navigate to the Proxy section and select your proxy type — HTTP, HTTPS, or SOCKS5. Enter the host, port, and credentials if required. Click Check Proxy to verify the connection before saving. Multilogin recommends one dedicated proxy per profile to maintain clean separation between browser environments.
Mara Vale is a Multi-Account Operations Consultant with 10+ years in performance marketing and digital operations. He tests anti-detect browsers, proxies, and automation tools across real client account environments.