← Back to Blog

Proxy for a Single Chrome Profile: --proxy-server, Extensions, Profiles

We explore three working methods to connect a proxy to a single Chrome profile without using an anti-detect browser: command line, extensions, and separate launch shortcuts.

📅November 17, 2026

If you manage multiple Facebook, Instagram accounts, or fill out cards on Wildberries from different browser profiles, sooner or later the question arises: how to attach a proxy to each Chrome profile without affecting the others. The standard system settings change the proxy for the entire OS at once, which leads to blocks when multi-accounting. In this article, we will discuss three working methods to isolate a proxy for a specific Chrome profile without purchasing an anti-detect browser.

Why Isolate Proxy at the Profile Level

The usual proxy settings in Windows or macOS are applied globally — to all programs at once. This is fine for a single account, but if you manage 5-10 Instagram accounts through different Chrome profiles, a global proxy is useless: all profiles will still go online from one IP, and the platform will quickly link them together by cookies, browser fingerprint, and IP address. The result is mass blocking (chain-ban).

Arbitrageurs who farm Facebook Ads or TikTok Ads accounts, and SMM specialists managing client accounts need each Chrome profile to go online through its unique IP. This reduces the risk of account linking and bans due to IP fingerprinting. A separate proxy for each profile is also beneficial for marketplace sellers: if you monitor prices on Wildberries or Ozon from different accounts, different IPs will prevent the platform from suspecting scraping.

There are three ways to solve this problem without an expensive anti-detect browser: command line flag, an extension within the profile, and separate launch shortcuts with an attached profile. Let’s examine each in detail.

Method 1: --proxy-server Flag in Launch Shortcut

Chrome supports launching with command line parameters, including specifying a proxy server for a specific instance of the browser. This is the quickest way to test a proxy on one profile without installing extensions.

Create a Chrome shortcut (right-click on the desktop → New → Shortcut, specify the path to chrome.exe), then open its properties and add the parameters in the "Target" field after the path:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="http://123.45.67.89:8000" --user-data-dir="C:\ChromeProfiles\Profile1"

The --proxy-server parameter sets the address and port of the proxy, while --user-data-dir specifies a separate profile folder — this is critically important, otherwise all opened Chrome windows will share one profile and one proxy. For SOCKS5, the format is as follows:

--proxy-server="socks5://123.45.67.89:1080"

If the proxy requires a username and password, the --proxy-server flag does not accept them directly — Chrome will show a login prompt on the first request. To bypass the prompt, you can use an extension or a proxy without login authorization (IP-based). In practice, for accounts where stability is important, arbitrageurs often prefer residential proxies — they have built-in support for authorization through extensions, which will be discussed below.

For each subsequent profile, create a new shortcut with a different proxy port and a different user-data-dir folder. This way, you will have a set of shortcuts — one for each account, each with its isolated proxy and cookie profile.

Method 2: SwitchyOmega and Proxy Helper Extensions

If login/password authorization is mandatory and reconfiguring shortcuts every time is inconvenient, use a proxy manager extension directly within the profile. The most popular ones are Proxy SwitchyOmega and Proxy Helper from the Chrome Web Store. They are installed once in a specific profile and store proxy settings within that profile, without affecting the others.

Steps to set up SwitchyOmega:

  1. Open the desired Chrome profile (through the profile menu in the upper right corner).
  2. Install the SwitchyOmega extension from the Chrome Web Store specifically in this profile.
  3. In the extension settings, create a new proxy profile: specify the protocol (HTTP, HTTPS, or SOCKS5), IP address, and port.
  4. If the proxy requires a username and password — enter them in the corresponding fields, the extension will save the authorization and will not show a popup.
  5. Activate the created proxy profile as the main one for this browser window.

The advantage of this method is flexibility: you can switch proxies directly from the extension icon without restarting Chrome. The downside is that the extension is visible to the platform's anti-fraud systems as installed third-party software, which in rare cases may affect the assessment of the browser's trustworthiness. For most SMM and e-commerce tasks, this is not critical.

For mobile traffic (for example, when working with TikTok Ads, where it is important for the IP to appear as a regular smartphone operator), it is better to connect mobile proxies — they trigger protective systems less frequently because they use real IPs from telecom operators with rotation.

Method 3: Separate Chrome Profiles with Launch Shortcuts

This method combines the built-in Chrome profile system (Profile → Add Profile) with the --proxy-server flag from the first method. The essence is that you create a standard Chrome profile through the browser interface (with its icon, name, history, and cookies), and then make a separate shortcut for it with the attached proxy.

Steps:

  1. In Chrome, click on the profile icon → "Add" → create a new profile with a name, for example, "Instagram_Client1".
  2. Find the path to this profile's folder: go to chrome://version and check the "Profile" value.
  3. Create a chrome.exe shortcut and in the properties write the --profile-directory flag with the folder name (for example, "Profile 3") and the --proxy-server flag with the desired address.
  4. Save and use this shortcut to launch the client account — not through the regular Chrome profile menu, but through the created shortcut.
"C:\Program Files\Google\Chrome\Application\chrome.exe" --profile-directory="Profile 3" --proxy-server="http://45.67.89.10:8000"

This approach is convenient for SMM agencies: a separate profile is created for each client with a clear name and icon, and the proxy is attached via a desktop shortcut. The folder with shortcuts turns into a quick access panel to all managed accounts.

Comparison of Methods

Method Login/Password Authorization Ease of Switching Suitable for
--proxy-server in Shortcut No (IP authorization required) Low — editing the shortcut Quick test, 1-3 accounts
SwitchyOmega / Proxy Helper Yes High — click from the icon SMM, 5-20 accounts
Chrome Profiles + Shortcut No (IP authorization required) Medium — separate shortcut for each account Agencies, client accounts

If the proxy provider supports whitelisting by IP (authorization without a username and password), the first and third methods become more convenient — there is no need to enter credentials at all. This is especially relevant for data center proxies, which often use this type of authorization when scraping marketplaces.

WebRTC and DNS Leaks: How to Check

Attaching a proxy to a profile via a flag or extension does not solve one important problem — leaking the real IP through WebRTC. The browser can reveal your actual address directly, bypassing the proxy, if the page code uses a WebRTC request (this is common in Facebook and TikTok ad trackers).

To prevent this, additionally install an extension to block WebRTC in each profile with a proxy (for example, WebRTC Leak Shield or the built-in blocking in SwitchyOmega, if supported). After setting up, be sure to check the profile on sites like browserleaks.com or ipleak.net: they show which IP is detected through a regular request, through WebRTC, and which DNS server is being used.

If the DNS server is identified not from the proxy provider but from your internet provider — this is also a leak that can reveal your real location. In Chrome settings (chrome://settings/security), switch DNS over HTTPS and ensure that the DNS corresponds to the region of the proxy.

When to Switch to an Anti-Detect Browser

Manual proxy configuration through flags and extensions works great for 3-10 profiles. But if you manage 30-50 Instagram accounts or farm Facebook Ads ad accounts in batches, manual management of shortcuts and profiles becomes inconvenient and vulnerable: regular Chrome, even with different profiles, gives the same canvas fingerprint, the same fonts, and WebGL parameters for all accounts. Platforms detect this as multi-accounting regardless of IP changes.

In this case, it makes sense to switch to an anti-detect browser: Dolphin Anty, AdsPower, Multilogin, GoLogin, or Octo Browser. They generate a unique digital fingerprint for each profile and inherently bind the proxy to the profile without the hassle of shortcuts and flags — you simply enter the IP, port, username, and password in the corresponding profile settings field. This is especially important when scaling: 5 profiles can be managed manually, but 50 can only be done through specialized tools.

For selecting proxies for such scenarios, residential proxies with session binding are suitable — they allow you to keep the same IP for an account for a long time, which is important for warming up and farming.

Conclusion

You can bind a proxy to a single Chrome profile in three ways: the --proxy-server flag in a shortcut for quick testing, the SwitchyOmega extension for convenient management with login/password authorization, or a combination of built-in Chrome profiles with separate shortcuts for agency work with client accounts. Each method isolates the profile's traffic from the rest of the system but does not solve the problem of the browser's digital fingerprint — for scaling beyond 10-15 accounts, it is advisable to switch to an anti-detect browser.

If you are just starting with multi-accounting and testing the scheme on 3-5 profiles, data center proxies are suitable for starting out — they are cheaper and faster for simple tasks like checking availability or basic SMM. For working with ad accounts and social networks, where stability and similarity to a regular user are important, it is better to immediately use residential or mobile IPs to avoid wasting time on reconfiguration after the first blocks.